**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.
Target Corporation
EDI Guideline
Domestic
850
Purchase Order
Basic Format
Version 4010
Revised: February 2023
Change Log
Date | Change | Comments |
February 2023 | PO1 SLN | Added IB as new item identifier/qualifier. |
July 2022 | PO4 PO414
N902
MSG | Added verbiage to segment note.
Added Truckload Reference ID note.
Added usage note for N901. |
November 2020 | Converted from .pdf to .docx file format | Changes to file format only – no change to content. |
May 2020 | Added “CT” qualifier to DTM segment |
|
September 2017 | Added new PO format to the BEG and N9 segment.
| Starting in Dec 2017 Target will be phasing in a new PO format: 12345678901-1234 |
| Added ‘IN’ as a new item identifier in the PO1 and SLN segments. |
|
850 Purchase Order (Version 4010)
Functional Group ID=PO
Introduction:
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.
Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M | 010 | ST | Transaction Set Header | M | 1 |
|
|
|
|
|
|
|
|
M | 020 | BEG | Beginning Segment for Purchase Order | M | 1 |
|
|
|
|
|
|
|
|
M | 050 | REF | Reference Identification | M | >1 |
|
|
|
|
|
|
|
|
| 060 | PER | Administrative Communications Contact | O | 3 |
|
|
|
|
|
|
|
|
| 080 | FOB | F.O.B. Related Instructions | O | >1 |
|
|
|
|
|
|
|
|
| 110 | CSH | Sales Requirements | O | 5 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - SAC |
|
| 25 |
|
|
|
|
|
|
|
| 120 | SAC | Service, Promotion, Allowance, or Charge Information | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
M | 130 | ITD | Terms of Sale/Deferred Terms of Sale | M | >1 |
|
|
|
|
|
|
|
|
M | 150 | DTM | Date/Time Reference | M | 10 |
|
|
|
|
|
|
|
|
| 240 | TD5 | Carrier Details (Routing Sequence/Transit Time) | O | 12 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - N9 |
|
| 1000 |
|
|
|
|
|
|
|
| 295 | N9 | Reference Identification | O | 1 |
|
|
|
|
|
|
|
|
| 300 | MSG | Message Text | O | 1000 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| LOOP ID - N1 |
|
| 200 |
|
|
|
|
|
|
|
| 310 | N1 | Name | O | 1 |
|
|
|
|
|
|
|
|
| 320 | N2 | Additional Name Information | O | 2 |
|
|
|
|
|
|
|
|
| 330 | N3 | Address Information | O | 2 |
|
|
|
|
|
|
|
|
| 340 | N4 | Geographic Location | O | >1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Detail:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
|
|
| LOOP ID - PO1 |
|
| 100000 |
|
|
|
|
|
|
|
M | 010 | PO1 | Baseline Item Data | M | 1 |
| n1 |
|
|
|
|
|
|
|
|
| LOOP ID - CTP |
|
| >1 |
|
|
|
|
|
|
|
| 040 | CTP | Pricing Information | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| LOOP ID - PID |
|
| 1000 |
|
|
|
|
|
|
|
| 050 | PID | Product/Item Description | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 090 | PO4 | Item Physical Details | O | >1 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - SAC |
|
| 25 |
|
|
|
|
|
|
|
| 130 | SAC | Service, Promotion, Allowance, or Charge Information | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 140 | IT8 | Conditions of Sale | O | 1 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - SLN |
|
| 1000 |
|
|
|
|
|
|
|
| 470 | SLN | Subline Item Detail | O | 1 |
|
|
|
|
|
|
|
|
| 490 | PID | Product/Item Description | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
|
|
| LOOP ID - CTT |
|
| 1 |
|
|
|
|
|
|
|
M | 010 | CTT | Transaction Totals | M | 1 |
| n2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
M | 030 | SE | Transaction Set Trailer | 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.
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: |
| ************************ Sample ST Segment ___________________ ST*850*0001 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | ST01 | 143 | Transaction Set Identifier Code | M |
| ID 3/3 | ||||
| Code uniquely identifying a Transaction Set |
| ||||||||
| 850 |
| Purchase Order |
| ||||||
M | ST02 | 329 | Transaction Set Control Number | M |
| AN 4/9 | ||||
| Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set |
| ||||||||
Segment: BEG Beginning Segment for Purchase Order
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes: 1 BEG05 is the date assigned by the purchaser to purchase order.
Comments:
Notes: |
| ************************ NOTE: Starting in Dec 2017, Target will start phasing in a new PO format. The new format removes the 4 digit department number prefix and the purchase order number will be moving from 7 digits to 11 digits. No changes are being made to the location number. During this transition, your company needs to be able to receive both PO formats, as both may be received during transition. The same PO format received from Target will need to be returned on all EDI related documents for that PO to ensure no business interruption.
New Purchase Order Number Format: 12345678901-0551
Sample BEG Segment ________________________ BEG*00*SA*SSSS-PPPPPPP-LLLL**20000320*D
BEG*00*SA*12345678909-0551**20000320*D ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | BEG01 | 353 | Transaction Set Purpose Code | M |
| ID 2/2 | |||||
| Code identifying purpose of transaction set |
| |||||||||
| 00 |
| Original |
| |||||||
| 06 |
| Confirmation |
| |||||||
| This code is used for confirmation orders only. Vendor should have previously received an order via phone or fax. |
| |||||||||
M | BEG02 | 92 | Purchase Order Type Code | M |
| ID 2/2 | |||||
| Code specifying the type of Purchase Order |
| |||||||||
| BK |
| Blanket Order (Quantity Firm) |
| |||||||
| An order with a purchase order type code of "BK", can NOT be released for shipment. A release order (purchase order type of "RL") must be received, before a shipment can be released for delivery. |
| |||||||||
| RL |
| Release or Delivery Order |
| |||||||
| An order for goods and services placed against a pre-existing contract or blanket order |
| |||||||||
| SA |
| Stand-alone Order |
| |||||||
| An order with one or more locations that is approved and allocated on the same day. |
| |||||||||
M | BEG03 | 324 | Purchase Order Number | M |
| AN 1/22 | |||||
| Identifying number for Purchase Order assigned by the orderer/purchaser |
| |||||||||
| New Purchase Order Number Format: 12345678901-1234
The Basic PO Number format is: SSSS-PPPPPPP-LLLL SSSS=Source Code PPPPPPP=Purchase Order Number LLLL = Location ID (Always the Bill To Location)
Vendor Cross Dock (VCD) means the merchandise is shipped to the DC, but is billed to and marked for the store. |
| |||||||||
| BEG04 | 328 | Release Number | O |
| AN 1/30 | |||||
| Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction |
| |||||||||
| Sequentially numbered releases against a blanket order. This element is used only when BEG02=RL. |
| |||||||||
M | BEG05 | 373 | Date | M |
| DT 8/8 | |||||
| Date expressed as CCYYMMDD |
| |||||||||
| The date the purchase order was created in the Target system. |
| |||||||||
| BEG06 | 367 | Contract Number | O |
| AN 1/30 | |||||
| Contract number |
| |||||||||
| This element will be used for the Target Stores Speed Sourcing Program. |
| |||||||||
| D |
| Standard |
| |||||||
| Q |
| Quick Reaction |
| |||||||
| S |
| Speed |
| |||||||
Segment: REF Reference Identification
Position: 050
Loop:
Level: Heading
Usage: Mandatory
Max Use: >1
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.
3 If either C04005 or C04006 is present, then the other is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comments:
Notes: |
| ************************ Target will send at least two occurrences of the REF. The first occurrence will contain a Target internal vendor number identifying the company receiving the PO. The second occurrence will contain the Target department number. If sent, the third occurrence will contain a reference or identification number defined by the vendor for a particular purchase if the purchase order has an assigned promotional number.
Sample REF Segments ______________________ REF*IA*3342078*VENDORABC REF*DP*907
REF*IA*3342078*VENDORABC REF*DP*907 REF*PD*024678AB ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | REF01 | 128 | Reference Identification Qualifier | M |
| ID 2/3 | |||||
| Code qualifying the Reference Identification |
| |||||||||
| AR |
| Arrival Code |
| |||||||
| This code is used by selected vendors only. Unless you are contacted by Target Supplier Performance Management, no action is required on your part for this code. |
| |||||||||
| DP |
| Department Number |
| |||||||
| IA |
| Internal Vendor Number |
| |||||||
| PD |
| Promotion/Deal Number |
| |||||||
| REF02 | 127 | Reference Identification | X |
| AN 1/30 | |||||
| Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier |
| |||||||||
| When REF01 = AR, Valid Codes for REF02: 01 = Single Day Arrival (SDA) 02 = Single Day Receipt (SDR)
VR = Volume Route PO |
| |||||||||
| REF03 | 352 | Description | X |
| AN 1/80 | |||||
| A free-form description to clarify the related data elements and their content |
| |||||||||
| When REF01 = IA, this will contain Vendor Name. When REF01 = AR, this filed will contain one of the following values, dependent on the value in REF02: SDA = Single Day Arrival SDR = Single Day Receipt
VR = Volume Route PO |
| |||||||||
Segment: PER Administrative Communications Contact
Position: 060
Loop:
Level: Heading
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.
2 If either PER05 or PER06 is present, then the other is required.
3 If either PER07 or PER08 is present, then the other is required.
Semantic Notes:
Comments:
Notes: |
| ************************ This segment is used for sending guest contact numbers special orders shipping direct from vendor to guest.
Sample PER Segment _____________________ PER*DC*Valuable Guest*TE*6123755510 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | PER01 | 366 | Contact Function Code | M |
| ID 2/2 | ||||
| Code identifying the major duty or responsibility of the person or group named |
| ||||||||
| DC |
| Delivery Contact |
| ||||||
| PER02 | 93 | Name | O |
| AN 1/60 | ||||
| Free-form name |
| ||||||||
| Guest Name |
| ||||||||
| PER03 | 365 | Communication Number Qualifier | X |
| ID 2/2 | ||||
| Code identifying the type of communication number |
| ||||||||
| EM |
| Electronic Mail |
| ||||||
| FX |
| Facsimile |
| ||||||
| TE |
| Telephone |
| ||||||
| PER04 | 364 | Communication Number | X |
| AN 1/80 | ||||
| Complete communications number including country or area code when applicable |
| ||||||||
| Guest Contact Number |
| ||||||||
| PER05 | 365 | Communication Number Qualifier | X |
| ID 2/2 | ||||
| Code identifying the type of communication number |
| ||||||||
| EM |
| Electronic Mail |
| ||||||
| FX |
| Facsimile |
| ||||||
| TE |
| Telephone |
| ||||||
| PER06 | 364 | Communication Number | X |
| AN 1/80 | ||||
| Complete communications number including country or area code when applicable |
| ||||||||
| Guest Contact Number |
| ||||||||
| PER07 | 365 | Communication Number Qualifier | X |
| ID 2/2 | ||||
| Code identifying the type of communication number |
| ||||||||
| EM |
| Electronic Mail |
| ||||||
| FX |
| Facsimile |
| ||||||
| TE |
| Telephone |
| ||||||
| PER08 | 364 | Communication Number | X |
| AN 1/80 | ||||
| Complete communications number including country or area code when applicable |
| ||||||||
| Guest Contact Number |
| ||||||||
| PER09 | 443 | Contact Inquiry Reference | O |
| AN 1/20 | ||||
| Additional reference number or description to clarify a contact number |
| ||||||||
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.
3 If FOB07 is present, then FOB06 is required.
4 If FOB08 is present, then FOB09 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: |
| ************************ Sample FOB Segment ______________________ FOB*DF*DE*MINNEAPOLIS, MN ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | FOB01 | 146 | Shipment Method of Payment | M |
| ID 2/2 | ||||
| Code identifying payment terms for transportation charges |
| ||||||||
| DF |
| Defined by Buyer and Seller |
| ||||||
| FOB02 | 309 | Location Qualifier | X |
| ID 1/2 | ||||
| Code identifying type of location |
| ||||||||
| DE |
| Destination (Shipping) |
| ||||||
| OR |
| Origin (Shipping Point) |
| ||||||
| ZZ |
| Mutually Defined |
| ||||||
| FOB03 | 352 | Description | O |
| AN 1/80 | ||||
| A free-form description to clarify the related data elements and their content |
| ||||||||
| Free-form name of destination or origin |
| ||||||||
Segment: CSH Sales Requirements
Position: 110
Loop:
Level: Heading
Usage: Optional
Max Use: 5
Purpose: To specify general conditions or requirements of the sale
Syntax Notes: 1 If CSH02 is present, then CSH03 is required.
2 If either CSH06 or CSH07 is present, then the other is required.
3 If either CSH09 or CSH10 is present, then the other is required.
Semantic Notes: 1 CSH03 is the maximum monetary amount value which the order must not exceed.
2 CSH04 is the account number to which the purchase amount is charged.
3 CSH05 is the date specified by the sender to be shown on the invoice.
4 CSH06 identifies the source of the code value in CSH07.
Comments:
Notes: |
| ************************ Sample CSH Segment _______________________ CSH*Y ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
| CSH01 | 563 | Sales Requirement Code | O |
| ID 1/2 | |||||
| Code to identify a specific requirement or agreement of sale |
| |||||||||
| N |
| No Back Order |
| |||||||
| Back Order not Authorized |
| |||||||||
| Y |
| Back Order if Out of Stock |
| |||||||
| Back Order Authorized |
| |||||||||
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.
3 If either SAC06 or SAC07 is present, then the other is required.
4 If either SAC09 or SAC10 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.
7 If SAC14 is present, then SAC13 is required.
8 If SAC16 is present, then SAC15 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.
Notes: |
| ************************ This segment will be used only if receiving a special type of purchase order.
Sample SAC Segment _______________________ SAC*N**VI*OHPR ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | SAC01 | 248 | Allowance or Charge Indicator | M |
| ID 1/1 | |||||
| Code which indicates an allowance or charge for the service specified |
| |||||||||
| N |
| No Allowance or Charge |
| |||||||
| SAC02 | 1300 | Service, Promotion, Allowance, or Charge Code | X |
| ID 4/4 | |||||
| Code identifying the service, promotion, allowance, or charge |
| |||||||||
| Not used by Target |
| |||||||||
| SAC03 | 559 | Agency Qualifier Code | X |
| ID 2/2 | |||||
| Code identifying the agency assigning the code values |
| |||||||||
| VI |
| Voluntary Inter-Industry Commerce Standard (VICS) EDI |
| |||||||
| SAC04 | 1301 | Agency Service, Promotion, Allowance, or Charge Code | X |
| AN 1/10 | |||||
| Agency maintained code identifying the service, promotion, allowance, or charge |
| |||||||||
| This is a 2-part, 4-character field. The first 2 characters will be 'OH'. The next 2 characters will be one of the following codes: |
| |||||||||
| DS |
| Drop Ship |
| |||||||
| Guest Request, Vendor to Guest |
| |||||||||
| KO |
| Closeout Order |
| |||||||
| NS |
| New Store Order |
| |||||||
| PR |
| Promotional Order |
| |||||||
| RC |
| Raincheck Order |
| |||||||
| RO |
| Rush Order |
| |||||||
| SB |
| Seasonal Buildup Order |
| |||||||
| SO |
| Special Order |
| |||||||
| SP |
| Sample Order |
| |||||||
| ZQ |
| Vendor Warehouse |
| |||||||
Segment: ITD Terms of Sale/Deferred Terms of Sale
Position: 130
Loop:
Level: Heading
Usage: Mandatory
Max Use: >1
Purpose: To specify terms of sale
Syntax Notes: 1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD13 is required.
2 If ITD08 is present, then at least one of ITD04 ITD05 or ITD13 is required.
3 If ITD09 is present, then at least one of ITD10 or ITD11 is required.
Semantic Notes: 1 ITD15 is the percentage applied to a base amount used to determine a late payment charge.
Comments: 1 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.
Notes: |
| ************************ Sample ITD Segments ____________________ ITD*01*2*****30
ITD*02*2****20000710 (Net EOM)
ITD*02*2*2*20000810 (2% EOM +30)
ITD*10*************L (Domestic Letter of Credit) ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | ITD01 | 336 | Terms Type Code | M |
| ID 2/2 | |||||
| Code identifying type of payment terms |
| |||||||||
| 01 |
| Basic |
| |||||||
| 02 |
| End of Month (EOM) |
| |||||||
| 10 |
| Instant |
| |||||||
| 14 |
| Previously agreed upon |
| |||||||
| Not used by Target at this time. |
| |||||||||
M | ITD02 | 333 | Terms Basis Date Code | M |
| ID 1/2 | |||||
| Code identifying the beginning of the terms period |
| |||||||||
| 2 |
| Delivery Date |
| |||||||
| 3 |
| Invoice Date |
| |||||||
| ITD03 | 338 | Terms Discount Percent | O |
| R 1/6 | |||||
| Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date |
| |||||||||
| 99.999=Discount % Note: the digits after the decimal are floating and not fixed. This means ending zeroes will be dropped. For example, 9.990 will display as 9.99, but 9.999 will display as 9.999. |
| |||||||||
| ITD04 | 370 | Terms Discount Due Date | X |
| DT 8/8 | |||||
| Date payment is due if discount is to be earned expressed in format CCYYMMDD |
| |||||||||
| ITD05 | 351 | Terms Discount Days Due | X |
| N0 1/3 | |||||
| Number of days in the terms discount period by which payment is due if terms discount is earned |
| |||||||||
| # of days in terms discount period. |
| |||||||||
| ITD06 | 446 | Terms Net Due Date | O |
| DT 8/8 | |||||
| Date when total invoice amount becomes due expressed in format CCYYMMDD |
| |||||||||
| ITD07 | 386 | Terms Net Days | O |
| N0 1/3 | |||||
| Number of days until total invoice amount is due (discount not applicable) |
| |||||||||
| # of days until total invoice amount due. |
| |||||||||
| ITD08 | 362 | Terms Discount Amount | O |
| N2 1/10 | |||||
| Total amount of terms discount |
| |||||||||
| Not used by Target |
| |||||||||
| ITD09 | 388 | Terms Deferred Due Date | O |
| DT 8/8 | |||||
| Date deferred payment or percent of invoice payable is due expressed in format CCYYMMDD |
| |||||||||
| Not used by Target |
| |||||||||
| ITD10 | 389 | Deferred Amount Due | X |
| N2 1/10 | |||||
| Deferred amount due for payment |
| |||||||||
| Not used by Target |
| |||||||||
| ITD11 | 342 | Percent of Invoice Payable | X |
| R 1/5 | |||||
| Amount of invoice payable expressed in percent |
| |||||||||
| Not used by Target |
| |||||||||
| ITD12 | 352 | Description | O |
| AN 1/80 | |||||
| A free-form description to clarify the related data elements and their content |
| |||||||||
| ITD13 | 765 | Day of Month | X |
| N0 1/2 | |||||
| The numeric value of the day of the month between 1 and the maximum day of the month being referenced |
| |||||||||
| ITD14 | 107 | Payment Method Code | O |
| ID 1/2 | |||||
| Code identifying type of payment procedures |
| |||||||||
| L |
| Letter of Credit |
| |||||||
Segment: DTM Date/Time Reference
Position: 150
Loop:
Level: Heading
Usage: Mandatory
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required.
2 If DTM04 is present, then DTM03 is required.
3 If either DTM05 or DTM06 is present, then the other is required.
Semantic Notes:
Comments:
Notes: |
| ************************ The Date/Time qualifier sent in the DTM01 is determined by the terms set up by the Target Accounts Payable team and lead times set up by the Target merchant/buyer. EDI does not determine which codes will be sent. Depending on how terms and lead times are set, you could receive either 037/038 or 063/064. If a promotion applies you could also receive a third date with the 015 qualifier. You should be prepared to receive 037/038 and 063/064 and 015. Unless you have been contacted by Target Supplier Performance Management, you do NOT need to be prepared to receive either 078 or 118.
Sample DTM Segment _____________________ DTM*037*20060315 DTM*038*20060331
DTM*015*20060415
DTM*063*20051101 DTM*064*20051025 DTM*015*20051027
DTM*037*20060315 DTM*038*20060315 DTM*078*20060315*0745*LT ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | DTM01 | 374 | Date/Time Qualifier | M |
| ID 3/3 | |||||
| Code specifying type of date or time, or both date and time |
| |||||||||
| 015 |
| Promotion Start |
| |||||||
| Target Promotion Date. |
| |||||||||
| 037 |
| Ship Not Before |
| |||||||
| Vendor should not ship product before this date. |
| |||||||||
| 038 |
| Ship No Later |
| |||||||
| Vendor should not ship product after this date. |
| |||||||||
| 063 |
| Do Not Deliver After |
| |||||||
| Do not deliver product to Target after this date. |
| |||||||||
| 064 |
| Do Not Deliver Before |
| |||||||
| Do not deliver product to Target before this date. |
| |||||||||
| 078 |
| Promised for Delivery (Week of) |
| |||||||
| This code is used by selected vendors only. Unless you are contacted by Target Supplier Performance Management, no action is required on your part for this code.
If this code is used, a time will also be sent.
This code is used for prepaid freight only. |
| |||||||||
| 118 |
| Requested Pick-up |
| |||||||
| This code is used by selected vendors only. Unless you are contacted by Target Vendor Operations, no action is required on your part for this code.
If this code is used, a time will also be sent.
This code is used for collect freight only. |
| |||||||||
| DTM02 | 373 | Date | X |
| DT 8/8 | |||||
| Date expressed as CCYYMMDD |
| |||||||||
| DTM03 | 337 | Time | X |
| TM 4/8 | |||||
| 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) |
| |||||||||
| This field is used by selected vendors only. Unless you are contacted by Target Vendor Performance, no action is required on your part for this code. |
| |||||||||
| DTM04 | 623 | Time Code | O |
| ID 2/2 | |||||
| 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 |
| |||||||||
| CT |
| Central Time |
| |||||||
| LT |
| Local Time |
| |||||||
Segment: TD5 Carrier Details (Routing Sequence/Transit Time)
Position: 240
Loop:
Level: Heading
Usage: Optional
Max Use: 12
Purpose: To specify the carrier and sequence of routing and provide transit time information
Syntax Notes: 1 At least one of TD502 TD504 TD505 TD506 or TD512 is required.
2 If TD502 is present, then TD503 is required.
3 If TD507 is present, then TD508 is required.
4 If TD510 is present, then TD511 is required.
5 If TD513 is present, then TD512 is required.
6 If TD514 is present, then TD513 is required.
7 If TD515 is present, then TD512 is required.
Semantic Notes: 1 TD515 is the country where the service is to be performed.
Comments: 1 When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
Notes: |
| ************************ Sample TD5 Segment _____________________ TD5*B*2*OVNT*M
TD5*B*2*NEMF*C
TD5*B*92*PREPAID ROADWAY*M
TD5*B*92*See Routing Guide
NOTE: A Routing Guide should have been sent to your shipping department from the Target Transportation Department. ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | TD501 | 133 | Routing Sequence Code | M |
| ID 1/2 | ||||
| Code describing the relationship of a carrier to a specific shipment movement |
| ||||||||
| B |
| Origin/Delivery Carrier (Any Mode) |
| ||||||
M | TD502 | 66 | Identification Code Qualifier | M |
| ID 1/2 | ||||
| Code designating the system/method of code structure used for Identification Code (67) |
| ||||||||
| 2 |
| Standard Carrier Alpha Code (SCAC) |
| ||||||
| 92 |
| Assigned by Buyer or Buyer's Agent |
| ||||||
M | TD503 | 67 | Identification Code | M |
| AN 2/80 | ||||
| Code identifying a party or other code |
| ||||||||
| If TD502 = 2, this will be the carrier's SCAC. If TD502 = 92, this will be a text message. |
| ||||||||
| TD504 | 91 | Transportation Method/Type Code | X |
| ID 1/2 | ||||
| Code specifying the method or type of transportation for the shipment |
| ||||||||
| A |
| Air |
| ||||||
| C |
| Consolidation |
| ||||||
| H |
| Customer Pickup |
| ||||||
| M |
| Motor (Common Carrier) |
| ||||||
| U |
| Private Parcel Service |
| ||||||
Segment: N9 Reference Identification
Position: 295
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.
3 If either C04003 or C04004 is present, then the other is required.
4 If either C04005 or C04006 is present, then the other 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: |
| ************************ NOTE: Starting in Dec 2017, Target will start phasing in a new PO format. The new format removes the 4 digit department number prefix and the purchase order number will be moving from 7 digits to 11 digits. No changes are being made to the location number. During this transition, your company needs to be able to receive both PO formats, as both may be received during transition. The same PO format received from Target will need to be returned on all EDI related documents for that PO to ensure no business interruption.
New Purchase Order Number Format: 12345678901-1234
Sample N9 Segment ____________________ N9*ZZ*SPH
Example for Truckload Rounding: N9*AN*0123-1234567-0551 N9*AN*0123-7654321-0551 N9*AN*12345678901-0551 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | N901 | 128 | Reference Identification Qualifier | M |
| ID 2/3 | |||||
| Code qualifying the Reference Identification |
| |||||||||
| AN |
| Associated Purchase Orders |
| |||||||
| Truckload Reference ID. |
| |||||||||
| ZZ |
| Mutually Defined |
| |||||||
| N902 | 127 | Reference Identification | X |
| AN 1/30 | |||||
| Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier |
| |||||||||
| This element will contain codes explaining contents of the following MSG segment, such as: SPH = Special Handling Instructions.
When N901 = AN, this field will contain a Truckload Reference ID. All related PO numbers will be sent in the MSG segment. |
| |||||||||
Segment: MSG Message Text
Position: 300
Loop: N9 Optional
Level: Heading
Usage: Optional
Max Use: 1000
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: |
| ************************ This segment will be used to transmit order instructions.
If N901 = AN, all related PO numbers will be sent in MSG01. ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | MSG01 | 933 | Free-Form Message Text | M |
| AN 1/80 | |
| Free-form message text |
| |||||
| Note: Length is up to 80 characters. |
| |||||
Segment: N1 Name
Position: 310
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
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: |
| ************************ At least one N1 segment will be sent for Basic PO format POs. If the Basic Format PO is a VCD (Vendor Cross Dock), a Direct Ship to a Guest or a Target.com Fulfillment Center PO, a second N1 segment will be sent. An additional N1 for Vendor Factory will be sent when a Target owned brand item is included on the PO.
Sample N1 Segments __________________ N1*BY**92*0551 (Ship To/Bill To)
N1*BY**92*1001 (Bill To & Mark For Store) N1*ST*SHIP VIA VCD TO DC*92*0551 (Ship To)
N1*BY**92*1001 (Bill To) N1*ST*Guest Name*92*9998 (Ship Direct to Guest) Note: This location code (9998) must be returned on the 810 & 856 in the N1 with "ST" qualifier.
N1*ST*TARGET.COM OHL 1*92*9477
N1*MF*FACTORY NAME ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | N101 | 98 | Entity Identifier Code | M |
| ID 2/3 | |||||
| Code identifying an organizational entity, a physical location, property or an individual |
| |||||||||
| BY |
| Buying Party (Purchaser) |
| |||||||
| This is the Target location to be invoiced |
| |||||||||
| MF |
| Manufacturer of Goods |
| |||||||
| ST |
| Ship To |
| |||||||
| Target will only send an ST N1 Segment if merchandise goes through the Target DC's Vendor Cross Dock, merchandise is shipped direct to the guest or merchandise is shipped to a Target.com Replenishment Center. |
| |||||||||
| N102 | 93 | Name | X |
| AN 1/60 | |||||
| Free-form name |
| |||||||||
| It is used for VCD or Ship Direct to Guest. If N101 = "MF", this will be the factory name. |
| |||||||||
| N103 | 66 | Identification Code Qualifier | X |
| ID 1/2 | |||||
| Code designating the system/method of code structure used for Identification Code (67) |
| |||||||||
| 92 |
| Assigned by Buyer or Buyer's Agent |
| |||||||
| N104 | 67 | Identification Code | X |
| AN 2/80 | |||||
| Code identifying a party or other code |
| |||||||||
| 4-digit location |
| |||||||||
Segment: N2 Additional Name Information
Position: 320
Loop: N1 Optional
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: |
| ************************ This segment is used only when a Vendor Factory is sent.
Sample N2 Segment __________________ N2*MANUFACTURERS ID ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | N201 | 93 | Name | M |
| AN 1/60 | |
| Free-form name |
| |||||
| This will contain the manufacturer's ID. |
| |||||
Segment: N3 Address Information
Position: 330
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Notes: |
| ************************ An N3 segment will be sent for all Basic POs and will contain the Ship To address. If N101 ="MF", an N3 will be sent with the factory address.
Sample N3 Segment ____________________ N3*14750 MILLER AVE ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | N301 | 166 | Address Information | M |
| AN 1/55 | |
| Address information |
| |||||
| N302 | 166 | Address Information | O |
| AN 1/55 | |
| Address information |
| |||||
Segment: N4 Geographic Location
Position: 340
Loop: N1 Optional
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: |
| ************************ An N4 will be sent for all Basic POs and will contain the Ship To address. If N101 = "MF", an N3 will be sent with the factory address.
Sample N4 Segment ____________________ N4*FONTANTA*CA*92336 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
| N401 | 19 | City Name | O |
| AN 2/30 | |
| Free-form text for city name |
| |||||
| N402 | 156 | State or Province Code | O |
| ID 2/2 | |
| Code (Standard State/Province) as defined by appropriate government agency |
| |||||
| N403 | 116 | Postal Code | O |
| ID 3/15 | |
| Code defining international postal zone code excluding punctuation and blanks (zip code for United States) |
| |||||
| N404 | 26 | Country Code | O |
| ID 2/3 | |
| Code identifying the country |
| |||||
Segment: PO1 Baseline Item Data
Position: 010
Loop: PO1 Mandatory
Level: Detail
Usage: Mandatory
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.
4 If either PO108 or PO109 is present, then the other is required.
5 If either PO110 or PO111 is present, then the other is required.
6 If either PO112 or PO113 is present, then the other is required.
7 If either PO114 or PO115 is present, then the other is required.
8 If either PO116 or PO117 is present, then the other is required.
9 If either PO118 or PO119 is present, then the other is required.
10 If either PO120 or PO121 is present, then the other is required.
11 If either PO122 or PO123 is present, then the other is required.
12 If either PO124 or PO125 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.
Notes: |
| ************************ Note: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of receiving it and sending it back on inbound EDI documents to Target.
Three Product Identifiers will be sent: CB, VA, and UP or EN.
Sample PO1 Segment ____________________ PO1*000001*36*EA*4.06*WE*CB*Target DPCI*VA*100*UP*123456789016
PO1*000001*124*EA*2.069*WE*CB*Target DPCI*VA*200*EN*1234567890123
PO1*000001*124*EA*2.069*WE*CB*123456789*VA*200*UP*491234567890
PO1*000001*124*EA*2.069*WE*CB*Target DPCI*VA*200 *DPCI = Department, Class, Item
*If one item is ordered in two different casepacks then it should be treated as two separate items. ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | PO101 | 350 | Assigned Identification | M |
| AN 1/20 | |||||
| Alphanumeric characters assigned for differentiation within a transaction set |
| |||||||||
| PO102 | 330 | Quantity Ordered | X |
| R 1/15 | |||||
| Quantity ordered |
| |||||||||
M | PO103 | 355 | Unit or Basis for Measurement Code | M |
| ID 2/2 | |||||
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken |
| |||||||||
| Pharmacy vendors will always receive case quantities |
| |||||||||
| CA |
| Case |
| |||||||
| EA |
| Each |
| |||||||
| LB |
| Pound |
| |||||||
M | PO104 | 212 | Unit Price | M |
| R 1/17 | |||||
| Price per unit of product, service, commodity, etc. |
| |||||||||
| Note: digits after the decimal are floating and not fixed. This means ending zeroes will be dropped; e.g. 9.990 will display as 9.99, but 9.999 will display as 9.999. |
| |||||||||
| PO105 | 639 | Basis of Unit Price Code | O |
| ID 2/2 | |||||
| Code identifying the type of unit price for an item |
| |||||||||
| LE |
| Catalog Price per Each |
| |||||||
| PP |
| Price per Pound |
| |||||||
| QT |
| Quoted |
| |||||||
| UM |
| Price per Unit of Measure |
| |||||||
| Will be sent when UOM = CA and price is per case price |
| |||||||||
| WD |
| Wholesale Price per Dozen |
| |||||||
| WE |
| Wholesale Price per Each |
| |||||||
M | PO106 | 235 | Product/Service ID Qualifier | M |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
|
|
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| PO107 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| When PO106 = CB, this field will contain a 9-digit Target Corporation DPCI. When PO106 = EN, this field will contain the 13-digit European Article Number. When PO106 = UP, this field will contain the full 12-digit UPC Code or a 12-digit "4 code" DPCI.
The 4 code UPC is a 12 digit number made up from the DPCI. It will have "49" on the front and a check digit at the end. You will receive this code if you are not a UPC vendor.
When PO106 = VA, this field will contain the Vendor Style Number. When PO106 = Int'l Standard Book Number (ISBN). |
| |||||||||
| PO108 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
|
|
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| PO109 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| See notes in PO107. |
| |||||||||
| PO110 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
|
|
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| PO111 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| See Notes in PO107. |
| |||||||||
| PO112 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
|
|
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| PO113 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| See Notes in PO107. |
| |||||||||
Segment: CTP Pricing Information
Position: 040
Loop: CTP Optional
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.
3 If CTP09 is present, then CTP02 is required.
4 If CTP10 is present, then CTP02 is required.
5 If CTP11 is present, then CTP03 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: |
| ************************ Sample CTP Segment _____________________ CTP*RS*RES*9.99********3
CTP*RS*UCP*9.067 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
| CTP01 | 687 | Class of Trade Code | O |
| ID 2/2 | |||||
| Code indicating class of trade |
| |||||||||
| RS |
| Resale |
| |||||||
| CTP02 | 236 | Price Identifier Code | X |
| ID 3/3 | |||||
| Code identifying pricing specification |
| |||||||||
| RES |
| Resale |
| |||||||
| Retail |
| |||||||||
| UCP |
| Unit cost price |
| |||||||
| Item List Cost (only sent with Letter of Credit). |
| |||||||||
| CTP03 | 212 | Unit Price | X |
| R 1/17 | |||||
| Price per unit of product, service, commodity, etc. |
| |||||||||
| CTP04 | 380 | Quantity | X |
| R 1/15 | |||||
| Numeric value of quantity |
| |||||||||
| Not used by Target |
| |||||||||
| CTP05 | C001 | Composite Unit of Measure | X |
|
| |||||
| To identify a composite unit of measure (See Figures Appendix for examples of use) |
| |||||||||
| Not used by Target |
| |||||||||
| CTP06 | 648 | Price Multiplier Qualifier | O |
| ID 3/3 | |||||
| Code indicating the type of price multiplier |
| |||||||||
| Not used by Target |
| |||||||||
| CTP07 | 649 | Multiplier | X |
| R 1/10 | |||||
| Value to be used as a multiplier to obtain a new value |
| |||||||||
| Not used by Target |
| |||||||||
| CTP08 | 782 | Monetary Amount | O |
| R 1/18 | |||||
| Monetary amount |
| |||||||||
| Not used by Target |
| |||||||||
| CTP09 | 639 | Basis of Unit Price Code | O |
| ID 2/2 | |||||
| Code identifying the type of unit price for an item |
| |||||||||
| Not used by Target |
| |||||||||
| CTP10 | 499 | Condition Value | O |
| AN 1/10 | |||||
| Identifies rate restrictions or provisions |
| |||||||||
| Not used by Target |
| |||||||||
| CTP11 | 289 | Multiple Price Quantity | O |
| N0 1/2 | |||||
| Quantity of units for a given price, e.g., 3 for $10.00 |
| |||||||||
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.
4 If PID08 is present, then PID04 is required.
5 If PID09 is present, then PID05 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: |
| ************************ Sample PID Segment ______________________ PID*F*08***VNECK SWEATER
PID*X*08*VI*PP*MENS SHIRTS ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | PID01 | 349 | Item Description Type | M |
| ID 1/1 | ||||
| Code indicating the format of a description |
| ||||||||
| F |
| Free-form |
| ||||||
| S |
| Structured (From Industry Code List) |
| ||||||
| X |
| Semi-structured (Code and Text) |
| ||||||
| PID02 | 750 | Product/Process Characteristic Code | O |
| ID 2/3 | ||||
| Code identifying the general class of a product or process characteristic |
| ||||||||
| 08 |
| Product |
| ||||||
| 73 |
| Vendor color description |
| ||||||
| 74 |
| Vendor size description |
| ||||||
| PID03 | 559 | Agency Qualifier Code | X |
| ID 2/2 | ||||
| Code identifying the agency assigning the code values |
| ||||||||
| VI |
| Voluntary Inter-Industry Commerce Standard (VICS) EDI |
| ||||||
| PID04 | 751 | Product Description Code | X |
| AN 1/12 | ||||
| A code from an industry code list which provides specific data about a product characteristic |
| ||||||||
| PP |
| Prepack |
| ||||||
| PID05 | 352 | Description | X |
| AN 1/80 | ||||
| A free-form description to clarify the related data elements and their content |
| ||||||||
Segment: PO4 Item Physical Details
Position: 090
Loop: PO1 Mandatory
Level: Detail
Usage: Optional
Max Use: >1
Purpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item
Syntax Notes: 1 If either PO402 or PO403 is present, then the other is required.
2 If PO405 is present, then PO406 is required.
3 If either PO406 or PO407 is present, then the other is required.
4 If either PO408 or PO409 is present, then the other is required.
5 If PO410 is present, then PO413 is required.
6 If PO411 is present, then PO413 is required.
7 If PO412 is present, then PO413 is required.
8 If PO413 is present, then at least one of PO410 PO411 or PO412 is required.
9 If PO417 is present, then PO416 is required.
10 If PO418 is present, then PO404 is required.
Semantic Notes: 1 PO415 is used to indicate the relative layer of this package or range of packages within the layers of packaging. Relative Position 1 (value R1) is the innermost package.
2 PO416 is the package identifier or the beginning package identifier in a range of identifiers.
3 PO417 is the ending package identifier in a range of identifiers.
4 PO418 is the number of packages in this layer.
Comments: 1 PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
2 PO413 defines the unit of measure for PO410, PO411, and PO412.
Notes: |
| ************************ PO401 = The number of total units within the carton - OR - The number of inner packs within the outer carton. (The latter applies if PO414 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856. If the PO414 is not sent on the PO, do not send back/return a PO414 on the EDI 856.
Sample PO4 Segments ___________________
PO4*12 (no inner packs) - Casepack = 12 individual units PO4*4*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | PO401 | 356 | Pack | M |
| N0 1/6 | ||||
| The number of inner containers, or number of eaches if there are no inner containers, per outer container |
| ||||||||
| PO402 | 357 | Size | X |
| R 1/8 | ||||
| Size of supplier units in pack |
| ||||||||
| Not used by Target |
| ||||||||
| PO403 | 355 | Unit or Basis for Measurement Code | X |
| ID 2/2 | ||||
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken |
| ||||||||
| Not used by Target |
| ||||||||
| PO404 | 103 | Packaging Code | X |
| AN 3/5 | ||||
| Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required |
| ||||||||
| Not used by Target |
| ||||||||
| PCK |
| Packed - not otherwise specified |
| ||||||
| 71 |
| Not Otherwise Specified |
| ||||||
| PO405 | 187 | Weight Qualifier | O |
| ID 1/2 | ||||
| Code defining the type of weight |
| ||||||||
| Not used by Target |
| ||||||||
| PO406 | 384 | Gross Weight per Pack | X |
| R 1/9 | ||||
| Numeric value of gross weight per pack |
| ||||||||
| Not used by Target |
| ||||||||
| PO407 | 355 | Unit or Basis for Measurement Code | X |
| ID 2/2 | ||||
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken |
| ||||||||
| Not used by Target |
| ||||||||
| PO408 | 385 | Gross Volume per Pack | X |
| R 1/9 | ||||
| Numeric value of gross volume per pack |
| ||||||||
| Not used by Target |
| ||||||||
| PO409 | 355 | Unit or Basis for Measurement Code | X |
| ID 2/2 | ||||
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken |
| ||||||||
| Not used by Target |
| ||||||||
| PO410 | 82 | Length | X |
| R 1/8 | ||||
| Largest horizontal dimension of an object measured when the object is in the upright position |
| ||||||||
| Not used by Target |
| ||||||||
| PO411 | 189 | Width | X |
| R 1/8 | ||||
| Shorter measurement of the two horizontal dimensions measured with the object in the upright position |
| ||||||||
| Not used by Target |
| ||||||||
| PO412 | 65 | Height | X |
| R 1/8 | ||||
| Vertical dimension of an object measured when the object is in the upright position |
| ||||||||
| Not used by Target |
| ||||||||
| PO413 | 355 | Unit or Basis for Measurement Code | X |
| ID 2/2 | ||||
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken |
| ||||||||
| Not used by Target |
| ||||||||
| PO414 | 810 | Inner Pack | O |
| N0 1/6 | ||||
| The number of eaches per inner container |
| ||||||||
| If inner cartons are being sent, this must represent the number of selling units within one inner pack. If the PO414 element is received on the PO, then it is required to be sent back on the 856. |
| ||||||||
Segment: SAC Service, Promotion, Allowance, or Charge Information
Position: 130
Loop: SAC Optional
Level: Detail
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.
3 If either SAC06 or SAC07 is present, then the other is required.
4 If either SAC09 or SAC10 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.
7 If SAC14 is present, then SAC13 is required.
8 If SAC16 is present, then SAC15 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.
Notes: |
| ************************ Sample SAC Segments _____________________ SAC*N**VI*HA
SAC*N**VI*TC990101*********TICKETING CODE ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | SAC01 | 248 | Allowance or Charge Indicator | M |
| ID 1/1 | ||||
| Code which indicates an allowance or charge for the service specified |
| ||||||||
| N |
| No Allowance or Charge |
| ||||||
| SAC02 | 1300 | Service, Promotion, Allowance, or Charge Code | X |
| ID 4/4 | ||||
| Code identifying the service, promotion, allowance, or charge |
| ||||||||
| Not used by Target |
| ||||||||
| SAC03 | 559 | Agency Qualifier Code | X |
| ID 2/2 | ||||
| Code identifying the agency assigning the code values |
| ||||||||
| VI |
| Voluntary Inter-Industry Commerce Standard (VICS) EDI |
| ||||||
| SAC04 | 1301 | Agency Service, Promotion, Allowance, or Charge Code | X |
| AN 1/10 | ||||
| Agency maintained code identifying the service, promotion, allowance, or charge |
| ||||||||
| HA |
| Hanger Service |
| ||||||
| TC990101 |
| Ticketing Service |
| ||||||
| SAC05 | 610 | Amount | O |
| N2 1/15 | ||||
| Monetary amount |
| ||||||||
| Not used by Target |
| ||||||||
| SAC06 | 378 | Allowance/Charge Percent Qualifier | X |
| ID 1/1 | ||||
| Code indicating on what basis allowance or charge percent is calculated |
| ||||||||
| Not used by Target |
| ||||||||
| SAC07 | 332 | Percent | X |
| R 1/6 | ||||
| Percent expressed as a percent |
| ||||||||
| Not used by Target |
| ||||||||
| SAC08 | 118 | Rate | O |
| R 1/9 | ||||
| Rate expressed in the standard monetary denomination for the currency specified |
| ||||||||
| Not used by Target |
| ||||||||
| SAC09 | 355 | Unit or Basis for Measurement Code | X |
| ID 2/2 | ||||
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken |
| ||||||||
| Not used by Target |
| ||||||||
| SAC10 | 380 | Quantity | X |
| R 1/15 | ||||
| Numeric value of quantity |
| ||||||||
| Not used by Target |
| ||||||||
| SAC11 | 380 | Quantity | O |
| R 1/15 | ||||
| Numeric value of quantity |
| ||||||||
| Not used by Target |
| ||||||||
| SAC12 | 331 | Allowance or Charge Method of Handling Code | O |
| ID 2/2 | ||||
| Code indicating method of handling for an allowance or charge |
| ||||||||
| Not used by Target |
| ||||||||
| SAC13 | 127 | Reference Identification | X |
| AN 1/30 | ||||
| Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier |
| ||||||||
| This field will contain the ticketing code. Please refer to the Vendor Partnership Manual. |
| ||||||||
Segment: IT8 Conditions of Sale
Position: 140
Loop: PO1 Mandatory
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify general conditions or requirements and to detail conditions for substitution of alternate products
Syntax Notes: 1 At least one of IT801 IT802 IT803 IT805 or IT807 is required.
2 If either IT808 or IT809 is present, then the other is required.
3 If either IT810 or IT811 is present, then the other is required.
4 If either IT812 or IT813 is present, then the other is required.
5 If either IT814 or IT815 is present, then the other is required.
6 If either IT816 or IT817 is present, then the other is required.
7 If either IT818 or IT819 is present, then the other is required.
8 If either IT820 or IT821 is present, then the other is required.
9 If either IT822 or IT823 is present, then the other is required.
10 If either IT824 or IT825 is present, then the other is required.
11 If either IT826 or IT827 is present, then the other is required.
Semantic Notes: 1 IT803 is the maximum monetary amount value which the order must not exceed.
2 IT804 is the account number to which the purchase amount is to be charged.
3 IT805 is the date specified by the sender to be shown on the invoice.
Comments: 1 Element 235/234 combinations should be interpreted to include products and/or services. See the Data Dictionary for a complete list of IDs.
2 IT808 through IT827 provides 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.
Notes: |
| This segment will be sent to Prescription Pharmaceutical vendors only. If you have any questions, please check with your buyer.
************************ Sample IT8 Segment ________________
IT8*NS
This code will be sent only when a substitute item for a pharmaceutical item will not be accepted by Target Stores. ************************* |
Data Element Summary
Ref. Data
Des. Element Name Attributes
| IT801 | 563 | Sales Requirement Code | X |
| ID 1/2 | ||||
| Code to identify a specific requirement or agreement of sale |
| ||||||||
| NS |
| No Substitutes |
| ||||||
Segment: SLN Subline Item Detail
Position: 470
Loop: SLN Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify product subline detail item data
Syntax Notes: 1 If either SLN04 or SLN05 is present, then the other is required.
2 If SLN07 is present, then SLN06 is required.
3 If SLN08 is present, then SLN06 is required.
4 If either SLN09 or SLN10 is present, then the other is required.
5 If either SLN11 or SLN12 is present, then the other is required.
6 If either SLN13 or SLN14 is present, then the other is required.
7 If either SLN15 or SLN16 is present, then the other is required.
8 If either SLN17 or SLN18 is present, then the other is required.
9 If either SLN19 or SLN20 is present, then the other is required.
10 If either SLN21 or SLN22 is present, then the other is required.
11 If either SLN23 or SLN24 is present, then the other is required.
12 If either SLN25 or SLN26 is present, then the other is required.
13 If either SLN27 or SLN28 is present, then the other is required.
Semantic Notes: 1 SLN01 is the identifying number for the subline item.
2 SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
3 SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
4 SLN08 is a code indicating the relationship of the price or amount to the associated segment.
Comments: 1 See the Data Element Dictionary for a complete list of IDs.
2 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.
3 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.
Notes: |
| ************************ Note: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of receiving it and sending it back on inbound EDI documents to Target.
Sample SLN Segment _____________________ SLN*1**1*2400*EA*4.52*LE*I*CB*Target DPCI*UP*023456789015*VA*100
SLN*1**1*2400*EA*4.52*LE*I*CB*Target DPCI*EN*1234567890123*VA*200
SLN*1**I*20*EA (Example for Set Components Only) ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | SLN01 | 350 | Assigned Identification | M |
| AN 1/20 | |||||
| Alphanumeric characters assigned for differentiation within a transaction set |
| |||||||||
| Sequential counter assigned by Target |
| |||||||||
| SLN02 | 350 | Assigned Identification | O |
| AN 1/20 | |||||
| Alphanumeric characters assigned for differentiation within a transaction set |
| |||||||||
| Not used by Target |
| |||||||||
M | SLN03 | 662 | Relationship Code | M |
| ID 1/1 | |||||
| Code indicating the relationship between entities |
| |||||||||
| I |
| Included |
| |||||||
M | SLN04 | 380 | Quantity | M |
| R 1/15 | |||||
| Numeric value of quantity |
| |||||||||
M | SLN05 | C001 | Composite Unit of Measure | M |
|
| |||||
| To identify a composite unit of measure (See Figures Appendix for examples of use) |
| |||||||||
M | C00101 | 355 | Unit or Basis for Measurement Code | M |
| ID 2/2 | |||||
| Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken |
| |||||||||
| Pharmacy vendors will always receive case quantities |
| |||||||||
| CA |
| Case |
| |||||||
| EA |
| Each |
| |||||||
| LB |
| Pound |
| |||||||
| SLN06 | 212 | Unit Price | X |
| R 1/17 | |||||
| Price per unit of product, service, commodity, etc. |
| |||||||||
| SLN07 | 639 | Basis of Unit Price Code | O |
| ID 2/2 | |||||
| Code identifying the type of unit price for an item |
| |||||||||
| LE |
| Catalog Price per Each |
| |||||||
| QT |
| Quoted |
| |||||||
| WD |
| Wholesale Price per Dozen |
| |||||||
| WE |
| Wholesale Price per Each |
| |||||||
| SLN08 | 662 | Relationship Code | O |
| ID 1/1 | |||||
| Code indicating the relationship between entities |
| |||||||||
| I |
| Included |
| |||||||
| SLN09 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
|
|
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| SLN10 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| When SLN09 = CB, this field will contain the 9-digit Target DPCI. When SLN09 = EN, this field will contain the 13-digit European Article Number. When SLN09 = EO, this field will contain the 8-digit European Article Number. When SLN09 = UP, this field will contain the full 12-digit UPC Code or a 12 digit "4 code" DPCI. When SLN09 = VA, this field will contain the Vendor Style Number. When SLN09 = IB, this field will contain the Int'l Standard Book Number (ISBN). |
| |||||||||
| SLN11 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
|
|
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| SLN12 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| See Notes in SLN10. |
| |||||||||
| SLN13 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
| EAN/UCC - 8 |
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| SLN14 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| See Notes in SLN10. |
| |||||||||
| SLN15 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
| EAN/UCC-8 |
| |||||||
| IB |
| International Standard Book Number (ISBN) |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| VA |
| Vendor's Style Number |
| |||||||
| SLN16 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| See Notes in SLN10. |
| |||||||||
Segment: PID Product/Item Description
Position: 490
Loop: SLN 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.
4 If PID08 is present, then PID04 is required.
5 If PID09 is present, then PID05 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: |
| ************************ Sample PID Segment ______________________ PID*F*08*VI*PP*SHIRT BLUE XL ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | PID01 | 349 | Item Description Type | M |
| ID 1/1 | ||||
| Code indicating the format of a description |
| ||||||||
| F |
| Free-form |
| ||||||
| S |
| Structured (From Industry Code List) |
| ||||||
| X |
| Semi-structured (Code and Text) |
| ||||||
| PID02 | 750 | Product/Process Characteristic Code | O |
| ID 2/3 | ||||
| Code identifying the general class of a product or process characteristic |
| ||||||||
| 08 |
| Product |
| ||||||
| 73 |
| Vendor color description |
| ||||||
| 74 |
| Vendor size description |
| ||||||
| PID03 | 559 | Agency Qualifier Code | X |
| ID 2/2 | ||||
| Code identifying the agency assigning the code values |
| ||||||||
| VI |
| Voluntary Inter-Industry Commerce Standard (VICS) EDI |
| ||||||
| PID04 | 751 | Product Description Code | X |
| AN 1/12 | ||||
| A code from an industry code list which provides specific data about a product characteristic |
| ||||||||
| PP |
| Prepack |
| ||||||
| PID05 | 352 | Description | X |
| AN 1/80 | ||||
| A free-form description to clarify the related data elements and their content |
| ||||||||
Segment: CTT Transaction Totals
Position: 010
Loop: CTT Mandatory
Level: Summary
Usage: Mandatory
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: |
| ************************ Sample CTT Segment _____________________ CTT*12*137 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | CTT01 | 354 | Number of Line Items | M |
| N0 1/6 | |
| Total number of line items in the transaction set |
| |||||
| CTT02 | 347 | Hash Total | O |
| R 1/10 | |
| 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: 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: |
| ************************ Sample SE Segment ___________________ SE*2*0011 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | SE01 | 96 | Number of Included Segments | M |
| N0 1/10 | |
| Total number of segments included in a transaction set including ST and SE segments |
| |||||
M | SE02 | 329 | Transaction Set Control Number | M |
| AN 4/9 | |
| Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set |
| |||||
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article