How To Fix 5B036 - IDOC2 or IDOC3 is filled, but IDOC1 is not

SAP Error Message - Details

• Message type: E = Error

• Message class: 5B -

• Message number: 036

• Message text: IDOC2 or IDOC3 is filled, but IDOC1 is not

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 5B036 - IDOC2 or IDOC3 is filled, but IDOC1 is not ?

  The SAP error message 5B036 indicates that there is an issue with the IDoc structure, specifically that the IDOC2 or IDOC3 segments are filled, but the IDOC1 segment is not. This typically occurs in the context of IDoc processing, where the IDoc structure is expected to follow a certain hierarchy and completeness.
  Cause:
  
  
  Incomplete IDoc Structure: The IDOC1 segment is the control record of the IDoc, which contains essential information about the IDoc itself, such as the message type, sender, receiver, and other metadata. If IDOC2 or IDOC3 segments are populated without a corresponding IDOC1 segment, it indicates that the IDoc is not properly initialized or has been corrupted.
  
  
  Data Transfer Issues: There may have been an issue during the data transfer process, leading to the IDoc being generated without the necessary control record.
  
  
  Configuration Issues: Incorrect configuration in the IDoc processing settings or the message type settings can lead to this error.
  
  
  Programmatic Errors: If the IDoc is being generated or processed through custom programs or interfaces, there may be a bug or oversight in the code that fails to populate the IDOC1 segment.
  
  
  Solution:
  
  
  Check IDoc Generation: Ensure that the IDoc is being generated correctly. Review the process that creates the IDoc to ensure that the IDOC1 segment is populated before IDOC2 or IDOC3 segments.
  
  
  Review Configuration: Check the configuration settings for the IDoc type and message type in transaction WE20 (Partner Profiles) and WE30 (IDoc Types). Ensure that all necessary settings are correctly configured.
  
  
  Reprocess the IDoc: If the IDoc is found to be incomplete, you may need to delete the erroneous IDoc and regenerate it. Use transaction WE19 (Test Tool) to create a new IDoc for testing purposes.
  
  
  Debugging: If the issue persists, consider debugging the program or process that generates the IDoc. Look for any logic that might skip the population of the IDOC1 segment.
  
  
  Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as there may be known issues that have been resolved in newer versions.
  
  
  Related Information:
  
  
  IDoc Structure: Understanding the structure of IDocs is crucial. IDocs consist of a control record (IDOC1), followed by data records (IDOC2, IDOC3, etc.). Each segment has a specific purpose and must be filled correctly for successful processing.
  
  
  Transaction Codes:
  
  WE02: Display IDocs
  WE19: Test IDoc
  WE20: Partner Profiles
  WE30: IDoc Types
  
  
  
  SAP Notes: Check SAP Notes for any known issues related to this error message. You can search for the error message number or related keywords in the SAP Support Portal.
  
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.