Message Content Inventory |
Archived, and was part of release 201501 : Identifier : EROD05x - Echange contextuel, données groupe/personne (activité exercée) - (Données groupe/personne (activité exercée)) |
Sender : Any
Receiver : Any
Status : 3 - Version : 2
|
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 |
Contrat
|
No
|
-
|
-
|
Mand.
|
XEH+01+2
|
|||
20 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ROD+05x
|
ObjectInsured...
|
||
30 |
Adresse optimisée sur base de
|
Yes
|
1
|
Option.
|
info: a better alternative is to use X099 in segment ADR
|
ROD+05x - GIS+A09Y+x--x
|
AddressOptimisedBasedUponProcesscode
|
||
40 |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Option.
|
ROD+05x - NME+001+x--x
|
OfficialName NameDetail LastName
|
||
50 |
Nom officiel - Premier prénom
|
No
|
-
|
-
|
Option.
|
ROD+05x - NME+001+:x--x
|
OfficialName NameDetail FirstName
|
||
60 |
Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
ROD+05x - NME+001+::x--x
|
OfficialName NameDetail FirstName
|
||
70 |
Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
ROD+05x - NME+001+:::x--x
|
OfficialName NameDetail FirstName
|
||
80 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
ROD+05x - NME+001+::::x--x
|
OfficialName NameDetail NameExtension
|
||
90 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002+x--x
|
OfficialAddress AddressDetail StreetName
|
||
100 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002+:x--x
|
OfficialAddress AddressDetail HouseNumber
|
||
110 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002+::x--x
|
OfficialAddress AddressDetail BoxNumber
|
||
120 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002+::::x--x
|
OfficialAddress AddressDetail AddressExtension
|
||
130 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002+:::::x--x
|
OfficialAddress AddressDetail AddressIdentifier
|
||
140 |
Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002+:::::x--x:x--x
|
OfficialAddress
|
||
150 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002++x--x
|
OfficialAddress PostalCode
|
||
160 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002+++x--x
|
OfficialAddress CityName
|
||
170 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
ROD+05x - ADR+002++++x--x
|
OfficialAddress CountryCoded
|
||
180 |
Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
ROD+05x - RFF+075:x--x
|
CompanyNumberReference
|
||
190 |
Numéro d'unité d'entreprise
|
No
|
-
|
-
|
Option.
|
ROD+05x - RFF+076:x--x
|
EstablishmentUnitNumberReference
|
||
200 | u |
Code commerce (NACEBEL)
|
Yes
|
1
|
Cond.
|
UNTIL 31/12/2009 - Multiple presencies possible
|
ROD+05x - ATT+3104+x--x:x--x:x--x:x--x
|
BusinessCodeNacebelCode
|
|
210 | u |
Code commerce (NACE-BEL 2008)
|
Yes
|
1
|
Cond.
|
STARTING 01/01/2010 - Multiple presencies possible
|
ROD+05x - ATT+3105+x--x:x--x:x--x:x--x
|
BusinessCodeNacebel2008Code
|
|
220 |
Nombre d’assurés dans le groupe
|
No
|
-
|
-
|
Option.
|
ROD+05x - QTY+130:x--x:x--x
|
InsuredWithinTheGroupQuantity
|
||
230 |
Description
|
No
|
-
|
-
|
Option.
|
ROD+05x - FTX+019+x--x:x--x:x--x:x--x:x--x
|
DescriptionText
|
||
240 |
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
0..n presencies
|
ROD+05x - SRO+xxx (segment group, multiple occurrencies)
|
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.