856 Ship Notice/Manifest

Transcription

1 Global Procurement Ship Notice/Manifest Page 1 of Ship Notice/Manifest Segment Usage Table 5. Segment usage, requirements, max use and loop information. Pos No. Seg ID Description Req Max Use Loop Repeat H E A D E R 010 ST Transaction Set Header M BSN Beginning Segment for Ship Notice M DTM Date/Time Reference I 10 D E T A I L > BEGIN HL LOOP > *HL Hierarchical Level M LIN Item Identification Detail I SN1 Item Detail (Shipment) I PRF Purchase Order Reference I PO4 Item Physical Details O PID Product/Item Description O PWK Paperwork O TD5 Carrier Details (Routing I 12 Sequence/Transit Time) 140 TD4 Carrier Details (Special I 5 Handling/Hazardous Materials) 150 REF Reference Numbers I >1 >> BEGIN N1 LOOP >> N1 Name I N2 Additional Name Information O N3 Address Information O N4 Geographic Location O PER Administrative Communications O 3 Contact 280 FOB F.O.B. Related Instructions O 1 >> END N1 LOOP >> > END HL LOOP > S U M M A R Y 010 *CTT Transaction Totals O SE Transaction Set Trailer M 1

2 Global Procurement Ship Notice/Manifest Page 2 of 58 Notes * (CTT) Number of line items (CCT01) is the accumulation of the number of HL segments. If used, (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment. Comments * (HL) The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. Header Information ST - Transaction Set Header To indicate the start of a transaction set and to assign a control number. Table 6. ST - Transaction Set Header Elem. Elem. Data Element Name ID No. ST Transaction Set ID ST Transaction Set Control Number Semantic Notes Req. Data Type M/M or M Z ID 3/3 Description 856 X12.10 Ship Notice/Manifest M AN 4/9 01 The Transaction Set Control Number must be assigned such that it will uniquely identify one transmission of an 856 transaction set. This number is used by the supplier in the 997 acknowledgement to indicate that this specific 856 either was acceptable or had errors. ST02 in this header segment (ST) must match SE02 in the trailer segment (SE). This number should also be sequential. BSN - Beginning Segment for Ship Notice To transmit identifying numbers, dates and other basic data relating to the transaction set Table 7. BSN - Beginning Segment for Ship Notice

3 Global Procurement Ship Notice/Manifest Page 3 of 58 Elem. ID Elem. No. BSN BSN Data Element Name Req. Data Type Transaction Set Purpose Shipment Identification M/M or M ID 2/2 Description 00 Original 01 Cancellation 05 Replace (BSN02 value equal to original 856 BSN02 value) 06 Confirmation 07 Duplicate M AN 2/30 BSN Date M DT 6/6 (YYMMDD) BSN Time M TM 4/8 (HHMM) or (HHMMSS) Comments 00 For shipments internal to IBM the first three positions of the shipment identification number (BSN02) must be "IBM". DTM - Date/Time Reference To specify pertinent dates and times Table 8. DTM - Date/Time Reference Elem. ID Elem. No. Data Element Name Req. Data Type M/M or Description DTM Date/Time Qualifier M ID 3/3 011 Shipped 017 Estimated Delivery 035 Delivery 069 Promised for Delivery 097 Transaction Creation 108 Postmark DTM Date X DT 6/6 (YYMMDD) DTM Time X M 4/8 (HHMM) or (HHMMSS) DTM Time O ID 2/2 Syntax Notes 02

4 Global Procurement Ship Notice/Manifest Page 4 of 58 Note R At least one of DTM02, DTM03 or DTM06 is required. 00 If your location has a system which tracks transit time for a shipment, the DTM segment must be mandatory. The supplier must provide DTM01 (with a code of "011"), DTM02/DTM03 (with the actual ship date and time) and DTM04. This applies to both supplier and IBM shipments. Detail Information HL - Hierarchical Level To identify dependencies among and the content of hierarchically related groups of data segments. Table 9. HL - Hierarchical Level Elem. Elem. Data Element Name ID No. HL HL HL HL Notes Hierarchical ID Number Hierarchical Parent ID Number Hierarchical Level Hierarchical Child Req. Data Type M/M or M AN 1/12 O AN 1/12 M ID 1/2 I S T O ID 1/1 Description Item Shipment Shipping Tare (CASE) 0 No subordinate HL segment in this hierarchical structure 1 Additional subordinate HL segments in this hierarchical structure. 00 IBM will use the hierarchical level codes in the following sequence: Shipment (S) is IBM's top level and will carry information applicable to the total shipment The bar coded serial n mber (incl ding the 2S

5 Global Procurement Ship Notice/Manifest Page 5 of 58 the total shipment. The bar-coded serial number (including the 2S identifier) will be in the first REF segment at this level. Ship-from location, ship-to location, carrier number, paperwork identification and shipment information (packing slip number, weights, package/container counts) are specified at the shipment level. Shipping Tare (T) or "case" in IBM terminology is IBM's middle level specification. The bar-coded serial number for a case (carrying the 9S identifier) will be in the first REF segment at this level. Item (I) is IBM's lowest level of the hierarchy. Information at this level identifies parts or serialized components (using the 3S or 1S or 11S or S number) which are part of the shipment, using the lowest level of packaging or using a part number or machine/model/serial number identification. Not every shipment will require the use of all three hierarchical level codes. The minimum required for incoming shipments from suppliers or other IBM locations (interplant) is shipment identification (S level containing the bar-coded serial number) and item identification (I level containing part or machine/model/serial number). Outgoing shipments of IBM products require use of three hierarchical levels - Shipment (S), Shipping Tare (T) and Item (I). LIN - Item Identification To specify basic item identification data Table 10. LIN - Item Identification Elem. ID Elem. No. LIN LIN Data Element Name Req. Data Type Assigned Identification Product/Service ID Qualifier M/M or O Z AN 1/11 M ID 2/2 Description AB Assembly AC Aggregation (Used to consolidate Part Families) BN Bar d Serial Number BP Buyers Part Number ' CH Country of Origin EC Engineering Change Level MG Manufacturers Part Number MN Model Number

6 Global Procurement Ship Notice/Manifest Page 6 of 58 MN Model Number MT Major Product/Material/ Machine Type PD Part Number Description PI Purchasers Item PN Company Part Number SK Stock Keeping Unit SN Serial Number SV Service Rendered VC Vendors (Sellers) Catalog Number VP Vendors (Sellers) Part Number LIN Product/Service ID M AN 1/30 Semantic Notes 01 LIN01 is the line item identification Comments 02 LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. Notes 00 The LIN segment is required to identify the country of origin and IBM's part number or machine/model/serial number at the Item (I) level. SN1 - Item Detail (Shipment) To specify line item detail relative to shipment Table 11. SN1 - Item Detail (Shipment) Elem. ID Elem. No. SN SN SN Data Element Name Req. Data Type Assigned Identification Number of Units Shipped Unit or Basis for Measurement M/M or O AN 1/11 M R 1/10 Description M ID 2/2 See Appendix A

7 Global Procurement Ship Notice/Manifest Page 7 of 58 SN Quantity Shipped to Date SN Unit or Basis for Measurement Semantic Notes O R 1/9 X ID 2/2 See Appendix A 01 SN101 is the ship notice line item identification. Comments 03 SN103 defines the unit of measurement for both SN102 and SN104. Notes 00 The SN1 segment is required to specify the quantity being shipped, the unit of measure and the quantity shipped to date (if applicable). PRF - Purchase Order Reference To provide reference to a specific purchase order Table 12. PRF - Purchase Order Reference Elem. ID Elem. No. Data Element Name Req. Data Type M/M or PRF Purchase Order M AN 1/22 Number PRF Release Number O AN 1/30 PRF Change Order O AN 1/8 Sequence Number PRF Purchase Order Date I DT 6/6 PRF Assigned O AN 1/11 Identification PRF Contract Number O AN 1/30 Notes Description The PRF segment is required (from external suppliers) to identify the IBM purchase order being satisfied with this shipment. Only purchase order related data is to appear in this segment. For interplant shipments this segment must not be used. The release number is required to specify the deliver/pull number against a previously placed order or pull (862) request." Th PO d (PRF04) i i d b IBM If i i il bl h h

8 Global Procurement Ship Notice/Manifest Page 8 of 58 The PO date (PRF04) is required by IBM. If it is not available then the ship date must be used. PO4 - Item Physical Details To specify the physical qualities, packaging, weights and dimensions relating to the item Table 13. PO4 - Item Physical Details Elem. ID Elem. No. Data Element Name Req. Data Type M/M or Description PO Weight Qualifier O ID 1/2 A3 Shipper's Weight T Tare Weight U Weight per Unit PO Gross Weight per X R 1/9 Pack PO Unit or Basis for Measurement X ID 2/2 GR Gram HP Hundred Pounds KG Kilogram LB Pound OZ Ounce - Av TO Troy Ounce PO Gross Volume per X R 1/9 Pack PO Unit or Basis for Measurement X ID 2/2 CM Centimeter FT Foot IN Inch MR Meter YD Yard PO Length O R 1/8 PO Width O R 1/8 PO Height O R 1/8 PO Unit or Basis for X ID 2/2 See Appendix A Measurement Syntax Notes 05 C If PO405 is present, then PO406 is required. 06 C0607 If PO406 is present then PO407 is required

9 Global Procurement Ship Notice/Manifest Page 9 of 58 C If PO406 is present, then PO407 is required P If either PO408 or PO409 is present, then the other is required. C If PO410 is present, then PO413 is required. C If PO411 is present, then PO413 is required. C If PO412 is present, then PO413 is required. L If PO413 is present, then at least one of PO410, PO411 or PO412 is required. Comments 13 PO413 defines the unit of measure for PO410, PO411, and PO412. PID - Product/Item Description To describe a product or process in coded or free-form format Table 14. PID - Product/Item Description Elem. ID Elem. No. Data Element Name Req. Data Type M/M or PID Item Description Type M ID 1/1 F PID Prod/Process O ID 2/3 Characteristic PID Agency Qualifier X Z ID 2/2 PID Product Description X Z AN 1/12 PID Description X AN 1/80 Syntax Notes Description Free-form C If PID04 is present, then PID03 is required. R At least one of PID04 or PID05 is required. Semantic Notes

10 Global Procurement Ship Notice/Manifest Page 10 of Use PID03 to indicate the organization that publishes the code list being referred to. 04 PID04 should be used for industry-specific product description codes. Comments Notes 00 The PID segment is required for non-production items that do not have a part number assigned. PWK - Paperwork To identify the type and transmission of paperwork or supporting information. Table 15. PWK - Paperwork Elem. ID. Elem. No. Data Element Name Req. Data Type M/M or Description PWK Report Type M ID 2/2 11 Chemical Analysis CP Certificate of Compliance (Material Certification) SM Shipping Manifests PWK Report Transmission O ID 2/2 BM By Mail SE Electronically Before Shipping PWK04 98 Entity Identifier O ID 2/2 AD Party to be advised (Written orders) BY Buying Party (Purchaser) CM Customs PA Party to Receive Inspection Report PJ Party to Receive Correspondence PWK05 66 Identification Qualifier X ID 1/2

11 Global Procurement Ship Notice/Manifest Page 11 of 58 1 DUNS # 2 Standard Carrier Alpha (SCAC) 9 DUNS with 4- character suffix 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer PWK06 67 Identification X AN 2/17 PWK Description O AN 1/80 Syntax Notes 05 P If either PWK05 or PWK06 is present, then the other is required. Comments PWK05 and PWK06 may be used to identify the addressee by a code number. PWK07 may be used to indicate special information to be shown on the specified report. Notes 05 The SCAC code is required for the over-the-road carriers. TD5 - Carrier Details (Routing Sequence/Transit Time) To specify the carrier, sequence of routing and to provide transit time information Table 16. TD5 - Carrier Details (Routing Sequence/Transit Time) Elem. Elem. Data Element Name Req. Data M/M Description ID No. Type or TD Routing Sequence I ID 1/2 B Origin/Delivery Carrier (Any mode) TD Identification X ID 1/2 Qualifier 1 DUNS 2 Standard Carrier Alpha (SCAC)

12 Global Procurement Ship Notice/Manifest Page 12 of 58 4 International Air Transport Association (IATA) 9 DUNS with 4- character suffix 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer TD Identification X AN 2/17 TD Transportation Method/Type X ID 1/2 A Air AE Air Express BU Bus C Consolidation CE Customer Pickup/Customers expense D Parcel Post E Expedited Truck L Contract Carrier LT Less Than Trailer Load (LTL) M Motor (Common Carrier) R Rail SR Supplier Truck T Best Way (Shipper's Option) U Private Parcel Service TD Routing X AN 1/35 TD Location Qualifier I ID 1/2 OR Origin (Shipping Point) TD Location Identifier X AN 1/30 Syntax Notes R At least one of TD502, TD504, TD505, TD506 or TD512 is required. C If TD502 is present, then TD503 is required. C If TD507 is present, then TD508 is required. Comments

13 Global Procurement Ship Notice/Manifest Page 13 of The identification code of sending location can be in TD503. TD4 - Carrier Details (Special Handling or Hazardous Materials or Both) To specify transportation special handling requirements or hazardous materials information or both Table 17. TD4 - Carrier Details (Special Handling or Hazardous Materials or Elem. ID Elem. No. TD TD TD Data Element Name Req. Data Type Special Handling Hazardous Material Qualifier Hazardous Material Class M/M or X ID 2/3 TD Description X AN 1/80 Syntax Notes Description HM Endorsed as Hazardous Materials X ID 1/ Level DOT 6 Airline Tariff 6D 9 49 Series of the Standard Transportation Commodity (STCC) A IATA/ICAO D Hazardous Materials ID, DOT X AN 2/ R At least one of TD401, TD402 or TD404 is required. C If TD402 is present, then TD403 is required. Notes 00 The TD4 segment is only required when shipping hazardous material.

14 Global Procurement Ship Notice/Manifest Page 14 of 58 REF - Reference Numbers To specify identifying numbers Table 18. REF - Reference Numbers Elem. ID Elem. No. Data Element Name Req. Data Type M/M or Description REF Reference Number M ID 2/2 See Appendix A Qualifier REF Reference Number X AN 1/30 REF Description X AN 1/80 Syntax Notes 02 R At least one of REF02 or REF03 is required. Notes 00 The first occurrence of the REF segment under the top HL segment (loop) is required by IBM and will use the qualifier "LS" to specify the bar-coded serial number of the shipment. Reference IBM distribution or packaging documentation for the format of this bar-coded serial number. If a system is utilized to track incoming shipment status, the REF segment must be made mandatory. The shipper must provide either the bill of lading number ("BM") or carrier PRO number ("CN") so that shipment status (214 transaction set) may be associated with the correct 856 transaction information. For internal IBM (interplant) 856 transactions, the REF segment (using the qualifier "IL") must be used to specify the IPR or pull number with which the goods were ordered. In addition, if the 856 is sent as a result of a pull transaction (862); a second REF segment (using the RE qualifier) must be sent to specify the release number. At the item level, the REF segment must be used to identify each unique number for Asset Protection (APC) 3, 4,and For the supplier managed inventory (SMI) process; it is required at the item level to use PK in REF01 and the packing list number in REF02. N1 - Name To identify a party by type or organization, name and code

15 Global Procurement Ship Notice/Manifest Page 15 of 58 Table 19. N1 - Name Elem. Elem. Data Element Name ID No. Req. Data Type M/M or Description N Entity Identifier M ID 2/2 AK Party to Whom Acknowledgment Should Be Sent BF Billed From BO Broker or Sales Office (Branch Office) BT Party to be Billed For Other Than Freight (Bill To) BY Buying Party (Purchaser) CS Consolidator DB Distributor Branch Office MA Party for whom Item is Intended OB Ordered By PF Party to Receive the Freight Bill PN Party to Receive Shipping Notice SD Sold To and Ship To SE Selling Party SF Ship From SH Shipper ST Ship To N Name X AN 1/35 N Identification Qualifier X ID 1/2 1 DUNS # 9 DUNS with 4- character suffix 91 Assigned by Seller or Seller's Agent 92 Assigned by Buyer N Identification X AN 2/17 Syntax Notes R At least one of N102 or N103 is required. P0304 If i h N103 N104 i h h h i i d

16 Global Procurement Ship Notice/Manifest Page 16 of 58 Comments P If either N103 or N104 is present, then the other is required. 04 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. Notes N102, N103 and N104 may all appear in an occurrence of the N1 For Internal IBM shipments (interplant orders) it is recommended that two N1 loops be used at the top hierarchical level to indicate the selling ("SE") location and the ship to ("ST") location. Qualifier code "92" must be used in these N1 loop occurrences. N2 - Additional Name Information To specify additional names or those longer than 35 characters in length Table 20. N2 - Additional Name Information Elem. Elem. Data Element Name Req. Data M/M ID No. Type or N Name M AN 1/35 N Name O AN 1/35 Description N3 - Address Information To specify the location of the named party Table 21. N3 - Address Information Elem. Elem. Data Element Name ID No. Req. Data Type M/M or N Address Information M AN 1/35 N Address Information O AN 1/35 Description N4 - Geographic Location To specify the geographic place of the names party

17 Global Procurement Ship Notice/Manifest Page 17 of 58 Table 22. N4 - Geographic Location Elem. Elem. Data Element Name ID No. Req. Data Type M/M or N City Name O AN 2/30 N State or Province O ID 2/2 N Postal O ID 3/9 N Country O ID 2/3 Comments Description A combination of either N401 through N404 may be adequate to specify a location. N402 is required only if city name (N401) is in the USA or Canada. Notes C If Segment N4 is used, then N401, N402 and N403 are required by the IBM Corporation. N403 is the five position Zip code or the extended Zip + 4. N404 is the Standard ISO 3166 Country. PER - Administrative Communications Contact To identify a person or office to whom administrative communications should be directed Table 23. PER - Administrative Communications Contact Elem. Elem. Data Element Name Req. Data M/M Description ID No. Type or PER Contact Function M ID 2/2 BD Buyer Name or Department CW Confirmed With ED Emergency Contact- Consignee IC Information Contact NT Notification Contact

18 Global Procurement Ship Notice/Manifest Page 18 of 58 NT Notification Contact OC Order Contact RD Receiving Dock SU Supplier Contact PER02 93 Name O AN 1/35 PER Communication Number Qualifier X ID 2/2 BN Beeper Number ED Electronic Data Interchange Access No. EM Electronic Mail FX Facsimile TE Telephone PER Communication X AN 1/80 Number Syntax Notes 03 P If either PER03 or PER04 is present, then the other is required. Notes 02 Either PER02 or PER03/PER04 is required to make the occurrence of the PER segment have any meaning. FOB - F.O.B. Related Instructions To specify transportation instructions relating to shipment. Table 24. FOB - F.O.B. Related Instructions Elem. ID Elem. No. Data Element Name Req. Data Type M/M or FOB Shipment Method of M Z ID 2/2 Payment FOB Location Qualifier X Z ID 1/2 FOB Description O AN 1/80 FOB Transportation Terms O ID 2/2 Qualifier FOB Transportation Terms X ID 3/3 FOB Location Qualifier X Z ID 1/2 FOB Description O AN 1/80 FOB08 54 Risk of Loss Qualifier O Z ID 2/2 Description

19 Global Procurement Ship Notice/Manifest Page 19 of 58 FOB Description X AN 1/80 Syntax Notes C If FOB03 is present, then FOB02 is required. C If FOB04 is present, then FOB05 is required. C If FOB07 is present, then FOB06 is required. C If FOB08 is present, then FOB09 is required. Semantic Notes FOB01 indicates which party will pay the carrier. FOB02 is the code specifying transportation responsibility location. FOB06 is the code specifying the title passage location. FOB08 is the code specifying the point at which the risk of loss loss transfers. This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07. Summary Information CTT - Transaction Totals To transmit a hash total for a specific element in the transaction set. tcap.ctt - Transaction Totals Elem. Elem. Data Element Name Req. Data M/M Description ID No. Type or CTT Number of Line Items M N0 1/6 Comments Notes 01 Number of line items (CTT01) is the accumulation of the number of HL segments.

20 Global Procurement Ship Notice/Manifest Page 20 of 58 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 25. SE - Transaction Set Trailer Elem. Elem. Data Element Name ID No. SE01 96 SE Comments Number of Included Segments Transaction Set Control Number Req. Data Type M/M or M N0 1/10 M AN 4/9 Description 00 SE is the last segment of each transaction set. Notes 02 The value in SE02 must be equal to the value in ST02. Segment and Element Information Detail Usage Examples 856 Between IBM Locations and Suppliers Examples Table 26. Single Purchase Order Shipment This table provides an example of an inbound 856 from a supplier that has one purchase order. EDI Data Description of Data ST*856* The ST segment identifies this as an 856 transaction with an identification number of BSN*00* *940920*1000 DTM*011*940920*1000 The BSN segment is mandatory. In this case it indicates that an original(00) 856 transaction, with a shipment identification number ( ) was created at 10:00 am on September 20, The DTM is a mandatory segment. The value "011" in the DTM01 indicates that the item was shipped at 10:00am on September 20, 1994

21 Global Procurement Ship Notice/Manifest Page 21 of 58 HL*1**S*1 TD5*B*2*PRES*L*PRESTON TRUCKING**OR REF*LS*2SAAA The HL segment is mandatory. The HL01 indicates the number of the HL, the HL02 does not have a value which means it is not a subordinate. The HL03 value of "S" means that the HL is at the shipment level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The TD5 segment is required for tracking purposes within IBM. This example indicates that the shipment is being transported by Preston Trucking. Preston's SCAC code is PRES. The "LS" is the bar code qualifier, the "2SAAA " is the unique licence plate number for the entire shipment. Note: The licence plate bar code number should matched the bar code on on the packing list and/or the physical shipment. REF*BM* The Bill of Lading number is N1*ST*IBM CORP - PCC*92*988 N3*305 DOCK*3039 Cornwallis Rd N4*Durham*NC*27709*US PER*BD*John Doe N1*SE*ANY SHIPPER*92* N3*PO BOX 1234 N4*ANYTOWN*SC*29606*US HL*2*1*I*0 LIN*1*BP* *CH*US SN1*1*20*EA PRF*L54601*** The N1 segment indicates that the shipment is being sent to the IBM Corp - PCC. 988 indicates the physical plant code. Building and street address City, State, Zip and Country. The buyer name is John Doe The seller's name is ANY SHIPPER Address of seller City, State, Zip and country. This is the second HL segment and it is a subordinate of the shipment HL. It is at the Item (I) level and it does not have a subordinate. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 20 and "EA" is the unit of measure code for each. The PRF segment is used to identify the purchase order number, of the shipment, in PRF01. CTT*2 Note: It is not necessary in IBM to use PRF02 and PRF03, however, some translators require that PRF04 be used. There are 2 HL segments used in this

22 Global Procurement Ship Notice/Manifest Page 22 of 58 CTT 2 SE*20* There are 2 HL segments used in this transaction There are 20 segments used in this transaction identified as Table 27. Single Purchase Order Shipment. This table provides an example of an inbound 856 from a supplier that has one purchase and the part number has an APC of 3, 4, or 5. EDI Data Description of Data ST*856* The ST segment identifies this as an 856 transaction with an identification number of BSN*00* *940120*0900 DTM*011*940120*0900 HL*1**S*1 TD5*B*2*PRES*L*PRESTON TRUCKING**OR REF*LS*2SAAA The BSN segment is mandatory. In this case it indicates that an original (00) 856 transaction, with a shipment identification number ( ) was created at 9:00 am on January 20, The DTM is a mandatory segment. The value "011" in the DTM01 indicates that the item was shipped at 9:00am on January 20, 1994 The HL segment is mandatory. The HL01 indicates the number of the HL, the HL02 does not have a value which means it is not a subordinate. The HL03 value of "S" means that the HL is at the shipment level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The TD5 segment is required for tracking purposes within IBM. This example indicates that the shipment is being transported by Preston Trucking. Preston's SCAC code is PRES. The "LS" is the bar code qualifier the "2SAAA " is the unique licence plate number for the entire shipment. Note: The licence plate bar code number should matched the bar code on the packing list and/or the physical shipment. REF*BM* The Bill of Lading number is N1*ST*IBM CORP - PCC*92*988 N3*305 DOCK*3039 Cornwallis Rd The N1 segment indicates that the shipment is being sent to the IBM Corp - PCC. 988 indicates the physical plant code. Building and street address N4*Durham*NC*27709*US City, State, Zip and Country. PER*BD*John Doe The buyer name is John Doe N1*SE*ANY The seller's name is ANY SHIPPER SHIPPER*92* N3*PO BOX 1234 Address of seller N4*ANYTOWN*SC*29606*US Ci S Zi d

23 Global Procurement Ship Notice/Manifest Page 23 of 58 N4*ANYTOWN*SC*29606*US HL*2*1*I*0 LIN*1*BP* *CH*US SN1*1*10*EA PRF*537891*** REF*LS*11S REF*LS*11S REF*LS*11S REF*LS*11S REF*LS*11S REF*LS*11S REF*LS*11S REF*LS*11S REF*LS*11S REF*LS*11S CTT*2 SE*30* City, State, Zip and country. This is the second HL segment and it is a subordinate of the shipment HL. It is at the Item (I) level and it does not have a subordinate. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 10 and "EA" is the unit of measure code for each. The PRF segment is used to identify the purchase order number, of the shipment, in PRF01. Note: It is not necessary in IBM to use PRF02 and PRF03, however, some translators require that PRF04 be used. The REF segment is used at this level to identify the barcoded tracking ID in REF02. In this example the "LS" is the bar code qualifier, the "11S " is the tracking ID. A repeat of the "REF" segment is required for each unique item. Note: The tracking ID should match the bar code on the physical item. There are 2 HL segments used in this transaction There are 30 segments used in this transaction identified as Table 28.

24 Global Procurement Ship Notice/Manifest Page 24 of 58 Shipment resulting from a Shipping Schedule (862) Transaction This table provides an example of an inbound 856 from a supplier that has received an 862 transaction from IBM. EDI Data Description of Data ST*856* The ST segment identifies this as an 856 transaction with an identification number of BSN*00*4321*960531*1100 The BSN segment is mandatory. In this case it indicates that an original(00) 856 transaction, with a shipment identification number (4321) was created at 11:00 am on May 31, DTM*011*960531*1000*ET The DTM is a mandatory segment. The value "011" in the DTM01 indicates that the item was shipped at 11:00am, Eastern Time, on May 31, HL*1**S*1 The HL segment is mandatory. The HL01 indicates the number of the HL, the HL02 does not have a value which means it is not a subordinate. The HL03 value of "S" means that the HL is at the shipment level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. TD5*B*2*MYWY*L*MYWAY TRUCKING**OR REF*LS*2SBQY The TD5 segment is required for tracking purposes within IBM. This example indicates that the shipment is being transported by MYWAY Trucking. MYWAY's SCAC code is MYWY. The "LS" is the bar code qualifier, the "2SBQY " is the unique licence plate number for the entire shipment. Note: The licence plate bar code number should matched the bar code on on the packing list and/or the physical shipment. REF*PK* The Packing list number is REF*BM* The Bill of Lading number is N1*ST*IBM CORP - POK The N1 segment indicates that the shipment is being sent to the IBM Corp - POK. N1*SE**92* The seller's ID number is HL*2*1*I*0 This is the second HL segment and it is a subordinate of the shipment HL. It is at the Item (I) level and it does not have a

25 Global Procurement Ship Notice/Manifest Page 25 of 58 LIN*1*BP* *CH*US*PI* subordinate. The LIN is necessary to indicate the part number, the country of origin and the Purchaser's Item. In this case the Buyer's Part Number "BP" is , the country of origin (CH) is US and the Purchaser's Item is SN1*1*20*EA PRF*254601*** CTT*2 SE*16* Note: The Purchaser's Item is provided to the shipper by IBM in the Shipping Schedule (862) transaction. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 20 and "EA" is the unit of measure code for each. The PRF segment is used to identify the purchase order number, of the shipment, in PRF01. Note: It is not necessary in IBM to use PRF02 and PRF03, however, some translators require that PRF04 be used. There are 2 HL segments used in this transaction There are 16 segments used in this transaction identified as Table 29. Non-Production Order Shipment This table provides an example of a Non-Production inbound 856 from a supplier that has one purchase order. EDI Data Description of Data ST*856* The ST segment identifies this as an 856 transaction with an identification number of BSN*00*654321*960520*1000 DTM*011*960520*1000 HL*1**S*1 The BSN segment is mandatory. In this case it indicates that an original(00) 856 transaction, with a shipment identification number (654321) was created at 10:00 am on May 20, The DTM is a mandatory segment. The value "011" in the DTM01 indicates that the item was shipped at 10:00am on May 20, 1996 The HL segment is mandatory. The HL01 indicates the number of the HL, the HL02 does not have a value which means it is

26 Global Procurement Ship Notice/Manifest Page 26 of 58 TD5*B*2*RDWY*L*ROADWAY TRUCKING**OR REF*LS*2SABA does not have a value which means it is not a subordinate. The HL03 value of "S" means that the HL is at the shipment level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The TD5 segment is required for tracking purposes within IBM. This example indicates that the shipment is being transported by ROADWAY Trucking. ROADWAY's SCAC code is RDWY. The "LS" is the bar code qualifier, the "2SABA " is the unique licence plate number for the entire shipment. Note: The licence plate bar code number should matched the bar code on on the packing list and/or the physical shipment. REF*BM* The Bill of Lading number is N1*ST*IBM CORP - PCC*92*988 N3*305 DOCK*3039 Cornwallis Rd N4*Durham*NC*27709*US PER*BD*John Doe N1*SE*ANY SHIPPER*92* N3*PO BOX 1234 N4*ANYWHERE*NC*29606*US HL*2*1*I*0 SN1*1*20*DZ PRF*N12121*** The N1 segment indicates that the shipment is being sent to the IBM Corp - PCC. 988 indicates the physical plant code. Building and street address City, State, Zip and Country. The buyer name is John Doe The seller's name is ANY SHIPPER Address of seller City, State, Zip and country. This is the second HL segment and it is a subordinate of the shipment HL. It is at the Item (I) level and it does not have a subordinate. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 20 and "DZ" is the unit of measure code for dozen. The PRF segment is used to identify the purchase order number, of the shipment, in PRF01. PID*F****Pencils CTT*2 Note: It is not necessary in IBM to use PRF02 and PRF03, however, some translators require that PRF04 be used. The PID segment is used to provide a description of the item/s shipped and should only be used when an item does not have an IBM part number. The "F" in PID01 indicates that the item description type is "Free Format". The description of the item is in PID05. There are 2 HL segments used in this transaction

27 Global Procurement Ship Notice/Manifest Page 27 of 58 SE*20* transaction There are 20 segments used in this transaction identified as Between IBM Location Examples Table 30. Multiple Case Shipment Example. This table provides an example of an inbound 856 from another IBM location with multiple cases on a shipment/packing list. EDI Data Description of Data ST*856* The ST segment identifies this as an 856 transaction with an identification number of BSN*00*IBM000002*940120*0900 The BSN segment is mandatory. In this example it indicates that an original (00) 856 transaction, with a shipment identification number (IBM000002) was created at 9:00 am on January 20, DTM*011*940120*0900 HL*1**S*1 SN1*1*2*CA TD5*B*2*RDWY*L***OR REF*LS*2SAAA Note: It is recommended that the first three positions of the identification number for IBM shipments be "IBM". The DTM is a mandatory segment. The value "011" in the DTM01 indicates that the item was shipped at 9:00am on January 20, 1994 The HL segment is mandatory. The HL01 indicates the number of the HL, the HL02 does not have a value which means it is not a subordinate. The HL03 value of "S" means that the HL is at the shipment level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2 and "CA" is the unit of measure code for case, therefore 2 cases are in this shipment. The TD5 segment is required for tracking purposes within IBM. This example indicates that the shipment is being transported by ROADWAY. ROADWAY's SCAC code is RDWY. TD507 value of OR indicates that ROADWAY is the original carrier. The "LS" is the bar code qualifier, the "2SAAA " is the unique licence plate number for the entire shipment. Note: The licence plate bar code number should matched the bar code on the

28 Global Procurement Ship Notice/Manifest Page 28 of 58 packing list and/or the physical shipment. REF*BM* The Bill of Lading number is N1*ST*IBM CORP - PCC*92*988 N3*305 DOCK*3039 Cornwallis Rd N4*Research Triangle Park*NC*27709*US N1*SE*IBM CORP*92*980 N3*HIWAY 52 NORTH N4*ROCHESTER*MN*55901*US HL*2*1*T*1 REF*LS*9S The N1 segment indicates that the shipment is being sent to the IBM Corp - PCC. (988 indicates the physical plant code). Building and street address City, State, Zip and Country. The N1 segment indicates that the Selling Party (SE) is the IBM-Corp. (the 980 indicates the physical plant code). Address City, State, Zip and country The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the first (1) HL. The HL03 value of "T" means that the HL is at the tare (case) level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The "LS" is the bar code qualifier, the "9S " is the unique licence plate number for this case. HL*3*2*I*0 LIN*2*BP* *CH*US SN1*2*2700*EA REF*IL* N1*ST**92*988 N1*BF**92*92E HL*4*2*I*0 Note: The licence plate bar code number should matched the bar code on the physical case. The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the second (2) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2700 and "EA" is the unit of measure code for each, therefore 2700 items are in this shipment. the internal order (IL) for this item is The 988 is the "Ship to" from the interplant order. The 92E is the "Invoice From" segmentation code The HL01 indicates the number of the

29 Global Procurement Ship Notice/Manifest Page 29 of 58 LIN*2*BP* *CH*US SN1*2*2700*EA REF*IL* N1*ST**92*988 N1*BF**92*92E HL*5*2*I*0 LIN*2*BP* *CH*US SN1*2*2700*EA REF*IL* N1*ST**92*988 N1*BF**92*92E HL*6*1*T*1 REF*LS*9S HL, the HL02 indicates that this HL is a subordinate of the second (2) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2700 and "EA" is the unit of measure code for each, therefore 2700 items are in this shipment. the internal order (IL) for this item is The 988 is the "Ship to" from the interplant order. The 92E is the "Invoice From" segmentation code The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the second (2) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2700 and "EA" is the unit of measure code for each, therefore 2700 items are in this shipment. the IBM internal order (IL) for this item is The 988 is the "Ship to" from the interplant order. The 92E is the "Invoice From" segmentation code The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the first (1) HL. The HL03 value of "T" means that the HL is at the tare (case) level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The "LS" is the bar code qualifier, the "9S " is the unique li l b f hi

30 Global Procurement Ship Notice/Manifest Page 30 of 58 licence plate number for this case. HL*7*6*I*0 LIN*5*BP* *CH*US SN1*5*100*EA REF*IL* N1*ST**92*988 N1*BF**92*92E HL*8*6*I*0 LIN*6*BP* *CH*US SN1*6*500*EA REF*IL* CTT*8 SE*48* Note: The licence plate bar code number should matched the bar code on the physical case. The HL01 consist indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the sixth (6) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 100 and "EA" is the unit of measure code for each, therefore 100 items are in this shipment. the IBM internal order (IL) for this item is The 988 is the "Ship to" from the interplant order. The 92E is the "Invoice From" segmentation code The HL01 consist indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the sixth (6) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 500 and "EA" is the unit of measure code for each, therefore 500 items are in this shipment. the IBM internal order (IL) for this item is There are 8 HL segments used in this transaction There are 48 segments used in this transaction identified as

31 Global Procurement Ship Notice/Manifest Page 31 of 58 Table 31. Single Case Shipment Example. This table provides an example of an inbound 856 from another IBM location that has only one case associated with the shipment/packing list. EDI Data Description of Data ST*856* The ST segment identifies this as an 856 transaction with an identification number of BSN*00*IBM00001*940125*1000 The BSN segment is mandatory. In this example it indicates that an original (00) 856 transaction, with a shipment identification number (IBM00001) that was created at 10:00 am on January 25, DTM*011*940125*0900 HL*1**S*1 TD5*B*2*RDWY*L***OR REF*LS*2S Note: It is recommended that the first three positions of the identification number for IBM shipments be "IBM". The DTM is a mandatory segment. The value "011" in the DTM01 indicates that the item was shipped at 9:00am on January 25, 1994 The HL segment is mandatory. The HL01 indicates the number of the HL, the HL02 does not have a value which means it is not a subordinate. The HL03 value of "S" means that the HL is at the shipment level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The TD5 segment is required for tracking purposes within IBM. This example indicates that the shipment is being transported by ROADWAY. ROADWAY's SCAC code is RDWY. The "LS" is the bar code qualifier, the "2S " is the unique licence plate number for the entire shipment. Note: The licence plate bar code number should matched the bar code on the packing list and/or the physical shipment. REF*BM* The Bill of Lading number is N1*ST*IBM CORP - RTP*92*988 N3*305 DOCK*3039 Cornwallis Rd N4*Research Triangle Park*NC*27709*US N1*SE*IBM CORP*92*980 N3*HIWAY 52 NORTH The N1 segment indicates that the shipment is being sent to the IBM Corp - RTP. (988 indicates the physical plant code). Building and street address City, State, Zip and Country. The N1 segment indicates that the Selling Party (SE) is the IBM-Corp. (the 980 indicates the physical plant code). Address

32 Global Procurement Ship Notice/Manifest Page 32 of 58 N4*ROCHESTER*MN*55901*US HL*2*1*I*0 LIN*1*BP* *CH*US SN1*1*2700*EA REF*IL* N1*ST**92*988 N1*BF**92*92E HL*3*1*I*0 LIN*2*BP* *CH*US SN1*2*2700*EA REF*IL* N1*ST**92*988 N1*BF**92*92E HL*4*1*I*0 City, State, Zip and country The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the first (1) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2700 and "EA" is the unit of measure code for each, therefore 2700 items are in this shipment. the internal order (IL) for this item is The 988 is the "Ship to" from the interplant order. The 92E is the "Invoice From" segmentation code The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the first (1) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2700 and "EA" is the unit of measure code for each, therefore 2700 items are in this shipment. the internal order (IL) for this item is The 988 is the "Ship to" from the interplant order. The 92E is the "Invoice From" segmentation code The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the first (1) HL. The HL03 value of "I" means that the HL is at the item level and finally, HL04 value of 0 indicates that there are no subordinate HL loop.

33 Global Procurement Ship Notice/Manifest Page 33 of 58 LIN*2*BP* *CH*US SN1*2*2700*EA REF*IL* N1*ST**92*988 N1*BF**92*92E CTT*4 SE*33* The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2700 and "EA" is the unit of measure code for each, therefore 2700 items are in this shipment. the internal order (IL) for this item is The 988 is the "Ship to" from the interplant order. The 92E is the "Invoice From" segmentation code There are 4 HL segments used in this transaction There are 33 segments used in this transaction identified as Table 32. Multiple Case Shipment with APC 3,4 or 5. This table provides an example of an inbound 856 from another IBM location that has multiple cases associated with the shipment/packing list and the APC is 3, 4 or 5. EDI Data Description of Data ST*856* The ST segment identifies this as an 856 transaction with an identification number of BSN*00*IBM00002*940126*0800 The BSN segment is mandatory. In this example it indicates that an original(00) 856 transaction, with a shipment identification number (IBM00002) was created at 8:00 am on January 26, DTM*011*940126*0800 HL*1**S*1 SN1*1*2*CA Note: It is recommended that the first three positions of the identification number for IBM shipments be "IBM". The DTM is a mandatory segment. The value "011" in the DTM01 indicates that the item was shipped at 8:00am on January 26, 1994 The HL segment is mandatory. The HL01 indicates the number of the HL, the HL02 does not have a value which means it is not a subordinate. The HL03 value of "S" means that the HL is at the shipment level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The SN1 segment is necessary to indicate the number of units shipped. The SN102 indicates a quantity of 2 and "CA" is the

34 Global Procurement Ship Notice/Manifest Page 34 of 58 TD5*B*2*YFSY*L***OR REF*LS*2S q y unit of measure code for case, therefore 2 cases are in this shipment. The TD5 segment is required for tracking purposes within IBM. This example indicates that the shipment is being transported by Yellow Freight. Yellow Freight's SCAC code is YFSY. The "LS" is the bar code qualifier, the "2S " is the unique licence plate number for the entire shipment. Note: The licence plate bar code number should matched the bar code on the packing list and/or the physical shipment. REF*BM* The Bill of Lading number is N1*ST*IBM CORP - RTP*92*988 N3*305 DOCK*3039 Cornwallis Rd N4*Research Triangle Park*NC*27709*US N1*SE*IBM CORP*92*980 N3*HIWAY 52 NORTH N4*ROCHESTER*MN*55901*US HL*2*1*T*1 REF*LS*9S The N1 segment indicates that the shipment is being sent to the IBM Corp - RTP. (988 indicates the physical plant code). Building and street address City, State, Zip and Country. The N1 segment indicates that the Selling Party (SE) is the IBM-Corp. (the 980 indicates the physical plant code). Address City, State, Zip and country The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the first (1) HL. The HL03 value of "T" means that the HL is at the Tare (case) level and finally, HL04 value of 1 indicates that there is at least one subordinate HL loop. The "LS" is the bar code qualifier, the "9S " is the unique licence plate number for the entire case. HL*3*2*I*0 LIN*2*BP* *CH*US Note: The licence plate bar code number should matched the bar code on the physical case. The HL01 indicates the number of the HL, the HL02 indicates that this HL is a subordinate of the first (1) HL. The HL03 value of "I" means that the HL is at the Item level and finally, HL04 value of "0" indicates that there is no subordinate HL loop. The LIN is necessary to indicate the part number and the country of origin. In this case the Buyer's Part Number "BP" is and the country of origin (CH) is US