|
|
|
|
Function: |
|
To provide free form or coded text information. |
|
| |
|
EAN
|
*
|
|
|
|
|
Text subject code qualifier |
|
|
M
|
*
|
|
|
= |
|
Non-acceptance information |
|
|
= |
|
Change information |
|
|
|
|
|
O
|
|
|
|
= |
Text for subsequent use |
|
|
|
|
|
D
|
|
|
This composite is only used when trading partners have agreed to use mutually defined code values. |
|
|
|
|
|
M
|
|
|
|
|
|
Code list identification code |
|
|
O
|
|
|
|
|
|
Code list responsible agency code |
|
|
D
|
|
|
|
= |
GS1 |
|
|
= |
Assigned by supplier or supplier's agent |
|
|
|
|
|
D
|
|
|
This composite is only used if coded text can not be used. |
|
|
|
|
|
M
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
O
|
|
|
|
|
|
|
D
|
|
|
ISO 639 two alpha code |
|
This data element is only used when non coded free text has been provided in data element C108. |
|
|
|
|
|
N
|
|
|
|
Segment Notes: |
|
This segment is used to provide free form or coded text information related to the entire message.
Use of this segment in free form is not recommended since it may inhibit automatic processing of the booking confirmation message. Coded references to standard texts is an available functionality which enables automatic processing and reduces transmission overheads. Standard texts should be mutually defined between trading partners and can be used to cover legal or other requirements.
This segment can be used to indicate the reason for the non-acceptance of a previous complete booking or amendments at the message level.
Example:
FTX+BAL+1+001::91'
Standard text 001 = 'Booking not accepted until outstanding accounts settled'. |
|
