830 Planning Schedule with Release Capability

Transcription

1 Global Procurement Planning Schedule with Release Capability Page 1 of Planning Schedule with Release Capability Segment Usage Table 5. Segment usage, requirements, max use and loop infmation. Pos Seg Description Req Max Use Loop Repeat H E A D E R 010 ST Transaction Set Header M 1 0 BFR Beginning Segment f Planning Schedule M 1 > BEGIN N1 LOOP > N1 Name O N2 Additional Name Infmation O N3 Address Infmation O N4 Geographic Location O 1 > END N1 LOOP > D E T A I L > BEGIN LIN LOOP > >1 010 LIN Item Identification M 1 0 UIT Unit Detail O 1 1 DTM Date/Time Reference O PER Administrative Communications Contact O *QTY Quantity O >1 230 ATH Resource Authization O 20 >> BEGIN SLN LOOP >> 1 3 SLN Subline Item Detail O 1 >> END SLN LOOP >> >> BEGIN SDP LOOP >> SDP Ship/Delivery Pattern O FST Fecast Schedule O 260 >> END SDP LOOP >> >> BEGIN SHP LOOP >> SHP Shipped/Received Infmation O REF Reference Numbers O 5

2 Global Procurement Planning Schedule with Release Capability Page 2 of REF Reference Numbers O 5 >> END SHP LOOP >> > END LIN LOOP > S U M M A R Y 010 *CTT Transaction Totals O 1 0 SE Transaction Set Trailer M 1 *(QTY) QTY is used to specify supplemental quantities relevant to the fecast function. However, QTY is not related to the actual fecast quantity in the FST segments. *(CTT) Number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash totals (CTT) is the sum of the values of the quantities (FST01) f each FST segment. Header Infmation ST - Transaction Set Header To indicate the start of a transaction set and to assign a control number. Table 6. ST - Transaction Set Header Data Element Name ST Transaction Set ST 329 Transaction Set Control Number Semantic Req. Data M Z 3/3 Description 830 X12.14 Planning Schedule with Release Capability M AN 4/9 01 The Transaction Set Control Number must be assigned such that it will uniquely identify one transmission of an 830 transaction set. This number is used by the supplier in the 997 acknowledgement to indicate that this specific 830 either was acceptable had errs. ST in this header segment (ST) must match SE in the trailer segment (SE). This number should also be sequential.

3 Global Procurement Planning Schedule with Release Capability Page 3 of 21 BFR - Beginning Segment f Planning Schedule To indicate the beginning of a planning schedule transaction set; whether a ship delivery based fecast; and related fecast envelopes dates Table 7. BFR - Beginning Segment f Planning Schedule Description BFR Transaction Set Purpose M 2/2 Original 05 Replace 06 Confirmation 07 Duplicate 19 Seller Initiated Change 44 Rejection BFR 127 Reference Number X Z AN 1/30 BFR Release Number X AN 1/30 BFR Schedule Qualifier M 2/2 DL Delivery Based JS Buyer Production Sequence Schedule SH Shipment Based BFR Schedule Quantity Qualifier M 1/1 A Actual Discreet Quantities C Cumulative Quantities R Replacement Quantities BFR Date M Z DT 6/6 BFR Date O Z DT 6/6 BFR Date M Z DT 6/6 BFR Contract Number O AN 1/30 BFR Purchase Order O AN 1/22 Number Syntax R03 - At least one of BFR BFR03 is required. Semantic BFR i h id if i b f f i d b h

4 Global Procurement Planning Schedule with Release Capability Page 4 of 21 BFR is the identifying number f fecast assigned by the derer/purchaser BFR06 - fecast hizon start date: The date when the fecast hizon (envelope) begins. BFR07 - fecast hizon end date: The date when the fecast hizon (envelope) ends. BFR08 - date fecast generated: : The date the fecast was generated. N1 - Name To identify a party by type ganization, name and code Table 8. N1 - Name Data Element Name Req. Data Description N Entity Identifier M 2/2 BT Bill-to-Party BY Buying Party (Purchaser) SE Selling Party ST Ship To N1 93 Name X AN 1/35 N Identification Qualifier X 1/2 1 Dun and Bradstreet (Credit Repting) (DUNS) 9 DUNS with 4-digit suffix 91 Assigned by Seller Seller's Agent 92 Assigned by Buyer Buyer's Agent N Identification X AN 2/17 Syntax 03 R03 - At least one of N1 N103 is required. P If either N103 N104 is present, then the other is required.

5 Global Procurement Planning Schedule with Release Capability Page 5 of 21 Comments 04 This segment, used alone, provides the most efficient method of providing ganizational identification. To obtain this efficiency the " " (N104) must provide a key to the table maintained by the transaction processing party. This segment should only be used when it is necessary f crect processing between the trading partners. N1, N103 and N104 may all appear in an occurrence of the N1 segment. N2 - Additional Name Infmation To specify additional names those longer than 35 characters in length Table 9. N2 - Additional Name Infmation N Name M AN 1/35 N2 93 Name O AN 1/35 Description This segment should only be used when it is necessary f crect processing between the trading partners. N3 - Address Infmation To specify the location of the named party Table 10. N3 - Address Infmation

6 Global Procurement Planning Schedule with Release Capability Page 6 of 21 Data Element Name Req. Data N Address Infmation M AN 1/35 N3 166 Address Infmation O AN 1/35 Description This segment should only be used when it is necessary f crect processing between the trading partners. N4 - Geographic Location To specify the geographic place of the names party Table 11. N4 - Geographic Location Data Element Name Req. Data N City Name I AN 2/30 N4 156 State Province I 2/2 N Postal I 3/9 N Country O 2/3 Comments Description N4 is required only if city name (N401) is in the USA Canada This segment should only be used when it is necessary f crect processing between the trading partners. C If Segment N4 is used, then N401, N4 and N403 are required by the IBM Cpation. N404 is the Standard ISO 3166 Country. Detail Infmation

7 Global Procurement Planning Schedule with Release Capability Page 7 of 21 LIN - Item Identification To specify basic item identification data Table 12. LIN - Item Identification Description LIN Assigned O Z AN 1/11 Identification LIN 235 Product/Service Qualifier M 2/2 BE Buyers EC Level Number BP Buyers Part Number CP Carry-over Part Number EC Engineering Change Level PD Part Number Description PI Purchasers Item SK Stock Keeping Unit (SKU) VP Vends (Seller's) Part Number LIN Product/Service M AN 1/30 Semantic 01 LIN01 is the line item identification Comments 04 Data element LIN and LIN03 may be repeated 7 times after the initial occurrence (LIN04 to LIN17). UIT - Unit Detail To specify item unit data Table 13. UIT - Unit Detail

8 Global Procurement Planning Schedule with Release Capability Page 8 of 21 UIT Unit Basis f Measurement Description M 2/2 See Appendix A DTM - Date/Time Reference To specify pertinent dates and times Table 14. DTM - Date/Time Reference Description DTM Date/Time Qualifier M 3/3 097 Transaction Creation DTM 373 Date X DT 6/6 DTM Time X TM 4/8 Syntax R At least one of DTM, DTM03 DTM06 is required. PER - Administrative Communications Contact To identify a person office to whom administrative communications should be directed Table 15. PER - Administrative Communications Contact Description PER Contact Function M 2/2 BD Buyer Name Department CW Confirmed With IC Infmation Contact NT Notification Contact OC Order Contact RD Receiving Dock SU Supplier Contact PER 93 Name O AN 1/35 PER Communication X 2/2 Number Qualifier

9 Global Procurement Planning Schedule with Release Capability Page 9 of 21 PER Communication Number Syntax BN Beeper Number ED Electronic Data Interchange Access EM Electronic Mail FX Facsimile TE Telephone X AN 1/80 03 P If either PER03 PER04 is present, then the other is required. 04 Either PER PER03/PER04 is required to make the occurrence of the PER segment have any meaning. Fmat is xxxxxxxxxx, a continuous string without any fmatting characters. QTY - Quantity To specify quantity infmation Table 16. QTY - Quantity Description QTY Quantity Qualifier M 2/2 17 Quantity On Hand 67 Minimum Ship Qty 69 Incremental Ord Qty - Use f Rate Per Day 72 Minimum Stock Level 73 Maximum Stock Level YW Reder Point Qty QTY 380 Quantity M R 1/15 The Quantity segment will be used to provide inventy on hand and

10 Global Procurement Planning Schedule with Release Capability Page 10 of 21 The Quantity segment will be used to provide inventy on hand and quantity parameters (min, max, etc.) needed to determine when to replenish inventy. ATH - Resource Authization To specify resource authizations (i.e. finished lab, material, etc.) in the planning schedule. Table 17. ATH - Resource Authization Description ATH Resource Authization M 2/2 FI Finished (Lab, Material, and Overhead/ Burden) MT Material ATH 373 Date X Z DT 6/6 ATH Quantity X Z R 1/15 ATH Quantity O R 1/15 ATH Date X Z DT 6/6 Syntax R03 - At least one of ATH ATH03 is required. C If ATH03 is present, then ATH05 is required. C If ATH04 is present, then ATH05 is required. Semantic ATH - resource authization through-date: The date through which the buyer authizes the seller to commit the resource defined in element ATH01. ATH03 - current cumulative requirements quantity: The cumulative quantity that has been authized to-date from the the cumulative start date (ATH05) through the resource authization through-date (ATH). ATH05 - cumulative start date: The date where the cumulative quantity count starts. This date might be the start date of a contract period, a calendar fiscal year, other.

11 Global Procurement Planning Schedule with Release Capability Page 11 of 21 Comments y, It is imperative that negotiations defining "Financial Commitment" have previously occurred and are agreed to by both buyer and seller. ATH04 - Maximum Cumulative Requirements Quantity: The maximum cumulative quantity that has been authized to-date from the cumulative start-date (ATH05) through the resource authization thrudate (ATH). This is a high water mark. If the fecast decreases, the current cumulative requirements quantity also decreases, but the maximum cumulative requirements quantity does not decrease. SLN - Subline Item Detail To specify product subline detail item data Table 18. SLN - Subline Item Detail Description SLN Assigned Identification M Z AN 1/11 SLN Configuration M 1/1 I Included SLN Quantity M R 1/15 SLN Unit Basis f M 2/2 See Appendix A Measurement SLN Product/Service Qualifier O 2/2 BE Buyers EC Level Number BP Buyers Part Number CP Carry-over Part Number EC Engineering Change Level PD Part Number Description PI Purchasers Item SK Stock Keeping Unit (SKU) VP Vends (Seller's) Part Number SLN Product/Service X AN 1/30

12 Global Procurement Planning Schedule with Release Capability Page 12 of 21 Syntax 09 C If SLN09 is present, then SLN10 is required. Semantic SLN01 is the identifying number f the subline item. Data element SLN10 and SLN11 may be repeated 7 times after the initial occurrence (SLN12 to SLN24). SDP - Ship/Delivery Pattern To identify specific ship/delivery requirements Table 19. SDP - Ship/Delivery Pattern SDP SDP 679 Comments Ship/Delivery Calendar Pattern Ship/Delivery Pattern Time M 1/2 N Y M 1/1 F Y Description As Directed None As Directed None The intent of this segment is to define the routine ship delivery patterns, as required, when der quantities are in "buckets", such as weekly, monthly. Ship/Delivery patterns eliminate the need to transmit discrete quantities and dates f each required shipment delivery. It is assumed that a "bucketed" quantity is to be divided equally by the ship/delivery pattern. F example, a weekly quantity of 1 with a delivery pattern of Monday and Wednesday would result in 50 to be delivered on Monday and 50 to be delivered on Wednesday. FST - Fecast Schedule To specify the fecasted dates and quantities

13 Global Procurement Planning Schedule with Release Capability Page 13 of 21 Table 20. FST - Fecast Schedule FST Quantity M R 1/15 FST 680 Fecast Qualifier M 1/1 C D FST Fecast Timing M Z 1/1 Qualifier D F FST Date M DT 6/6 FST Date O DT 6/6 Semantic M Q W Description Firm Planning Discrete Flexible Interval (from Date X through Date Y) Monthly Bucket (Calendar Months) Quarterly (Calendar Quarters) Weekly Bucket (Monday through Sunday) 03 If FST03 - "F" (including flexible interval), then FST04 and FST05 are required. FST04 would be used f the start date of the flexible interval and FST05 would be used f the end date of the flexible interval. Comments As qualified by FST and FST03, FST04 represents either a discrete fecast date, the first date of a fecasted bucket weekly, monthly, quarterly, etc.) the start date of a flexible interval FST04 is shipment delivery date FST05 is only used as the end date of a Flexible Interval (FST03 = F). SHP - Shipped/Received Infmation

14 Global Procurement Planning Schedule with Release Capability Page 14 of 21 To specify shipment and/ receipt infmation Table 21. SHP - Shipped/Received Infmation Description SHP Quantity Qualifier O 2/2 87 Quantity Received SHP 380 Quantity X R 1/15 SHP Date/Time Qualifier X 3/3 050 Received SHP Date O Z DT 6/6 Syntax C01 - If SHP01 is present, then SHP is required. C If SHP04 is present, then SHP03 is required. Semantic 04 SHP04 - The date shipped, delivered, received, the cumulative quantity start date (as qualified by SHP03). Comments The SHP segment is used to communicate shipment, delivery, receipt infmation and may include discrete cumulative quantities, dates, and times. REF - Reference Numbers To specify identifying numbers Table 22. REF - Reference Numbers Description REF Reference Number Qualifier M 2/2 PK Packing List Number REF 127 Reference Number X AN 1/30 REF Description X AN 1/80 Syntax

15 Global Procurement Planning Schedule with Release Capability Page 15 of 21 y R03 - At least one of REF REF03 is required. REF Segment used to identify the quantity received (provided in SHP) to a specific shipment. Summary Infmation CTT - Transaction Totals To transmit a hash total f a specific element in the transaction set Table 23. CTT - Transaction Totals CTT Number of Line Items M N0 1/6 CTT 347 Hash Total O R 1/10 Comments Description This segment is intended to provide hash totals to validate transaction completeness and crectness. 01 CTT01 is the number of LIN segments. CTT is the sum of FST01 quantities. SE - Transaction Set Trailer To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Table 24. SE - Transaction Set Trailer

16 Global Procurement Planning Schedule with Release Capability Page 16 of 21 SE01 96 SE 329 Comments Data Element Name Number of Included Segments Transaction Set Control Number Req. Data M N0 1/10 M AN 4/9 Description SE is the last segment of each transaction set. The value in SE must be equal to the value in ST f this 830 transaction. Segment and Element Infmation Detail Usage Examples Example: 830 Between IBM Locations and Suppliers - Fecast/Pull Process Table 25. Example of 830 Segment / Element Breakdown A sample 830 fecast to establish the quantities and liability f parts to be "pulled" using an 862 shipping schedule. The fecast is executed against a purchase der on the supplier. EDI Data Description of Data ST*830*111111! The ST segment identifies this as an 830 transaction with an identification number of BFR***01*SH*A*950710* *950605***501! N1*BY*IBM CORP*92*988! N3*Building 1, ZIP 66A*1 IBM Street! N4*Raleigh*NC*27704! The BFR segment identifies this recd as the 01 fecast against purchase der 501. The fecast was created on 6/5/95, starts on 7/10/95 and ends on 12/29/95. The N1 segment indicates that the fecast is from IBM plant 988. The N3 segment contains the buyer's building and street address. The N4 segment contains the city, state and ZIP code. LIN*01*VP* *BP*74G2735! The LIN segment identifies this as the first fecast line f vend

17 Global Procurement Planning Schedule with Release Capability Page 17 of 21 UIT*CQ! DTM*097*950605*223010! PER*BD*John Doe*TE* ! ATH*FI*950804! ATH*MT*950915! SDP*Y*Y! FST*321*D*W*950714! FST*432*D*W*950811! FST*543*D*W*951229! CTT*01! SE*39*111111! part number which is IBM part number 74G2735. The UIT segment specifies the unit of measure as cartridge. The DTM segment provides the time in hours, minutes and seconds (223010) that the 830 transaction was created. The creation date is the same as that in the BFR segment (950605). The PER segment contains the buyer's name and telephone number. The ATH segments show liability f four weeks of the finished goods and six week of the material acquired by the supplier to satisfy the fecasted quantities. The SDP segment indicates that the 830 fecast does not authize shipment. Shipment will be authized using the 862 Shipping Schedule. The FST segment is repeated once f each weekly quantity f the duration of the fecasted time frame. This time frame would begin July 14 and end December 29, 1995 f a total period of 25 weeks. The CTT segment shows that there is one LIN segment in this transaction. The SE segment indicates the end of the 830 transaction with control number and 39 segments including the ST and SE segments. Example: 830 Between IBM Locations and Suppliers - Supplier Managed Inventy Table 26. Example of 830 Segment / Element Breakdown A sample 830 fecast to establish the quantities and liability f parts to be replenished by the supplier. The 830 contains inventy and quantity infmation to facilitate the process which is executed against a purchase der on the supplier. EDI Data Description of Data ST*830*111111! The ST segment identifies this as an 830 transaction with an identification number of

18 Global Procurement Planning Schedule with Release Capability Page 18 of 21 BFR***01*SH*A*950710* *950605***501! N1*BY*IBM CORP*92*988! N3*Building 1, ZIP 66A*1 IBM Street! N4*Raleigh*NC*27704! The BFR segment identifies this recd as the 01 fecast against purchase der 501. The fecast was created on 6/5/95, starts on 7/10/95 and ends on 12/29/95. The N1 segment indicates that the fecast is from IBM plant 988. The N3 segment contains the buyer's building and street address. The N4 segment contains the city, state and ZIP code. LIN*01*VP* *BP*74G2735! The LIN segment identifies this as the first fecast line f vend part number which is IBM part number 74G2735. UIT*CQ! The UIT segment specifies the unit of measure as cartridge. PER*BD*John Doe*TE* ! The PER segment contains the buyer's name and telephone number. QTY*17*1! QTY*72*110! QTY*73*3! ATH*FI*950804! ATH*MT*950915! SDP*N*F! FST*321*D*W*950714! FST*432*D*W*950811! FST*543*D*W*951229! The QTY segment shows 1 parts on hand with a minimum stock level of 110 and maximum stock level of 3. The ATH segments show liability f four weeks of the finished goods and six week of the material acquired by the supplier to satisfy the fecasted quantities. The SDP segment indicates that shipment is authized by the 830 as directed in the established agreement. The FST segment is repeated once f each weekly quantity f the duration of the fecasted time frame. This time frame would begin July 14 and end December 29, 1995 f a total period of 25 weeks. SHP*87*125*050*9506! The SHP segment shows that 125 pieces were received on June 2, REF*PK*A253301! The REF segment identifies that the 125 pieces were received with packing list number A CTT*01! The CTT segment shows that there is one LIN segment in this transaction. SE*43*111111! The SE segment indicates the end of the 830 transaction with control number and 43 segments including the ST and SE segments.

19 Global Procurement Planning Schedule with Release Capability Page 19 of 21 APPENDIX A Validation Tables The following is a list of validation tables with codes and descriptions used in this Planning Schedule (830) Subset version 3 release 040. Table : 355X340 Description: Unit Basis f Measurement Length of Data Description Length of Entries of Entries Description CH Y 63 Entry Description Entry Description BA Bale JR Jar BF Board Feet KG Kilogram BG Bag KT Kit BO Bottle LB Pound BR Barrel LT Liter BX Box MJ Minutes CA Case MM Millimeter CB Carboy MO Months CF Cubic Feet MR Meter CG Card OZ Ounce - Av CH Container PA Pail CL Cylinder PC Piece CM Centimeter PK Package CN Can PL Pallet/Unit Load CO Cubic Meters (Net) PR Pair CQ Cartridge PT Pint CR Cubic Meter QT Quart CT Carton RL Roll CW Hundred Pounds (CWT) RM Ream CX Coil SF Square Foot CY Cubic Yard SH Sheet

20 Global Procurement Planning Schedule with Release Capability Page 20 of 21 C8 Cubic Decimeter SM Square Meter DA Days SO Spool DM Decimeter ST Set DR Drum SY Square Yard DZ Dozen TB Tube EA Each TH Thousand FT Foot TK Tank GA Gallon TY Tray GI Imperial Gallons UN Unit GR Gram VI Vial GS Gross WK Week HR Hours YD Yard HU Hundred YR Years IN Inch ZZ Mutually Defined APPENDIX B Source s 16 - D-U-N-S Number SOURCE Dun & Bradstreet AVAILABLE FROM: U.S. D-U-N-S Number assignment and lookup services are available on-line, and through several types of mainframe and personal computer media, through a 9 Number Service ( ), and in print. Dun & Bradstreet Infmation Services Infmation Quality Department D- U-N-S Number Administration 899 Eaton Avenue Bethlehem, PA ABSTRACT: The D-U-N-S Number is a non-indicative nine-digit number assigned and maintained by Dun & Bradstreet to identify unique business establishments. D-U-N-S Numbers are assigned to businesses wldwide. The ninth digit of The D-U-N-S Number is a Modulus Ten Check Digit which catches 1% of single digit errs and 98% of single transposition errs. D-U-N-S numbers provide positive identification of business locations possessing unique, separate, and distinct operations. Through the D-U-N-S Number, Dun & Bradstreet maintains linkage between units of an ganization to easily identify cpate family relationships, such as those between headquarters, branches, subsidiaries, and divisions. The D-U-N-S Number is the non-indicative computer "address" of a business

21 Global Procurement Planning Schedule with Release Capability Page 21 of 21 f which detailed marketing and credit infmation is maintained by Dun & Bradstreet. Subset Update Summary Updated level of HyperText Markup Language (HTML) f use on the Wld Wide Web. [ ]