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

Transcription

1 MOBIS Alabama RDC, LLC IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS MATERIAL RELEASE TRANSACTION SET (830) VERSION/RELEASE Guideline Version 1.0 Issue Date 01/21/2005 MOBIS Alabama Redistribution Center, USA 1395 Mitchell Young Road Montgomery, Alabama, 36108

2 830 Planning Schedule with Release Capability Introduction: Functional Group ID=PS 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. 01/21/ (4010) 2

3 Pos. No. Table 1: Header Seg. ID Name Req. Max. Use 010 ST Transaction Set Header M BFR Beginning Segment for Planning Schedule M 1 Loop Repeat Notes and Comments LOOP ID - N N1 Name O PER Administrative Communications Contact O 3 Pos. No. Table 2: Detail Seg. ID Name Req. Max. Use Loop Repeat LOOP ID - LIN LIN Item Identification M UIT Unit Detail M CUR Currency O CTP Pricing Information O PID Product/Item Description O TD5 Carrier Details (Routing sequence/transit Time) O 12 Notes and Comments LOOP ID N N1 Name O N2 Additional Name Information O N3 Address Information O N4 Geographic Location O 1 LOOP ID - FST FST Forecast Schedule O 1 Table 3: Summary Pos. No. Seg. ID Name Req. Max. Use 010 CTT Transaction Totals O SE Transaction Set Trailer M 1 Loop Repeat Notes and Comments 01/21/ (4010) 3

4 Segment: ISA Interchange Control Header Position: Loop: Level: N/A Usage: Mandatory 1 per interchange Purpose: To start and identify an interchange of one or more functional groups and interchange-related control segments 1. The actual values of the data element separator and the data segment terminator for this interchange are set by the interchange control header. For a particular interchange, the value at the fourth character position is the data element separator, and the value of the last character position is the value of the data segment terminator. The extent of this particular usage of the data element separator and the data segment separator terminator is from this header to and including the next interchange trailer. The interchange control number value in ISA13 in this header must match the value in the same data element n the corresponding interchange control trailer in IEA02. Comments: The first occurrence of the data element separator (byte 4) defines the actual value of the data element separator and is graphically displayed as an asterisk *. The first occurrence of the segment terminator, 1 byte after the data element ISA16, defines the actual value of the data segment terminator and is graphically displayed as ~. Example: ISA*00* *00* *ZZ*MOBIS-RDC *ZZ*Supplier *040218*1438*U*00401* *0*P*>~ ISA01 I01 Authorization Information Qualifier M ID 2/2 00 No Authorization Information Present ISA02 I02 Authorization Information M AN 10/10 10 empty spaces must be entered here as the ISA segment is space sensitive. ISA03 I03 Security Information Qualifier M ID 2/2 00 No Password ISA04 I04 Security Information M ID 10/10 10 empty spaces must be entered here as the ISA segment is space sensitive. ISA05 I05 Interchange ID Qualifier M ID 2/2 ZZ Mutually Defined ISA06 I06 Interchange Sender ID M ID 15/15 Left justify, space fill MOBIS-RDC ISA07 I05 Interchange ID Qualifier M ID 2/2 ZZ Mutually Defined ISA08 I07 Interchange Receiver ID M ID 15/15 Left justify, space fill Supplier ISA09 I08 Interchange Date M DT 6/6 Date of creation ISA10 I09 Interchange Time M TM 4/4 Time of creation 01/21/ (4010) 4

5 ISA11 I10 Interchange Control Standards Identifier M ID 1/1 U United States ISA12 I11 Interchange Control Version Number M ID 5/ ISA13 I12 Interchange Control Number M N0 9/9 A number that cannot be repeated within a 1 year period at a time ISA14 I13 Acknowledgment Requested M ID 1/1 Use 0 for no Ack. Req., use 1 for Ack. Req. 0 No Acknowledgement requested ISA15 I14 Test Indicator M ID 1/1 Use T for test data or P for production data ISA16 I15 Component Element Separator M ID 1/1 01/21/ (4010) 5

6 Segment: GS Functional Group Header Position: Loop: Level: N/A Usage: Mandatory 1 per functional group Purpose: To indicate the beginning of a functional group and to provide control information See the ASC X12 segment directory for rules and notes Comments: Strict compliance and agreement on content by trading partners is required. Example: GS*PS*MOBIS-RDC*Supplier* *1438*31*X*004010~ GS Functional Identifier Code M ID 2/2 PS Planning Schedule with Release Capability GS Application Sender s Code M ID 2/15 MOBIS-RDC GS Application Receiver s Code M ID 2/15 Supplier GS Date M DT 8/8 Date Created GS Time M TM 4/8 Time created GS06 25 Group Control Number M N0 1/9 Start with 1 and increment by 1 for each subsequent GS segment GS Responsible Agency Code M ID 1/2 Code used in conjunction with Data Element GS08 to identify the issuer of the standard X ASC X12 format GS Version/Release/Industry ID Code M ID 6/12 This code indicates the version, release and subrelease of the EDI standard being used, including the GS and GE segments. Positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version Draft Standard 01/21/ (4010) 6

7 Segment: ST Transaction Set Header Position: 010 Loop: Level: Header Usage: Mandatory Purpose: To indicate the start of a transaction set and to assign a control number 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). The Transaction Set Control Number (ST02) in this header must match the Transaction Set Control Number (SE02) in the Transaction Set Trailer (SE). Comments: Example: ST*830* ~ ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 830 Planning Schedule with Release Capability ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set. 01/21/ (4010) 7

8 Segment: BFR Beginning Segment for Shipping Schedule/Production Sequence Position: 020 Loop: Level: Header Usage: Mandatory Purpose: To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast envelope dates. 1. BFR02 is the identifying number for a forecast assigned by the orderer/purchaser 2. BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins 3. BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends 4. BFR08 is the date forecast generated: The date the forecast data was generated Comments: 1. The intent of this segment is to provide information for the entire transaction. Some of this information may be overridden by subsequent segments in the transaction Example: BFR*05*AG5P4LC **DL*A* ** ~ BFR Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set 05 Replace 00 Original BFR Reference Number M AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier This number must be unique within a contractual agreement, i.e., a scheduling agreement BFR Schedule Type Qualifier M ID 2/2 Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast DL Delivery Based BFR Schedule Quantity Qualifier M ID 1/1 Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast A Actual Discrete Quantities BFR Forecast Start Date M DT 8/8 Date (CCYYMMDD) BFR Forecast End Date O DT 8/8 Date (CCYYMMDD) BFR Date Document Generated M DT 8/8 Date (CCYYMMDD) 01/21/ (4010) 8

9 Segment: N1 Name Position: 230 Loop: N1 Level: Header Usage: Optional Purpose: To identify a party by type of organization, name, and code 1. At least one of N102 or N104 is required 2. If either N103 or N104 is present, then the other is required 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. This N1 loop in the header area can be used to identify the shipping schedule issuer, the supplier, and the ship-to and ship-from locations. Example: N1*BY*MOBIS ALABAMA RDC, U.S.A*92*A001~ N1*SU*Supplier Name*92*AG5P~ N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, or an individual BY Buyer SU Release Supplier BT Bill To N Name X AN 1/60 Free-form name N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned By Buyer N Identification Code M AN 1/80 Code identifying a party or other code 01/21/ (4010) 9

10 Segment: PER Administrative Communications Contact Position: 280 Loop: N1 Level: Header Usage: Optional Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed 1. If either PER03 or PER04 is present, then the other is required Comments: Example: PER*IC*Hayden Park*TE* ~ PER Contact Function Code X ID 1/2 Code Identifying the major duty or responsibility of the person or group named IC Information Contact PER02 93 Name X AN 1/60 Free form name PER Communication Number Qualifier X ID 2/2 Code Identifying the type of communication number TE Telephone PER Communication Number X ID 1/80 Code Identifying the type of communication number 01/21/ (4010) 10

11 Segment: LIN Item Identification Position: 010 Loop: LIN Level: Detail Usage: Mandatory Purpose: To specify basic item identification data 1. If either LIN04 or LIN05 is present, then the other is required 2. If either LIN06 or LIN07 is present, then the other is required 3. If either LIN08 or LIN09 is present, then the other is required 4. If either LIN10 or LIN11 is present, then the other is required Comments: Example: LIN**BP* *VP*D *PO*AG5P4LC1*PL*0002~ LIN 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 LIN Product/Service ID - Buyer's Part Number M AN 1/48 Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) VP Vendors Part Number LIN Product/Service ID Vendor s Part Number X AN 1/48 Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) PO Purchase Order Number LIN Product/Service ID Purchase Order Number X AN 4/48 Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) PL Line Item Number on Contract LIN Product/Service ID Line Item Number on Contract X AN 4/48 Identifying number for a product or service LIN Product/Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) ON Customer Order Number LIN Product/Service ID for Dealer Direct only X AN 4/48 Identifying number for a product or service 01/21/ (4010) 11

12 Segment: UIT Unit Detail Position: 020 Loop: LIN Level: Detail Usage: Mandatory Purpose: To specify item unit data Comments: Example: UIT*EA~ Ref. Des. UIT01 Data Element Name 355 Composite unit of measure M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. EA Each 01/21/ (4010) 12

13 Segment: CUR Reference Identification Position: 030 Loop: LIN Level: Detail Usage: Optional Purpose: To specify the currency used in the transaction Comments: Example: CUR*BY*USD~ CUR01 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual BY Buying Party (Purchaser) CUR Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified This is a three position alpha code of the ISO-4217 code list 01/21/ (4010) 13

14 Segment: CTP Pricing Information Position: 070 Loop: LIN Level: Detail Usage: Optional Purpose: To specify the pricing information Comments: Example: CTP**ACT*2~ CTP Price Identifier Code M ID 3/3 Code identifying pricing information ACT Actual (final negotiated contact price) CTP Unit Price M ID 1/17 Price per Unit of Product 01/21/ (4010) 14

15 Segment: TD5 Carrier Details (Routing sequence/transit Time) Position: 250 Loop: LIN Level: Detail Usage: Optional Purpose: To specify the carrier and sequence of routing and provide transit time information Comments: Example: TD5*B***A~ TD Routing Sequence Code X ID 1/2 Code describing the relationship of the carrier to a specific shipment movement B Origin/Delivery Carrier TD Transportation Method X ID 1/2 Code specifying the method or type of transportation for the shipment A Air D Parcel Post DD Dedicated Delivery Service E Expedited Truck M Motor O Containerized Ocean PC Private Carrier PD Parcel Delivery (UPS, Federal Express, etc.) R Rail VE Vessel 01/21/ (4010) 15

16 Segment: PID Product/Item Description Position: Loop: LIN Level: Detail Usage: Optional Purpose: To describe a product or process in coded or free form format Comments: If PID01 equals F, then PID05 is used. Example: PID*F****PINION VALVE ASSY~ PID Item Description Type X ID 1/1 F Free-form PID Description X AN 1/80 01/21/ (4010) 16

17 Segment: N1 Name Position: 320 Loop: LIN\N1 Level: Detail Usage: Optional Purpose: To identify a party by type of organization, name, and code 1. At least one of N102 or N104 is required 2. If either N103 or N104 is present, then the other is required 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. This N1 loop in the header area can be used to identify the shipping schedule issuer, the supplier, and the ship-to and ship-from locations. Example: N1*ST*MOBIS ALABAMA RDC, U.S.A*92*A001~ N1*ST*HWASHIN AMERICA CORP. U.S.A*92*W001~ N1*ST*GLOVIS WAREHOUSE AT HMMA U.S.A*92*G001~ N Organization Identifier M ID 2/3 Code identifying an organizational entity, a physical location, or an individual ST Ship To N Name X AN 1/60 Free-form name N Identification Code Qualifier M ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by buyer N Identification Code M AN 1/80 Code identifying a party or other code 01/21/ (4010) 17

18 Segment: N2 Address Information Position: 330 Loop: LIN/N1 Level: Detail Usage: Optional Purpose: To specify the location of the named party Comments: - for dealer direct shipments only - Example: N2*MOBIS*RDC~ N Name O AN 1/60 Free-form name N Name O AN 1/60 Free-form name 01/21/ (4010) 18

19 Segment: N3 Address Information Position: 340 Loop: LIN/N1 Level: Detail Usage: Optional Purpose: To specify the location of the named party Comments: - for dealer direct shipments only - Example: N3*5 Concourse Parkway ~ N Address Information O AN 1/55 Code identifying an organizational entity, a physical location, or an individual 01/21/ (4010) 19

20 Segment: N4 Geographic Location Position: 350 Loop: LIN/N1 Level: Detail Usage: Optional Purpose: To specify the geographic place of the named party Comments: 1. A combination of N401 through N404 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada. 3. If N401 is present, then N402 and N403 are required. - for dealer direct shipments only - Example: N4*Atlanta*GA*30328*US~ N City Name O AN 2/30 Free form city name N State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Code Identifying the country 01/21/ (4010) 20

21 Segment: FST Forecast Schedule Position: 410 Loop: LIN/FST Level: Detail Usage: Mandatory Purpose: To specify the forecasted dates and quantities 1. At least one occurrence of segment FST is required. Comments: As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted Example: FST*310*C*W* ***~ FST Quantity M N 1/15 Numeric value of quantity FST Forecast Qualifier M ID 1/1 Code specifying the sender's confidence level of the forecast data or an action associated with a forecast A Immediate C Firm D Planning Z Mutually defined (Backorder) FST Forecast Timing Qualifier M ID 1/1 Code specifying interval grouping of the forecast W Weekly C Daily D Discrete F Flexible M Monthly FST Date M DT 8/8 Date (CCYYMMDD) FST Date O DT 8/8 Date (CCYYMMDD) FST Date/Time Qualifier X ID 3/3 Code specifying type of date or time or both date and time 002 Delivery Requested FST Time X TM 4/8 Time expressed in 24-hours clock time as follows: HHMM, or HHMMSSD, or HHMMSSDD 01/21/ (4010) 21

22 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Usage: Mandatory Purpose: To transmit a hash total for a specific element in the transaction set Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness. Example: CTT*2~ CTT Number of Line Items M N 1/6 Total number of line items (LIN segments) in the transaction set 01/21/ (4010) 22

23 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Usage: Mandatory 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). Comments: 1. SE is the last segment of each transaction set. 2. The Transaction Set Control Number value in this trailer must match the same element value in the Transaction Set Header (ST02). Example: SE*45* ~ SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments SE 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 01/21/ (4010) 23

24 Segment: GE Functional Group Trailer Position: Loop: Level: N/A Usage: Mandatory 1 per functional group Purpose: To indicate the end of a functional group and to provide control information 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: Example: GE*1*31~ GE01 97 Number of Transaction Sets Included M N0 1/6 Total number of ST segments in group GE02 28 Group Control Number M N0 1/9 Must be identical to the same data element in the associated group header (GS06) 01/21/ (4010) 24

25 Segment: IEA Interchange Control Trailer Position: Loop: Level: N/A Usage: Mandatory 1 per Interchange Purpose: To define the end of an interchange of zero or more functional groups and interchange-related control segments The interchange control number IEA02 in this trailer must match the value in ISA13 Comments: Example: IEA*1* ~ IEA01 I16 Number of Included Functional Groups M N0 1/5 Number of GS segments included between ISA and this IEA IEA02 I12 Interchange Control Number M N0 9/9 Must match ISA13 01/21/ (4010) 25

26 Example 1 EDI Structure EDI FORMAT ST*830*0001~ BFR*05*AG5P4LC **DL*A* ** ~ N1*BY*MOBIS ALABAMA RDC, U.S.A*92*A001~ PER*IC*Hayden Park*TE* ~ N1*SU*Supplier Name*N006~ LIN**BP* *VP*D *PO*AG5 P4LC1*PL*0002~ UIT*EA~ CUR*BY*USD~ INTERPRETATION X12 Transaction Set = 830 (Planning Schedule) Transaction Set Control Number =0001 Transaction Set Purpose = 05 (Replace) Reference Number: = AG5P4LC Delivery Based Dates Actual Discrete Quantities Horizon Start Date = 11/10/2004 PO Date = 11/10/2004 Buyer Code = A001 Information Contact = Hayden Park Telephone = Supplier Code = N006 Buyer s Part Number = Vendors Part Number = D Purchase Order Number = AG5P4LC1 Order Line = 0002 Unit of Measure = Each Buyer s Currency = US Dollars CTP**ACT*2.4~ Actual negotiated contract price = 2.4 $ PID*F****BULB-12V 5W(H/METAL FREE)~ N1*ST*MOBIS ALABAMA RDC, U.S.A*92*A001~ Free Product description Ship To Code = A001 FST*230*C*M* ~ Monthly Firm Shipment Quantity = 230 Start Date = 01/01/2005 FST*235*C*M* ~ Monthly Firm Shipment Quantity = 235 Start Date = 02/01/2005 FST*238*D*M* ~ Monthly Planning Shipment Quantity = 238 Start Date = 03/01/2005 CTT*1~ Total number of Lin Items = 1 SE*16*0001~ Total Number of Segments = 16 Transaction Set Control Number = /21/ (4010) 26