Handling of Depreciation Posting Errors

Various errors can occur during depreciation posting. The causes of these errors and methods for correcting them are outlined below.

Checks During the Posting Run

The system runs various checks during the posting run:

First the system checks if it is possible to execute the run using the selection conditions entered. For example, for a regular posting run, it checks if the posting period follows the last posting period in chronological order. If an error occurs in this initial phase, the run terminates and an error message is issued. Analyze the error and start the posting run again.

Errors can occur during depreciation calculation when the system calculates the depreciation amounts that are to be posted. If an error of this type is discovered, this does not lead to a termination of the posting program. The assets affected are excluded from further processing, and the error messages that occur are gathered in the error log. If no other errors occur, then a restart is not necessary. However, the overall status of the run (in the Schedule Manager) is incorrect. Check the values of the assets that have errors in the Asset Explorer, and make the necessary corrections. You can then post the depreciation for these assets to Financial Accounting, either through a repeat run or in the next planned depreciation posting run.

Checks during creation of line items. Errors that occur during creation of line items affect either individual assets or groups of assets. An example is missing accounts in the account assignment. In this case, the system cannot process the assets further in the given depreciation area. These assets are shown in the log as having errors. It is not possible for the accounting document for them to be created and updated. However, the system continues to process the other assets. After you correct the error(s), you have to restart.

Checks during the update of the accounting document. An example here is a missing or invalid cost center to which account assignment is supposed to be made. In this case, the system cannot update the document, but continues with processing of the subsequent documents. The log shows all assets, which are assigned to a document with errors, as having errors. After you correct the error(s), such as by changing the cost center in the asset master record, you have to restart.

Error Log

You analyze the error log differently depending on whether the posting run was created in dialog mode (only possible for a test run) or if it was started in the background.

Dialog: Choose Error List on the output list screen. An overview appears containing all the errors that occurred. Sorting of the error list corresponds to the sequence of the checks as explained above. There is a title line preceding each error message that explains the origin of the error (for example, error during check of document 3000001). Double click on the error line to jump to the long text of the error message. This contains additional information on the cause of the error, or provides hints for correcting the error. Another option is to double click on the icon (red traffic light) in the Status column in the output list. This takes you directly to the error message assigned to the line.

Background processing: When background processing is used, the errors are stored by the Schedule Manager, rather than in the output list (spool list). To analyze the errors, you can

Call the log of the depreciation posting run and jump from there to the log of the Schedule Manager

Call the log of the depreciation posting run with the SchedMan Monitor Only option, to go directly to the monitor of the Schedule Manager

Start the Schedule Manager separately and select the posting run there in the monitor

Here you can also double click on the error message to see the long text.