en:asset
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:asset [2023/05/22 14:26] triinp [6.6.3. Example - fixed asset history is generated 2 months ahead] |
en:asset [2023/05/23 09:38] (current) triinp [9.3.3. System setting: Asset and Employee relation] |
||
|---|---|---|---|
| Line 733: | Line 733: | ||
| * If a value correction has been indicated on the fixed asset, and **depreciation has been calculated on this amount, this value correction can no longer be deleted** (row is locked). If the depreciation transactions are deleted, it is possible to delete the value correction. | * If a value correction has been indicated on the fixed asset, and **depreciation has been calculated on this amount, this value correction can no longer be deleted** (row is locked). If the depreciation transactions are deleted, it is possible to delete the value correction. | ||
| - | * A negative value correction can also be entered. For negative amounts, enter the amount with a minus sign. This lowers the current price and the monthly amortization amount decreases. Cannot enter a minus sum that exceeds the current price - the system informs **"Min. amount is greater than current price"** and does not allow saving. | + | * A negative value correction can also be entered. For negative amounts, enter the amount with a minus sign. This lowers the current price and the monthly amortization amount decreases. Cannot enter a minus sum that exceeds the current price - the system informs **"Remianing value is greater than current price"** and does not allow saving. |
| * If the value correction needs to be entered in the past, but depreciation has already been calculated for that period, the system warns **"The asset has later changes"** and does not allow to save. If necessary, these depreciation transactions can be deleted along with the history, and then the value correction can be entered into the past. | * If the value correction needs to be entered in the past, but depreciation has already been calculated for that period, the system warns **"The asset has later changes"** and does not allow to save. If necessary, these depreciation transactions can be deleted along with the history, and then the value correction can be entered into the past. | ||
| - | ==== 7.2. Effect of value correction entry dates on depreciation ==== | + | ==== 7.2. Influence of value correction entry dates on depreciation ==== |
| * If the monthly depreciation transaction has been made (eg March 2023) and the value correction is added with the last date of the given month (e.g. 31.3.2023), then value correction goes into the depreciation calculation starting from the next month, i.e. April. If the value correction is added up to the date of the last month (e.g. with a date between 1-30.3.2023), then the system does not allow it and gives an error "The asset has later changes". If the depreciation transactions for March 2023 are deleted, it is possible to add a value correction to March 2023. | * If the monthly depreciation transaction has been made (eg March 2023) and the value correction is added with the last date of the given month (e.g. 31.3.2023), then value correction goes into the depreciation calculation starting from the next month, i.e. April. If the value correction is added up to the date of the last month (e.g. with a date between 1-30.3.2023), then the system does not allow it and gives an error "The asset has later changes". If the depreciation transactions for March 2023 are deleted, it is possible to add a value correction to March 2023. | ||
| Line 765: | Line 765: | ||
| | | ||
| - | ===== 7. Address on fixed asset and low value asset card ===== | + | ===== 8. Address on fixed asset and low value asset card ===== |
| - | ==== 7.1. Setting the addresses ==== | + | ==== 8.1. Setting the addresses ==== |
| Line 782: | Line 782: | ||
| - | ==== 7.2. Entering addresses location codes ==== | + | ==== 8.2. Entering addresses location codes ==== |
| Line 802: | Line 802: | ||
| - | ==== 7.3. Use of address location codes ==== | + | ==== 8.3. Use of address location codes ==== |
| Line 813: | Line 813: | ||
| - | ==== 7.4. Display location fields on the Fixed Asset and Low Value Asset card ==== | + | ==== 8.4. Display location fields on the Fixed Asset and Low Value Asset card ==== |
| The location code is in the data group ** LOCATION ** on the fixed asset card. More fields of the location code can be displayed under the Fixed Asset card fine-tuning - ''Asset location additional info fields''. | The location code is in the data group ** LOCATION ** on the fixed asset card. More fields of the location code can be displayed under the Fixed Asset card fine-tuning - ''Asset location additional info fields''. | ||
| - | ===== 8. User management ===== | + | ===== 9. User management ===== |
| Fixed assets can be linked to users with purpose to have an overview who owns or is responsible for the asset. Users are managed using the fields ** User ** and ** In charge ** on the asset main page or in the tab** Users **: | Fixed assets can be linked to users with purpose to have an overview who owns or is responsible for the asset. Users are managed using the fields ** User ** and ** In charge ** on the asset main page or in the tab** Users **: | ||
| Line 824: | Line 824: | ||
| {{:et:triinp20220404-155914.png}} | {{:et:triinp20220404-155914.png}} | ||
| - | ==== 8.1. Simple user management ==== | + | ==== 9.1. Simple user management ==== |
| Line 833: | Line 833: | ||
| - | ==== 8.2. Detailed user management ==== | + | ==== 9.2. Detailed user management ==== |
| Line 857: | Line 857: | ||
| {{:et:triinp20220408-125539.png}} | {{:et:triinp20220408-125539.png}} | ||
| - | ==== 8.3. Setup and usage options ==== | ||
| - | === 8.3.1. Relation between assets and personnel assets === | + | ==== 9.3. Setup and usage options ==== |
| + | |||
| + | === 9.3.1. Relation between assets and personnel assets === | ||
| It is necessary to set the assets **Types**, in order to save assets lines to **Assets** tab in Employee card. A list of asset types is created ''Settings -> Personnel settings -> Data Types -> Asset'': | It is necessary to set the assets **Types**, in order to save assets lines to **Assets** tab in Employee card. A list of asset types is created ''Settings -> Personnel settings -> Data Types -> Asset'': | ||
| Line 876: | Line 877: | ||
| - | === 8.3.2. Setting: An asset can have one active In charge user or User at the same time === | + | === 9.3.2. Setting: An asset can have one active In charge user or User at the same time === |
| ''Settings -> System settings -> Asset settings -> An asset can have one active In charge user or User at the same time'': | ''Settings -> System settings -> Asset settings -> An asset can have one active In charge user or User at the same time'': | ||
| Line 892: | Line 893: | ||
| {{:et:triinp20220408-140330.png}} | {{:et:triinp20220408-140330.png}} | ||
| - | === 8.3.3. System setting: Asset and Employee relation === | + | === 9.3.3. System setting: Asset and Employee relation === |
| Option **user** and **in charge** is intended for use, when the system setting ''An asset can have one active In charge user or User at the same time = **Yes**'' is selected.\\ | Option **user** and **in charge** is intended for use, when the system setting ''An asset can have one active In charge user or User at the same time = **Yes**'' is selected.\\ | ||
| Line 903: | Line 904: | ||
| - | ==== 8.4. Reports ==== | + | **Column names of the Users tab table** |
| + | |||
| + | The name of the user column in the table depends on the system setting "Asset and Employee relation". | ||
| + | |||
| + | |||
| + | If "User" is selected in the setting or if the setting is empty, then "User" is displayed as the name of the User column. | ||
| + | |||
| + | {{:et:triinp20230523-092811.png}} | ||
| + | |||
| + | |||
| + | If "In charge" is selected in the setting, then the column name will be displayed as "In charge". | ||
| + | |||
| + | {{:et:triinp20230523-093832.png}} | ||
| + | ==== 9.4. Reports ==== | ||
| ON TÄIENDAMISEL !!\\ | ON TÄIENDAMISEL !!\\ | ||
| Line 914: | Line 928: | ||
| {{:et:triinp20220408-141445.png}} | {{:et:triinp20220408-141445.png}} | ||
| - | ===== 9. Asset actions ===== | + | |
| + | ===== 10. Asset actions ===== | ||
| [[en:inv_tegevus|]] codes are created to monitor different fixed assets actions. \\ | [[en:inv_tegevus|]] codes are created to monitor different fixed assets actions. \\ | ||
| Line 922: | Line 937: | ||
| - | ===== 10. Fixed Assets register ===== | + | ===== 11. Fixed Assets register ===== |
| [[et:t_list|]] allows to sort fixed asset cards, etc. | [[et:t_list|]] allows to sort fixed asset cards, etc. | ||
| Line 943: | Line 958: | ||
| :!: Asset history report still shows future periods depreciation, if ** Update history ** is prepared for a future period. Press ** Delete history ** in order for the Asset History report to show only the actual depreciation. | :!: Asset history report still shows future periods depreciation, if ** Update history ** is prepared for a future period. Press ** Delete history ** in order for the Asset History report to show only the actual depreciation. | ||
| - | ===== 11. Frequently Asked Questions ===== | + | ===== 12. Frequently Asked Questions ===== |
| - | ==== 11.1. How do I get rid of a draft? ==== | + | ==== 12.1. How do I get rid of a draft? ==== |
| * If a draft is left from document, cannot be saved and reports an error, then the error message can be removed by closing the asset card, reopening it and pressing **Discard**. | * If a draft is left from document, cannot be saved and reports an error, then the error message can be removed by closing the asset card, reopening it and pressing **Discard**. | ||
| Line 959: | Line 974: | ||
| - | ==== 11.2. Why can't the draft be saved? ==== | + | ==== 12.2. Why can't the draft be saved? ==== |
| * If the document does not have an active save button, may some fields contain code, that does not exist in Directos. | * If the document does not have an active save button, may some fields contain code, that does not exist in Directos. | ||
