delivery schedule message delfor (jit) (inbound … instruments incorporated 1 of 34 delivery...

Texas Instruments Incorporated 1 of 34 Delivery Schedule Message (DELFOR) v. 1.0

TEXAS INSTRUMENTS

Delivery Schedule Message

DELFOR (JIT)

(Inbound to TI)

Based on EDIFICE Issue 2(Based on EDIFACT Version 92.1)

Date : July 1996TI Version 1.0

This document can be found on the World Wide Web from http://www.ti.com/sc/docs/scedi/sctecpak.htm


Copyright 1996Texas Instruments IncorporatedAll Rights Reserved

The information and/or drawings set forth in this document and all rights in and to inventionsdisclosed herein and patents which might be granted there on disclosing and employing thematerials, methods, techniques, or apparatus described herein are exclusive property of TexasInstruments Incorporated.


Table of Contents

TITLE __________________________________________________________________PAGE

TABLE OF CONTENTS________________________________________________________ 3INTRODUCTION _____________________________________________________________ 4HOW TO USE THIS DOCUMENTATION_________________________________________ 5PURPOSE OF THIS MESSAGE _________________________________________________ 6REFERENCES _______________________________________________________________ 7EDIFICE MESSAGE DIAGRAM_________________________________________________ 8UNH MESSAGE HEADER_____________________________________________________ 9BGM BEGINNING OF MESSAGE _____________________________________________ 10DTM DATE / TIME / PERIOD ________________________________________________ 11SEGMENT GROUP 1________________________________________________________ 12RFF REFERENCE ___________________________________________________________ 13SEGMENT GROUP 2_________________________________________________________ 14NAD NAME AND ADDRESS _________________________________________________ 15SEGMENT GROUP 3_________________________________________________________ 17CTA CONTACT INFORMATION ______________________________________________ 18COM COMMUNICATION CONTACT __________________________________________ 19UNS SECTION CONTROL____________________________________________________ 20SEGMENT GROUP 18________________________________________________________ 21

LIN LINE ITEM ________________________________________________________ 22PIA ADDITIONAL PRODUCT ID _________________________________________ 23

SEGMENT GROUP 24________________________________________________________ 24NAD NAME AND ADDRESS _____________________________________________ 25

SEGMENT GROUP 27________________________________________________________ 26QTY QUANTITY _______________________________________________________ 27SCC SCHEDULING CONDITIONS ________________________________________ 28DTM DATE / TIME / PERIOD ____________________________________________ 29

SEGMENT GROUP 28________________________________________________________ 30RFF REFERENCE_______________________________________________________ 31

UNS SECTION CONTROL____________________________________________________ 32UNT MESSAGE TRAILER____________________________________________________ 33EXAMPLES ________________________________________________________________ 34


Introduction

This guide was developed by members of the Texas Instruments EDI message development Group. It isbased on the guide developed by members of the Electronics Industry through the associationsrepresenting Europe (EDIFICE), Japan (EIAJ) and the USA (EIDX). It represents and is specific to theusage as specified by Texas Instruments.


How To Use This Documentation

This document was created to aid in your implementation of UN/EDIFACT standards. This documentationcontains those segments and elements that will be used by Texas Instruments Incorporated.

A complete description of the segments are outlined in the UN/EDIFACT Standards Manual. If yourequire/need to be sent additional segments not listed in this documentation, an agreement must be reached withTexas Instruments Incorporated.

This document defines the TI preferred structure and content of the EDIFICE endorsed DEFLOR message.

Segment/Data Element Usage(M) Mandatory = EDIFACT dictates that the Data Element or Segment must be present.(R) Required = EDIFICE members agree that the data concerned must be sent.(D) Depending = The data concerned must be sent if a particular defined condition or set of conditions exists.

The associated conditions must be explained at the appropriate level of detail.(A) Advised = Indicates that the RECEIVER of the message would prefer the data concerned to be sent, but

does not require its transmission.(O) Optional = Indicates that the transmission of the data concerned is at the need or discretion of the

SENDER, i.e. it is not required by the receiver in order to perform its business function.EDIFICE requires that the use of ‘O’ must be agreed between trading partners.

(X) Not Used = The Data Element or Segment will not be used by EDIFICE members.

The EDIFICE usage status and number of occurrences for segments or segment groups will berepresented analogue to the representation of data elements.

e.g.: R3 The segment or group is required 3 times (fixed number)R..3 The segment or group is required up to 3 times (maximum number)

Data Element Representation(a) Alpha(an) Alpha Numeric(n) Numeric

EnvelopingThe UNB/UNZ interchange envelope and the UNH/UNT message envelope are shown in this documentin the message diagram. Details on these segments are found separately in the SERSEG document.

Texas Instruments Instruments 6 of 34 Delivery Schedule Message (DELFOR) v.1.0

Purpose of this Message

The Delivery Schedule message is used to give information on future product requirements(FORECAST) and for placing firm orders (CALL-OFFS) which relate to previous forecasts. Thismessage can also be used for committing to material acquisition for, and production of, products, wherefinal delivery requirements are not specified. Texas Instruments does not currently make use ofcommitted quantities.

The Delivery Schedule Message can be used in a number of different business cycles. Typical businesscycles are:

a) to forecast material in association with blanket purchase orders.

b) to forecast material in association with a contract.

With both these uses call off can be made using one of the following methods:

- with a Delivery Schedule message - with a Delivery Just in Time message - with a traditional purchase order (either EDI or manual)

The Delivery Schedule Message will normally be used where trading partners have a stable tradingenvironment, and multiple deliveries of stable product requirements exist.

A typical streamlined business cycle using Blanket Order and Delivery Just in Time messages would be:

+--------------+ +----------------+ ! ! BLANKET PO (transmitted e.g. annually) ! ! ! B ! --------------------------------------------------------> ! S ! ! U ! ! E ! ! Y ! DELFOR (transmitted e.g. monthly) ! L ! ! E ! -------------------------------------------------------> ! L ! ! R ! ! E ! ! ! DELJIT (transmitted e.g. daily) ! R ! ! ! --------------------------------------------------------> ! !

+-------------+ +----------------+


References

UNSM DELIVERY SCHEDULE MESSAGE STATUS 1, RELEASE 921; REF UN 92-09EDIFACT STANDARD DATA SEGMENT DIRECTORY 92.1EDIFACT CODE LIST 92.1EDIFICE Utilisation of the EDIFACT Service Segments, Issue 2ISO 9735 : 1988 (E) EDIFACT APPLICATION LEVEL SYNTAX RULES FIRST EDITION : 1988-07-15 AMENDED AND REPRINTED : 1990-11-15ISO 4217 Codes for the representation of currencies and fundsISO 3166 Codes for the representation of names of countriesUN/ECE Recommendation 20 Codes for Units of MeasurementUN/ECE Recommendation 21 Codes for types of Cargo, Packages and Packaging Materials


Delivery Schedule (DELFOR)

SEG NAME REQDES

MAXUSE

LOOP REPEAT

UNB Interchange header M 1UNH Message header M 1

BGM Beginning of message M 1DTM Date/time/period R 1

SEGMENT GROUP 1 D..4RFF Reference M 1

SEGMENT GROUP 2 R..5NAD Name and Address M 1

SEGMENT GROUP 3 O..2CTA Contact information M 1COM Communication contact R ..3

UNS Section Control M 1

SEGMENT GROUP 18 R..9999LIN Line Item M 1PIA Additional product id D ..10

SEGMENT GROUP 24 R R..500NAD Name and Address M 1

SEGMENT GROUP 27 R..50QTY Quantity M 1SCC Scheduling conditions R 1DTM Date/time/period R ..2

SEGMENT GROUP 28 D 1RFF Reference M 1

UNS Section control M 1

UNT Message trailer M 1UNZ Interchange trailer M 1


UNH - Message Header

Function: To head, identify and specify a message.

Usage: M1

Remarks: Refer to EDIFICE Utilisation of the EDIFACT Service Segments, Issue 2.

Field # Ref. Rep. Field Usage TI UtilisationUNH01 0062 an..14 MESSAGE REFERENCE

NUMBERM Transmission message count from 1

UNH02 S009 MESSAGE IDENTIFIER M0065 an..6 Message type identifier M ‘DELFOR’0052 an..3 Message type version number M ‘1’0054 an..3 Message type release number M ‘921’0051 an..2 Controlling agency M ‘UN’0057 an..6 Association assigned code R ‘ED2’

UNH03 0068 an..35 COMMON ACCESSREFERENCE

X

UNH04 S010 STATUS OF THE TRANSFER O0070 n..2 Sequence message transfer

numberM

0073 a..1 First/last sequence messagetransfer indication

O


BGM - Beginning of Message

Function: To indicate the beginning of the Delivery Schedule message and to transmit the deliveryschedule number.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationBGM01 C002 DOCUMENT/MESSAGE NAME R

1001 an..3 Document/message name, coded R ‘241’ Delivery schedule1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency,

codedX

1000 an..35 Document/message name XBGM02 1004 an..35 DOCUMENT/MESSAGE

NUMBERR Delivery schedule number

BGM03 1225 an..3 MESSAGE FUNCTION, CODED XBGM04 4343 an..3 RESPONSE TYPE, CODED X


DTM - Date/Time/Period

Function: To specify date of the Delivery Schedule message.

Usage: R1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationDTM01 C507 DATE/TIME PERIOD M

2005 an..3 Date/time/period qualifier M '137' Document/message date/time2380 an..35 Date/time/period R2379 an..3 Date/time/period format

qualifierR '102' CCYYMMDD


Segment Group 1

Function: To indicate reference documents associated with the whole Delivery Schedule message..

Usage: D..4

Remarks: Reference (RFF) segments specifying contract or blanket order number should be present.Where the information refers to the whole Delivery Schedule message it must be in SegmentGroup 1.

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 1 D..4RFF Reference M 1


Segment Group 1RFF - Reference

Function: To specify contract or the previous Delivery schedule references.

Usage: M1

Remarks: This RFF segment is used where blanket order or contract applies to the whole message.

Field # Ref. Rep. Field Usage TI UtilisationRFF01 C506 REFERENCE M

1153 an..3 Reference qualifier M See Note 11154 an..35 Reference number R As specified by DE 11531156 an..6 Line number X4000 an..35 Reference version number X

RFF Notes

1. DE 1153 REFERENCE QUALIFIER‘BO’ Blanket order number‘CT’ Contract number

Reference number of the contract between two partiesTI requires a numeric contract number.


Segment Group 2

Function: A group of segments that identify name, address and contacts of the parties relevant to thewhole Delivery Schedule message.

Usage: R1

Remarks: The NAD segments that identify the buyer and the seller must be present. Where there aremultiple delivery locations then this information should be transmitted at detail level.

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 2 R..5NAD Name and Address M 1



Segment Group 2NAD - Name and Address

Function: To specify the identification/name/address of the parties involved in the Delivery Schedulemessage.

Usage: M1

Remarks: EDIFICE advises that the Party Identification composite element (C082) be used. When C082cannot be used EDIFICE recommends using the structured name and address elements (C080through 3207), rather than the unstructured one (C058).

Field # Ref. Rep. Field Usage TI UtilisationNAD01 3035 an..3 PARTY QUALIFIER M See Note 1NAD02 C082 PARTY IDENTIFICATION

DETAILSA

3039 an..17 Party id identification M1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency,

codedR See Note 2

NAD03 C058 NAME AND ADDRESS D3124 an..35 Name and address line M3124 an..35 Name and address line O3124 an..35 Name and address line O3124 an..35 Name and address line O3124 an..35 Name and address line O

NAD04 C080 PARTY NAME D3036 an..35 Party name M3036 an..35 Party name O3036 an..35 Party name O3036 an..35 Party name O3036 an..35 Party name O3045 an..3 Party name format, coded X

NAD05 C059 STREET D3042 an..35 Street and number/P.O. Box M3042 an..35 Street and number/P.O. Box O3042 an..35 Street and number/P.O. Box O

NAD06 3164 an..35 CITY NAME DNAD07 3229 an..9 COUNTRY SUB-ENTITY

IDENTIFICATIOND

NAD08 3251 an..9 POSTCODE IDENTIFICATION DNAD09 3207 an..3 COUNTRY, CODED D See ISO 3166 2 alpha code


Segment Group 2NAD - Name and Address (Continued)

NAD Notes

1. DE 3035 PARTY QUALIFIER'BY' Buyer‘DP' Delivery party'SE' Seller

At least the BY and SE codes should be present. The DP code should only be used once between Blanket Order,Delivery Schedule message and Delivery Just in Time. They should be transmitted as soon as the buyer knows theinformation and should not be subject to change.

2. DE 3055 CODE LIST RESPONSIBLE AGENCY, CODED'91' Assigned by seller or seller's agent'92 Assigned by buyer or buyer's agent


Segment Group 3

Function: To give additional contact information relating to the party specified in the NAD segment.

Usage: O..2

Remarks: This segment group will only be used under the NAD identifying the buyer.

SEG NAME REQDES

MAXUSE

LOOP REPEAT



Segment Group 3CTA - Contact information

Function: To identify a person or a department to whom communication should be directed.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI Utilisation

CTA01 3139 an..3 CONTACT FUNCTION, CODED R 'PD' Purchasing contactCTA02 C056 DEPARTMENT OR EMPLOYEE

DETAILSR See Note 1

3413 an..17 Department or employeeidentification

D

3412 an..35 Department or employee A

CTA Notes

1. DE C056 DEPARTMENT OR EMPLOYEE DETAILSEDIFICE recommends to use the employee name in preference to the department name, in DE 3412. Thisinformation can alternatively be coded in DE 3413.


Segment Group 3COM - Communication contact

Function: To identify a communication number of a department or a person to whom communicationshould be directed.

Usage: R..3

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationCOM01 C076 COMMUNICATION CONTACT M

3148 an..25 Communication number M3155 an..3 Communication channel qualifier M See Note 1

COM Notes

1. DE 3155 COMMUNICATION CHANNEL QUALIFIER'TE' Telephone'TL' Telex'FX' Telefax


Segment Group 3UNS - Section Control

Function: To separate header and detail sections of a Delivery Schedule message.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationUNS01 0081 a1 SECTION IDENTIFICATION M ‘D’ Start of detail


Segment Group 18

Function: A group of segments containing part information, quantities and dates plus the status of eachquantity.

Usage: R..9999

Remarks:

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 18 R..9999LIN Line Item M 1PIA Additional product id D ..10





Segment Group 18LIN - Line Item

Function: To identify a line item for which a forecast is given and/or a call-off is made and the itemnumber agreed to be the primary reference number between the Buyer and Seller.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationLIN01 1082 n..6 LINE ITEM NUMBER R See Note 1LIN02 1229 an..3 ACTION REQUEST/

NOTIFICATION, CODEDX

LIN03 C212 ITEM NUMBER IDENTIFICATION A7140 an..35 Item number R Buyer Part Number7143 an..3 Item number type, coded R ‘BP’ Buyer’s part number

1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency, coded R‘92’ Assigned by buyer or buyer’s

agentLIN04 5495 an..3 SUB-LINE INDICATOR, CODED XLIN05 1222 n..2 CONFIGURATION LEVEL XLIN06 7083 an..3 CONFIGURATION, CODED X

LIN Notes

1. DE 1082 LINE ITEM NUMBERIt is required to assign a number to the line items within a message. The number is assigned by the sender of themessage. The first line item within a message will be numbered '1' and further line items will be incremented by'1' for each new line.


Segment Group 18PIA - Additional Product ID

Function: To specify additional item identification.

Usage: D..10

Remarks: Additional information that needs to be attached to the product such as engineering changelevel can also be included in this segment.

Field # Ref. Rep. Field Usage TI UtilisationPIA01 4347 an..3 PRODUCT ID FUNCTION

QUALIFIERM ‘1’ Additional identification

PIA02 C212 ITEM NUMBER IDENTIFICATION M7140 an..35 Item number R Vendor Part Number7143 an..3 Item number type, coded R See Note 1

1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency, coded R See Note 2

PIA03 C212 ITEM NUMBER IDENTIFICATION O7140 an..35 Item number R Engineering change level7143 an..3 Item number type, coded R See Note 1

1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency, coded R See Note 2

PIA04 C212 ITEM NUMBER IDENTIFICATION O7140 an..35 Item number R7143 an..3 Item number type, coded R1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency, coded R




Segment Group 18PIA - Additional Product ID

PIA Notes:

1. DE 7143 ITEM NUMBER TYPE, CODED'EC' Engineering change level'VP' Vendor's (seller's) part number

2. DE 3055 CODE LIST RESPONSIBLE AGENCY, CODED'91' Assigned by seller or seller's agent‘92’ Assigned by buyer or buyer’s agent


Segment Group 24

Function: A group of segments providing quantity and scheduling details relating to the individualdeliveries, and details of multiple delivery locations.

Usage: R..500

Remarks: When there is a single delivery location this information will be given in the header level NADand a dummy NAD will be sent in this Segment Group.

SEG NAME REQDES

MAXUSE

LOOP REPEAT





Segment Group 24NAD - Name and Address

Function: To specify multiple delivery party name and address details.

Usage: M1

Remarks: Use the code ‘ZZZ’ when no information is to be given in this segment.

Field # Ref. Rep. Field Usage TI UtilisationNAD01 3035 an..3 PARTY QUALIFIER M 'ZZZ' Mutually defined

Only to be used as a Dummy to allowaccess to SG 24.

NAD02 C082 PARTY IDENTIFICATIONDETAILS

A

3039 an..17 Party id identification M1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency,

codedR

NAD03 C058 NAME AND ADDRESS D3124 an..35 Name and address line M3124 an..35 Name and address line O3124 an..35 Name and address line O3124 an..35 Name and address line O3124 an..35 Name and address line O

NAD04 C080 PARTY NAME D3036 an..35 Party name M3036 an..35 Party name O3036 an..35 Party name O3036 an..35 Party name O3036 an..35 Party name O3045 an..3 Party name format, coded X

NAD05 C059 STREET D3042 an..35 Street and number/P.O. Box M3042 an..35 Street and number/P.O. Box O3042 an..35 Street and number/P.O. Box O

NAD06 3164 an..35 CITY NAME DNAD07 3229 an..9 COUNTRY SUB-ENTITY

IDENTIFICATIOND

NAD08 3251 an..9 POSTCODE IDENTIFICATION DNAD09 3207 an..3 COUNTRY, CODED D See ISO 3166 2 alpha code


Segment Group 27

Function: A group of segments specifying quantity related information for actual delivery, materialand/or manufacturing committed quantities and forecast quantities as required for the lineitem.

Usage: R..50

Remarks:

SEG NAME REQDES

MAXUSE

LOOP REPEAT




Segment Group 27QTY - Quantity

Function: To specify quantities

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationQTY01 C186 QUANTITY DETAILS M

6063 an..3 Quantity qualifier M See Note 16060 n..15 Quantity M Quantity6411 an..3 Measure unit qualifier O See Note 2

QTY Notes

1. DE 6063 QUANTITY QUALIFIER'21 Ordered quantity'FQ' Forecast quantity

Use this code until EDIFACT makes one available.

These codes are used with the following codes in SG 27 SCC.Code '21' with code '1'.Code 'FQ' with code '4'.

2. DE 6411 MEASURE UNIT QUALIFIERSee UN/ECE recommendation number 20, 3 alpha code


Segment Group 27SCC - Scheduling Conditions

Function: To clearly indicate whether the Quantity and Dates in segment group 27 are CALL-OFF orFORECAST data.

Usage: R1

Remarks: As well as SCC+1 and SCC+4 TI recognizes the existence of SCC+2 (Commitment for manufacturing and material) and SCC+3 (Commitment for material) but converts them to SCC+4, thus only recognizing firm and forecast quantities.

Field # Ref. Rep. Field Usage TI UtilisationSCC01 4017 an..3 DELIVERY PLAN STATUS

INDICATOR, CODEDM See Note 1

SCC02 4493 an..3 DELIVERY REQUIREMENTS,CODED

X

SCC03 C329 PATTERN DESCRIPTION X2013 an..3 Frequency, coded2015 an..3 Despatch pattern, coded2017 an..3 Despatch pattern timing, coded

SCC Notes

1. DE 4017 DELIVERY PLAN STATUS INDICATOR, CODED'1' Firm‘2’ Commitment for manufacturing and material‘3’ Commitment for material'4' Planning/forecast


DTM - Date/Time/Period

Function: To specify either the timeframe for a forecast i.e. horizon start and end date (SCC segmentDE 4017 Codes ‘2’ , ‘3’ , ‘4’), or the requested delivery date (SCC segment DE 4017 Code‘1’) in the case of call-offs.

Usage: R..2

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationDTM01 C507 DATE/TIME PERIOD M

2005 an..3 Date/time/period qualifier M See Note 12380 an..35 Date/time/period R2379 an..3 Date/time/period format qualifier R '102' CCYYMMDD

DTM Notes

1. DE 2005 DATE/TIME/PERIOD QUALIFIER'2' Delivery date/time, requested'158' Horizon start date'159 Horizon end date

TI currently has no facility to process horizon dates. At least one DTM segment must be sent fora forecast with a qualifier of 158. This will become the forecast date.


Segment Group 28

Function: A group of segments providing reference to a purchase order number or a delivery schedulenumber. The segment is only used for firm CALL - OFFS.

Usage: D1

Remarks: This segment is only used when the SCC segment DE 4017 code is '1'. It is used only where itis necessary to give different references for each CALL - OFF quantity. At this level of detailonly one reference should be given in this Segment Group.

SEG NAME REQDES

MAXUSE

LOOP REPEAT



Segment Group 28RFF - Reference

Function: To reference purchase order number for CALL-OFFS.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationRFF01 C506 REFERENCE M

1153 an..3 Reference qualifier M 'ON' Order number (purchase)

1154 an..35 Reference number R As specified by DE 11531156 an..6 Line number X4000 an..35 Reference version number X


UNS - Section Control

Function: To separate detail and summary sections of a Delivery Schedule message.

Usage: M1

Remarks:


UNS01 0081 a1 SECTION IDENTIFICATION M ‘S’ Start of summary


UNT - Message Trailer

Function: To end and check the completeness of a message.

Usage: M1

Remarks: Refer to EDIFICE Utilisation of the EDIFACT Service Segments, Issue 2.


UNT01 0074 n..6 NUMBER OF SEGMENTS INA MESSAGE

M

UNT02 0062 an..14 MESSAGE REFERENCENUMBER

M


Examples

EXAMPLE 1 - FORECAST AND CALL-OFF.

UNH+1+DELFOR:1:921:UN:ED2'

Header Section

BGM+241+5678' Delivery Schedule NumberDTM+137:19970518:102' Message DateRFF+CT+999456' Contract NumberNAD+BY+ABC LTD::92' Customer - Buyer IdCTA+PD+:PETER SMITH'COM+0756-551234:TE'NAD+DP+ABC SHIP::92 Customer - Delivery Party IdNAD+SE+TEXAS001::91 Seller IdUNS+D'

Detail Section

LIN+1++ABC0071:BP::92 Buyers Part NumberPIA+1+ACT2T:VP::91' Vendors Part NumberNAD+ZZZ'QTY+FQ:500:PCE' Forecast quantitySCC+4' ForecastDTM+158:19970524:102' Horizon start dateDTM+159:19970524:102' Horizon end dateQTY+FQ:500:PCE'SCC+4'DTM+158:19970601:102'DTM+159:19970601:102'QTY+21:500:PCE' Call-off quantitySCC+1' Call-offDTM+2:19970524:102' Call-off dateRFF+ON:5677' Purchase order number

UNS+S'

UNT+26+1'

delivery schedule message delfor (jit) (inbound … instruments incorporated 1 of 34 delivery...

Documents