Fixed Asset Implementation Guide
Translated by
ScribdTranslationsFixed Asset Implementation Guide
Translated by
ScribdTranslationsPage 1 of 3
Redandpackaging
I FixedAssets
Revision: 08/12/2004
Scope
Versão 7.10
Fixed Asset Implementation Script
Basic Registrations
Tips:
zExplain the necessity of filling in the mandatory fields (fields in
blue color).
zCheck if there is a need to create new specific fields for the
client. Use the configurator for this.
zThe Moeda 3 (UFIR) is already set up as the currency for calculating Fixed Assets.
zThe UFIR had its rate frozen at 0.8287 on 12/16/1995 (Law No. 9249 art.
IV), with the extinction of the indexers.
zThe Purchasing module can be integrated with Fixed Assets through the field 'Current.'
The 'Asset' of the TES. In this way, the asset is already automatically recorded in the registration of
assets should only be classified.
Registrations:
zCoins
{ Use this registration to inform the daily rate of the UFIR (0.8287). If the
customers controlling the asset in other currencies must be informed of the
daily quotes of these currencies.
zCentros de Custo
{ Only those should be registered if the accounting module (Accounting or
Managerial Accounting) is not in use.
zChart of Accounts (Accelerator: CT1 model database)
{ It should only be registered if the accounting module (Accounting or
Managerial Accounting) is not in use.
z Suppliers (Accelerator: SA2 Import Program)
{ In the Fixed Asset module, this registration is merely informative and may
including being dismissed.
z Assets (Accelerator: SN1/SN3 Import Program)
Page 2 of 3
{ Here, the company's assets (permanent assets) must be registered.
{ The acquisition and depreciation data of the asset must be provided.
{ Configure the parameters MV_ULTDEPR, MV_ATFMOED, MV_MOEDA3,
MV_MOEDAP3 and MV_SIMB3.
Note: If the user wants to make the monetary correction (even if not
it must be mandatory), the parameter MV_CORREC must contain 'S' and the parameter
MV_VALCORR must contain the rate to be used in the correction.
zActions
{ This registration is optional and should only be used if the company
distributes and controls your actions among the employees.
zEmployees
{ This registration is optional and should only be used if necessary.
to control the transfer of shares between the company's employees.
They should only be registered if the Personnel Management module is not.
is in use.
Miscellaneous
zIntegrity Check
{ Use this routine to check the integrity of the Fixed Asset files.
after the importation of the goods or after a calculation of depreciation.
zRebuild Balances
{ Use this routine to reconstruct the Balance File (SN5). The Balance
can be reconstructed from the Asset Register (SN1+SN3) or from
Movement File (SN4).
Accounting Integration Process Fixed Assets
If there is accounting integration, the following registration must be implemented:
zStandardized Releases (Accelerator: CT5 model database)
Be aware of:
zFill in the fields: cost centers (acquisition and depreciation) and accounts
fixed assets (depreciation and accumulated depreciation) from the registration of
assets.
zSetthe MV_ATFCONT parameter.
zEach process has its standardized launch code already determined. The
Releases related to the Fixed Asset Module are as follows:
801 - Implementation of asset - Type 01 (Acquisition)
802 - Implementation of asset - Type 02 (Reassessment)
803 - Implementation of asset - Type 03 (Advance)
804 - Implementation of asset - Type 04 (Law 8200)
Page 3 of 3
805 - Record exclusion - Type 01 (Acquisition)
806 - Exclusion of record - Type 02 (Reevaluation)
807 - Record exclusion - Type 03 (Advance)
808 - Record exclusion - Type 04 (Law 8200)
810 - Cancellation of the record - Type 01 (Acquisition)
811 - Record Deletion - Type 02 (Reevaluation)
812 - Record cancellation - Type 03 (Advance)
813 - Record cancellation - Type 04 (Law 8200)
814 - Cancellation of the Deletion of the record - Type 01 (Acquisition)
815 - Cancellation of the Deregistration - Type 02 (Reassessment)
816 - Cancellation of registration cancellation - Type 03 (Advance)
817 - Cancellation of Registration Deregistration - Type 04 (Law 8200)
820 - Calculation of Depreciation.
821 - Expansion
825 - Miscalculation
827 - Inventory
830 - Transfer
831 - Transfer between companies or branches (does not exist)
835 - Acquisition of Goods by Transfer (508)
836 - Cancellation of Acquisitions by Transfers (508)
840 - Calculation of accelerated depreciation (specific for SBPS - ATFA170)
Related Groups
Principal / Implementation Accelerators / Financial Administrative / Fixed Assets / Standard /
Implementation Script
Top of Page
Common questions
Powered by AINot setting the MV_ATFCONT parameter can lead to improper integration and recording of fixed asset transactions, resulting in inaccurate financial reporting and potential non-compliance with accounting standards. This parameter ensures that each asset process is aligned with the standardized launch codes, maintaining consistency and accuracy in asset management operations .
Creating new specific fields for clients in the Fixed Asset module allows for customized asset tracking and reporting, tailored to meet specific client needs or industry requirements. This customization enhances the functionality of the system, enabling comprehensive data capture that supports precise financial analysis and decision-making specific to the client’s operational context .
Configuring parameters like MV_ULTDEPR and MV_VALCORR is crucial for accurate asset depreciation and correction. MV_ULTDEPR indicates the last depreciation period, facilitating ongoing depreciation calculations, while MV_VALCORR specifies the correction rate if monetary correction is to be performed. This setup ensures precision in calculating an asset's value over time, accommodating potential inflation or market changes .
The Fixed Asset module manages acquisition and depreciation data by requiring detailed registration of each company's permanent assets. Key parameters such as MV_ULTDEPR and MV_ATFMOED must be configured to track asset acquisition dates and calculate accurate depreciation over time, using UFIR as the currency standard for consistency .
Registration codes like 820 and 840 represent specific operations within the Fixed Asset module, such as the calculation of general depreciation and accelerated depreciation, respectively. These codes facilitate streamlined and standardized processing of complex asset management tasks, ensuring consistent application of depreciation policies across assets .
The UFIR rate, which was frozen at 0.8287 per law, serves as the currency standard for calculating the value of fixed assets, ensuring consistent monetary valuation across financial reporting. Its daily rate should be informed in the system for correct asset registration and valuation, aiding in accurate accounting and legislative conformity .
The Fixed Asset module accommodates changes in asset valuation due to legislative changes, like Law 8200, through specific implementation and exclusion records with standardized launch codes. These include asset implementation types such as reassessment (802) and specific law implementations (Type 04). For exclusions or cancellations related to Law 8200, codes like 808 and 813 are used. This systematic approach ensures compliance with legislative requirements while maintaining accurate asset records .
It would be unnecessary to register cost centers and chart of accounts within the Fixed Asset Module if either the Accounting or Managerial Accounting module is already in use. These modules handle the necessary classifications, rendering separate registrations in the Fixed Asset module redundant .
Conducting an integrity check after importing goods or calculating depreciation is vital to ensure that all records within the Fixed Asset system are accurate and consistent. It identifies discrepancies or errors in asset data, maintaining the reliability of financial reporting and preventing potential losses or compliance issues arising from inaccurate asset valuations .
The critical steps in integrating the Purchasing module with the Fixed Asset module include ensuring that the 'Asset' field in the TES is correctly filled to automatically record the asset in the asset registration system. This seamless integration allows for the classification of the asset once acquired .