|
|
|
| |
Function: |
| |
To provide free form or coded text information. |
|
| |
|
EAN |
* |
|
|
|
|
Text subject code qualifier |
|
|
M |
|
| AAI |
|
= |
General information |
| ZZZ |
|
= |
Mutually defined |
|
|
|
|
|
O |
* |
|
|
|
|
|
D |
|
|
This composite is only used when trading partners have agreed to use mutually defined code values. |
|
|
|
|
|
M |
|
|
001 = Reference to standard text between trading partners. |
|
|
|
|
Code list identification code |
|
|
O |
|
|
|
|
|
Code list responsible agency code |
|
|
D |
|
| 91 |
|
= |
Assigned by supplier or supplier's agent |
| 92 |
|
= |
Assigned by buyer or buyer's agent |
|
|
|
|
|
D |
|
|
This data element is only used when non coded free text has been provided in data element C108. |
|
|
|
|
|
M |
|
|
|
|
|
|
O |
|
|
|
|
|
|
O |
|
|
|
|
|
|
O |
|
|
|
|
|
|
O |
|
|
|
|
|
|
O |
|
|
|
|
|
|
N |
|
|
|
Segment Notes: |
|
This segment is used to provide free form or coded text information which applies to the complete order status report message.
Use of this segment in free form is not recommended since in most cases it inhibits automatic processing of the order status report message.
Coded references to standard texts is an available functionality which enables automatic processing and reduces transmission and processing overheads. Standard texts should be mutually defined among trading partners and can be used to cover legal and other requirements.
Example:
FTX+AAI++001::91' |
|
