Type = How Tos ; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User,; Orchestration = Manufacturing, Clinical Supply,; Function = Supply Chain, IT, Project Management,

View B2B messages

Application Administrators and members with standard access can filter and view the B2B messages for AS2 , SFTP and SMTP connection types. Owners can also download the B2B message and functional acknowledgment details.

Owners can view failed messages and understand the reason for the failure. For example, when a sender application sends an X12 message (e.g. B2B_EDI_X12_850_PurchaseOrder_IB_V1) over the AS2 B2B connection, the message fails because the selected choreography type while creating an AS2 B2B connection was EDIFACT. In Track & Trace Services, there was no easy way to catch the failed messages and troubleshoot them. With Extensible TraceLink Transfer, the message is captured before the sender's canonical format is applied.

Owners can view the status of sent messages only. To check whether the message successfully reached the corresponding recipient, go to the network that the message was sent within (e.g. the specific Multienterprise Information Network Tower network). See the Multienterprise Information Network Tower Help Center for more information about this example.

View B2B messages

  1. Select the Main Menu icon.

  2. Select Extensible Tracelink Transfer AWS.

  3. Select Search B2B Messages in the side menu.

  4. Fill in one or more of the following fields to filter the results:

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

      • Failure (default) – To see the messages that failed to deliver.

      • Processing – To see the messages that are still in-progress.

      • Success – To see the messages that are successfully delivered to the recipient.

    • Last Updated drop-down – The list of messages populated in the selected time period:

      • Last week (default) – The messages populated in the last 7 days, from the current day.

      • Last 14 days – The messages populated in the last 14 days, from the current day.

      • Last month – The messages populated in the last 30 days, from the current day.

      • Last 3 months – The messages populated in the last 90 days, from the current day.

      • Last 6 months – The messages populated in the last 180 days, from the current day.

  5. Select Apply.

    The results display in the table.

    • Status – The status of the message.
    • Error code –The error indicating the reason for failure:
      • B2B_CREATE_TOKEN_ERROR – An error occurred while configuring B2B message. Contact TraceLink Support for further assistance.
      • B2B_COULD_NOT_GET_EDI_COUNTER – An error occurred while configuring B2B message. Contact TraceLink Support for further assistance.
      • B2B_COULD_NOT_GET_PARTNER_CONFIGURATION – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_COULD_NOT_GET_TRANSFORM_ENTRY – An error occurred while configuring the transform. Contact TraceLink Support for further assistance.
      • B2B_COULD_NOT_GET_TRANSFORM_VERSION – An error occurred while configuring the transform. Contact TraceLink Support for further assistance.
      • B2B_COULD_NOT_RESOLVE_B2B_CONNECTION – An error occurred while configuring B2B connection. Contact TraceLink Support for further assistance.
      • B2B_COULD_NOT_RESOLVE_LINKIDENTIFIER – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_COULD_NOT_RESOLVE_PROCESS_NETWORK – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_EDI_COUNTER_NOT_UNIQUE – An error occurred while configuring B2B message. Contact TraceLink Support for further assistance.
      • B2B_EMPTY_LINK_IDENTIFIER – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_NO_CANONICAL_FOUND – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_NO_CONTROL_FILE_HEADER – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_NO_INTEGRATION_PRINCIPAL – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_NO_REGION_FOUND – An error occurred while configuring the entity receiving the message. Contact TraceLink Support for further assistance.
      • B2B_NO_ROUTE_FOUND – Internal B2Bmessage error. Contact TraceLink Support for further assistance.
      • B2B_PROCESSING_EXCEPTION – An error in message processing. Contact TraceLink Support for further assistance.
      • B2B_TRANSACTION_TYPE_NAME_NOT_REGISTERED – For an SFTP connection, the file path or folder name is incorrect. For an AS2 connection, the AS2 subject is empty or invalid. If the issue persists, contact TraceLink Support.
      • B2B_TRANSACTION_TYPE_VERSION_NOT_FOUND – Internal B2B message error. Contact TraceLink Support for further assistance.
      • B2B_TRANSFORM_FAILED – The message failed while executing the transform. Contact TraceLink Support for further assistance.
      • XTT_AS2_FAILED_INBOUND – Internal Extensible TraceLink Transfer error. Contact TraceLink Support for further assistance.
      • XTT_CHOREOGRAPHY_CANNOT_PROCESS_FILE – The message failed because the file type did not match the choreography. The supported choreography by TraceLink are:

        • EDIFACT – For EDIFACT files

        • X12 – For X12 files

        • OTHER – For Serialized shipment

      • XTT_FAILED_AV_SCAN – The message failed due an infected file.
      • XTT_INTERNAL_ERROR – Internal Extensible TraceLink Transfer error. Contact TraceLink Support for further assistance.
      • XTT_INVALID_DATA_SPACE – Internal Extensible TraceLink Transfer error. Contact TraceLink Support for further assistance.
      • XTT_INVALID_FILEPATH_WITHIN_INBOX – An incorrect SFTP file path is used. The correct file paths are: INBOX/(transaction_type)/(inbound_document), INBOX/transaction_type/(transform_name)/(inbound_document). If the issue persists, contact TraceLink Support.
      • XTT_RECIPIENT_NOT_FOUND – The message failed because the recipient was not configured correctly. Contact TraceLink Support for further assistance.
      • XTT_RECIPIENT_NOT_UNIQUE – The message failed because the same recipient was configured more than once. Contact TraceLink Support for further assistance.
      • XTT_UNSUPPORTED_TRANSACTION_TYPE – The message failed because TraceLink does support the message type. Contact TraceLink Support for further assistance.

      Error code displays only if the status of the message is Failed.

    • Functional Acknowledgment – A syntactical check to verify whether the received message meets the requirements of the selected choreography type.

      • Accepted – The received message meets the syntactic requirements when the choreography type is X12 or EDIFACT, allowing it to be sent for further processing.

        A failed message can have the functional acknowledgment as Accepted, because the message failed after the functional acknowledgment was received while processing the B2B message.

      • Rejected – The message is not syntactically correct, and rejected for further processing.

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

    • Last Updated – The time when the message is sent or received. The inbound messages display the time when the message was sent to the target application or the time at which an error occurred. The outbound messages display the time when Extensible TraceLink Transfer receives a response.

    • Sender Application – The name of the entity and application sending the message.

    • Recipient Application – The name of the entity and application receiving the message.

  6. Select the Action icon in the row for the B2B message.

  7. Select View in the row for the B2B message.

    The View B2B Message screen displays.

  • Select Download B2B Message to view the details of the B2B message.

  • Select Download Functional Acknowledgment to view the details of the functional acknowledgment. This option is displayed only for messages involving exchange of X12 and EDIFACT files.

B2B message details

  • Sender – The entity sending the message.
  • Sender Application – The name of the application sending the message.
  • Recipient – The entity receiving the message.
  • Recipient Application – The name of the application receiving the message.
  • Status – The status of the message.
  • Choreography Type – 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.
    • X12 – The choreography is based on the X12 standard.
    • EDIFACT – The choreography is based on the EDIFACT standard.
  • B2B Connection Name – The name of the entity creating the B2B connection.
  • B2B Connection Type – The type of the B2B connection e.g. SFTP.
  • Message Type – The type of message e.g. Purchase order.
  • Message ID – The ID of the message.
  • Start Date – For inbound messages, the time when the file arrived via AS2 or SFTP connection. For outbound messages, the time at which the application initiated the message and the file was received the B2B Transaction Processor.

  • Last Updated – The time when a when the file is sent or received in a message. The inbound messages display the time when the action was completed by sending the file to the target application or the time at which an error occurred. The outbound messages displays the time when XTT receives a response.

  • File Size – The size of the message file in KB.

  • File Name – For inbound messages, the file name provided by the sender entity. For outbound messages, the file name generated by TraceLink.
  • Error code – The error indicating the reason for failure. It has no value when the status of the message is Success or Processing. The list of errors are:
    • B2B_CREATE_TOKEN_ERROR – An error occurred while configuring B2B message. Contact TraceLink Support for further assistance.
    • B2B_COULD_NOT_GET_EDI_COUNTER – An error occurred while configuring B2B message. Contact TraceLink Support for further assistance.
    • B2B_COULD_NOT_GET_PARTNER_CONFIGURATION – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_COULD_NOT_GET_TRANSFORM_ENTRY – An error occurred while configuring the transform. Contact TraceLink Support for further assistance.
    • B2B_COULD_NOT_GET_TRANSFORM_VERSION – An error occurred while configuring the transform. Contact TraceLink Support for further assistance.
    • B2B_COULD_NOT_RESOLVE_B2B_CONNECTION – An error occurred while configuring B2B connection. Contact TraceLink Support for further assistance.
    • B2B_COULD_NOT_RESOLVE_LINKIDENTIFIER – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_COULD_NOT_RESOLVE_PROCESS_NETWORK – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_EDI_COUNTER_NOT_UNIQUE – An error occurred while configuring B2B message. Contact TraceLink Support for further assistance.
    • B2B_EMPTY_LINK_IDENTIFIER – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_NO_CANONICAL_FOUND – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_NO_CONTROL_FILE_HEADER – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_NO_INTEGRATION_PRINCIPAL – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_NO_REGION_FOUND – An error occurred while configuring the entity receiving the message. Contact TraceLink Support for further assistance.
    • B2B_NO_ROUTE_FOUND – Internal B2Bmessage error. Contact TraceLink Support for further assistance.
    • B2B_PROCESSING_EXCEPTION – An error in message processing. Contact TraceLink Support for further assistance.
    • B2B_TRANSACTION_TYPE_NAME_NOT_REGISTERED – For an SFTP connection, the file path or folder name is incorrect. For an AS2 connection, the AS2 subject is empty or invalid. If the issue persists, contact TraceLink Support.
    • B2B_TRANSACTION_TYPE_VERSION_NOT_FOUND – Internal B2B message error. Contact TraceLink Support for further assistance.
    • B2B_TRANSFORM_FAILED – The message failed while executing the transform. Contact TraceLink Support for further assistance.
    • XTT_AS2_FAILED_INBOUND – Internal Extensible TraceLink Transfer error. Contact TraceLink Support for further assistance.
    • XTT_CHOREOGRAPHY_CANNOT_PROCESS_FILE – The message failed because the file type did not match the choreography. The supported choreography by TraceLink are:

      • EDIFACT – For EDIFACT files

      • X12 – For X12 files

      • OTHER – For Serialized shipment

    • XTT_FAILED_AV_SCAN – The message failed due an infected file.
    • XTT_INTERNAL_ERROR – Internal Extensible TraceLink Transfer error. Contact TraceLink Support for further assistance.
    • XTT_INVALID_DATA_SPACE – Internal Extensible TraceLink Transfer error. Contact TraceLink Support for further assistance.
    • XTT_INVALID_FILEPATH_WITHIN_INBOX – An incorrect SFTP file path is used. The correct file paths are: INBOX/(transaction_type)/(inbound_document), INBOX/transaction_type/(transform_name)/(inbound_document). If the issue persists, contact TraceLink Support.
    • XTT_RECIPIENT_NOT_FOUND – The message failed because the recipient was not configured correctly. Contact TraceLink Support for further assistance.
    • XTT_RECIPIENT_NOT_UNIQUE – The message failed because the same recipient was configured more than once. Contact TraceLink Support for further assistance.
    • XTT_UNSUPPORTED_TRANSACTION_TYPE – The message failed because TraceLink does support the message type. Contact TraceLink Support for further assistance.
  • Error Description - The reason the message failed (e.g. The EDIFACT document could not be read from the incoming file).
  • Direction - To identify whether the message is inbound or outbound. The values are:
    • Inbound - The message delivered to Extensible TraceLink Transfer.
    • Outbound - The message sent from Extensible TraceLink Transfer.
  • Status - The status of the functional acknowledgment associated with the message.

    • Accepted – The received message meets the syntactic requirements when the choreography type is X12 or EDIFACT, allowing it to be sent for further processing.

      A failed message can have the functional acknowledgment as Accepted, because the message failed after the functional acknowledgment was received while processing the B2B message.

    • Rejected – The message is not syntactically correct and it is rejected for further processing.

  • Date received – The date the functional acknowledgment was received.
  • File Name – The name of the functional acknowledgment.
  • File Size – The size of the functional acknowledgment in KB.

Tag end