Processing 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] No item detail entry found matching aggregation item line number -- and lot number [Lot Number] THPICKEXCEEDQTYERROR: No Transaction Histories found matching NDC NDC542 [NDC] and Lot [Lot Number], at Location --.

Root Cause: When processing either a PickShip or ASN, the request cannot be completed because there is missing data in the system regarding the specific NDC listed. The most common issues are a missing Strength value (not required in Product Master Data but required on the ASN), missing or incomplete TH in the ASN (NDC line item values or line item missing completely), or an NDC value is missing from Product Master Data completely. PickShip requires that controlled substances supply a combination of NDC, Lot, and Expiration.

Solution: First, confirm that the Product Master Data for the specified NDC is present and complete. Then, add any missing Product Master Data information if necessary or verify that the line item requirements are present.

Responsible Party: Customer

Sample Error Message: Delivery Number [Delivery Number] already exists for a previous inbound shipment.

Root Cause: The delivery number on the inbound shipment already exists for a previous shipment and cannot be reused.

Solution: Check and confirm that the delivery number on the inbound shipment is unique and has not been sent previously. If it has been sent previously, a new unique value is required. Update the delivery number on the shipment ASN and resend the message.

Responsible Party: Sender

Sample Error Message: Could not determine owner of business process from alternate id PT.[ID]

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

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

Responsible Party: Customer

Sample Error Message: Error processing Transaction History data for Delivery [DELIVERYNUMBER], NDC542 [NDC], Quantity X. No NDC attributes were provided and NDC not found in Product Master Data.

Root Cause: When processing either a PickShip or ASN, the request cannot be completed because there is missing data in the system regarding the specific NDC listed. The most common issues are a missing Strength value (not required in Product Master Data but required on the ASN), missing or incomplete TH in the ASN (NDC line item values or line item missing completely), or an NDC value missing from Product Master Data completely. PickShip requires that controlled substances supply a combination of NDC, Lot, and Expiration.

Solution: First, confirm that the Product Master Data for the specified NDC is present and complete. Then, add any missing Product Master Data information if necessary or verify that the line item requirements are present.

Responsible Party: Customer

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: Serial Number [Serial Number] cannot be commissioned because it is not associated with Internal Material Number [Internal Material Number] in [Company Name]s Product Master Data.

Root Cause: The Internal Material Code value for a given product must be in sync between the CMO and MAH's records. If there is a mismatch, the transaction (commissioning) will fail.

Solution: Confirm that the Product Master Data information is correct and is the same for both the CMO and MAH. If they do not match, correct the data to align both values for the given product and then resend the adjusted commissioning file.

Responsible Party: Sender

Sample Error Message: Cannot pick against Delivery Number

Root Cause: The same delivery number is used in the receipt and shipment message.

Solution: Confirm that the delivery number does not already exist in the system. Send a unique delivery number in the receipt message or update the inbound map on 3PL account.

Responsible Party: Sender

Sample Error Message: No picked Transaction Histories found matching NDC [NDC] and Lot [LOT] at COMPANYSITEID [COMPANYSITEID ]No picked Transaction Histories found matching NDC [NDC] and Lot [Lot]at COMPANYSITEID [Company Site ID]No picked Transaction Histories found matching NDC [NDC] and Lot []LOT at COMPANYSITEID [Company Site ID]

Root Cause: No transaction histories of specified NDC/Lot at Location are in a Picked status - and therefore cannot be Unpicked.

Solution: Remove the Unpick action for the specified NDC/Lot and reprocess the Unpick file if there are additional items to be Unpicked. Once all items have been fully unpicked, resend the original Pick/Ship message as needed.

Responsible Party: Sender

Sample Error Message: NDC [NDC ] could not be found in product master data or redbook data.

Root Cause: The NDC is not found in Product Master Data or in the supplementary Redbook data look-up, so the Item information cannot be retrieved to populate the transaction history.

Solution: Identify the product that is failing and check its Master Data information. The NDC in question may need to be added to Product Master Data. Contact TraceLink Support to then add the NDC to the Redbook supplemental database for Dispenser look-up. Once added, resend the message.

Responsible Party: Sender

Sample Error Message: Validation exception: Serial Number Manager does not have sufficient serial numbers to satisfy the serial number request for [Product Code].

Root Cause: The number of serial numbers in the pool for the requested product exceeds the current amount of existing serial numbers.

Solution: Check the serial number pool, minimum threshold, and amount of already requested but not commissioned serial numbers for the CMO. If needed, the MAH refills the serial number pool and then advises the CMO to start a new request (old open requests will not be replenished).

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.

Sample Error Message: GTIN-14 Identifier [GTIN-14] is not in the permitted serial number request list.

Root Cause: The GTIN is not assigned to a Serial Number Exchange profile.

Solution: In the Serial Number Exchange module, navigate to the Manage Profiles screen to select the profile in question and search for the requested GTIN. Add the product to Product Master Data, create a serial number template, and assign the GTIN to the Partner's Serial Number Exchange profile.

Responsible Party: Customer

Sample Error Message: Validation exception: Quantity requested

Root Cause: The quantity of serial numbers requested is greater than the maximum request quantity defined by the MAH.

Solution: Confirm with the MAH the defined maximum request quantity and re-submit a request for serial numbers below the limit.

Responsible Party: Sender

Sample Error Message: PrimaryItemCode INTERNAL_MATERIAL_CODE [Internal Material Code]: PrimaryItemCode INTERNAL_MATERIAL_CODE [Internal Material Code] in use but is not a primary identifier

Root Cause: The process of updating Product Master Data from CSV or API failed. This error occurs because the feed is attempting to set this material as a Primary Item Code, but it is already in use, as it belongs to another entry in Product Master Data and is not the primary identifier.

Solution: Correct the assignment of the Internal Material Code in Product Master Data to the appropriate IMN or national codes (NDCs, EAN13, Codigo National), and adjust the Primary Item Code designation as needed.

Responsible Party: Customer

Sample Error Message: Validation exception

Root Cause: The packaging code has not been added at the receiver's Serial Number Exchange Manage Profiles screen.

Solution: In the Serial Number Exchange module, select Manage Profiles to check whether the packaging code has been added to the sender-receiver ServiceLink. The sender should contact the receiver and get the packaging code added under the appropriate ServiceLink.

Responsible Party: Sender