Search for EDIINT Transaction Records

Edit online

About this task

In Sterling B2B Integrator, you can use the Central Search pages to perform basic and advanced searches for information about EDIINT transaction records for business processes that included AS3 processing (including MDNs).

Using the EDIINT search feature, you can use tracking options to view the correlation between an outbound message, its corresponding MDN (if any), and its state (for example, Processed without errors).

To search for EDIINT transaction records for business processes that included EDI interchange processing:

Procedure

  1. From the Administration menu, select Business Processes > Advanced Search > EDIINT.
  2. In the EDIINT Transaction Search page, complete one of the following:
    • Click Go! to view all EDIINT transaction records.
    • Search for specific EDIINT transaction records. Specify any combination of the following search criteria and click Go!

      Contracts – Display the records whose contract name corresponds to the specified contract.

      Status – Display the records whose status corresponds to the specified status. Statuses include ALL, Processed without errors, Processed with errors, Pending, Expired, and MIC Invalid.

      Note: The status displayed is the status of the MDN as it relates to the received transaction. This status does not signify the result of the HTTP transfer of the MDN.

      Type – Display the records whose Internet security protocol type corresponds to the specified type. Search parameters include AS3.

      Note: To view only AS3 records, you will need to select AS3 in the Type list to sort by that message type.

      Start Date – Display the records generated starting on the specified start dates and time.

      End date/time range – Display the records generated prior to the specified end dates and time.

  3. In the EDIINT Transaction Summary page, use the following fields and columns to view general processing information about business processes and perform other activities, as appropriate:
    Status
    Indicator of the status of the EDIINT transaction.
    ID
    AS3 identifier. Click the number to display the Business Process Details page.
    Duplicates
    Number of messages with duplicate message IDs. Click the number to display the EDIINT Duplicate Transaction Summary page. When a message with a duplicate message ID is received, a record for a duplicate message is created. This record contains the transaction information for the instance of the message prior to receiving the duplicate. The current transaction record is updated with information about the duplicate, which is the latest instance of the message.
    Created
    Date and time this transaction record was created. Records are created when messages are built or received.
    State
    Current state of the EDIINT transaction:
    • Processed with errors - An error occurred processing the message. These are usually EDIINT specific errors returned in MDNs, such as decryption failures.
    • Processed without errors - The message was processed successfully.
    • Pending - An acknowledgement has not yet been received for the message.
    • Expired - An acknowledgement was not received for the message in the required amount of time.
    • MIC Invalid - The cryptographic hash in an MDN did not match the one calculated by the system when the message was created.
    Contract
    Contract associated with the EDIINT transaction.
    Type
    Type of communication protocol used. AS3 indicates AS3 protocol.
    Acknowledged
    Date and time that the message was acknowledged.
  4. From the EDIINT Transaction Summary page, click the ID number to access the EDIINT Transaction Detail page. The EDIINT Transaction Detail page provides you with additional details about the EDIINT transaction. From the EDIINT Transaction Detail page, you can click the Message-ID to view the message, click the MDN Message-ID to view the MDN, or change the state of the business process.

    In the EDIINT Transaction Detail page, use the following fields to review detailed process information and perform activities, as appropriate:

    ID
    Number assigned to identify the EDIINT transaction.
    Record created
    Date and time that the record was created.
    Message-ID
    Identification string of the message.
    State
    Current state of the EDIINT transaction:
    • Processed with errors - An error occurred processing the message. These are usually EDIINT specific errors returned in MDNs, such as decryption failures.
    • Processed without errors - The message was processed successfully.
    • Pending - An acknowledgement has not yet been received for the message.
    • Expired - An acknowledgement was not received for the message in the required amount of time.
    • MIC Invalid - The cryptographic hash in an MDN did not match the one calculated by the system when the message was created.
    Acknowledged
    Date and time that the message was acknowledged.
    MDN Message-ID
    Identification string of the MDN.
    Disposition
    Status of the transaction. For example, processed or waiting.
    SHA1 MIC
    Security string information.
    Contract
    Contract associated with the message.
    Type
    Type of transmission protocol used with the message.
    Sender
    Sender of the message.
    Recipient
    Recipient of the message.
    Input Documents
    A link to the business document used to create the message if the transaction is for a message created by this system. This field does not appear if the message was created by a trading partner's system.
    Output Documents
    A link to the business documents extracted from the message, if business documents were extracted from the message. This field does not appear if no documents were extracted from the message. If processing of duplicate messages is not enabled and this transaction is not the first instance of the message, no documents are extracted from the message.
  5. From the EDIINT Transaction Detail page, click the Message-ID string to access the EDIINT Transaction Message contents. The Message page displays, showing the contents of the message sent in the transaction.
  6. From the EDIINT Transaction Detail page, click the MDN Message-ID string to access the EDIINT Transaction MDN contents. The MDN page displays, showing the contents of the MDN sent in the transaction.
  7. If a link is displayed in the EDIINT Transaction Summary page (Duplicates column), click the number in the Duplicates column to access the EDIINT Duplicate Transaction Summary page. The EDIINT Duplicate Transaction Summary page provides you with a list of documents that have duplicate message IDs. From the EDIINT Duplicate Transaction Summary page, you can refine the detail of your search by clicking the ID number for each duplicate document.

    In the EDIINT Duplicate Transaction Summary page, use the following fields to review detailed processing information, as appropriate:

    Status
    Indicator of the status of the EDIINT transaction.
    ID
    Number assigned to identify a business process. Click the number to display the Business Process Details page.
    Duplicates
    Number of messages with duplicate message IDs. Click the number to display the EDIINT Duplicate Transaction Summary page. When a message with a duplicate message-ID is received, a record for a duplicate message is created. This record contains the transaction information for the instance of the message prior to receiving the duplicate.
    Created
    Date and time this transaction record was created. Records are created when messages are built or received.
    State
    Current state of the EDIINT transaction:
    • Processed with errors - An error occurred processing the message. These are usually EDIINT specific errors returned in MDNs, such as decryption failures.
    • Processed without errors - The message was processed successfully.
    • Pending - An acknowledgement has not yet been received for a message.
    • Expired - An acknowledgement was not received for the message in the required amount of time.
    • MIC Invalid - The cryptographic hash in an MDN did not match the one calculated by the system when the message was created
    Contract
    Contract associated with the EDIINT transaction.
    Type
    Type of communication protocol used. AS3 indicates AS3 protocol.
    Acknowledged
    Date and time that the message was acknowledged.
  8. From the EDIINT Duplicate Transaction Summary page, click the ID number to access the EDIINT Duplicate Transaction Detail page. The EDIINT Duplicate Transaction Detail page provides you with additional details about the business process. From the EDIINT Duplicate Transaction Detail page, you can click the Message-ID to view the message, and click the MDN Message-ID to view the MDN.

    In the EDIINT Duplicate Transaction Detail page, use the following fields to review detailed process information and perform activities, as appropriate:

    ID
    Number assigned to identify the EDIINT transaction.
    Record created
    Date and time that this record was created.
    Message-ID
    Identification string of the message.
    State
    Current state of the EDIINT transaction:
    • Processed with errors - An error occurred processing the message. These are usually EDIINT specific errors returned in MDNs, such as decryption failures.
    Note: When a negative MDN is received from a trading partner, the corresponding transaction status in the MDN Correlation (MSGMDNCORRELATION) table is updated to Processed with errors and the disposition type and disposition modifier values are extracted from the Disposition header of the original message.
    • Processed without errors - The message was processed successfully.
    • Pending - An acknowledgement has not yet been received for a message.
    • Expired - An acknowledgement was not received for the message in the required amount of time.
    • MIC Invalid - The cryptographic hash in an MDN did not match the one calculated by the system when the message was created.
    Acknowledged
    Date and time that the message was acknowledged.
    MDN Message-ID
    Identification string of the MDN.
    Disposition
    The disposition of the message according to the MDN.
    SHA1 MIC
    Security string information.
    Contract
    Contract associated with the message.
    Type
    Type of transmission protocol used with the message.
    Sender
    Sender of the message.
    Recipient
    Recipient of the message.
    Output Documents
    A link to the business documents extracted from the message, if business documents were extracted from the message. This field does not appear if a document was not extracted from the message. If processing of duplicate messages is not enabled and this transaction is not the first instance of the message, no documents will be extracted from the message.
  9. From the EDIINT Duplicate Transaction Detail page, click the Message-ID string to access the EDIINT Transaction Message contents. The Message page displays showing the contents of the message sent in the transaction.
  10. From the EDIINT Duplicate Transaction Detail page, click the MDN Message-ID string to access the EDIINT Transaction MDN contents. The MDN page displays showing the contents of the MDN sent in the transaction.