SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release : Identifier : M0116 - Contrat, péréquation - (Péréquations, message intégré dans Contrat, mise à jour portefeuille vie) - (UN/Edifact & XML/JSON : added info ) |
Sender : Insurer
Receiver : Broker
Status : 3 - Version : 3
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitIssueDateTime
|
||
| 20 |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescription
|
||
| 30 | u |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 40 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
PolicyReference
|
||
| 50 |
GUID (Globally Unique IDentifier) du message, sera référencé par le(s) document(s) annexe(s)
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
MessageGuidReference
|
|
| 60 |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
DocumentsAttachedQuantity
|
|
| 70 |
Numéro du producteur dans la compagnie
|
No
|
-
|
-
|
Mand.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 80 |
Référence police producteur
|
No
|
-
|
-
|
Option.
|
BrokerPolicyReference
|
||
| 90 |
Nom du produit à la compagnie
|
No
|
-
|
-
|
Option.
|
ProductNameProductcode
|
||
| 100 |
Date d'effet de l'adaptation
|
No
|
-
|
-
|
Mand.
|
InceptionDate
|
||
| 110 |
Nom du preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName NameExtension
|
||
| 120 |
Commission d'acquisition supplémentaire suite à l'adaptation
|
No
|
-
|
-
|
Mand.
|
SupplementaryAcquisitionCommissionAmount
|
||
| 130 |
Code mouvement : indexation ou refus d'indexation
|
Yes
|
1
|
Mand.
|
CurrentAccountLineFollowingRedistributionProcesscode
|
|||
| 140 |
Péréquations par garantie ...
|
No
|
-
|
-
|
Mand.
|
ROD : 1..n presencies - ICD : 1..n presencies
|
(Sub)Guarantee...
|
|
| 150 |
Garantie - Nouveau capital
|
No
|
-
|
-
|
Cond.
|
This (A) one or the 2 (B) next ones.
|
CapitalAmount
|
|
| 160 |
Garantie - Nouveau capital vie
|
No
|
-
|
-
|
Cond.
|
This (B) or the (A) previous one.
|
LifeBenefitAmount
|
|
| 170 |
Garantie - Nouveau capital décès
|
No
|
-
|
-
|
Cond.
|
This (B) or the (A) previous one.
|
DeathBenefitAmount
|
|
| 180 |
Garantie - Augmentation du capital
|
No
|
-
|
-
|
Cond.
|
This (A) one or the 2 (B) next ones.
|
ChangeOfCapitalAmount
|
|
| 190 |
Garantie - Augmentation du capital vie
|
No
|
-
|
-
|
Cond.
|
This (B) or the (A) previous one.
|
ChangeInLifeBenefitAmount
|
|
| 200 |
Garantie - Augmentation du capital décès
|
No
|
-
|
-
|
Cond.
|
This (B) or the (A) previous one.
|
ChangeInDeathBenefitAmount
|
|
| 210 |
Garantie - Nouvelle prime
|
No
|
-
|
-
|
Mand.
|
NetPremiumAmount
|
||
| 220 |
Garantie - Augmentation de prime
|
No
|
-
|
-
|
Mand.
|
IncreaseOfPremiumAmount
|
||
(*) 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.