SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 200601 : Identifier : ICD1xx - - (Données spécifiques des garanties Vie) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 3 - 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 |
||||||
| 4 |
Garantie, type
|
No
|
-
|
-
|
Mand.
|
Guarantee...
|
||
| 5 |
Date prestation du capital vie
|
No
|
-
|
-
|
Option.
|
LifeBenefitPaymentDate
|
||
| 10 |
Date dernière péréquation
|
No
|
-
|
-
|
Option.
|
LastEqualizationDate
|
||
| 15 |
Type de solde restant dû
|
Yes
|
1
|
Option.
|
DebtBalanceCode
|
|||
| 20 |
Régime d'imposition de la prestation
|
Yes
|
1
|
Option.
|
PerformanceTaxabilityCode
|
|||
| 25 |
Contrat génère des participations bénéficiaires
|
No
|
-
|
-
|
Option.
|
ContractGeneratesProfitsharingBinary
|
||
| 30 |
Contrat assujetti à péréquation
|
No
|
-
|
-
|
Option.
|
ContractSubjectToEqualizationBinary
|
||
| 35 |
Imposition de la prestation
|
No
|
-
|
-
|
Option.
|
PerformanceTaxationLiabilityBinary
|
||
| 40 |
Capital vie
|
No
|
-
|
-
|
Option.
|
LifeBenefitAmount
|
||
| 45 |
Capital décès
|
No
|
-
|
-
|
Option.
|
DeathBenefitAmount
|
||
| 50 |
Participation bénéficiaire acquise vie
|
No
|
-
|
-
|
Option.
|
AcquiredBonusLoadingForLifeAmount
|
||
| 55 |
Participation acquise décès
|
No
|
-
|
-
|
Option.
|
AcquiredBonusLoadingForDeathAmount
|
||
| 60 |
Coëfficient multiplicateur ACRA
|
No
|
-
|
-
|
Option.
|
AIARMultiplicatorQuantity
|
||
| 65 |
Taux d'intérêt solde restant dû
|
No
|
-
|
-
|
Option.
|
RateOnRemainingBalanceDuedPercentage
|
||
| 69 |
Bénéficiaire
|
No
|
-
|
-
|
Option.
|
PartyBeneficiary
|
||
| 70 |
Bénéficiaire - Nom officiel
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
| 75 |
Bénéficiaire - Type de bénéficiaire standard
|
Yes
|
1
|
Option.
|
StandardBeneficiaryCode
|
|||
| 80 |
Bénéficiaire - Type de bénéficiaire acceptant
|
Yes
|
1
|
Option.
|
AcceptingBeneficiaryCode
|
|||
| 85 |
Bénéficiaire - Bénéficiaire a accepté l'avantage du contrat
|
No
|
-
|
-
|
Option.
|
BeneficiaryAcceptedTheContractualBenefitBinary
|
||
| 89 |
Cessionnaire
|
No
|
-
|
-
|
Option.
|
PartyCessionary
|
||
| 90 |
Cessionnaire - Nom officiel
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
| 95 |
Cessionnaire - Numéro du dossier
|
No
|
-
|
-
|
Option.
|
FileReference
|
||
| 100 |
Cessionnaire - Description
|
No
|
-
|
-
|
Option.
|
DescriptionText
|
||
| 110 |
Sous-garanties
|
No
|
-
|
-
|
Option.
|
SubGuarantee...
|
||
(*) 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.