Purchase Order 850
SDQ Format

Documentation

Untitled 850 Purchase Order - SDQ (Inbound) 
 
   
  Functional Group ID=PO
 
 
Introduction: 
 
This MARS Inc. Standard contains the format and establishes the data contents of the Inbound Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is 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 which, under ANSI X12 standard implementations, is not machine processable. 
 
 
 
 
Notes: 
 
  * is used as a data delimiter to separate and maintain element position.
 
  Codes listed below ID Fields are the only ones accepted by MARS Inc. ID Fields with invalid codes will be ignored or rejected.
 
                                                       
 
  Heading:
 
 
    Pos. Seg. Req. Loop   Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
  Must Use   010   ST   Transaction Set Header   M   1
  Must Use   020   BEG   Beginning Segment for Purchase Order   M   1
      050   REF   Reference Identification   O   >1
      080   FOB   F.O.B. Related Instructions   O   >1
        LOOP ID - SAC   25    
      120   SAC   Service, Promotion, Allowance, or Charge Information   O   1    
 
  Must Use   130   ITD   Terms of Sale/Deferred Terms of Sale   M   >1
      150   DTM   Date/Time Reference   O   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    
  Must Use   310   N1   Name   M   1    
 
 
  Detail:
 
 
    Pos. Seg. Req. Loop   Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
        LOOP ID - PO1   100000    
  Must Use   010   PO1   Baseline Item Data   M   1   n1    
        LOOP ID - SAC   25      
      130   SAC   Service, Promotion, Allowance, or Charge Information   O   1      
   
      190   SDQ   Destination Quantity   O   500    
 
 
  Summary:
 
 
    Pos. Seg. Req. Loop   Notes and
  No. ID Name Des. Max.Use Repeat Comments
 
        LOOP ID - CTT   1    
  Must Use   010   CTT   Transaction Totals   M   1   n2    
 
  Must Use   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:   Example: 
 
ST*850*10001001 
 
The Transaction Set Identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition. 
 
850 is the code used to identify the Purchase Order Transaction Set.
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   ST01   143   Transaction Set Identifier Code   M   ID 3/3
      Code uniquely identifying a Transaction Set
     
      850 X12.1 Purchase Order
 
  >>   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
      ST Control Number must be the same as the Control Number (SE02) in the SE segment.

           
  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:   Example: 
 
BEG*00*SA*40146**20010129 
 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   BEG01   353   Transaction Set Purpose Code   M   ID 2/2
      Code identifying purpose of transaction set
     
      00 Original
      06   Confirmation
 
  >>   BEG02   92   Purchase Order Type Code   M   ID 2/2
      Code specifying the type of Purchase Order
     
      BK Blanket Order (Quantity Firm)
      CF   Confirmation
      NE   New Order
      SA   Stand-alone Order
 
  >>   BEG03   324   Purchase Order Number   M   AN 1/22
      Identifying number for Purchase Order assigned by the orderer/purchaser
  >>   BEG05   373   Date   M   DT 8/8
      Date expressed as CCYYMMDD
      Purchase Order Date

           
  Segment:   REF Reference Identification
  Position:   050
  Loop:
  Level:   Heading
  Usage:   Optional
  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:   Example: 
 
REF*BK*123456 
 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   REF01   128   Reference Identification Qualifier   M   ID 2/3
      Code qualifying the Reference Identification
     
      BK Broker's Order Number
      BR   Broker or Sales Office Number
      DP   Department 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
      Broker Memo Number 
Broker Number 
Customer 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:   Example: 
 
FOB*PB
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   FOB01   146   Shipment Method of Payment   M   ID 2/2
      Code identifying payment terms for transportation charges
     
      PB Customer Pick-up/Backhaul
      PP   Prepaid (by Seller)
      PU   Pickup
 

           
  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:   Example: 
 
SAC*A*F340**********02
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   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
 
      SAC02   1300   Service, Promotion, Allowance, or Charge Code   X   ID 4/4
      Code identifying the service, promotion, allowance, or charge
     
      F340 Pick/Up
      F800   Promotional Allowance
 
      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
 

           
  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:   Example: 
 
ITD*03*3*2**10**30 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
      ITD01   336   Terms Type Code   O   ID 2/2
      Code identifying type of payment terms
     
      03 Fixed Date
 
  >>   ITD02   333   Terms Basis Date Code   M   ID 1/2
      Code identifying the beginning of the terms period
     
      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
      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
  >>   ITD07   386   Terms Net Days   M   N0 1/3
      Number of days until total invoice amount is due (discount not applicable)

           
  Segment:   DTM Date/Time Reference
  Position:   150
  Loop:
  Level:   Heading
  Usage:   Optional
  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:   Example: 
 
DTM*002*20010129 
 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   DTM01   374   Date/Time Qualifier   M   ID 3/3
      Code specifying type of date or time, or both date and time
     
      001 Cancel After
      002   Delivery Requested
      010   Requested Ship
      037   Ship Not Before
      038   Ship No Later
 
      DTM02   373   Date   X   DT 8/8
      Date expressed as CCYYMMDD

           
  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:   Example: 
 
TD5****M*CARRIER NAME 
 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
      TD504   91   Transportation Method/Type Code   X   ID 1/2
      Code specifying the method or type of transportation for the shipment
     
      H Customer Pickup
      M   Motor (Common Carrier)
 
      TD505   387   Routing   X   AN 1/35
      Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

           
  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:   Example: 
 
N9*ZZ*SPECIAL INSTRUCTIONS
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   N901   128   Reference Identification Qualifier   M   ID 2/3
      Code qualifying the Reference Identification
      Refer to 004010X12 Data Element Dictionary for acceptable code values.
      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

           
  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:   Example: 
 
MSG*SPECIAL INSTRUCTIONS 
MSG*DELIVERY INSTRUCTIONS 
 
The MSG segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. The use of the MSG segment should therefore be avoided, if at all possible, in an automated environment. 
 
M&M MARS' application system will process ONLY SEVENTEEN MSG segments.
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   MSG01   933   Free-Form Message Text   M   AN 1/264
      Free-form message text

           
  Segment:   N1 Name
  Position:   310
  Loop:   N1 Mandatory
  Level:   Heading
  Usage:   Mandatory
  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:   Example: 
 
N1*ST*SHIPTO NAME*9*1234567890123 
 
The MARS Standards are that the N1 Segment for the "SHIP TO" is Mandantory, any other N1 Segment is Optional. 
 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   N101   98   Entity Identifier Code   M   ID 2/3
      Code identifying an organizational entity, a physical location, property or an individual
     
      BO Broker or Sales Office
      BS   Bill and Ship To
      BY   Buying Party (Purchaser)
      ST   Ship To
 
      N102   93   Name   X   AN 1/60
      Free-form name
      N103   66   Identification Code Qualifier   X   ID 1/2
      Code designating the system/method of code structure used for Identification Code (67)
     
      9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix
 
      N104   67   Identification Code   X   AN 2/80
      Code identifying a party or other code

           
  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:   Example: 
 
PO1*1*10*CA*2.00**UA*00400004168 
 
While our EDI translation software can handle up to 565 items, our application systems CAN NOT currently PROCESS purchase orders containing more than 99 lines. Your order will be REJECTED by our application systems or EXCESSIVE Items will be BYPASSED. 
 
We. require that the UPC code is used for all items ordered. The Vendor Item Number and Customer Item Number are optional.
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
      PO101   350   Assigned Identification   O   AN 1/20
      Alphanumeric characters assigned for differentiation within a transaction set
  >>   PO102   330   Quantity Ordered   M   R 1/15
      Quantity ordered
  >>   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
     
      BA Bale
      BG   Bag
      CA   Case
      PL   Pallet/Unit Load
 
  >>   PO104   212   Unit Price   M   R 1/17
      Price per unit of product, service, commodity, etc.
  >>   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)
     
      UA U.P.C./EAN Case Code (2-5-5)
      UI   U.P.C. Consumer Package Code (1-5-5)
      UN   U.P.C. Case Code Number (1-1-5-5)
      UP   U.P.C. Consumer Package Code (1-5-5-1)
 
  >>   PO107   234   Product/Service ID   M   AN 1/48
      Identifying number for a product or service
      Manufacturer's Codes 
 
M&M/ MARS 
Confectionery 40000 + 5 digit item number 
COMBOs 41419 + 5 digit item number 
Frozen 47677 + 5 digit item number 
Chupa Chups 76350 + 5 digit item number 
 
Kal Kan 23100 + 5 digit item number 
 
Uncle Ben's 54800 + 5 digit item number 
      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
      IN   Buyer's Item Number
      PI   Purchaser's Item Code
      VN   Vendor's (Seller's) Item Number
 
      PO109   234   Product/Service ID   X   AN 1/48
      Identifying number for a product or service
      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)
      Same values as PO108.
     
 
      PO111   234   Product/Service ID   X   AN 1/48
      Identifying number for a product or service
      Same values as PO109.
      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)
      Same values as PO108.
     
 
      PO113   234   Product/Service ID   X   AN 1/48
      Identifying number for a product or service
      Same values as PO109.
      PO114   235   Product/Service ID Qualifier   X   ID 2/2
      Code identifying the type/source of the descriptive number used in Product/Service ID (234)
      Same values as PO108.
      Refer to 004010X12 Data Element Dictionary for acceptable code values.
      PO115   234   Product/Service ID   X   AN 1/48
      Identifying number for a product or service
      Same values as PO109.

           
  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:   Example: 
 
SAC*A*F800******10.25****02*ABC123 
 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   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
 
      SAC02   1300   Service, Promotion, Allowance, or Charge Code   X   ID 4/4
      Code identifying the service, promotion, allowance, or charge
     
      F340 Pick/Up
      F800   Promotional Allowance
 
      SAC08   118   Rate   O   R 1/9
      Rate expressed in the standard monetary denomination for the currency specified
      SAC12   331   Allowance or Charge Method of Handling Code   O   ID 2/2
      Code indicating method of handling for an allowance or charge
     
      01 Bill Back
      02   Off Invoice
 
      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

           
  Segment:   SDQ Destination Quantity
  Position:   190
  Loop:   PO1 Mandatory
  Level:   Detail
  Usage:   Optional
  Max Use:   500
  Purpose: To specify destination and quantity detail
  Syntax Notes:   1   If either SDQ05 or SDQ06 is present, then the other is required.
      2   If either SDQ07 or SDQ08 is present, then the other is required.
      3   If either SDQ09 or SDQ10 is present, then the other is required.
      4   If either SDQ11 or SDQ12 is present, then the other is required.
      5   If either SDQ13 or SDQ14 is present, then the other is required.
      6   If either SDQ15 or SDQ16 is present, then the other is required.
      7   If either SDQ17 or SDQ18 is present, then the other is required.
      8   If either SDQ19 or SDQ20 is present, then the other is required.
      9   If either SDQ21 or SDQ22 is present, then the other is required.
Semantic Notes:   1 SDQ23 identifies the area within the location identified in SDQ03, SDQ05, SDQ07, SDQ09, SDQ11, SDQ13, SDQ15, SDQ17, SDQ19, and SDQ21.
Comments:   1 SDQ02 is used only if different than previously defined in the transaction set.
    2 SDQ03 is the store number.
    3 SDQ23 may be used to identify areas within a store, e.g., front room, back room, selling outpost, end aisle display, etc. The value is agreed to by trading partners or industry conventions.
  Notes:   Example: 
 
SDQ*CA*92*0001*100*0002*100*0003*100 
 
Store Quantity totals must add up to Quantity Ordered specified in the preceding PO1 segment.
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   SDQ01   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
     
      CA Case
 
      SDQ02   66   Identification Code Qualifier   O   ID 1/2
      Code designating the system/method of code structure used for Identification Code (67)
     
      92 Assigned by Buyer or Buyer's Agent
 
  >>   SDQ03   67   Identification Code   M   AN 2/80
      Code identifying a party or other code
  >>   SDQ04   380   Quantity   M   R 1/15
      Numeric value of quantity
      SDQ05   67   Identification Code   X   AN 2/80
      Code identifying a party or other code
      SDQ06   380   Quantity   X   R 1/15
      Numeric value of quantity
      SDQ07   67   Identification Code   X   AN 2/80
      Code identifying a party or other code
      SDQ08   380   Quantity   X   R 1/15
      Numeric value of quantity
      SDQ09   67   Identification Code   X   AN 2/80
      Code identifying a party or other code
      SDQ10   380   Quantity   X   R 1/15
      Numeric value of quantity
      SDQ11   67   Identification Code   X   AN 2/80
      Code identifying a party or other code
      SDQ12   380   Quantity   X   R 1/15
      Numeric value of quantity
      SDQ13   67   Identification Code   X   AN 2/80
      Code identifying a party or other code
      SDQ14   380   Quantity   X   R 1/15
      Numeric value of quantity

           
  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:   Example: 
 
CTT*1**10*LB 
 
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   CTT01   354   Number of Line Items   M   N0 1/6
      Total number of line items in the transaction set
      CTT03   81   Weight   X   R 1/10
      Numeric value of weight

           
  Segment:   SE Transaction Set Trailer
  Position:   030
  Loop:
  Level:   Summary
  Usage:   Mandatory
  Max Use:   1
  Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
  Syntax Notes:
  Semantic Notes:
Comments:   1 SE is the last segment of each transaction set.
  Notes:   Example: 
 
SE*29*100010001 
 
SE is the last segment of each transaction set.
 
Data Element Summary 
                               
      Ref.   Data
    Des.   Element   Name   Attributes
  >>   SE01   96   Number of Included Segments   M   N0 1/10
      Total number of segments included in a transaction set including ST and SE segments
  >>   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
      SE Control Number must be the same as the Control Number (ST02) in the ST segment.

Back     Home