Introduction
The order request is send from a Buyer to a Seller. The receipt of the order request by the Seller is acknowledged with an Acknowledgement or Negative-Acknowledgement message.
Process
Choreography
The order request is submitted by the Buyer to Onetrail TPN™. Onetrail TPN™ confirms the technical receipt of the order request, process the order request and submit it to the Seller. Once the Seller has confirmed the technical receipt of the order request, Onetrail TPN™ will generate an Acknowledgment and submit this to the Buyer.
In case Onetrail TPN™ does not confirm the technical receipt of the order request, the Buyer needs to take care of resubmitting the order request. In case the Seller refuses the order request, Onetrail TPN™ will generate a Non-Acknowledgment and submit this to the Buyer. The Buyer needs to take care of the proper actions and create a new or modified order request. This can differ per Seller, because some Sellers cannot accept the same purchase order number more than once, in that case a new purchase order needs to be created by the Buyer.
Process management
Once the order request is technically accepted by Onetrail TPN™, a time-alert is started with the process monitor. Once the order is technically confirmed (can be either "accept"/"reject") by the Seller, the time-alert is removed from the process monitor. If the time-alert is not removed within the specified time frame, the process monitor will generate an exception and the Onetrail TPN™ support department will take appropriate actions.
Order scenarios
Onetrail TPN™ supports the following order scenarios:
- Drop Shipment Order (direct delivery)
- Warehouse Order
- Special Bid Order
- Special Deal Order
- eCarepack Order
The scenarios can be combined, except 1 with 2 and 3 with 4.
Also the following flags are available:
- Ship Complete (both on header and line level)
The scenarios and flags are detailed in the Format & Syntax paragraph.
For more detailed information about supported order processes we refer to: order processes
Content
The companies and addresses used in the orders are referenced by Global Location Numbers (formerly known as EAN/ILN address codes). These codes can be supplied by Onetrail unless your company already has GLN's numbers. These given GLN's can only be used to communicate with Onetrail.
The following GLN's are relevant to the Order Request:
- To identify the Buyer: XML: fromRole EDIFACT: UNB020, S002, 0004
- To identify the Seller: XML: toRole EDIFACT: UNB030, S003, 0010
- Where the goods are shipped to in case of Warehouse Shipment: XML: ShipTo EDIFACT: NAD+ST
- Where the Invoice needs to be send to: XML: BillTo EDIFACT: NAD+IV
For more details about standardized content we refer to: content
Format & Syntax
- XML
The format of the standard Onetrail XML messages is XML version 1.0. The encoding must be UTF-8. Please refer to our ORDREQ XSD Documentation for default values, multiplicity of elements, attributes, business rules and an overview for mapping design purposes.
- EDIFACT
Besides XML Onetrail also supports a standard Edifact D97A INVOIC besides a lot of other industry standards. For more information about supported standards we refer to: Available Industry Standards
Communication
Besides web services for both SOAP and REST, Onetrail also supports HTTPS, FTP, AS2 and other communication protocols. For more information about supported communication protocols we refer to: Onetrail TPN™ Communication
Examples
Category:Documentation_version_15.04 Category:Documentation_version_16.01 Category:Documentation_version_16.07 Category:Documentation_version_17.09
