X12 Implementation Guidelines For Inbound Price Catalog v (832I)

Similar documents
EDI Transaction Set 832 Price Sales Catalog X12 Version 4010

LOOP ID - N1 > N1 Party Identification M 1

832 Price/Sales Catalog

810 Invoice Version 4010

810 IBM Subset - Invoice From Supplier - (004010) 03/20/06

g Electronic Commerce Service Center

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SUPPLIER SHIP DIRECT (SSD) MISCELLANEOUS CHARGE INVOICE (810) TRANSACTION SET

Page Pos. Seg. Req. Loop Notes and No. No. ID Name Des. Max.Use Repeat Comments LOOP ID - CTT CTT Transaction Totals O 1 n2

850 IBM Subset - Sales Order To IBM - (004010)

810 Transaction 810 IBM Subset - Invoice From Supplier /2009

855 IBM Guideline - Sales Order Ack to Customer ) - 03/17/06

862 Shipping Schedule

850 IBM Guideline - Purchase Order to Supplier - (004010) 03/21/06

Electronic Components Industry Association Guideline. EDI Transaction Set 867 Product Transfer and Resale Report. X12 Version 4010

Pos. Seg. Req. Loop Notes and

810 Invoice. Introduction: Notes: Heading: Detail: Functional Group ID=IN

830 Planning Schedule with Release Capability

GENERAL MOTORS IMPLEMENTATION GUIDELINES FOR ANSI X12 TRANSACTION SET 840 REQUEST FOR QUOTATION

NAPM RAIL INDUSTRY FORUM PURCHASE ORDER IMPLEMENTATION GUIDELINE FOR EDI

X12 Implementation Guidelines For Outbound Purchase Order v2001 (850O)

860 IBM Subset - Sales Order Change To IBM - (004010)

GENERAL MOTORS IMPLEMENTATION GUIDELINES FOR ANSI X12 TRANSACTION SET 850 PURCHASE ORDER

Pittsburgh Glass Works. X Purchase Order Specifications

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR PURCHASE ORDER ACKNOWLEDGMENT (855) TRANSACTION SET

Land O'Lakes 875 Grocery Products Purchase Order

ARVINMERITOR P.O.'S 850 TRANSACTION SET WILL BE UTILIZED TO COMMUNICATE CONTRACTUAL INFORMATION REGARDING PART AND PRICE

Purchase Order/Garden Ridge - Trading Partner Specification

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT MATERIAL CLAIM (847) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR CONSIGNMENT SUPPLIER MATERIAL INVENTORY ADVICE (846) TRANSACTION SET

ISM RAIL INDUSTRY FORUM PURCHASE ORDER IMPLEMENTATION GUIDELINE FOR EDI

05/11/1998 Ingram Book Company Purchase Order INGRAM BOOK COMPANY Electronic Data Interchange Mapping Requirements PURCHASE ORDER (850)

850 Kimberly-Clark Corporation's Purchase Order (Apex Version)

1/6/2011 Purchase Order Table of Contents

810 Invoice Functional Group=IN

GENERAL MOTORS IMPLEMENTATION GUIDELINES FOR ANSI X12 TRANSACTION SET 860 PURCHASE ORDER CHANGE

ANSI version Shipping Schedule

843 Response to Request for Quotation

861 Receiving Advice/Acceptance Certificate

810 Invoice - ArvinMeritor CVS Oracle

ANSI X (Invoice) Outbound (from Eclipse) Version 4010

MOBIS Alabama RDC, LLC IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS INVOICE TRANSACTION SET (810) VERSION/RELEASE

850 Purchase Order. Introduction: Heading: Changes 5/2011: SCH11 Schedule line identifier

Price Sales Catalog. Transaction Set (832) (Outbound from TI) Draft Copy

340 N4 Geographic Location O >1 390 TD5 Carrier Details (Routing Sequence/Transit Time)

LOOP ID - IT IT1 Baseline Item Data (Invoice) M 1 LOOP ID - SAC SAC Service, Promotion, Allowance, or Charge Information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR TO DEALER PURCHASE ORDER (850) TRANSACTION SET

Inquiry/Advice 060 REF Reference Identification O 12. Detail: Pos.Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID LIN 10000

Evo.com 810 Invoice Publication: 8/1/2017 Modified: 8/2/2017 Current: 8/2/2017

856 Ship Notice/Manifest

865 Purchase Order Chg Ack 865 IBM Guideline - Sales Order Change Ack/Response To Customer - (004010) - 09/25/08

810 - INVOICE Specification and Vendor Reference Guide EDI ANSI X

852 Product Activity Data

ARMY & AIR FORCE EXCHANGE SERVICE 810 Invoice

Pittsburgh Glass Works. X Inventory/ Advice Specifications. PGW_846_Specs.docx 6/20/11 Page 1 of 14

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR PURCHASE ORDER (850) TRANSACTION SET

Bass Pro Shops 850 Purchase Order Outbound 850 Purchase Order Version VICS

820 Transaction 820 IBM Subset - Payment Order/Remittance Advice /2009. Pos. Seg. Req. Loop Notes and

850 Purchase Order vs 4010 Change Document

05/11/1998 Ingram Book Company Invoice INGRAM BOOK COMPANY Electronic Data Interchange Mapping Requirements INVOICE (810)

Agilent Technologies Company Guideline For Electronic Data Interchange Transaction Set 856 Advance Ship Notice/Manifest - Inbound

SHERWIN-WILLIAMS 810 Invoice

Inbound 846 (Inventory Inquiry/Advice) X12 Specification for Release

860 Purchase Order Change Request - Buyer Initiated

832 Price/Sales Catalog

856 Ship Notice/Manifest

862 Shipping Schedule

PACCAR Parts Division Electronic Invoices version /15/01

Rite Aid Corporation 860 DC Purchase Order Change Request - Buyer Initiated Version

Belk Stores 850 Purchase Order

Transaction Set 832 Price/Sales Catalog. Functional Group ID = SC X12 Version 004 Release 010

Mapping Guideline Finlay's 810 Invoice

947 Warehouse Inventory Adjustment Advice

evo.com 850 Purchase Order

Introduction: Heading: Detail: Summary: Functional Group ID=PO

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR TO DEALER PURCHASE ORDER ACKNOWLEDGMENT (855) TRANSACTION SET

830 Planning Schedule with Release Capability

830 Planning Schedule with Release Capability

Toys R Us Import Purchase Order Transaction Set 850/4010

ThyssenKrupp Presta Danville, LLC. EDI Implementation Guidelines for 830 Planning Schedule with Release Capability ANSI X-12 version/release

BIG ROCK SPORTS INVOICE

Inbound 860 (Purchase Order Change) X12 Specification for Release

Functional information for inbound EDI purchase order (PO) EDIFACT - ORDERS ANSI X12-850

Inbound 865 (Purchase Order Change Acknowledgment/Request - Seller Initiated) X12 Specification for Release

Advanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice

An example of a paper product activity report and its ASC X12 interpretation can be found at the back of this guideline.

Outbound Inventory Advice X

The Product Activity Data Transaction - 852

Verizon Logistics 855 Implementation Guide ANSI Version Purchase Order Acknowledgement EDI Implementation Guide Trading Partner Edition

ANSI 860 Purchase Order Change - Outbound -

TRANSACTION SET. Invoice

AT&T Corporate Standard Specifications for New Horizons Wireline EDI 810 Invoice

856 Ship Notice/Manifest. X12/V4010/856 : 856 Ship Notice/Manifest Version: 1.0 Draft

An EIDX Convention for Electronic Data Interchange

810 Invoice. Version: 2.0 Draft

Verizon Business Purchasing, LLC 855 Guide 855 Purchase Order Acknowledgment

AT&T Corporate Standard Specifications for New Horizons Wireline EDI 850 Purchase Order

EDI Specifications Guide. 856 Supplier Advance Ship Notice

Verizon Business Purchasing, LLC 856 Guide 856 Ship Notice/Manifest

Rite Aid Corporation 856 DSD Ship Notice/Manifest Direct Store Delivery (DSD)

856 Ship Notice/Manifest

Transcription:

X12 Implementation Guidelines For Inbound Price Catalog v003010 (832I)

832 Price/Sales Catalog Functional Group ID=SC Introduction: This standard provides the format and establishes the data contents of a price/sales catalog transaction set. The price/sales catalog transaction set provides 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. 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 BCT Beginning Segment for Price/Sales Catalog M 1 030 NTE Note/Special Instruction F 100 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - LIN 700000 M 010 LIN Item Identification M 1 M 030 DTM Date/Time/Period M 10 040 REF Reference Numbers O 12 060 CTB Restrictions/Conditions O 25 140 LDT Lead Time O 1 LOOP ID - CTP 25 M 170 CTP Pricing Information M 1 180 DTM Date/Time/Period O 10 200 CUR Currency O 5 220 CTB Restrictions/Conditions O 5 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 CTT Transaction Totals M 1 n1 M 020 SE Transaction Set Trailer M 1 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. FD832I (003010) 1

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: Comments: 1 The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set). Notes: ST~832~0001' M ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set M ST02 329 Transaction Set Control Number M AN 4/9 Identifying control number assigned by the originator for a transaction set. FD832I (003010) 2

Segment: BCT Beginning Segment for Price/Sales Catalog Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of the Price/Sales Catalog Transaction Set and specify catalog purpose and number information Syntax Notes: Comments: Notes: BCT~PC~NIS 000001350~~~~~~~~02' M BCT01 683 Catalog Purpose Code M ID 2/2 Code indicating purpose of catalog PC Price Catalog SC Sales Catalog M BCT02 684 Catalog Number M AN 1/15 Identifying number for catalog or superseded catalog BCT10 353 Transaction Set Purpose Code O ID 2/2 Code identifying purpose of transaction set 00 Original 01 Cancellation 02 Add 03 Delete 04 Change ZZ Mutually Defined FD832I (003010) 3

Segment: NTE Note/Special Instruction Position: 030 Loop: Level: Heading Usage: Floating Max Use: 100 Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction Syntax Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment. Notes: NTE~GEN~GENERAL NOTE' NTE01 363 Note Reference Code O ID 3/3 Code identifying the functional area or purpose for which the note applies M NTE02 3 Free Form Message M AN 1/60 Free-form text FD832I (003010) 4

Segment: LIN Item Identification Position: 010 Loop: LIN Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If LIN04 is present, then LIN05 is required. 2 If LIN06 is present, then LIN07 is required. 3 If LIN08 is present, then LIN09 is required. 4 If LIN10 is present, then LIN11 is required. 5 If LIN12 is present, then LIN13 is required. 6 If LIN14 is present, then LIN15 is required. 7 If LIN16 is present, then LIN17 is required. 8 If LIN18 is present, then LIN19 is required. 9 If LIN20 is present, then LIN21 is required. 10 If LIN22 is present, then LIN23 is required. 11 If LIN24 is present, then LIN25 is required. 12 If LIN26 is present, then LIN27 is required. 13 If LIN28 is present, then LIN29 is required. 14 If LIN30 is present, then LIN31 is required. Comments: 1 See the Data Dictionary for a complete list of ID's. 2 LIN01 is the line item identification 3 LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Notes: LIN~~BP~CLB 3157~VP~267170B001' M LIN02 235 Product/Service ID Qualifier M ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number M LIN03 234 Product/Service ID M AN 1/30 Identifying number for a product or service LIN04 235 Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) VP Vendor's (Seller's) Part Number LIN05 234 Product/Service ID C AN 1/30 Identifying number for a product or service LIN06 235 Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) EC Engineering Change Level LIN07 234 Product/Service ID C AN 1/30 Identifying number for a product or service LIN08 235 Product/Service ID Qualifier O ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) CH Country of Origin Code LIN09 234 Product/Service ID C AN 1/30 FD832I (003010) 5

Identifying number for a product or service FD832I (003010) 6

Segment: DTM Date/Time/Period Position: 030 Loop: LIN Mandatory Level: Detail Usage: Mandatory Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Comments: Notes: DTM~097~011020' DTM~007~020921' M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 007 Effective 097 Transaction Creation DTM02 373 Date C DT 6/6 Date (YYMMDD) FD832I (003010) 7

Segment: REF Reference Numbers Position: 040 Loop: LIN Mandatory Level: Detail Usage: Optional Max Use: 12 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Comments: Notes: REF~ZA~34~000000001' M REF01 128 Reference Number Qualifier M ID 2/2 Code qualifying the Reference Number. REF02 127 Reference Number C AN 1/30 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. REF03 352 Description C AN 1/80 A free-form description to clarify the related data elements and their content FD832I (003010) 8

Segment: CTB Restrictions/Conditions Position: 060 Loop: LIN Mandatory Level: Detail Usage: Optional Max Use: 25 Purpose: To specify restrictions/conditions (such as shipping, ordering) Syntax Notes: 1 At least one of CTB02 or CTB04 is required. 2 If either CTB03 or CTB04 is present, then the other is required. Comments: Notes: CTB~SR~~67~1' M CTB01 688 Restrictions/Conditions Qualifier M ID 2/2 Code identifying the type of restriction/condition CTB03 673 Quantity Qualifier C ID 2/2 Code specifying the type of quantity CTB04 380 Quantity C R 1/10 Numeric value of quantity FD832I (003010) 9

Segment: LDT Lead Time Position: 140 Loop: LIN Mandatory Level: Detail Usage: Optional Max Use: 1 Purpose: To specify lead time for availability of products and services Syntax Notes: Comments: 1 LDT04 is the effective date of lead time information. Notes: LDT~AE~128~DA' M LDT01 345 Lead Time Code M ID 2/2 Code indicating the time range AE From date of PO receipt to shipment M LDT02 380 Quantity M R 1/10 Numeric value of quantity M LDT03 344 Unit of Time Period or Interval M ID 2/2 Code indicating the time period or interval DA Calendar Days FD832I (003010) 10

Segment: CTP Pricing Information Position: 170 Loop: CTP Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To specify pricing information Syntax Notes: 1 If CTP02 is present, then CTP03 is required. 2 If CTP04 is present, then CTP05 is required. 3 If CTP06 is present, then CTP07 is required. Comments: 1 Example of use of CTP03 and CTP04. PRICE QUANTITY RANGE 1.00 0 to 999 0.75 1000 to 4999 0.50 5000 to 9999 0.25 10000 and above CTP03 CTP04 1.00 0 0.75 1000 0.50 5000 0.25 10000 2 Example of use of CTP03, CTP04 and CTP07. CTP03 CTP04 CTP07 1.00 0 0.90 0.75 1000 0.90 0.50 5000 0.90 0.25 10000 0.90 3 CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of 90 would be the factor if a 10% discount is given. Notes: CTP~~~~1~PC' CTP~~UCP~60.42~1~PC' CTP02 236 Price Qualifier O ID 3/3 Code identifying pricing specification CTP03 212 Unit Price C R 1/14 Price per unit of product, service, commodity, etc. CTP04 380 Quantity O R 1/10 Numeric value of quantity CTP05 355 Unit or Basis for Measurement Code C ID 2/2 Code identifying the basic unit of measurement. FD832I (003010) 11

Segment: DTM Date/Time/Period Position: 180 Loop: CTP Mandatory Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Comments: Notes: DTM~097~011020' M DTM01 374 Date/Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time DTM02 373 Date C DT 6/6 Date (YYMMDD) FD832I (003010) 12

Segment: CUR Currency Position: 200 Loop: CTP Mandatory Level: Detail Usage: Optional Max Use: 5 Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction Syntax Notes: 1 If CUR08 is present, then CUR07 is required. 2 If CUR09 is present, then CUR07 is required. 3 If CUR11 is present, then CUR10 is required. 4 If CUR12 is present, then CUR10 is required. 5 If CUR14 is present, then CUR13 is required. 6 If CUR15 is present, then CUR13 is required. 7 If CUR17 is present, then CUR16 is required. 8 If CUR18 is present, then CUR16 is required. 9 If CUR20 is present, then CUR19 is required. 10 If CUR21 is present, then CUR19 is required. Comments: 1 Monetary values are assumed to be expressed in the currency of the country of the transaction originator unless the optional CUR segment is used to specify a different currency. The CUR segment also permits the transaction originator to indicate a specific exchange rate, foreign exchange location and date/time as the basis for a currency conversion. Example 1. Assuming the currency of the transaction originator is U.S. dollars, the following CUR segment, when used in the heading area of a transaction, would indicate that all monetary values appearing in the transaction are expressed in Canadian Dollars (CAD). (In this example the exchange rate is at the discretion of the receiver). CUR*BY*CAD* N/L Example 2. Assuming the currency of the transaction originator is U.S. dollars, the following CUR segment, when used in the detail area of a transaction, describes a currency conversion for that particular item from U.S. dollars to Canadian dollars. It also indicates that a specific exchange rate, at a specified foreign exchange location on a given date/time be used as the basis for the currency conversion. Notes below the diagram describe the meaning of the element values. CUR*BY*USD*1.20*SE*CAD*NY*007*840821*1400 N/L 1 2 3 4 1. Identifies the buyer's (BY) currency as U.S. dollars (USD). 2. The multiplier (1.20) is the exchange rate factor for the conversion. 3. Identifies the seller's (SE) currency as Canadian dollars (CAD). 4. Indicates the basis for the exchange rate as the New York Foreign Exchange (NY) and the effective date/time (007) as August 21, 1984 (840821) at 2:00 P.M. (1400). The value for this item is to be converted to Canadian dollars (CAD) at the exchange rate of 1.20, based on the New York Foreign Exchange (NY) at 2:00 P.M. (1400) on August 21, 1984. The actual unit price conversion for the item would be: The unit price value 7.50 (U.S. dollars) multiplied by the exchange rate (1.20) equals 9.00 Canadian dollars (7.50 X 1.20 = 9.00) CUR07 through CUR21 provide for five (5) dates/times relating to the currency conversion, i.e., effective date, expiration date, etc. Notes: CUR~SE~USD' M CUR01 98 Entity Identifier Code M ID 2/2 Code identifying an organizational entity or a physical location. M CUR02 100 Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified FD832I (003010) 13

Segment: CTB Restrictions/Conditions Position: 220 Loop: CTP Mandatory Level: Detail Usage: Optional Max Use: 5 Purpose: To specify restrictions/conditions (such as shipping, ordering) Syntax Notes: 1 At least one of CTB02 or CTB04 is required. 2 If either CTB03 or CTB04 is present, then the other is required. Comments: Notes: CTB~SR~~67~1' M CTB01 688 Restrictions/Conditions Qualifier M ID 2/2 Code identifying the type of restriction/condition CTB03 673 Quantity Qualifier C ID 2/2 Code specifying the type of quantity CTB04 380 Quantity C R 1/10 Numeric value of quantity FD832I (003010) 14

Segment: CTT Transaction Totals Position: 010 Loop: 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 CTT03 is present, then CTT04 is required. 2 If CTT05 is present, then CTT06 is required. Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. Notes: CTT~12' M CTT01 354 Number of Line Items M N0 1/6 Total number of line items in the transaction set FD832I (003010) 15

Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: Syntax Notes: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Comments: 1 SE is the last segment of each transaction set. Notes: SE~9~0001' M SE01 96 Number of Included Segments M N0 1/6 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 assigned by the originator for a transaction set. FD832I (003010) 16

EXAMPLE ISA~00~ ~00~ ~ZZ~GTST1 ~ZZ~F159B ~030424~0345~U~00200~000003839~0~P~~_ GS~SC~GTST1~GPLT1~030424~0345~1235~X~003010_ ST~832~000001363_ BCT~PC~MyCatalog~~~~~~~~02_ LIN~~BP~TESTP 12A6 50BA_ DTM~097~030423_ DTM~007~030423_ LDT~AE~60~DA_ CTP~~~~1~PC_ CTB~SR~~69~1_ LIN~~BP~TSTP2 12259 AB_ DTM~097~030423_ DTM~007~030423_ CTP~~~~1~PC_ CTB~SR~~69~1_ CTT~2_ SE~15~000001363_ GE~1~1235_ IEA~1~000003839_ FD832I (003010) 17