Search Messages

Administrators can search for and view recall messages such as Consumer Responses and Public Recall Advisements that are exchanged with TraceLink asynchronously. This functionality enables users to troubleshoot message issues by downloading the message's canonical file.

For example, companies using the Recalls process in the Supply Chain Work Management solution can monitor when a new recall comes into Product Information Exchange from Product Information Manager, but then fails to deliver to Agile Process Teams. Customers can then investigate the failure and reprocess the message on their own before contacting TraceLink support for help.

Search Recall Messages

Search for recall messages sent asynchronously to view their status, troubleshoot any issues with a message by downloading the message's canonical file, and reprocess outbound messages that failed to deliver to TraceLink.

  1. Select a [Customer-defined PIE Network] from the Network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the PIE Messages Process in the header.
  4. Select the Go button in the header.
  5. Select Search in the side menu.
  6. Fill in one or more of the following fields to filter the results:

    • Last Processed date drop-down – The date that the message was processed last.

    • Status drop-down – The status of the message: 

      • All (default)
      • In Progress – The message has been received from Product Information Manager and it is currently processing, prior to its map-in success or failure. This step takes place before validation.
      • Forwarding Failed – An error occurred while TraceLink was validating the structure and business logic of the message before sending it to the receiving party.
      • Delivered – The message has successfully been delivered to the receiving party.
      • Received Only – The message has been received from Product Information Manager

    • Message Type drop-down – The type of message sent.

      • Public Recall Advisement – The message contains information about a new or updated recall.
      • Subscription Request – The message contains a request to receive new recalls when they are published by the TraceLink Network Operations team.
      • Historical Sync Request – The message contains a request for recall data from up to the last 12 months (the length of time is determined upon initial configuration of the Supply Chain Work Management Recalls process).
      • Consumer Response – The messages contains recall responses.
  7. Select Show Additional Filters and fill in one or more of the following fields to further filter the results:
    Select Add Additional Filter to include additional filter fields.
    • Sender field – The name or identifier of the party that sends the message.
    • Receiver field – The name or identifier of the party that receives the message.
    • Responding Entity field – The name or identifier of the party responding to the recall (available only if the Message Type is Public Recall Advisement or Consumer Response).
    • TraceLink Recall ID field – The unique identifier that TraceLink assigned to the recall.
    • Product Type drop-down – The type of product in the recall.
      • Biologics – The recalled product is a biological product (e.g. gene therapies).
      • Devices – The recalled product is a device.
      • Drugs – The recalled product is a drug (e.g. acetaminophen).
      • Veterinary – The recalled product is intended for use in animals.
    • Product Description field – Details about the recalled product (e.g. name and dosage).
    • Recalling Company – The name or identifier of the company that manufactured the recalled product.
    • FDA Event ID field – The unique identifier that the FDA assigned to the recall.
    • FDA Recall Number field – The unique identifier that the FDA assigns to each product the recall.
    • FDA Publish Date drop-down – The period of time in which the recall was published by the FDA:
      • Last Week – The recall was published in the last 7 days.
      • Last Month – The recall was published in the last 30 days.
      • Last 3 Months – The recall was published in the last 90 days.
      • Last 6 Months – The recall was published in the last 180 days.
    • Recall Initiation Date drop-down – The period of time in which the recall was initiated by the manufacturer:
      • Last Week – The recall was initiated in the last 7 days.
      • Last Month – The recall was initiated in the last 30 days.
      • Last 3 Months – The recall was initiated in the last 90 days.
      • Last 6 Months – The recall was initiated in the last 180 days.

    • Response Type drop-down – The type of recall response submitted to TraceLink:

      • Acknowledgment – Confirmation that the responding location has been informed of the recall and the individual products being recalled.
      • Impact – Communicates whether each product being recalled is in stock at the location.
      • Quantity – Communicates how much of each product type (e.g. 60 count bottles) in the recall are in stock at the location and will be sent back to the recalling company.
      • Completion – Confirms that the impact and quantity responses for each product in the recall are completed and any product in stock at the location is being sent back to the recalling company.
    • Response Submission Date field – The period of time in which the response was submitted to Tracelink:
      • Last Week – The response was submitted in the last 7 days.
      • Last Month – The response was submitted in the last 30 days.
      • Last 3 Months – The response was submitted in the last 90 days.
      • Last 6 Months – The response was submitted in the last 180 days.
  8. Select Search.

    The results display in the table.

View a message's details and troubleshoot delivery errors

View the details of a message to see additional information about the message such as any exceptions, help troubleshoot any issues with the message by downloading the files, and reprocess a message that failed to deliver to the receiving party.

  1. Select a [Customer-defined PIE Network] from the Network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the PIE MessagesProcess in the header.
  4. Select the Go button in the header.
  5. Select Search in the side menu.
  6. Filter to find the message.
  7. Select the Actions icon in the row for the message.

  8. Select View.

    The message details screen displays.

Download a message’s canonical file to see how the elements submitted in the initial message sent to TraceLink were mapped during message transformation for future reference or as an additional troubleshooting resource.

  1. Select a [Customer-defined PIE Network] from the Network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the PIE MessagesProcess in the header.
  4. Select the Go button in the header.
  5. Select Search in the side menu.
  6. Filter to find the message.
  7. Select the Canonical File link in the row for the message.

    The selected JSON file for the message is downloaded.

Tips

  • The message's canonical file can also be downloaded from the View Details screen using the Action icon in the top right of the screen.

Reprocess an outbound message that failed to deliver to the recipient after troubleshooting. Reprocessing a failed outbound message resubmits the message to TraceLink for processing. Only messages with a Processing Status of Delivery Failed can be reprocessed.

  1. Select a [Customer-defined PIE Network] from the Network drop-down in the header.
  2. Select a Team (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  3. Select the PIE Messages Process in the header.
  4. Select the Go button in the header.
  5. Select Search in the side menu.
  6. Filter to find the message.
  7. Select the Actions icon in the row for the message.

  8. Select Reprocess.

    The message attempts to successfully reprocess.