SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EROD149 - Echange contextuel, données prêt - (Données prêt)
- Approved
, and is part of release 201401 |
Sender : Any
Receiver : Any
Status : 2 - 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 |
Contrat
|
No
|
-
|
-
|
Mand.
|
XEH+01+2
|
|||
| 20 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ROD+149
|
ObjectInsuredLoan
|
||
| 30 |
Durée
|
No
|
-
|
-
|
Option.
|
ROD+149 - DTM+006
|
LengthDuration
|
||
| 40 |
Durée fixité initiale du prêt
|
No
|
-
|
-
|
Option.
|
ROD+149 - DTM+144
|
InitialLoanFirmnessDuration
|
||
| 50 |
Indice de référence hypothécaire, mois
|
No
|
-
|
-
|
Option.
|
ROD+149 - DTM+155:mmaaaa:005
|
MortgageReferenceIndexYearMonth
|
||
| 60 |
Durée période de prélèvement en mois
|
No
|
-
|
-
|
Option.
|
ROD+149 - DTM+156:x--x:103
|
DebtSumCollectionDurationMonths
|
||
| 70 |
Type de prêt
|
Yes
|
1
|
Option.
|
ROD+149 - ATT+0200
|
LoanCode
|
|||
| 80 |
Type de révision prêt
|
Yes
|
1
|
Option.
|
ROD+149 - ATT+0210
|
LoanReviewCode
|
|||
| 90 |
Type d'acte hypothécaire
|
Yes
|
1
|
Option.
|
ROD+149 - ATT+0220
|
MortgageDeedCode
|
|||
| 100 |
Rang hypothécaire
|
Yes
|
1
|
Option.
|
ROD+149 - ATT+0221
|
MortgageOrderCode
|
|||
| 110 |
Type de remboursement
|
Yes
|
2
|
Option.
|
ROD+149 - ATT+0300
|
LoanRepaymentCode
|
|||
| 120 |
Indice de référence hypothécaire, type
|
Yes
|
1
|
Option.
|
ROD+149 - ATT+0410+x--x
|
MortgageReferenceIndexCode
|
|||
| 130 |
Indice de référence hypothécaire, périodicité
|
Yes
|
1
|
Option.
|
ROD+149 - ATT+0420+x--x
|
MortgageReferenceIndexPeriodicityCode
|
|||
| 140 |
Montant emprunté
|
No
|
-
|
-
|
Option.
|
ROD+149 - MOA+174
|
AmountBorrowedAmount
|
||
| 150 |
Solde restant dû
|
No
|
-
|
-
|
Option.
|
ROD+149 - MOA+022
|
RemainingBalanceOverdueAmount
|
||
| 160 |
Nombre de prélèvements maximal
|
No
|
-
|
-
|
Option.
|
ROD+149 - QTY+150:x--x
|
MaximumWithdrawalsQuantity
|
||
| 170 |
Nombre de prélèvements atteint
|
No
|
-
|
-
|
Option.
|
ROD+149 - QTY+151:x--x
|
WithdrawalsDoneQuantity
|
||
| 180 |
Taux d'intérêt lors de l'octroi du prêt
|
No
|
-
|
-
|
Option.
|
ROD+149 - PCD+051
|
InterestRateAsOnLoanApprovalPercentage
|
||
| 190 |
Pourcentage Cap +
|
No
|
-
|
-
|
Option.
|
ROD+149 - PCD+052
|
PercentageCapPlusPercentage
|
||
| 200 |
Pourcentage Cap -
|
No
|
-
|
-
|
Option.
|
ROD+149 - PCD+053
|
PercentageCapMinusPercentage
|
||
| 210 |
Obligation à long terme de départ
|
No
|
-
|
-
|
Option.
|
ROD+149 - PCD+054
|
InitialLongTermCommitmentPercentage
|
||
| 220 |
Quotité du montant emprunté
|
No
|
-
|
-
|
Option.
|
ROD+149 - PCD+055
|
LoanAmountQuotientPercentage
|
||
| 230 |
Indice de référence hypothécaire
|
No
|
-
|
-
|
Option.
|
ROD+149 - PCD+061:x--x:y
|
MortgageReferenceIndexPercentage
|
||
| 240 |
Description du type de prêt
|
No
|
-
|
-
|
Option.
|
ROD+149 - FTX+043+x--x:x--x:x--x:x--x:x--x
|
LoanTypeDescriptionText
|
||
(*) 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.