Message Content Inventory |
Archived, and was part of release 200601 : Identifier : M0405 - Demande, bloc retour (sur demande) / Vraag, antwoord-record (op aanvraag) - (Demande d'un bloc retour / Aanvraag van een antwoord-record) - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Broker
Receiver : Insurer
Status : 3 - 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 |
Numéro de police
|
No
|
-
|
-
|
Option.
|
RFF+001
|
||
14 |
Assureur
|
No
|
-
|
-
|
Option.
|
PTY+006
|
||
15 |
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
X044
|
||
19 |
Intermédiaire
|
No
|
-
|
-
|
Option.
|
PTY+002
|
||
20 |
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
X044(1)
|
|
25 |
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
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.