> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 200601 :
Identifier : PTY003GRP - - (Données preneur d'assurance - Groupement de personnes / Gegevens verzekeringsnemer - Groepering van personen)
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
4  
Party, type
No
-
-
Mand.
 
PTY+003 
PartyMainPolicyHolder 
5  
Nom officiel - Nom
No
-
-
Mand.
 
NME+001 
OfficialName 
9  
Nom officiel - Extension du nom
No
-
-
Option.
 
NME+001 
OfficialName 
10  
Code titre
Yes
0
Option.
 
NME+001 
OfficialName 
20  
Adresse - rue
No
-
-
Mand.
 
ADR+002 
AddressDetail StreetName 
21  
Adresse - numéro de maison
No
-
-
Mand.
 
ADR+002 
AddressDetail HouseNumber 
22  
Adresse - numéro de boîte
No
-
-
Option.
 
ADR+002 
AddressDetail BoxNumber 
23  
Adresse - extension
No
-
-
Option.
 
ADR+002 
AddressDetail AddressExtension 
24  
Adresse - identifiant
No
-
-
Option.
 
ADR+002 
AddressDetail AddressIdentifier 
25  
Adresse - code postal
No
-
-
Mand.
 
ADR+002 
PostalCode 
26  
Adresse - localité
No
-
-
Option.
 
ADR+002 
CityName 
27  
Adresse - code pays
No
-
-
Option.
 
ADR+002 
CountryCoded 
55  
Numéro du compte financier
No
-
-
Option.
 
RFF+020 
AccountReference 
60  
Numéro IBAN
No
-
-
Option.
 
RFF+077 
InternationalBankAccountNumberReference 
75  
Numéro de téléphone privé
No
-
-
Option.
 
COM+001 
PrivateTelephoneCommID 
80  
Numéro de fax
No
-
-
Option.
 
COM+002 
FaxCommID 
85  
Adresse boîte postale électronique
No
-
-
Option.
 
COM+003 
EmailAddressCommID 
95  
Personne physique ou morale
Yes
2
Mand.
 
ATT+A131 
NaturalOrLegalPersonCode 
105  
Langue de communication
Yes
3
Mand.
 
ATT+A10C 
LanguageCode 
110  
Nationalité
Yes
6
Option.
 
ATT+A121 
NationalityCode 
125  
Statut juridique
Yes
4
Option.
 
ATT+A130 
LegalFormCode 
130  
Statut social
Yes
5
Option.
 
ATT+A132 
SocialStatusCode 
135  
Code commerce (NACEBEL)
Yes
1
Option.
 
ATT+3104 
BusinessCodeNacebelCode 
150  
Instructions en cours
No
-
-
Option.
 
QRS+5V0E 
DeclarationInvestigationPending ResponseCoded 
165  
Assurance refusée, résiliée ou prolongée sous conditions
No
-
-
Option.
 
QRS+5V0S 
DeclarationInsuranceRefusedOrEndedOrExtendedUnderCircumstances ResponseCoded 
175  
Assurance refusée, résiliée ou prolongée sous conditions - Type de difficulté
Yes
1
Option.
 
RDT+A1D0 
ResponseTypeOfDifficulty ResponseDetail ResponseDetailValueCoded 

(*) 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.