How To Fix E0036 - EDI: Error with database insert/update in table EDID4

SAP Error Message - Details

• Message type: E = Error

• Message class: E0 - SAP EDI messages

• Message number: 036

• Message text: EDI: Error with database insert/update in table EDID4

What causes this issue?

When creating an IDoc an error was reported by the database when
inserting or updating data records in table EDID4 for IDoc number &v1&.

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?

Contact your systema dministration.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message E0036 - EDI: Error with database insert/update in table EDID4 ?

  The SAP error message E0036, which indicates an "EDI: Error with database insert/update in table EDID4," typically arises during the processing of Electronic Data Interchange (EDI) messages. This error suggests that there was a problem when the system attempted to insert or update data in the EDID4 table, which is used to store EDI data.
  Causes:
  
  Database Locking Issues: The table EDID4 might be locked by another process, preventing the current transaction from completing.
  Data Integrity Violations: The data being inserted or updated may violate constraints (e.g., primary key, foreign key, or unique constraints) defined on the EDID4 table.
  Insufficient Authorizations: The user or process attempting the operation may not have the necessary authorizations to perform the insert/update.
  Database Issues: There could be underlying database issues, such as corruption or connectivity problems.
  Configuration Errors: Incorrect configuration settings in the EDI subsystem or related modules may lead to this error.
  
  Solutions:
  
  Check Database Locks: Use transaction codes like SM12 to check for locks on the EDID4 table. If locks are found, determine the cause and resolve them.
  Review Data: Ensure that the data being processed does not violate any constraints. Validate the incoming EDI message for correctness.
  Authorization Check: Verify that the user or process has the necessary authorizations to perform the operation. You can check this using transaction SU53 or SUIM.
  Database Health Check: Perform a health check on the database to ensure there are no issues. This may involve checking for corruption or running database consistency checks.
  Review EDI Configuration: Check the configuration settings for the EDI subsystem in transaction WE20 (partner profiles) and WE21 (port definitions) to ensure they are set up correctly.
  Error Logs: Review the application logs (transaction SLG1) for more detailed error messages that can provide additional context on the failure.
  
  Related Information:
  
  EDID4 Table: This table is part of the EDI subsystem in SAP and is used to store inbound EDI messages. Understanding its structure and constraints can help in troubleshooting.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE02 (to view EDI messages), WE19 (to test EDI messages), and WE60 (to view EDI documentation).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support or consult with a technical expert who specializes in EDI and SAP database issues.