|
|
|
|
Function: |
|
To provide free form or coded text information. |
|
| |
|
EAN
|
*
|
|
|
|
|
Text subject code qualifier |
|
|
M
|
|
|
|
= |
Entire transaction set |
|
|
= |
Mutually defined |
|
|
|
|
|
O
|
*
|
|
|
= |
|
Text for subsequent use |
|
|
|
|
|
D
|
|
|
This composite is only used when trading partners have agreed to use mutually defined code values. |
|
|
|
|
|
M
|
|
|
001 = Standard text between trading partners |
|
|
|
|
Code list identification code |
|
|
O
|
|
|
|
|
|
Code list responsible agency code |
|
|
D
|
|
|
|
= |
Assigned by supplier or supplier's agent |
|
|
= |
Assigned by buyer or buyer'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 or coded text information related to the complete party information message.
Use of this segment is not recommended in free form since it inhibits automatic processing of the party information. Coded references to standard texts is an available functionality which enables automatic processing and reduces transmission overheads.
Standard texts should be mutually defined among trading partners and can be used to cover legal and other requirements.
Example:
(E.g. standard text 001 = This confirms our previous transmissions).
FTX+GEN+1+001::91' |
|
