edifact implementation guidelines for shanghai gm … edi implementation guidelines...edifact...

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

1500 Shen Jiang Road, Jin Qiao, Pu Dong, Shanghai

Printed: August 28, 2009 SGM EDI Document

SGM EDIFACT Implementation Guide

Revision History

Version Number

Date Updated

Revision Author

Summary of Major Changes Made

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.



Menu

1 Initial Electronic Setup ............................................................ 4

1.1 Purpose of this guideline ............................................................. 4

1.2 SGM EDIFACT Requirements....................................................... 4

1.2.1 Supplier receives ................................................................................... 4

1.2.2 Supplier sends ....................................................................................... 4

1.2.3 EDIFACT Standards .............................................................................. 4

1.3 Additional Information .............................................................. 5

2 DELJIT-PUS Delivery Schedule Message............................... 5

2.1 Introduction ............................................................................... 5

2.1.1 Message Definition ................................................................................ 5

2.1.2 Principles & References......................................................................... 5

2.2 Message Description................................................................. 5

2.2.1 Segment Table....................................................................................... 5

2.2.2 Branching Diagram ................................................................................ 7

2.2.3 Message Standard Description............................................................ 10

2.2.4 Message Structure............................................................................... 13

2.2.5 Segments Description.......................................................................... 15

2.2.6 Example ............................................................................................... 21



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.

1.2.1 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”.

1.2.2 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.

1.2.3 EDIFACT Standards

The transactions follow GM standards closely. It should be noted that the segments lengths follow EDIFACT standards unless other wised stated.



1.3 Additional Information

SGM Communication code: QGM SGM Material Issuer ID: 654651652

2 DELJIT-PUS Delivery Schedule Message

2.1 Introduction

2.1.1 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.

2.1.2 Principles & References

The Pick Up Sheet Message is part of the Lean Materials strategy and is intended to: l Specify daily material requirements and packaging conditions to the Supplier; l Specify to both the Supplier and the Carrier a specific pick up window; l 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: l 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. l 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.

2.2.1 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.



POS. SEG. NAME ST REPEATS

0010 UNH Message header M 1 0020 BGM Beginning of message M 1 0030 DTM Date/time/period M 10 0040 FTX Free text C 5

0050 Segment group 1 C 10

0060 RFF Reference M 1 0070 DTM Date/time/period C 1

0080 Segment group 2 C 20 0090 NAD Name and address M 1

0100 LOC Place/location identification C 10 0110 FTX Free text C 5

0120 Segment group 3 C 5 0130 CTA Contact information M 1 0140 COM Communication contact C 5

0150 Segment group 4 M 9999 0160 SEQ Sequence details M 1 0170 DTM Date/time/period C 5 0180 GIR Related identification numbers C 99 0190 LOC Place/location identification C 5

0200 Segment group 5 C 5 0210 PAC Package identification M 1

0220 Segment group 6 C 999 0230 PCI Package identification M 1 0240 GIN Goods identity number C 10

0250 Segment group 7 C 9999 0260 LIN Line item M 1 0270 PIA Additional product id C 10 0280 IMD Item description C 10 0290 ALI Additional information C 5

0300 GIR Related identification numbers C 5 0310 TDT Details of transport C 5 0320 FTX Free text C 5 0330 PAC Package identification C 5 0340 DTM Date/time/period C 5

0350 Segment group 8 C 5

0360 RFF Reference M 1 0370 DTM Date/time/period C 1

0380 Segment group 9 C 5 0390 LOC Place/location identification M 1

0400 Segment group 10 C 5 0410 CTA Contact information M 1 0420 COM Communication contact C 5

0430 Segment group 11 C 100 0440 QTY Quantity M 1

0450 SCC Scheduling conditions C 1 0460 DTM Date/time/period C 2

0470 Segment group 12 C 5 0480 RFF Reference M 1 0490 DTM Date/time/period C 1

0500 UNT Message trailer M 1



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 9999

1 BGM DTM FTX RFF NAD SEQ

M 1 M 10 C 5 M 1 M 1 M 1

SG03 SG05 See

C 5 C 5 2 2 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 999 3 COM PCI

C 5 M 1

4 GIN C 10



Level 2

0 See See 2 3

1

See SG07

2 C 9999 2 LIN

M 1

SG08 SG09 SG11

C 5 C 5 C 100 3 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 5 3 4 DTM CTA SCC DTM

C 1 M 1 C 1 C 2

5 COM

C 5



Level 3

0 See UNT

2 M 1

1 2 3

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



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 2.2.5. 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. 0020 BGM, Beginning of message A segment for unique identification of the document name and its number. 0030 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. 0040 FTX, Free text Segment giving additional information relevant to the entire message. 0050 Segment group 1: RFF-DTM A group of segments giving references relevant to the whole message, e.g. contract number. 0060 RFF, Reference A segment for referencing documents to the whole message, e.g. contract, import/export license. 0070 DTM, Date/time/period Date/time/period as applied the referred document. 0080 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. 0090 NAD, Name and address A segment for identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message. 0100 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. 0110 FTX, Free text A segment with free text in coded or clear form, to give further clarification, when required, about the party. 0120 Segment group 3: CTA-COM



A group of segments to identify person, function, department and appropriate numbers to whom communication should be directed. 0130 CTA, Contact information A segment to identify person, function, department to whom communication should be directed. 0140 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. 0160 SEQ, Sequence details A segment providing specific details related to the delivery sequence requested by the buyer or recipient of the product. 0170 DTM, Date/time/period A segment specifying the date, and when relevant, the time/period for delivery of that sequence. 0180 GIR, Related identification numbers A segment to be able to give related identification numbers. 0190 LOC, Place/location identification A segment identifying a general location to which products, as specified in the Segment Group 7, should be delivered. 0200 Segment group 5: PAC-SG6 Segment group to support KANBAN operation where customers must notify a supplier packaging labels and conditions.

0210 PAC, Package To describe the number and type of packages/physical units. 0220 Segment group 6: PCI-GIN A segment group giving packaging identification and good identity number related to the segment PAC. 0230 PCI, Package identification To specify markings and labels on individual packages or physical units. 0240 GIN, Goods identity number To give specific identification numbers, either as single numbers or ranges. 0250 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. 0260 LIN, Line item



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. 0270 PIA, Additional product id A segment providing additional product identification. 0280 IMD, Item description A segment for describing the product to be delivered. 0290 ALI, Additional information A segment indicating that the line item is subject to special conditions owing to origin, customs preference, or commercial factors. 0300 GIR, Related identification numbers A segment providing sets of related identification numbers for the line item. 0310 TDT, Details of transport A segment specifying the carriage, and the mode and means of transport of the goods to be delivered. 0320 FTX, Free text A segment with free text in coded or clear form, to give further clarification, when required, to the line group. 0330 PAC, Package Segment giving information related to the instruction for package type which is valid for the specified deliveries of the line item.

0340 DTM, Date/time/period A segment specifying the date, and when relevant, the time/period for delivery of line item.

0350 Segment group 8: RFF-DTM A group of segments giving references and where necessary, their dates, relating to the line item.

0360 RFF, Reference A segment for referencing document and other numbers related to the line item as specified in the LIN segment.

0370 DTM, Date/time/period Date/time/period as applied to the referred document.

0380 Segment group 9: LOC-SG10 A group of segments providing delivery location information and where relevant contacts.

0390 LOC, Place/location identification A segment indicating more details regarding specific locations related to the line item.

0400 Segment group 10: CTA-COM



A group of segments to identify person, function, department and appropriate numbers to whom communication should be directed.

0410 CTA, Contact information A segment to identify person, function, department to whom communication should be directed.

0420 COM, Communication contact Identify communication types and numbers for person, function, department identified in CTA.

0430 Segment group 11: QTY-SCC-DTM-SG12 A group of segments specifying quantity related information for actual delivery.

0440 QTY, Quantity A segment to specify pertinent quantities relating to the line item.

0450 SCC, Scheduling conditions A segment indicating the scheduling conditions.

0460 DTM, Date/time/period A segment indicating the date/time/period details relating to the quantity and schedule details in the line item.

0470 Segment group 12: RFF-DTM A group of segments giving references relating to the quantities.

0480 RFF, Reference A segment for referencing the specific product release information e.g. appointment.

0490 DTM, Date/time/period Date/time/period as applied to the referred document.

0500 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.

2.2.4 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.



0010.UNH Start of Delivery Schedule Message

0020.BGM Message identification

0030-1.DTM Message issue date/time

0030-2.DTM Pick up window at supplier - star

0030-3.DTM Pick up window at supplier - end

0030-4.DTM Delivery window at destination - start 0030-5.DTM Delivery window at destination - end

0090-1.NAD Supplier identification

0090-2.NAD Schedule issuer (buyer)

0090-3.NAD Ship to identification (consignee)

0160-1.SEQ Start of detail section 1

0210.[SEQ].PAC Package details for part number 1

0260.[SEQ].LIN Part number 1

0390-1.[SEQ.LIN].LOC Dock identification for part number 1

0440-1.[SEQ.LIN].QTY 0440-2.[SEQ.LIN].QTY

0440-3.[SEQ.LIN].QTY

Quantity to be delivered date for part number 1 Quantity per pack for part number 1 Chargeable weight for part number 1

0450.[SEQ.LIN].SCC schedule information


... Part number 2 details


... Part number 3 details

0500.UNT End of message



2.2.5 Segments Description

Following service segments are as defined by UN/EDIFACT and presented under ISO 9735. 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.

UNB

UNH

MESSAGE 1

UNT

UNH

EXAMPLE OF AN INTERCHANGE STRUCTURE

MESSAGE 2

UNT

...

UNH

MESSAGE N

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.



Example Referenc

e

Segment/ Composit

e

Element Description Code or Value Comments

Example: UNB+UNOA:2+654651652+GMDATEDIPROD:ZZ+970607:1135+MPUS0331030++SGMDELJIT’ A B C D E F G H I UNB Interchange header

A S001 0001 Syntax identifier "UNOA"

B 0002 Syntax version number "2" Indication of the syntax version

used for this message.

C S002 0004 Sender identification "654651652"

Communication Code/Mailbox number of the party originating the

message.

D S003 0010 Recipient identification "GMDATEDIPR

OD"

Communication Code/Mailbox number of the party receiving the

message.

E 0007 Identification code

qualifier "ZZ" Qualifier of the party receiving the

message

F S004 0017 Date of preparation Date of

preparation YYMMDD format

G 0019 Time of preparation Time of

preparation HHMM format

H 0020

INTERCHANGE CONTROL

REFERENCE “MPUS0331030

”

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

I 0026 APPLICATION REFERENCE " SGMDELJIT"

Example: UNH+1+DELJIT:D:97A:UN+PUS’ A B C D E F UNH Message header

A 0062 Message Reference

Number

Unique message reference assigned by the sender to the

message B S009 0065 Message type "DELJIT" C 0052 Message version number "D" D 0054 Message release number "97A" E 0051 Controlling agency "UN"

F 0068 Common access

reference "PUS" “PUS” = Pick-up Sheet

Example: BGM+242::PUS+07S038167+9’ A B C D BGM Begin of message

A C002 1001 Document/message

name, coded “242” "242" = Delivery just-in-time

B 1000 Document/message

name “PUS” “PUS” = Pick-up Sheet

C C106 1004 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



group 16 of DESADV file.

D 1225 Message function code. “9” “9” = Original

Example: DTM+137:199706200812:203’ A B C

DTM(1) Document generation date

A C507 2005 Date/time/period qualifier “137” “137” means this date is the document generation date

B 2380 Date/time/period Date/time when a message is

issued.

C 2379 Date/time/period format

qualifier “203” ”203” means the date’s format is

“CCYYMMDDHHMM”

Example: DTM+234:199707100800:203’ A B C DTM(2) Pick up window at

supplier site/start

A C507 2005 Date/time/period qualifier “234” “234” means Collection date/time

earliest

B 2380 Date/time/period Start date/time of the pick up window at the supplier site.


qualifier “203” “203“ means the date’s format is

“CCYYMMDDHHMM”

Example: DTM+235:199707100800:203’ A B C

DTM(3) Pick up window at supplier site/end

A C507 2005 Date/time/period qualifier “137” “235” means Collection date/time

latest

B 2380 Date/time/period End date/time of the pick up window

at the supplier site.


qualifier “203” ”203” means the date’s format is

“CCYYMMDDHHMM”

Example: DTM+117:199707121400:203’ A B C DTM(4) Delivery window at

destination plant/start

A C507 2005 Date/time/period qualifier “117” “117” means Delivery date/time first

at Destination

B 2380 Date/time/period Start date/time of the delivery window at destination plant.



“CCYYMMDDHHMM”

Example: DTM+128:199707121400:203’ A B C

DTM(5) Delivery window at destination plant/end

A C507 2005 Date/time/period qualifier “128” “128” means Delivery date/time last

at Destination

B 2380 Date/time/period End date/time of the delivery window at destination plant.



“CCYYMMDDHHMM”



Example: NAD+SU+876543210::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 C082 3039 Party id. Identification

C 3055 Code list responsible

agency, coded “16” “16“ means the party id is DUN &

Bradstreet (DUNS). D C080 3036 Name of the party Name of the party

E C059 3042 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"

“MI” means planning schedule/material release issuer

(buyer). B C082 3039 Party id. Identification


agency, coded "92" “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 C082 3039 Goods shipping to The DUNS of the supplier


agency, coded "92" “92“ means the party id is assigned

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

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

B C202 7065 Type of packages

identification

Identification of the type of package to be used for the delivery of the

article defined in the following LIN segment.

Example: LIN+++90461451:IN’ A B



LIN Line Item A C212 7140 Item number Material number

B 7143 Item number type, coded “IN” “IN” means the item number is

buyer’s item number.

Example: LOC+11+A1A22’ A B

LOC Dock code

A 3227 Place/location qualifier "11" “11” means this segment

identifying place/port of discharge

B C517 3225 Place/location identification

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 C186 6063 Quantity qualifier. "1" “1” = Discrete Quantity

B 6060 Quantity

Actual quantity of the part number defined in the preceding LIN that

must be delivered


QTY(2) Quantity in package

A C186 6063 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


QTY(3) Chargeable gross weight

A C186 6063 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 Scheduling Conditions

A 4017 Delivery plan

commitment level, coded

With the delivery point driven method this segment group

provides the schedule for the identified delivery point and product.

Example: UNT+99+1’ A B UNT Message Trailer

A 0074 Number of segments in

the message

Control count of the number of segments in the message, including

UNH and UNT.

B 0062 MESSAGE

REFERENCE NUMBER Number must be identical to UNH -

tag 0062



Example: UNZ+1+MPUS0331030’ A B

UNZ Interchange Trailer

A 0036 INTERCHANGE

CONTROL COUNT Number of messages in an

interchange.

B 0020

INTERCHANGE CONTROL

REFERENCE

Value must be the same as 0020 - Interchange Control Reference in

UNB.



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:1+654651652 +MBXNOSUPPLIER:ZZ+970607:0735+MPUS0331030++SGMDELJIT’ UNH+1+DELJIT:D:97A:UN+PUS’ BGM+242::PUS+07S038167+9’ MAIS Pick Up Sheet identification DTM+137:199706200812:203’ Document issue date/time DTM+234:199707100800:203’ Pick up window at supplier - start DTM+235:199707100800:203’ Pick up window at supplier - end DTM+117:199707121400:203’ Delivery window at destination - start DTM+128:199707121400:203’ Delivery window at destination - end NAD+SU+007004526::16++DELPHI PACKARD+COVENTRY Supplier ROWLEY GREEK+SILVERSTONE DR+1234 56+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+++90461451: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+MPUS0331030’



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:1+654651652+MBXNOSUPPLIER:ZZ+970607:0735+MPUS0331030++SGMDELJIT'UNH+1+DELJIT:D:97A:UN+PUS'BGM+242::PUS+07S038167+9'DTM+137:199706200812:203'DTM+234:199707100800:203'DTM+117:199707121400:203'NAD+SU+007004526::16++DELPHI PACKARD+COVENTRY Supplier ROWLEY GREEK+SILVERSTONE DR+1234 56+US'NAD+MI+72872::92'NAD+ST+72872::92++OPEL POLAND'SEQ+6'PAC+3++KLT64280'LIN+++90461451:IN'LOC+11+RDC'QTY+1:3000'QTY+52:1000'QTY+101:500'SCC+1’SEQ+6'...SEQ+6'... UNT+47+1'UNZ+1+MPUS0331030'

edifact implementation guidelines for shanghai gm … edi implementation guidelines...edifact...

Documents