X12 850 Purchase Order
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) 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 the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
- ~ Segment
- * Element
- > Component
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- PO
- Purchase Order (850)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- 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).
- 850
- Purchase Order
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Purchase Order
To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Transaction Set Purpose Code "00" (Original) is sent on all purchase orders where the usage indicator in ISA15 is "P" (Production). Transaction Set Purpose "05" (Replace) is used to identify Replacement Purchase Orders. Replacement PO is an option for communicating purchase order changes via the EDI 850 instead of the EDI 860 (Purchase Order Change) transaction set. The purchase order number in BEG03 will not change from the original order on a Replacement PO. Transaction Set PurposeCode "07" (Duplicate) is used only on purchase orders where the usage indicator in ISA15 is "T" (Test). "18" (Reissue) is used to identify a PO which is re-issued due to a cancellation via the EDI 860 (PO Change). The EDI 860 contains a transaction set purpose code of "17" (Cancel, to be re-issued).
All Purchase Order Type Codes listed will be used in both Stores and eComm EDI 850 documents.
Purchase Order Type Code "BK " (Blanket Order - Quantity Firm) is used to commit to specific items, quantities and time period in which they will be shipped. The Blanket Order (BK) will not provide any specific shipping information as it is used to commit to wholesale quantities only. Specific shipping information will be provided in purchase order types "RE", "RL" and "SA". The EDI 855 (PO Acknowledgment) will be required as confirmation for all Blanket Orders.
When BEG02 = BK, BEG03 will be 12 digits (ie 300001234567)
When BEG02 = RL, RE or SA, BEG03 will be 8 characters (alpha/numeric for eComm, numeric only for Stores)
BEG06 is used on RL, SA, and RE purchase order types when there is an associated Blanket Order (BK). The contract number sent will be a 12 digits.
Example 1:
BEG00BK300001234567~~20170624.00
Example 2:
BEGRL123456782017062420170624300001234567.00
Example 3:
BEGSA1234567K300002345678.00
Example 4:
BEGRE1234567R2017062420170710~300001234567.30000123457805
Example 5:
BEGBK30000123456720170626.18
Example 6:
BEGRL12345678
Code identifying purpose of transaction set
Transaction Set Purpose Code usage
00 (Original) - This purpose code is used to identify the original Order/PO.
05 (Replace) - This purpose code identifies a Replacement Order/PO. This transaction set purpose code is sent only to suppliers who have requested buyer initiated purchase order changes via the EDI 850 (Replacement) instead of the EDI 860 (PO Change - Buyer Initiated)
transaction set.
07 (Duplicate) - This purpose code is used in the EDI 850 for orders that are identified as test. The indicator in ISA15 is sent as "T".
18 (Reissue) - This purpose code is sent if the PO was canceled and re-issued under the same number. The re-issued PO may or may not include changes from the original order.
- 00
- Original
This purpose code is used to identify the original Order/PO
- 05
- Replace
This purpose code identifies a Replacement Order/PO. This transaction set purpose code is sent only to suppliers who have requested buyer initiated purchase order changes via the EDI 850 (Replacement) instead of the EDI 860 (PO Change - Buyer Initiated)
transaction set. - 07
- Duplicate
This purpose code is used in the EDI 850 for orders that are identified as test. The indicator in ISA15 is sent as "T".
- 18
- Reissue
This purpose code is sent if the PO was canceled and re-issued under the same number. The re-issued PO may or may not include changes from the original order.
Code specifying the type of Purchase Order
- BK
- Blanket Order (Quantity Firm)
- RE
- Reorder
- RL
- Release or Delivery Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BEG05 is the date assigned by the purchaser to purchase order.
Retailer's original purchase order date
Department Number
To specify identifying information
Example:
REFDP123~WOMENS APPAREL.
Code qualifying the Reference Identification
- DP
- Department Number
This code may be used in the header area or the detail area, but not both.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
This data element is only generated when REF01 = DP to provide the department description.
Internal Vendor Number
To specify identifying information
Example:
REPIA012345
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Identification number assigned to the vendor, by the retailer, for use within the retailer's system
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
The purpose of this segment is to provide a contact for inquiries, regarding the contents of this purchase order document.
PERBDJANE SMITHEMJSMITH@JCP.COM~
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Sales Requirements
To specify general conditions or requirements of the sale
The CSH segment is used to indicate the ship date/order filling rules applicable to the order. This will be sent only on purchase order types RL, RE, and SA. Code P4 (Do Not Pre-Ship) indicates that the order must not be shipped prior the Requested (Earliest) ShipDate on the order. Sales Requirement Code SC (Ship Complete) and NS (No Substitutes) are related to order-filling rules. Code SC is used to indicate all merchandise on the order must be shipped together on one shipment. The only exception to this single shipment rule would be for orders too large to ship on one trailer. A split shipment of this order must be advised via the EDI 870 transaction ( see ISR segment requirements). This is typically used on "Bulk" orders. Code NS mandates that no substitutes are allowed for any items on the order. This segment may be repeated more than once.
CSHNSP4
CSH
CSH ~SC
Code to identify a specific requirement or agreement of sale
- NS
- No Substitutes
- P4
- Do Not Preship
- SC
- Ship Complete
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
ITD~14~~~~45~~~~~NET 45.
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
- 14
- Previously agreed upon
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
The percent is sent with a decimal point only when needed, e.g., 10.5% is sent as "10.5'', and 2% is sent as "2''.
Number of days in the terms discount period by which payment is due if terms discount is earned
Number of days until total invoice amount is due (discount not applicable)
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
For Purchase Order Type " BK " (Blanket Order), Date/Time Reference Code "010" (Requested Ship) is the date the supplier is expected to have the contracted merchandise available to ship. For Purchase Order Types "RE", "RL", and "SA", Date/TimeReference Code "010" (Requested Ship) is the earliest date on which a supplier can ship any merchandise against the order. Purchase Order Types "BK", "RE", "RL", and "SA", Date/Time Reference Code "001" (Cancel After) is the last date on which a supplier can ship any merchandise against the order. If a supplier wants to ship against the order after this date, an EDI 870 must be sent providing an "Expected to Ship By Date". Date extensions are subject to an approval by the JCPenney Buyer.
DTM01020170701.
DTM00120170708.
Code specifying type of date or time, or both date and time
- 001
- Cancel After
If the order has not been shipped by this date, the order is considered canceled.
- 010
- Requested Ship
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
The segment provides shipping instructions for an Expedited Order and basic routing. For basic routing (carrier details), suppliers must submit a request for routing through TMS (Transportation Management System).
For an Expedited PO, the JCPenney Buyer will decide if a Purchase Order needs to be expedited and will work with the supplier to determine the appropriate party to pay the expedited freight charges. See examples for values sent in TD505.
Basic Routing
TD5~~~~~FOLLOW TMS ROUTING INSTRUCTIONS
Supplier Pay:
TD5~~~~~EXPEDITE-SUPPLIER FOLLOW
TD5~~~~~SHIPPING INSTRUCTIONS
TD5~~~~~FROM SUPPLY CHAIN MANAGER
JCPenney Pay:
TD5~~~~~EXPEDITE-JCP FOLLOW
TD5~~~~~SHIPPING INSTRUCTIONS
TD5~~~~~FROM SUPPLY CHAIN MANAGER
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
For Expedited Order and PO:
Supplier Pay message:
EXPEDITE-SUPPLIER FOLLOW SHIPPING INSTRUCTIONS FROM SUPPLY CHAIN MANAGER
JCPenney Pay message:
EXPEDITE-JCP FOLLOW SHIPPING INSTRUCTIONS FROM SUPPLY CHAIN MANAGER
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
N9AH300001234567
N9AH1234567K
N9AH12345678
Code qualifying the Reference Identification
- AH
- Agreement Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Text
To specify textual data
This segment will contain any text clauses for the agreement referenced in the previous N9 segment. This text segment will only be sent as part of the first 850 within a functional group. There will be one note segment containing the following message. Note: The message included in the MTX segment was approved by JCPenney's legal department.
THIS ORDER IS SUBJECT TO THE TERMS OF THE TRADING PARTNER AGREEMENT (TPA AGREEMENT) BETWEEN THE PARTIES ON THE FILE WITH JCPENNEY ON THE DATE OF THIS ORDER, OR, IN THE ABSENCE OF A TPA AGREEMENT BETWEEN THE PARTIES, JCPENNEY'S STANDARD TPA AGREEMENT POSTED ON THE JCPENNEY SUPPLIER INTERNET SITE ON THE DATE OF THIS ORDER
Name
To identify a party by type of organization, name, and code
Up to four N1 loops may be generated for each of the Entity Identifier Codes listed in N101. These loops are generated for purchase order types (BEG02) "RE", "RL", and "SA". For Purchase Orders containing the SDQ (Destination Quantity) segment, the Mark For Party (Z7) will not be included in the N1 segment but in the SDQ.
Ship Point site will be identified in the N1 segment where the Entity Identifier Code "SF" (Ship From) is in N101, N102 contains the supplier's name and N104 is the 2-digit Ship Point location code (ie 00). An N4 segment will be included in this loop to identify the Ship Point site's geographic location (City, State and Zip Code).
N1BT~~9294417.
Ship Point Site:
N1SFABC COMPANY9200.
N1ST~~9294417.
N1Z7~~9200448.
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
- SF
- Ship From
- ST
- Ship To
- Z7
- Mark-for Party
This is the receiving location for the order where the location is neither the buying party nor the ship-to location and the mark-for party is specified on the shipping label, e.g., the mark-for party is a satellite warehouse, the buying party is the store, and the ship-to location is the distribution centre.
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- 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.
This is the location code as defined by N103. The location refers to
a store, warehouse, distribution centre, plant, etc. Location codes are used to alleviate the need to send complete names and addresses.
Five digit unit number (N101 = BT, ST, or Z7). When N101 = SF, the value in N104 is the two-digit ship point (ie 00).
Address Information
To specify the location of the named party
This segment is used to identify the Mark For Party's (N101 = Z7) and Ship To (N101 = ST) address. This segment is only generated for trading partners who do not receive the JCPenney address file electronically (EDI 864).
N3~1234 FAIR STREET
Geographic Location
To specify the geographic place of the named party
This segment is used to identify the Ship From (N101 = SF), Mark For Party (N101 = Z7), and Ship To (N101 = ST) geographic location.
For the Mark For and Ship To, this segment is only generated for trading partners who do not receive the JCPenney address file electronically. (EDI 864)
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Code identifying the country
Code required if not USA.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
All order types will include the JCPenney item number. If Vendor Style (product) Number and UPC-12 or EAN-13 are available in the JCPenney item database, it will be included in the PO1 segment. Item numbers can be viewed and verified by supplier on theJCPenney Supplier portal (see Item Inquiry).
When PO106 (Product/Service ID Qualifier) = IN (Buyer's Item Number), then PO107 (Product/Service ID) is the JCPenney item number.
The min/max character length:
Stores = 9/13
format: AAAABBBBC, AAAABBBBCC, AAAABBBBCCC, AAAABBBBCCCC or AAAABBBBCCCCC (AAAA = 4 digit lot #, BBBB = 4 digit line #, C = 1-5 character size description. "*ONLY" in the size description denotes assorted sizes, no size or pre-pack).
eComm = 11/11
format: AAAAAAABBBB (AAAAAAA = 7 digit lot #, BBBB = 4 digit SKU).
PO112 - PO113 are planned for future usage. These data elements will contain the qualifier (SK) and Oracle Retail Item Number(ORIN). The ORIN will have a minimum character length of 9 with a possible maximum character length of 25.
Stores
PO1~~20EA15.95WHIN12345678SVNABC123UP~111122223333.
Pre-pack
PO~~2AS30.24WHIN12345678*ONLYVN~CDEFG1234.
eComm
PO~~10EA6.5WHIN12345670034VN123ABCDUP~444455556666.
ORIN
PO~~5EA7.15WHIN12345678MVN1234DEFUP222233334444SK~123456789.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
For prepacks, code "AS" (Assortment) will be sent.
Price per unit of product, service, commodity, etc.
The price is sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95'', and $29.00 would be sent as "29''. To indicate a no charge item or free goods, PO104 will contain a single zero (0) and PO105 will contains code NC.
SKU cost price. Cost price is per unit of measure. Price contains a maximum of 5 integer and 2 decimal positions for all retail merchandise. For prepacks, the cost price is for the entire assortment.
Code identifying the type of unit price for an item
This data element is used to clarify or alter the basis of unit price. The unit price expressed in PO104 is always in the same terms as the unit of measure in PO103, unless otherwise specified in PO105.
- WH
- Wholesale
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- 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.
- IN
- Buyer's Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- EAN/UCC - 13
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
For future usage. Please include data element in map. This qualifier will be used to identify the Oracle Retail Item Number (ORIN) in PO113.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
For future usage. Please include data element in map. The Product/Service ID will be the Oracle Retail Item Number (ORIN).
Pricing Information
To specify pricing information
The Unit Price (Retail amount) will be sent on all purchase order types for both Stores and eComm channels. It will not be included on purchase order types " RE", "RL" or "SA"containing prepack or group lot numbers.
CTPRTL~79.99RTL~10
CTP
Code identifying pricing specification
- RTL
- Retail
Price per unit of product, service, commodity, etc.
- 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.
The price is sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95'', and $29.00 would be sent as "29''. Price contains a maximum of 5 integer and 2 decimal positions for all merchandise.
Product/Item Description
To describe a product or process in coded or free-form format
This segment will include product, colour and size descriptions.
PIDF08~~~FLEECE JACKET
PIDF75~~~CHARCOAL
PIDF91~~~10-12
PIDF08~~~BATH TOWEL
PIDF75~~~YELLOW STRIPES
PIDF08~~~SS SHIRT
PIDF75~~~BLACK
PIDF91~~~XXL
29PIDF08ANKLE BOOT.F
PID75CHOC BRWN
PIDF91~5.5
Code indicating the format of a description
- 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.
- F
- Free-form
The description will be found in PID05.
Code identifying the general class of a product or process characteristic
- 08
- Product
- 75
- Buyer's Color Description
- 91
- Buyer's Item Size Description
A free-form description to clarify the related data elements and their content
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The purpose of this segment is to identify the Case Size and Inner Pack.
If the Case Size equals "0" (single sku per order = open stock), the supplier may pack as many units per carton following JCPenney's weight per carton guidelines.
Case Size = 18, Inner Pack = 1
PO4~18~~~~~~~~~~~~~1.
Case Size = 12 , Inner Pack = 6
PO4~12~~~~~~~~~~~~~6.
No Case Size, Inner Pack 9
PO4~~~~~~~~~~~~~~9.
The number of inner containers, or number of eaches if there are no inner containers, per outer container
This data field will contain the Case Size. Case Size is optional and will not be sent if unavailable for the selected item.
The number of eaches per inner container
The item's inner pack is included in this data field.
Reference Identification
To specify identifying information
The purpose of this segment is to identify the Product Packaging Number (PPK #) assigned to a JCPenney item number by ProductDevelopment for Private Brand specifications.
REFS3111222
Code qualifying the Reference Identification
- S3
- Specification Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The PPK# has a min/max character length is 6/15.
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
There is one segment for each Allowance, Charge, Service, or Promotion being specified. If this segment appears in the header area of the transaction set, the data applies to the entire transaction set. If this segment appears in the detail area of the transaction set, the data applies only to that line item. The data specified in the header area is exclusive of the data specified in the detail area; it is not the sum of the data in the detail area, i.e., allowances or charges.
This SAC segment will be used to identify the Floor-Ready (if any) and ticketing requirements for the merchandise on the order. For Floor-Ready, only hanger requirements will be given (SAC04 = HA). The default requirement for Floor-Ready is 'Garment on Hanger'. If the requirements specify 'Hanger in Box', SAC15 will be sent with code 'IB' (Hanger in Box), otherwise, this data element will not be included in the transmission. The specific hanger number will be in SAC13. All other Floor-Ready requirements will be communicated separately.
The ticketing service requirements will be identified by code 'TC' in SAC04 and the ticket stock number will be in SAC13 ('UPC' if UPC ticketed).
SACN~~VITC~~~~~~~~~0123.
SACN~~VIHA~~~~~~~~~123-01-BL.
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- N
- No Allowance or Charge
Code identifying the agency assigning the code values
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
Agency maintained code identifying the service, promotion, allowance, or charge
- SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with SAC03 to further define SAC02.
Code "CS" is used to denote special processing text in SAC15.
- CS
- Custom Service
- HA
- Hanger Service
- TC
- Ticketing Service
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
Hanger or Ticket stock number.
A free-form description to clarify the related data elements and their content
Special processing text or code IB (Hanger in box).
Destination Quantity
To specify destination and quantity detail
The SDQ is to specify destination and quantity details on the Release/Delivery Order. The destination location is the Mark For (final) destination of the shipment.
SDQEA920044818009011801578360195854021701803897360955518122375413375721794736.
SDQEA9219323721998418.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
See Section III for code list.
Code designating the system/method of code structure used for Identification Code (67)
- SDQ02 is used only if different than previously defined in the transaction set.
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- SDQ03 is the store number.
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Code identifying a party or other code
Location.
Marking, Packaging, Loading
To describe marking, packaging, loading, and unloading requirements
This segment identifies the usage of RFID tags.
The RFID indicator may be included in both Stores and eCom orders.
PKGS34FDM R1.
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
- X
- Semi-structured (Code and Text)
The description will be found in PKG04 and PKG05.
Code specifying the marking, packaging, loading and related characteristics being described
- 34
- Product Marking
Code identifying the agency assigning the code values
- Use PKG03 to indicate the organization that publishes the code list being referred to.
- FD
- Uniform Code Council (UCS)
A code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product
- PKG04 should be used for industry-specific packaging description codes.
Data field will contain "M R1" for RFID tagged.
A free-form description to clarify the related data elements and their content
- Special marking or tagging data can be given in PKG05 (description).
Subline Item Detail
To specify product subline detail item data
This segment is used to identify the component items that make up the Pre-Pack. For each component item, SLN04 shows the quantity of that component item in 'one' pre-pack. SLN06 is the cost of one unit of measure [EA (each)] of the component. SLN09 through SLN14 contains the various types of item identifiers for the component item.
If SLN03 contains code D or code I, then SLN04 and SLN05 are required.
When SLN09 = IN, then SLN10 is the JCPenney Item Number.
When SLN13 = UP, then SLN14 is the vendor's UPC
When SLN13 = EN, then SLN14 is the vendor's EAN (European Article Number)
SLN 15 - SLN18 is planned for future usage.
SLN00000000000000000001~~I1EA5.04WH~~IN12345678SVN1234ABC1UP444455556666.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Increment by one starting with one (1).
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Numeric value of quantity
The quantity will reflect the number of sellable units.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
For prepacks we will only send code "EA" (Each).
Price per unit of product, service, commodity, etc.
The price is sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95'', and $29.00 would be sent as "29''.
To indicate a no charge item or free goods, SLN06 will contain a single zero (0) and SLN07 will contain code NC.
SKU cost price. Cost price is per unit of measure. Price contains a maximum of 5 integer and 2 decimal positions for all Retail merchandise.
Code identifying the type of unit price for an item
This data element is used to clarify or alter the basis of unit price.
The unit price expressed in SLN06 is always in the same terms as the unit of measure in SLN05, unless otherwise specified in SLN07.
- WH
- Wholesale
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- IN
- Buyer's Item Number
Identifying number for a product or service
For Store merchandise, we will send lot/line/size description in the following format: AAAABBBBCCCCC, where AAAA = lot number, BBBB = line number, CCCCC = size description.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- EAN/UCC - 13
- UP
- UCC - 12
Identifying number for a product or service
UPC or EAN (2-5-5-1) numbers will be sent on a selective basis by supplier product ID. We will not send both the EAN and UPC numbers; it will be one or the other.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
For future usage.
Identifying number for a product or service
For future usage.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
For future usage.
Identifying number for a product or service
For future usage.
Product/Item Description
To describe a product or process in coded or free-form format
The PID segment is used to provide product/item description in text and or coded formats. This PID segment is used to provide the product description for components (see SLN) of a pre-pack or group item.
Note: For an example, see prior PID segment.
Code indicating the format of a description
- 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.
- F
- Free-form
The description will be found in PID05.
Code identifying the general class of a product or process characteristic
- 08
- Product
- 75
- Buyer's Color Description
- 91
- Buyer's Item Size Description
A free-form description to clarify the related data elements and their content
For Stores merchandise, if PID02 is "08", this element will contain a twenty character lot description; if PID02 is "75", element will contain a five character colour description; if PID02 is "91", element will contain a five character size group description.
Pricing Information
To specify pricing information
CTP within the SLN loop is used to provide the Retail amount on component items included in a Pre-Pack or Group.
Code identifying pricing specification
- RTL
- Retail
Price per unit of product, service, commodity, etc.
- 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.
The price is sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95'', and $29.00 would be sent as "29''.
SKU retail price. Retail price is per unit of measure. Price contains a maximum of 5 integer and 2 decimal positions for all merchandise.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- 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.
Total number of line items in the transaction set
The number of PO1 segments present in the transaction set.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
sample
GS*PO*SENDERGS*RECEIVERGS*20231102*034105*000000001*X*004030
ST*850*300025780
BEG*00*BK*300001234567**20170620
REF*DP*123*WOMENS APPAREL
REF*IA*012345
PER*BD*JANE SMITH*EM*JSMITH@JCP.COM
CSH*NS
CSH*P4
CSH*SC
ITD*14****45*******NET 45
DTM*010*20170701
DTM*001*20170708
TD5*****FOLLOW TMS ROUTING INSTRUCTIONS
N9*AH*300001234567
N1*BT**92*94417
N1*SF*ABC COMPANY*92*00
N1*ST**92*94417
N1*Z7**92*00448
N3*1234 FAIR STREET
PO1**20*EA*15.95*WH*IN*12345678S*VN*ABC123*UP*111122223333
CTP**RTL*79.99
PID*F*08***FLEECE JACKET
PID*F*75***CHARCOAL
PID*F*91***10-12
PO4*18*************1
REF*S3*111222
SAC*N**VI*TC*********0123
SAC*N**VI*HA*********123-01-BL
SDQ*EA*92*00448*18*00901*18*01578*36*01958*54*02170*18*03897*36*09555*18*12237*54*13375*72*17947*36
SDQ*EA*92*19323*72*19984*18
PKG*X*34*FD*M R1
SLN*00000000000000000001**I*1*EA*5.04*WH**IN*12345678S*VN*1234ABC1*UP*444455556666
PID*F*08***FLEECE JACKET
PID*F*75***CHARCOAL
PID*F*91***10-12
CTT*1
SE*36*300025780
GE*1*000000001
IEA*1*000000001
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.