SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M0151 - Contrat, Attestation de sinistre - partie contrat / Contract, Schadeattest - gedeelte contract - (As in Community MIG's - Echanges Intercompagnies - Attestation de sinistres - partie contrat - Voir M0213 pour la partie sinistre(s) / Inter-maatschappijberichten - Schadeattest - gedeelte contract - Zie M0213 voor gedeelte schade(s))
- Approved
, and is part of release 202201 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Insurer
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, en domaine auto
|
No
|
-
|
-
|
Mand.
|
|||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 40 |
Date d'échéance principale
|
No
|
-
|
-
|
Mand.
|
MainRenewalMonthDay
|
||
| 50 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
| 60 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
| 70 | u |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
|
| 80 |
Assureur - Nom officiel (Nom)
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName
|
||
| 90 |
Assureur - Adresse (rue, numéro, boîte, code postal, commune, code pays, pays)
|
No
|
-
|
-
|
Mand.
|
OfficialAddress
|
||
| 100 | n |
Assureur - Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
CompanyNumberReference
|
|
| 110 | n |
Assureur - Numéro d'unité d'établissement
|
No
|
-
|
-
|
Option.
|
EstablishmentUnitNumberReference
|
|
| 120 | n |
Assureur - LEI
|
No
|
-
|
-
|
Option.
|
LegalEntityIdentifierReference
|
|
| 130 |
Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
PartyMainPolicyHolder
|
||
| 140 |
Preneur - Nom officiel (Nom de famille, max. 3 prénoms, titre)
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName TitleDetail TitleCoded
|
||
| 150 |
Preneur - Adresse (rue, numéro, boîte, code postal, commune, code pays, pays)
|
No
|
-
|
-
|
Mand.
|
OfficialAddress
|
||
| 160 |
Objet de risque, véhicule
|
No
|
-
|
-
|
Mand.
|
ObjectInsuredTractorVehicle
|
||
| 170 |
Objet de risque, véhicule - numéro de plaque
|
No
|
-
|
-
|
Mand.
|
RegistrationPlateReference
|
||
| 180 | u |
Objet de risque, véhicule - type de véhicule
|
Yes
|
7
|
Mand.
|
VehicleCode
|
||
| 190 |
Objet de risque, véhicule - SAS usage du véhicule assuré
|
Yes
|
1
|
Mand.
|
SasInsuredVehicleUsageCode
|
|||
| 200 |
Objet de risque, véhicule - Garantie, R.C.
|
No
|
-
|
-
|
Mand.
|
GuaranteeCLMotor
|
||
| 210 |
Objet de risque, véhicule - Garantie, R.C. - Date d'effet
|
No
|
-
|
-
|
Mand.
|
InceptionDate
|
||
| 220 |
Objet de risque, véhicule - Garantie, R.C. - Date de fin
|
No
|
-
|
-
|
Mand.
|
PeriodEndDate
|
||
| 230 |
Objet de risque, véhicule - Garantie, R.C. - Degrée bonus/malus d'application
|
Yes
|
2
|
Mand.
|
ActualNoClaimsBonusLevelCode
|
|||
| 240 |
Message End
|
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.