EA599 - When saving, process code '&' is also deleted in the ALE table

SAP Error Message - Details

• Message type: E = Error

• Message class: EA - IDoc Basis Messages

• Message number: 599

• Message text: When saving, process code '&' is also deleted in the ALE table

What causes this issue?

In the case of process codes for inbound processing, which are created
for
processing via function modules
the ID - the processing function module here - is not maintained from
this screen, but in the ALE table 'Function modules for ALE-EDI inbound
processing'.
In order to delete the process codes completely, it must also be
deleted in the ALE table, if it exists there.

System Response

When you save, the entry in table TBD52 is deleted.

How to fix this error?

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

AnswerBot

• What is the cause and solution for SAP error message EA599 - When saving, process code '&' is also deleted in the ALE table ?

  The SAP error message EA599 typically indicates an issue related to the Application Link Enabling (ALE) configuration, specifically when saving changes that affect process codes in the ALE table. This error can occur in various scenarios, such as when you are trying to save a configuration or a change in the ALE settings.
  Cause:
  The error message EA599 is triggered when the system detects that a process code (denoted by '&') is being deleted or is no longer valid in the context of the ALE configuration. This can happen due to:
  
  Inconsistent Configuration: Changes made to the ALE configuration that lead to inconsistencies, such as removing a process code that is still in use.
  Missing Dependencies: The process code may have dependencies that are not being met, leading to its deletion.
  Transport Issues: If the configuration was transported from one system to another, it might not have been properly adjusted for the target system.
  
  Solution:
  To resolve the EA599 error, you can follow these steps:
  
  
  Check Configuration: Review the ALE configuration settings to ensure that all process codes are correctly defined and that there are no inconsistencies. You can do this by navigating to the relevant transaction codes (e.g., WE20 for partner profiles, WE21 for port definitions).
  
  
  Validate Process Codes: Ensure that the process code you are trying to save is valid and not being used elsewhere. If it is being used, you may need to update or remove those dependencies before proceeding.
  
  
  Review Change Logs: If the error occurred after a recent change, check the change logs to identify what modifications were made and whether they could have led to the deletion of the process code.
  
  
  Transport Requests: If the issue arose after a transport, ensure that all related objects were included in the transport request and that they were imported correctly into the target system.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to ALE and process codes for any specific guidance or known issues.
  
  
  SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They may provide specific notes or patches that address the error.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE20 (Partner Profiles), WE21 (Ports), and WE30 (IDoc Types) for managing ALE configurations.
  SAP Notes: Search for SAP Notes related to EA599 for any specific fixes or recommendations provided by SAP.
  ALE Overview: Understanding the basics of ALE, including its architecture and how process codes function within it, can help in troubleshooting issues effectively.
  
  By following these steps, you should be able to identify the root cause of the EA599 error and implement a solution to resolve it.