The Revision Of Data The FA Card (4046912) batch job is created, which deals with posting the Salvage Value according to the value of the Residual Value Calculated field from the Financing Contract and also posting its change during the life of the Financing Contract. Furthermore, this task solves the recording of the change in the depreciation period (WMP) according to the financing period of the currently related financing contract. These are changes that are related to the calculation of accounting depreciation for the asset card.
The Tasks dialog box is added switch boolean Post for direct billing. After switching to Yes, the job checks in Fixed Asset Setup (FA) to see if Post Residual Value is enabled and, if the condition is met, posts the suggested lines for posting Salvage Value directly.
The task works with contracts that are in the Active, Closed, or Settled status.
The task does not work with asset cards that are:
STOCK = Yes
Blocked = Yes
Acquired= No
In the default depreciation book (accounting), in the Disposed Of field = Yes.
The task is divided into three areas Processing of Asset Cards for Contracts / Financed Objects:
Posting the First Salvage Value
If it is enabled to post Salvage Value in the Post Residual Value field in Fixed Asset Setup, the task first checks whether the Contract Extension field = No. Subsequently, he checks whether there is a FA Ledger Entries with FA Postin Type = Salvage Value for the depreciation book for the given asset card.
If no such item is found and the contract is not automatically extended (i.e., it is not a contract in Informal), the job suggests a line to post the first Salvage Value in the Fixed Asset Journal with the same amount as in the Residual Value Calculated field of the Financing Contract.
Posting the Change in Salvage Value and Recording the Change in Depreciation Period (POH)
To check for changes in POH and RV, the task sets a filter for active (not accounted for and not blocked) asset cards that have a value in the field STOCK = No. When a non-conformance is found at the WMP, the task enters the current data from the contract on the asset card. In addition, the task of finding the difference between the RV on the asset card and the RV on the Financing Contract will calculate the difference and suggest lines for posting the change in the RV in the fixed asset journal. If the posting date falls within a closed accounting period, the date is shifted to the first day of the open accounting period.
Cases where changes occur:
Change in Depreciation Period (POH):
when the financing period is properly extended or shortened, when the job checks for consistency between the Depreciation Ending Date on the asset card and the Contractual End Date on the Financing Contract Card tab, provided that the value in the Contract Extension = No field on the Financing Contract Card
during automatic contract extension (on a monthly basis when posting a payment calendar, the so-called Informal), when the task checks the correspondence between the Depreciation Ending Date on the asset card and the Prep. Terminate after extension (Expec. Term. Date After Extension) on the Financing Contract Card tab, provided that the value in the Contract Extension = Yes field on the Financing Contract Card
Change of Residual Value (RV) – in case of proper extension or shortening of the financing period and in case of change in mileage.
The result, after running the Revision Of Data The FA Card task, is:
Overwritten/updated depreciation period data on the asset card
A suggested line in the fixed asset journal to post the Salvage Value difference to the asset card. If direct posting was selected in the Task dialog box before the task was run, the proposed line will also be posted. A detailed description of the task process is described in https://iao.atlassian.net/wiki/spaces/OCDOC/pages/edit-v2/32440526#Proces-zpracov%C3%A1n%C3%AD-%C3%BAlohy
The task can be found and run from the following locations:
in the Fixed Asset overview is located in the Process -> Revision Of Data On The FA Card menu or in the Actions menu, where tasks can be rearranged by the user using the Personalize function
Search using the system magnifier.
Dependencies and assumptions
Correct processing of the job depends on the field settings in the Fixed Asset Setup (FA) table:
Post Residual Value = Yes
Residual Value FA – Template
Residual Value FA – Batch
FA Revision – Template
FA Revision – Batch.
A very important prerequisite: changes to the contract are not older than 60 days (there is a hard-coded restriction in the task).
In the payment calendar, the change of RV will be reflected in the first unposted payment. Therefore, the assumption that the change in RV will be reflected in the asset card is that payments and depreciation are accounted for regularly.
Job Processing Process
When a task is invoked, the task dialog box is displayed first. In the dialog box, the user can select Post. It is also possible to enter filters for data from the Contract Header (e.g. contract number, customer number, contract signing date, etc.). The task will work with the set conditions and filters after it is started by clicking on the OK button.
After starting the task with the OK button, the process of processing the task starts:
In Fixed Asset Setup (FA) Setup, check if the fields listed below are set. If they are not set (field is empty), the job is terminated with an error message
The default depreciation book (Default Depr. Book)
FA Revision – Template / Batch
Residual Value FA – Template / Batch
Example of an error message:
Checks if the journals that are set in the FA Revision – Batch field and the FA Revision – Batch field in the FA Fixed Asset Setup table and the FA Batch residual value field are empty. If the condition is not met, it terminates the processing of the job with an error message. If the condition is met, the processing continues
It applies filters to contracts as follows:
Financing Contract Type = Operative Leasing and Contract with Services = Yes
Contract Status = Active, Closed or Settled
Change Copy = No
Calculation Variant = No
Contract changes not older than 60 days from the start date of the task
If the contract status is other than Active, it assesses the Termination Date
If the Temination Date is empty, it stops processing the contract and moves on to processing the next contract
If there are more than 40 days between the Task Execution Date and the Termination Date, it will stop processing the contract and move on to processing the next contract
Checks if the Source Code must be set in the FA Jobs field in the Source Code Setup table. If the code is not set, it writes an error to the Fixed Assets Log (Fixed Assets Error Log) with the text "The FA Jobs field must have a value of (Must not be zero or empty) in the Source Code Setup: Primary Key= table." (FA Jobs must have a value in Source Code Setup: Primary Key=. It cannot be zero or empty.). Stops processing the contract and moves on to processing the next contract.
He looks at the Financed Object Card and looks up the Fixed Asset No. If there is a blank value in the Fixed Asset No. field, writes to the Fixed Assets Log (Fixed Assets Error Log) Notification "The Fixed Asset No. field must have a value (Must not be zero or empty) in the Financed Object table: Number=xxxxxx." (Fixed Asset No. must have a value in Financed Object: No.=xxxxxx. It cannot be zero or empty.) and continues to process another contract.
On the found asset card, he checks whether it is in the STOCK = YES field or in the Blocked = YES field. In the event of a match, they terminate the process and proceed to process the next contract. If STOCK = No in the field and Blocked = No in the field, the job continues to be processed according to the next steps.
Checks the Acquisition Date in the default (accounting) book of depreciation. If the date is empty, it stops processing the contract and moves on to processing the next contract
If direct posting was used by selecting from the Task dialog box, the task looks at the Default Depr. Book), after the check in the "All Acquisition in same Year = Yes" field is turned on. If the condition is met, the check is set to No and after posting, at the end of the job processing, it is set again to Yes. If he does not comply with the condition, he will do nothing
Processing of RV, i.e. Residual Values (Salvage Value)
Residual Value processing (Salvage Value) is carried out if:
the Post Residual Value field is set to Yes in Fixed Asset Setup
the contract is not automatically extended (not Informal), i.e. in the field Contract Extension = No on the contract.
First RV, Salvage Value
If the property card is traced, there is no items of the Residual Value (Salvage Value) and Depreciation (Depreciation) types find out the RV value, i.e. The Residual Value (Salvage Value) on the Financing Object to the Contract, the OC field tracks the difference in the Residual Value Calculated field from the Financing Contract.
Creates an entry in the Fixed Asset Journal. Filling the diary:
uses the journal template set in the Fixed Asset Setup table, in the Residual Value FA – Template field
uses the journal batch set in the Fixed Asset Setup (FA) table, in the Residual Value FA – Batch field
FA Posting Date (FA Posting Date) is entered by the job on the same date as it is in the Depreciation Starting Date field in the Depreciation Starting Date field on the default (accounting) book
The Document No. is used according to the settings of the FA Journal batch that is used
The Depreciation Book Code takes the set value from the Fixed Asset Setup table, the Default Depr. Book)
The FA No. is filled in with the number of the asset card for which the RV has identified the change
FA Posting Type enters option = Salvage Value
Description enters "Residual Value plus Contract No."
The amount will be filled by the determined RV, i.e. Salvage Value, from the financed object to the contract, turning the sign to a minus
Populates the Source Code with the value set in the FA Jobs field in the Source Code Setup table
Dimension populates from the asset card
If a direct posting was specified in the Jobs dialog box, the proposed line is posted. If direct posting has not been entered, the lines are suggested to the journal and the posting must be done by the user. Then the task moves on to processing the next contract.
Change of RV, Residual Value (Salvage Value)
If the property card is traced, exists items of the Salvage Value and Depreciation types, the task looks at the value in the Calculation Residual Value field on the Financing Contract, in the Default Depr. Book) of the traced asset card looks at the current Book Value and the total Salvage Value.
Compares the RV from the financing contract and the current Book Value in the Default Depr. Book).
If a non-zero difference is found, the task defines a branch of Positive or Negative difference and calculates the RV difference, i.e. calculates the difference between the found RV from the financing contract and the total Salvage Value on the asset card.
To define branches, look at the current Book Value on the asset card and check if the new Salvage Value from the object card is higher than the current Book Value on the asset card:
when it is higher, it defines POSITIVE branch. Calculates the difference between the current Book Value and the new Salvage Value. He then suggests the following lines in the Fixed Asset G/L Journal:
to top up the Book Value in the form of depreciation reductions. Filling the journal lines is described in the process below
for the calculated RV difference in the form of additional accounting of the Residual Value (Salvage Value). Filling the journal lines is described in the process below
when it is not higher, it defines NEGATIVE branch. It then suggests the calculated difference RV, i.e. Salvage Value, to the Fixed Asset Journal. Filling journal lines is described in the process below.
Fill in the fields of Fixed Asset G/L Journal (G/L Journal) lines for the defined POSITIVE RV Difference:
First Line
The Depreciation Book Code takes the set value from the Fixed Asset Setup table, the Default Depr. Book)
uses the journal template according to the settings in the FA Revision – Template field
uses the journal batch according to the settings in the Fixed Asset Setup table from the FA Revision – Batch field
The Posting Date is determined by the task by finding the first unposted line of the payment calendar for the contract. If there is one, it takes Date From plus one day from the searched line. If there is no such line, he finds the last posted line of the payment calendar for the contract and takes Date To as the date. If the calculated date falls within a closed accounting period, it shifts the date to the first day of the open accounting period.
Document No. is used according to the settings of the journal batch used
The Account Type enters the value of the Fixed Asset option
The Account No. is filled in by the number of the processed asset card
FA Posting Type enters the value of the Depreciation option
Description enters Corrective depreciation +account number
The amount is filled with the calculated difference between the Book Value and the new RV
Corection = Yes
Leaves No. of Depreciation Days blank
Populates the Source Code with the value set in the FA Jobs field in the Source Code Setup table
Dimension populates from the asset card
Second line
is filled in using the "Insert FA Counter-Account" function (Insert FA Bal. Account)
Third line
The Depreciation Book Code takes the set value from the Fixed Asset Setup table, the Default Depr. Book)
uses the journal template set in the FA Revision – Template field in the FA Revision (Fixed Asset Setup) table
use the journal batch set up in the FA Revision Batch (FA Revision) field
The Posting Date is determined by the task by finding the first unposted line of the payment calendar for the contract. If there is one, it takes Date From plus one day from the searched line. If there is no such line, he finds the last posted line of the payment calendar for the contract and takes Date To as the date. If the calculated date falls within a closed accounting period, it shifts the date to the first day of the open accounting period.
Document No. is used according to the settings of the journal batch used
The Account Type enters the value of the Fixed Asset option
The Account No. is filled in by the number of the processed asset card
FA Posting Type enters the option Acquisition Cost
Description enters Increase RV + account number
Amount (Amount) leaves blank
Residual Value (Salvage Value) – fills with the calculated difference RV with the opposite sign
Populates the Source Code with the value set in the FA Jobs field in the Source Code Setup table
Dimension populates from the asset card
If a direct posting was specified in the Jobs dialog box, the proposed lines are posted. If direct posting has not been entered, the lines are suggested to the journal and the posting must be done by the user. Then the task moves on to processing the next contract.
Populate the fields of the Fixed Asset Journal general journal lines for the defined NEGATIVE RV Difference:
uses the journal template set in the Fixed Asset Setup table, in the Residual Value FA – Template field
uses the journal batch set in the Fixed Asset Setup (FA) table, in the Residual Value FA – Batch field
FA Posting Date (FA Posting Date) is entered by the task the same as the last FA Ledger Entries for the traced FA card, which should be a depreciation for the previous period. If it does not find, it enters the user's Work Date. If the calculated date falls within the closed FA accounting period, it shifts the date to the first day of the open FA period
The Document No. is used according to the settings of the FA Journal batch that is used
The Depreciation Book Code takes the set value from the Fixed Asset Setup table, the Default Depr. Book)
The FA No. is filled in with the number of the asset card for which the RV has identified the change
FA Posting Type enters option = Salvage Value
The amount is filled with the calculated RV difference, i.e. the difference in Salvage Value, with a minus sign
Populates the Source Code with the value set in the FA Jobs field in the Source Code Setup table
Dimension populates from the asset card
If a direct posting was specified in the Jobs dialog box, the proposed line is posted. If direct posting has not been entered, the line is suggested to the journal and the posting must be done by the user. Then the task moves on to processing the next contract.
Date Revision (POH) - Change of Depreciation Period
Fixes the Default Depr. Book) on the property card found for the contract.
In the contract, it looks at the value in the Contract Extension field, and if the value =:
No – compares the Contractual End Date on the contract with the Depreciation Ending Date in the default (accounting) book of depreciation on the searched Fixed Asset Card. In case of mismatch, it overwrites the date on the asset card with the date from the contract and validates the No. of Depreciation Months field
Yes – Compares the date Prep. Date Terminate after extension (Expec. Term. Date After Extension) on a contract with the Depreciation Ending Date in the Default Depr. Book) on the traced Fixed Asset Card. In case of mismatch, it overwrites the date on the asset card with the date from the contract and validates the No. of Depreciation Months field.
Then the task moves on to processing the next contract.
If direct posting was used by selecting from the Task dialog box, the task looks at the Default Depr. Book), after the check in the "All Acquisition in same Year = Yes" field is turned on. If the condition is met, the check is set to No and after posting, at the end of the job processing, it is set again to Yes. If he does not comply with the condition, he will do nothing
After all contracts have been processed, if direct posting was used in the Jobs dialog box and the job has turned off the flag in the "All Acquisition in same Year = Yes" field in the Default Depr. Book), then turn the flag back on.
Once all contracts have been processed, a notification will appear about the end of processing and the number of contracts processed.
The duration of job processing (API Batch Job Log) is recorded in the batch job log. This log is not user-accessible.
To run a task in the Task Scheduler
Task No. 4046912 It is possible to run it within the task scheduler by displaying the Send to scheduler option after the task starts, then opening a dialog box with scheduler settings options.
The job scheduler is modified by toggling the boolean Post to Yes.
After completing a job, it is recommended to always check:
Job Queue Entries to determine whether the job was terminated by an error message. After solving/removing the written error, the task can be started again using the Restart button
Fixed Asset Error Log (fixed asset error log), whether any contract processing has been terminated due to an error found. After the written error report is resolved/deleted, the task can be run repeatedly.