Reviewing the list of messages

The Manage Messages page shows a list of successfully processed messages and failed messages.

To review the list of messages:

  1. Select Transformation > Manage Messages.
  2. Review this information:
    Creation Date
    The creation date of the message.
    Partner ID
    The partner ID is the hierarchy node of the configuration that identifies a communication partner or a group of communication partners.
    Sender ID
    The sender ID is the identification number of the sender that is contained in the message. For example, the sender ID is the customer ID, the supplier ID, or the logical address of the sender of the message.
    Receiver ID
    The receiver ID is the identification number of the receiver that is contained in the message. For example, the receiver ID can be the customer ID, the supplier ID, or the logical address of the receiver of the message.
    Document ID
    The field shows the document number of the original ASN message.
    Transmission Reference No.
    The field provides a transmission reference number for outgoing messages. In Transformation, the transmission reference number is automatically incremented by one with each message transfer.
    Message Standard
    The message standard defines the format or structure of the message. Examples are ASC X12, UN-EDIFACT, XML, or BOD.
    Message Type
    The message type defines the content of the message. Examples are VDA 4905, VDA 4915, ASC X12 830 Planning Schedule with Release Capability, or ASC X12 862 Shipping Schedule. The message type depends on the message standard.
    Note: For trading partners who require the Shipment Cancellation message to be sent to a different data source name (i.e., final recipient) than the regular shipment , a new code list must be activated in the FeatureActivation code list. On this code list, add the Code value UseShipmentCanceledMessageType. Activating this code results in process shipments with the status of Canceled to be created as messages with the message type Shipment Canceled BOD instead of Shipment.
    Message Status
    These message statuses exist:
    • New: A message is created.
    • Being Processed: The message is currently being processed.
    • Processed: The message is processed and completed.
    • Waiting for Transformation: The message is waiting for the transformation.
    • Ready to be Published: The message is ready to be published.
    • Error: The message transformation failed.
    • Waiting for CarrierRoute BOD: The message transformation is waiting for a CarrierRoute BOD to complete the Shipment BOD processing.
    • To be Processed: The message must be processed.
    • To be Deleted: The message must be deleted.
    Application Advice Received?
    The field shows whether an incoming Application Advice message is available in response to the previously published ASN message:
    • Not Expected: Published ASN message for which a notification of the sender by an Application Advice message is not expected.
    • Pending: Published ASN message for which an Application Advice is expected. The status of these ASN messages is Pending after the transformation, if the Application Advice Expected field on the Partner IDs page is set to Expected.
    • Received: Published ASN message for which an Application Advice has been received without reporting errors. The transformation set process has been successfully completed.
    • Alerted: Published ASN message for which an alert message has been sent to the user in these cases:

      An Application Advice has been received that reports errors on a previously sent ASN message.

      An Application Advice message is expected, but the defined waiting time on the Partner IDs page has been exceeded.

    You can check the Application Advice messages on the Application Advice page.

    Functional Acknowledgment Status
    This field shows the status of a Functional Acknowledgment in response to a previously sent EDI message.
    • Not Expected: EDI message for which a notification of the sender by a Functional Acknowledgment message is not expected.
    • Pending: EDI message for which a Functional Acknowledgment is expected. The status of these EDI messages is Pending after the transformation, if the Functional Acknowledgment Expected field on the Partner IDs page is set to Expected.
    • Alerted: Published EDI message for which an alert message has been sent to the user in these cases:

      A Functional Acknowledgment has been received that reports errors on a previously sent EDI message.

      A Functional Acknowledgment message is expected, but the defined waiting time on the Partner IDs page has been exceeded.

    • Accepted: Published EDI message for which a Functional Acknowledgment has been received without reporting errors. The transformation set process has been successfully accepted.
    • Accepted with Errors: Published EDI message for which a Functional Acknowledgment has been received with reporting errors. The transformation set process has been accepted in spite of the errors.
    • Rejected; Message Authentication: Functional Acknowledgment has been rejected, because EDI message requires authentication.
    • Partially Accepted: Published EDI message for which a Functional Acknowledgment has been received with some reporting errors. The transformation set process has been partially accepted.
    • Rejected: Functional Acknowledgment has been rejected, because of errors.

    You can check the Functional Acknowledgment messages on the Functional Acknowledgment page.

    Message Direction
    The message direction is Inbound for incoming messages or Outbound for outgoing messages.
    Publishing Frequency
    The field defines the frequency in which a message is published. The standard publishing frequency is Immediately.
    Message Sequence Number
    The messages are consecutively numbered in the order in which they are processed.
    Import Message Sequence Number
    This sequence number traces back to the Message Sequence Number column of the Import Messages page. On this page, you can use the sequence number to search for the originally imported message.
    Accounting Entity
    The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations.
    Publishing Service
    The publishing service specifies the target service to which a message is passed.
    • Communication Service: Transformed messages are passed to the Communication Service and sent to an external communication partner.
    • ION Connector Service: Messages are passed to the ION Connector Service and published to ION.
    • No Publishing: The messages are not published.
    Message Version
    The handling of different message versions is currently supported for UN-EDIFACT and ASC X12 messages. If a new message comes in without defined message version in the transformation rule, the transformation rule is updated automatically by the message version.