qrs catalogue 2.0 edi 832 (v4010) mapping guide for vendors catalog srvs/qrs catalogue...

Click here to load reader

Post on 30-Jan-2021

2 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • QRS Catalogue 2.0

    EDI 832 (v4010) Mapping Guide For Vendors

    May 2003

  • QRS Catalogue 2.0 EDI 832 (v4010) Mapping Guide for Vendors

    1

    832 Price/Sales Catalogue (v4010) For QRS Catalogue Vendors

    Functional Group ID=SC Revision: This version of the mapping guide removes the G5513 data element and adds the G5514 and G5515 data elements. This Draft Standard for Trial Use contains the format and establishes the data contents of the Price/Sales Catalogue Transaction Set (832) 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 furnishing or requesting the price of goods or services in the form of a catalogue. 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 BCT Beginning Segment for Price/Sales Catalogue M 1 070 DTM Date/Time Reference O 10 090 CUR Currency O 1 LOOP ID - N1 >1 150 N1 Name O 1 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments

    LOOP ID - LIN >1 010 LIN Item Identification O 1 030 DTM Date/Time Reference O 10 060 CTB Restrictions/Conditions O 2 070 PID Product/Item Description O 200 110 TD4 Carrier Details (Special Handling, or

    Hazardous Materials, or Both) O 1

    140 LDT Lead Time O 1 165 TC2 Commodity O 2 168 G55 Item Characteristics - Consumer Unit O 1 LOOP ID - CTP 100 170 CTP Pricing Information O 1 LOOP ID - SLN >1 350 SLN Subline Item Detail O 1 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 CTT Transaction Totals M 1 n1 Must Use 020 SE Transaction Set Trailer M 1

  • QRS Catalogue 2.0 EDI 832 (v4010) Mapping Guide for Vendors

    2

    Transaction Set Notes 1. Number of line items (CTT01) is the accumulation of the number of LIN segments. Hash total (CTT02) is not

    used in this transaction.

  • QRS Catalogue 2.0 EDI 832 (v4010) Mapping Guide for Vendors

    3

    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:

    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 832 Price/Sales Catalogue >> 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 The number is sequentially assigned by the sender, starting with one within

    each functional group. For each functional group, the first transaction set control number will be 0001 and incremented by one for each additional transaction set within the group.

  • QRS Catalogue 2.0 EDI 832 (v4010) Mapping Guide for Vendors

    4

    Segment: BCT Beginning Segment for Price/Sales Catalogue Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of the Price/Sales Catalogue Transaction Set and specify

    catalogue purpose and number information Syntax Notes: Semantic Notes: Comments:

    Notes: BCT10 is used only to clarify, to the receiver, the sender's purpose of the transaction set. Code 13 is used to request catalogue information from the owner of the catalogue or the authorized agent, e.g., a third party catalogue service. Code 11 is used only when the transaction set is a reply to a specific request transaction. If the sender has a standing request from the receiver for specific data when a specific event takes place, e.g., women's tops, new products, every two weeks, this is NOT considered a response, in which case, nothing will be sent in BCT10. The recipient will only receive a response (BCT10 contains code 11) if the recipient had previously sent a request (BCT10 contains code 13). Codes 02, 03, 04, and 05 are to be used to update catalogue information kept by the user of the catalogue data, e.g., a retailer or the vendor's agent. Caution must be exercised when deleting a U.P.C. from the catalogue. Due to ordering and shipping cycle times, a U.P.C. should reside on the catalogue as discontinued at least one year after the last of the product has been shipped. Deleting the U.P.C. from the catalogue does not alter the minimum retention period (30 months for apparel and 48 months for all other items) as defined in the U.P.C. Data Communications Guidelines for General Merchandise and Apparel.

    QRS Note: New BCT segments should only be generated if the Selection Code or action code changes. This will decrease your IE traffic, as well as ensure that your data is processed efficiently.

    Data Element Summary

    Ref. Data Des. Element Name Attributes >> BCT01 683 Catalogue Purpose Code M ID 2/2 Code indicating purpose of catalogue RC Resale Catalogue U.P.C. Catalogue Data, Traditional Vendor's Catalogue,

    and Item Maintenance BCT02 684 Catalogue Number O AN 9/12 Identifying number for catalogue or superseded catalogue VENDOR ID as defined by U.P.C. Data Communications Guidelines for

    General Merchandise and Apparel Owner of the catalogue, generally the vendor ITEM MAINTENANCE: Reference number

    QRS Note: Only for Catalogue data - inbound and outbound. Catalogue Vendor ID, Inbound: (from the vendor's QRS Account Number)

  • QRS Catalogue 2.0 EDI 832 (v4010) Mapping Guide for Vendors

    5

    12 = Vendor ID is telephone number. You must send the full 12 digit account number. 01 = Vendor ID is Duns Number, you must send the 9 digit Duns number or full 12 digit account number. 08 = Vendor ID is UCC Comm ID. You must send the 10 digit UCC ID or full 12 digit account number. Catalogue Vendor ID, Outbound: You will receive a full 12 digit number for all account types.

    BCT03 685 Catalogue Version Number O AN 3/3 Identifying version number of catalogue or superseded catalogue SELECTION CODE as defined by U.P.C. Data Communications Guidelines

    for General Merchandise and Apparel

    BCT09 352 Description O AN 1/25 A free-form description to clarify the related data elements and their content SELECTION CODE DESCRIPTION as defined by U.P.C. Data

    Communications Guidelines for General Merchandise and Apparel

    QRS Note: QRS Catalogue will truncate the information to 25 characters on inbound transmissions.

    BCT10 353 Transaction Set Purpose Code O ID 2/2 Code identifying purpose of transaction set ACTION CODE as defined by U.P.C. Data Communications Guidelines for

    General Merchandise and Apparel 01 Cancellation Restricted use. See U.P.C. Data Communications

    Guidelines for General Merchandise and Apparel 02 Add 03 Delete 04 Change 05 Replace

  • QRS Catalogue 2.0 EDI 832 (v4010) Mapping Guide for Vendors

    6

    Segment: DTM Date/Time Reference Position: 070 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: The publication and expiration dates identify the exact period to which the data apply. One segment for each date. This segment will be used to specify the dates for all SKUs identified in the transaction. If a particular SKU has a different date, the DTM segment in the detail area will be used to override the date for that SKU only. Codes 196 and 197 specify the applicable dates for the prices specified in this transaction, e.g., effective date or expiration date.

    QRS Note: - The DTM segments are valid at both the header and detail level. When used at the header level, all following Products and Items will be assigned this date, unless the this date is overridden by use of at DTM segment at the detail level. Outbound they are generated only at the detail level. - Send Discontinue Dates and Cancellation Dates no earlier than one month prior to the actual processing date. If sent too early, the discontinue and canceled transactions will result in transaction errors.

    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 018 Available U.P.C. CATALOGUE: AVAILABLE DATE - First

    available ship date. Implies nothing abou