Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Archived, and was part of release 200901 : Identifier : M0115 - Contrat, participation bénéficiare - (Participations bénéficiaires, première version) |
Sender : Insurer
Receiver : Broker
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 |
|||||||
| 10 | n |
Message issuing date and time
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0115+++domain++++yyyymmddhhmm+xx' (=X916 and =X918) (domain is mandatory)
|
ExchangeUnitIssueDateTime
|
|
| 11 | n |
Message content inventory identifier
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0115+++domain++++yyyymmddhhmm+xx:::M0115' (=X943)
|
ExchangeUnitBusinessContentDescription
|
|
| 12 | n |
Message content inventory version
|
No
|
-
|
-
|
Mand.
|
XEH+01+2+0115+++domain++++yyyymmddhhmm+xx:::M0115:1' (=X944)
|
ExchangeUnitBusinessContentDescriptionVersion
|
|
| 20 |
Numéro de police
|
No
|
-
|
-
|
Mand.
|
RFF+001:x--x
|
PolicyReference
|
||
| 25 | n |
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.
|
RFF+084 (NEW)
|
MessageGuidReference
|
| 26 | n |
Nombre de documents annexes
|
No
|
-
|
-
|
Cond.
|
Mandatory when added documents are sent.
|
QTY+134 (NEW)
|
DocumentsAttachedQuantity
|
| 30 |
Numéro du producteur dans la compagnie
|
No
|
-
|
-
|
Mand.
|
PTY+002+X044:2
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 40 |
Référence police producteur
|
No
|
-
|
-
|
Option.
|
PTY+002 - RFF+003:x--x
|
BrokerPolicyReference
|
||
| 50 |
Nom du produit à la compagnie
|
No
|
-
|
-
|
Option.
|
IPD+A532
|
ProductNameProductcode
|
||
| 60 |
Date d'effet de l'adaptation
|
No
|
-
|
-
|
Mand.
|
DTM+008:jjmmaass:001
|
InceptionDate
|
||
| 70 |
Nom du preneur d'assurance
|
No
|
-
|
-
|
Mand.
|
PTY+003 - NME+001:last:first:first2:first3:extension
|
OfficialName NameDetail LastName FirstName NameExtension
|
||
| 80 |
Taux de participation bénéficiaire de l'année
|
No
|
-
|
-
|
Mand.
|
PCD+030:9--9:decimals
|
RateOfBonusLoadingInCaseOfLifePercentage
|
||
| 90 |
Capital vie - indexé mais sans PB
|
No
|
-
|
-
|
Option.
|
ROD : 0..n presencies - ICD : 0..n presencies
|
ROD+... - ICD+... - MOA+023:9--9:EUR:2:001 +indexID:value:decimals
|
LifeBenefitAmount
|
|
| 100 |
Participation bénéficiaire vie de l'année
|
No
|
-
|
-
|
Option.
|
ROD+... - ICD+... - MOA+025:9--9:EUR:2:001
|
YearlyAmountOfBonusLoadingForLifeAmount
|
||
| 110 |
Participation bénéficiaire vie cumulée
|
No
|
-
|
-
|
Option.
|
ROD+... - ICD+... - MOA+024:9--9:EUR:2:001
|
AcquiredBonusLoadingForLifeAmount
|
||
| 120 |
Capital décès - indexé mais sans PB
|
No
|
-
|
-
|
Option.
|
ROD+... - ICD+... - MOA+026:9--9:EUR:2:001 +indexID:value:decimals
|
DeathBenefitAmount
|
||
| 130 |
Participation bénéficiaire décès de l'année
|
No
|
-
|
-
|
Option.
|
ROD+... - ICD+... - MOA+028:9--9:EUR:2:001
|
YearlyAmountOfBonusLoadingForDeathAmount
|
||
| 140 |
Participation bénéficiaire décès cumulée
|
No
|
-
|
-
|
Option.
|
ROD+... - ICD+... - MOA+027:9--9:EUR:2:001
|
AcquiredBonusLoadingForDeathAmount
|
||
| 150 |
Valeur de rachat du contrat à la fin de l'année précédente
|
No
|
-
|
-
|
Mand.
|
MOA+089:9--9:EUR:2:001
|
SurrenderValueOfContractAtEndOfLastYearAmount
|
||
(*) 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.