862 Shipping Schedule

Transcription

1 Global Procurement Shipping Schedule Page 1 of 26 (004010) December 5, Shipping Schedule Functional Group ID=SS Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Shipping Schedule Transaction Set (862) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources. The use of this transaction set will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization. Heading:

2 Global Procurement Shipping Schedule Page 2 of 26 Page Pos. Seg. Req. Loop Notes and No. No. ID Name Des. Max.Use Repeat Comments 010 ST Transaction Set Header 020 BSS Beginning Segment for Shipping Schedule/Production Sequence 030 DTM Date/Time Reference M 1 M 1 O 10 LOOP ID - N N1 Name O N2 Additional Name Information O N3 Address Information O N4 Geographic Location Not Used 090 REF Reference Identification Not Used 100 PER Administrative Communications Contact Not 110 FOB F.O.B. Related Used Instructions O 1 O 12 O 3 O 1 Detail: Page Pos. Seg. Req. Loop Notes and No. No. ID Name Des. Max.Use Repeat Comments

3 Global Procurement Shipping Schedule Page 3 of 26 LOOP ID - LIN LIN Item Identification M UIT Unit Detail M 1 Not 030 PKG Marking, Used Packaging, Loading Not 040 PO4 Item Physical Used Details Not Used 045 PRS Part Release Status O >1 O >1 O 1 Not 047 QTY Quantity O 1 Used 050 REF Reference Identification 060 PER Administrative Communications Contact Not 070 SDP Ship/Delivery Used Pattern O 12 O 1 O 1 LOOP ID - FST FST Forecast Schedule Not Used 090 DTM Date/Time Reference Not Used 100 SDQ Destination Quantity O 1 O >1 O >1 LOOP ID - JIT JIT Just-In-Time Schedule Not Used 120 REF Reference Identification O 1 O 500 LOOP ID - SHP 10 Not 140 SHP Shipped/Received Used Information Not Used 150 REF Reference Identification Not 160 TD1 Carrier Details Used (Quantity and Weight) Not 170 TD3 Carrier Details Used (Equipment) O 1 O 12 O 1 O 1

4 Global Procurement Shipping Schedule Page 4 of 26 ( q p ) Not 180 TD5 Carrier Details Used (Routing Sequence/Transit Time) O 1 Summary: Page Pos. Seg. Req. Loop Notes and No. No. ID Name Des. Max.Use Repeat Comments 010 CTT Transaction Totals 020 SE Transaction Set Trailer O 1 n1 M 1 Transaction Set Notes 1. The number of lines items (CTT01) is the accumulation of number of LIN segments. If used, hash total (CTT02) is the sum of the value of the quantities (FST01) for each FST segment. 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

5 Global Procurement Shipping Schedule Page 5 of 26 Syntax Notes: Semantic Notes: 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). Comments: >> ST Transaction Set Identifier Code M ID 3/3 862 Shipping Schedule >> ST Transaction Set Control Number M AN 4/9 Segment: BSS Beginning Segment for Shipping Schedule/Production Sequence Position: 020 Loop: Level: Heading: Usage: Mandatory Max Use: 1 Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Syntax Notes: 1 At least one of BSS07 or BSS08 is

6 Global Procurement Shipping Schedule Page 6 of 26 Semantic Notes: 1 Use BSS02 to indicate a document number. 2 Use BSS03 to indicate the date of this document. 3 Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins). 4 Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends). 5 BSS08 is the identifying number for a forecast assigned by the orderer/purchaser. Comments: Notes: When the "Blanket" purchase order authorizing the Pull (862) transaction contains multiple part numbers then the "Blanket" purchase order line item is required for invoicing and will be provided by putting the Scheduling Agreement Delivery Line number in BSS07 and the Scheduling Agreement Material Line Number in BSS08. BSS09 is the contract number governing this commitment >> BSS Transaction Set Purpose Code M ID 2/2 00 Original 05 Replace 06 Confirmation 07 Duplicate 19 Seller initiated change

7 Global Procurement Shipping Schedule Page 7 of 26 >> BSS Reference Identification M AN 1/30 >> BSS Date M DT 8/8 >> BSS Schedule Type Qualifier M ID 2/2 DL SH Delivery Based Shipment Based >> BSS Date M DT 8/8 >> BSS Date M DT 8/8 BSS Release Number X AN 1/30 BSS Reference Identification X AN 1/30 BSS Contract Number O AN 1/30 BSS Purchase Order Number O AN 1/22 Segment: DTM Date/Time Reference Position: 030 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 2 If DTM04 is present, then DTM03 is 3 If either DTM05 or DTM06 is present, then the other is

8 Global Procurement Shipping Schedule Page 8 of 26 Semantic Notes: Comments: Notes: Both DTM02 and DTM03 must be present for this segment to be of any value. >> DTM Date/Time Qualifier M ID 3/3 011 Shipped 017 Estimated Delivery 035 Delivered 036 Expiration 069 Promised for Delivery 097 Transaction Creation 108 Postmark DTM Date X DT 8/8 DTM Time X TM 4/8 DTM Time Code O ID 2/2 CT ET MT PT Central Time Eastern Time Mountain Time Pacific Time Segment: N1 Name Position: 050

9 Global Procurement Shipping Schedule Page 9 of 26 Loop: N1 Optional Level: Heading: Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is 2 If either N103 or N104 is present, then the other is Semantic Notes: 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 N105 and N106 further define the type of entity in N101. Notes: This segment should only be used when it is necessary for correct processing between the trading partners. N102, N103 and N104 may all appear in one occurence N104 is the Requestor's identification code >> N Entity Identifier Code M ID 2/3

10 Global Procurement Shipping Schedule Page 10 of 26 BT Bill-to-Party BY Buying Party (Purchaser) SE Selling Party ST Ship To N Name X AN 1/60 N Identification Code Qualifier X ID 1/2 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N- S+4, D- U-N-S Number with Four Character Suffix 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer or Buyer's Agent N Identification Code X AN 2/80 Segment: N2 Additional Name Information Position: 060 Loop: N1 Optional Level: Heading: Usage: Optional Max Use: 2

11 Global Procurement Shipping Schedule Page 11 of 26 Purpose: To specify additional names or those longer than 60 characters in length Syntax Notes: Semantic Notes: Comments: Notes: This segment should only be used when it is necessary for correct processing between the trading partners. >> N Name M AN 1/60 N Name O AN 1/60 Segment: N3 Address Information Position: 070 Loop: N1 Optional Level: Heading: Usage: Optional Max Use: 2 Purpose: To specify the location of the named party Syntax Notes: Semantic Notes: Comments:

12 Global Procurement Shipping Schedule Page 12 of 26 Notes: This segment should only be used when it is necessary for correct processing between the trading partners. >> N Address Information M AN 1/55 N Address Information O AN 1/55 Segment: N4 Geographic Location Position: 080 Loop: N1 Optional Level: Heading: Usage: Optional Max Use: 1 Purpose: To specify the geographic place of the named party Syntax Notes: 1 If N406 is present, then N405 is Semantic Notes: Comments: 1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the U.S. or Canada.

13 Global Procurement Shipping Schedule Page 13 of 26 Notes: This segment should only be used when it is necessary for correct processing between the trading partners. If segment N4 is used, then N401, N402 and N403 are required by the IBM Corporation N404 is the Standard ISO 3166 Country Code N City Name O AN 2/30 N State or Province Code O ID 2/2 N Postal Code O ID 3/15 N Country Code O ID 2/3 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 either LIN04 or LIN05 is present, then the other is 2 If either LIN06 or LIN07 is present, then the other is 3 If either LIN08 or LIN09 is present, then the other is 4 If either LIN10 or LIN11 is present, then the other is

14 Global Procurement Shipping Schedule Page 14 of 26 5 If either LIN12 or LIN13 is present, then the other is 6 If either LIN14 or LIN15 is present, then the other is 7 If either LIN16 or LIN17 is present, then the other is 8 If either LIN18 or LIN19 is present, then the other is 9 If either LIN20 or LIN21 is present, then the other is 10 If either LIN22 or LIN23 is present, then the other is 11 If either LIN24 or LIN25 is present, then the other is 12 If either LIN26 or LIN27 is present, then the other is 13 If either LIN28 or LIN29 is present, then the other is 14 If either LIN30 or LIN31 is present, then the other is Semantic Notes: 1 LIN01 is the line item identification Comments: 1 See the Data Dictionary for a complete list of IDs. 2 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. Notes: Data elements LIN02 and LIN03 may be repeated 7 times after the initial occurrence (LIN04 to LIN17)

15 Global Procurement Shipping Schedule Page 15 of 26 LIN Assigned Identification O AN 1/20 >> LIN Product/Service ID Qualifier M ID 2/2 BE BP CP EC PD PI SK VP Buyer's Engineering Change Level Number Buyer's Part Number Carry-over Part Number Engineering Change Level Part Number Description Purchaser's Item Code Stock Keeping Unit (SKU) Vendor's (Seller's) Part Number >> LIN Product/Service ID M AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Refer To Code List In LIN02 LIN Product/Service ID X AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Refer To Code List In LIN02 LIN Product/Service ID X AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Refer To Code List In LIN02

16 Global Procurement Shipping Schedule Page 16 of 26 LIN Product/Service ID X AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Refer To Code List In LIN02 LIN Product/Service ID X AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Refer To Code List In LIN02 LIN Product/Service ID X AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Refer To Code List In LIN02 LIN Product/Service ID X AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Refer To Code List In LIN02 LIN Product/Service ID X AN 1/48 Segment: UIT Unit Detail Position: 020 Loop: LIN Mandatory Level: Detail: Usage: Mandatory Max Use: 1 Purpose: To specify item unit data

17 Global Procurement Shipping Schedule Page 17 of 26 Syntax Notes: 1 If UIT03 is present, then UIT02 is Semantic Notes: Comments: >> UIT01 C001 Composite Unit of Measure >> C Unit or Basis for Measurement Code M M ID 2/2 BA BF BG BO BR BX C8 CA CB CF CG CH CL CM CN CO CQ Bale Board Feet Bag Bottle Barrel Box Cubic Decimeter Case Carboy Cubic Feet Card Container Cylinder Centimeter Can Cubic Meters (Net) Cartridge

18 Global Procurement Shipping Schedule Page 18 of 26 CQ Cartridge CR Cubic Meter CT Carton CW Hundred Pounds (CWT) CX Coil CY Cubic Yard DA Days DM Decimeter DR Drum DZ Dozen EA Each FT Foot GA Gallon GI Imperial Gallons GR Gram GS Gross HR Hours HU Hundred IN Inch JR Jar KG Kilogram KT Kit LB Pound LT Liter MJ Minutes MM Millimeter MO Months MR Meter OZ Ounce - Av PA Pail PC Piece PK Package PL Pallet/Unit Load

19 Global Procurement Shipping Schedule Page 19 of 26 PR Pair PT Pint QT Quart RL Roll RM Ream SF Square Foot SH Sheet SM Square Meter SO Spool ST Set SY Square Yard TB Tube TH Thousand TK Tank TY Tray UN Unit VI Vial WK Week YD Yard YR Years ZZ Mutually Defined Segment: REF Reference Identification Position: 050 Loop: LIN Mandatory Level: Detail: Usage: Optional Max Use: 12 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is

20 Global Procurement Shipping Schedule Page 20 of 26 2 If either C04003 or C04004 is present, then the other is 3 If either C04005 or C04006 is present, then the other is Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: Notes: In REF02 code CD is used to identify a credit card number >> REF Reference Identification Qualifier M ID 2/3 3Y AP CD DK LS Receiver Assigned Drop Zone Accounts Receivable Number Credit Note Number Dock Number Bar-Coded Serial Number REF Reference Identification X AN 1/30 Segment: PER Administrative Communications Contact Position: 060 Loop: LIN Mandatory

21 Global Procurement Shipping Schedule Page 21 of 26 Level: Detail: Usage: Optional Max Use: 1 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is 2 If either PER05 or PER06 is present, then the other is 3 If either PER07 or PER08 is present, then the other is Semantic Notes: Comments: Notes: Either PER02 or PER03/PER04 is required to make the occurrence of the PER segment have any meaning The format for PER04 is xxxxxxxxxx, a continuous string without any formattng characters >> PER Contact Function Code M ID 2/2 BD CW IC NT OC Buyer Name or Department Confirmed With Information Contact Notification Contact Order Contact

22 Global Procurement Shipping Schedule Page 22 of 26 RD Receiving Dock SU Supplier Contact PER02 93 Name O AN 1/60 PER Communication Number Qualifier X ID 2/2 BN ED EM FX TE Beeper Number Electronic Data Interchange Access Number Electronic Mail Facsimile Telephone PER Communication Number X AN 1/80 Segment: FST Forecast Schedule Position: 080 Loop: FST Optional Level: Detail: Usage: Optional Max Use: 1 Purpose: To specify the forecasted dates and quantities Syntax Notes: 1 If either FST06 or FST07 is present, then the other is 2 If either FST08 or FST09 is present, then the other is Semantic Notes: 1 If FST03 equals "F" (indicating flexible interval), then FST04 and FST05 are FST04 would be used for the start date of the flexible interval and FST05 would be used for the end date of the flexible interval.

23 Global Procurement Shipping Schedule Page 23 of 26 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. 2 FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24- hour clock to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as a.m. or p.m. Notes: The FST segment is used to communicate shipment or delivery information and indicates discrete quantities and dates. The BSS04 date element will show if the shipment/delivery information is delivery or shipment based. FST05 is only used as the end date of a Flexible Interval (FST03 = F) >> FST Quantity M R 1/15 >> FST Forecast Qualifier M ID 1/1 C Firm >> FST Forecast Timing Qualifier M ID 1/1 D F Discrete Flexible Interval (from Date X through Date Y) >> FST Date M DT 8/8 FST Date O DT 8/8

24 Global Procurement Shipping Schedule Page 24 of 26 Segment: JIT Just-In-Time Schedule Position: 110 Loop: JIT Optional Level: Detail: Usage: Optional Max Use: 1 Purpose: To identify the specific shipping/delivery time in terms of a 24-hour clock and identify the associated quantity Syntax Notes: Semantic Notes: Comments: Notes: The JIT segment is use only when deliveries of the quantity specified in the FST segment are to be split and delivered at specific times in discrete quantities. >> JIT Quantity M R 1/15 >> JIT Time M TM 4/8 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary:

25 Global Procurement Shipping Schedule Page 25 of 26 Usage: Optional Max Use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If either CTT03 or CTT04 is present, then the other is 2 If either CTT05 or CTT06 is present, then the other is Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. Notes: CTT01 is the number of LIN segments CTT02 is the sum of FST01 quantities >> CTT Number of Line Items M N0 1/6 CTT Hash Total O R 1/10 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary: Usage: Mandatory Max Use: 1

26 Global Procurement Shipping Schedule Page 26 of 26 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) Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. Notes: The value in SE02 must be equal to the value in ST02 >> SE01 96 Number of Included Segments >> SE Transaction Set Control Number M N0 1/10 M AN 4/9 Last updated 06/11/01