AA603 - SYST: Period version & not allowed in company code &

Start a new search

SAP Error Message - Details

  • Message type: E = Error

  • Message class: AA - Messages for Asset Accounting

  • Message number: 603

  • Message text: SYST: Period version & not allowed in company code &

  • Show details Hide details
  • What causes this issue?

    Processing terminated, since a period version &V1&, which is not
    allowed, is used in company code &V2&.

    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?

    Create period version &V1& or correct company code &V2&.

    Error message extract from SAP system. Copyright SAP SE.


AnswerBot

  • What is the cause and solution for SAP error message AA603 - SYST: Period version & not allowed in company code & ?

    The SAP error message AA603 indicates that there is an issue with the period version being used in the context of asset accounting (AA) for a specific company code. This error typically arises when the system is trying to post an asset transaction, but the period version specified is not allowed for the company code in question.

    Cause:

    1. Incorrect Period Version: The period version specified in the transaction does not match the settings defined for the company code in the asset accounting configuration.
    2. Configuration Issues: The period version may not be properly configured in the asset accounting settings for the company code.
    3. Posting Periods: The posting period may be closed or not open for the specified period version, preventing any transactions from being processed.

    Solution:

    1. Check Configuration:

      • Go to the configuration settings for Asset Accounting (Transaction code: SPRO).
      • Navigate to Financial Accounting (New) > Asset Accounting > Integration > Define Period Versions.
      • Ensure that the period version you are trying to use is correctly defined and assigned to the relevant company code.
    2. Review Posting Periods:

      • Check the posting periods for the company code (Transaction code: OB52).
      • Ensure that the posting period for the transaction date is open for the specified period version.
    3. Adjust Transaction:

      • If the period version is not appropriate for the transaction you are trying to post, consider changing the period version in the transaction or using a different transaction that aligns with the allowed period version.
    4. Consult Documentation:

      • Review SAP documentation or help resources for more details on period versions and their configurations.
    5. Contact Support:

      • If the issue persists after checking the configuration and posting periods, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.

    Related Information:

    • Transaction Codes:
      • SPRO: Customizing settings
      • OB52: Maintain posting periods
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to error AA603.
    • User Roles: Ensure that the user has the necessary authorizations to perform transactions in asset accounting.

    By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.

  • 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.