Map In Failed Errors

Sample Error Message: Delivery document [ID]: Skipping calculation of sender and receiver. alt id is not defined, partner is not definedDelivery document [ID]: Cannot calculate service subscriber to receive the ASN for deliveryTransactionType of sale because the ToBusinessPartyInfo COMPANYID [Company Id] does not correspond to a known Service Partner

Root Cause: The triggered ASN from an inbound PickShip cannot be associated to a downstream company as the ID used to identify that company is not referenced on the Partners screen. This is due to a missing or incorrect link which does not reference the internal ID.

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

Responsible Party: Customer

Sample Error Message: FATALSID: Transform_Input_FFD_ErrorSeverity: FatalCategory: Configuration_ErrorDescription: Unable to read input data for business object 856 due to a FFD Error.Scope: OtherDetail[Business Object Name]: 856Detail[FFD Error]: Data did not match flat file definition. Extra data found after position 107 in the input stream and parsing fails at the node /GS/GS08[1].Position at the input stream: 107Node name: /GS/GS08[1]

Root Cause: The inbound file to TraceLink cannot be processed because the file type cannot be determined (e.g. EDI, EPCIS, XML).

Solution: Confirm that the file being sent to TraceLink conforms to the standards of the chosen file type and that no extra characters appear in the header. Correct the source that is generating the file and resend the message.

Responsible Party: Sender

Sample Error Message: Report could not be created Error sending the message to the RU Connector. TraceLink might not contain credentials for the RU - Account Number.

Root Cause: Connection credentials are missing from the configuration.

Solution: Check the published Russia Compliance configuration and MDLP settings. If credentials are missing, update the relevant MDLP Credentials settings in the Russia Compliance service and add credentials for the Russia account number.

Responsible Party: Customer

Sample Error Message: Errors found in the request, EUGR wont be sent out to EMVSErrors found in the request, EUGR wont be sent out to EMVSEU Product Pack State Update Report can not be generated because the Serial Numbers are not in a destroyed or decommissioned state.

Root Cause: The government report could not be generated.

Solution: Check any prerequisite prior reports and the relevant serial number statuses, and regenerate the report.

Responsible Party: Customer

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: At least one of Commissioning or Aggregation or Transformation events is required

Root Cause: The commissioning event fields are missing in the DA file.

Solution: Check the Canonical file for the failed DA transaction and look for the <ns2:CommissionEventDetail> tag. The values will be missing in the file, which resulted in the error. Take the input file and add the missing information to the CommissionEvent fields, then Import in Info Exchange to process.

Responsible Party: Sender

Sample Error Message: ERRORSID: User_Error_MessageSeverity: ErrorCategory: Custom_ErrorDescription: User Command Error: Senders ship-from business street address is required in source STREET1.Scope: OutputDetail[Text]: Senders ship-from business street address is required in source STREET1.Detail[Output Path]: CanonicalPTSalesShipmentType | MessageBody | ShipmentTransaction | BusinessEntityDetails | SenderInfo | choice_2 | ShipFromLocationInfo | LocationInfo | Street1InputAddressInterfacePath: /ZDELVRY073P

Root Cause: No street address information has been entered in the STREET1 field of the ship from business section.

Solution: Check the inbound transaction for empty street tags in the ship from business section. Update the street information in the transaction and resend the file.

Responsible Party: Sender

Sample Error Message: ERRORSID: User_Error_MessageSeverity: ErrorCategory: Custom_ErrorDescription: User Command Error: Sending business party name in source N102 is required

Root Cause: The N102 value is missing or was sent incorrectly in the inbound file.

Solution: Check the inbound file and see what value was sent in the N102 field. If the N102 value is missing, request that the sender add the missing field. If the N102 value was sent incorrectly, then request that the sender correct it and resend the file.

Responsible Party: Sender

Sample Error Message: EU Commission reports not found for the specified lot [Lot Number] and packaging code [Packaging Code]

Root Cause: A given serial number status is in the process of being updated (e.g. goods are being exported out of the EU and the system notifies EMVO that they are no longer available in the EU), however, the commissioning report for the serial number is not yet available.

Solution: Before resending a report, verify the lot details and commissioning data. This error can occur because the serial number update or shipment occurs before the serial number commissioning is reported. Check, in order, that the following information is correct and regenerate the report if necessary:

1. commissioning event
2. commissioning report
3. update/shipment event
4. update report

To regenerate any EU FMD report, use Serialized Operations Manager - Workflow Management.

Responsible Party: Customer

Sample Error Message: ERRORSID: Empty_Tag_Creation_For_Output_FieldSeverity: ErrorCategory: Output_Data_ErrorDescription: An empty tag was created for a target field, but an empty tag is not valid data for the field.Scope: OutputDetail[Output Path]: CanonicalIEProcessingAckMessage | MessageBody | ProcessingResults | ProcessedNoWarning | ProcessedItem[*] | choice_1 | MfrSalesShipmentTHSpec | ShippingReferenceDocuments[*] | BusinessDocument | @typeDetail[Minimum Target Iteration Count]: 1Detail[Actual Iterati

Root Cause: The map version is not correct or the Input file is missing the required fields.

Solution: Check the canonical file and see which tag the error points to, then check if the inbound file is missing that particular tag. If the tag is missing, correct the inbound file. If the tag is not missing, then contact TraceLink Support.

Responsible Party: Sender

Sample Error Message: GLN for message recipient not found in Partner Master Data.No manufacturer ID exists for the given serial numbers.

Root Cause: There is either missing or mismatched GLN information stored in the Partner Master Data section.

Solution: Check Partner Master Data for missing or mismatched GLN information and either add or correct the GLN value, then resend the message.

Responsible Party: Customer

Sample Error Message: ERRORSID: Input_Occurs_Less_Than_Min_OccursSeverity: ErrorCategory: Iteration_ErrorDescription: Data Error: ParentSerialNumber occurs fewer times than its minimum number of occurrences.Scope: InputDetail[Input Path]: CanonicalIEProcessingAckMessage | MessageBody | ProcessingResults | FailedItem | ProcessedItem[0] | choice_1 | SNX_DispositionAssignedSpec | Aggregation | ParentSerialNumberDetail[Source Minimum Iteration]: 1Detail[Source Actual Iteration]: 0Detail[Error Name]: Input_Occ

Root Cause: There is a missing required field in the outbound message.

Solution: Check the error message details to determine the missing field. If needed, check the relevant API guidelines for the given message. Add the missing field to the inbound message and resend it.

Responsible Party: Sender

This error can occur for multiple processing statuses.