Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0421 - Demande, attestation de sinistres / Vraag, schadeattest - (As in Community MIG's - Echanges Intercompagnies / Inter-maatschappijberichten - Demande attestation de sinistres / Aanvraag schadeattest)
- Approved
, and is part of release 200601 |
Sender : Insurer
Receiver : Insurer
Status : 2 - Version : 1
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
|||||||
| 10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
XEH+04+1+0421+++domain++++yyyymmddhhmm+xx' (=X916 and =X918)
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+04+1+0421+++domain++++yyyymmddhhmm+xx:::M0421' (=X943)
|
ExchangeUnitBusinessContentDescription
|
||
| 30 |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+04+1+0421+++domain++++yyyymmddhhmm+xx:::M0421:1' (=X944)
|
ExchangeUnitBusinessContentDescriptionVersion
|
||
| 40 |
Compagnie émettrice
|
No
|
-
|
-
|
Mand.
|
PTY+043
|
PartySendingCompany
|
||
| 50 |
Compagnie émettrice Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PTY+043+x--x:006
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 60 |
Compagnie émettrice Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+043 - RFF+075:x--x'
|
CompanyNumberReference
|
||
| 70 |
Compagnie émettrice Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
PTY+043 - RFF+076:x--x'
|
EstablishmentUnitNumberReference
|
||
| 80 |
Compagnie émettrice Assureur - LEI
|
No
|
-
|
-
|
Option.
|
PTY+043 - RFF+107:x--x'
|
LegalEntityIdentifierReference
|
||
| 90 |
Compagnie émettrice Assureur - Numéro du dossier
|
No
|
-
|
-
|
Mand.
|
PTY+043 - RFF+017:x--x'
|
FileReference
|
||
| 100 |
Compagnie destinataire
|
No
|
-
|
-
|
Mand.
|
PTY+044
|
PartyReceivingCompany
|
||
| 110 |
Compagnie destinataire Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PTY+044+x--x:006
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 120 |
Compagnie destinataire Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
PTY+044 - RFF+075:x--x'
|
CompanyNumberReference
|
||
| 130 |
Compagnie destinataire Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
PTY+044 - RFF+076:x--x'
|
EstablishmentUnitNumberReference
|
||
| 140 |
Compagnie destinataire Assureur - LEI
|
No
|
-
|
-
|
Option.
|
PTY+044 - RFF+107:x--x'
|
LegalEntityIdentifierReference
|
||
| 150 |
Compagnie destinataire Assureur - Numéro de police
|
No
|
-
|
-
|
Mand.
|
PTY+044 - RFF+001:x--x'
|
PolicyReference
|
||
| 160 |
Message end
|
No
|
-
|
-
|
Mand.
|
XET+04
|
|||
(*) 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.