855 Po Acknowledgment

Ariba, Inc. cXML 1.
2: ANSI X12 004010 855 PO Acknowledgment Implementation Guidelines
855 Purchase Order Acknowledgment
Functional Group ID= PR

Introduction:
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order
Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI)
environment. The transaction set can be used to provide for customary and established business and industry
practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as
notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as
prearranged in their partnership.
Notes:
Ariba Network allows Suppliers to send Order Confirmations to Buyers in the form of the cXML
ConfirmationRequest.
As a service to Suppliers preferring to transact via EDI, Ariba Network accepts the ANSI X12 004010 855 Purchase
Order Acknowledgment document.
On receiving the 855 (documented here), Ariba Network validates the EDI content, returns a 997 to the Supplier,
and converts it to the cXML ConfirmationRequest. The final cXML document is internally posted to process the
actual order confirmation.
If an error arises at the application level, an email notification is sent to the Supplier, advising the failure and the
reason. Ariba Network does not currently implement the 824 Application Advice.
All separator characters within the ANSI X12 domain are allowed. You do not need to use the same separators that
you receive on your 850. The recommended separators are:
Segment Terminator: ~ (tilde)

Element Separator: * (asterisk)
Sub-Element Separator: > (greater than)
* Note that different VANs have different separator char requirements. They are usually modified in transit. These
three chars are always written to all inbound interchanges to Ariba Network by Sterling Commerce. Needless to say,
these three chars must not occur within your data itself.
On the returning 997, the following points should be noted.
Summary 997's are implemented, returning AK2/AK5 segments. Detailed 997's with AK3 and AK4 segments are
not supported at this time.
Interchanges are not acknowledged. Do not expect a TA1 segment. ISA14 should be set to 0, and is ignored.
AK5 acknowledgement codes:
- Code "A" constitutes acceptance. A cXML ConfirmationRequest was successfully prepared for submission to
Ariba Network. This only means that it cleared the EDI gateway -- not that it passed all business rules in Ariba
Network.
- Code "E" is an EDI Compliance error. If you receive this in an AK5, it means that the 810 was not converted and
did not make it past our EDI gateway.
- Code "R" represents total rejection. Ariba Network EDI does not currently implement this code.
Copyright (c) 1996–2014 Ariba, Inc. All rights reserved. 1 Revised 06 March 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 855 PO Acknowledgment Implementation Guidelines
AK9 acknowledgement codes:
- The above codes apply. Code "P" is possible if not all AK5's are code "A".
In reading this Implementation Guide, the following usage codes are used:
Status Segment Element

----------------------- ------------ -----------
Mandatory M M
Must Use Must Use M (Required)
Recommended R R
Dependant D D
Not Recommended NR NR
Not Used X X
Mandatory means that X12 says it is mandatory, so the guideline is bound by that rule.
Must Use means that X12 says it is optional, but Ariba Network requires it.
Recommended means that X12 says it is optional, and Ariba Network considers it optional, but recommends that it
be used.
Dependant means that X12 might have its usage dependant on other segments or elements, or by semantic notes, or
that Ariba Network describes semantics on which its dependency lies.
Not Recommended is the opposite of Recommended. The information may be technically allowed, but is probably
ignored.
Not Used segments and elements are not even shown in the guideline. In cases there they made need to be shown for
consistency, they are marked with an X.
Heading:
Page Pos. Seg. Base User Loop Notes and
No. No. ID Name Guide Status Max.Use Repeat Comments
4 010 ST Transaction Set Header M M 1
5 020 BAK Beginning Segment for Purchase Order M M 1
Acknowledgment
8 040 CUR Currency O 1
9 050 REF Reference O 3
10 080 FOB F.O.B. Related Instructions O 1
LOOP ID - SAC 2
12 120 SAC Service, Promotion, Allowance, or Charge O 1
Information
LOOP ID - SAC 22
Information
20 150 DTM Date/Time Reference - Acknowledgement O Must Use 1

Date
24 275 TXI Tax Information O 99
LOOP ID - N9 1
29 280 N9 Reference Identification - Comments O 1
31 290 MSG Message Text O 99
LOOP ID - N9 99
32 280 N9 Reference Identification - Extrinsic O 1
LOOP ID - N1 99
35 300 N1 Contact Information - Name O Rec 1
36 310 N2 Additional Name Information O 2
37 320 N3 Address Information O 2
38 330 N4 Geographic Location O 1
41 350 PER Administrative Communications Contact O 99
Detail:
LOOP ID - PO1 100000
44 010 PO1 Baseline Item Data O D 1 n1
46 040 CTP Pricing Information O 1
LOOP ID - PID 1000
48 050 PID Product/Item Description O 1
49 100 REF Reference – Multi Level Line Item O 1
LOOP ID - SAC 22
Information
LOOP ID - ACK 104

55 270 ACK Line Item Acknowledgment O Must Use 1
60 280 DTM Date/Time Reference O Rec 1
LOOP ID - N9 1
63 350 N9 Reference Identification - Comments O 1
LOOP ID - N1 99
66 370 N1 Name O 1
67 380 N2 Additional Name Information O 2
68 390 N3 Address Information O 2
69 400 N4 Geographic Location O 1
70 420 PER Administrative Communications Contact O 3
Summary:
LOOP ID - CTT 1
71 010 CTT Transaction Totals O Must Use 1 n2
72 020 AMT Monetary Amount O 1 n3
73 030 SE Transaction Set Trailer M M 1
Transaction Set Notes

1. PO102 is required.
2. The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total
(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
3. If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction
amount as calculated by the sender.
Segment: ST Transaction Set Header

Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g., 810
selects the Invoice Transaction Set).
Comments:
Notes: Example:
ST*855*0001~
produces...
<ConfirmationRequest>
Data Element Summary

Ref. Data Base User
Des. Element Name Attributes Attributes
ST01 143 Transaction Set Identifier Code M ID 3/3 M
Code uniquely identifying a Transaction Set
855 Purchase Order Acknowledgment
ST02 329 Transaction Set Control Number M AN 4/9 M
Identifying control number that must be unique within the transaction set functional group
assigned by the originator for a transaction set
Segment: BAK Beginning Segment for Purchase Order Acknowledgment

Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and
transmit identifying numbers and dates
Syntax Notes:
Semantic Notes: 1 BAK04 is the date assigned by the purchaser to purchase order.
2 BAK08 is the seller's order number.
3 BAK09 is the date assigned by the sender to the acknowledgment.
Comments:
Notes: Example:
BAK*00*AC*D-0115-1612h*20010111****ORDSP4125874*20010110~
produces...
<ConfirmationHeader confirmID="ORDSP4125874" operation="new" type="detail"
...>
...
</ConfirmationHeader>
<OrderReference orderID="DO364" orderDate="2000-04-15T08:39:52-0500">
<DocumentReference payloadID="original-order-payload-id" />
</OrderReference>
* The order number and order date supplied by BAK were combined with the buyer's id
and cross-referenced in the AN database. The complete orderDate and payloadID were
then retrieved and filled in.
Mapping target:
<ConfirmationHeader ...>
...
<OrderReference...>
Ariba Network supports multiple updates to order confirmations sent through EDI.
Note: Any subsequent updates to an already updated order confirmation must include the
previous order confirmation’s date and/or the confirmation ID.
Suppliers can send an update to an order confirmation using the DTM*636 in the DTM01 and
the REF*F8 in the REF01 segment to store the notice date and ID of the previous order
confirmation. Suppliers must also send the date of the newly updated order confirmation
using the DTM*ACK in the DTM01 segment.
Example of an updated order confirmation:
BAK*05*AE*PO123*20140105****OC2*20140107~
DTM*ACK*20140107*1010*ED~
DTM*636*20140106*1010*ED~
REF*F8*OC1~

Ref. Data Base User
BAK01 353 Transaction Set Purpose Code M ID 2/2 M
Code identifying purpose of transaction set
<ConfirmationHeader>
operation (new | update)
00 (Original) --> "new"

05 (Replace) --> "update"
00 Original
05 Replace
BAK02 587 Acknowledgment Type M ID 2/2 M
Code specifying the type of acknowledgment
type (accept | detail | except | reject) #REQUIRED
"AC" --> "detail", "AE" --> "except", "AT" --> "accept", "RJ" -->
"reject"
AC Acknowledge - With Detail and Change
type="detail"
A separate line item (PO1 group) is required in the 855 to confirm

each individual line item in the purchase order.
AE Acknowledge - With Exception Detail Only
type="except"
Very useful for large purchase orders with few exceptions. You
provide a PO1 group for each PO line item that is not accepted "as
is". (i.e. backordered, rejected, etc.) Any PO line item not
referenced with an 855 line item will be marked as "confirmed as
is".
Ack type AE with no line items is equivalent to ack type AT.

Ack type AE with all line items is equivalent to ack type AC.
AT Accepted
type="accept"
Sets the entire purchase order to confirmed "as is".
Line items (PO1 groups) are allowed in the 855, but the only
allowed status type is "accept" (ACK01="IA"). With this status
type, you may still fill in the shipment and delivery dates for
individual line items.
Every line item in the order will be set to confirmed, whether it has
a PO1 group in the 855 or not.
RJ Rejected - No Detail
type="reject"
Total rejection of the entire purchase order. This is the opposite of

ack type AT.
No line item (PO1 groups) are allowed in the 855, and every line
item in the PO will be marked as rejected.
You may use the N9 group to provide comments as to the reason

why, if you wish.
BAK03 324 Purchase Order Number M AN 1/22 M
Identifying number for Purchase Order assigned by the orderer/purchaser
Purchase Order Number, copied from the 850's BEG03
<OrderReference>
orderID %string; #IMPLIED
BAK04 373 Date M DT 8/8 O
Date expressed as CCYYMMDD
Purchase Order date, copied from the 850's BEG05
<OrderReference>
orderDate %datetime.tz; #IMPLIED
Note that only the date portion is available to be mapped.

BAK08 127 Reference Identification O AN 1/30 M
Reference information as defined for a particular Transaction Set or as specified by the
Reference Identification Qualifier
Supplier's order number. This is used for the confirmation identifier.
confirmID %string; #IMPLIED
BAK09 373 Date O DT 8/8 O
Order date is accepted, but is ignored. The required noticeDate for the acknowledgment is
preferred from DTM*ACK at 1/150 to allow complete date/time/zone specification.
Segment: CUR Currency

Position: 040
Loop:
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Syntax Notes: 1 If CUR08 is present, then CUR07 is required.
2 If CUR09 is present, then CUR07 is required.
3 If CUR10 is present, then at least one of CUR11 or CUR12 is required.
Semantic Notes:
Comments: 1 See Figures Appendix for examples detailing the use of the CUR segment.
Usage Notes: Used/Optional
Notes: Example: CUR*BY*USD~
produces...
<Total>
<Money currency="USD">
Mapping target:
<Total>
<Money>
currency %isoCurrencyCode; #REQUIRED

Ref. Data Base User
CUR01 98 Entity Identifier Code M ID 2/3 M
Code identifying an organizational entity, a physical location, property or an individual
BY Buying Party (Purchaser)
CUR02 100 Currency Code M ID 3/3 M
Code (Standard ISO) for country in whose currency the charges are specified
Segment: REF Reference

Position: 050
Loop:
Level: Heading
Usage: Optional
Max Use: 3
Purpose: To specify identifying information
Syntax Notes: 1 At least one of REF02 or REF03 is required.
2 If either C04003 or C04004 is present, then the other is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comments:
Notes: Example:
REF*IL*1234567~
REF*IV*INV34572~
produces...
<ConfirmationHeader ... invoiceID="INV34572">
* Note - REF*IL is used internally by the EDI system. It has no cXML counterpart.
Mapping target:
<ConfirmationHeader ...
invoiceID=REF02 where REF01="IV"
>
REF*F8*OC1~
OC1 is the ID of the previous order confirmation.

Ref. Data Base User
REF01 128 Reference Identification Qualifier M ID 2/3 M
Code qualifying the Reference Identification
IL Internal Order Number
Ariba Network Internal Order Number
This is the internal order number used by Ariba Network. It
positively and unambiguously identifies an order. A future version
of the 850 will supply this number which suppliers can simply
echo.
IV Seller's Invoice Number
If the supplier already has an invoice number assigned to the order,
F8 Original Reference Number
This is the identification number of previous order confirmation.
REF02 127 Reference Identification X AN 1/30 O
Segment: FOB F.O.B. Related Instructions

Position: 080
Loop:
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify transportation instructions relating to shipment
Syntax Notes: 1 If FOB03 is present, then FOB02 is required.
2 If FOB04 is present, then FOB05 is required.
Semantic Notes: 1 FOB01 indicates which party will pay the carrier.
2 FOB02 is the code specifying transportation responsibility location.
3 FOB06 is the code specifying the title passage location.
4 FOB08 is the code specifying the point at which the risk of loss transfers. This may
be different than the location specified in FOB02/FOB03 and FOB06/FOB07.
Comments:
Notes: Example: FOB*DE***01*CFR~
produces...
<ConfirmationHeader ... incoTerms="cfr" ...>

Ref. Data Base User
FOB01 146 Shipment Method of Payment M ID 2/2 M
Code identifying payment terms for transportation charges
DE Per Contract
Destination with exceptions as agreed between buyer and seller
FOB04 334 Transportation Terms Qualifier Code O ID 2/2 M
Code identifying the source of the transportation terms
01 Incoterms
FOB05 335 Transportation Terms Code X ID 3/3 M
Code identifying the trade terms which apply to the shipment transportation responsibility
The cXML incoTerms attribute requires that the code here be translated to lowercase. For
example:
incoTerms="cfr" where FOB05="CFR"
Mapping target:
<ConfirmationHeader ...
incoTerms=FOB05, translated
CFR Cost and Freight
Seller pays cost and freight to named port of destination; buyer
assumes all risks of loss and damage and additional costs incurred
once goods are delivered on board the vessel; these are assumed by
the buyer when the goods pass over the rail of the ship at the port of
shipment
CIF Cost, Insurance, and Freight
assumes all risks of loss and damage and additional costs incurred
once goods are delivered onboard the vessel; risks are assumed by
shipment; seller must in addition procure (i.e. contract and pay for)
marine insurance against the buyer's risk of loss or damage during
shipment
CIP Carriage and Insurance Paid To
assumes all risk of damage or loss and additional costs incurred once
goods are delivered on board the vessel; these risks are assumed by
shipment; seller must procure (i.e. contract and pay for) marine
insurance against the buyer's risk of loss or damage during carriage;
seller must in addition procure (i.e. contract and pay for) cargo
insurance against the buyer's risk of loss or damage to the goods
during carriage
CPT Carriage Paid To
Seller pays freight charges named to destination; the risk of loss or
damage to the goods, as well as any additional costs due to events
occurring after the time the goods have been delivered to other
carrier, is transferred from the seller to the buyer when the goods
have been delivered into the custody of the carrier
DAF Delivered at Frontier
Seller fulfills obligation to deliver when goods have been made
available, cleared for export, at the named point and place at the
frontier, but before the border of the adjoining country
DDP Delivered Duty Paid
Seller bears costs and risks involved in bringing goods to the named
place in the country of importation including duties, taxes, and other
official charges payable upon import
DDU Deliver Duty Unpaid
Seller bears costs and risks involved in bringing goods to the named
place in country of importation exclusive of duties, taxes, or other
official charges payable upon import, and the costs and risks of
carrying out import formalities
DEQ Delivered Ex Quay
Seller bears all costs and risks involved, including duties, taxes, and
other charges involved in delivering the goods to the quay (wharf) at
the named port of destination, cleared for import; seller's obligation
ends when the goods are available to the buyer on the quay (this term
used only for sea or inland waterway shipments)
DES Delivered Ex Ship
Seller bears all costs and risks involved in bringing goods to the
named port of destination; seller's obligation ends when goods are
available to buyer on board the ship uncleared for import at named
port of destination (this term used only for sea or inland waterway
shipments)
EXW Ex Works
Buyer bears all costs and risks in taking the goods from the seller's
premises to the desired location
FAS Free Alongside Ship
Seller's obligation ends when goods have been placed alongside the
vessel on the quay or in lighters at the named port of shipment; buyer
bears all costs and risks thereafter
FCA Free Carrier
Seller fulfills his obligation when goods are handed over, cleared for
export, and into the charge of the carrier named by the buyer at the
named place or location
FOB Free on Board
Segment: SAC Service, Promotion, Allowance, or Charge Information

Position: 120
Loop: SAC Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount
or percentage for the service, promotion, allowance, or charge
Syntax Notes: 1 At least one of SAC02 or SAC03 is required.
2 If either SAC03 or SAC04 is present, then the other is required.
5 If SAC11 is present, then SAC10 is required.
6 If SAC13 is present, then at least one of SAC02 or SAC04 is required.
Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
2 SAC05 is the total amount for the service, promotion, allowance, or charge.
If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
3 SAC08 is the allowance or charge rate per unit.
4 SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is
different from the purchase order or invoice quantity.
SAC10 and SAC11 used together indicate a quantity range, which could be a dollar
amount, that is applicable to service, promotion, allowance, or charge.
5 SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference
number as identified by the code used.
6 SAC14 is used in conjunction with SAC13 to identify an option when there is more
than one option of the promotion.
7 SAC16 is used to identify the language being used in SAC15.
Comments: 1 SAC04 may be used to uniquely identify the service, promotion, allowance, or
charge. In addition, it may be used in conjunction to further the code in SAC02.
2 In some business applications, it is necessary to advise the trading partner of the
actual dollar amount that a particular allowance, charge, or promotion was based on
to reduce ambiguity. This amount is commonly referred to as "Dollar Basis
Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -
Dollars in SAC09.

Ref. Data Base User
SAC01 248 Allowance or Charge Indicator M ID 1/1 M
Code which indicates an allowance or charge for the service specified
C Charge
SAC02 1300 Service, Promotion, Allowance, or Charge Code X ID 4/4 O
Code identifying the service, promotion, allowance, or charge
See specific examples and usage under SAC02, DE1300.
G830 Shipping and Handling
Example:
SAC*C*G830***4680********21428339882*FedEx*Fed-Ex 2
day*en~
produces...
<Shipping trackingDomain="FedEx"
trackingId="21428339882">
<Money currency="USD">46.80</Money>
<Description xml:lang="en">Fed-Ex 2 day</Description>
</Shipping>
Here the supplier states what the shipping charges for the order
will truly be. The buyer may have sent an SAC*C*G830 on the
PO, indicating the "expected" shipping charges. If the supplier
cannot honor that charge, then the corrected charge should appear
here. At any rate, whether the buyer stated an anticipated charge or
not, the supplier can advise the buyer what shipping charges they
"should" be expecting on the invoice.
Mapping target:
<Shipping trackingDomain=SAC14 trackingId=SAC13>

<Money currency=CUR02>SAC05</Money>
<Description xml:lang=SAC16>SAC15</Description>
</Shipping>
H850 Tax
Example:
SAC*C*H850***2718**********Total combined taxes*en~
produces...
<Tax>
<Description xml:lang="en">Total combined
taxes</Description>
</Tax>
* SAC13 and SAC14 are ignored.
Mapping target:
<Tax>
<Money currency=CUR02>SAC05</Money>
<Description xml:lang=SAC16>SAC15</Description>
</Tax>
SAC05 610 Amount O N2 1/15 O
Monetary amount
SAC13 127 Reference Identification X AN 1/30 O
SAC14 770 Option Number O AN 1/20 O
A unique number identifying available promotion or allowance options when more than
one is offered
When used with a shipping charge (SAC*C*G830), this represents the "tracking domain",
or namely an identification of the carrier. When specific strings are used to identify
carriers, Ariba Network renders on the online inbox a hyperlink to that carrier's online
tracking service.
The following strings are self-explanatory. When typed exactly into this element, the
carrier firm is "officially" recognized by Ariba Network.
Airborne Express
CF
DHL
EmeryWorldwide
FedEx
Purolator
Roadway Express
UPS
US Postal Service
Viking Freight
SAC15 352 Description X AN 1/80 M
A free-form description to clarify the related data elements and their content
SAC16 819 Language Code O ID 2/3 M
Code designating the language used in text, from a standard code list maintained by the
International Standards Organization (ISO 639)
Segment: SAC Allowances & Charges - Modifications

Position: 120
Loop: SAC Optional
Level: Heading
Usage: Optional
Max Use: 1
amount that is applicable to service, promotion, allowance, or charge.
Dollars in SAC09.
Notes: Example: SAC*N**ZZ*F050*2200**********Original Price*en~
CUR*BY*CAD~
SAC*A**ZZ*I530**6*5********Volume Discount*en~
CUR*BY*CAD*****196*20050504*101500*197*20050701*101500~
In the header section, this represents a modification in the order to the supplier. There can
be multiple modifications. Maximum number of modifications supported is 11. This is an
example of a modification in an order..
<Total>
<Money>……</Money>
<Modifications>
<Modification>
<OriginalPrice>
<Money currency="CAD">22.00</Money>
</OriginalPrice>
<AdditionalDeduction>
<DeductionPercent percent="5"/>
</AdditionalDeduction>
<ModificationDetail endDate="2005-07-01T10:15:00-08:00" name="Volume
Discount" startDate="2005-05-04T10:15:00-08:00">
<Description xml:lang="en-US">Volume Discount</Description>
</ModificationDetail>
</Modification>

Ref. Data Base User
C Charge
A Allowance
N No Allowance or Charge
SAC03 559 Agency Qualifier Code X ID 2/2 M
Code identifying the agency assigning the code values
ZZ Mutually Defined
SAC04 1301 Agency Service, Promotion, Allowance, or Charge M AN 1/10 M
Code
F050 Other
H970 Allowance
B660 Contract Allowance
C310 Discount
C300 Discount-Special
I530 Volume Discount
A040 Access Charge
A050 AccountNumberCorrectionCharge
A060 AcidBattery
A170 Adjustment
A960 Carrier
A520 Charge
D240 Freight
D180 FreightBasedOnDollarMinimum
D500 Handling
D980 Insurance
G580 Royalties
G821 Shipping
G830 ShippingAndHandling
SAC05 610 Amount O N2 1/15 M
Description: Monetary amount
OriginalPrice/Money (For Original Price)
AdditionalCost/Money (For Charge)
AdditionalDeduction/DeductionAmount/Money (For Allowances)
SAC06 378 Allowance/Charge Percent Qualifier X ID 1/1 O
Description: Code indicating on what basis allowance or charge percent is calculated
6 Price Based Amount
SAC07 332 Percent X R 1/6 O
Description: Percent expressed as a percent
Description: A unique number identifying available promotion or allowance options when
more than one is offered
1 Used if SAC05 value is amount
2 Used if SAC05 value is price

Description: A free-form description to clarify the related data elements and their content
Description: Code designating the language used in text, from a standard code list maintained
by the International Standards Organization (ISO 639)
<ModificationDetail endDate="2005-07-01T10:15:00-08:00" name="Volume Discount"
startDate="2005-05-04T10:15:00-08:00">

Position: 125
Loop: SAC Optional
Level: Heading
Usage: Optional
Max Use: 1
Semantic Notes:
Notes: Example 1: CUR*BY*USD~
Example 2: CUR*BY*CAD*****196*20050504*101500*197*20050701*101500~

Ref. Data Base User
See Note on Currency Codes with CUR [1/040].. Any ISO4217 code can be sent.
Currency codes shown here are examples. For more information on currency codes, see
http://www.unece.org/trade/rec/rec09en.htm
CAD Canadian Dollars
GBP British Pound
USD US Dollars
XEU European Monetary Coop Fund
CUR07 374 Date/Time Qualifier X ID 3/3 O
Description: Code specifying type of date or time, or both date and time
196 Start
CUR08 373 Date O DT 8/8 O
Description: Date expressed as CCYYMMDD
CUR09 337 Time O TM 4/8 O
Description: Time expressed in 24-hour clock time as follows:
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD, where H = hours (00-23), M =
minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds
are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
197 End
CUR11 373 Date X DT 8/8 O
CUR12 337 Time X TM 4/8 O
Segment: DTM Date/Time Reference - Acknowledgement Date

Position: 150
Loop:
Level: Heading
Usage: Optional (Must Use)
Max Use: 1
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 DTM03 is required.
2 If DTM04 is present, then DTM03 is required.
Semantic Notes:
Comments:
Usage Notes: Mandatory
Notes: Example:
DTM*ACK*20000415*0830*ED~
produces...
<ConfirmationHeader ... noticeDate="2000-04-15T08:30:00-0400" ...>
* DTM04="ED" represents Eastern Daylight Time, which is UTC-0400
DTM*004*20000415*0830*ED~
produces...
<OrderReference>
orderDate="2000-04-15T08:30:00-0400"..
Specify the Acknowledgement notice date here. The noticeDate attribute is required in
the cXML <ConfirmationHeader>. This is simply the date you are acknowledging the
order.
Note that a complete date/time/zone is recommended. Timestamps in cXML are

represented as a date with a time, and an offset to UTC. If you do not specify a time, it
may be taken as midnight on the date specified. If you do not specify the time code
(zone), then it may be defaulted.
Mapping target:
DTM*ACK maps to
<ConfirmationHeader
noticeDate %datetime.tz; #REQUIRED
= DTM02 + DTM03 + DTM04 where DTM01 = "ACK"
>
DTM*004 maps to
<OrderReference>
orderDate=%datetime.tz; #REQUIRED
DTM*636*20140106*1010*ED~
Specify the notice date of the previous order confirmationhere.
<ConfirmationHeader
noticeDate %datetime.tz; #REQUIRED>

Ref. Data Base User
DTM01 374 Date/Time Qualifier M ID 3/3 M
Code specifying type of date or time, or both date and time
004 Purchase Order
ACK Acknowledgment
636 Date of last update
DTM02 373 Date X DT 8/8 M
DTM03 337 Time X TM 4/8 R
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD,
or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-
59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9)
and DD = hundredths (00-99)
DTM04 623 Time Code O ID 2/2 R
Code identifying the time. In accordance with International Standards Organization
standard 8601, time can be specified by a + or - and an indication in hours in relation to
Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are
substituted by P and M in the codes that follow
Note that the LT code is not available. This is because Ariba Network does not currently
have a way to make a context-sensitive assumption on the time zone.
The ISO codes are favorable because you have direct control over the output, but they do
not support half hour zones as in Newfoundland. (If you need Newfoundland time, NS &
NT map to -0330, ND maps to -0230)
01 Equivalent to ISO P01
="+01:00"
="+02:00"
="+03:00"
="+04:00"
="+05:00"
="+06:00"
="+07:00"
="+08:00"
="+09:00"
="+10:00"
="+11:00"
="+12:00"
13 Equivalent to ISO M12
="-12:00"
="-11:00"
="-10:00"
="-09:00"
="-08:00"
="-07:00"
="-06:00"
="-05:00"
="-04:00"
="-03:00"
="-02:00"
="-01:00"
AD Alaska Daylight Time
="-08:00"
AS Alaska Standard Time
="-09:00"
AT Alaska Time
="-09:00"
CD Central Daylight Time
="-05:00"
CS Central Standard Time
="-06:00"
CT Central Time
="-06:00"
ED Eastern Daylight Time
="-04:00"
ES Eastern Standard Time
="-05:00"
ET Eastern Time
="-05:00"
GM Greenwich Mean Time
="+00:00"
HD Hawaii-Aleutian Daylight Time
="-10:00"
HS Hawaii-Aleutian Standard Time
="-10:00"
HT Hawaii-Aleutian Time
="-10:00"
MD Mountain Daylight Time
="-06:00"
MS Mountain Standard Time
="-07:00"
MT Mountain Time
="-07:00"
ND Newfoundland Daylight Time
="-02:30"
NS Newfoundland Standard Time
="-03:30"
NT Newfoundland Time
="-03:30"
PD Pacific Daylight Time
="-07:00"
PS Pacific Standard Time
="-08:00"
PT Pacific Time
="-08:00"
TD Atlantic Daylight Time
="-03:00"
TS Atlantic Standard Time
="-04:00"
TT Atlantic Time
="-04:00"
UT Universal Time Coordinate
="Z" or "-00:00"
This is Coordinated Universal Time, or UTC. The correct ISO

zone extension for UTC is simply Z. However this release of
Ariba Network does not support Z, so it renders as "-00:00", to
distinguish it from GMT which uses "+00:00".
Segment: TXI Tax Information

Position: 275
Loop:
Level: Heading
Usage: Optional
Max Use: 99
Purpose: To specify tax information
Syntax Notes: 1 At least one of TXI02 TXI03 or TXI06 is required.
2 If either TXI04 or TXI05 is present, then the other is required.
3 If TXI08 is present, then TXI03 is required.
Semantic Notes: 1 TXI02 is the monetary amount of the tax.
2 TXI03 is the tax percent expressed as a decimal.
3 TXI07 is a code indicating the relationship of the price or amount to the associated
segment.
Comments:
Notes: TXI is used to supply <TaxDetail> to accompany <Tax> defined in SAC (1/120), where
SAC01="C" and SAC02="H850".
If TXI is used, then SAC*C*H850 @1/120 is required.
<TaxDetail> has four attributes: purpose, category, percentageRate, and

isVatRecoverable. In Ariba Network, purpose="tax" and category is one of "sales", "gst",
"vat", or "other". percentage captures TXI03 and isVatRecoverable is not mapped.
How TXI is used is that all TXI01 codes are allowed. A many to one mapping is
performed on TXI01 to the four category values cited:
"sales": CS, CP, LT, SU, ST

"gst": CG, CV, GS
"vat": VA
"other": everything else
The jurisdiction code must be assigned by the supplier and is captured by

<TaxLocation>. The final <Description> is not offered by TXI, so it captures the X12
description for the TXI01 code.
Example:
TXI*ST*4538*8.25*VD*California***550~
TXI*HZ*962*1.75*VD*California***550~
produces...
<TaxDetail purpose="tax" category="sales" percentageRate="8.25">

<TaxableAmount>
<Money currency="USD">550</Money>
</TaxableAmount>
<TaxAmount>
</TaxAmount>
<TaxLocation>California</TaxLocation>
<Description xml:lang="en">State Sales Tax</Description>
</TaxDetail>
<TaxDetail purpose="tax" category="other" percentageRate="1.75">
<TaxableAmount>
<Money currency="USD">550</Money>
</TaxableAmount>
<TaxAmount>
</TaxAmount>
<TaxLocation>California</TaxLocation>
<Description xml:lang="en">Hazardous Waste Tax</Description>
</TaxDetail>
* Note that TXI01=TX implies "All Taxes", so if used should be alone.
Mapping target:
<TaxDetail purpose="tax" category=(sales | gst | vat | other)

percentageRate=TXI03 isVatRecoverable=(not mapped)>
<TaxableAmount>
<Money currency=CUR02>TXI08</Money>
</TaxableAmount>
<TaxAmount>
<Money currency=CUR02>TXI02</Money>
</TaxAmount>
<TaxLocation xml:lang=(defaulted)>TXI05</TaxLocation>
<Description xml:lang=(defaulted)>(Description of TXI01 code
from X12 standard)</Description>
</TaxDetail>

Ref. Data Base User
TXI01 963 Tax Type Code M ID 2/2 M
Code specifying the type of tax
AA Stadium Tax
AB Surtax
AT Assessment
BP Business Privilege Tax
Tax imposed on non-American Indian businesses for the privilege of
conducting business on an American Indian reservation
CA City Tax
Service Tax imposed by City
CB Threshold Tax
CG Federal Value-added Tax (GST) on Goods
CI City Rental Tax
Levied by a city government against the periodic fee paid by a
customer in return for the right to use the property of another party
CP County/Parish Sales Tax
CR County Rental Tax
Levied by a county government against the periodic fee paid by a
CS City Sales Tax
CT County Tax
CV Federal Value-added Tax (GST) on Services
DL Default Labor Tax
EQ Equipment Tax
ET Energy Tax
Tax applied to the utility and petroleum industries
EV Environmental Tax
F1 FICA Tax
F2 FICA Medicare Tax
F3 FICA Social Security Tax
FD Federal Tax
Usage tax imposed by federal (US and Canadian) government
FF Fuel Super Fund Tax
FI Federal Income Tax Withholding
FL Fuel L.U.S.T. Tax (Leaking Underground Storage Tank)
FR Franchise Tax
Tax imposed by municipality for the right to provide service
FS Fuel Spill Tax
FT Federal Excise Tax
GR Gross Receipts Tax
GS Goods and Services Tax
Canadian value-added tax
HS Public Health and Education Tax
Canadian tax levied to fund public care and education
HT Handicap Tax
Tax assessed to assist the handicapped
HZ Hazardous Waste Tax
LB Labor By Trade Tax
LO Local Tax (Not Sales Tax)
Service tax imposed on a local level
LS State and Local Sales Tax
LT Local Sales Tax (All Applicable Sales Taxes by Taxing Authority
Below the State Level)
LU Leaky Underground Storage Tank (LUST) Tax (federal)
Leaky Underground Storage Tank (LUST) Tax (federal); tax
imposed in the U.S., at the federal level, for clean-up of leaky
underground storage tanks
LV Leaky Underground Storage Tank (LUST) Tax (state)
Leaky Underground Storage Tank (LUST) Tax (state); tax imposed
in the U.S., at the state level, for clean-up of leaky underground
storage tanks
MA Material Tax
MN Minimum Tax
MP Municipal Tax
Service tax imposed by a municipality
MS Miscellaneous State Tax
MT Metropolitan Transit Tax
OH Other Taxes
OT Occupational Tax
Tax imposed on telecommunication companies for the right to
provide service
PG State or Provincial Tax on Goods
PS State or Provincial Tax on Services
SA State or Provincial Fuel Tax
SB Secondary Percentage Tax
SC School Tax
Tax collection by taxing authority for schools
SE State Excise Tax
Usage tax imposed by state of provincial government
SF Superfund Tax
Superfund is a U.S. government fund created for the clean up or
eradication of sites at which toxic waste, hazardous to the
environment, has been dumped
SL State and Local Tax
State and Local tax funds, exclusive of State and Local Sales tax
SP State/Provincial Tax
State tax levied which excludes sales or excise taxes
SR State Rental Tax
Levied by a state government against the periodic fee paid by a
SS State Tax on Specific Labor
ST State Sales Tax
SU Sales and Use Tax
Tax on Equipment and Service provided
SX Enhanced 911 - State Excise Tax
A tax imposed to pay for enhanced 911 services such as automatic
call identification
T1 Pre-threshold Tax
T2 Post Threshold Tax
TD Telecommunications Device for the Deaf (TDD) Service Excise Tax
Tax imposed to recover the cost of providing TDD equipment
TT Telecommunications Tax
Tax imposed on telecommunications companies for the right to
provide service or usage tax imposed. (This could be an excise tax)
TX All Taxes
Total of all applicable taxes
UL License Tax
Tax used to report the amount of license tax which is passed to the
consumer
UT Utility Users' Tax
City or county tax for natural gas usage that is imposed upon
customers
VA Value Added Tax
WS Well Service
ZA 911-City Tax
Tax levied to recover the cost of providing 911 emergency services
within a city
ZB 911-County Tax
Tax levied to recover the cost of providing 911 emergency service
within a county
ZC 911-Excise Tax
Usage tax imposed to recover the cost of 911 service
ZD 911-State Tax
Tax levied to recover the cost of providing 911 emergency service
within a State
ZE 911-Tax
Tax to recover the cost of 911 service
ZZ Mutually Defined
TXI02 782 Monetary Amount X R 1/18 M
Monetary amount
TXI03 954 Percent X R 1/10 O
Percentage expressed as a decimal
TXI04 955 Tax Jurisdiction Code Qualifier X ID 2/2 O
Code identifying the source of the data used in tax jurisdiction code
Refer to 004010 Data Element Dictionary for acceptable code values.
TXI05 956 Tax Jurisdiction Code X AN 1/10 O
Code identifying the taxing jurisdiction
TXI08 828 Dollar Basis For Percent O R 1/9 O
Dollar basis to be used in the percent calculation of the allowance, charge or tax
Segment: N9 Reference Identification - Comments

Position: 280
Loop: N9 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To transmit identifying information as specified by the Reference Identification Qualifier
Syntax Notes: 1 At least one of N902 or N903 is required.
2 If N906 is present, then N905 is required.
Semantic Notes: 1 N906 reflects the time zone which the time reflects.
2 N907 contains data relating to the value cited in N902.
Comments:
Notes: Example:
N9*L1*en*Comments~
MSG*Be sure printer ink cartridges are properly sealed to avoid spillage.~
produces...
<ConfirmationHeader ...>
...
<Comments xml:lang="en">Be sure printer ink cartridges are properly sealed to avoid
spillage.</Comments>
Multiline comments are also possible. For intentional linefeeds, simply use multiple
MSG segments. If you need a single comment line longer than 264 chars, use another
MSG with MSG02="LC".
N9*L1*en-CA*Comments~
MSG*Fountain pens are on special next month.~
MSG*Several popular brands are available,~
MSG*along with various colours of ink.*LC~
MSG*Supplies are limited.~
produces...
<Comments xml:lang="en-CA">Fountain pens are on special next month.

Several popular brands are available, along with various colours of ink.
Supplies are limited</Comments>
N902 is taken to be a language code. This must a two char ISO 639 language code
optionally followed by a dash and a two char ISO 3166 country code.
Some examples...
"en" English
"en-US" American English
"en-GB" British English
"es" Spanish
"fr" French
"fr-CA" Canadian French
(Text from ANSI X12 is interpreted by Ariba Network to be ISO-8859-1, but chars above
7-bit ASCII may not relay with integrity across Value Added Networks. If you need this
kind of support in EDI, you might consider using EDIFACT.)
Mapping target:
<Comments xml:lang=N902>MSG01
MSG01</Comments>

Ref. Data Base User
N901 128 Reference Identification Qualifier M ID 2/3 M
L1 Letters or Notes
N902 127 Reference Identification X AN 1/30 R
Language code of the comments.
N903 369 Free-form Description X AN 1/45 M

Free-form descriptive text
Always set to "Comments". Since the language code is Recommended, but Optional, this
constant guarantees that either N902 or N903 is filled.
Application Value List:

Comments
Segment: MSG Message Text

Position: 290
Loop: N9 Optional
Level: Heading
Usage: Optional
Max Use: 99
Purpose: To provide a free-form format that allows the transmission of text information
Syntax Notes: 1 If MSG03 is present, then MSG02 is required.
Semantic Notes: 1 MSG03 is the number of lines to advance before printing.
Comments: 1 MSG02 is not related to the specific characteristics of a printer, but identifies top of
page, advance a line, etc.
2 If MSG02 is "AA - Advance the specified number of lines before print" then MSG03
is required.
Notes: Example: MSG*Be sure printer ink cartridges are properly sealed to avoid spillage.~
The actual comment text. You should generate a new MSG segment for each comment
line, to help preserve context and form. If you need more than 264 chars for a line, then
word break and start a new MSG segment, setting MSG02 in the new segment to "LC".
Mapping target:
<Comments>
#PCDATA

Ref. Data Base User
MSG01 933 Free-Form Message Text M AN 1/264 M
Free-form message text
MSG02 934 Printer Carriage Control Code X ID 2/2 O
A field to be used for the control of the line feed of the receiving printer
Set to "LC" if you mean to continue a comment line that has overflowed a previous MSG
segment. If you need comment lines longer than 264 chars, then you should consider
reformatting into multiple lines.
LC Line Continuation
Segment: N9 Reference Identification - Extrinsic

Position: 280
Loop: N9 Optional
Level: Heading
Usage: Optional
Max Use: 1
Comments:
Notes: Example 1 - Simple data with N902:
N9*ZZ*Critical*Order Priority~
produces...
<Extrinsic name="Order Priority">Critical</Extrinsic>
Example 2 - Multiline text with MSG:
N9*ZZ**Bragging~
MSG*Our product is the original; the one and only...~
MSG*Accept no substitutes!~
produces...
<Extrinsic name="Bragging">Our product is the original; the one and only...

Accept no substitutes!</Extrinsic>
* In this example, N902 need not be used. Multiple lines may be rendered on the output
by simply using multiple MSG segments. Each MSG produces a new line in the cXML
output. If N902 is used with MSG, then N902 simply occupies the first line, as in the
following example.
Example 3 - N902 with MSG:
N9*ZZ*2% net 10*Payment Terms~

MSG*When you get the invoice, consider a 2% discount if you pay it within 10 days.~
MSG*But remember, if you take more than 30 days, we start charging you interest!~
produces...
<Extrinsic name="Payment Terms">2% net 10

When you get the invoice, consider a 2% discount if you pay it within 10 days.
But remember, if you take more than 30 days, we start charging you interest!</Extrinsic>
* In this example, the implementer has cleverly used N902 to act as a pre-agreeded upon
payment terms code, and then added the verbal comments. When used in combination,
N902 simply occupies the first line, and a line feed separates it from the first MSG text.
Nothing more.
While it would be highly unusual to extend a line beyond the width of MSG01, it is
supported. Simply set MSG02="LC" to suppress a line feed.
Extrinsics are used in cXML as additional parameters you need to insert into the
document, but which are not otherwise supported in cXML. This general implementation
is provided in EDI to directly map into cXML's Extrinsic elements.
You should abstain from using this feature unless it is necessary. Names of individuals
involved in handling your order should be identified in the N1 Contacts section wherever
possible.
Mapping target:
<Extrinsic name=N903>N902
MSG01</Extrinsic>
* If MSG is added when N902 is present, then N902 forms the first
line of a multi-line piece of text. A line feed is added to
separate them.

Ref. Data Base User
ZZ Mutually Defined
N902 127 Reference Identification X AN 1/30 O
Optional short piece of data for the Extrinsic.
<Extrinsic>
name %string #REQUIRED
Required name attribute of the Extrinsic.

Extrinsic

Position: 290
Loop: N9 Optional
Level: Heading
Usage: Optional
Max Use: 99
is required.
Notes: See examples on usage with N9.

Ref. Data Base User
Segment: N1 Contact Information - Name

Position: 300
Loop: N1 Optional (Recommended)
Level: Heading
Usage: Optional (Recommended)
Max Use: 1
Purpose: To identify a party by type of organization, name, and code.
The documentation and usage here has been greatly simplied. You can supply as much or
as little contact information as you like. The same "role" however (N101), cannot be used
on both header and line item levels.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104) must
provide a key to the table maintained by the transaction processing party.
2 N105 and N106 further define the type of entity in N101.
Usage Notes: Recommended
Notes: Example: N1*SU*The Supplier~
This section of N1 allows for detailed contact information. There is no reason to copy any
of the contact information from the purchase order, unless the supplier wishes to send it.
This should represent supplier related contact information for the buyer's reference.
The <PostalAddress> structure is built from segments N2, N3, and N4. <PostalAddress>
is optional in itself. If used, then at least one N3 is required, along with N401 and N404.
If N404="US" or "CA", then N402 is required.
If you are entering a Postal Address, the <PostalAddress> structure in cXML mandates at
least one <Street>, a <City> and a <Country>. Therefore, N3 and N4 become mandatory.

Ref. Data Base User
N101 98 Entity Identifier Code M ID 2/3 M
60 Salesperson
Identification of individual that sold the product e.g. SSN,
salesperson id, etc.
A9 Sales Office
A business entity whose main activity is, or a location at which, the
sale of goods or services takes place
BT Bill-to-Party
KY Technical Office
RI Remit To
SF Ship From
ST Ship To
SU Supplier/Manufacturer
N102 93 Name X AN 1/60 M
Free-form name
Name is optional, but it is recommended.
Segment: N2 Additional Name Information

Position: 310
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify additional names or those longer than 35 characters in length
Syntax Notes:
Semantic Notes:
Comments:
Notes: Example:
N2*Andrea Walsh*National Account Manager~

N2*Supplier Corporation~
Each DE0093 produces one <DeliverTo> in a <PostalAddress>. They are translated in

the sequence: N201, N202, N201, N202. A maximum of four <DeliverTo> elements can
be generated.
Within a <PostalAddress>, <DeliverTo> is supposed to represent specific recipient

name(s) of a package or envelope. This may also include intra-office routing information,
such as a department, a floor, office, or cube number.
Use of <DeliverTo> is entirely optional.
<Contact>
<PostalAddress>
<DeliverTo>

Ref. Data Base User
N201 93 Name M AN 1/60 M
Free-form name
N202 93 Name O AN 1/60 O
Free-form name
Segment: N3 Address Information

Position: 320
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Notes: Example: N3*One Supplier Blvd.~
produces...
<Street>One Supplier Blvd.</Street>
Each DE0166 produces one <Street> in a <PostalAddress>. They are translated in the
sequence: N301, N302, N301, N302. A maximum of four <Street> elements can be
generated.
Within a <PostalAddress>, <Street> is supposed to be used by the postal service or

courier. It should include an address to the resolution of a building or an office suite.
A recommendation is to use <Street> as far as outside carriers would deliver it, and then
use <DeliverTo> for the internal delivery.
If you are building a <PostalAddress> then at least one <Street> is required.
<Contact>
<PostalAddress>
<Street>

Ref. Data Base User
N301 166 Address Information M AN 1/55 M
Address information
N302 166 Address Information O AN 1/55 O
Address information
Segment: N4 Geographic Location

Position: 330
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to
specify a location.
2 N402 is required only if city name (N401) is in the U.S. or Canada.
Notes: Example: N4*Portland*OR*97220*US~
produces...
<PostalAddress>
...
<City>Portland</City>
<State>OR</State>
<PostalCode>97220</PostalCode>
<Country isoCountryCode="US">UNITED STATES</Country>
</PostalAddress>
If you are building a <PostalAddress> then <City> and <Country> are required, hence
N4 is required.

Ref. Data Base User
N401 19 City Name O AN 2/30 M
Free-form text for city name
<Contact>
<PostalAddress>
<City>
N402 156 State or Province Code O ID 2/2 R
Code (Standard State/Province) as defined by appropriate government agency
For addresses in the United States or Canada, use the two letter digraph recognized by the
United States Postal Service or Canada Post.
Official State and Territory codes are published by the US Postal Service here:
http://www.usps.gov/ncsc/lookups/abbr_state.txt
All codes for US and Canada are listed here for convenience.
Ariba Network may fail a document if N402 and N404 contradict.
<Contact>
<PostalAddress>
<State>
AB Alberta
AK Alaska
AL Alabama
AR Arkansas
AS American Samoa
AZ Arizona
BC British Columbia
CA California
CO Colorado
CT Connecticut
DC District of Columbia
DE Delaware
FL Florida
FM Federated States of Micronesia
GA Georgia
GU Guam
HI Hawaii
IA Iowa
ID Idaho
IL Illinois
IN Indiana
KS Kansas
KY Kentucky
LA Louisiana
MA Massachusetts
MB Manitoba
MD Maryland
ME Maine
MH Marshall Islands
MI Michigan
MN Minnesota
MO Missouri
MP Northern Mariana Islands
MS Mississippi
MT Montana
NB New Brunswick
NC North Carolina
ND North Dakota
NE Nebraska
NF Newfoundland
NH New Hampshire
NJ New Jersey
NM New Mexico
NS Nova Scotia
NT Northwest Territories
NU Nunavut
NV Nevada
NY New York
OH Ohio
OK Oklahoma
ON Ontario
OR Oregon
PA Pennsylvania
PE Prince Edward Island
PR Puerto Rico
PW Palau
QC Quebec
RI Rhode Island
SC South Carolina
SD South Dakota
SK Saskatchewan
TN Tennessee
TX Texas
UT Utah
VA Virginia
VI Virgin Islands
VT Vermont
WA Washington
WI Wisconsin
WV West Virginia
WY Wyoming
YT Yukon
N403 116 Postal Code O ID 3/15 O
Code defining international postal zone code excluding punctuation and blanks (zip code
for United States)
Zip codes will be either five or nine digits with no separator. Canadian postal codes must
be formatted A9A9A9, with no separator.
Ariba Network may validate a Zip/Postal code to correspond to the State or Province code
in N402, if N404="US" or "CA", and cause the document to fail if it is obviously wrong.
<Contact>
<PostalAddress>
<PostalCode>
N404 26 Country Code O ID 2/3 M ID 2/2
Code identifying the country
Country code is ISO-3166 compliant, and must be a two char digraph. You can see a list
here along with their respective currency codes:
If N404 is "US" or "CA", then N402 is required.
<Contact>
<PostalAddress>
<Country>
isoCountryCode %isoCountryCode; #REQUIRED
Segment: PER Administrative Communications Contact

Position: 350
Level: Heading
Usage: Optional
Max Use: 99
Purpose: To identify a person or office to whom administrative communications should be
directed.
Since all contacts at this level are under the parent N1, which defines the overall contact
role, we only use PER01="CN" for general contact here.
Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
Semantic Notes:
Comments:
Notes: Example:
PER*CN*Help Desk*EM*helpdesk@thesupplier.org*TE*1-888-555-4321~
PER*CN*Billing Inquiries*TE*1 (800) 5551234 x7890*EM*billing@thesupplier.org~
produces...
<Email name="Help Desk">helpdesk@thesupplier.org</Email>

<Email name="Billing Inquiries">billing@thesupplier.org</Email>
<Phone name="Help Desk">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>888</AreaOrCityCode>
<Number>555-4321</Number>
</TelephoneNumber>
</Phone>
<Phone name="Billing Inquiries">
<TelephoneNumber>
<CountryCode isoCountryCode="US">1</CountryCode>
<AreaOrCityCode>800</AreaOrCityCode>
<Number>5551234</Number>
<Extension>7890</Extension>
</TelephoneNumber>
</Phone>
Some important things need to be noted from the above example:
1. In some documents, PER is a limited resource, allowing only 3 iterations, with 3

communications contacts in each one. PER sorts by name then type. cXML sorts by type
and then name, so they get rearranged. They will all be collected and sorted out.
2. It is not necessary to fill all three contacts in PER, and PER02 is allowed to repeat.
3. Telephone numbers have to be intelligently broken. The <TelephoneNumber>

structure imposed by cXML is mandatory. Therefore, it is imperative that phone and fax
numbers be correctly written, or else the break algorithm will probably misinterpret them.
Here are some *very important* recommendations in writing out phone numbers for
correct rendering:
(a) Always start with the correct country code. NANP (North American Numbering Plan)
numbers always begin with '1'. The break algorithm may be tolerant enough to assume
that ten digits not starting with 1 or 0 is in NANP.
(b) If you dial 9 for an outside line, do not include it here. Remember that country code
91 is India.
(c) A leading + (plus) sign is allowed.
(d) Separator characters, such as spaces or dashes, or brackets around the area code have
influence on the break algorithm. Separators are not required, (you may send raw digits),
but they do help to mark off the different sections.
(e) An 'x' preceding an extension has the effect of segregating the trailing text as an
extension.
(f) isoCountryCode resolution is done from the leading telephone country code. If it is 1
for NANP, then the following rules are used:
- i) If the AreaOrCityCode is known, then imply the country from that.

- ii) If N404 is present, then use N404.
- iii) Use the supplier default country code in Ariba Network.
- iv) Default "US" if still indeterminate.
<(Email | Phone | Fax | URL) name=PER02>

DE0364
<Email> if DE0365="EM", <Phone> if DE0365="TE", <Fax> if

DE0365="FX", <URL> if DE0365="UR"

Ref. Data Base User
PER01 366 Contact Function Code M ID 2/2 M
Code identifying the major duty or responsibility of the person or group named
CN General Contact
PER02 93 Name O AN 1/60 O
Free-form name
PER03 365 Communication Number Qualifier X ID 2/2 O

Code identifying the type of communication number
EM Electronic Mail
FX Facsimile
TE Telephone
UR Uniform Resource Locator (URL)
PER04 364 Communication Number X AN 1/80 O
Complete communications number including country or area code when applicable
EM Electronic Mail
FX Facsimile
TE Telephone
EM Electronic Mail
FX Facsimile
TE Telephone
Segment: PO1 Baseline Item Data

Position: 010
Loop: PO1 Optional (Dependent)
Level: Detail
Usage: Optional (Dependent)
Max Use: 1
Purpose: To specify basic and most frequently used line item data
Syntax Notes: 1 If PO103 is present, then PO102 is required.
2 If PO105 is present, then PO104 is required.
3 If either PO106 or PO107 is present, then the other is required.
Semantic Notes:
Comments: 1 See the Data Element Dictionary for a complete list of IDs.
2 PO101 is the line item identification.
3 PO106 through PO125 provide for ten different product/service IDs per each item.
For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Usage Notes: Dependant
Notes: Example: PO1*5*25*RO*4.19~
produces...
...
<ConfirmationItem quantity="25" lineNumber="5">
<UnitOfMeasure>D65</UnitOfMeasure>
* PO103 goes through a translation table to convert it to the ISO Unit of Measure code
required by cXML.
In the Confirmation, we use the first three elements, which must be exact copies of their
respective counterparts from the Purchase Order. You must reference the Line Item's
"Assigned Identification" as well as the original quantity that was ordered, along with the
unit of measure. Then use the ACK group to make your amendments.
PO104 is optional, as it has no counterpart in cXML. If you use it, then it should be a
copy of PO104 from the purchase order line.
A change in unit price is done with a single occurrence of CTP @2/040.
Mapping target:
<ConfirmationItem quantity=PO102 lineNumber=PO101>

<UnitOfMeasure>PO103 (translated)</UnitOfMeasure>

Ref. Data Base User
PO101 350 Assigned Identification O AN 1/20 M
Alphanumeric characters assigned for differentiation within a transaction set
Must match counterpart line number from 850. To reference a specific line item in the
Purchase Order, you must copy the exact value of PO101 from the line of the 850 you are
confirming. In cXML, this value is numeric.
<ConfirmationItem>
lineNumber %uint; #REQUIRED
PO102 330 Quantity Ordered X R 1/15 M
Quantity ordered
Total amount that the Buyer ordered. This must be an exact copy of its counterpart from the
850.
PO103 355 Unit or Basis for Measurement Code O ID 2/2 M
Code specifying the units in which a value is being expressed, or manner in which a
measurement has been taken
Must be an exact copy of its counterpart in the 850's line item.
PO104 212 Unit Price X R 1/17 O
Price per unit of product, service, commodity, etc.
PO104 may optionally be used to echo the unit price from the purchase order, but it is not
captured. To make a change to the unit price, you must use the CTP segment at 2/040.
PO106 235 Product/Service ID Qualifier X ID 2/2 O
Code identifying the type/source of the descriptive number used in Product/Service ID
(234)
C3 Classification
MF Manufacturer
MG Manufacturer's Part Number
VP Vendor's (Seller's) Part Number
PO107 234 Product/Service ID X AN 1/48 O
Identifying number for a product or service
(234)
C3 Classification
MF Manufacturer
(234)
C3 Classification
MF Manufacturer
(234)
C3 Classification
MF Manufacturer
Segment: CTP Pricing Information

Position: 040
Loop: PO1 Optional (Dependent)
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify pricing information
Syntax Notes: 1 If either CTP04 or CTP05 is present, then the other is required.
2 If CTP06 is present, then CTP07 is required.
Semantic Notes: 1 CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90
would be the factor if a 10% discount is given.
2 CTP08 is the rebate amount.
Comments: 1 See Figures Appendix for an example detailing the use of CTP03 and CTP04.
See Figures Appendix for an example detailing the use of CTP03, CTP04 and
CTP07.
Notes: Example:
CTP*AS*CHG*4.10~
produces...
<ConfirmationStatus ...>
...
<UnitPrice>
</UnitPrice>
CTP*AS*CUP*5.12~
produces...
...
<ItemIn ...>
....
<UnitPrice>
</UnitPrice>
CTP is used here to show a changed unit price. The value of CTP03 would be expected to
be different from PO104.
CUP is used to show a confirmed unit price and should be used only when there is a part
number change. The value of CTP03 would be expected to be different from PO104.
IMPORTANT! In cXML, the adjusted Unit Price must be written to the

ConfirmationStatus (ACK level). Therefore, if you have multiple ACK groups, each one
will copy the new Unit Price.
When CTP*AS*CUP is present VP, PD and C3 qualifiers are mandatory

in ACK segment and vice versa.

Ref. Data Base User
CTP01 687 Class of Trade Code O ID 2/2 M
Code indicating class of trade
AS Seller
CTP02 236 Price Identifier Code X ID 3/3 M
Code identifying pricing specification
CHG Changed Price
CUP Confirmed Unit Price
CTP03 212 Unit Price X R 1/17 M
Price per unit of product, service, commodity, etc.
Segment: PID Product/Item Description

Position: 050
Loop: PID Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To describe a product or process in coded or free-form format
Syntax Notes: 1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PID05 is required.
3 If PID07 is present, then PID03 is required.
Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred to.
2 PID04 should be used for industry-specific product description codes.
3 PID08 describes the physical characteristics of the product identified in PID04. A
"Y" indicates that the specified attribute applies to this item; an "N" indicates it does
not apply. Any other value is indeterminate.
4 PID09 is used to identify the language being used in PID05.
Comments: 1 If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If
PID01 equals "X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being described in
the segment.
3 PID07 specifies the individual code list of the agency specified in PID03.
Notes: Example:
PID*F*GEN***3M Brand Scotch Tape****en~

PID*F****A cellophane strip bearing an adhesive coating on one side and wound
tightly****en~
PID*F****onto a roll. A frame surrounds the roll with a tearing edge protruding about
one****en~
PID*F****inch from the center of the roll's rotational axis.****en~

Ref. Data Base User
PID01 349 Item Description Type M ID 1/1 M
Code indicating the format of a description
F Free-form
PID02 750 Product/Process Characteristic Code O ID 2/3 O
Code identifying the general class of a product or process characteristic
PID05 352 Description X AN 1/80 O
PID09 819 Language Code O ID 2/3 O
Code designating the language used in text, from a standard code list maintained by the
International Standards Organization (ISO 639)
Segment: REF Reference Identification – Multi level line item

Position: 100
Loop: PID Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify identifying information
Syntax Notes: 1 At least one of REF02 or REF03 is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comments:
Notes: Use this segment to specify if the line item is parent or child line item. You can also
specify the corresponding line number for the line item. This is an optioal segment.
Example:
REF*FL*2*item~
produces…
<ConfirmationItem parentLineNumber="2" itemType="item">
REF*FL**composite~
produces….
<ConfirmationItem itemType="composite">

Ref. Data Base User
REF01 128 Reference Identification Qualifier M ID 2/3 M
FL Fine Line Classification
REF02 127 Reference Identification X AN 1/30 O
Reference information as defined for a particular transaction set or as specified by the
The value in REF02 is used to provide the parent line number for the current item. The value
provided in REF02 will be mapped to
ConfirmationRequest/ConfirmationItem/@parentLineNumber
REF03 352 Description X AN 1/80 O
The value in REF02 is used to provide the type of item. An item can be of type “item” and
composite”. This value is mapped to
ConfirmationRequest/ConfirmationItem/@itemType
item To identify a child item.
composite To identify a parent item.
Segment: SAC Allowances & Charges - Modifications

Position: 130
Loop: SAC Optional
Level: Detail
Usage: Optional
Max Use: 1
amount, that is applicable to service, promotion, allowance, or charge.
Dollars in SAC09.
Notes: Example: SAC*N**ZZ*F050*2200**********Original Price*en~
CUR*BY*CAD~
SAC*A**ZZ*I530**6*5****** IC**Volume Discount*en~
CUR*BY*CAD*****196*20050504*101500*197*20050701*101500~
In the header section, this represents a modification in the order to the supplier. There can
be multiple modifications. Maximum number of modifications supported is 11 This is an
example of a modification in an order.
<ConfirmationItem>
<ConfirmationStatus>
<UnitPrice>
<Money>……</Money>
<Modifications>
<Modification>
<OriginalPrice>
<Money currency="CAD">22.00</Money>
</OriginalPrice>
<AdditionalDeduction>
<DeductionPercent percent="5"/>
</AdditionalDeduction>
<ModificationDetail endDate="2005-07-01T10:15:00-08:00" name="Volume
Discount" startDate="2005-05-04T10:15:00-08:00">
</ModificationDetail>
</Modification>

Ref. Data Base User
C Charge
A Allowance
N No Allowance or Charge
SAC03 559 Agency Qualifier Code X ID 2/2 M
Code identifying the agency assigning the code values
ZZ Mutually Defined
SAC04 1301 Agency Service, Promotion, Allowance, or Charge M AN 1/10 M
Code
F050 Other
H970 Allowance
B660 Contract Allowance
C310 Discount
C300 Discount-Special
I530 Volume Discount
A040 Access Charge
A050 AccountNumberCorrectionCharge
A060 AcidBattery
A170 Adjustment
A960 Carrier
A520 Charge
D240 Freight
D180 FreightBasedOnDollarMinimum
D500 Handling
D980 Insurance
G580 Royalties
G821 Shipping
G830 ShippingAndHandling
SAC05 610 Amount O N2 1/15 M
Description: Monetary amount
OriginalPrice/Money (For Original Price)
AdditionalCost/Money (For Charge)
AdditionalDeduction/DeductionAmount/Money (For Allowances)
SAC06 378 Allowance/Charge Percent Qualifier X ID 1/1 O
Description: Code indicating on what basis allowance or charge percent is calculated
6 Price Based Amount
SAC07 332 Percent X R 1/6 O
Description: Percent expressed as a percent
SAC13 127 Reference Identification X AN 1/30 O
Description: Reference information as defined for a
particular transaction set or as specified by the Reference
Identification Qualifier
This is used to attach the modification with the status.
The value of SAC13 must match one of the values of

ACK01.
Notes:
• Only used in second iteration per modification.
• When IA or IR values are specified, Ariba Network
ignores these values for allowances and charges.
IA Item Accepted
IB Item Backordered
IC Item Accepted - Changes Made
IR Item Rejected
Description: A unique number identifying available promotion or allowance options when
more than one is offered
1 Used if SAC05 value is amount
2 Used if SAC05 value is price
Description: A free-form description to clarify the related data elements and their content
Description: Code designating the language used in text, from a standard code list maintained
by the International Standards Organization (ISO 639)
<ModificationDetail endDate="2005-07-01T10:15:00-08:00" name="Volume Discount"
startDate="2005-05-04T10:15:00-08:00">

Position: 135
Loop: SAC Optional
Level: Detail
Usage: Optional
Max Use: 1
Semantic Notes:
Notes: Example 1: CUR*BY*USD~
Example 2: CUR*BY*CAD*****196*20050504*101500*197*20050701*101500~

Ref. Data Base User
See Note on Currency Codes with CUR[1/040]. Any ISO4217 code can be sent.
Currency codes shown here are examples. . For more information on currency codes, see
CAD Canadian Dollars
GBP British Pound
USD US Dollars
XEU European Monetary Coop Fund
196 Start
CUR08 373 Date O DT 8/8 O
CUR09 337 Time O TM 4/8 O
197 End
CUR11 373 Date X DT 8/8 O
CUR12 337 Time X TM 4/8 O
Segment: ACK Line Item Acknowledgment

Position: 270
Loop: ACK Optional (Must Use)
Level: Detail
Max Use: 1
Purpose: To acknowledge the ordered quantities and specify the ready date for a specific line item
Syntax Notes: 1 If either ACK02 or ACK03 is present, then the other is required.
2 If ACK04 is present, then ACK05 is required.
3 If either ACK07 or ACK08 is present, then the other is required.
14 If ACK28 is present, then both ACK27 and ACK29 are required.
Semantic Notes: 1 ACK29 Industry Reason Code may be used to identify the item status. In addition, it
may be used in conjunction with ACK01 to further clarify the status.
Comments:
Notes: The contents of the ACK segment depend on whether this is an order confirmation with
part number change, or regular order confirmation.
An order confirmation with part number change must posses the following:
1. Product/Service ID Qualifiers VP, PD and C3 are required.

2. CTP*AS*CUP*.. is required.
3. ACK01 must be IC, otherwise ACK07 to ACK22 will be ignored.
4. Product/Service ID Qualifiers VS, MF, MG, and BP can be used optionally.
5. If either MF or MG is used, the other is required.
Violating any of these rules will cause a compliance error.
Example:
CTP*AS*CUP*2.10~
ACK*IC*1*DZ*068*20000415**VP* V16311*PD*xyz*C3*2345678~
produces...
<ConfirmationStatus quantity="1" type="detail" ...>

<UnitOfMeasure>DZN</UnitOfMeasure>
<ItemIn quantity="1">
<ItemID>
<SupplierPartID>V16311</SupplierPartID>
</ItemID>
<ItemDetail>
<UnitPrice>
</UnitPrice>
<Description xml:lang="pt-US">xyz</Description>
<UnitOfMeasure>DZN</UnitOfMeasure>
<Classification domain="UNSPSC">2345678</Classification>
</ItemDetail>
</ItemIn>
</ConfirmationStatus>
ACK*IC*5*RO*068*20000415~
DTM*017*20000416*0800*CT~
produces...
<ConfirmationStatus quantity="5" type="detail" shipmentDate="2000-04-15"

deliveryDate="2000-04-16T08:00:00-06:00">
<UnitOfMeasure>D65</UnitOfMeasure>
Suppliers use this segment group to specify exactly what they are going to fulfill and
when. Any amendments to the PO1 and Requested Delivery Date go here.
** IMPORTANT **
Scheduled shipment date, ACK05, is REQUIRED if you are accepting the item. Ariba
Network will NOT accept the order confirmation if ACK01="IA" or "IC" and ACK04-05
is absent. Shipment date is optional for backorder status, ACK01="IB".
Note: Shipment date is mandatory if your buyer requires a delivery date in the Order
Confirmation and Ship Notices.
When VP,PD and C3 qualifiers are present in ACK segment then ACK01
must be IC, otherwise it will not be treated as part number
change.

Ref. Data Base User
ACK01 668 Line Item Status Code M ID 2/2 M
Code specifying the action taken by the seller on a line item requested by the buyer
IA Item Accepted
type="accept"
IB Item Backordered
type="backordered"
IC Item Accepted - Changes Made
type="detail"
IR Item Rejected
type="reject"
ACK02 380 Quantity X R 1/15 O
Numeric value of quantity
Quantity actually being fulfilled
ACK03 355 Unit or Basis for Measurement Code X ID 2/2 O
Code specifying the units in which a value is being expressed, or manner in which a
measurement has been taken
ACK04 374 Date/Time Qualifier O ID 3/3 D
068 Current Schedule Ship
ACK05 373 Date X DT 8/8 D
Date the supplier expects to ship the goods.
This is required if the item is being accepted (ACK01="IA" or "IC") and recommended if
you are backordering (ACK01="IB").
It is not recommended if the item is being rejected (ACK01="IR"). It is in fact optional,

and will be ignored if ACK01="IR".
ACK07 235 Product/Service ID Qualifier X ID 2/2 O
(234)
SupplierPartID.
.....
<ItemIn ...>
<ItemID>
<SupplierPartID>...</SupplierPartID>
</ItemID>
ACK08 234 Product/Service ID X AN 1/48 O

(234)
VS Vendor's Supplemental Item Number
SupplierPartAuxilaryID.
.....
<ItemIn ...>
<ItemID>
....
<SupplierPartAuxilaryID>
(234)
ManufacturerPartID.
.....
<ItemIn ...>
.....
<ItemDetail>
....
<ManufacturerPartID>
(234)
MF Manufacturer
ManufacturerName.
.....
<ItemIn ...>
.....
<ItemDetail>
....
<ManufacturerName>
(234)
PD Part Number Description
.....
<ItemIn ...>
.....
<ItemDetail>
....
<Description>

(234)
C3 Classification
.....
<ItemIn ...>
.....
<ItemDetail>
....
<Classification>

(234)
BP Buyer's Part Number
.....
<ItemIn ...>
.....
<ItemDetail>
....
<Extrinsic name="Buyer's Part ID">

(234)
UP U.P.C. Consumer Package Code (1-5-5-1)
.....
<ItemIn ...>
.....
<ItemDetail>
....
<Extrinsic name="UPC Code">

Segment: DTM Date/Time Reference

Position: 280
Loop: ACK Optional (Must Use)
Level: Detail
Usage: Optional (Recommended)
Max Use: 1
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 DTM03 is required.
2 If DTM04 is present, then DTM03 is required. .
Semantic Notes:
Comments:
Usage Notes: Recommended
Notes: See example with ACK notes.
DTM specifies the estimated delivery date, preferably with a full time and zone if known.
For example, if you will ship on the 15th for next day delivery by 8:00 in the morning,
the delivery time is known.

Ref. Data Base User
DTM01 374 Date/Time Qualifier M ID 3/3 M
017 Estimated Delivery
DTM02 373 Date X DT 8/8 O
DTM03 337 Time X TM 4/8 O
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD,
or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-
59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9)
and DD = hundredths (00-99)
DTM04 623 Time Code O ID 2/2 O
Code identifying the time. In accordance with International Standards Organization
standard 8601, time can be specified by a + or - and an indication in hours in relation to
Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are
substituted by P and M in the codes that follow
Note that the LT code is not available. This is because Ariba Network does not currently
have a way to make a context-sensitive assumption on the time zone.
The ISO codes are favorable because you have direct control over the output, but they do
not support half hour zones as in Newfoundland. (If you need Newfoundland time, NS &
NT map to -0330, ND maps to -0230)
For Central European Time, use code 01.
Note also a little inconsistency with Hawaii-Aleutian Time. Hawaii and the Aleutian
Islands are not on exactly the same time zone. So the midpoint of -10:00 is used without a
shift.
="+01:00"
="+02:00"
="+03:00"
="+04:00"
="+05:00"
="+06:00"
="+07:00"
="+08:00"
="+09:00"
="+10:00"
="+11:00"
="+12:00"
="-12:00"
="-11:00"
="-10:00"
="-09:00"
="-08:00"
="-07:00"
="-06:00"
="-05:00"
="-04:00"
="-03:00"
="-02:00"
="-01:00"
AD Alaska Daylight Time
="-08:00"
AS Alaska Standard Time
="-09:00"
AT Alaska Time
="-09:00"
CD Central Daylight Time
="-05:00"
CS Central Standard Time
="-06:00"
CT Central Time
="-06:00"
ED Eastern Daylight Time
="-04:00"
ES Eastern Standard Time
="-05:00"
ET Eastern Time
="-05:00"
GM Greenwich Mean Time
="+00:00"
HD Hawaii-Aleutian Daylight Time
="-10:00"
HS Hawaii-Aleutian Standard Time
="-10:00"
HT Hawaii-Aleutian Time
="-10:00"
MD Mountain Daylight Time
="-06:00"
MS Mountain Standard Time
="-07:00"
MT Mountain Time
="-07:00"
ND Newfoundland Daylight Time
="-02:30"
NS Newfoundland Standard Time
="-03:30"
NT Newfoundland Time
="-03:30"
PD Pacific Daylight Time
="-07:00"
PS Pacific Standard Time
="-08:00"
PT Pacific Time
="-08:00"
TD Atlantic Daylight Time
="-03:00"
TS Atlantic Standard Time
="-04:00"
TT Atlantic Time
="-04:00"
UT Universal Time Coordinate
="Z" or "-00:00"
This is Coordinated Universal Time, or UTC. The correct ISO

zone extension for UTC is simply Z. However this release of
Ariba Network does not support Z, so it renders as "-00:00", to
distinguish it from GMT which uses "+00:00".
Segment: N9 Reference Identification - Comments

Position: 350
Loop: N9 Optional
Level: Detail
Usage: Optional
Max Use: 1
Comments:
Notes: Example:
N9*L1*en*Comments~
MSG*Be sure printer ink cartridges are properly sealed to avoid spillage.~
produces...
<ConfirmationItem ...>
...
<Comments xml:lang="en">Be sure printer ink cartridges are properly sealed to avoid
spillage.</Comments>
Multiline comments are also possible. For intentional linefeeds, simply use multiple
MSG segments. If you need a single comment line longer than 264 chars, use another
MSG with MSG02="LC".
N9*L1*en-CA*Comments~
MSG*Fountain pens are on special next month.~
MSG*Several popular brands are available,~
MSG*along with various colours of ink.*LC~
MSG*Supplies are limited.~
produces...
<Comments xml:lang="en-CA">Fountain pens are on special next month.

Several popular brands are available, along with various colours of ink.
Supplies are limited</Comments>
N902 is taken to be a language code. This must a two char ISO 639 language code
optionally followed by a dash and a two char ISO 3166 country code.
Some examples...
"en" English
"en-US" American English
"en-GB" British English
"es" Spanish
"fr" French
"fr-CA" Canadian French
(Text from ANSI X12 is interpreted by Ariba Network to be ISO-8859-1, but chars above
7-bit ASCII may not relay with integrity across Value Added Networks. If you need this
kind of support in EDI, you might consider using EDIFACT.)
In case there is more than one status for the line item, this comment will be mapped to all
the statuses. This is because; currently cXML supports comments at ConfirmationStatus,
but not at Confirmation Item.
Where as EDI 855 supports comments at confirmation item (PO1) level, but not at status
(ACK) level.
Mapping target:
<Comments xml:lang=N902>MSG01
MSG01</Comments>

Ref. Data Base User
L1 Letters or Notes
N902 127 Reference Identification X AN 1/30 R
Language code of the comments.

Always set to "Comments". Since the language code is Recommended, but Optional, this
constant guarantees that either N902 or N903 is filled.

Comments

Position: 360
Loop: N9 Optional
Level: Detail
Usage: Optional
Max Use: 99
is required.
Notes: Example: MSG*Be sure printer ink cartridges are properly sealed to avoid spillage.~
The actual comment text. You should generate a new MSG segment for each comment
line, to help preserve context and form. If you need more than 264 chars for a line, then
word break and start a new MSG segment, setting MSG02 in the new segment to "LC".
Mapping target:
<ConfirmationItem..>
<ConfirmationStatus..>
<Comments>
#PCDATA

Ref. Data Base User
Set to "LC" if you mean to continue a comment line that has overflowed a previous MSG
segment. If you need comment lines longer than 264 chars, then you should consider
reformatting into multiple lines.
Segment: N1 Name
Position: 370
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104) must
provide a key to the table maintained by the transaction processing party.
2 N105 and N106 further define the type of entity in N101.
Notes: See examples and notes on usage on entire N1 group with N1 (1/300) at header level.
Each occurrence of the N1 group produces a <Contact> within <ConfirmationItem>.

Ref. Data Base User
N101 98 Entity Identifier Code M ID 2/3 M
60 Salesperson
Identification of individual that sold the product e.g. SSN,
salesperson id, etc.
role="sales"
A9 Sales Office
A business entity whose main activity is, or a location at which, the
sale of goods or services takes place
role="customerService"
EN End User
role="endUser"
KY Technical Office
role="technicalSupport"
NG Administrator
role="administrator"
PD Purchaser's Department Buyer
role="purchasingAgent"
ST Ship To
role="shipTo"
N102 93 Name X AN 1/60 O
Free-form name
Segment: N2 Additional Name Information

Position: 380
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 2
Purpose: To specify additional names or those longer than 35 characters in length
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref. Data Base User
N201 93 Name M AN 1/60 M
Free-form name
N202 93 Name O AN 1/60 O
Free-form name
Segment: N3 Address Information

Position: 390
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref. Data Base User
N301 166 Address Information M AN 1/55 M
Address information
N302 166 Address Information O AN 1/55 O
Address information
Segment: N4 Geographic Location

Position: 400
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Syntax Notes: 1 If N406 is present, then N405 is required.
Semantic Notes:
Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to
specify a location.
2 N402 is required only if city name (N401) is in the U.S. or Canada.
Notes:

Ref. Data Base User
N401 19 City Name O AN 2/30 O
Free-form text for city name
N402 156 State or Province Code O ID 2/2 O
Code (Standard State/Province) as defined by appropriate government agency
N403 116 Postal Code O ID 3/15 O
Code defining international postal zone code excluding punctuation and blanks (zip code
for United States)
N404 26 Country Code O ID 2/3 O ID 2/2
Code identifying the country
Segment: PER Administrative Communications Contact

Position: 420
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required.
Semantic Notes:
Comments:
Notes:

Ref. Data Base User
PER01 366 Contact Function Code M ID 2/2 M
Code identifying the major duty or responsibility of the person or group named
CN General Contact
PER02 93 Name O AN 1/60 O
Free-form name
EM Electronic Mail
FX Facsimile
TE Telephone
EM Electronic Mail
FX Facsimile
TE Telephone
EM Electronic Mail
FX Facsimile
TE Telephone
Segment: CTT Transaction Totals

Position: 010
Loop: CTT Optional (Must Use)
Level: Summary
Max Use: 1
Purpose: To transmit a hash total for a specific element in the transaction set
Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is required.
2 If either CTT05 or CTT06 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment is intended to provide hash totals to validate transaction completeness
and correctness.
Notes: Example: CTT*1*25~
CTT does not map to cXML, but it is used to formally close the detail section and the
document. CTT02 is optional, but if it is used, our EDI map may validate it against the
calculated hash total and throw a compliance error if it does not match.

Ref. Data Base User
CTT01 354 Number of Line Items M N0 1/6 M
Total number of line items in the transaction set
CTT02 347 Hash Total O R 1/10 O
Sum of values of the specified data element. All values in the data element will be summed
without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the
left most digits if the sum is greater than the maximum size of the hash total of the data
element. Example: -.0018 First occurrence of value being hashed. .18 Second occurrence of
value being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth occurrence
of value being hashed. --------- 1855 Hash total prior to truncation. 855 Hash total after
truncation to three-digit field.
Segment: AMT Monetary Amount

Position: 020
Loop: CTT Optional (Must Use)
Level: Summary
Usage: Optional
Max Use: 1
Purpose: To indicate the total monetary amount
Syntax Notes:
Semantic Notes:
Comments:
Notes: Example:
AMT*TT*321.68~
produces...
...
<Total>
</Total>
Mapping target:
<Total>
<Money currency=CUR02>AMT02</Money>
</Total>

Ref. Data Base User
AMT01 522 Amount Qualifier Code M ID 1/3 M
Code to qualify amount
TT Total Transaction Amount
AMT02 782 Monetary Amount M R 1/18 M
Monetary amount
Segment: SE Transaction Set Trailer

Position: 030
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments)
Syntax Notes:
Semantic Notes:
Comments: 1 SE is the last segment of each transaction set.
Notes: Example: SE*87*0001~

Ref. Data Base User
SE01 96 Number of Included Segments M N0 1/10 M
Total number of segments included in a transaction set including ST and SE segments
SE02 329 Transaction Set Control Number M AN 4/9 M
Identifying control number that must be unique within the transaction set functional group
assigned by the originator for a transaction set

855 Po Acknowledgment

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

855 Po Acknowledgment

Uploaded by

Copyright:

Available Formats

Ariba, Inc. cXML 1.

2: ANSI X12 004010 855 PO Acknowledgment Implementation Guidelines

855 Purchase Order Acknowledgment

Functional Group ID= PR

Segment Terminator: ~ (tilde)

On the returning 997, the following points should be noted.

AK5 acknowledgement codes:

Status Segment Element

20 150 DTM Date/Time Reference - Acknowledgement O Must Use 1

LOOP ID - ACK 104

73 030 SE Transaction Set Trailer M M 1

Transaction Set Notes

Segment: ST Transaction Set Header

Data Element Summary

Segment: BAK Beginning Segment for Purchase Order Acknowledgment

Example of an updated order confirmation:

Data Element Summary

00 (Original) --> "new"

A separate line item (PO1 group) is required in the 855 to confirm

Ack type AE with no line items is equivalent to ack type AT.

Sets the entire purchase order to confirmed "as is".

Total rejection of the entire purchase order. This is the opposite of

You may use the N9 group to provide comments as to the reason

Note that only the date portion is available to be mapped.

Segment: CUR Currency

Data Element Summary

Segment: REF Reference

Data Element Summary

Segment: FOB F.O.B. Related Instructions

<ConfirmationHeader ... incoTerms="cfr" ...>

Data Element Summary

incoTerms="cfr" where FOB05="CFR"

Segment: SAC Service, Promotion, Allowance, or Charge Information

Data Element Summary

<Shipping trackingDomain=SAC14 trackingId=SAC13>

SAC*C*H850***2718**********Total combined taxes*en~

* SAC13 and SAC14 are ignored.

Segment: SAC Allowances & Charges - Modifications

Data Element Summary

SAC15 352 Description X AN 1/80 M

Segment: CUR Currency

Data Element Summary

Segment: DTM Date/Time Reference - Acknowledgement Date

<ConfirmationHeader ... noticeDate="2000-04-15T08:30:00-0400" ...>

* DTM04="ED" represents Eastern Daylight Time, which is UTC-0400

Note that a complete date/time/zone is recommended. Timestamps in cXML are

Data Element Summary

This is Coordinated Universal Time, or UTC. The correct ISO

Segment: TXI Tax Information

If TXI is used, then SAC*C*H850 @1/120 is required.

<TaxDetail> has four attributes: purpose, category, percentageRate, and

"sales": CS, CP, LT, SU, ST

The jurisdiction code must be assigned by the supplier and is captured by

<TaxDetail purpose="tax" category="sales" percentageRate="8.25">

* Note that TXI01=TX implies "All Taxes", so if used should be alone.

<TaxDetail purpose="tax" category=(sales | gst | vat | other)

Data Element Summary

Segment: N9 Reference Identification - Comments

<Comments xml:lang="en-CA">Fountain pens are on special next month.

Data Element Summary

N903 369 Free-form Description X AN 1/45 M

Application Value List:

Segment: MSG Message Text

SACCH850*2718********Total combined taxes*en~

If TXI is used, then SACCH850 @1/120 is required.

N9ZZ2% net 10*Payment Terms~

N2Andrea WalshNational Account Manager~

When CTPASCUP is present VP, PD and C3 qualifiers are mandatory

PIDFGEN*3M Brand Scotch Tape**en~