How To Fix /ACCGO/OE_MSG022 - Configuration changed; sequence number not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/OE_MSG -

• Message number: 022

• Message text: Configuration changed; sequence number not found

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /ACCGO/OE_MSG022 - Configuration changed; sequence number not found ?

  The SAP error message /ACCGO/OE_MSG022 Configuration changed; sequence number not found typically occurs in the context of the SAP General Ledger (G/L) accounting module, particularly when dealing with the configuration of document types, number ranges, or other related settings. This error indicates that there has been a change in the configuration that affects the sequence number for document processing, and the system is unable to find the expected sequence number.
  Causes:
  
  
  Configuration Changes: Changes made to the document type configuration, number range intervals, or other related settings can lead to this error. If a sequence number is expected but has been altered or deleted, the system will not be able to process the document.
  
  
  Missing Number Ranges: If the number range for a specific document type has not been defined or has been deleted, the system will not find the required sequence number.
  
  
  Transport Issues: If configuration changes were transported from one system to another (e.g., from development to production) and the transport did not include all necessary objects, this could lead to inconsistencies.
  
  
  Custom Development: If there are custom developments or enhancements that interact with the document processing logic, they may inadvertently cause this error if not properly aligned with the configuration.
  
  
  Solutions:
  
  
  Check Configuration: Review the configuration settings for the document type in question. Ensure that the number range is correctly defined and that the sequence numbers are available.
  
  Navigate to SPRO ? Financial Accounting ? General Ledger ? Document Types ? Define Document Types.
  Check the number range assignment for the document type.
  
  
  
  Define Number Ranges: If the number range is missing, you may need to define it. Go to the number range configuration and ensure that the required number ranges are set up correctly.
  
  Navigate to SPRO ? Financial Accounting ? General Ledger ? Document Types ? Define Number Ranges for Document Types.
  
  
  
  Transport Check: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included in the transport request. If something is missing, you may need to re-transport the configuration.
  
  
  Review Custom Code: If there are any custom developments that interact with the document processing, review the code to ensure it is compatible with the current configuration.
  
  
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  Consult SAP Notes: Search for relevant SAP Notes that may address this specific error message. SAP frequently updates its knowledge base with solutions for known issues.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (for document types) and OBA7 (for number ranges).
  Documentation: Review SAP documentation related to G/L accounting configuration for best practices and guidelines.
  Support: If the issue persists after checking the above, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.