DSW 832 EDI Transaction (Price/Sales Catalog) Mapping Notes
DSW 832 EDI Transaction notes described in this blog contain those important for the usage of the Price/Sales Catalog Transaction Set within the context of an Electronic Data Interchange (EDI) environment. The DSW 832 EDI transaction set can be used to provide for customary and established business and industry practice relative to furnishing or requesting the price of goods or services in the form of a catalog. The DSW 832 EDI transaction notes listed below regard not to all segments in the document, but to those that have important notes to mention.
GS Functional Group Header
- GS04 is the group date
- GS05 is the group time
- The data interchange control number GS06 in the header must be identical to the same data element in the associated functional group trailer, GE02.
- A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.
ST Transaction Set Header
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
BCT Beginning Segment
- BCT02 should always be Vendor ISA ID or Agreed upon ID
- C0807 – If CUR08 is present, then CUR07 is required.
- C0907 – If CUR09 is present, then CUR07 is required.
- L101112 – If CUR10 is present, then at least one of CUR11 or CUR12 is required.
- C1110 – If CUR11 is present, then CUR10 is required.
- C1210 – If CUR12 is present, then CUR10 is required.
- L131415 – If CUR13 is present, then at least one of CUR14 or CUR15 is required.
- C1413 – If CUR14 is present, then CUR13 is required.
- C1513 – If CUR15 is present, then CUR13 is required.
- L161718 – If CUR16 is present, then at least one of CUR17 or CUR18 is required.
- C1716 – If CUR17 is present, then CUR16 is required.
- C1816 – If CUR18 is present, then CUR16 is required.
- L192021 – If CUR19 is present, then at least one of CUR20 or CUR21 is required.
- C2019 – If CUR20 is present, then CUR19 is required.
- C2119 – If CUR21 is present, then CUR19 is required.
Loop N1 – N1 Name
- R0203 – At least one of N102 or N103 is required.
- P0304 – If either N103 or N104 is present, then the other is required.
- 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.
- N105 and N106 further define the type of entity in N101.
Loop LIN – LIN Item Identification
- LIN01 is the line item identification
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- LIN08 SM qualified data must comply to NRF guidlines and only contain 50000 series for Item UPC data or 90000 series for Case-pack(Kit) UPC
Loop LIN – DTM Date/Time Reference
- R020305 – At least one of DTM02, DTM03 or DTM05 is required.
- C0403 – If DTM04 is present, then DTM03 is required.
- P0506 – If either DTM05 or DTM06 is present, then the other is required.
Loop LIN – PID Product/Item Description
- Use PID03 to indicate the organization that publishes the code list being referred to.
- PID04 should be used for industry-specific product description codes.
- 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.
- PID09 is used to identify the language being used in PID05.
- All three PID02 qualifiers and corresponding data are required.
Loop SLN – SLN Subline Item Detail
- 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.
- 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.
Interested in EDI mapping parctice? Sign up for advanced EDI trainings in your region.