How To Fix EDATEX313 - No external point of delivery description available

SAP Error Message - Details

• Message type: E = Error

• Message class: EDATEX - Messages for Data Exchange Processes

• Message number: 313

• Message text: No external point of delivery description available

What causes this issue?

You want to execute a data exchange process. Processing cannot be
completed because no external point of delivery description is ava
ilable.

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?

Check whether an external point of delivery description has been
specified for the point of delivery.

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 EDATEX313 - No external point of delivery description available ?

  The SAP error message EDATEX313 ("No external point of delivery description available") typically occurs in the context of Electronic Data Interchange (EDI) processes, particularly when dealing with delivery documents. This error indicates that the system is unable to find a description for the external point of delivery that is required for processing the EDI message.
  Cause:
  
  Missing Data: The external point of delivery (often a location or address) may not be defined in the system. This could be due to missing master data or configuration settings.
  Incorrect Configuration: The configuration for EDI or the specific message type may not be set up correctly, leading to the system not being able to retrieve the necessary descriptions.
  Data Mapping Issues: There may be issues with how data is mapped between the SAP system and the external system, leading to missing or incorrect references.
  
  Solution:
  
  Check Master Data: Ensure that the external point of delivery is correctly defined in the system. This includes checking the relevant master data records (e.g., customer master, vendor master, or material master) to ensure that all necessary fields are populated.
  Review EDI Configuration: Verify the EDI configuration settings in transaction codes like WE20 (Partner Profiles) and WE21 (Port Definition). Ensure that the message type and associated parameters are correctly set up.
  Maintain External Point of Delivery Descriptions: If the external point of delivery is a custom or specific entry, ensure that it has been properly maintained in the relevant tables (e.g., T005 for countries, T001 for company codes).
  Check Data Mapping: If you are using middleware (like SAP PI/PO or other EDI tools), check the mapping configurations to ensure that the external point of delivery is being correctly translated from the incoming EDI message to the SAP format.
  Consult Documentation: Review SAP documentation or notes related to the specific EDI message type you are working with to see if there are any known issues or additional configuration steps required.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE02 (EDI Audit Log), WE19 (Test EDI), and WE20 (Partner Profiles) for troubleshooting EDI issues.
  SAP Notes: Search for SAP Notes related to EDATEX313 or the specific EDI message type you are working with for any patches or updates that may address the issue.
  Support: If the issue persists after checking the above areas, 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 cause of the EDATEX313 error in your SAP system.