|
|
|
A group of segments identifying a message or transaction and the status of the referred message/transaction, as well as any reasons clarifying the status. |
|
|
|
|
|
A group of segments identifying the status, and any reasons clarifying this status, of the referred message/transaction. |
|
|
|
|
|
|
Function: |
|
To provide free form or coded text information. |
|
| |
|
EAN
|
*
|
|
|
|
|
Text subject code qualifier |
|
|
M
|
|
|
|
= |
Payment detail/remittance 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 |
|
|
= |
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 any free text information related to the status information being provided.
Use of this segment in free form is not recommended since in most cases it inhibits automatic processing of the Banking Status. 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+PMD++001::ZZZ'
Agreed code value 001: The order identified in the RFF segment has not be processed because the date of the cheque was invalid. |
|
