Stage | Description |
---|---|
Transferring incoming files | The gateway receives files from a source defined by the inbound connection. |
Processing incoming files | For a custom file that Intelligent Structure Discovery processes, the message structure parses the file and produces output group (interface) files, then writes each interface file to the B2B Gateway document store. For other custom files, the custom inbound mapping writes the incoming files to an interface file on the B2B Gateway document store or writes the data to the backend system. |
Processing files to backend | Processing the process-to-backend mapping. |
Reprocessed from event | Indicates that the event was generated as a result of reprocessing of another event. The Event ID is presented in the status. |
Reprocessed | Indicates that the event was reprocessed and a new event was generated. |
Change event status to discarded | Indicates that the event status was manually changed to Discarded. If the user entered a reason for the change, the reason is displayed. |
Stage | Description |
---|---|
Processing files from backend | Processing the process-from-backend mapping. |
Processing outbound mapping | The outbound mapping reads the files from the gateway and sends them to the partner. |
Transferring incoming files | The gateway sends files to a target defined by the outbound connection. |
Waiting for Acknowledgment (EDI X12 messages, outbound flow) | Waiting for partner to send a technical acknowledgment, a functional acknowledgment, or both. |
Reprocessed from event | Indicates that the event was generated as a result of reprocessing of another event. The Event ID is presented in the status. |
Reprocessed | Indicates that the event was reprocessed and another event was generated. |
Change event status to discarded | Indicates that the event status was manually changed to Discarded. If the user entered a reason for the change, the reason is displayed. |