SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EPTY002 - Echange contextuel, données producteur - (Numéro compte producteur)
- Approved
, and is part of release 200601 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 2 - Version : 1
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Contrat
|
No
|
-
|
-
|
Mand.
|
XEH+01+2
|
||
| 20 |
Intermédiaire - Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PTY+002
|
||
| 30 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
PTY+002+x--x (X044-1)
|
||
| 40 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
|
No
|
-
|
-
|
Mand.
|
PTY+002++x--x (X044-2)
|
||
(*) n u d : new / updated / deleted since previous version.
(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.
Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard. And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used". Ideally we should implement the same ideas.