View Transaction Details

Select the View Details icon in the Actions column of the results table on the Info Exchange screen.

View details about a specific message and troubleshoot issues:

• Diagnose issues by viewing the message's processing status and downloading files.
• Manually reprocess or continue processing a failed message.
• Manually deliver and redeliver the message to the appropriate recipient.

• Processlink or Service – The company-assigned name of the specific TraceLink app that correlates to the message (e.g. Kendall Product Trace US).
• Business Process – The TraceLink app that correlates to the message (e.g. Master Data Exchange, Serialized Operations Manager).
• Transaction Type – The type of message for the specific app (e.g. the Product Track module's Transaction Type could be Pick/Ship, Return Receipt, Create Initial Transaction, etc.).

  See Message Types for more information.

• Input File Name – The initial file sent to TraceLink (initiating the message).

  The Input, Canonical, and Output Files are identical for the following Transaction Types when sent between two Owners of Serialized Operations Manager:

  • SOM_DEACTIVATE_EVENT and SOM_DEACTIVATE_EVENT_IB
  • SOM_DESTROY_EVENT and SOM_DESTROY_EVENT_IB
  • SOM_DECOMMISSION_EVENT and SOM_DECOMMISSION_EVENT_IB
  • SOM_END_OF_BATCH_EVENT and SOM_END_OF_BATCH_EVENT_IB
  • SOM_PRODUCT_RELEASE_EVENT and SOM_PRODUCT_RELEASE_EVENT_IB
  • SOM_RECEIPT_EVENT and SOM_RECEIPT_EVENT_IB
  • SOM_SHIPMENT_EVENT and SOM_SHIPMENT_EVENT_IB
• Canonical File Name – The TraceLink-specific format that displays the data in a normalized fashion (independent of the Input or Output files).
• Sender – The entity information of the sender of the message.
• Recipient – The recipient of the message.
• Transaction ID – TraceLink's unique message identifier. This field determines the available actions against the message (e.g. receipt, import, delivery, redelivery).
• Input File Format – The format of the input file (e.g. XML, CSV).
• Canonical File Format – The format of the canonical file (e.g. XML, CSV).
• Reconciliation Information – The reconciliation status of the message.
  • Status:
    • False – The message has not been reconciled.
    • True – The message has been reconciled.
  • Reason – The remarks about the reconciliation of the message.

This table shows the state of the message at each processing step.

• Date - Time – The date and time of the processing step. Format is [DD] [Mmm] [YYYY] - [HH]:[MM] [AM/PM].
• Processing Code – The resulting state of the processing step, including:
  • Submitted messages:
    • A Submitted link displays next to the message's Processing Code if the message is processing, prior to its map-in success or failure.
  • Failed status types:
    • Map In Failed
    • Processing Failed
    • Map Out Failed
    • Blocked
    • Needs Investigation
  • Success status types:
    • Processed
    • Delivered
    • With Warning

  See the Processing Status Descriptions and Icons drop-down on the Info Exchange help topic for more information.

• Review Status– If the message is configured to be reviewed before delivery, this field shows its status.

  • Pending Review – The message must be reviewed before delivery.
  • Delivery Allowed – A user reviewed the message and allowed delivery.
  • Delivery Stopped – A user reviewed the message and did not allow the delivery.
• Output File Name – If the message was delivered, the name of the transformed output file. Select the link to view or download the file.

  The Input, Canonical, and Output Files are identical for the following Transaction Types when sent between two Owners of Serialized Operations Manager:

  • SOM_DEACTIVATE_EVENT and SOM_DEACTIVATE_EVENT_IB
  • SOM_DESTROY_EVENT and SOM_DESTROY_EVENT_IB
  • SOM_DECOMMISSION_EVENT and SOM_DECOMMISSION_EVENT_IB
  • SOM_END_OF_BATCH_EVENT and SOM_END_OF_BATCH_EVENT_IB
  • SOM_PRODUCT_RELEASE_EVENT and SOM_PRODUCT_RELEASE_EVENT_IB
  • SOM_RECEIPT_EVENT and SOM_RECEIPT_EVENT_IB
  • SOM_SHIPMENT_EVENT and SOM_SHIPMENT_EVENT_IB
• Output File Format – The format of the output file (e.g. XML, IDoc, Flat).

Table Example

	Date - Time	Processing Code Review Status	Output File Name	Output File Format	Actions
	28 Aug 2016 03:49 PM GMT	Map in Failed --	--	--	Reprocess Input File
	29 Aug 2016 11:23 AM GMT	Delivered --	10_Shipment_1_CommAggShip_RxWholesaler_test.xml	XML	Redeliver Output File

• Select Input File Name or Canonical File Name.

  The file downloads.

• Select the link in the Processing Code column of the table to view the processing status details of the message.

  TraceLink displays the processing result in a new browser window (in text format) for analysis.

• Select a link in the Actions column of the table:
  • Redeliver Output File – TraceLink resends the same outbound message. Available for messages that either succeed or fail. Redelivery does not generate new messages in the application but does reprocess and resend the message to the recipient.
  • Deliver Output File – TraceLink sends an outbound message that failed on the recipient's end. Only available to users from the recipient company if the Processing Code is Processed and the Review Status is not Pending Review.

  • Reprocess Input File – TraceLink reprocesses an inbound message. Only available to Administrator users from the sender or recipient company if the Processing Code is Processing Failed or Map In Failed.

    If a Dispenser is receiving against an ASN where one or more lines have previous processing exceptions (Informational Message) related to missing Product Master Data, ​Reprocess Input File displays if the Processing Status is Delivered, the Company is a Dispenser, and the Transaction Typeis US Product Track Shipment Transaction History.