How To Fix 88794 - Document type &1 is consecutive document type for &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 88 - REA Processing

• Message number: 794

• Message text: Document type &1 is consecutive document type for &2

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 88794 - Document type &1 is consecutive document type for &2 ?

  The SAP error message 88794 indicates that there is an issue with the document type configuration in the system. Specifically, it states that the document type you are trying to use is a consecutive document type for another document type, which means that it cannot be used in the current context.
  Cause:
  This error typically occurs in the following scenarios:
  
  Document Type Configuration: The document type you are trying to use is set up as a consecutive document type for another document type. For example, if you are trying to create a document of type "Invoice" but the system expects a "Purchase Order" to be created first, you will encounter this error.
  Incorrect Document Flow: The sequence of document creation is not being followed as per the configuration in the system. For instance, if a document type is configured to be a follow-up document, it cannot be created independently without its predecessor.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Document Type Configuration:
  
  Go to the configuration settings for document types in SAP (Transaction Code: OBA7 for Financial Accounting or OMR6 for Logistics).
  Verify the settings for the document type you are trying to use and see if it is indeed set as a consecutive document type for another document type.
  
  
  
  Create the Preceding Document:
  
  If the document type you are trying to use is a follow-up document, ensure that the preceding document (the one it is dependent on) has been created first. For example, if you are trying to create an invoice, ensure that the corresponding purchase order exists.
  
  
  
  Adjust Document Flow:
  
  If the document flow does not meet your business requirements, you may need to adjust the configuration. This may involve changing the settings for the document types in question or modifying the workflow to allow for the creation of the document type you need.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP administrator or functional consultant to understand the specific configuration and dependencies related to the document types in your system.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBA7 (for document type configuration) and OMR6 (for logistics document types).
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  User Authorization: Ensure that you have the necessary authorizations to create or modify the document types in question.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.