Message Content Inventory |
Identifier : ECNTRCT - Echange contextuel, données contrat - (Données contrat, pour avenant ou pour consultation)
- Approved
, and is part of release 201801 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 2 - Version : 2
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
10 |
Contrat
|
No
|
-
|
-
|
Mand.
|
|||
20 | u |
Numéro de police
|
No
|
-
|
-
|
Cond.
|
At least the one or the other
|
PolicyReference
|
30 | n |
Numéro de tarification à la compagnie
|
No
|
-
|
-
|
Cond.
|
At least the one or the other
|
CompanyQuotationReference
|
40 | u |
Intermédiaire
|
No
|
-
|
-
|
Mand.
|
PartyIntermediary
|
|
50 | u |
Intermédiaire - Numéro FSMA
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
60 | u |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie (numéro de compte producteur)
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
70 |
Contrat - indication fin dossier
|
No
|
-
|
-
|
Mand.
|
(*) 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.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.