SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Under construction : Identifier : M0601 - Récapitulation, péréquation / Samenvatting, perequatie - (Péréquations, totaux de contrôle, première version / Perequaties, controle-totalen, eerste versie) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 0 - Version : 1
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 | n |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
|
| 20 |
Numéro du producteur dans la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 30 |
Nombre de polices impliquées par l'adaptation
|
No
|
-
|
-
|
Mand.
|
PoliciesQuantity
|
||
| 40 |
Totaux des capitaux vie - indexés
|
No
|
-
|
-
|
Mand.
|
LifeBenefitAmount
|
||
| 50 |
Totaux des augmentations des capitaux vie
|
No
|
-
|
-
|
Mand.
|
ChangeInLifeBenefitAmount
|
||
| 60 |
Totaux des capitaux décès - indexés
|
No
|
-
|
-
|
Mand.
|
DeathBenefitAmount
|
||
| 70 |
Totaux des augmentations des capitaux décès
|
No
|
-
|
-
|
Mand.
|
ChangeInDeathBenefitAmount
|
||
| 80 |
Totaux des nouvelles primes - impôts non compris
|
No
|
-
|
-
|
Mand.
|
NetPremiumAmount
|
||
| 90 |
Totaux des augmentations des primes - impôts non compris
|
No
|
-
|
-
|
Mand.
|
IncreaseOfPremiumAmount
|
||
| 100 |
Totaux des commissions d'acquisition supplémentaires (suite à l'adaptation)
|
No
|
-
|
-
|
Mand.
|
SupplementaryAcquisitionCommissionAmount
|
||
(*) 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.