Message Implementation Guideline

Order
Version 2010

Issue date: 01.07.2010

Author: wdk/BRV/GEFEG

Generated by GEFEG.FX
order_A2
XML - INDUSTRIAL SOLUTION
Guideline Structure

Occurrence Element / Attribute

order_A2
1 .. 1 xsd:sequence
1 .. 1 DocumentID
0 .. 1 Variant
1 .. 1 xsd:sequence
0 .. 1 EarliestDeliveryDate
0 .. 1 TransportPriority
0 .. 1 Campaign
0 .. 1 DeliveryRemarks
0 .. 1 BlanketOrderReference
1 .. 1 xsd:sequence
1 .. 1 DocumentID
1 .. 1 CustomerReference
1 .. 1 xsd:sequence
1 .. 1 DocumentID
1 .. 1 BuyerParty
1 .. 1 xsd:sequence
1 .. 1 PartyID
1 .. 1 AgencyCode
0 .. 1 OrderingParty
1 .. 1 xsd:sequence
1 .. 1 PartyID
1 .. 1 AgencyCode
0 .. 1 Consignee
1 .. 1 xsd:sequence
1 .. 1 PartyID
1 .. 1 AgencyCode
0 .. 1 PaymentTerms
1 .. 1 xsd:sequence
1 .. 1 PaymentMethod
1 .. unbounded OrderLine
1 .. 1 xsd:sequence
1 .. 1 LineID
0 .. 1 PortalReference
0 .. 1 AdditionalCustomerReferenceNumber
1 .. 1 xsd:sequence
1 .. 1 DocumentID
1 .. 1 OrderedArticle
1 .. 1 xsd:sequence
1 .. 1 ArticleIdentification
1 .. 1 xsd:sequence
0 .. 1 BuyersArticleID
0 .. 1 ManufacturersArticleID
0 .. 1 EANUCCArticleID
1 .. 1 xsd:sequence
0 .. 1 RequestedDeliveryDate
1 .. 1 RequestedQuantity
1 .. 1 xsd:sequence
1 .. 1 QuantityValue

EDIWheel version 2010 Print date: 09.09.2010

Issue date: 01.07.2010 Page: 2/ 2
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

order_A2 Name Root element tag Identification numbers and text: The allowed characters are
Descr. The tag of the root element indicates the document type and a [a-z, A-Z,0-9 and the underscore '_']. The terms
suffix 'Mandatory', 'must be used', 'has to be used' and any min
Remark The root element tag of this order is always "order_A2". occurence greater than '0' mean that an XML element must
be sent with a value in it .
xsd:sequence Occurrence 1 .. 1
DocumentID Occurrence 1 .. 1
Length .. 17
Name Message version
Descr. Identification of Message version
Remark This field should only contain ‘A2’ as fix value.
In some cases the status of this element is optional, and so
not used by some users.In order to guarantee a compatibility
of all business partners in the future these few applications will
be updated step by step.
Variant Occurrence 0 .. 1
Length 1
Name Variant number
Descr. Variant of the message.
Remark The variant of this release is “5”. The EDIWheel website will
provide further information about the currently available
variants.
xsd:sequence Occurrence 1 .. 1
EarliestDeliveryDate Occurrence 0 .. 1
Length .. 10
Pattern \d{4}-\d{2}-\d{2}
Name Earliest delivery date
Descr. Earliest delivery date at the place of delivery.
Remark This header information provides optimization in the logistic.
TransportPriority Occurrence 0 .. 1 Rush:If the customer wants to receive delivery faster than
Length .. 4 the agreed regular terms, then he can use this element to
Name Transport priority inform the supplier that the order must be treated differently
Remark In order to express that the order is a normal order the from the usual case. As mentioned before, the delivery
element must not be used. terms are agreed as a default at the supplier/customer level
The customer can inform the supplier how this order should so they can be specified differently on a case by case basis.
be handled. If the element is not used it means the order will The rush order simply means that the goods ordered in this
be handled by the supplier under the default way and the order should be delivered faster as usual.
goods will be delivered within the default delivery scheme or
Replenishment:It means that the customer either sends an

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 3/ 3
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

according to the RequestDeliveryDates provided at line level. order for which he does not expect an exact timing or
The default delivery schemes are supplier/customer/country sends an ordrer for which the supplier will compute the
specific and therefore not specified in this documentation. contractual RequestedDeliveryDate. It should be used only
Before starting any integration, the customer and the supplier on bilateral agreement between the customer and the
must agree on what is the normal delivery term. supplier. Note some suppliers in some countries will confirm
the dates for such kind of order so the rule should be if date
is confirmed, than it means the supplier will deliver on those
dates, if the date is 99991231, than no exact date is
confirmed in the order confirmation message and it means
as well that the suppliers customer service will contact the
customer to agree on delivery dates and quantities.There
are no general rules about the volume or about the way the
supplier is processing this replenishment orders.

Seasonal orders:This transport priority means that the

customer is purchasing goods for a whole season (winter or
summer).Knowing that these orders are containing big
quantity of tyres and that the delivery of these goods has to
be spread over the whole period, the exact delivery dates
will not be confirmed in the order confirmation message.
The actual procedures will remain meaning the customer
service will contact regularely the customer to agree on
which quantity should be delivered by when.
Applicable Codes
REPL Replenishment
The order has to be processed folllowing the supplier's
replenishment delivery scheme. Depending on the supplier it
can mean that in the order response, - the delivery dates and
quantities are not calculated at request time but later. In this
case the order response returns 99991231, meaning the
delivery dates cannot be committed.- the delivery dates and
quantities are calculated based on the replenishment scheme
of the supplier and provided requested dates.
RUSH Rush Order
SEAS Seasonal order
Seasonal order means that there will never be a confirmed
delivery date in the order confirmation message. The
requested delivery date will be considered as a starting date
by when the first shipments should take place. Nevertheless,
the suppliers customer service will always contact the dealer

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 4/ 4
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

Applicable Codes
to agree exactly what and when will be delivered.
Campaign Occurrence 0 .. 1 This information is mainly used in the order / order
Length .. 12 confirmation message and is optional. Not supported by all
Name Campaign suppliers.
Descr. Identification of a Campaign/ a Promotion.
This element is used to identify if the order is related to a
sales campaign/promotion. The content of the element
should be the campaign number given by the supplier.

As for each functionality, the customer must check before

implementing the automatic ordering with the supplier if a
given functionality is supported or not by the supplier.
DeliveryRemarks Occurrence 0 .. 1 Optional field. Not supported by all suppliers. This field
Length .. 70 could be used to give additional information about delivery
Name Delivery Remarks purposes.
BlanketOrderReference Occurrence 0 .. 1 This value is used only in the order message. Not supported
Name Blanket order reference information by all suppliers.
Remark Equivalent EDIFACT code is BO
xsd:sequence Occurrence 1 .. 1
DocumentID Occurrence 1 .. 1
Length .. 35
Name Reference to contract number
Descr. Reference to the contract referring to the present order.
CustomerReference Occurrence 1 .. 1
Name Customer reference information
xsd:sequence Occurrence 1 .. 1
DocumentID Occurrence 1 .. 1 Only used in the order message. If a customer reference is
Length .. 35 sent within an inquiry the supplier will simply ignore it and
return as received.
This number is the customer purchase order number
generated by the customer IT system. It should not be a
manually created number.

This number has to be unique if a customer wants the

supplier to apply a control procedure that he does not
process the same order twice.

This order number will be used in all subsequent flows

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 5/ 5
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

(order confirmation, delivery, invoice, order status) for

reconciliation and controlling purpose. This number is also
present on the delivery and invoice and is as well sent back
to the customer in the different EDI messages.
BuyerParty Occurrence 1 .. 1
Remark Contracting party, e.g. party who is doing / establishing the
sales contract by a legal way. In other words it's the entity
who's doing the business contract with the supplier and who
takes the legal responsibility. Depending on the customers
organisation it could be a central purchasing department
(headquarter) or a main dealer.
xsd:sequence Occurrence 1 .. 1
PartyID Occurrence 1 .. 1 By the party ID, called buyer party, is considered the
Length .. 17 number which identifies the purchasing party. In other
Name Buyer ID words, who is demanding goods. Depending on the
Descr. Identification number of a buyer. customer organisation, it might be the same as the ship-to
(consignee) or the same as the invoice payer.
AgencyCode Occurrence 1 .. 1
Descr. Code identifying the agency responsible for a code list.
Length .. 3
Name Type of the buyer's identification number.
Applicable Codes
9 EAN (International Article Numbering association)
91 Assigned by seller or seller's agent
92 Assigned by buyer or buyer's agent
OrderingParty Occurrence 0 .. 1
Remark The initial ordering / stipulating party is the partner who is
placing/creating the purchase order in the customer system.
This element has to be used when the ordering party is
different from the buyer (example shop versus head office).
Note: This level is not supported by all manufactureers.
xsd:sequence Occurrence 1 .. 1
PartyID Occurrence 1 .. 1
Length .. 17
Name Ordering Party ID
AgencyCode Occurrence 1 .. 1
Descr. Code identifying the agency responsible for a code list.
Length .. 3

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 6/ 6
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

Name Type of the ordering party's identification number.

Applicable Codes
9 EAN (International Article Numbering association)
91 Assigned by seller or seller's agent
92 Assigned by buyer or buyer's agent
Consignee Occurrence 0 .. 1 This code is used to identify the address where the goods
Remark The delivery address in the header is valid for all items. are to be sent. For the supplier this address is where the
Indicating a consignee [ship-to] on the item level, which differs goods will be shipped (ship-to address).
from the consignee specified on the header level, is not The customer has to agree upfront with the supplier which
possible. are the concerned ship-to addresses for a given sold-to.
If the delivery address is not identical with the buyer address,
a consignee has to be sent. Exception: if a note in the
supplier's system indicates that the goods have always to be
delivered to another recorded address, then it is not necessary
to send a separate consignee.
xsd:sequence Occurrence 1 .. 1
PartyID Occurrence 1 .. 1
Length .. 17
Name Identification consignee/delivery address
AgencyCode Occurrence 1 .. 1 Condition: If AgencyCode is used then PartyID must be
Descr. Code identifying the agency responsible for a code list. used and vice versa.
Length .. 3
Name Type of the consignee's identification number.
Applicable Codes
9 EAN (International Article Numbering association)
91 Assigned by seller or seller's agent
92 Assigned by buyer or buyer's agent
PaymentTerms Occurrence 0 .. 1
Name Payment terms information
xsd:sequence Occurrence 1 .. 1
PaymentMethod Occurrence 1 .. 1 This functionality is not supported by all suppliers.
Length .. 10 In some European market’s, the customer might get a
Name Payment method different discount depending on the payment method. For
Descr. Identification of the method of payment. example paying cash at delivery, he could have a 2% extra
Remark In order to express that the normal payment method (by discount, or paying by a Visa card.
Invoice) is used the element (i.e. the element group) must not This option is supplier/customer dependent so before using
be used. this field, a preliminary bilateral agreement is required.

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 7/ 7
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

If not used, the supplier will apply the usual agreed payment
terms.
Applicable Codes
C Cash
K Credit Card
OrderLine Occurrence 1 .. unbounded
Name Line item information
Remark It should be checked with each supplier what the supported
maximum occurence is.
xsd:sequence Occurrence 1 .. 1
LineID Occurrence 1 .. 1
Length .. 6
Name Line identification number
Descr. Identification of a line in a document
PortalReference Occurrence 0 .. 1
Length .. 14
Name Portal Reference
Descr. Portal Reference
Remark For statistic purposes. Not yet to be used.
AdditionalCustomerReferenceNumber Occurrence 0 .. 1
Name Additional Customer's reference information
xsd:sequence Occurrence 1 .. 1
DocumentID Occurrence 1 .. 1 If the customer wants to have more references (ex. 4 tyres
Length .. 35 for Mr. Smith) by sending this to the supplier, the supplier
Descr. Customer’s reference to the business transaction on item can print this information on the delivery document. The
level. information in this field is not checked on the supplier side
and is taken there as a kind of free text.
OrderedArticle Occurrence 1 .. 1
Remark Article information
xsd:sequence Occurrence 1 .. 1
ArticleIdentification Occurrence 1 .. 1 The customer MUST send either the EAN code or the
Remark Normally the EAN is mandatory because it’s used as primary supplier product code. The reason for this is that the
key to identify the article on manufacturers side. In some supplier does not know the product code assigned by the
cases the suppliers article number must be used as primary customer. Nevertheless, if the customer wishes to send as
key (example: complete wheels) instead the EAN, but this well his product code, the supplier will store this number on
must be based on a bilateral agreement. the sales order, will print it on the delivery documents (on
request) and will return it in all subsequent EDI messages
(order confirmation, delivery, invoice).

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 8/ 8
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

Not supported by some manufacturers.

Before starting the electronic business, there has to be a

bilateral agreement between the customer and supplier
which codes will be used for article identification.
xsd:sequence Occurrence 1 .. 1
BuyersArticleID Occurrence 0 .. 1
Length .. 17
Name Buyer article number
Descr. Identification of the article, assigned by the buyer
ManufacturersArticleID Occurrence 0 .. 1
Length .. 35
Name Manufacturer's article number
Descr. Identification of the article, assigned by the manufacturer.
Remark A sent EAN number has priority compared with a
manufacturer assigned article number. If there is no EAN
number, then a manufacturer assigned article number is
mandatory.
EANUCCArticleID Occurrence 0 .. 1
Length .. 14
Name EANUCC Article number
Remark The use of any other number than the 13 digit GTIN (Global
Trade Item Number, known as EAN Number) has to be
agreed bilaterally.
xsd:sequence Occurrence 1 .. 1
RequestedDeliveryDate Occurrence 0 .. 1
Length .. 10
Pattern \d{4}-\d{2}-\d{2}
Name Requested delivery date
Descr. The meaning of the requested delivery date can vary from
supplier to supplier and from customer to customer.
Sometimes the customer has a contractual agreement with
the supplier to have planned delivery dates so the meaning of
the requested delivery date can change. In any case, before
implementing this message, contact your supplier to agree on
the exact meaning of this field.
RequestedQuantity Occurrence 1 .. 1

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 9/ 9
order_A2 XML - INDUSTRIAL SOLUTION
Description

Element/Attribute Annotation User Comments

xsd:sequence Occurrence 1 .. 1
QuantityValue Occurrence 1 .. 1
TotalDigits 15
Name Requested quantity
Remark Quantity must be larger than 0. No decimals are allowed.

Bold = Element, Italic = Attribute, Grey = Group

EDIWheel version 2010 Print date: 09.09.2010
Issue date: 01.07.2010 Page: 10 / 10