> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 201201 :
Identifier : ROD05x - - (Données groupe/personne (activité exercée) / Gegevens persoon/groep (uitgeoefende activiteit)) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 3 - 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
5  
Riskobject, type
No
-
-
Mand.
 
ObjectInsured... 
10 n 
Adresse optimisée sur base de
Yes
1
Option.
info: a better alternative is to use X099 in segment ADR 
AddressOptimisedBasedUponProcesscode 
20  
Nom officiel - Nom de famille
No
-
-
Option.
 
OfficialName NameDetail LastName 
30  
Nom officiel - Premier prénom
No
-
-
Option.
 
OfficialName NameDetail FirstName 
40  
Nom officiel - Deuxième prénom
No
-
-
Option.
 
OfficialName NameDetail FirstName 
50  
Nom officiel - Troisième prénom
No
-
-
Option.
 
OfficialName NameDetail FirstName 
60  
Nom officiel - Extension du nom
No
-
-
Option.
 
OfficialName NameDetail NameExtension 
70  
Adresse - rue
No
-
-
Option.
 
OfficialAddress AddressDetail StreetName 
80  
Adresse - numéro de maison
No
-
-
Option.
 
OfficialAddress AddressDetail HouseNumber 
90  
Adresse - numéro de boîte
No
-
-
Option.
 
OfficialAddress AddressDetail BoxNumber 
100  
Adresse - extension
No
-
-
Option.
 
OfficialAddress AddressDetail AddressExtension 
110  
Adresse - identifiant
No
-
-
Option.
 
OfficialAddress AddressDetail AddressIdentifier 
120 n 
Adresse - Adresse optimisée suivant fournisseur, code
No
-
-
Option.
 
OfficialAddress 
130  
Adresse - code postal
No
-
-
Option.
 
OfficialAddress PostalCode 
140  
Adresse - localité
No
-
-
Option.
 
OfficialAddress CityName 
150  
Adresse - code pays
No
-
-
Option.
 
OfficialAddress CountryCoded 
160  
Numéro d'entreprise
No
-
-
Option.
 
CompanyNumberReference 
170  
Numéro d'unité d'entreprise
No
-
-
Option.
 
EstablishmentUnitNumberReference 
180 u 
Code commerce (NACEBEL)
Yes
1
Cond.
UNTIL 31/12/2009 
BusinessCodeNacebelCode 
190 n 
Code commerce (NACE-BEL 2008)
Yes
1
Cond.
STARTING 01/01/2010 
BusinessCodeNacebel2008Code 
200  
Nombre d’assurés dans le groupe
No
-
-
Option.
 
InsuredWithinTheGroupQuantity 
210  
Description
No
-
-
Option.
 
DescriptionText 
220  
Garantie
No
-
-
Mand.
1..n presencies 
Guarantee... 
230  
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.