860 Purchase Order Change Request - Buyer Initiated
Party City · X12 004010
Party City’s published 860 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
15 of 15 segments
HEADING
ST
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
pos 0100
Required
max —
DTM
Date/Time Reference
To specify pertinent dates and times
pos 1500
Optional
max 10
BCH
Beginning Segment for Purchase Order Change
To indicate the beginning of the Purchase Order Change Transaction Set and transmit
pos 0200
Required
max —
N1 Looprepeats 200
N1
Name
To identify a party by type of organization, name, and code
pos 3000
Optional
max —
N3
Address Information
To specify the location of the named party
pos 3200
Optional
max 2
N4
Geographic Location
To specify the geographic place of the named party
pos 3300
Optional
max —
CUR
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
pos 0400
Optional
max —
REF
Reference Identification
To specify identifying information
pos 0500
Optional
max —
PER
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
pos 0600
Optional
max 3
DETAIL
POC Loop
POC
Line Item Change
To specify changes to a line item
pos 0100
Optional
max —
LIN
Item Identification
To specify basic item identification data
pos 0150
Optional
max —
PID Looprepeats 1000
PID
Product/Item Description
To describe a product or process in coded or free-form format
pos 0500
Optional
max —
SUMMARY
CTT Looprepeats 1
CTT
Transaction Totals
To transmit a hash total for a specific element in the transaction set
pos 0100
Optional
max —
AMT
Monetary Amount
To indicate the total monetary amount
pos 0200
Optional
max 5
SE
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted
pos 0300
Required
max —
Validate a 860
Paste or upload a document and check it against Party City’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Party City’s 860 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Party City, and keeps the spec current as it changes.