BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 830 VERSION 4010 FROM BRP INC. Document version 1.0

Transcription

1 BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 830 VERSION 4010 FROM BRP INC. Document version 1.0 The following guide is intended to facilitate the user in implementing Electronic Data Interchange transactions with BRP Inc. Every effort has been made to verify that the information contained in this guide conforms to the accepted standards, is up-to-date and valid. BRP Inc. assumes no liability for, nor makes any warranty with respect to, the accuracy of the information in this guide or that its use will ensure error-free transmissions and transactions. BRP Inc. 1

2 Document Change Log Version Date Page Description BRP Inc. 2

3 SUPPLIER IMPLEMENTATION GUIDE TABLE OF CONTENTS Section one: General Information Ø Competitive Advantage Ø What is EDI? Ø EDI Standards Ø BRP Inc. s EDI Direction Ø Interchange and Functional Group ID Information Ø Delimiters Ø Re-certification Section Two: Appendix A: Appendix B: 830 Guidelines Supplier Registration Form 830 Sample Files BRP Inc. 3

4 Section One: General Information Competitive Advantage: Embracing EDI can result in many benefits for your organization, including stronger strategic relationships, reduced purchased prices and procurement costs, improved customer service levels, shorter lead times, and lower inventory. By automating communication between your organization and your trading partners, electronic data interchange (EDI) can help realize these benefits and position your company for a competitive advantage. What is EDI? EDI is the exchange of routine business transactions in a format which can be processed by a computer. Exchanging business documents can take seconds instead of days, and documents are far less likely to get lost or damaged. EDI allows you to send information over public or private communication links. A Value Added Network (VAN) is the most common communication link and is the communication method used by BRP Inc. EDI Standards Make It Possible: Documents sent via EDI can serve as input for a receiving company's application software because they are formatted according to standards. These standards indicate where certain data should be located and whether the data is mandatory or optional. The most common standards are ANSI ASC X.12 (American Standards Institute, Accredited Standards Committee X.12) and UN/EDIFACT. All BRP Inc. EDI transactions shall comply with the standards set by ANSI ASC X.12 Version BRP Inc. s EDI Direction: BRP Inc. has recognized that Electronic Data Interchange (EDI) is a requirement in today's business environment. EDI provides the financial and operational advantages companies need to remain competitive. BRP Inc. will send the 830 transaction set (Planning Schedule with Release Capability) and the 862 transaction set (Shipping Schedule). BRP Inc. will require suppliers to send an 856 transaction (Ship Notice/Manifest). BRP Inc. requires a Functional Acknowledgement (997) be sent in response to any 830 and/or 862 transaction sent. The use of EDI for document exchange has bottom-line benefits and strategic advantages for both trading partners. BRP Inc. is committed to taking both itself and its business partners to a position where we both will realize the full potential of EDI. BRP Inc. s Interchange and Functional Group ID Information: Production: BRP Inc. s ISA Qualifier is: ZZ BRP Inc. s ISA ID is: BRP Inc. s GS ID is: Test: BRP Inc. s ISA Qualifier is: BRP Inc. s ISA ID is: BRP Inc. s GS ID is: ZZ T T BRP Inc. s Delimiters: Element Delimiter: ~ (HEX 7E) Sub-Element Delimiter: * (HEX 2A) Segment Terminator: ^ (HEX 5E) BRP Inc. 4

5 Re-certification: Following go-live, if a supplier changes anything (i.e. software/process/method) which affects the receipt or transmission of EDI transactions from/to BRP Inc., they must advise BRP BEFORE implementing such change(s), and submit such change(s) to the BRP Inc. supplier testing process (described above), at supplier's expense. BRP Inc. 5

6 Section Two: 830 Guideline 830 Planning Schedule with Release Capability Functional Group=PS Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set (830) 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 practice relative to the transfer of forecasting/material release information between organizations.the planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders. Not Defined: Pos Id Segment Req Max Use Repeat Notes ISA Interchange Control Header M 1 GS Functional Group Header M 1 Heading: Pos Id Segment Req Max Use Repeat Notes 010 ST Transaction Set Header M BFR Beginning Segment for Planning Schedule M 1 LOOP ID - N N1 M N2 Additional Information O N3 Address Information O N4 Geographic Location O PER Administrative Communications Contact M 3 Detail: Pos Id Segment Req Max Use Repeat Notes LOOP ID - LIN >1 010 LIN Item Identification M UIT Unit Detail M REF Reference Identification M 12 LOOP ID - SDP SDP Ship/Delivery Pattern M FST Forecast Schedule M 260 Summary: Pos Id Segment Req Max Use Repeat Notes 010 CTT Transaction Totals M 1 N3/ SE Transaction Set Trailer M 1 Not Defined: Pos Id Segment Req Max Use Repeat Notes GE Functional Group Trailer M 1 IEA Interchange Control Trailer M 1 Notes: 3/010 Number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is the BRP Inc. 6

7 sum of the values of the quantities (FST01) for each FST segment. User Note 1: Signification of the code regarding the requirement specification M O X Description Mandatory Optional Conditionnal BRP Inc. 7

8 ISA Interchange Control Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 16 Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments ISA01 I01 Authorization Information Qualifier M ID 2/2 Description: to identify the type of information in the Authorization Information 00 No Authorization Information Present (No Meaningful Information in I02) ISA02 I02 Authorization Information M AN 10/10 Description: Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01) ISA03 I03 Security Information Qualifier M ID 2/2 Description: to identify the type of information in the Security Information 00 No Security Information Present (No Meaningful Information in I04) ISA04 I04 Security Information M AN 10/10 Description: This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03) ISA05 I05 Interchange ID Qualifier M ID 2/2 Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified ZZ Mutually Defined ISA06 I06 Interchange Sender ID M AN 15/15 Description: Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element ISA07 I05 Interchange ID Qualifier M ID 2/2 Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified All valid standard codes are used. ISA08 I07 Interchange Receiver ID M AN 15/15 Description: Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them ISA09 I08 Interchange Date M DT 6/6 Description: Date of the interchange ISA10 I09 Interchange Time M TM 4/4 Description: Time of the interchange ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Description: to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer All valid standard codes are used. BRP Inc. 8

9 ISA12 I11 Interchange Control Version Number M ID 5/5 Description: specifying the version number of the interchange control segments Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997 ISA13 I12 Interchange Control Number M N0 9/9 Description: A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Description: sent by the sender to request an interchange acknowledgment (TA1) 0 No Acknowledgment Requested ISA15 I14 Usage Indicator M ID 1/1 Description: to indicate whether data enclosed by this interchange envelope is test, production or information P T Production Data Test Data ISA16 I15 Component Element Separator M 1/1 Description: Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator BRP Inc. 9

10 GS Functional Group Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 8 Purpose: To indicate the beginning of a functional group and to provide control information GS Functional Identifier M ID 2/2 Description: identifying a group of application related transaction sets PS Planning Schedule with Release Capability (830) GS Application Sender's M AN 2/15 Description: identifying party sending transmission; codes agreed to by trading partners GS Application Receiver's M AN 2/15 Description: identifying party receiving transmission; codes agreed to by trading partners GS Date M DT 8/8 Description: Date expressed as CCYYMMDD GS Time M TM 4/8 Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) GS06 28 Group Control Number M N0 1/9 Description: Assigned number originated and maintained by the sender GS Responsible Agency M ID 1/2 Description: identifying the issuer of the standard; this code is used in conjunction with Data Element 480 X Accredited Standards Committee X12 GS Version / Release / Industry Identifier M AN 1/12 Description: indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997 Semantics: 1. GS04 is the group date. 2. GS05 is the group time. 3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Comments: 1. 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. BRP Inc. 10

11 ST Transaction Set Header Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 Purpose: To indicate the start of a transaction set and to assign a control number ST Transaction Set Identifier M ID 3/3 Description: uniquely identifying a Transaction Set 830 Planning Schedule with Release Capability ST Transaction Set Control Number M AN 4/9 Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Semantics: 1. 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). BRP Inc. 11

12 BFR Beginning Segment for Planning Schedule Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 7 Purpose: To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast envelope dates BFR Transaction Set Purpose M ID 2/2 Description: identifying purpose of transaction set 05 Replace BFR Release Number M AN 1/30 Description: Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction BFR Schedule Type Qualifier M ID 2/2 Description: identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast ZZ Mutually Defined BFR Schedule Quantity Qualifier M ID 1/1 Description: identifying the type of quantities used when defining a schedule or forecast A Actual Discrete Quantities BFR Date M DT 8/8 Description: Date expressed as CCYYMMDD BFR Date M DT 8/8 Description: Date expressed as CCYYMMDD BFR Date M DT 8/8 Description: Date expressed as CCYYMMDD Semantics: 1. BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins. 2. BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends. 3. BFR08 is the date forecast generated: The date the forecast data was generated. BRP Inc. 12

13 Loop Pos: 230 Repeat: 200 Mandatory Loop: N1 Elements: N/A Purpose: To identify a party by type of organization, name, and code Loop Summary: Pos Id Segment Req Max Use Repeat 230 N1 M N2 Additional Information O N3 Address Information O N4 Geographic Location O PER Administrative Communications Contact M 3 BRP Inc. 13

14 N1 Pos: 230 Max: 1 Heading - Mandatory Loop: N1 Elements: 4 Purpose: To identify a party by type of organization, name, and code N Entity Identifier M ID 2/3 Description: identifying an organizational entity, a physical location, property or an individual ST SU Ship To Supplier/Manufacturer N X AN 1/60 Description: Free-form name N Identification Qualifier X ID 1/2 Description: designating the system/method of code structure used for Identification (67) 92 Assigned by Buyer or Buyer's Agent N Identification X AN 2/80 Description: identifying a party or other code Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID " (N104) must provide a key to the table maintained by the transaction processing party. User Note 1: The actual delivery address will be in the REF~SL segment for each item, and this segment will contain: Example: N1~ST~BRP plant code-92~0001^ User Note 2: For each Item Number, PO Number combination, you will have a distinct SL, which defines the final destination. Thus will be specified in Page 22 defined in the REF segment for Storage location BRP Inc. 14

15 N2 Additional Information Pos: 240 Max: 2 Heading - Optional Loop: N1 Elements: 2 Purpose: To specify additional names or those longer than 35 characters in length N M AN 1/60 Description: Free-form name N O AN 1/60 Description: Free-form name User Note 1: For the N1 Loopwhere N104 = SU, the N2 will be sent BRP Inc. 15

16 N3 Address Information Pos: 250 Max: 2 Heading - Optional Loop: N1 Elements: 2 Purpose: To specify the location of the named party N Address Information M AN 1/55 Description: Address information N Address Information O AN 1/55 Description: Address information User Note 1: For the N1 Loopwhere N104 = SU, the N3 will be sent BRP Inc. 16

17 N4 Geographic Location Pos: 260 Max: 1 Heading - Optional Loop: N1 Elements: 4 Purpose: To specify the geographic place of the named party N City M AN 2/30 Description: Free-form text for city name N State or Province O ID 2/2 Description: (Standard State/Province) as defined by appropriate government agency N Postal M ID 3/15 Description: defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country M ID 2/3 Description: identifying the country BRP Inc. 17

18 PER Administrative Communications Contact Pos: 280 Max: 3 Heading - Mandatory Loop: N1 Elements: 4 Purpose: To identify a person or office to whom administrative communications should be directed PER Contact Function M ID 2/2 Description: identifying the major duty or responsibility of the person or group named EX Expeditor PER02 93 O AN 1/60 Description: Free-form name PER Communication Number Qualifier M ID 2/2 Description: identifying the type of communication number TE Telephone PER Communication Number M AN 1/80 Description: Complete communications number including country or area code when applicable Syntax Rules: 1. P If either PER03 or PER04 is present, then the other is required. User Note 1: PER segment will be present for N1-SU only BRP Inc. 18

19 Loop Item Identification Pos: 010 Repeat: >1 Mandatory Loop: LIN Elements: N/A Purpose: To specify basic item identification data Loop Summary: Pos Id Segment Req Max Use Repeat 010 LIN Item Identification M UIT Unit Detail M REF Reference Identification M Loop SDP M 260 BRP Inc. 19

20 LIN Item Identification Pos: 010 Max: 1 Detail - Mandatory Loop: LIN Elements: 6 Purpose: To specify basic item identification data LIN Product/Service ID Qualifier M ID 2/2 Description: identifying the type/source of the descriptive number used in Product/Service ID (234) BP Buyer's Part Number LIN Product/Service ID M AN 1/48 Description: Identifying number for a product or service LIN Product/Service ID Qualifier M ID 2/2 Description: identifying the type/source of the descriptive number used in Product/Service ID (234) User Note 1: BRP Inc. may send a Drawing Revision Level in the ECN level/number segment. If no ECN level/number is available for the item, BRP Inc. will send: NONE EC Engineering Change Level LIN Product/Service ID M AN 1/48 Description: Identifying number for a product or service LIN Product/Service ID Qualifier M ID 2/2 Description: identifying the type/source of the descriptive number used in Product/Service ID (234) PO Purchase Order Number LIN Product/Service ID M AN 1/48 Description: Identifying number for a product or service User Note 1: The LIN07 consists of two parts, the PO Number, and the Line Item Number. The two parts are separated by a dash. Ex: PO# = , PO Line Item# = The resultant value in LIN07 will be BRP Inc. 20

21 UIT Unit Detail Pos: 020 Max: 1 Detail - Mandatory Loop: LIN Elements: 1 Purpose: To specify item unit data UIT01 C001 Composite Unit of Measure M Comp Description: To identify a composite unit of measure(see Figures Appendix for examples of use) UIT Unit or Basis for Measurement M ID 2/2 Description: specifying the units in which a value is being expressed, or manner in which a measurement has been taken BRP Inc. 21

22 REF Reference Identification Pos: 140 Max: 12 Detail - Mandatory Loop: LIN Elements: 2 Purpose: To specify identifying information REF Reference Identification Qualifier M ID 2/3 Description: qualifying the Reference Identification SL Storage Location REF Reference Identification M AN 1/30 Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier User Note 1: The ASN must contain only items with the same SL value BRP Inc. 22

23 Loop Ship/Delivery Pattern Pos: 450 Repeat: 260 Mandatory Loop: SDP Elements: N/A Purpose: To identify specific ship/delivery requirements Loop Summary: Pos Id Segment Req Max Use Repeat 450 SDP Ship/Delivery Pattern M FST Forecast Schedule M 260 BRP Inc. 23

24 SDP Ship/Delivery Pattern Pos: 450 Max: 1 Detail - Mandatory Loop: SDP Elements: 2 Purpose: To identify specific ship/delivery requirements SDP Ship/Delivery or Calendar Pattern M ID 1/2 Description: which specifies the routine shipments, deliveries, or calendar pattern Y None (Also Used to Cancel or Override a Previous Pattern) SDP Ship/Delivery Pattern Time M ID 1/1 Description: which specifies the time for routine shipments or deliveries Y None (Also Used to Cancel or Override a Previous Pattern) Comments: 1. The intent of this segment is to define the routine ship or delivery patterns, as required, when order quantities are in "buckets", such as weekly, monthly. Ship/delivery patterns eliminate the need to transmit discrete quantities and dates for each required shipment or delivery. It is assumed that a "bucketed" quantity is to be divided equally by the ship/delivery pattern. For example, a weekly quantity of 100 with a delivery pattern of Monday and Wednesday would result in 50 to be delivered on Monday and 50 to be delivered on Wednesday. BRP Inc. 24

25 FST Forecast Schedule Pos: 460 Max: 260 Detail - Mandatory Loop: SDP Elements: 5 Purpose: To specify the forecasted dates and quantities FST Quantity M R 1/15 Description: Numeric value of quantity FST Forecast Qualifier M ID 1/1 Description: specifying the sender's confidence level of the forecast data or an action associated with a forecast D Planning FST Forecast Timing Qualifier M ID 1/1 Description: specifying interval grouping of the forecast D M W Discrete Monthly Bucket (Calendar Months) Weekly Bucket (Monday through Sunday) FST Date M DT 8/8 Description: Date expressed as CCYYMMDD FST Date O DT 8/8 Comments: 1. As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start date of a flexible interval. BRP Inc. 25

26 CTT Transaction Totals Pos: 010 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 Purpose: To transmit a hash total for a specific element in the transaction set CTT Number of Line Items M N0 1/6 Description: Total number of line items in the transaction set CTT Hash Total M R 1/10 Description: Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element. Example: First occurrence of value being hashed..18 Second occurrence of value being hashed. 1.8 Third occurrence of value being hashed Fourth occurrence of value being hashed Hash total prior to truncation. 855 Hash total after truncation to three-digit field. Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness. BRP Inc. 26

27 SE Transaction Set Trailer Pos: 020 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 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) SE01 96 Number of Included Segments M N0 1/10 Description: Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 Comments: 1. SE is the last segment of each transaction set. Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set BRP Inc. 27

28 GE Functional Group Trailer Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 2 Purpose: To indicate the end of a functional group and to provide control information GE01 97 Number of Transaction Sets Included M N0 1/6 Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element GE02 28 Group Control Number M N0 1/9 Description: Assigned number originated and maintained by the sender Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Comments: 1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header. BRP Inc. 28

29 IEA Interchange Control Trailer Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 2 Purpose: To define the end of an interchange of zero or more functional groups and interchange-related control segments IEA01 I16 Number of Included Functional Groups M N0 1/5 Description: A count of the number of functional groups included in an interchange IEA02 I12 Interchange Control Number M N0 9/9 Description: A control number assigned by the interchange sender BRP Inc. 29

30 Appendix A: Supplier Registration Form to: Date: Sent By: Phone: PLEASE PROVIDE YOUR KEY CONTACT INFORMATION: EDI Contact : Phone: Fax: Company : Supplier Number: Address: Address: City: State: Zip : TO COMMUNICATE WITH BRP INC., PLEASE ENTER: VAN: ISA Qualifier: ISA ID: GS ID: BRP Inc. 30

31 Appendix B: 830 Sample Files Planning Schedule sent by BRP to a Supplier : ISA~00~ ~00~ ~ZZ~ ~ZZ~ ~140124~1834~U~00401~ ~0~P~*^ GS~PS~ ~ ~ ~1834~12705~X~004010^ ST~830~0001^ BFR~05~~ ~DL~A~ ~ ~ ^ N1~SU~SUPPLIER NAME~92~ ^ N3~123, 4E AVENUE^ N4~CITY~QC~J1G 5H7~CA^ PER~EX~EXPEDITOR NAME~TE~ ^ N1~ST~BRP plant code-0001~0001^ LIN~~BP~ ~EC~NONE~PO~ ^ UIT~PC^ REF~SL~ ^ SDP~Y~Y^ FST~0~D~D~ ^ CTT~1~0^ SE~14~0001^ GE~1~12705^ IEA~1~ ^ BRP Inc. 31