|
- |
C |
1 |
- |
Service string advice |
|
This segment is used to inform the receiver of the interchange that a set of service string characters which are different to the default characters are being used. |
|
|
|
- |
M |
1 |
- |
Interchange header |
|
This segment is used to envelope the interchange, as well as to identify both, the party to whom the interchange is sent and the party who has sent the interchange. The principle of the UNB segment is the same as a physical envelope which covers one or more letters or documents, and which details, both the address where delivery is to take place and the address from where the envelope has come. |
|
|
Delivery Schedule Heading Section
|
|
- |
M |
1 |
- |
Message header |
|
This segment is used to head, identify and specify a message. |
|
|
|
- |
M |
1 |
- |
Beginning of message |
|
This segment is used to indicate the type and function of a message and to transmit the identifying number. |
|
|
|
- |
M |
10 |
- |
Date/time/period |
|
This segment is used to specify the date of the Delivery Schedule message. |
|
|
|
- |
C |
5 |
- |
Free text |
|
This segment is used to specify any free text information relevant to the delivery schedule message. |
|
|
|
- |
C |
10 |
- |
RFF-DTM |
|
A group of segments giving references relevant to the whole message, e.g. contract number. |
|
|
|
- |
M |
1 |
- |
Reference |
|
This segment is used to identify additional references relevant to the whole Delivery Schedule. |
|
|
|
- |
C |
1 |
- |
Date/time/period |
|
This segment is used to indicate any dates associated with the references provided in the previous RFF segment. |
|
|
|
- |
C |
99 |
- |
NAD-SG4 |
|
A group of segments identifying names, addresses, locations, and contacts relevant to the whole Delivery Schedule. |
|
|
|
- |
M |
1 |
- |
Name and address |
|
This segment is used to indicate the trading parties involved in the Delivery Schedule process. Identification of buyer and supplier is mandatory in the delivery schedule. Additionally, the consignee and invoicee may also be specified if different to the buyer and supplier. |
|
|
|
- |
C |
5 |
- |
CTA-COM |
|
A group of segments to identify people, functions, or departments and appropriate numbers to whom communication should be directed. |
|
|
|
- |
M |
1 |
- |
Contact information |
|
This segment is used to identify department and/or contact names within the party specified in the previous NAD segment. |
|
|
|
- |
C |
5 |
- |
Communication contact |
|
This segment identifies the communications number, and type of communications, for the department or person identified in the previous CTA segment. |
|
|
Delivery Schedule Detail Section
|
|
- |
C |
9999 |
- |
GIS-SG7-SG12 |
|
A group of segments providing details on delivery points and products and related information using one of both scheduling methods. |
|
|
|
- |
M |
1 |
- |
General indicator |
|
The GIS segment is the trigger segment of the DELFOR details. Either a location driven approach (Segment group 7 and segment group 12) or a product driven approach (Segment group 12 and segment group 22) may follow. |
|
|
|
- |
C |
1 |
- |
NAD-LOC-FTX-SG11 |
|
A group containing delivery names and addresses, related information and details of line items to be consigned to the delivery points. |
|
|
|
- |
M |
1 |
- |
Name and address |
|
This segment triggers the location driven delivery schedule. By choosing this approach (specified in GIS segment data element 7365, value 94) the product driven approach is automatically excluded. |
|
|
|
- |
C |
10 |
- |
Place/location identification |
|
A segment identifying a place or a location and/or related locations. |
|
|
|
- |
C |
5 |
- |
Free text |
|
This segement is used to provide free form or coded text information. |
|
|
|
- |
C |
10 |
- |
TDT-DTM |
|
A group of segments specifying details of the mode and means of transport, and date/time of departure and destination relating to specified delivery point. |
|
|
|
- |
M |
1 |
- |
Details of transport |
|
This segment is used to specify transport details for the delivery schedule. If successive stages of transport need to be identified, then segment group 11 will be repeated for each successive stage, e.g.,on-carriage, etc,. |
|
|
|
- |
C |
5 |
- |
Date/time/period |
|
This segment is used to specify dates and times relevant to the previous TDT segment. |
|
|
|
- |
C |
9999 |
- |
LIN-PIA-IMD-MEA-LOC-DTM-FTX-SG13-SG17-SG20-SG22 |
|
A group of segments providing details of the individual line items for both methods. |
|
|
|
- |
M |
1 |
- |
Line item |
|
This segment is used to identify the product or service for which the schedule or forecast is being provided. |
|
|
|
- |
C |
10 |
- |
Additional product id |
|
This segment is used to specify additional or substitutional item identification codes such as a buyer's or supplier's item number. |
|
|
|
- |
C |
10 |
- |
Item description |
|
This segment is used to describe the current line item. |
|
|
|
- |
C |
5 |
- |
Measurements |
|
This segment is used to specify the actual physical dimensions of the product being sold in variable lengths or volumes. |
|
|
|
- |
C |
999 |
- |
Place/location identification |
|
|
|
- |
C |
5 |
- |
Date/time/period |
|
Date/time/period associated with the line item, such as the date of the engineering change. |
|
|
|
- |
C |
5 |
- |
Free text |
|
This segment is used to specify any special requirements for the current line item. |
|
|
|
- |
C |
10 |
- |
RFF-DTM |
|
A group of segments giving references related to the line item and where necessary, their dates. |
|
|
|
- |
M |
1 |
- |
Reference |
|
This segment is used to provide reference numbers which provide further identification of each line item in the delivery schedule. |
|
|
|
- |
C |
1 |
- |
Date/time/period |
|
This segment is used to indicate any dates associated with the references provided in the previous RFF segment. |
|
|
|
- |
C |
999 |
- |
SCC-SG18 |
|
A group of segments specifying the schedule information for the product identified in the LIN segment. With the delivery point driven method this segment group provides the schedule for the identified delivery point and product. With the product driven method this segment group can be used to summarise all schedules provided with the subsequent delivery point information given in segment group 22. |
|
|
|
- |
M |
1 |
- |
Scheduling conditions |
|
This segment is used to specify the type and status of the schedule being given, and optionally defining a pattern to be established, e.g., firm or proposed delivery schedule for a weekly pattern. |
|
|
|
- |
C |
999 |
- |
QTY-DTM |
|
A group of segments specifying quantity related information for actual delivery, reporting or cumulative quantities and forecast quantities as required for the line item under the schedule conditions of the previous SCC segment. |
|
|
|
- |
M |
1 |
- |
Quantity |
|
This segment is used to specify quantities related to the current SCC item. |
|
|
|
- |
C |
2 |
- |
Date/time/period |
|
This segment is used to provide dates and times relating to the quantity and schedule details in the SCC/QTY segments. This segment may indicate date/time ranges, e.g., the start and end date for a delivery pattern, etc. |
|
|
|
- |
C |
99 |
- |
PAC |
|
A group of segments identifying the packaging for goods referenced in the line item to be delivered. |
|
|
|
- |
M |
1 |
- |
Package |
|
This segment is used to provide packaging details for the current line item. |
|
|
|
- |
C |
999 |
- |
NAD-SG27-SG30 |
|
A group of segments providing details of the individual delivery points for the given product. |
|
|
|
- |
M |
1 |
- |
Name and address |
|
This segment is used to identify the delivery points for the current line item. |
|
|
|
- |
M |
999 |
- |
SCC-SG28 |
|
A group of segments specifying scheduling information detailing quantities and date for the given delivery point. This segment group also specifies references and their associated dates related to the schedule as required for the delivery point. |
|
|
|
- |
M |
1 |
- |
Scheduling conditions |
|
This segment is used to specify the type and status of the schedule being given, and optionally defining a pattern to be established, e.g., firm or proposed delivery schedule for a weekly pattern. |
|
|
|
- |
M |
999 |
- |
QTY-DTM |
|
A group of segments specifying quantity related information and associated dates for the actual delivery. |
|
|
|
- |
M |
1 |
- |
Quantity |
|
This segment is used to specify quantities related to the current delivery party. |
|
|
|
- |
C |
2 |
- |
Date/time/period |
|
This segment is used to provide dates and times relating to the quantity and schedule details in the SCC/QTY segments. This segment may indicate date/time ranges, e.g., the start and end date for a delivery pattern, etc. |
|
|
|
- |
C |
10 |
- |
TDT-DTM |
|
A group of segments specifying details of the mode and means of transport, and date/time of departure and destination relating to the specified location. |
|
|
|
- |
M |
1 |
- |
Details of transport |
|
This segment is used to specify transport details for the delivery schedule. If successive stages of transport need to be identified, then segment group 30 will be repeated for each successive stage, e.g.,on-carriage, etc. |
|
|
|
- |
C |
5 |
- |
Date/time/period |
|
This segment is used to specify dates and times relevant to the previous TDT segment. |
|
|
|
- |
M |
1 |
- |
Message trailer |
|
This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message. |
|
|
|
- |
M |
1 |
- |
Interchange trailer |
|
This segment is used to provide the trailer of an interchange. |
|
|