Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Archived, and was part of release 200601 : Identifier : ROD05x - - (Données groupe/personne (activité exercée) / Gegevens persoon/groep (uitgeoefende activiteit)) |
Sender :
Receiver :
Status : 3 - 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 |
|||||||
| 5 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ROD+05x
|
ObjectInsured...
|
||
| 10 |
Nom officiel - Nom de famille
|
No
|
-
|
-
|
Option.
|
NME+001
|
OfficialName
|
||
| 15 |
Nom officiel - Premier prénom
|
No
|
-
|
-
|
Option.
|
NME+001
|
OfficialName
|
||
| 20 |
Nom officiel - Deuxième prénom
|
No
|
-
|
-
|
Option.
|
NME+001
|
OfficialName
|
||
| 25 |
Nom officiel - Troisième prénom
|
No
|
-
|
-
|
Option.
|
NME+001
|
OfficialName
|
||
| 30 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
NME+001
|
OfficialName
|
||
| 35 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
ADR+002
|
AddressDetail StreetName
|
||
| 40 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
ADR+002
|
AddressDetail HouseNumber
|
||
| 45 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
ADR+002
|
AddressDetail BoxNumber
|
||
| 50 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
ADR+002
|
AddressDetail AddressExtension
|
||
| 55 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
ADR+002
|
AddressDetail AddressIdentifier
|
||
| 60 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
ADR+002
|
PostalCode
|
||
| 65 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
ADR+002
|
CityName
|
||
| 70 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
ADR+002
|
CountryCoded
|
||
| 75 |
Numéro d'entreprise
|
No
|
-
|
-
|
Option.
|
RFF+075
|
CompanyNumberReference
|
||
| 80 |
Numéro d'unité d'entreprise
|
No
|
-
|
-
|
Option.
|
RFF+076
|
EstablishmentUnitNumberReference
|
||
| 85 |
Code commerce (NACEBEL)
|
Yes
|
1
|
Option.
|
ATT+3104
|
BusinessCodeNacebelCode
|
|||
| 90 |
Nombre d’assurés dans le groupe
|
No
|
-
|
-
|
Option.
|
QTY+130
|
InsuredWithinTheGroupQuantity
|
||
| 95 |
Description
|
No
|
-
|
-
|
Option.
|
FTX+019
|
DescriptionText
|
||
| 100 |
Garantie
|
No
|
-
|
-
|
Mand.
|
ICD+xxx
|
Guarantee...
|
||
| 110 |
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
SRO+xxx
|
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.