Message type: E = Error
Message class: EA - IDoc Basis Messages
Message number: 604
Message text: EDI: Receiver partner number in control record is default
An error was identified in the control record while adding an
<DS:GLOS.IDoc>IDoc</>. No value has been entered for the recipient
partner number, which is not permitted.
Recipient data:
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Please inform your system administrator.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message EA604, which states "EDI: Receiver partner number in control record is default," typically occurs in the context of Electronic Data Interchange (EDI) processes. This error indicates that the system is unable to find a valid receiver partner number in the control record of the EDI message, which is essential for routing the message to the correct partner.
Cause:
- Default Partner Number: The control record may contain a default partner number instead of a specific one. This can happen if the partner profile is not correctly set up or if the message is being processed without a valid partner configuration.
- Missing Partner Profile: The partner profile for the receiver may not be defined in the system, or it may not be correctly linked to the relevant message type.
- Incorrect Configuration: There may be issues with the configuration of the EDI settings, such as the logical system or the message type.
- Data Entry Errors: There could be errors in the data entry for the EDI message, leading to the system not being able to identify the correct partner.
Solution:
- Check Partner Profiles: Verify that the partner profile for the receiver is correctly set up in the system. You can do this by navigating to the transaction code
WE20
and checking the relevant partner profile.- Update Control Record: Ensure that the control record for the EDI message contains the correct receiver partner number. You may need to manually update this if it is set to a default value.
- Review Message Type Configuration: Check the configuration for the message type in transaction code
WE81
and ensure that it is correctly linked to the appropriate partner profiles.- Test EDI Configuration: Use transaction code
WE19
to simulate the EDI message and test the configuration. This can help identify if the issue is with the message format or the partner settings.- Consult Documentation: Review SAP documentation or notes related to EDI configuration for any specific requirements or updates that may be relevant to your version of SAP.
Related Information:
WE20
: Partner ProfilesWE81
: Message TypesWE19
: EDI Test ToolBy following these steps, you should be able to resolve the EA604 error and ensure that your EDI messages are processed correctly.
EA603 EDI: Receiver partner type in control record is default
What causes this issue? An error was identified in the control record while add...
EA602 EDI: Receiver port in control record is invalid
What causes this issue? An error was identified in the control record while add...
EA605 EDI: Sender port in control record is invalid
What causes this issue? An error was identified in the control record while add...
EA606 EDI: Sender port in control record is default
What causes this issue? An error was identified in the control record while add...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.