SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201401 : Identifier : EROD04x - Echange contextuel, données groupe de personnes - (Données groupe de personnes) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 3 - Version : 1
|
| 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
|
No
|
-
|
-
|
Mand.
|
|||
| 20 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ObjectInsured...
|
||
| 30 |
Adresse optimisée sur base de
|
Yes
|
1
|
Option.
|
info: a better alternative is to use X099 in segment ADR
|
AddressOptimisedBasedUponProcesscode
|
||
| 40 |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail LastName
|
||
| 50 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail NameExtension
|
||
| 60 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail StreetName
|
||
| 70 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail HouseNumber
|
||
| 80 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail BoxNumber
|
||
| 90 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressExtension
|
||
| 100 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressIdentifier
|
||
| 110 |
Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
OfficialAddress
|
||
| 120 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
OfficialAddress PostalCode
|
||
| 130 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
OfficialAddress CityName
|
||
| 140 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryCoded
|
||
| 150 |
Numéro plaque d'immatriculation
|
No
|
-
|
-
|
Option.
|
RegistrationPlateReference
|
||
| 160 |
Code commerce (NACEBEL)
|
Yes
|
1
|
Cond.
|
UNTIL 31/12/2009
|
BusinessCodeNacebelCode
|
||
| 170 |
Code commerce (NACE-BEL 2008)
|
Yes
|
1
|
Cond.
|
STARTING 01/01/2010
|
BusinessCodeNacebel2008Code
|
||
| 180 |
Ouvriers - classe de risque
|
Yes
|
1
|
Cond.
|
in ROD+041 and there mandatory if multiple ROD+041 co-exist
|
WorkersRiskClassCode
|
||
| 190 |
Employées - classe de risque
|
Yes
|
1
|
Cond.
|
in ROD+042 and there mandatory if multiple ROD+042 co-exist
|
EmployedRiskClassCode
|
||
| 200 |
Non assujettis (A.T. - dmfa)
|
No
|
-
|
-
|
Cond.
|
if needed in worker's compensation premium settlement
|
NonSubmittedToWorkersCompensationBinary
|
|
| 210 |
Masse salariale limité au plafond légal
|
No
|
-
|
-
|
Option.
|
TotalSalaryUptoLegalMaximumAmount
|
||
| 220 |
Masse salariale excédent le plafond légal
|
No
|
-
|
-
|
Option.
|
TotalSalaryExcedingLegalMaximumAmount
|
||
| 230 |
Nombre d’assurés dans le groupe
|
No
|
-
|
-
|
Option.
|
InsuredWithinTheGroupQuantity
|
||
| 240 |
Nombre de salariés
|
No
|
-
|
-
|
Option.
|
EmployeesQuantity
|
||
| 250 |
Superficie
|
No
|
-
|
-
|
Option.
|
SurfaceAreaQuantity
|
||
| 260 |
Nombre de véhicules
|
No
|
-
|
-
|
Option.
|
VehiclesQuantity
|
||
| 270 |
Nombre de biens en location
|
No
|
-
|
-
|
Option.
|
GoodsRentedQuantity
|
||
| 280 |
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
0..n presencies
|
Subobject...
|
|
(*) 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.