Versions Compared

Old Version 3

changes.mady.by.user user-97a1e

Saved on

compared with

New Version 4

changes.mady.by.user user-97a1e

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Onetrail TPN™ Order Response Message

Introduction

The Order Response Status (hereinafter called Order Response) is send from a Seller to a Buyer, to inform the Buyer about the latest status of the related purchase order.

Process

Choreography

OrdRsp_choreography.jpgImage Added

The Order Response is submitted by the Seller to Onetrail TPN™. Onetrail TPN™ processes the Order Response and submits it to the Buyer in their requested format.

Process management

The time between Orders and Order Status (Update) varies per Seller and depends on when the Order Status (Update) Messages are delivered to Onetrail by the Seller.

For more detailed information about supported order response processes we refer to: order response processes

Order Status scenarios

Onetrail TPN™ supports the following Order Status scenarios (or combinations):

  1. Scenario 1: Order Confirmed without changes;
  2. Scenario 2: Order Confirmed with changes;
  3. Scenario 3: Order on-hold;
  4. Scenario 4: Order-line on-hold;
  5. Scenario 5: Order Deleted;
  6. Scenario 6: Order Line(s) Deleted;
  7. Scenario 7: Order-line is added;
  8. Scenario 8: Order-line is split;

The scenarios are detailed in the Syntax paragraph.

Content

The Global Location Numbers (formerly known as EAN address codes) is used to refer to companies and addresses in order messages. These codes can be supplied by Onetrail unless a Trading Partner already has GLNs. The following GLNs are relevant to the Order Response Message (OrdRsp):

  • To identify the Seller: fromRole
  • To identify the Buyer: toRole
  • Where the goods are shipped to in case of warehouse shipment: ShipTo

The planned shipment date is supported by Onetrail in the OrdRsp messages. The planned shipment date can be "provided" and / or "calculated" in the OrdRsp.

The provided shipment date is mandatory, while the calculated shipment date is optional in the OrdRsp Message.

Several scheduledEvents are supported by Onetrail as documented in ORDRSP 3.1.. The GlobalTransportationEventCode is Ship. Ship is a fixed value as dispayed in the image below. The following options are supported:

  • Ship
  • Ship Calculated (optional)
  • Delivery (optional)
  • Delivery Calculated (optional)

<tns:scheduledEvent>
        <tns:TransportationEvent>
               <tns:DateStamp>20140307T000000</tns:DateStamp>
               <tns:GlobalTransportEventCode>Ship</tns:GlobalTransportEventCode>
        </tns:TransportationEvent>
</tns:scheduledEvent>
<tns:scheduledEvent>
        <tns:TransportationEvent>
               <tns:DateStamp>201403010T000000</tns:DateStamp>
               <tns:GlobalTransportEventCode>Delivery</tns:GlobalTransportEventCode>
        </tns:TransportationEvent>
</tns:scheduledEvent>

Format & Syntax

The format of the standard Onetrail XML messages is XML version 1.0. The encoding must be UTF-8. Please refer to our Order XSD Documentation for default values, multiplicity of elements, attributes, business rules and an overview for mapping design purposes. Besides XML Onetrail also supports a standard Edifact D97.A Order Response. For more information about supported standards we refer to: Format & Syntax Order Response

Format

The format of the messages is XML version 1.0. The encoding must be UTF-8.

Communication

Please refer to the communication page: Onetrail TPN™ Communication

Examples

Category:Documentation_version_15.04 Category:Documentation_version_17.03

...