EDIFACT Implementation Guidelines For Shanghai GM

Transcription

1 1500 Shen Jiang Road, Jin Qiao, Pu Dong, Shanghai EDIFACT Implementation Guidelines For Shanghai GM DELJIT-PUS EDIFACT DELJIT D.97A Revision No. 1.3 Revision Date: Aug 28,2009 Creation Date: Dec 26, 2005

2 Revision History Version Date Revision Summary of Major Changes Made Number Updated Author 1.0 Dec.26, 2005 Shen Xuyan Initial document created. 1.1 Feb.1, 2007 Tang Min Add NAD SF segment. 1.2 Jun.6, 2007 Chen Chen Cancel NAD SF segment. 1.3 Aug.28, 2009 Guo Chao Update 0030 DTM segment. Printed: August 28, 2009 Page 2 SGM EDI Document

3 Menu 1 Initial Electronic Setup Purpose of this guideline SGM EDIFACT Requirements Supplier receives Supplier sends EDIFACT Standards Additional Information DELJIT-PUS Delivery Schedule Message Introduction Message Definition Principles & References Message Description Segment Table Branching Diagram Message Standard Description Message Structure Segments Description Example Printed: August 28, 2009 Page 3 SGM EDI Document

4 1 Initial Electronic Setup 1.1 Purpose of this guideline The purpose of this guideline is to communicate our requirements and expectations to our suppliers. This drive for excellence, in conjunction with a close working relationship, will enable us both to continuously improve and become leaders in a world class supply base. 1.2 SGM EDIFACT Requirements In order to send our requirements or receive ASNs, the supplier must be setup electronically. All suppliers are required to be EDIFACT (Electronic Data Interchange for Administration Commerce and Transport Requirements) compatible (receiving and sending) with SGM. Suppliers must be capable of receiving DELFOR (Delivery Forecast Schedule), DELJIT-SH (Delivery Just in Time), DELJIT-PUS (Pick Up Sheet) and sending DESADV (Despatch Advice). SGM suppliers will be required to conform to SGM s EDIFACT standards for DELFOR,DELJIT-SH, DELJIT-PUS and DESADV transactions. It is critical that suppliers or supplier s software representative follows the SGM EDIFACT Implementation Guideline to ensure correct setup Supplier receives 1. The DELFOR is a standard planning schedule with 20 weeks volume forecast, message from SGM to Suppliers, which contains long-term material planning requirements. 2. The DELJIT-SH (Ship Schedule) is a cum-based shipping schedule with 2 slide 1 schedule type, message from SGM to Suppliers, week2 is a new firm shipping schedule, and week1 includes the shipping schedule firmed in the previous week and supplier under-shipped information. Schedule Agreement Number by part level will be indicated in each DELJIT-SH file, supplier should send EDI ASN (DESADV) to SGM with this key Schedule Agreement Number. The DELJIT-PUS is a shipping schedule with Pick-Up-Sheet schedule type, message from SGM to Suppliers, which contains details on shipping/delivery requirements. SGM ordering strategy is to send DELJIT-PUS to oversea suppliers for week2 frozen order. SGM Purchasing Order Number will be indicated in each DELJIT-PUS file, supplier should send EDI ASN (DESADV) to SGM with SGM Purchasing Order Number Supplier sends 1. The DESADV file format (ASN) received from the supplier will contain a shipping schedule based on the requirements form the DELJIT file. Advance shipment notification data must be sent for each shipment made for SGM, which is by case level if wooden crates will be packed into one container. The data consists of two types of information. The first type is the shipment detail and specifies a unique shipment number, the case number, the supplier code, and the destination codes, the second type is the part detail and consists of part, quantity shipped and cumulative year to date shipped. 2. For non-consolidation oversea suppliers, Suppliers are required to send DESADV (EDI ASNs) to SGM at the time material shipments occur. For all consolidation oversea suppliers, supplier's ASN will be compiled by 3PL after material consolidation. 3. One key point is supplier should send ASNs and indicate SGM Schedule Agreement Number or "Purchase Order Number" in the segment "RFF" of DESADV file EDIFACT Standards The transactions follow GM standards closely. It should be noted that the segments lengths follow EDIFACT standards unless other wised stated. Printed: August 28, 2009 Page 4 SGM EDI Document

5 1.3 Additional Information SGM Communication code: QGM SGM Material Issuer ID: DELJIT-PUS Delivery Schedule Message 2.1 Introduction Message Definition This document provides the definition of an Advanced Shipping Notification (ASN) or Despatch Advice Message, based on the EDIFACT DESADV D97.A, to be used in Electronic Data Interchange (EDI) between a Trading Partner and SGM. This documentation is fully comprehensive and allows the implementation of the EDIFACT DESADV without the necessity for any additional standard related documentation. The ASN/Despatch Advice message is a message from a SGM Supplier to the relevant SGM application. It gives information concerning material despatched to a SGM location as instructed by a previously received Delivery Instruction or Shipping Schedule message and in line with the conditions set out in the contract or order Principles & References The Pick Up Sheet Message is part of the Lean Materials strategy and is intended to: Specify daily material requirements and packaging conditions to the Supplier; Specify to both the Supplier and the Carrier a specific pick up window; Specify to the Carrier specific delivery windows for the delivery of the material to the receiving plant in line with the specified routing. The content of this message is based on: The message structure as defined by EDIFACT for the UNSM Delivery Just in Time message DELJIT as published in the UN/EDIFACT D.97A Directory. The agreement between the Trading Partners on the data elements to be used, their unique definition, their representation and their values (coded or clear form) as identified in this document. SGM has opted for the EDIFACT D.97A Directory and consistently uses this directory for all its EDIFACT messages. 2.2 Message Description Following pages contain a full description of the EDIFACT DELJIT D.97A message as implemented by SGM. All segments are included regardless whether used or not used in the interchange with SGM. The official EDIFACT segment description is complemented with remarks pertaining to the specific requirements for an interchange with SGM. Those remarks contain specific code values used, additional information on the values shown in a specific field, etc Segment Table The following table shows the segments defined for the EDIFACT UNSM DELJIT D.97A Delivery Just in Time message. Shaded areas identify the segments that are not used in the subset of DELJIT used by SGM. This table, which should be read in conjunction with the branching diagram indicates the maximum number of occurrences for each segment. Printed: August 28, 2009 Page 5 SGM EDI Document

6 POS. SEG. NAME ST REPEATS 0010 UNH Message header M BGM Beginning of message M DTM Date/time/period M FTX Free text C Segment group 1 C RFF Reference M DTM Date/time/period C Segment group 2 C NAD Name and address M LOC Place/location identification C FTX Free text C Segment group 3 C CTA Contact information M COM Communication contact C Segment group 4 M SEQ Sequence details M DTM Date/time/period C GIR Related identification numbers C LOC Place/location identification C Segment group 5 C PAC Package identification M Segment group 6 C PCI Package identification M GIN Goods identity number C Segment group 7 C LIN Line item M PIA Additional product id C IMD Item description C ALI Additional information C GIR Related identification numbers C TDT Details of transport C FTX Free text C PAC Package identification C DTM Date/time/period C Segment group 8 C RFF Reference M DTM Date/time/period C Segment group 9 C LOC Place/location identification M Segment group 10 C CTA Contact information M COM Communication contact C Segment group 11 C QTY Quantity M SCC Scheduling conditions C DTM Date/time/period C Segment group 12 C RFF Reference M DTM Date/time/period C UNT Message trailer M 1 Printed: August 28, 2009 Page 6 SGM EDI Document

7 2.2.2 Branching Diagram The branching diagram shows the structure of the message. It is a combination of various segments that are organized in a certain hierarchical order. A segment is a pre-defined set of functionally related values (e.g., segment NAD groups all values that relate to a Party: name - address - etc.) Each segment within the branching diagram is broken down into one or multiple data elements. Within a segment, only those data elements that contain data must appear. Shaded areas identify the segments that are not used in the subset of DELJIT used by SGM. Level 1 0 UNH See M 1 2 SG01 SG02 SG04 C 10 C 20 M BGM DTM FTX RFF NAD SEQ M 1 M 10 C 5 M 1 M 1 M 1 SG03 SG05 See C 5 C DTM LOC FTX CTA DTM GIR LOC PAC C 1 C 10 C 5 M 1 C 5 C 99 C 5 M 1 SG06 C COM PCI C 5 M 1 4 GIN C 10 Printed: August 28, 2009 Page 7 SGM EDI Document

8 Level 2 0 See See See SG07 2 C LIN M 1 SG08 SG09 SG11 C 5 C 5 C PIA IMD ALI GIR TDT FTX PAC DTM RFF LOC QTY C 10 C 10 C 5 C 5 C 5 C 5 C 5 C 5 M 1 M 1 M 1 SG10 See C DTM CTA SCC DTM C 1 M 1 C 1 C 2 5 COM C 5 Printed: August 28, 2009 Page 8 SGM EDI Document

9 Level 3 0 See UNT 2 M See SG12 NAD Name of the segment 2 C 5 M 1 Number of occurrences 4 RFF Ø Status (M = Mandatory - C = Conditional) M 1 5 DTM C 1 Printed: August 28, 2009 Page 9 SGM EDI Document

10 2.2.3 Message Standard Description This section provides the description of the UN Standard Message DELJIT as defined in the 97A Directory. Only the segments printed in bold are used in the subset defined by SGM and will be further explained in section Shaded areas identify the segments that are not used in the subset of DELJIT used by SGM. 1. Header Section Information to be provided in the Header section: 0010 UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Delivery just in time message is DELJIT BGM, Beginning of message A segment for unique identification of the document name and its number DTM, Date/time/period A segment specifying the date and, when relevant, the time/period for delivery of that sequence, relating to the whole message. The DTM segment must be specified at least once to identify the Delivery Just In Time document date FTX, Free text Segment giving additional information relevant to the entire message Segment group 1: RFF-DTM A group of segments giving references relevant to the whole message, e.g. contract number RFF, Reference A segment for referencing documents to the whole message, e.g. contract, import/export license DTM, Date/time/period Date/time/period as applied the referred document Segment group 2: NAD-LOC-FTX-SG3 A group of segments identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message NAD, Name and address A segment for identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message LOC, Place/location identification A segment indicating more details regarding specific place/locations related to the party specified in the NAD segment, e.g. internal site/building number FTX, Free text A segment with free text in coded or clear form, to give further clarification, when required, about the party Segment group 3: CTA-COM Printed: August 28, 2009 Page 10 SGM EDI Document

11 A group of segments to identify person, function, department and appropriate numbers to whom communication should be directed CTA, Contact information A segment to identify person, function, department to whom communication should be directed COM, Communication contact Identify communication types and numbers for person, function, department identified in CTA. 2. Detail Section Information to be provided in the Detail section: 0150 Segment group 4: SEQ-DTM-GIR-LOC-SG5-SG7 A group of segments providing details related to the delivery sequence. All other segments in this Segment Group 4 following the SEQ segment refer to that sequence SEQ, Sequence details A segment providing specific details related to the delivery sequence requested by the buyer or recipient of the product DTM, Date/time/period A segment specifying the date, and when relevant, the time/period for delivery of that sequence GIR, Related identification numbers A segment to be able to give related identification numbers LOC, Place/location identification A segment identifying a general location to which products, as specified in the Segment Group 7, should be delivered Segment group 5: PAC-SG6 Segment group to support KANBAN operation where customers must notify a supplier packaging labels and conditions PAC, Package To describe the number and type of packages/physical units Segment group 6: PCI-GIN A segment group giving packaging identification and good identity number related to the segment PAC PCI, Package identification To specify markings and labels on individual packages or physical units GIN, Goods identity number To give specific identification numbers, either as single numbers or ranges Segment group 7: LIN-PIA-IMD-ALI-GIR-TDT-FTX-PAC-DTM-SG8-SG9-SG11 A group of segments providing details of the individual line items to be delivered LIN, Line item Printed: August 28, 2009 Page 11 SGM EDI Document

12 A segment identifying the details of the product/service being delivered e.g. product identification. All other segments in the detail section following the LIN segment refer to the line item PIA, Additional product id A segment providing additional product identification IMD, Item description A segment for describing the product to be delivered ALI, Additional information A segment indicating that the line item is subject to special conditions owing to origin, customs preference, or commercial factors GIR, Related identification numbers A segment providing sets of related identification numbers for the line item TDT, Details of transport A segment specifying the carriage, and the mode and means of transport of the goods to be delivered FTX, Free text A segment with free text in coded or clear form, to give further clarification, when required, to the line group PAC, Package Segment giving information related to the instruction for package type which is valid for the specified deliveries of the line item DTM, Date/time/period A segment specifying the date, and when relevant, the time/period for delivery of line item Segment group 8: RFF-DTM A group of segments giving references and where necessary, their dates, relating to the line item RFF, Reference A segment for referencing document and other numbers related to the line item as specified in the LIN segment DTM, Date/time/period Date/time/period as applied to the referred document Segment group 9: LOC-SG10 A group of segments providing delivery location information and where relevant contacts LOC, Place/location identification A segment indicating more details regarding specific locations related to the line item Segment group 10: CTA-COM Printed: August 28, 2009 Page 12 SGM EDI Document

13 A group of segments to identify person, function, department and appropriate numbers to whom communication should be directed CTA, Contact information A segment to identify person, function, department to whom communication should be directed COM, Communication contact Identify communication types and numbers for person, function, department identified in CTA Segment group 11: QTY-SCC-DTM-SG12 A group of segments specifying quantity related information for actual delivery QTY, Quantity A segment to specify pertinent quantities relating to the line item SCC, Scheduling conditions A segment indicating the scheduling conditions DTM, Date/time/period A segment indicating the date/time/period details relating to the quantity and schedule details in the line item Segment group 12: RFF-DTM A group of segments giving references relating to the quantities RFF, Reference A segment for referencing the specific product release information e.g. appointment DTM, Date/time/period Date/time/period as applied to the referred document UNT, Message trailer A service segment ending a message, giving the total number of segments in the message and the control reference number of the message Message Structure The message structure illustrates how the segments will be repeated in the Pick Up Sheet message to accommodate the requirements identified by General Motors. Printed: August 28, 2009 Page 13 SGM EDI Document

14 0010.UNH Start of Delivery Schedule Message 0020.BGM Message identification DTM Message issue date/time DTM Pick up window at supplier - star DTM Pick up window at supplier - end DTM Delivery window at destination - start DTM Delivery window at destination - end NAD Supplier identification NAD Schedule issuer (buyer) NAD Ship to identification (consignee) SEQ Start of detail section [SEQ].PAC Package details for part number [SEQ].LIN Part number [SEQ.LIN].LOC Dock identification for part number [SEQ.LIN].QTY [SEQ.LIN].QTY [SEQ.LIN].QTY Quantity to be delivered date for part number 1 Quantity per pack for part number 1 Chargeable weight for part number [SEQ.LIN].SCC schedule information SEQ Start of detail section 2... Part number 2 details SEQ Start of detail section 3... Part number 3 details 0500.UNT End of message Printed: August 28, 2009 Page 14 SGM EDI Document

15 2.2.5 Segments Description Following service segments are as defined by UN/EDIFACT and presented under ISO The UNB, UNH, UNT and UNZ segments are the envelope of any message, enclosing all the data that is being transmitted. The UNB (Interchange header) and UNZ (Interchange trailer) segments mark respectively the beginning and the end of an interchange thereby providing a unique interchange control reference. MESSAGE 1 UNB UNH UNT EXAMPLE OF AN INTERCHANGE STRUCTURE MESSAGE 2... MESSAGE N UNH UNT UNH UNT UNZ Within the interchange the UNH (message header) and UNT (Message trailer) segments uniquely begin and end the various messages contained in an interchange. This part includes only the segments defined in the standard and used in the subset exchanged between GM and its Trading Partners. The segments are described in the same sequence as they appear in the message. Printed: August 28, 2009 Page 15 SGM EDI Document

16 Example Referenc e Segment/ Composit e Element Description Code or Value Comments Example: UNB+UNOA: GMDATEDIPROD:ZZ :1135+MPUS SGMDELJIT A B C D E F G H I UNB Interchange header A S Syntax identifier "UNOA" B 0002 Syntax version number "2" Indication of the syntax version used for this message. C S Sender identification " " Communication Code/Mailbox number of the party originating the message. D S Recipient identification Identification code E 0007 qualifier F S Date of preparation G 0019 Time of preparation H 0020 I 0026 INTERCHANGE CONTROL REFERENCE APPLICATION REFERENCE Example: UNH+1+DELJIT:D:97A:UN+PUS A B C D E F UNH Message header "GMDATEDIPR OD" "ZZ" Date of preparation Time of preparation MPUS " SGMDELJIT" A 0062 Message Reference Number B S Message type "DELJIT" C 0052 Message version number "D" D 0054 Message release number "97A" E 0051 Controlling agency "UN" F 0068 Communication Code/Mailbox number of the party receiving the message. Qualifier of the party receiving the message YYMMDD format HHMM format The ICR number is UNIQUE within an inventory year. Consists of 4 digits for the message identification(mpus = Pick Up Sheet) and 3 digits for the Julian day. eg.jan.1 = 001,Dec. 31 = 365/366 and plus 4 digits for the time of issuance Unique message reference assigned by the sender to the message Common access reference "PUS" PUS = Pick-up Sheet Example: BGM+242::PUS+07S A B C D BGM Begin of message Document/message A C name, coded 242 "242" = Delivery just-in-time B 1000 Document/message name PUS PUS = Pick-up Sheet C C Document/message number PUS number, a unique reference number assigned by the Sender to identify the Pick Up Sheet. Supplier should indicate SGM PUS number in the segment "RFF" in segment Printed: August 28, 2009 Page 16 SGM EDI Document

17 group 16 of DESADV file. D 1225 Message function code. 9 9 = Original Example: DTM+137: :203 A B C DTM(1) Document generation date A C Date/time/period qualifier 137 B 2380 Date/time/period Date/time/period format C 2379 qualifier 203 Example: DTM+234: :203 A B C DTM(2) Pick up window at supplier site/start A C Date/time/period qualifier 234 B 2380 Date/time/period Date/time/period format C 2379 qualifier 203 Example: DTM+235: :203 A B C DTM(3) Pick up window at supplier site/end A C Date/time/period qualifier 137 B 2380 Date/time/period Date/time/period format C 2379 qualifier 203 Example: DTM+117: :203 A B C DTM(4) Delivery window at destination plant/start A C Date/time/period qualifier 117 B 2380 Date/time/period Date/time/period format C 2379 qualifier 203 Example: DTM+128: :203 A B C DTM(5) Delivery window at destination plant/end A C Date/time/period qualifier 128 B 2380 Date/time/period Date/time/period format C 2379 qualifier means this date is the document generation date Date/time when a message is issued. 203 means the date s format is CCYYMMDDHHMM 234 means Collection date/time earliest Start date/time of the pick up window at the supplier site. 203 means the date s format is CCYYMMDDHHMM 235 means Collection date/time latest End date/time of the pick up window at the supplier site. 203 means the date s format is CCYYMMDDHHMM 117 means Delivery date/time first at Destination Start date/time of the delivery window at destination plant. 203 means the date s format is CCYYMMDDHHMM 128 means Delivery date/time last at Destination End date/time of the delivery window at destination plant. 203 means the date s format is CCYYMMDDHHMM Printed: August 28, 2009 Page 17 SGM EDI Document

18 Example: NAD+SU ::16++SUPPLIER+STREET+CITY+ZIPCODE+DE A B C D E F H J NAD(1) Name and Address A 3035 Party qualifier SU SU means the party is the supplier B C Party id. Identification C 3055 Code list responsible agency, coded means the party id is DUN & Bradstreet (DUNS). D C Name of the party Name of the party E C Street and number/p.o. box Street name of the party F 3164 City name City name of the party G 3229 Country sub-entity identification National State code H 3251 Postcode identification Postal or ZIP code J 3207 Country, coded Country code Example: NAD+MI+72872::92 A B C NAD(2) Name and Address A 3035 Party qualifier "MI" B C Party id. Identification Code list responsible C 3055 agency, coded "92" MI means planning schedule/material release issuer (buyer). 92 means the party id is assigned by buyer or buyer s agent. Example: NAD+ST+72872::92++OPEL POLAND A B C D NAD(3) Name and Address A 3035 Ship To ST ST means Ship To location (consignee) B C Goods shipping to The DUNS of the supplier Code list responsible 92 means the party id is assigned C 3055 agency, coded "92" by buyer or buyer s agent. D 3036 Name of the party Name of the Ship to identification Example: SEQ+6 A SEQ Sequence Details A 1245 Status indicator, coded "6" 6 = Agreement. Example: PAC+3++KLT64280 A B PAC Package A 7224 Number of packages B C Type of packages identification Number of packages, as identified in tag 7065 below, used for the delivery of the quantity, specified in the following QTY segment, of the article defined in the following LIN segment Identification of the type of package to be used for the delivery of the article defined in the following LIN segment. Example: LIN :IN A B Printed: August 28, 2009 Page 18 SGM EDI Document

19 LIN Line Item A C Item number Material number IN means the item number is B 7143 Item number type, coded IN buyer s item number. Example: LOC+11+A1A22 A B LOC Dock code A 3227 Place/location qualifier "11" B C Place/location identification 11 means this segment identifying place/port of discharge Code identifying the receiving dock at the plant where the goods will be delivered. Example: QTY+1:3000 A B QTY(1) Quantity to be delivered A C Quantity qualifier. "1" 1 = Discrete Quantity B 6060 Quantity Actual quantity of the part number defined in the preceding LIN that must be delivered Example: QTY+52:1000 A B QTY(2) Quantity in package A C Quantity qualifier. "52" 52 = Quantity per pack B 6060 Quantity Actual quantity of the part number defined in the preceding LIN that is contained in the package identified in the preceding PAC Example: QTY+101:500 A B QTY(3) Chargeable gross weight A C Quantity qualifier "101" 101 = Chargeable gross weight B 6060 Quantity Actual gross weight of the total quantity to be delivered and the packaging identified in the preceding PAC Example: SCC+1 A SCC A 4017 Example: UNT+99+1 A B UNT A 0074 B 0062 Scheduling Conditions Delivery plan commitment level, coded Message Trailer Number of segments in the message MESSAGE REFERENCE NUMBER With the delivery point driven method this segment group provides the schedule for the identified delivery point and product. Control count of the number of segments in the message, including UNH and UNT. Number must be identical to UNH - tag 0062 Printed: August 28, 2009 Page 19 SGM EDI Document

20 Example: UNZ+1+MPUS A B UNZ Interchange Trailer A 0036 INTERCHANGE CONTROL COUNT INTERCHANGE CONTROL B 0020 REFERENCE Number of messages in an interchange. Value must be the same as Interchange Control Reference in UNB. Printed: August 28, 2009 Page 20 SGM EDI Document

21 2.2.6 Example Following example is only illustrative and does not necessarily reflect an existing situation. It MAY NEVER be used as a basis for programming or implementing this message. UNB+UNOA: MBXNOSUPPLIER:ZZ :0735+MPUS SGMDELJIT UNH+1+DELJIT:D:97A:UN+PUS BGM+242::PUS+07S MAIS Pick Up Sheet identification DTM+137: :203 Document issue date/time DTM+234: :203 Pick up window at supplier - start DTM+235: :203 Pick up window at supplier - end DTM+117: :203 Delivery window at destination - start DTM+128: :203 Delivery window at destination - end NAD+SU ::16++DELPHI PACKARD+COVENTRY Supplier ROWLEY GREEK+SILVERSTONE DR US NAD+MI+72872::92 Buyer NAD+ST+72872::92++OPEL POLAND Consignee SEQ+6 Detail trigger segment 1 PAC+3++ KLT64280 Packing details part number 1 LIN :IN Part number 1 LOC+11+RDC Delivery dock number for part 1 QTY+1:3000 Quantity to be delivered for part 1 QTY+52:1000 Quantity per pack for part 1 QTY+101:500 Chargeable weight SCC+1 SEQ+6 Detail trigger segment 2... Details for part 2 SEQ+6 Detail trigger segment n... Details for part n UNT+47+1 UNZ+1+MPUS Printed: August 28, 2009 Page 21 SGM EDI Document

22 For ease of reading the message has been shown with each segment type on a separate line, which will not be the case when the message is normally transmitted. Next example is how the same message will look when transmitted. UNB+UNOA: MBXNOSUPPLIER:ZZ :0735+MPUS SGMDELJIT'UNH+1+DE LJIT:D:97A:UN+PUS'BGM+242::PUS+07S 'DTM+137: :203'DTM+234: : 203'DTM+117: :203'NAD+SU ::16++DELPHI PACKARD+COVENTRY Supplier ROWLEY GREEK+SILVERSTONE DR US'NAD+MI+72872::92'NAD+ST+72872::92++OPEL POLAND'SEQ+6'PAC+3++KLT64280'LIN :IN'LOC+11+RDC'QTY+1:3000'QTY+52:1000'QTY+10 1:500'SCC+1 SEQ+6'...SEQ+6'... UNT+47+1'UNZ+1+MPUS ' Printed: August 28, 2009 Page 22 SGM EDI Document