Páginas filhas
  • Fixed Assets Project (ATFA430 - SIGAATF)

CONTENTS

01. OVERVIEW

This routine facilitates the accounting record of projects to generate fixed assets, whether tangible or intangible, in the duration of its execution.

You can register the project, the stages and the integration with fixed asset forms, as well as the technical interpretation ICPC 01 - Concession Contracts.

Important

This feature only controls the expense project, not generating revenue and not being integrated with module Project Control.

In the project, you can: Add, Edit and View.


02. FIXED ASSETS PROJECT CREATION EXAMPLE

To register and activate a fixed asset project:

  1. Enter routine ATFA430, accessing module SIGAATF > Updates > Register > Fixed Assets Project.
  2. Click Add.
  3. Fill in the fields of folder Project. This folder contains fields related to the project, APV and also to define the asset code that the project will generate. See below some examples of how to fill them in:
  4. Fill in the fields of folder Stage. This folder contains fields related to the stages of the fixed assets project. See the example below:


Tip

You may register more than one stage in the project, in which for each stage you need to fill in the stage item. The system does not allow registering the next stage without first filling in the stage items in table FND.


5. Fill in the fields of folder Stage Item. This folder contains the fields related to the project's stage items, in which you can set whether to generate asset form and whether to generate its value, description, etc. See below an example of stage 001 item registration:


Tip

The field Plan Value defines the original value of the asset and is tied to the original value of tab accounting configuration. Yet field Exec Prev. Date feeds field N1_DTAVP in the asset, provided field FND_INDAVP (this field is triggered when you fill in FNB_INDAVP) is filled in with the index desired.

6. Fill in the fields of folder Accounting Configuration. This folder contains fields related to the accounting classification of assets to be generated, thus select the Stage Item in which you will make the configuration and access tab Accounting Configuration. You can fill in the asset group, the accounting entities, the depreciation rate, etc. See below an example of completion:

7. After feeding all folders in accordance with the needs of the project, click Confirm.

8. Now, to generate the Assets related to the Project, make the selection in the Project desired (the white caption must be present) and click Update and Confirm:

9. An asset form is generated for each project item, which you may check in routine ATFA012.


Important

After generating the asset, you can neither use option Edit to edit the project, nor can you use option Delete in Related Features to delete it. You can only use options Revision and Lock.

03. FIXED ASSETS PROJECT REVISION

You can run the Revision process when the Project is active in ATFA430 (status Green); that is, project assets are already generated, but the project requires changes. Thus, option Revision posts the assets generated, changes the current revision status to Locked - Revision and creates a new revision for the project with status Generated. Therefore, in this new revision generated, you can make the adjustments needed, editing it and generating the assets again in option Other Actions > Update.

To make a Revision, select the Revision desired and click Other Actions > Revise:

Confirm the operation:

04. FIXED ASSETS PROJECT LOCKING

You can run the Locking process when the Project is active in ATFA430 (status Green); that is, project assets are already generated, but you need to Lock the project for the moment. 

To apply a Lock, select the Revision desired and click Other Actions > Lock/Unlock:

Change the field Lock to Yes and Confirm it:

05. APPROVAL RULES FOR REVISION AND LOCKING

Due to the activation of approval control for revision and locking operations of fixed asset projects, after using options Revise and Lock, a screen is displayed for adding a justification for the revision or for locking. The approver defined in the competence uses this information to approve or reject the request for revision or locking made by the user.

Utilization Rules of approval control for revising fixed asset projects

After revising a fixed asset project with approval control, the project's current revision remains active until the revision request is evaluated. Thus, the new revision of the project has its status locked by revision.

When you confirm the addition of the revision, the system displays a screen for you to enter a justification for the revision, which the approver defined in the authorizations register must evaluate.

    • If the revision is approved, the project's active version is locked by revision and the new revision is activated.
    • If the revision is rejected, the project's current revision remains active and the new revision acquires the status locked by approval.
    • To start a new revision approval process, edit the revision locked by approval. When you confirm the editing, the system again displays the screen for adding a justification, which the approver defined in the authorizations register later evaluates.
    • If you do not want to edit the locked revision to keep that rejection's history, you can create a new revision of the active project. The process for this action is the same described above.

Utilization Rules of approval control for locking fixed asset projects

After locking a fixed asset project with approval control, the project's current revision remains active until the locking request is evaluated.

When you confirm the locking of the project, the system displays a screen for you to enter a justification for the locking, which the approver defined in the authorizations register must evaluate.

    • If the locking is approved, the status of the project's active revision is updated to 9 - LOCKED - USR (locked by user).
    • At this point, the system locks all fixed asset forms linked with the project.
    • If the locking request is rejected, the project's current revision remains active, but the user may start a new locking approval process by again using option Lock.

You can enable the Competence process in routine ATFA002, configure it in routine ATFA003 and perform Approval/Rejection in routine ATFA004. Be mindful that, when you activate approval control and execute a Revision/Locking, instead of becoming active directly, it requires approval in ATFA004 for the system to activate it.


06. OTHER INFORMATION