Document detail events

To more accurately display the times that are associated with important events in the lifecycle of your data, the Document detail page might display the following events:

Transmitted: Indicates when IBM received the document
Pre-processed: Indicates that some additional processing occurred before normal processing of the document
Started Processing: Indicates that the document is being processed
Post-processed: Indicates that some additional processing occurred after normal processing of the document
Submitted to Mailboxing: Indicates when the document was sent to the appropriate mailboxes
Loaded: Indicates when the document was available for pickup
Picked Up: Indicates when the trading partner picked up the document

Note: The events that display are dependent on the actual configured data flow.

Depending on the IBM services to which you have subscribed, InFlight might display additional events that are generated for your unique tracking requirements.

eInvoicing

If you are configured for eInvoicing, you might see the following events:
Events	Description
eInvoicing Signed eInvoicing Validated	These events can be associated with green or red status indicators.
eInvoicing Passthrough	Pass-through data.
Internal eInvoicing Error	Internal error—call IBM Customer Support.
eInvoicing TrustWeaver Polled	TrustWeaver has been polled to ensure that systems are available. This event is only applicable for Brazil and Mexico.
eInvoicing Cancellation Initiated	The cancellation of an invoice has been initiated. This event is only applicable for Brazil.
eInvoicing Canceled	The cancellation of an invoice has been completed. This event is only applicable for Brazil.
Buyer eInvoicing Archived Supplier eInvoicing Archived eInvoicing Archive Receive eInvoicing Supplier Archive Send eInvoicing Buyer Archive Send (if External Archiving* is used)	Archive data responses.
eInvoicing Archive Initiated	Archiving of an invoice has been initiated.
eInvoicing Archive Created	Archive data response.
eInvoicing TrustWeaver Archive Created	TrustWeaver has created an archive for the invoice. This event is only applicable for those who subscribe to TrustWeaver Archiving.
eInvoicing Signing Initiated	The signing of an invoice has been initiated. This event is only applicable for Brazil and Mexico.
eInvoicing Scheduled for Retry	An invoice was not successfully processed and has been scheduled for a retry.

Note: * External Archiving is archiving not provided by IBM

RosettaNet

If you are configured for RosettaNet, you might see the following events:
Events	Description
Received at Business Tone	A Partner Interface Process (PIP) was received by an IBM internal service, Business Tone.
Processed at Business Tone	A PIP was processed at Business Tone.
Sent from Business Tone	A PIP was sent from Business Tone.
Business Tone Received Receipt Notification	A notification received when a PIP completely processes through Business Tone.
Business Tone Acknowledgment Error	Business Tone was able to deliver the file but received an acknowledgment that could not be processed.
Business Tone Retried	The initial send attempt failed and the file has gone into retries.
Business Tone 0A1 Sent	The retries were exhausted and the file was not delivered, so an 0A1 notification is sent.
Business Tone 0A1 Received	The trading partner received the file but could not send a response, so they sent a 0A1 notification.

NAESB

If you are configured for NAESB, you might see the following events:
Events	Description
Received at Business Tone	A transaction doc was received by an internal service, Business Tone.
Processed at Business Tone	A transaction doc was processed at Business Tone.
Sent from Business Tone	A NAESB doc was sent from Business Tone.
Business Tone Received Receipt Notification	A positive NAESB receipt is received when a NAESB doc completely processes through Business Tone.
Business Tone Acknowledgment Error	A negative NAESB receipt is sent when the NAESB doc is sent to partner.

SAP Status

If you are configured for SAP Status, you might see the following events:
Events	Description
Processed Response Sent Response	SAP status

Note: If you have subscribed for SAP Status messages, you might see documents with the type SAPSTAT.

OFTP2, SFTP, FTPS, or HTTP/S Protocol

If you are configured for OFTP2, SFTP, FTPS, or HTTP/S Protocol, you might see the following events:
Events	Description
Protocol Started Accepted Rejected Scheduled for Retry Retry Started Near Retry Limit Retry Limit Exceeded Scheduled for Delivery Available Picked Up Session failed Exceeded throttle limit	Files might be sent immediately or might be scheduled to be delivered at a later time. Schedules can be set up to deliver files for specific trading partners at specified times, or to pull files from a trading partner's server at a specific time. Note: The Exceeded throttle limit message means there are too many open sessions to that particular host for that protocol, so the process needs to wait.

Sterling Synchronous B2B Process Service

If you are configured for the Sterling Synchronous B2B Process Service, you might see the following events:
Events	Description
Primary Request Secondary Request Secondary Response Primary Response	These events indicate where the message is or if there has been a failure in processing and delivering the message. Primary Request This is the initial web service request. You or your trading partner initiates a request to the service. Secondary Request This is the service making a secondary web service request to you or your trading partner. Secondary Response This is the response received from the secondary request. Primary Response This is the response from the service, back to the initiator of the primary request.

Sterling Process Enrichment Service

If you are configured for the Sterling Process Enrichment Service, you might see the following events:
Events	Description
Primary Punchout Request Secondary Punchout Request Secondary Punchout Response Primary Punchout Response	These events indicate where the message is or if there has been a failure in processing and delivering the message. Primary Punchout Request This is the initial web service request. You or your trading partner initiates a request to the service. Secondary Punchout Request This is the service making a secondary web service request to you or your trading partner. Secondary Punchout Response This is the response received from the secondary request. Primary Punchout Response This is the response from the service to the initiator of the primary request.

SOAP Gateway

If you are configured for the SOAP Gateway, you might see the following events:
Events	Description
Receive Pushout Request Send Pushout Request Receive Pushout Response	These events indicate where the message is or if there has been a failure in processing and delivering the message. Receive Pushout Request This event occurs when the SOAP gateway receives a request from B2B Integration SaaS. Send Pushout Request This event occurs when the SOAP gateway sends the document to you or your trading partner. Receive Pushout Response This event occurs when a response is received from the SOAP gateway, indicating that the document has been sent.

x400

If you are configured for the x400, you might see the following events:
Events	Description
Submitted to Gateway Delivered to Network Picked up Failed to Deliver Not Picked up Start Processing Transmitted	These events indicate where the message is or if there has been a failure in processing and delivering the message.