How To Fix E0116 - EDI: Inconsistency in fields of the control record

SAP Error Message - Details

• Message type: E = Error

• Message class: E0 - SAP EDI messages

• Message number: 116

• Message text: EDI: Inconsistency in fields of the control record

What causes this issue?

The values for the Intermediate Document type, basic IDoc type, and
extension type have not been stored as a combination in table EDIDO.
The following values are entered in the control record:
IDoc type: &v1&
Basic IDoc type: &v2&
Extension type: &v3&

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?

Please contact your system administration.
The data cannot be stored in an Intermediate Document until this
inconsistency has been removed.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message E0116 - EDI: Inconsistency in fields of the control record ?

  The SAP error message E0116, which states "EDI: Inconsistency in fields of the control record," typically occurs in the context of Electronic Data Interchange (EDI) processes. This error indicates that there is a mismatch or inconsistency in the control record fields of the EDI message being processed. Here are some common causes, solutions, and related information for this error:
  Causes:
  
  Incorrect Control Record Data: The control record may contain incorrect or incomplete data, such as missing mandatory fields or incorrect values.
  Field Length Issues: The data in the control record may exceed the defined length for certain fields, leading to inconsistencies.
  Configuration Issues: There may be configuration issues in the EDI settings, such as incorrect mapping or settings in the partner profiles.
  Version Mismatch: The EDI message version being used may not be compatible with the expected version in the SAP system.
  Data Format Issues: The format of the data being sent may not conform to the expected format, leading to parsing errors.
  
  Solutions:
  
  Check Control Record: Review the control record for any missing or incorrect data. Ensure that all mandatory fields are filled out correctly.
  Validate Field Lengths: Ensure that the data in the control record does not exceed the defined lengths for each field.
  Review EDI Configuration: Check the EDI configuration settings in the partner profiles (transaction WE20) and ensure that they are set up correctly.
  Update EDI Mapping: If there are changes in the EDI message structure, update the mapping accordingly in transaction WE60 or WE30.
  Test with Sample Data: Use sample data to test the EDI process and identify if the issue persists with specific data sets.
  Consult SAP Notes: Look for relevant SAP Notes that may address known issues related to this error message.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE02 (EDI Audit Log), WE05 (EDI Monitoring), and WE20 (Partner Profiles) for troubleshooting.
  SAP Documentation: Refer to SAP Help documentation for EDI configuration and troubleshooting guidelines.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to identify and resolve the inconsistency in the control record that is causing the E0116 error in your SAP EDI processes.