Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : M0140 - Contrat, transmission donn. carte verte au FCGB-Veridass / Contract, groene kaart naar BGWF-Veridass - (FCGB/BGWF - Veridass - Envoi de la carte verte / Opsturen van de groene kaart / (Belgian Mutual Guarantee Fund) - Modifications imposées dés 01.10.2010 - WGN 20240612 (item #218): Stop updating.)
- Approved
, and is part of release 201510 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : BMGF
Status : 2 - Version : 3
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 40 |
Contrat
|
No
|
-
|
-
|
Mand.
|
|||
| 50 |
Code opération VERIDASS
|
Yes
|
1
|
Mand.
|
VeridassTransactionProcesscode
|
|||
| 60 |
Date de la dernière mise à jour
|
No
|
-
|
-
|
Mand.
|
LastUpdateDate
|
||
| 70 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
| 80 |
Assureur
|
No
|
-
|
-
|
Mand.
|
PartyInsurer
|
||
| 90 |
Assureur - Numéro FSMA
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 100 |
Assureur - Identifiant siège ou succursale
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier PartySeatSubsidiaryIdentificationDetail SeatSubsidiaryIdentifier
|
||
| 110 |
Preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
PartyMainPolicyHolder
|
||
| 120 |
Preneur - Nom officiel - Nom de famille
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName
|
||
| 130 |
Preneur - Nom officiel - Premier prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 140 |
Preneur - Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 150 |
Preneur - Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail FirstName
|
||
| 160 |
Preneur - Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail NameExtension
|
||
| 170 |
Preneur - Code titre
|
Yes
|
0
|
Option.
|
OfficialName TitleDetail TitleCoded
|
|||
| 180 |
Preneur - Titre
|
No
|
-
|
-
|
Option.
|
OfficialName TitleDetail TitleCoded TitleName
|
||
| 190 |
Preneur - Adresse - rue
|
No
|
-
|
-
|
Mand.
|
OfficialAddress AddressDetail StreetName
|
||
| 200 |
Preneur - Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail HouseNumber
|
||
| 210 |
Preneur - Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail BoxNumber
|
||
| 220 |
Preneur - Adresse - extension
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressExtension
|
||
| 230 |
Preneur - Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressIdentifier
|
||
| 240 |
Preneur - Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
OfficialAddress
|
||
| 250 |
Preneur - Adresse - code postal
|
No
|
-
|
-
|
Mand.
|
OfficialAddress PostalCode
|
||
| 260 |
Preneur - Adresse - localité
|
No
|
-
|
-
|
Mand.
|
OfficialAddress CityName
|
||
| 270 |
Preneur - Adresse - code pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryCoded
|
||
| 280 |
Preneur - Adresse - pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryName
|
||
| 290 |
Preneur - Langue de communication
|
Yes
|
3
|
Mand.
|
LanguageCode
|
|||
| 300 | u |
Objet de risque : véhicule ou remorque
|
No
|
-
|
-
|
Mand.
|
ObjectInsured...
|
|
| 310 |
Véhicule - Marque
|
No
|
-
|
-
|
Mand.
|
MakeModelTypeName NameDetail LastName
|
||
| 320 |
Véhicule - Modèle
|
No
|
-
|
-
|
Mand.
|
MakeModelTypeName NameDetail FirstName
|
||
| 330 |
Véhicule - Type
|
No
|
-
|
-
|
Option.
|
MakeModelTypeName NameDetail FirstName
|
||
| 340 |
Véhicule - Numéro plaque d'immatriculation
|
No
|
-
|
-
|
Mand.
|
RegistrationPlateReference
|
||
| 350 |
Véhicule - Numéro plaque d'immatriculation - nouveau, corrigé
|
No
|
-
|
-
|
Mand.
|
RegistrationPlateReference
|
||
| 360 |
Véhicule - Numéro plaque d'immatriculation - ancien
|
No
|
-
|
-
|
Mand.
|
RegistrationPlateReference
|
||
| 370 |
Véhicule - Numéro de châssis
|
No
|
-
|
-
|
Option.
|
ObjectInsuredTractorVehicle ChassisReference
|
||
| 380 |
Véhicule - Numéro de châssis - nouveau, corrigé
|
No
|
-
|
-
|
Option.
|
ObjectInsuredTractorVehicle ChassisReference
|
||
| 390 |
Véhicule - Numéro de châssis - ancien
|
No
|
-
|
-
|
Option.
|
ObjectInsuredTractorVehicle ChassisReference
|
||
| 400 | n |
Véhicule - VIN Unifier
|
No
|
-
|
-
|
Option.
|
DIV change imposed starting 20151001
|
VinUnifierReference
|
| 410 | n |
Véhicule - VIN Unifier - nouveau, corrigé
|
No
|
-
|
-
|
Option.
|
DIV change imposed starting 20151001
|
VinUnifierReference
|
| 420 | n |
Véhicule - VIN Unifier - ancien
|
No
|
-
|
-
|
Option.
|
DIV change imposed starting 20151001
|
VinUnifierReference
|
| 430 | n |
Véhicule - Check Digit Numéro de châssis
|
No
|
-
|
-
|
Option.
|
ObjectInsuredTractorVehicle CheckDigitOnTheChassisNumberReference
|
|
| 440 | n |
Véhicule - Check Digit Numéro de châssis - nouveau, corrigé
|
No
|
-
|
-
|
Option.
|
ObjectInsuredTractorVehicle CheckDigitOnTheChassisNumberReference
|
|
| 450 | n |
Véhicule - Check Digit Numéro de châssis - ancien
|
No
|
-
|
-
|
Option.
|
ObjectInsuredTractorVehicle CheckDigitOnTheChassisNumberReference
|
|
| 460 |
Véhicule - Numéro PVA
|
No
|
-
|
-
|
Option.
|
PvaReference
|
||
| 470 |
Véhicule - Numéro de PVA européen
|
No
|
-
|
-
|
Option.
|
EuropeanConformityCertificateReference
|
||
| 480 |
Véhicule - Code DIV ( marque - modèle )
|
No
|
-
|
-
|
Option.
|
AdrUnNumberReference
|
||
| 490 |
Véhicule - WVTA-code - WVTA-variante (25 positions dixit Veridass)
|
No
|
-
|
-
|
Option.
|
WvtaCodeVariantReference
|
||
| 500 |
Véhicule - WVTA-code - WVTA-version (35 positions dixit Veridass)
|
No
|
-
|
-
|
Option.
|
WvtaCodeVersionReference
|
||
| 510 |
Véhicule - Catégorie de véhicule
|
Yes
|
2
|
Option.
|
VehicleCategoryCode
|
|||
| 520 |
Véhicule - Type de véhicule
|
Yes
|
6
|
Option.
|
VehicleCode
|
|||
| 530 |
Véhicule - Véhicule fait partie d'une flotte
|
No
|
-
|
-
|
Mand.
|
VehicleBelongingToAFleetBinary
|
||
| 540 |
Véhicule - Cylindrée (en cc - cm3)
|
No
|
-
|
-
|
Option.
|
EngineCapacityQuantity
|
||
| 550 |
Véhicule - Puissance (en kW)
|
No
|
-
|
-
|
Option.
|
PowerQuantity
|
||
| 560 |
Véhicule - Description du véhicule
|
No
|
-
|
-
|
Option.
|
VehicleDescriptionText
|
||
| 570 |
Véhicule - WVTA-code - WVTA-numéro (40 positions dixit Veridass)
|
No
|
-
|
-
|
Option.
|
WvtaCodeNumberText
|
||
| 580 |
Véhicule - Garantie RC
|
No
|
-
|
-
|
Mand.
|
GuaranteeCLMotor
|
||
| 590 |
Véhicule - Garantie RC - Date de début
|
No
|
-
|
-
|
Option.
|
PeriodStartDate
|
||
| 600 |
Véhicule - Garantie RC - Date de fin
|
No
|
-
|
-
|
Option.
|
PeriodEndDate
|
||
| 610 |
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.