> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201201 : Identifier : PTY003GRP - - (Données preneur d'assurance - Groupement de personnes / Gegevens verzekeringsnemer - Groepering van personen)- - ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info ) |
Sender :
Receiver :
Status : 3 - Version : 5
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
||
Indicator |
Identifier |
Version |
|||||
| 5 |
Party, type
|
No
|
-
|
-
|
Mand.
|
||
| 10 |
Adresse optimisée sur base de
|
Yes
|
1
|
Option.
|
info: a better alternative is to use X099 in segment ADR
|
||
| 20 |
Nom officiel - Nom
|
No
|
-
|
-
|
Mand.
|
||
| 30 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
||
| 40 |
Code titre
|
Yes
|
0
|
Option.
|
|||
| 50 |
Adresse - rue
|
No
|
-
|
-
|
Mand.
|
||
| 60 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Mand.
|
||
| 70 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
||
| 80 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
||
| 90 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
||
| 100 | n |
Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
|
| 110 |
Adresse - code postal
|
No
|
-
|
-
|
Mand.
|
||
| 120 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
||
| 130 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
||
| 140 |
Numéro du compte financier
|
No
|
-
|
-
|
Option.
|
||
| 150 |
Code BIC
|
No
|
-
|
-
|
Option.
|
||
| 160 |
Numéro IBAN
|
No
|
-
|
-
|
Option.
|
||
| 170 |
Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
||
| 180 |
Numéro de fax
|
No
|
-
|
-
|
Option.
|
||
| 190 |
Adresse boîte postale électronique
|
No
|
-
|
-
|
Option.
|
||
| 200 |
Personne physique ou morale
|
Yes
|
2
|
Mand.
|
|||
| 210 |
Langue de communication
|
Yes
|
3
|
Mand.
|
|||
| 220 |
Nationalité
|
Yes
|
7
|
Option.
|
|||
| 230 | u |
Statut juridique
|
Yes
|
8
|
Option.
|
||
| 240 |
Statut social
|
Yes
|
5
|
Option.
|
|||
| 250 | u |
Code commerce (NACEBEL)
|
Yes
|
1
|
Cond.
|
UNTIL 31/12/2009
|
|
| 251 | n |
Code commerce (NACE-BEL 2008)
|
Yes
|
1
|
Cond.
|
STARTING 01/01/2010
|
|
| 260 |
Instructions en cours
|
No
|
-
|
-
|
Option.
|
||
| 270 |
Assurance refusée, résiliée ou prolongée sous conditions
|
No
|
-
|
-
|
Option.
|
||
| 280 |
Assurance refusée, résiliée ou prolongée sous conditions - Type de difficulté
|
Yes
|
1
|
Option.
|
|||
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) 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.