Transaction statuses

Transactions that are passing through Orderful have three different types of status:

  1. Validation
  2. Delivery
  3. Acknowledgement

Each of these statuses contains information about the transaction.

Validation status

Validation is a process to check if the format and content of a transaction respect the defined validation requirements. Validation can involve GuidelinesGuidelines - A Guideline defines the information that a transaction should contain. Guidelines are applied as requirements for Relationships., Workflows, or RulesRules - A Rule is an instruction that modifies EDI data as it passes through the Orderful platform. A Rule can be applied to an element, segment, or entire loop within an EDI document.. Validation can be performed on the sender's side, the receiver's side, or both.

There are three possible validation statuses:

  • Processing: Orderful is executing RulesRules - A Rule is an instruction that modifies EDI data as it passes through the Orderful platform. A Rule can be applied to an element, segment, or entire loop within an EDI document. and running GuidelineGuideline - A Guideline defines the information that a transaction should contain. Guidelines are applied as requirements for Relationships. validation on the transaction. You will not be able to view the transaction or perform any actions on it while it is in this status.
  • Valid: The transaction respects Inbound GuidelinesGuidelines - A Guideline defines the information that a transaction should contain. Guidelines are applied as requirements for Relationships. and Workflow requirements. There were no RuleRule - A Rule is an instruction that modifies EDI data as it passes through the Orderful platform. A Rule can be applied to an element, segment, or entire loop within an EDI document. execution errors.
  • Invalid: The transaction doesn't respect one of the Inbound GuidelinesGuidelines - A Guideline defines the information that a transaction should contain. Guidelines are applied as requirements for Relationships. or Workflow requirements, or there was a RuleRule - A Rule is an instruction that modifies EDI data as it passes through the Orderful platform. A Rule can be applied to an element, segment, or entire loop within an EDI document. execution error.

Delivery status

Delivery is the process of sending a file from Orderful to a Communication ChannelCommunication Channel - The Communication Channel is the connection between Orderful and a Trading Partner’s System of Record (SOR). and checking if it has been received.

There are four possible delivery statuses:

  • Pending: From the sender's side, the delivery status stays "Pending" when the transaction hasn’t been sent to the receiver. From the receiver's perspective, the delivery status stays "Pending" when the transaction hasn’t been sent to the receiver’s communication channel.
  • Sent: From the sender's side, the delivery status becomes "Sent" when the transaction is sent to the receiver. From the receiver's side, the delivery status becomes "Sent" when the transaction is sent to the receiver’s communication channel.
  • Failed: The receiver’s Communication Channel didn’t receive the transaction.
  • Delivered: The receiver’s Communication Channel confirmed the transaction has been received.

Acknowledgement status

Acknowledgement is a process initiated by the receiver to inform the sender whether the information from a transaction can be processed by the receiver’s backend system.

There are three possible acknowledgement statuses:

  • Accepted: The receiver confirms to the sender that the transaction can be processed by their backend system. The receiver can either allow Orderful to auto-accept all their transactions or send an X12 functional acknowledgment (997) that contains an "Accepted" acknowledgment code.
  • Accepted (with errors): The receiver confirms to the sender that the transaction can be processed by their backend system but highlights errors that they would like the sender to fix for future transactions. The sender doesn’t have to resend an updated transaction. This status is only available if the receiver sends an X12 functional acknowledgment (997) that contains an "Accepted with errors" acknowledgment code.
  • Rejected: The receiver confirms to the sender that the transaction can’t be processed by their backend system. The sender has to resend an updated transaction correcting the errors. This status is only available if the receiver sends an X12 functional acknowledgment (997) that contains a "Rejected" acknowledgment code.

Did this page help you?