Skip to Content
author's profile photo Former Member
Former Member

Depreciation Run

Hi all,

for the client requirement we created new asset category and created some assets. the depreciation run in afab, before the month posted correctly. at that time this assets are not in the production. after adding this assets in the depreciation run the new assets depreciation posted, but the rest of the assets not posted. for the log of the depn run in AFBP the following error message has came.

Assets with errors in planned depreciation.

Message no AAPO504.


The assets below listed have incorrect planned depreciation values.

System Response

processing continues.


Check the depreciation for the listed assets and remove the cause of the error.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 04:59 AM


    This is the SAP notes for the error solution.


    Every depreciation run that is executed as an update run is logged using the schedule monitor (Transaction SCMO ). The status of the processing is also transferred to the schedule monitor in this case. If a depreciation run terminates with errors, this run is flagged as being incorrect (the status is red) in the schedule monitor. If the depreciation run ends successfully or ends with a warning message, the status is green or yellow in the schedule monitor.

    Depreciation runs should only be indicated as incorrect (red) in the schedule monitor if this causes the depreciation run to RESTART.

    <b>However, depreciation runs that do not lead to a RESTART are sometimes flagged as incorrect in the schedule monitor also. This is the case, for example, when assets are supposed to be posted and this shows errors in the depreciation calculation. In these cases, the system issues the error AAPO 505 (Assets with errors in calculation of depreciation to be posted) as a message and logs it in the schedule monitor but the depreciation does not terminate. This run is logged as "successful" in the log table TABA, but the run has the status "incorrect" in the schedule monitor.</b>

    This inconsistency of the run status causes problems when you use the delta extraction procedure of the depreciation with InfoSource 0FI_AA_12 in the Business Warehouse (BW). The delta extraction does not extract d epreciation runs in which there were error messages that only refer to depreciation problems for assets but that do not cause the update to terminate or cause errors in the update. The delta extraction of the posted depreciation is based on the logged depreciation runs that have ended successfully in the schedule monitor or that have ended with warning messages .

    Other terms

    SCMO, RAPOST2000, RABUCH00, AAPO503, AAPO504, AAPO505, AAPO506, AAPO507, AAPO508, AAPO509, AAPO 503, AAPO 504, AAPO 505, AAPO 506, AAPO 507, AAPO 508, AAPO 509

    Reason and Prerequisites

    The problem is due to a program error.


    When you implement the source code corrections, the errors from the depreciation calculation will be flagged as warnings and no longer as errors during a depreciation run. You can consider these messages as notes about errors in assets and not as the overall status of the depreciation run.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi all,

      kindly suggest me in this regard, the assets are not posted near 700 assets.

      for this may i choose repeat run? or any solution available? this happens in production.

      so needs urgent solutions please.......


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.