Map Out Failed Errors

Sample Error Message: No service configuration found for file recipient. Recipient [Company ID] is not a subscriber to the service.

Root Cause: The inbound Ship Notice cannot be associated to a company in the downstream supply chain because the ID used to identify that company is not referenced on the Partners screen. This failure is due to a missing or incorrect ServiceLink that does not reference the internal ID.

Solution: Check the ID sent in the inbound transaction from your company against the information on the Partners screen to ensure that the value is present and is set correctly. Update the company Partner Master Data to ensure that the ID is associated to the correct downstream partner and create a new ServiceLink, which will then populate the Partners screen, allowing the document to process and associate with the correct company for future messages.

Responsible Party: Customer

This error can occur for multiple processing statuses.

Sample Error Message: No item detail entry found matching aggregation item line number -- and lot number [Lot Number] No item detail entry found matching aggregation item line number -- and lot number [Lot Number]

Root Cause: Either the customer does not have the NDC in their master data and/or the partner is not including the necessary NDC fields and values in the ASN.

Solution: Check the respective ASN as well as the Product Master Data the for the NDC fields. Confirm the NDC value with Sender and Receiver and get confirmation to add it to the respective fields, and then resend the message.

Responsible Party: Sender

This error can occur for multiple processing statuses.

Sample Error Message: ERRORSID: User_Error_MessageSeverity: ErrorCategory: Custom_ErrorDescription

Root Cause: This is a generic catch-all error that can occur in several different scenarios.

Solution: Identify the specific error message for your scenario by checking the timestamp for the transaction in the account. Depending on the specific error message, consult the IE Common Errors to proceed further. If unable to effectively troubleshoot the error, contact TraceLink Support.

Responsible Party: Sender

This error can occur for multiple processing statuses.

Sample Error Message: ERRORSID: User_Error_MessageSeverity: ErrorCategory: Custom_ErrorDescription: User Command Error: EDI sender ID in source PartnerNumber is required

Root Cause: The delivery is outbound and the EDI Settings CSV has not been completed for the receiving party's account, resulting in the ISA06 not being populated.

Solution: First, check the delivery rules if the ASN is not meant to be delivered externally, or check the EDI Settings on the receiving party's account. Then, either turn off delivery rules if the ASN is not meant to be delivered externally, or complete the EDI Settings on receiving party's account.

Responsible Party: Sender