**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
810
Invoice
Version 4010
Revised: August 2019
Change Log
Date | Change | Comments |
November 2020 | Converted from .pdf to .docx file format | Changes to file format only – no change to content. |
September 2017 | Added new PO format to the BIG 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 IT1 segment. |
|
April 2016 | Removed Target.com specific references. | Throughout document.
|
| Removed verbiage in the IT103 for Pharmacy partners to send “CA”. |
|
November 2014 | Added note for Target.com vendor to the ISS02. | The “CA” qualifier is not used by Target.com. |
April 2013 | Added verbiage to the IT103 for Pharmacy partners to send “CA”. | Pharmacy partners must send “CA” in the IT103. |
February 2013 | Added verbiage to the SAC05. | Monetary amount must be 10 cents or greater. Anything less than 10 cents will be rejected and will not feed into Target’s application system. Two decimal places are implied. Do not send a decimal point. |
August 2012 | Added note for Target.com to the IT103. | The “CA” qualifier is not used by Target.com. |
February 2012 | Corrected the SCAC in the CAD01. | Corrected from UPNS to UPSN. |
February 2011 | Added note for Target.com vendor to the IT103 | Target.com vendors must send “EA” in the IT103 field. |
810 Invoice
Functional Group ID=IN
Introduction:
This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) 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 billing for goods and services provided.
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 | BIG | Beginning Segment for Invoice | M | 1 |
|
|
|
|
|
|
|
|
| 030 | NTE | Note/Special Instruction | O | 100 |
|
|
|
|
|
|
|
|
Must Use | 050 | REF | Reference Identification | O | 12 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - N1 |
|
| 200 |
|
|
|
|
|
|
|
Must Use | 070 | N1 | Name | O | 1 |
|
|
|
|
|
|
|
|
| 090 | N3 | Address Information | O | 2 |
|
|
|
|
|
|
|
|
| 100 | N4 | Geographic Location | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Must Use | 130 | ITD | Terms of Sale/Deferred Terms of Sale | O | >1 |
|
|
|
|
|
|
|
|
Must Use | 140 | DTM | Date/Time Reference | O | 10 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - N9 |
|
| 1 |
|
|
|
|
|
|
|
| 240 | N9 | Reference Identification | O | 1 |
|
|
|
|
|
|
|
|
M | 250 | MSG | Message Text | M | 10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Detail:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
|
|
| LOOP ID - IT1 |
|
| 200000 |
|
|
|
|
|
|
|
Must Use | 010 | IT1 | Baseline Item Data (Invoice) | O | 1 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - PID |
|
| 1000 |
|
|
|
|
|
|
|
| 060 | PID | Product/Item Description | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 100 | PO4 | Item Physical Details | O | 1 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - SAC |
|
| 25 |
|
|
|
|
|
|
|
| 180 | SAC | Service, Promotion, Allowance, or Charge Information | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M | 010 | TDS | Total Monetary Value Summary | M | 1 |
|
|
|
|
|
|
|
|
Must Use | 030 | CAD | Carrier Detail | O | 1 |
|
|
|
|
|
|
|
|
|
|
| LOOP ID - SAC |
|
| 25 |
|
|
|
|
|
|
|
| 040 | SAC | Service, Promotion, Allowance, or Charge Information | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| LOOP ID - ISS |
|
| >1 |
|
|
|
|
|
|
|
Must Use | 060 | ISS | Invoice Shipment Summary | O | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Must Use | 070 | CTT | Transaction Totals | O | 1 |
| n1 |
|
|
|
|
|
|
M | 080 | SE | Transaction Set Trailer | M | 1 |
|
|
|
|
|
|
|
|
Transaction Set Notes
1. Number of line items (CTT01) is the accumulation of the number of IT1 segments. If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 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*810*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 |
| ||||||||
| 810 |
| Invoice |
| ||||||
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: BIG Beginning Segment for Invoice
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates
Syntax Notes:
Semantic Notes: 1 BIG01 is the invoice issue date.
2 BIG03 is the date assigned by the purchaser to purchase order.
3 BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.
Comments: 1 BIG07 is used only to further define the type of invoice when needed.
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 PO Format: 12345678909-1234
Sample BIG Segment _________________
BIG*20010306*1234567**0123-1234567-1234
NOTE: DSD vendors should add leading zeroes to the PO number to make it 7 digits.
New Purchase Order Number Format:
BIG*20010306*1234567**12345678909-1234
************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | BIG01 | 373 | Date | M |
| DT 8/8 | ||||
| Date expressed as CCYYMMDD |
| ||||||||
| Invoice issue date. |
| ||||||||
M | BIG02 | 76 | Invoice Number | M |
| AN 1/22 | ||||
| Identifying number assigned by issuer |
| ||||||||
| Note: Invoice numbers must not be more than 19 characters long. Invoice numbers may contain alphas but no special characters. Alpha characters must be in upper case.
|
| ||||||||
| BIG03 | 373 | Date | O |
| DT 8/8 | ||||
| Date expressed as CCYYMMDD |
| ||||||||
| Not used by Target |
| ||||||||
Must Use | BIG04 | 324 | Purchase Order Number | O |
| AN 1/22 | ||||
| Identifying number for Purchase Order assigned by the orderer/purchaser |
| ||||||||
| This field is required. Send the same number here that was received on the 850 PO in element BEG03. The purchase order number will be formatted either as SSSS-PPPPPPP-LLLL (17 characters) or SSSS-PPPPPPP (12 characters).
SSSS = Source code, PPPPPPP = PO number, LLLL = Location ID Code
New Purchase Order Number Format: 12345678901-1234
|
| ||||||||
| BIG05 | 328 | Release Number | O |
| AN 1/30 | ||||
| Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction |
| ||||||||
| Not used by Target |
| ||||||||
| BIG06 | 327 | Change Order Sequence Number | O |
| AN 1/8 | ||||
| Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set |
| ||||||||
| Not used by Target |
| ||||||||
| BIG07 | 640 | Transaction Type Code | O |
| ID 2/2 | ||||
| Code specifying the type of transaction |
| ||||||||
| The "DO" code is required for Drop Ship to Guest Home. N1, N3 and N4 are also required for this situation.
**All other invoices (credit, display, samples, freight only, pallets, etc.) must be on paper and mailed to the appropriate area. |
| ||||||||
| DO |
| Drop Shipment Invoice |
| ||||||
Segment: NTE Note/Special Instruction
Position: 030
Loop:
Level: Heading
Usage: Optional
Max Use: 100
Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction
Syntax Notes:
Semantic Notes:
Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine process able. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.
Notes: |
| ************************ Sample NTE Segment ___________________
NTE*CER*Free Form Text ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
| NTE01 | 363 | Note Reference Code | O |
| ID 3/3 | ||||
| Code identifying the functional area or purpose for which the note applies |
| ||||||||
| CER |
| Certification Narrative |
| ||||||
| Any notes associated with the certification involved |
| ||||||||
M | NTE02 | 352 | Description | M |
| AN 1/80 | ||||
| A free-form description to clarify the related data elements and their content |
| ||||||||
Segment: REF Reference Identification
Position: 050
Loop:
Level: Heading
Usage: Optional (Must Use)
Max Use: 12
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: |
| ************************ Two occurrences must be sent, where REF01 = IA & DP.
Sample REF Segment _____________________
REF*IA*1234567
REF*DP*023
REF*PD*9876543210 (Send only if received on the PO) ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | REF01 | 128 | Reference Identification Qualifier | M |
| ID 2/3 | ||||
| Code qualifying the Reference Identification |
| ||||||||
| DP |
| Department Number |
| ||||||
| IA |
| Internal Vendor Number |
| ||||||
| PD |
| Promotion/Deal Number |
| ||||||
Must Use | 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 |
| ||||||||
| IA = Vendor Number. Vendor number must be 7 digits. Add leading zeroes to make 7 digits. PD = Promotion/Deal Number DP = Department Note: Department must be 3 digits. Add leading zero(s) to make 3 digits. |
| ||||||||
Segment: N1 Name
Position: 070
Loop: N1 Optional (Must Use)
Level: Heading
Usage: Optional (Must Use)
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: |
| ************************ One occurrence of the N1 must be sent, where N101 = BY or BS (Common Predistro). ST used for Drop Ship to Guest Home or when CAD01 = C.
Sample N1 Segment _________________
N1*BY**92*0551
N1*BY**92*1001 (Bill To) N1*ST**92*9998 (Direct Ship to Guest)
N1*BS**92*3902 (Predistro - packed and marked for store, but shipped to DC)
************************ |
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 |
| |||||||||
| BS |
| Bill and Ship To |
| |||||||
| BY |
| Buying Party (Purchaser) |
| |||||||
| SF |
| Ship From |
| |||||||
| ST |
| Ship To |
| |||||||
| N102 | 93 | Name | X |
| AN 1/60 | |||||
| Free-form name |
| |||||||||
| Not used by Target |
| |||||||||
| N103 | 66 | Identification Code Qualifier | X |
| ID 1/2 | |||||
| Code designating the system/method of code structure used for Identification Code (67) |
| |||||||||
| 91 |
| Assigned by Seller or Seller's Agent |
| |||||||
| Used when N101 = SF. |
| |||||||||
| 92 |
| Assigned by Buyer or Buyer's Agent |
| |||||||
| N104 | 67 | Identification Code | X |
| AN 2/80 | |||||
| Code identifying a party or other code |
| |||||||||
| A list of Target location codes may be found on the Partners Online website. |
| |||||||||
Segment: N3 Address Information
Position: 090
Loop: N1 Optional (Must Use)
Level: Heading
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party
Syntax Notes:
Semantic Notes:
Comments:
Notes: |
| ************************ Sample N3 Segment __________________ N3*Main St.
Send this segment when the invoice is for a Drop Ship to the Guest's home. ************************ |
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: 100
Loop: N1 Optional (Must Use)
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: |
| ************************ Sample N4 Segment _________________ N4*Hometown*MN*55402
Send this segment when the invoice is for a Drop Ship to the Guest's home.
Send only if sending the N3. ************************ |
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) |
| |||||
Segment: ITD Terms of Sale/Deferred Terms of Sale
Position: 130
Loop:
Level: Heading
Usage: Optional (Must Use)
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 Segment __________________ For Target Store only: ITD*01*2*****30 (with no discount, use elements 01, 02 and 07) ITD*02*2*8**34 (with discount, use elements 01, 02, 03 and 05)
************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use | ITD01 | 336 | Terms Type Code | O |
| ID 2/2 | |||||
| Code identifying type of payment terms |
| |||||||||
| 01 |
| Basic |
| |||||||
| 02 |
| End of Month (EOM) |
| |||||||
| When this code is used, ITD07 should NOT be sent. |
| |||||||||
| 14 |
| Previously agreed upon |
| |||||||
| Not used by Target at this time. |
| |||||||||
Must Use | ITD02 | 333 | Terms Basis Date Code | O |
| 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 |
| |||||||||
| ITD04 | 370 | Terms Discount Due Date | X |
| DT 8/8 | |||||
| Date payment is due if discount is to be earned expressed in format CCYYMMDD |
| |||||||||
| Not used by Target. |
| |||||||||
| 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 |
| |||||||||
| ITD06 | 446 | Terms Net Due Date | O |
| DT 8/8 | |||||
| Date when total invoice amount becomes due expressed in format CCYYMMDD |
| |||||||||
| Not used by Target. |
| |||||||||
| ITD07 | 386 | Terms Net Days | O |
| N0 1/3 | |||||
| Number of days until total invoice amount is due (discount not applicable) |
| |||||||||
| ITD08 | 362 | Terms Discount Amount | O |
| N2 1/10 | |||||
| Total amount of terms discount |
| |||||||||
Segment: DTM Date/Time Reference
Position: 140
Loop:
Level: Heading
Usage: Optional (Must Use)
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: |
| ************************ Sample DTM Segment __________________
DTM*011*20020205 ************************ |
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 |
| ||||||||
| 011 |
| Shipped |
| ||||||
Must Use | DTM02 | 373 | Date | X |
| DT 8/8 | ||||
| Date expressed as CCYYMMDD |
| ||||||||
| Date Merchandise was shipped. |
| ||||||||
Segment: N9 Reference Identification
Position: 240
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: |
| Sample N9 segment _________________ N9*ZZ*PACA
This segment used only when the MSG segment is present. ___________________ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | N901 | 128 | Reference Identification Qualifier | M |
| ID 2/3 | ||||
| Code qualifying the Reference Identification |
| ||||||||
| 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 |
| ||||||||
| PACA |
| ||||||||
Segment: MSG Message Text
Position: 250
Loop: N9 Optional
Level: Heading
Usage: Mandatory
Max Use: 10
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: |
| NOTE: This segment is NOT required by Target. If the N9 loop is included, then this segment must be sent.
The MSG segment is used to send the Perishable Agricultural Commodities Act (PACA) "trust statement". One MSG segment will be sent for each line of text as follows:
MSG*The perishable agricultural commodities listed on this MSG*invoice are sold subject to the statutory trust authorized MSG*by Section 5(c) of the Perishable Agricultural Commodities MSG*Act, 1930 (7 U.S.C. 4993(c)). The seller of these MSG*commodities retains a trust claim over these commodities, MSG*all inventories of food or other products derived from MGS*these commodities, and any receivables or proceeds from MSG*the sale of these commodities until full payment is MSG*received. |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | MSG01 | 933 | Free-Form Message Text | M |
| AN 1/264 | |
| Free-form message text |
| |||||
| MSG*The perishable agricultural commodities listed on this MSG*invoice are sold subject to the statutory trust authorized MSG*by Section 5(c) of the Perishable Agricultural Commodities MSG*Act, 1930 (7 U.S.C. 4993(c)). The seller of these MSG*commodities retains a trust claim over these commodities, MSG*all inventories of food or other products derived from MGS*these commodities, and any receivables or proceeds from MSG*the sale of these commodities until full payment is MSG*received. |
| |||||
Segment: IT1 Baseline Item Data (Invoice)
Position: 010
Loop: IT1 Optional (Must Use)
Level: Detail
Usage: Optional (Must Use)
Max Use: 1
Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions
Syntax Notes: 1 If any of IT102 IT103 or IT104 is present, then all are required.
2 If either IT106 or IT107 is present, then the other is required.
3 If either IT108 or IT109 is present, then the other is required.
4 If either IT110 or IT111 is present, then the other is required.
5 If either IT112 or IT113 is present, then the other is required.
6 If either IT114 or IT115 is present, then the other is required.
7 If either IT116 or IT117 is present, then the other is required.
8 If either IT118 or IT119 is present, then the other is required.
9 If either IT120 or IT121 is present, then the other is required.
10 If either IT122 or IT123 is present, then the other is required.
11 If either IT124 or IT125 is present, then the other is required.
Semantic Notes: 1 IT101 is the purchase order line item identification.
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 IT106 through IT125 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 sending it back on inbound EDI documents.
Sample IT1 Segment _________________ IT1**50*EA*1.49**CB*058020714*UP*123456789012
When sending a substitution (must be pre-approved by the Buyer) please follow these instructions: Send the substitute item info in the IT1 segment. The original item should not be included in the 810.
************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
| IT101 | 350 | Assigned Identification | O |
| AN 1/20 | |||||
| Alphanumeric characters assigned for differentiation within a transaction set |
| |||||||||
Must Use | IT102 | 358 | Quantity Invoiced | X |
| R 1/10 | |||||
| Number of units invoiced (supplier units) |
| |||||||||
Must Use | IT103 | 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 |
| |||||||||
| The UOM should match the UOM received on the PO. The value in the ISS02 must be the same as this value. |
| |||||||||
| CA |
| Case |
| |||||||
| EA |
| Each |
| |||||||
| LB |
| Pound |
| |||||||
Must Use | IT104 | 212 | Unit Price | X |
| R 1/17 | |||||
| Price per unit of product, service, commodity, etc. |
| |||||||||
| Target only reads out five places after the decimal point, sending more than 5 places can result in a fatal error. |
| |||||||||
| IT105 | 639 | Basis of Unit Price Code | O |
| ID 2/2 | |||||
| Code identifying the type of unit price for an item |
| |||||||||
| Not used by Target |
| |||||||||
Must Use | IT106 | 235 | Product/Service ID Qualifier | X |
| ID 2/2 | |||||
| Code identifying the type/source of the descriptive number used in Product/Service ID (234) |
| |||||||||
| Either a CB or UP or UI or EN must be sent. |
| |||||||||
| CB |
| Buyer's Catalog Number |
| |||||||
| EN |
| European Article Number (EAN) (2-5-5-1) |
| |||||||
| EO |
| EAN/UCC - 8 |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UI |
| U.P.C. Consumer Package Code (1-5-5) |
| |||||||
| To be used by direct to store delivery beverage vendors only. |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
Must Use | IT107 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| IT108 | 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 |
|
|
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UI |
| U.P.C. Consumer Package Code (1-5-5) |
| |||||||
| To be used by direct to store delivery beverage vendors only. |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| IT109 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
| IT110 | 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 |
| |||||||
| IN |
| Buyer's Item Number |
| |||||||
| Target Corporation Item Number (TCIN) |
| |||||||||
| UI |
| U.P.C. Consumer Package Code (1-5-5) |
| |||||||
| To be used by direct to store delivery beverage vendors only. |
| |||||||||
| UP |
| U.P.C. Consumer Package Code (1-5-5-1) |
| |||||||
| IT111 | 234 | Product/Service ID | X |
| AN 1/48 | |||||
| Identifying number for a product or service |
| |||||||||
Segment: PID Product/Item Description
Position: 060
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***BLUE XL
Description of Item. This helps better define your product. Please send this segment if DPCI/TCIN doesn't fully describe your product. ************************ |
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 |
| ||||||
| PID02 | 750 | Product/Process Characteristic Code | O |
| ID 2/3 | ||||
| Code identifying the general class of a product or process characteristic |
| ||||||||
| 08 |
| Product |
| ||||||
| PID03 | 559 | Agency Qualifier Code | X |
| ID 2/2 | ||||
| Code identifying the agency assigning the code values |
| ||||||||
| Not used by Target |
| ||||||||
| PID04 | 751 | Product Description Code | X |
| AN 1/12 | ||||
| A code from an industry code list which provides specific data about a product characteristic |
| ||||||||
| Not used by Target |
| ||||||||
Must Use | 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: 100
Loop: IT1 Optional (Must Use)
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: |
| ************************ Sample PO4 Segment ____________________
PO4*12 (no inner packs)
PO4*6*******************4 (inner packs) ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use | PO401 | 356 | Pack | O |
| 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 |
| |||||
| 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 |
| |||||
Segment: SAC Service, Promotion, Allowance, or Charge Information
Position: 180
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 Segment ______________________
SAC*A*C310***1542 ************************ |
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 |
| ||||||||
| A |
| Allowance |
| ||||||
| C |
| Charge |
| ||||||
Must Use | SAC02 | 1300 | Service, Promotion, Allowance, or Charge Code | X |
| ID 4/4 | ||||
| Code identifying the service, promotion, allowance, or charge |
| ||||||||
| Below is a list of the most common codes. B950 Damaged Merchandise C310 Discount D170 Free Goods D270 Fuel Surcharge F800 Promotional Allowance H000 Special Allowance H090 Special Handling H700 Tax - Local Tax CRV - Container Redemption (bottle deposit) H750 State and Local Tax |
| ||||||||
| 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 |
| ||||||
Must Use | SAC05 | 610 | Amount | O |
| N2 1/15 | ||||
| Monetary amount |
| ||||||||
| Monetary amount must be 10 cents or greater. Anything less than 10 cents will be rejected and will not feed into Target's application system. Two decimal places are implied, do not send a decimal point. |
| ||||||||
| SAC06 | 378 | Allowance/Charge Percent Qualifier | X |
| ID 1/1 | ||||
| Code indicating on what basis allowance or charge percent is calculated |
| ||||||||
| SAC07 | 332 | Percent | X |
| R 1/6 | ||||
| Percent expressed as a percent |
| ||||||||
| 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 |
| ||||||||
| EA |
| Each |
| ||||||
| SAC10 | 380 | Quantity | X |
| R 1/15 | ||||
| Numeric value of quantity |
| ||||||||
| When SAC02 = D170, this data element is required and should contain the quantity of free goods. SAC09 should contain the unit of measure of the free goods. |
| ||||||||
| 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 |
| ||||||||
| 02 |
| Off Invoice |
| ||||||
| 06 |
| Charge to be Paid by Customer |
| ||||||
| 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 |
| ||||||||
| Not used by Target |
| ||||||||
| SAC14 | 770 | Option Number | O |
| AN 1/20 | ||||
| A unique number identifying available promotion or allowance options when more than one is offered |
| ||||||||
| Not used by Target |
| ||||||||
| SAC15 | 352 | Description | X |
| AN 1/80 | ||||
| A free-form description to clarify the related data elements and their content |
| ||||||||
Segment: TDS Total Monetary Value Summary
Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To specify the total invoice discounts and amounts
Syntax Notes:
Semantic Notes: 1 TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
2 TDS02 indicates the amount upon which the terms discount amount is calculated.
3 TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).
4 TDS04 indicates the total amount of terms discount.
Comments: 1 TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
Notes: |
| ************************ Sample TDS Segment __________________ TDS*53000
2 Decimal places implied - do NOT send a decimal point in the TDS01 or 02 ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
M | TDS01 | 610 | Amount | M |
| N2 1/15 | |
| Monetary amount |
| |||||
| Total amount of invoice (including charges, less allowances) before terms discount. |
| |||||
| TDS02 | 610 | Amount | O |
| N2 1/15 | |
| Monetary amount |
| |||||
| Total amount of merchandise. If you offer a discount on gross amount before allowances, this field is required. Otherwise it is not needed. |
| |||||
Segment: CAD Carrier Detail
Position: 030
Loop:
Level: Summary
Usage: Optional (Must Use)
Max Use: 1
Purpose: To specify transportation details for the transaction
Syntax Notes: 1 At least one of CAD05 or CAD04 is required.
2 If CAD07 is present, then CAD08 is required.
Semantic Notes:
Comments:
Notes: |
| ************************ Sample CAD Segment ____________________
CAD*M***RDWY***BM*12345678901234567
CAD*U***UPSN*UPS**CN*123456
CAD*P***SELF***CN*123456 (Direct Store Delivery vendors may use "SELF" in the CAD04, if the vendor does not have a SCAC code assigned by the National Freight Traffic Association (NFTA))
------------------------------------------------------------------------------------- Transportation Method Type CAD01 CAD07
Consolidation C BM Bill of Lading #
_________________ ___________________ TL or LTL M BM Bill of Lading #
____________________________________ Private Parcel U CN Carrier Ref.#
___________________________________ Direct Store P CN Carrier Ref.# Delivery
************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use | CAD01 | 91 | Transportation Method/Type Code | O |
| ID 1/2 | |||||
| Code specifying the method or type of transportation for the shipment |
| |||||||||
| C |
| Consolidation |
| |||||||
| Used for domestic consolidation |
| |||||||||
| M |
| Motor (Common Carrier) |
| |||||||
| used for larger quantity shipments |
| |||||||||
| P |
| Private Carrier |
| |||||||
| used for Direct Store Delivery (DSD) |
| |||||||||
| U |
| Private Parcel Service |
| |||||||
| Used for small package or small quantities. ONLY UPSN or FDEG may use this. |
| |||||||||
| CAD02 | 206 | Equipment Initial | O |
| AN 1/4 | |||||
| Prefix or alphabetic part of an equipment unit's identifying number |
| |||||||||
| Not used by Target |
| |||||||||
| CAD03 | 207 | Equipment Number | O |
| AN 1/10 | |||||
| Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred) |
| |||||||||
| Not used by Target |
| |||||||||
Must Use | CAD04 | 140 | Standard Carrier Alpha Code | X |
| ID 2/4 | |||||
| Standard Carrier Alpha Code |
| |||||||||
| CAD05 | 387 | Routing | X |
| AN 1/35 | |||||
| Free-form description of the routing or requested routing for shipment, or the originating carrier's identity |
| |||||||||
| CAD06 | 368 | Shipment/Order Status Code | O |
| ID 2/2 | |||||
| Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction |
| |||||||||
| Not used by Target |
| |||||||||
Must Use | CAD07 | 128 | Reference Identification Qualifier | O |
| ID 2/3 | |||||
| Code qualifying the Reference Identification |
| |||||||||
| A value is not required in the CAD07 for DSD vendors. |
| |||||||||
| BM |
| Bill of Lading Number |
| |||||||
| Required when shipping via motor carrier or consolidation. |
| |||||||||
| CN |
| Carrier's Reference Number (PRO/Invoice) |
| |||||||
| Required when shipping parcel package shipments. |
| |||||||||
Must Use | CAD08 | 127 | Reference Identification | X |
| AN 1/30 | |||||
| Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier |
| |||||||||
| A value is not required in the CAD08 for DSD vendors. |
| |||||||||
Segment: SAC Service, Promotion, Allowance, or Charge Information
Position: 040
Loop: SAC Optional
Level: Summary
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 Segment _____________________
SAC*C*D240***1500*******02***Freight Charge ************************ |
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 |
| ||||||||
| A |
| Allowance |
| ||||||
| C |
| Charge |
| ||||||
Must Use | SAC02 | 1300 | Service, Promotion, Allowance, or Charge Code | X |
| ID 4/4 | ||||
| Code identifying the service, promotion, allowance, or charge |
| ||||||||
| Below is a list of the most common codes. B950 Damaged Merchandise C310 Discount D170 Free Goods D270 Fuel Surcharge F800 Promotional Allowance H000 Special Allowance H090 Special Handling H700 Tax - Local Tax CRV - Container Redemption (bottle deposit) H750 State and Local Tax |
| ||||||||
| 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 |
| ||||||
Must Use | SAC05 | 610 | Amount | O |
| N2 1/15 | ||||
| Monetary amount |
| ||||||||
| Monetary amount must be 10 cents or greater. Anything less than 10 cents will be rejected and will not feed into Target's application system. Two decimal places are implied, do not send a decimal point. |
| ||||||||
| SAC06 | 378 | Allowance/Charge Percent Qualifier | X |
| ID 1/1 | ||||
| Code indicating on what basis allowance or charge percent is calculated |
| ||||||||
| 3 |
| Discount/Gross |
| ||||||
| SAC07 | 332 | Percent | X |
| R 1/6 | ||||
| Percent expressed as a percent |
| ||||||||
| 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 |
| ||||||||
| SAC11 | 380 | Quantity | O |
| R 1/15 | ||||
| Numeric value of quantity |
| ||||||||
| SAC12 | 331 | Allowance or Charge Method of Handling Code | O |
| ID 2/2 | ||||
| Code indicating method of handling for an allowance or charge |
| ||||||||
| 02 |
| Off Invoice |
| ||||||
| 06 |
| Charge to be Paid by Customer |
| ||||||
| 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 |
| ||||||||
| Not used by Target |
| ||||||||
| SAC14 | 770 | Option Number | O |
| AN 1/20 | ||||
| A unique number identifying available promotion or allowance options when more than one is offered |
| ||||||||
| Not used by Target |
| ||||||||
Must Use | SAC15 | 352 | Description | X |
| AN 1/80 | ||||
| A free-form description to clarify the related data elements and their content |
| ||||||||
Segment: ISS Invoice Shipment Summary
Position: 060
Loop: ISS Optional (Must Use)
Level: Summary
Usage: Optional (Must Use)
Max Use: 1
Purpose: To specify summary details of total items shipped in terms of quantity, weight, and volume
Syntax Notes: 1 At least one of ISS01 ISS03 or ISS05 is required.
2 If either ISS01 or ISS02 is present, then the other is required.
3 If either ISS03 or ISS04 is present, then the other is required.
4 If either ISS05 or ISS06 is present, then the other is required.
Semantic Notes: 1 ISS07 is the quantity of third party pallets.
2 ISS08 is the gross weight of third party pallets in pounds.
Comments:
Notes: |
| ************************ Target requires at least one occurrence of the ISS with the total number of eaches, pounds or cases (same UOM as found on the PO). If there are multiple units of measure in the invoice, an ISS should be sent with the total number of each unit of measure. . Sample ISS Segment ____________________ ISS*45*EA
ISS*60*EA*3*LB
When multiple units of measure occur in the invoice, send multiple ISS segments as in the following example: ISS*40*EA ISS*10*CA
Only ISS01 & ISS02 are mandatory. ISS03 & ISS04 may be sent. ************************ |
Data Element Summary
Ref. Data
Des. Element Name Attributes
Must Use | ISS01 | 382 | Number of Units Shipped | X |
| R 1/10 | ||||
| Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set |
| ||||||||
Must Use | ISS02 | 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 |
| ||||||||
| CA |
| Case |
| ||||||
| CT |
| Carton |
| ||||||
| EA |
| Each |
| ||||||
| LB |
| Pound |
| ||||||
| ISS03 | 81 | Weight | X |
| R 1/10 | ||||
| Numeric value of weight |
| ||||||||
| ISS04 | 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 |
| ||||||||
| LB |
| Pound |
| ||||||
Segment: CTT Transaction Totals
Position: 070
Loop:
Level: Summary
Usage: Optional (Must Use)
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*25 ************************ |
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 |
| |||||
Segment: SE Transaction Set Trailer
Position: 080
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*25*0001 ************************ |
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