AA686 - OBSOLETE - Repeat run only possible in & &

Start a new search

SAP Error Message - Details

  • Message type: E = Error

  • Message class: AA - Messages for Asset Accounting

  • Message number: 686

  • Message text: OBSOLETE - Repeat run only possible in & &

  • Show details Hide details
  • <ZH>***Obsolete***</>
    ------------------

    What causes this issue?

    You want to repeat a depreciation posting run in a period in which no
    posting run was performed.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?

    You must specify the period in which the last posting run was performed
    for repeat runs.

    Error message extract from SAP system. Copyright SAP SE.


AnswerBot

  • What is the cause and solution for SAP error message AA686 - OBSOLETE - Repeat run only possible in & & ?

    The SAP error message AA686 "OBSOLETE - Repeat run only possible in & &" typically occurs in the context of Asset Accounting (FI-AA) when you are trying to execute a repeat run for an asset transaction that is no longer valid or has been marked as obsolete. This can happen for various reasons, such as changes in the asset master data, the asset transaction being processed in a different period, or the transaction being flagged for deletion.

    Cause:

    1. Obsolete Transaction: The asset transaction you are trying to repeat has been marked as obsolete, meaning it cannot be processed again.
    2. Period Closing: The period in which the original transaction was posted may have been closed, preventing any modifications or repeat runs.
    3. Changes in Asset Master Data: If there have been changes to the asset master data after the original transaction was posted, it may affect the ability to perform a repeat run.
    4. Configuration Issues: There may be configuration settings in the Asset Accounting module that restrict repeat runs for certain types of transactions.

    Solution:

    1. Check Transaction Validity: Verify if the transaction you are trying to repeat is indeed marked as obsolete. You can do this by checking the asset transaction history.
    2. Review Period Status: Ensure that the posting period for the original transaction is still open. If it is closed, you may need to reopen the period or use a different approach to correct the transaction.
    3. Adjust Asset Master Data: If there have been changes to the asset master data, ensure that these changes are consistent with the transaction you are trying to repeat.
    4. Consult Configuration: Review the configuration settings in the Asset Accounting module to see if there are any restrictions on repeat runs for the specific transaction type.
    5. Manual Correction: If a repeat run is not possible, consider manually correcting the transaction or posting a new transaction that reflects the necessary changes.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as AS02 (Change Asset), AS03 (Display Asset), and AW01N (Asset Explorer) to investigate asset transactions and their statuses.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional insights or solutions.
    • Documentation: Review SAP documentation on Asset Accounting for best practices and guidelines on handling asset transactions and repeat runs.

    If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant specializing in Asset Accounting for further assistance.

  • AnswerBot is an artificial intelligence solution provided by tomco.ai.
    Disclaimer

Sign up and try ERPlingo for free.

Sign up takes 1 minute. 7-day free trial.




Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.