SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201301 : Identifier : ICDGEN - - (Données communes garanties) |
Sender :
Receiver :
Status : 3 - Version : 7
|
| 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 | u |
Garantie, type
|
No
|
-
|
-
|
Mand.
|
Generic- possbly completed with one of (ICD1xx.v5 / ICD2xx.v1 / ICD3xx.v3 / ICD5xx.v3 / ICD6xx.v2)
|
ICD+xxx
|
Guarantee...
|
| 20 |
Formule - identifiant
|
No
|
-
|
-
|
Option.
|
IFD+xxx
|
Formula FormulaDetail FormulaQualifier
|
||
| 30 |
Formule - numéro CBFA
|
No
|
-
|
-
|
Option.
|
IFD+xxx:(X901):x--x
|
Formula FormulaDetail FormulaQualifier CodeListIdentifier CodeListResponsibleAgencyCoded FormulaName
|
||
| 40 |
Formule - nom
|
No
|
-
|
-
|
Option.
|
IFD+xxx:::x--x
|
Formula FormulaDetail FormulaQualifier FormulaName
|
||
| 50 |
Date d'effet
|
No
|
-
|
-
|
Option.
|
DTM+008:x--x:001
|
InceptionDate
|
||
| 60 |
Date d'expiration
|
No
|
-
|
-
|
Option.
|
DTM+138:x--x:001
|
ExpiryDate
|
||
| 70 |
Date première commission
|
No
|
-
|
-
|
Option.
|
DTM+023:x--x:001
|
FirstCommissionDate
|
||
| 80 |
Date dernière commission
|
No
|
-
|
-
|
Option.
|
DTM+024:x--x:001
|
LastCommissionDate
|
||
| 100 |
Réponse action commerciale
|
No
|
-
|
-
|
Option.
|
BIN+A537+x--x
|
ResponseToCommercialActionBinary
|
||
| 110 |
Présence d'une franchise
|
No
|
-
|
-
|
Option.
|
BIN+3419+x--x
|
ExemptionPresentBinary
|
||
| 120 |
Capital
|
No
|
-
|
-
|
Option.
|
MOA+004:x--x:EUR:2:(status) +(index):x--x:(decimals)
|
CapitalAmount
|
||
| 130 | n |
Augmentation du capital
|
No
|
-
|
-
|
Option.
|
MOA+091:x--x:EUR:2:(status) +(index):x--x:(decimals)
|
ChangeOfCapitalAmount
|
|
| 140 |
Coûts techniques
|
No
|
-
|
-
|
Option.
|
MOA+167:x--x:EUR:2:(status)
|
TechnicalExpensesAmount
|
||
| 150 |
Frais de commercialisation
|
No
|
-
|
-
|
Option.
|
MOA+163:x--x:EUR:2:(status)
|
CommercializationExpensesMotorLiabilityAmount
|
||
| 160 |
Montant Commission
|
No
|
-
|
-
|
Option.
|
MOA+015:x--x:EUR:2:(status)
|
CommissionAmount
|
||
| 170 |
Montant Charges
|
No
|
-
|
-
|
Option.
|
MOA+016:x--x:EUR:2:(status)
|
ChargesAmount
|
||
| 180 |
Montant Frais
|
No
|
-
|
-
|
Option.
|
MOA+017:x--x:EUR:2:(status)
|
CostAmount
|
||
| 190 |
Montant Charges et frais
|
No
|
-
|
-
|
Option.
|
MOA+018:x--x:EUR:2:(status)
|
ChargesAndCostsAmount
|
||
| 200 |
Prime nette
|
No
|
-
|
-
|
Mand.
|
MOA+005:x--x:EUR:2:(status)
|
NetPremiumAmount
|
||
| 210 |
Frais de fractionnement
|
No
|
-
|
-
|
Option.
|
MOA+039:x--x:EUR:2:(status)
|
SplittingCostsAmount
|
||
| 220 |
Autres coûts à ajouter à la prime nette
|
No
|
-
|
-
|
Option.
|
MOA+105:x--x:EUR:2:(status)
|
OtherCostsToBeAddedToTheNetPremiumAmount
|
||
| 230 |
Taux de prime
|
No
|
-
|
-
|
Option.
|
PCD+016:x--x:(decimals)
|
PremiumRatePercentage
|
||
| 240 |
Taux de commission
|
No
|
-
|
-
|
Option.
|
PCD+005:x--x:(decimals)
|
CommissionPercentage
|
||
| 250 |
Pourcentage des charges
|
No
|
-
|
-
|
Option.
|
PCD+006:x--x:(decimals)
|
ChargesPercentage
|
||
| 260 |
Pourcentage des frais
|
No
|
-
|
-
|
Option.
|
PCD+007:x--x:(decimals)
|
CostsPercentage
|
||
| 270 |
Pourcentage frais et charges
|
No
|
-
|
-
|
Option.
|
PCD+010:x--x:(decimals)
|
CostsAndChargesPercentage
|
||
| 280 |
Pourcentage réduction commerciale
|
No
|
-
|
-
|
Option.
|
PCD+036:x--x:(decimals)
|
PercentageCommercialDiscountPercentage
|
||
| 300 |
Franchise
|
No
|
-
|
-
|
Option.
|
Completed with DEDxxx.v1
|
DED+xxx
|
Deductible...
|
|
(*) 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.