Search for EDI Correlations

Edit online

About this task

To search for EDI correlations:

Procedure

  1. From the Administration menu, select Business Process > Monitor > Advanced Search > EDI Correlation.
  2. In the Search Option area, specify any combination of the following search criteria, as appropriate:
    Field Description Action
    All Level Options
    Location EDI correlations maintained in a specific location. Select one of the following options:
    • Live Tables – Display live (active) EDI correlations. This is the default.
    • Restored Tables – Display EDI correlations restored from an offline location.
    Search Level Type EDI processing level. Select one of the following options:
    • Interchange – For the search query, display results from the interchange level. This is the default.
    • Group – For the search query, display results from the group level.
    • Transaction – For the search query, display results from the transaction level.
    Test Mode Mode of the Sterling B2B Integrator system where documents that contain the EDI correlations were created. Select one of the following options:
    • Any (default)
    • Test
    • Production
    • Information
    • Interchange is a test
    • Syntax only test
    • Echo request
    • Echo response
    Direction Flow of the documents that contain the EDI correlations. Select one of the following options:
    • Any (default)
    • Inbound
    • Outbound
    Sender ID ID for the organization that is sending documents. Type the identifier of the sender.
    Receiver ID ID for the receiving organization. Type the identifier of the receiver.
    Sender ID Qualifier Qualifier used with the Sender ID to define the organization that is sending documents. Type the qualifier of the sender.
    Receiver ID Qualifier Qualifier used with the Receiver ID for the receiving organization. Type the qualifier of the receiver.
    Start Date Documents in progress or completed after the specified start date and time. Using the following formats, type a starting date and time range and select A.M. or P.M.:
    • Date – MM/DD/YY
    • Time – HH:MM:SS
    End Date Documents in progress or completed before the specified end date and time. Using the following formats, type an end date and time range and select A.M. or P.M.:
    • Date – MM/DD/YY
    • Time – HH:MM:SS
    Interchange Level Options
    Interchange Control Number Sequential number, located at the beginning and end of an interchange, used to verify that all interchanges sent have been received and that the information in the interchange is complete. Type the control number that references the interchange.
    Standard EDI standard you agree to use for a trading partnership. Type the name of the standard (including CHIPS or Fedwire).
    Acknowledge-
    ment Status    		 Status of an expected acknowledgement at the interchange level. Select one of the following options:
    • Any (default)
    • Waiting
    • Accepted
    • Accepted with Errors
    • Rejected
    • OverDue
    • Received
    • None
    • Manually Accepted
    Compliance Status Status of compliance checking at the interchange level. Select one of the following options:
    • Any (default)
    • OK
    • NOT OK
    Start Date EDI correlations generated or completed for documents at the interchange level after the specific start date and time. This date is compared with the interchange date/time in the data. Using the following formats, type a starting date and time range and select A.M. or P.M.:
    • Date – MM/DD/YY
    • Time – HH:MM:SS
    End Date EDI correlations generated or completed for documents at the interchange level before the specific end date and time. This date is compared with the interchange date/time in the data. Using the following formats, type an end date and time range and select A.M. or P.M.:
    • Date – MM/DD/YY
    • Time – HH:MM:SS
    Group Level Options - these fields are only available if you choose Group for Search Level Type
    Functional Group ID ID of the functional group indicated in the document. Type the ID of the functional group.
    Group Control Number Sequential number, used to verify that all groups sent have been received and that the information in the group is complete. Type the control number that references the group.
    Acknowledge-
    ment Status    		 Status of an expected acknowledgement at the group level. Select one of the following options:
    • Any (default)
    • Waiting
    • Accepted
    • Accepted with Errors
    • Rejected
    • OverDue
    • Received
    • None
    • Manually Accepted
    • Partially Accepted
    Compliance Status Status of compliance checking at the functional group level. Select one of the following options:
    • Any (default)
    • OK
    • NOT OK
    Start Date EDI correlations generated or completed for documents at the group level after the specific start date and time. This date is compared with the group date/time in the data. Using the following formats, type a starting date and time range and select A.M. or P.M.:
    • Date – MM/DD/YY
    • Time – HH:MM:SS
    End Date EDI correlations generated or completed for documents at the group level before the specific end date and time. This date is compared with the group date/time in the data. Using the following formats, type an end date and time range and select A.M. or P.M.:
    • Date – MM/DD/YY
    • Time – HH:MM:SS
    Transaction Level Options - these fields are only available if you choose Group for Search Level Type
    Transaction Set ID ID of the transaction set indicated in the document. Type the ID of the transaction set.
    Compliance Status Status of compliance checking at the transaction set level. Select one of the following options:
    • Any (default)
    • OK
    • NOT OK
    Message Repair Status Status of message repair (for SWIFT documents only). Select one of the following options:
    • Any
    • Ready for Edit
    • Ready for Resend
    • Aborted
    • Resent
  3. Click Go! to display the EDI correlation records that match your search criteria.
  4. In the EDI Correlation Interchange Results page, click info in the Detail column for the interchange for which you want to view details.
    Note: If Delivery Monitoring is enabled, two Correlations are created when a message is sent. These Correlations are the same names used by the XML Format 2 envelope: MessageStatusIsSuccess and ReceiverDeliveryStatus. The values for both Correlations are initialized to WAITING. When the Delivery Notification or Non-Delivery Warning message is processed these Correlation values will be updated appropriately. If a Delivery Notification message is processed, that means the message has been delivered to the recipient. Therefore, ReceiverDeliveryStatus is set to RcvDelivered and MessageStatusIsSuccess is set to true. If a Non-Delivery Warning message is processed, then the ReceiverDeliveryStatus will be set to RcvDelayedNak, indicating that the a message has been rejected by FIN. For a Non-Delivery Warning message, MessageStatusIsSuccess is set to false. Likewise, if a NAK message is processed, the ReceiverDeliveryStatus is set to RcvDelayedNak because the message has been rejected by FIN and will not be delivered.
    Note: One additional Correlation, Non-Delivery Warning Message Status, is created when processing a Non-Delivery Warning message. This Correlation value contains a numeric error code found in field 431. This error code gives a more detailed status for messages that are not delivered. The following error codes are possible:
    Error Code Error Description
    01

    Delivered

    Note: Not set for a non-Delivery Warning messag.
    02

    Rejected by destination.
    07

    No delivery attempt.
    08

    One or more unsuccessful attempts.
    10

    Message not delivered (that is no delivery history) for one of the following reasons: Message negatively acknowledged on input, Message is Login, Select, Quit or Logout Request, Message was sent in local test mode (not deliverable), Message is MT 097 (processed directly by Slice Processor and never delivered to any logical terminal, and so does not have a delivery history).
    12

    Intercepted.
    31

    Authorized by the copy service server and delivered.
    32

    Not authorized by the copy service server and aborted by the system.
    33

    Copy message is aborted and not delivered to the copy service server.
    34

    Authorized by the copy service server but aborted by the system.
    35

    Not yet authorized/refused by the copy service server.
    37

    Authorized by the copy service server but no delivery attempted.
    38

    Authorized by the copy service server but one or more unsuccessful delivery attempts.
    41

    Copy service bypassed and message delivered.
    44

    Copy service bypassed but message aborted by the system.
    47

    Copy service bypassed but no delivery attempted.
    48

    Copy service bypassed but one or more unsuccessful delivery attempts.
    49

    Refused by central institution. Abort notification MT 019 contains an alphanumeric abort code.
    50-99

    These codes are specific to each FINCopy service. Contact your respective service provider for the meaning of each code within the range 50-99.
    70

    Refusal from the Clearing Computer, and delivery aborted; the Sender of the payment message should also receive an MT 998 / SMT n75 Error Message from the Clearing Computer giving further reasons for the refusal.
    71

    Refusal from the Clearing Computer because of a message format error that prevented normal processing, and delivery aborted.
    99

    System error
  5. In the EDI Correlation Interchange/Group/Transaction Detail Results page, click info to the right of Document Correlations.
    Note: Correlations for a specific standard are displayed using the Standard name as the beginning of the correlation. For the specific correlations that are used with a particular standard, see the documentation for that standard.
    Note: SWIFT data that does not include a Message User Reference may not have a functioning link to the transaction-level correlations when interchange-level correlations are displayed using the EDI Correlation search functionality. If this occurs, view the transaction-level correlations by performing a transaction-level search, or by using the Correlation search functionality.
    Note: Transaction Overdue Time in the EDI Correlation Detail pages is displayed in system milliseconds instead of a formatted date string. To obtain the correct timestamp, take the timestamp when the enveloping process ran and add the configured overdue time to it.
  6. For SWIFT documents, on the EDI Correlation Transaction Results page, click info in the Detail column for the document you want to edit or click the View icon to display the message in read-only mode. The Read Only dialog displays the business names and associated data components. Click Close to exit the Read Only dialog.
    Note: If the Document Repair Status is ReadyForEdit and is a link, you have the necessary permissions set to access and edit the document in the SWIFT Message Editor. If you have corrected a failed document and saved it, the status is changed to ReadyforResend and an e-mail is sent to the address specified in Enveloping properties.
  7. In the Document Correlation Details page, view details about the AS2 message you selected, and to see the correlation between the AS2 message and corresponding EDI document or data. The details available include:
    • time stamp
    • scope
    • process ID
    • document name
    • data value