View B2B messages

Application Administrators and members with standard access can filter and view the B2B messages exchanged using a given SAP Ariba connection.

View B2B messages

  1. Select the Main Menu icon.

  2. Select Extensible TraceLink Transfer Exchanges.

  3. Select B2B Messages in the side menu.

  4. Select the Filter button.

  5. In the Filters panel, fill in one or more of the following fields to filter the results:

    • Application Transaction Identifier field – ??.

    • Connection Name field – The name of the B2B connection.

    • Connection Type field – The type of the B2B connection. E.g SAP Ariba.

    • Direction drop-down – The direction of the message.

      • Inbound – A B2B message sent to TraceLink.

      • Outbound – A B2B message sent from TraceLink.

    • Error Code field – The error indicating the reason for failure. It has no value when the status of the message is Success or Processing.

    • Error Message field – The reason the message failed (e.g. The EDIFACT document could not be read from the incoming file).

    • External File Name field – For inbound messages, the external file is the file received by TraceLink from an external system. For outbound messages, it is the file sent from TraceLink to the external system after transformation.

    • Last Updated field – The date and time the message is updated in DD MMM YYYY MM:SS AM/PM format.

      • Last 12 Hours – The messages populated in the last 12 hours, from the current time.

      • Last 24 Hours – The messages populated in the last 24 hours.

      • Last 72 Hours – The messages populated in the last 72 hours.

      • Next 12 Hours – The messages populated in the next 12 hours.

      • Next 24 Hours – The messages populated in the next 24 hours.

      • Next 72 Hours – The messages populated in the next 72 hours.

      • Custom Range – The messages populated in the selected date and time range.

      • Relative – The messages populated in the provided time range in hours.

    • Message Identifier field – The ID of the message.

    • Message Type field – The type of message e.g. Purchase order.

    • Receiver field – The entity receiving the message.

    • Sender field – The entity sending the message.

    • Sending Application field – The name of the application sending the message.

    • Start Time drop-down – The day (in DD MMM YYYY format), the time (in HH:MM:SS format) when TraceLink received the message.

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

      • Failure – Messages that failed to deliver to the recipient.

      • Processing – Messages that are still in-progress.

      • Success – Messages that are successfully delivered to the recipient.

  6. Select Apply.

    The results display in the table.

    • Message Type –The name of the B2B connection.
    • Application Transaction Identifier – A unique business reference, such as a purchase order number, invoice number, or shipment number, that provides a more intuitive way to locate transactions.
    • Direction – The direction of the message.
    • Sender – The name of the entity sending the message.
    • Receiver – The name of the entity receiving the message.
    • Start Time – The day (in DD MMM YYYY format), the time (in HH:MM:SS format) when TraceLink received the message.

  7. Select the Message Type link from the results table.

    The View B2B Message Details screen displays.

B2B Message Details

  • Message Identifier – The ID of the message.
  • Message Type – The type of message e.g. Purchase order.
  • Application Transaction Identifier – A unique business reference, such as a purchase order number, invoice number, or shipment number, that provides a more intuitive way to locate transactions.
  • Sender – The entity sending the message.
  • Sending Application – The name of the application sending the message.
  • Transaction Start Time – The day (in DD MMM YYYY format), the time (in HH:MM::SS format) when TraceLink received the message.
  • Transaction Duration – The time between start and end time of a transaction.
  • External File – For inbound messages, the external file is the file received by TraceLink from an external system. For outbound messages, it is the file sent from TraceLink to the external system after transformation.

  • Canonical File – A standardized internal message format used by TraceLink to represent business transactions consistently across applications and integrations. For Inbound, messages are transformed into the canonical format before being processed, and for outbound, messages are generated from the canonical format to match the destination system’s requirements. For detailed information about the canonical structure and mapping guidelines, see Canonical Guidelines.

  • Processing Status drop-down – The status of the B2B message:
    • Failure – Messages that failed to deliver to the recipient.

    • Processing – Messages that are still in-progress.

    • Success – Messages that are successfully delivered to the recipient.

  • Original Message Type – For inbound the type of message receied from the external exchange, e.g. cXML. For outbound, the type of message sent by the business application, e.g. MPC_Purchase_Order.
  • Direction – The direction of the message.
  • Connection Name –The name of the B2B connection.
  • Connection Type –The type of connection, e.g. SAP Ariba.
  • Receiver – The entity receiving the message.

  • Receiving Application – The name of the application receiving the message.

  • Choreography Type drop-down – The sequence of events that occurs when a B2B message is transmitted:

    • OTHER – The choreography is based on neither the X12 nor the EDIFACT standard.
  • Transform version – A link to the the transform used in the connection. For more information about transforms, see Integration Catalog help center.
  • License Plate – For internal use. The value is used to track a transaction.
  • Forwarded – Forwarded is set to Yes when the B2B message is sent from the Partner’s XTT Exchanges.
  • Delivery Option – The method of delivery for the message from the sender to the receiver. For more information, see the Administer help center.
  •  File Arrived - The time the file arrived in the OPUS system.
  • File Received by XTT Exchanges – The date and time the receiver of the inbound message receives the inbound file in XTT Exchanges.
  • File Received from Partner XTT Exchanges – The date and time the sender of the inbound message receives the forwarded inbound message from the recipient's XTT Exchanges app.
  • Sent to Message Processor – The time when XTT Exchanges sends the message to the B2B message processor.
  • Received by Message Processor – The time the B2B message processor received the message.
  • Sent for Canonical Transformation – The time the message processor sends the file to the transform service, which converts it into the canonical format.
  • Received After Canonical Transformation - The time the message processor receives the file from the transform service.
  • Response Sent to XTT Exchanges - The time the message processor sends the response back to XTT Exchanges.
  • Sent to Business Application - The time the message processor sends the message to the business application.
  • Processing Completed - The time the processing of the transaction is complete.