Syntax Independent Components
Implementation Related Components
Implementation Related Components
|
|
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0405 - Demande, bloc retour (sur demande) / Vraag, antwoord-record (op aanvraag) - (Demande d'un bloc retour / Aanvraag van een antwoord-record) - ( UN/Edifact MIG : Fr / Nl ) |
Version : 1 Status : 3 |
| n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
XML-tag |
UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
Numéro de police
|
No
|
-
|
-
|
Option.
|
Contract ContractIdentifier
|
RFF+001
|
||
Assureur
|
No
|
-
|
-
|
Option.
|
PartyRole Insurer
|
PTY+006
|
||
Assureur - Numéro CBFA
|
No
|
-
|
-
|
Mand.
|
InsuranceProvider ICBIdentifier
|
X044
|
||
Intermédiaire
|
No
|
-
|
-
|
Option.
|
PartyRole InsuranceProvider Intermediary
|
PTY+002
|
||
Intermédiaire - Numéro CBFA
|
No
|
-
|
-
|
Option.
|
Since 15/7/2017 the FSMA no longer attributes such number
|
InsuranceProvider ICBIdentifier
|
X044(1)
|
|
Intermédiaire - Identifiant de l'intermédiaire aupres de la compagnie
|
No
|
-
|
-
|
Mand.
|
Intermediary BrokerAccountIdentifier
|
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.