CDR 5.0 & BDL-CDR · 2018. 11. 6. · BANQUE DU LIBAN I.T DEPARTMENT CDR 5.0 Technical document (CDR_50_TDV1.1.doc) Page : 4 II. ABBREVIATIONS BDL Banque du Liban. CDR Centrale des

Page : 1 CDR 5.0 Technical document (CDR_50_TDV1.1.doc)

I.T DEPARTMENT

مديرية المعلوماتية

CDR 5.0 & BDL-CDR

TECHNICAL DOCUMENT

Centrale des Risques

Version 1.0 November 2018

CDR_50_TDV1.0.doc

BANQUE DU LIBAN I.T DEPARTMENT


TABLE OF CONTENTS

I. WHO SHOULD USE THIS MANUAL 3

II. ABBREVIATIONS 4

III. GENERAL VIEW 5

1. INTRODUCTION 5

2. GENERAL RULES AND NAMING CONVENTION 7

3. DATA CYCLE DESCRIPTION 8

IV. SYSTEM REQUIREMENTS 9

V. DATABASE STRUCTURE 10

1. OVERVIEW 10

2. STATIC TABLES 11

3. WORKING TABLES 20

4. INTERFACE FILES WITH THE CDR CENTER 27

VI. ADMINISTRATION 57

APPENDIX 1 : ADDITIONAL INTERFACE FILES 58



I. WHO SHOULD USE THIS MANUAL

This manual is intended to help the members of the Centrale Des Risques (CDR) understand

the concept of Banque du Liban CDR 5.0 application, and it provides a complete technical

description of the tables and files used by the application, in order to build an automated

interface to this application and bypass the data entry operation.

Furthermore, this document describes in 'Appendix 1' the interface files with BDL-CDR

system that will be used to integrate with the internal systems of the members.



II. ABBREVIATIONS

BDL

Banque du Liban.

CDR

Centrale des Risques.

BDL-CDR The system that manages the CDR data at BDL and provides the CDR

members workflows for monthly declaration and on line inquiry.

DC

Data Cycle.

MES Message file, type of file sent from the members to the CDR center.

COM Communication file, type of file sent from the CDR center to the

members.

IND.

Individual.

STE.

Company (Societe).

AU

Authorized credit amount.

UT

Used credit amount.



III. GENERAL VIEW

1. Introduction

The aim of the CDR 5.0 application is to support the members of the CDR to declare on

monthly basis the risk of their clients to the CDR center. The monthly declaration is detailed

by branch and client.

In order to declare a client, the member should have the CDR number of that client which is

assigned by the CDR center through a request executed on the BDL-CDR system. Therefore

the declaration of the identification information of the clients is done using BDL-CDR system

and not using the CDR 5.0 application. Once the CDR number is assigned, the member can

load that number into the clients repository in the CDR 5.0 application and use it later on in

the monthly declaration process.

The clients declared in the previous month, named old clients, will be available in the system

and can be used in the declaration of the current month. Any client not declared in the

previous month and need to be declared as new client will be retrieved from the upper

mentioned repository.

The application provide data entry forms to declare the risk of the clients as per BDL basic

circular 75.

After completing the data entry, the application allows the members to validate their data and

generate a file that will be uploaded into BDL-CDR system during the monthly declaration

process.



After receiving the declarations from all the members, the CDR center will prepare for each

member a set of files named "COM files" and make them available for download through

BDL-CDR system. The set of files consist of:

1- The "AVIS" file named COM_AV_00bbbyymm contains the global risk of the member's

clients in the banking sector.

2- The "UPDATE" file named COM_UP_00bbbyymm contains the updates on the static data

that occurred at the CDR center.

3- The "FIRST" file named COM_FF_00bbbyymm contains the clients identification data and

risk data declared by the member to the CDR center. The preparation of this file is optional

because it is used only in case the member lost his data.

The downloaded files will be loaded into CDR 5.0 application to allow the members to be

aware of the global risk of their clients in the banking sector and to create the next situation to

declare in an up-to-date environment.



2. General rules and naming convention

Previous situation means the situation directly preceding the situation in preparation.

Old clients are the clients declared in the previous situation.

Deleted client is a client in a branch who existed in the previous situation but has no risk

amounts in the current situation.

Any client in a branch with no risk amounts declared in the previous situation is

considered as a new client.

To declare the risk amounts of a new client, that client should exist in the client

repository of the application.

To load the client information in the client repository, the CDR member should execute

a request for CDR number through the BDL-CDR system and load the outcome into the

CDR 5.0 application.

The declaration of the identification information of the clients is done using BDL-CDR

system and not using the CDR 5.0 application.

Control Record is a record containing totals of the data entered. A control record must

be entered for each branch. The control is done on:

The summation of the amounts by subgroup The count of the clients and the summation of their numbers split as old and new.

For a branch with no risk amounts, a zero control record must be entered.

Validation must be done to ensure that the control records are correct and to permit the

export of the data into a file named MES_DR_00bbbyymm that will be uploaded into

BDL-CDR system. The export process generates totals for the member's declared data,

called BDL control.

The BDL control must be signed and uploaded into BDL-CDR system along with the

file named MES_DR_00bbbyymm.



3. DATA CYCLE DESCRIPTION

Each month (situation) is considered as one Data Cycle (DC). The different steps to perform a

DC are :

1- At the bank or Financial institution:

Entry of data per branch: Risk amounts and control records.

Validation of the entries.

Export the validated data into the file "MES_DR" and print and sign "BDL Control".

Upload the file "MES_DR" into BDL-CDR system and verify that it passed the

technical validation.

Attach a scanned copy of "BDL Control" to the automatically created declaration

request and forward it to the CDR center.

2- At the “Centrale des Risques” center :

Receive the files "MES_DR" from all the members and perform business validation

on each of them.

Prepare for each member the "return files" and make them available to download from

BDL-CDR system.

3- At the bank or Financial institution :

Download the "return files" from BDL-CDR system.

Import the "return files" into CDR 5.0 application.

Review the global risk of the clients in the banking sector.

Create the next situation date to declare.

CDR Member

(Bank or financial

institution)

CDR center

(BDL)

MES

COM



IV. SYSTEM REQUIREMENTS

CDR 5.0 is built on Microsoft Access 2010.

This application runs on Microsoft Windows

7.

It is not mandatory to have Microsoft Access 2010 running on your PC. BDL will provide

you with the necessary runtime.



V. DATABASE STRUCTURE

1. OVERVIEW

The CDR 5.0 application is developed using Microsoft Access 2010 environment. The

application is built using three Microsoft Database files which are:

CDR_50_S.accdb (Static Database) contains the codes and parameters of the

application.

CDR_50_W.accdb (Working Database) contains the risk data of the members.

CDR_50_I.accde (Interface Database) contains the forms, reports and the modules

of the application.

The Interface Database CDR_50_I.accde is linked to the other databases CDR_50_S.accdb

and CDR_50_W.accdb.

In addition, Interface files (line sequential text files) are used by the application to send or

receive data to or from the system BDL-CDR.

Refer to the next paragraphs for detailed information.

CDR_50_I

CDR_50_S

CDR_50_W



2. STATIC TABLES

The static tables are database tables used to store the codes and parameters of the application.

The file CDR_50_S.accdb contains thirty static tables which are: Liability tables

LiabilityGroup Contains the main liability groups a client may have, which

are :

Direct

Indirect.

LiabilitySubGroup Contains the liability subgroups a client may have, which are:

Direct Liabilities,

Received Guarantees,

Off balance sheet accounts,

Memorandum items.

LiabilityType Contains all the liability types a client may have. These types

are related to liability subgroups (ACB, AVM, ASH, etc.

…….).

LoanType Contains all possible loan types. The loan types are related

only to the Direct Liability subgroup ( a1, a2, a3, etc…)

LiabilityCrossLoan Contains the possible relation between the liability Types and

the Loan types.

Branches tables

Bank Contains the member name (Bank or Financial Institution).

BankBranches Contains all the branches names and numbers of the member

itself.

Names Dictionnary tables

DictFamily Contains all the possible family names that can be used in the

Identification cards of the individuals.

DictFemale Contains all the possible female names that can be used in the


DictMale Contains all the possible Male names that can be used in the




General codes tables

ClassificationClient Contains the clients economic classification ECO02 as per

Basic Decision 6271 - Basic Circular 28.

ClassificationRisk Contains the risk rating of the loans as per Basic Decision

7159 - Basic Circular 58.

Devise Contains the currencies list DEV01.

EcoSector Contains the possible economic sectors main codes ECO01.

EcoSecSubdiv Contains the possible economic sectors subdivisions codes

ECO01.

EtatContentieux Contains all the possible judicial statuses of the clients.

FormeJuridique Contains all the possible legal forms of the clients.

CreditPortfolio Contains all the possible credit portfolios of the clients.

QualiteAssocie Contains the partners, shareholders and participants types in

a moral person.

JuridiqueCrossQualite Contains the possible relation between the

“FormeJuridique” and the “QualiteAssocie” data tables.

Nationality Contains the nationalities list NAT01.

PlaceRegistre Contains the Lebanese regions used for personal register

locations and addresses.

RegistreCommerce Contains the trade register locations in Lebanon.

Location

Contains the possible Lebanese regions (caza) or countries

where the loans or the facilities are used.

FamilyStatus Contains the possible family statuses of the individual

clients.

RequestPurpose Contains the possible values of the purpose why a request

for a CDR number was initiated in BDL-STR system.

Special tables

Labels Contains labels used in the application forms for

programming purposes.

STMessages Contains the end-user messages used in the application.

LockTab Used for programming purposes.

LockDatabase Used for programming purposes.



The upper tables are recognized and coded by the CDR center. Therefore any kind of

modification is prohibited. A recognized modification should be done only by the

“Centrale des Risques” administrator.



2.1 Relation between Static tables and CDR declarations

Déclaration à la Centrale Des Risques CDR1 Risques au ____/____/________

No. et Nom de l’établissement : No. et Nom de l’agence : No. et Nom du bénéficiaire :

En millions LL Liability Subgroup 1

Code type

de crédit Code

Sect Eco. Code

Devise Montant

Autorisé Montant

Utilisé Période

restante

(mois)

Classif.

Des

Risques

Pays /

Region

d'util.

Liability type Loan type Loan type Total


Total des Eng. Directs Liability Subgroup 2

Liability type Liability type

En millions LL

Liability Subgroup 3

Code type

de crédit Code Sect

Eco. Code

Devise Montant

Autorisé Montant

Utilisé Période

restante

(mois)

Classif.

Des

Risques

Pays /

Region

d'util.

Marges

Monétaires

et autre



Total des Eng. Indirects Liability Subgroup 4

Liability type Liability type

Liability Group 1

(Direct)

Liability Group 2

(Indirect)



2.2 Static tables description

Table name : LiabilityGroup

Primary key : LiabilityGroup

Fields Type Format Values

Key LiabilityGroup Byte 9

Description Text(20)

Table name : LiabilitySubGroup

Primary key : LiabilityGroup, SubgroupCode



SubgroupCode Byte 9


Table name : LiabilityType

Primary key : LiabilityGroup, SubgroupCode, LiabilityType



SubgroupCode Byte 9

LiabilityType Byte 99

Shortdescription Text(6)


Authorized Yes/No

Ltype Yes/No

Margin Yes/No

Table name : LoanType

Primary key : LoanType


Key LoanType integer 999

ShortDescription Text(4)


LocalCurrency Yes/No

Table name : LiabilityCrossLoan

Primary key : LiabilityGroup, SubgroupCode, LiabilityType, LoanType



SubgroupCode Byte 9

LiabilityType Byte 99

LoanType integer 999



Table name : Bank

Primary key : BankNumber


Key BankNumber Integer 999

Bank Name Text(30)

Table name : BankBranches

Primary key : BankNumber, BranchNumber


Key BankNumber Integer 999

BranchNumber Integer 999

BranchName Text(30)

Active Yes/No

Table name : DictFamily

Primary key : DFLatin


Key DFLatin Text(20)

DFArabic Text(20)

Table name : DictFemale

Primary key : DFMLatin


Key DFMLatin Text(20)

DFMArabic Text(20)

Table name : DictMale

Primary key : DMLatin


Key DMLatin Text(20)

DMArabic Text(20)

Table name : ClassificationClient

Primary key : CltClassCode


Key CltClassCode Text(4)

CltClassDescriptionLatin Text(105)

CltClassDescriptionArabic Text(105)

CltClasslevel Text(1) 1,2,3,4

CltClassTerminus Yes/No



Table name : ClassificationRisk

Primary key : RiskClassCode


Key RiskClassCode Byte 9

RiskClassDescriptionLatin Text(60)

RiskClassDescriptionArabic Text(60)

Table name : Devise

Primary key : DevCode


Key DevCode Integer 999

DevDescriptionLatin Text(25)

DevDescriptionArabic Text(25)

ISOCode Text(3)

Table name : EcoSector

Primary key : SectorCode


Key SectorCode Text(1)


Table name : EcoSecSubdiv

Primary key : SectorCode, SubdivCode


Key SectorCode Text(1)

SubdivCode Text(2) 99


Table name : EtatContentieux

Primary key : ECCode


Key ECCode Integer 999

ECDescriptionLatin Text(60)

ECDescriptionArabic Text(60)



Table name : FormeJuridique

Primary key : FJCode


Key FJCode Byte 99

FJDescriptionLatin Text(60)

FJDescriptionArabic Text(60)

FJtype Text(2) I, S, IS

FieldObligation Yes/No

Table name : CreditPortfolio

Primary key : CrPrtfCode


Key CrPrtfCode Byte 99

CrPrtfDescriptionLatin Text(60)

CrPrtfDescriptionArabic Text(60)

Table name : QualiteAssocie

Primary key : QACode


Key QACode Byte 99

QADescriptionLatin Text(60)

QADescriptionArabic Text(60)

Table name : JuridiqueCrossQualite

Primary key : FJCode, QACode


Key FJCode Byte 99

QACode Byte 99

Table name : Nationality

Primary key : NatCode


Key NatCode Integer 999

NatDescriptionLatin Text(35)

NatDescriptionArabic Text(35)



Table name : PlaceRegistre

Primary key : PRCode


Key PRCode Long Integer 99999

PRDescriptionLatin Text(60)

PRDescriptionArabic Text(60)

Registre Yes/No

Table name : RegistreCommerce

Primary key : RegCode


Key RegCode Byte 99

RegDescriptionLatin Text(60)

RegDescriptionArabic Text(60)

Table name : Location

Primary key : LocCode


Key LocCode Long Integer 999

LocDescriptionLatin Text(60)

LocDescriptionArabic Text(60)

LocShortDesc Text(4)

Table name : FamilyStatus

Primary key : FMCode


Key FMCode Text(1)

FMDescriptionLatin Text(60)

FMDescriptionArabic Text(60)

Table name : RequestPurpose

Primary key : ReqPurpCode


Key FMCode Text(6)

ReqPurpDescriptionLatin Text(60)

ReqPurpDescriptionArabic Text(60)

Table name : Labels

Primary key : Controlcharacter


Key Controlcharacter byte 99


Table name : STMessages

Primary key : Code


Key Code Text(6) XXX999




3. WORKING TABLES

The working tables are database tables used to store information about Clients Identification,

Data credits details and Control Records.

The file CDR_50_W.accdb contains eleven working tables which are :

Situation Used to store all the situation dates that exist in the application

including the current situation date.

Risk tables

RiskID Contains summary information about the Clients Identification

data.

RiskIDBR Indicates in which branch the client has credits and whether the

client is an old or a new client.

RiskAmt Contains the credits amounts of the client detailed by branch,

liability group and subgroup, liability type, loan type, economic

sector, currency, remaining period, utilization country code and

risk classification.

RiskVal Contains the data validation flag of the branches in a situation

and used in the validation process.

RiskCtl Contains the control records of the branches in a situation and

used for data integrity purposes.



Avis tables

AvisAmt Contains the total amount of credits granted by the banking and

financial sector to the clients of the members, classified by

liability group and subgroup, liability type, loan type, economic

sector, currency, remaining period, utilization country code and

risk classification.

AvisBranchCtl Contains the control records of the situation classified by branch,

used for data integrity and statistical purposes.

Repository tables

RiskReq_rep Contains the requests executed by the member to get the

identification information of a client using BDL-CDR system.

RiskID_rep Contains the detailed identification information of new clients

who were subject to request for CDR number.

ComLoad Contains the name of the daily files (COM-I1, COM-ID files)

that were used to upload data in the previous 2 tables.



3.1 Working tables description

Table name : Situation

Primary key : CurrentSituationyear, CurrentSituationmonth


Key CurrentSituationyear Integer 9999

CurrentSituationmonth Byte 99

PreviousSituationyear Integer 9999

PreviousSituationmonth Byte 99

NextSituationyear Integer 9999

NextSituationmonth Byte 99

SituationStatus Text(1) D = deleted

Deletion date Date yyyy/mm/dd

Table name : RiskID

Primary key : Situationyear, Situationmonth, Clientnumber


Key Situationyear Integer 9999

Situationmonth Byte 99

ClientNumber Long integer 99999999

Clientname Text(70)

Clienttype Text(1) P = Physical person

M = Moral person

BFdate Text(8) Birth / Foundation date: yyyymmdd

RegCode Byte 99

PRCode Long Integer 99999

Registrationnumber Text(12)

Table name : RiskIDBR

Primary key : Situationyear, Situationmonth, Clientnumber, Branchnumber





Branchnumber Integer 999

OldNew Text(1) O = Old client

N = New client



Table name : RiskAmt

Primary key : Situationyear, Situationmonth, Branchnumber, Clientnumber, Liabilitygroup, Subgroupcode, Liabilitytype, Loantype






Liabilitygroup Byte 9 1=direct / 2=indirect

Subgroupcode Byte 9 1=direct/2=guarnt/1=hbilan/2=mem

Liabilitytype Byte 99

Loantype integer 999

keyfield Text(13) SectorCode ||SubDivCode||

CurCode|| RemainingPeriod||

RiskClassCode||UtlCountryCode

In case any of the fields is empty

the corresponding value will be

replaced by the character ‘-‘ for the

text fields and by ‘0’ for the

numeric fields.

SectorCode Text(1)

SubDivCode Text(2) 99

CurCode Integer 999

RemainingPeriod Integer 999

RiskClassCode Byte 9

UtlCountryCode integer 999 Utilization region or country

CreditLimit Long integer 9999999 (in millions of LL)

CreditUsed Long integer 9999999 (in millions of LL)

Marges Long integer 9999999 (in millions of LL)

Table name : RiskVal

Primary key : Situationyear, Situationmonth, Branchnumber





Validationflag Yes/No Y= validated / N= not yet validated



Table name : RiskCtl

Primary key : Situationyear, Situationmonth, Branchnumber, Controlcharacter





Controlcharacter Byte 9 1,2,3,4,5,6

Controlfield1 Double 999999999999999


The following table shows the values of the control fields:

Control

Character

Control field 1 Control field 2

1 Credit limit total for liability

subgroup 1

Credit used total for liability

subgroup 1


subgroup 2


subgroup 2


subgroup 3


subgroup 3


subgroup 4


subgroup 4

5 Count of the old clients in this

branch.

Sum of the CDR numbers of the

old clients in this branch.

6 Count of the new clients in this

branch.


new clients in this branch.

Table name : AvisAmt

Primary key : Situationyear, Situationmonth, Branchnumber, Clientnumber, Liabilitygroup, Subgroupcode, Liabilitytype, Loantype, keyfield

Fields Format Values





Liabilitygroup Byte 9 1=direct / 2=indirect

Subgroupcode Byte 9 1=direct/2=guarnt/1=hbilan/2=mem

Liabilitytype Byte 99

Loantype Integer 999

keyfield Text(13) SectorCode ||SubDivCode||

CurCode|| RemainingPeriod||

RiskClassCode|| UtlCountryCode

SectorCode Text(1)

SubDivCode Text(2) 99

CurCode Integer 999

RemainingPeriod Integer 999

RiskClassCode Byte 9

UtlCountryCode Integer 999 Utilization region or country

CreditLimit Long integer 9999999 (in millions of LL)

CreditUsed Long integer 9999999 (in millions of LL)

Marges Long integer 9999999 (in millions of LL)



Table name : AvisBranchCtl

Primary key : Situationyear, Situationmonth, Branchnumber, Controlcharacter Fields Description Format Values

Key Situation year Integer 9999

Situation month Byte 99

Branch number Integer 999

Control character Byte 9 1,2,3,4,5,6,7,8




Control

Character



subgroup 1


subgroup 1


subgroup 2


subgroup 2


subgroup 3


subgroup 3


subgroup 4


subgroup 4

5 Count of the clients in this branch

in the previous situation.


clients in this branch in the

previous situation.

6 Count of the clients deleted in this

branch in this situation.


clients deleted in this branch in this

situation.

7 Count of the new clients in this



new clients in this branch in this

situation.

8 Count of the clients (old and new)

in this branch in this situation.


clients (old and new) in this branch

in this situation.

Table name : ComLoad

Primary key : ComFileName


Key ComFileName Text(70)

ComFileType Text(10) COM-I1

COM-ID

LoadDate Date

ReferenceDate Date



Table name : RiskReq_Rep

Primary key : Clientnumber


Key


ReferenceDate Date

Branch Integer 999

RequestNum Text(21) Format : yyyymm00BBBbbbnnnnn

CRMRefNum Text(16)

RequestPurpose Text(6)

RequestOperType Text(1) N:new

M:Modification

C:confirmation

Table name : RiskID_Rep

Primary key : Situationyear, Situationmonth, Clientnumber, clientserial


Key ClientNumber Text(9)

clientserial Byte 99 00 for Beneficiary

01,02,03,etc for partners

Clienttype Text(1) P = Physical person

M = Moral person

Nom Text(40)

Prenom Text(40)

PrenomPere Text(40)

PrenomMere Text(40)

FamilleMere Text(40)

PrenomConjoint Text(40)

FamilleConjoint Text(40)

RaisonSociale Text(240)

Sex Text(1) M : Male, F : Female

FamilyStatus Text(1) Table: FamilyStatus

BFDate Text(8)

PRCode Long Integer 99999 Table: PlaceRegistre

RegCode Byte 99 Table: RegistreCommerce

RegistrationNumber Text(12)

NatCode Integer 999 Table: Nationality

Residence Text(1) Y: Yes, N: NO

AddresseImm Text(35)

AddresseRue Text(35)

AddresseSect Text(35)

AddresseVille Text(35)

AddresseLocalite Long Integer 99999 Table: PlaceRegistre

AddressePays Integer 999 Table: Nationality

AddresseTel1 Text(12)

AddresseTel2 Text(12)

AddressePostale Text(8)

CltClassCode Text(4) Table: ClassificationClient

FJCode Byte 99 Table: FormeJuridique

ECCode Integer 999 Table: EtatContentieux

CrPrtfCode byte 99 Table: CreditPortfolio

NomsCommerciaux Text(120)

Divers Text(240)

QACode Byte 99 Table: QualiteAssocie

PourcentageParticipation Integer 999



4. INTERFACE FILES WITH THE CDR CENTER

The Interface files with the CDR center are line sequential text files containing columns

separated by '?', sent or received by the members to or from the CDR 5.0 application. These

files are either uploaded or downloaded from BDL-CDR system.

The interface files are of 2 types:

The "MES" files are the one generated by the CDR 5.0 application and uploaded to

BDL-CDR system.

The "COM" files are the one downloaded from BDL-CDR system and imported into

the CDR 5.0 application.

Follows the complete list of interface files and their brief description.

MES_DR Contains the risk data of the clients and is generated by CDR 5.0

application and sent monthly by the members to the CDR center

at BDL through upload in BDL-CDR system.

COM_ID It is prepared by the BDL-CDR system on each end of day and

contains the answers to requests received from the member and

processed in BDL during the period from the previous

preparation date till the date of preparation of the current file.

COM_I1 Contains the answer to one request received from the member

and processed in BDL. It is prepared by the BDL-CDR system

and downloaded when the member receive back his request from

BDL.

COM_AV Contains the global risk of the member's clients in the banking

sector. It is prepared by the BDL-CDR system on monthly basis

as an answer to MES_DR file.

COM_FF Contains the clients identification data and risk data declared by

the member to the CDR center. It is prepared on request by the

BDL-CDR system on monthly basis.



COM_RC Contains the list of clients who were subject to an update in their

risk classification at BDL center due to discrepancies between

the risk classification evaluated by the Banking Control

Commission (BCC) and the risk classification specified by the

member. This file is for information only, it is not loaded into


COM_UP Contains the updates on the static data that occurred at the CDR

center. These updates will be replicated on the members static

database when importing that file.

COM_IN Contains flags that indicate what commands to be executed at the

member’s site upon receiving the data from the CDR center.

Notes:

The files COM_AV, COM_FF, COM_RC, COM_UP and COM_IN are downloaded from

BDL-CDR system through one single compressed file named COM_ZP_00bbbyymm.zip,

where bbb=bank num, yy=year, mm=month



4.1 Interface files description

File name : MES_DR

Type: text file with fields separated by '?'

Naming convention: MES_DR_00bbbyymm (bbb=bank num, yy=year, mm=month)

The data existing in this file is grouped by branch. Each branch data is delimited by a branch

header records and eight branch control records. The entire branches data is delimited by a

bank header record and four bank control records.

The file skeleton is as follows:

Bank Header Record

Branch number 1, Header Record

Branch number 1, risk amount data Records

Branch number 1, Control Record 1

Control Record 2

Control Record 3

Control Record 4

Control Record 5

Control Record 6

Control Record 7

Control Record 8

Branch number 2, Header Record

Branch number 2, risk amount data Records


Control Record 2

Control Record 3

Control Record 4

Control Record 5

Control Record 6

Control Record 7

Control Record 8

Bank Control Record 1

Control Record 2

Control Record 3

Control Record 4



Bank header record (File MES_DR)

Order Fields Description Format Max Length Values

1 Format character Char 5 AA

Separator Char 1 ?

2 Identification field Char 8 MES-DR

Separator Char 1 ?

3 Bank number Num 3

Separator Char 1 ?

4 Bank name Char 30

Separator Char 1 ?

5 Situation date Num 6 yyyymm

Separator Char 1 ?

Branch header record (File MES_DR)


1 Format character Char 5 BB

Separator Char 1 ?

2 Branch number Num 3

Separator Char 1 ?

3 Identification field Char 8 MES-DR

Separator Char 1 ?

4 Bank number Num 3

Separator Char 1 ?

5 Branch name Char 30

Separator Char 1 ?


Separator Char 1 ?

Amounts data record (File MES_DR)


1 Format character Char 5 D

Separator Char 1 ?


Separator Char 1 ?

3 Client status Char 1 O: Old

N: New

Separator Char 1 ?

4 Client CDR number Num 8

Separator Char 1 ?

5 Liability group Num 1

Separator Char 1 ?

6 Subgroup code Num 1

Separator Char 1 ?

7 Liability type Num 2

Separator Char 1 ?

8 Loan type Num 3

Separator Char 1 ?




9 Currency code Num 3

Separator Char 1 ?

10 Credit limit Num 7 (in millions of LL)

Separator Char 1 ?

11 Credit used Num 7 (in millions of LL)

Separator Char 1 ?

12 Economic sector Char 1 1 space if not

applicable

Separator Char 1 ?

13 Economic sub sector Char 2 2 spaces if not

applicable

Separator Char 1 ?

14 Remaining Period Num 3 In months or 0 if not

applicable

Separator Char 1 ?

15 Risk classification Num(1) 1

Separator Char 1 ?

16 Margin Num(7) 7 (in millions of LL)

Separator Char 1 ?

17 Utilization country Num(3) 3

Separator Char 1 ?

Note that all fields are mandatory and that null values are not accepted.

To represent a null value, two consecutive ?? are not accepted. If the field is numeric you have to use ?0?

otherwise you will use ? ?.

Follows an extract of a sample file:



Branch control record (File MES_DR)


1 Format character Char 1 Y

Separator Char 1 ?


Separator Char 1 ?

3 Extra bit Char 1 1,2,3,4,5,6,7,8

Separator Char 1 ?

4 Control field 1 Num 15

Separator Char 1 ?


Separator Char 1 ?


Extra

Bit


1 Credit limit total for liability subgroup 1 Credit used total for liability subgroup 1




5 Count of the old clients in this branch. Sum of the CDR numbers of the old

clients in this branch.

6 Count of the new clients in this branch. Sum of the CDR numbers of the new


7 Count of the clients (old and new) in this

branch in the previous situation.

Sum of the CDR numbers of the clients

(old and new) in this branch in the

previous situation .

8 Count of the clients deleted in this branch in

this situation.

Sum of the CDR numbers of the clients

deleted in this branch in this situation.



Bank control record (File MES_DR)


1 Format character Char 1 Z

Separator Char 1 ?

3 Extra bit Char 1 1,2,3,4

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit


1 Credit limit total for the complete bank

and all liability subgroups.

Credit used total for the complete bank and

all liability subgroups.

2 Count of the old clients in this bank. Sum of the CDR numbers of the old clients

in this bank.

3 Count of the new clients in this bank. Sum of the CDR numbers of the new clients

in this bank.

4 Number of rows in the file including the

current one

Zero

The validation of the MES_DR file is done using 3 validation levels:

Level 1: The application will verify the structure of the file: Bank Header, Branch header, risk

amount data records, branch control, bank control.

Level 2: The application will verify the validity of the codes used in the file.

Level 3: The application will verify some business validation rules.

Follows some validation rules applied on the MES_DR file. It cannot be considered as the

complete list of validation rules.

1- All the active branches should be declared and only the active branches should be declared.

2- CDR numbers should be valid and linked to the bank and branch through previous

declaration or through a request for CDR number using BDL-CDR system.

3- All codes used in the file should be defined in the corresponding tables.

4- Authorize amounts and margin amounts can be used only in liability types where theses

amounts are allowed.

5- Risk classification cannot be equal to zero for liability subgroup 1 and liability subgroup 4.

6- Risk classification should be equal to zero for liability subgroup 2 and liability subgroup 3.

7- Remaining period should be equal to zero for liability subgroup 2 and liability subgroup 3.

8- For liability subgroup 2, the economic sector must be equal to one space and the sub sector

to two spaces.

9- Housing loans should have economic sector equal to R02.

10- Agriculture loans should have economic sector equal to A01.

11- Education loans should have economic sector equal to R06.



File name : COM_ID


Naming convention: COM_ID_00bbbyymmdd (bbb=bank num, yy=year, mm=month,

dd=day)

The file begins by a Bank Header Record containing the preparation date of the file. The data

in this file represent the requests received from the CRMs and processed in BDL during the

period from the previous preparation date till the date of preparation of the current file.


Bank Header Record

ID data records

Inquiry history data records

Risk amounts data records

ID data records



ID data records



ID data records



ID data records




Bank header record (File COM_ID)


1 Format character Char 5 A1

Separator Char 1 ?

2 Identification field Char 8 COM-ID

Separator Char 1 ?

3 Bank number Num 3

Separator Char 1 ?

4 Bank name Char 30

Separator Char 1 ?

5 Preparation date Num 8 yyyymmdd

Separator Char 1 ?



ID data record (File COM_ID)

Applicability

Order Fields Description Format Max Length Values Common

to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

1 Format character Char 5 CPB: Physical client beneficiary

CPA: Physical client associate

CMB: Moral client beneficiary

CMA: Moral client associate

X

CPB

CPA

CMB

CMA

Separator Char 1 ?

2 Client branch number Num 3 X X X X X

Separator Char 1 ?

3 Request number Char 21 NULL in case the record is due to

an update initiated by another

CRM

X X X X X

Separator Char 1 ?

4 CRM reference number Char 16 NULL in case the record is due to


CRM

X X X X X

Separator Char 1 ?

5 Purpose of the inquiry request Char 6 NULL in case the record is due to


CRM

X X X X X

Separator Char 1 ?

6 Processing date in BDL Num 8 X X X X X

Separator Char 1 ?

7 Client CDR number Num 8 99999999 X X X X X

Separator Char 1 ?

8 Client sequence Num 2 00 for Beneficiary ,

01,02,03,etc… for associates

X 00 01,02,... 00 01,02, ...

Separator Char 1 ?

9 Operation type Char 1 N: New

M: Modification

C: confirmation

X X X X X

Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

10 Client type Char 1 P: Physical person

M: Moral person

X P P M M

Separator Char 1 ?

11 Client family name Char 40 X X

Separator Char 1 ?

12 Client first name Char 40 X X

Separator Char 1 ?

13 Client father’s name Char 40 X X

Separator Char 1 ?

14 Client mother’s first name Char 40 X X

Separator Char 1 ?

15 Client mother’s maiden name Char 40 X X

Separator Char 1 ?

16 Client spouse first name Char 40 X X

Separator Char 1 ?

17 Client spouse family name Char 40 X X

Separator Char 1 ?

18 Gender Char 1 M: Male

F: Female

X X

Separator Char 1 ?

19 Family status Char 1 X X

Separator Char 1 ?

20 Register location Num 5 X X

Separator Char 1 ?

21 Company name Char 240 X X

Separator Char 1 ?

22 Register of commerce place Num 2 X X

Separator Char 1 ?

23 Birth/Foundation date Num 8 X X X X X

Separator Char 1 ?

24 Register number Char 12 X X X X X

Separator Char 1 ?

25 Nationality Num 3 X X X X X

Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

26 Resident Char 1 1: Resident

0: Not resident

X X X X X

Separator Char 1 ?

27 Building / floor Char 35 X X

Separator Char 1 ?

28 Street Char 35 X X

Separator Char 1 ?

29 District Char 35 X X

Separator Char 1 ?

30 City / Village Char 35 X X

Separator Char 1 ?

31 Address location code Num 5 X X

Separator Char 1 ?

32 Address country code Num 3 X X

Separator Char 1 ?

33 Postal code Char 8 X X

Separator Char 1 ?

34 Telephone number 1 Char 12 X X

Separator Char 1 ?


Separator Char 1 ?

36 Client Classification Char 4 X X

Separator Char 1 ?

37 Legal form Num 2 X X X X X

Separator Char 1 ?

38 Judicial status Num 3 X X

Separator Char 1 ?

39 Commercial names Char 120 X X

Separator Char 1 ?

40 Additional information Char 240 X X

Separator Char 1 ?

41 Partner/associate type Num 2 X X

Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

42 Participation percentage Num 5 99.99 X X

Separator Char 1 ?

43 Credit Portfolio Num 2 X X

Separator Char 1 ?

44 Request modified by BDL Char 1 1: Yes

0: No

X X X X X

Separator Char 1 ?


Inquiry history data record (File COM_ID)


1 Format character Char 5 HI

Separator Char 1 ?

2 Client branch number Num 3

Separator Char 1 ?

3 Client CDR number Num 8 99999999

Separator Char 1 ?

4 Inquiry date Num 8 yyyymmdd

Separator Char 1 ?

5 Purpose of the inquiry Char 6

Separator Char 1 ?

6 Count of inquiries Num 10

Separator Char 1 ?

Amounts data record (File COM_ID)


1 Format character Char 5 D1

Separator Char 1 ?

2 Client branch number Num 3

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

8 Loan type Num 3

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


applicable

Separator Char 1 ?


applicable

Separator Char 1 ?


applicable

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



Notes:

1- The ID record should directly precede the inquiry history records and amount records of

the related ID.

2- Only the ID record is mandatory for each request, the inquiry history records and amount

records may exist or not.

3- A null value is represented by two consecutive ??.

4- If a field is not applicable within a format character, it will be omitted.

Bank control record (File COM_ID)



Separator Char 1 ?

3 Extra bit Char 1 4

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit



current one

Zero

File name : COM_I1


Naming convention: COM_I1_requestnumber

request number format: yyyymm00BBBbbbnnnnn where yyyy=year, mm=month,

BBB=bank num, bbb=branch num, nnnnn=sequence num.

The file structure is identical to COM_ID but contains the answer to only one request.



File name : COM_AV


Naming convention: COM_AV_00bbbyymm (bbb=bank num, yy=year, mm=month)

The file begins by a Bank Header Record containing the current situation date and the date of

the next situation to create. The data in this file is grouped by branch. Each branch data is

terminated by eight branch control records.

The file skeleton is as follows :

Bank Header Record

Branch number 1, global amounts data Records


Control Record 2

Control Record 3

Control Record 4

Control Record 5

Control Record 6

Control Record 7

Control Record 8

Branch number 2, global amounts data Records


Control Record 2

Control Record 3

Control Record 4

Control Record 5

Control Record 6

Control Record 7

Control Record 8




Bank header record (File COM_AV)



Separator Char 1 ?

2 Identification field Char 8 COM-AV

Separator Char 1 ?

3 Bank number Num 3

Separator Char 1 ?

4 Bank name Char 30

Separator Char 1 ?

5 Current situation date Num 6 yyyymm

Separator Char 1 ?

6 Next situation date Num 6 yyyymm

Separator Char 1 ?

7 Previous situation date Num 6 yyyymm

Separator Char 1 ?

Branch header record (File COM_AV)


1 Format character Char 5 BB

Separator Char 1 ?


Separator Char 1 ?

3 Identification field Char 8 COM-AV

Separator Char 1 ?

4 Bank number Num 3

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

Amounts data record (File COM_AV)



Separator Char 1 ?


Separator Char 1 ?


N: New

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

8 Loan type Num 3

Separator Char 1 ?


Separator Char 1 ?





Separator Char 1 ?


Separator Char 1 ?


applicable

Separator Char 1 ?


applicable

Separator Char 1 ?

14 Remaining period Num 3 In months or 0 if not

applicable

Separator Char 1 ?

15 Risk classification Num 1

Separator Char 1 ?

16 Margin Num 7 (in millions of LL)

Separator Char 1 ?

17 Utilization Country Num 3

Separator Char 1 ?

Branch control record (File COM_AV)



Separator Char 1 ?


Separator Char 1 ?

3 Extra bit Char 1 1,2,3,4,5,6,7,8

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit






5 Count of the clients in this branch in the

previous situation.

Sum of the numbers of the clients in this

branch in the previous situation.

6 Count of the clients deleted in this branch

in this situation.

Sum of the numbers of the clients deleted in

this branch in this situation.

7 Count of the new clients in this branch in

this situation.

Sum of the numbers of the new clients in

this branch in this situation.

8 Count of the clients (old and new) in this


Sum of the numbers of the clients (old and

new) in this branch in this situation.



Bank control record (File COM_AV)



Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit



current one

Zero



File name : COM_FF


Naming convention: COM_FF_00bbbyymm (bbb=bank num, yy=year, mm=month)

The file begins by a Bank Header Record containing the current situation date and the date of

the previous situation. The data in this file is grouped by branch. Each branch data is

terminated by six branch control records.


Bank Header Record

Branch number 1, Data Records (ID and Amounts)

Note : All ID records should directly precede the amount records of the related ID


Control Record 2

Control Record 3

Control Record 4

Control Record 5

Control Record 6

Branch number 2, Data records (ID and Amounts)

Note : All ID records should directly precede the amount records of the related ID


Control Record 2

Control Record 3

Control Record 4

Control Record 5

Control Record 6




Bank header record (File COM_FF)



Separator Char 1 ?

2 Identification field Char 8 COM-FF

Separator Char 1 ?

3 Bank number Num 3

Separator Char 1 ?

4 Bank name Char 30

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

Branch header record (File COM_FF)


1 Format character Char 5 B2

Separator Char 1 ?


Separator Char 1 ?

3 Identification field Char 8 COM-FF

Separator Char 1 ?

4 Bank number Num 3

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



ID data record (File COM_FF)

Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

1 Format character Char 5 FPB: Physical client beneficiary

FPA: Physical client associate

FMB: Moral client beneficiary

FMA: Moral client associate

X

FPB

FPA

FMB

FMA

Separator Char 1 ?

2 Branch number Num 3 X X X X X

Separator Char 1 ?

3 Client CDR number Num 8 99999999 X X X X X

Separator Char 1 ?

4 Merged client CDR number Num 8 99999999 or NULL = ?? X X X X X

Separator Char 1 ?



X 00 01,02,... 00 01,02, ...

Separator Char 1 ?


N: New

X X X X X

Separator Char 1 ?


M: Moral person

X P P M M

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.


Separator Char 1 ?


Separator Char 1 ?

15 Gender Char 1 M: Male, F: Female X X

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

23 Resident Char 1 1: Resident,

0: Not resident

X X X X X

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

Notes:

1- The ID record should directly precede the amount records of the related ID.




Amounts data record (File COM_FF)



Separator Char 1 ?


Separator Char 1 ?


N: New

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

8 Loan type Num 3

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


applicable

Separator Char 1 ?


applicable

Separator Char 1 ?


applicable

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



Branch control record (File COM_FF)



Separator Char 1 ?


Separator Char 1 ?

3 Extra bit Char 1 1,2,3,4,5,6

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit






5 Count of the old clients in this branch. Sum of the CDR numbers of the old


6 Count of the new clients in this branch. Sum of the CDR numbers of the new


Bank control record (File COM_FF)



Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit



current one

Zero



File name : COM_RC


Naming convention: COM_RC_00bbbyymm (bbb=bank num, yy=year, mm=month)

The file begins by a Bank Header Record containing the current situation date and the dates

of the previous and next situation.


Bank Header Record

Data Row 1

Data Row 2




Bank header record (File COM_RC)



Separator Char 1 ?

2 Identification field Char 8 COM-RC

Separator Char 1 ?

3 Bank number Num 3

Separator Char 1 ?

4 Bank name Char 30

Separator Char 1 ?

5 Current situation date Num 8 yyyymmdd

Separator Char 1 ?

6 Next situation date Num 8 yyyymmdd

Separator Char 1 ?

7 Previous situation date Num 8 yyyymmdd

Separator Char 1 ?

Data row (File COM_RC)



Separator Char 1 ?

2 BCC Risk classification Num(1) 1

Separator Char 1 ?

3 Original Risk classification Num(1) 1

Separator Char 1 ?

Bank control record (File COM_RC)



Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit



current one

Zero



File name : COM_UP


The file begins by a Header Record containing the current situation date and the preparation

date and time of the file. The data rows in the file are of two types:

- Structure rows that indicates the format of the table to be updated,

-Data rows that indicates the data to be inserted or modified or deleted from the

corresponding table.


Header Record

Structure row 1

Data row 1

Data row 2

Structure row 2

Data row 1

Data row 2



Header record (File COM_UP)

Order Fields Description Format Max length Values

1 Format character Char 1 A

2 Separator Char 1 ?

3 Identification field Char 6 COM_UP


5 Bank number Num 3


7 Bank name Char 30




11 Preparation date & time Num 14 Yyyymmddhhmmss


Structure row (File COM_UP)

Order Fields Description Format Max length Values

1 Format character Char 1 B


3 Table name Char 30


5 Number of key fields (n) Num 1


n times Field name Char 30

Separator Char 1 ?

Number of fields other than key

(m)

Num 2

Separator Char 1 ?

m times Field name Char 30

Separator Char 1 ?

Data row (File COM_UP)

Starting Fields Description Format Max length Values

1 Format character Char 1 “C”


3 Operation type Char 1 “A” : Add

“M” : Modify

“D” : Delete

Separator Char 1 ?

n x Key value Char variable

Separator Char 1 ?

m x Field value Char variable

Separator Char 1 ?

Note : n is the number of key fields in the corresponding table while m is the number of

fields other than the key in the corresponding table.



File name : COM_IN

This file contains 4 flags with the following possible values :

2 Indicates to the CDR 5.0 application that the "COM_FF" file has been prepared by

BDL-CDR system and that it’s data should replace the last existing situation risk data in


3 Indicates to the CDR 5.0 application that the "COM_AV" file prepared by BDL_CDR

system.

4 Indicates to the CDR 5.0 application that the "COM_UP" file has been prepared by

BDL_CDR system.

Examples of a CDR_IN :

234 The "COM_FF" and "COM_AV" and "COM_UP" files have been prepared by

BDL_CDR system.

34 The "COM_AV" and "COM_UP" files have been prepared by BDL_CDR system.

3 The "COM_AV" file has been prepared by BDL_CDR system.



VI. ADMINISTRATION

The Entry of data to the application is done for each branch separately. If you choose to install

the application for multi users only one user at a time can prepare the data for a specific

branch. No concurrent users for the same branch are allowed.

Furthermore some functions (processing functions) of the application cannot be run unless

nobody is using the application other than the one who is requesting these functions. These

functions are: create new situation, receive data from BDL, copy data to BDL and purge data.

These restrictions are done using special tables “LockTab” and “Lockdatabase” defined in the

Static Database (CDR_50_S.accdb). When the data of a branch is being edited the number of

this branch is written into table “LockTab” thus preventing any other user to edit the data of

this branch. And when running any processing function a field in table “Lockdatabase” is set

to true thus preventing any other user to use the application.

If for any technical reason (connection lost between the user PC and the server, system crash,

etc…) the flags are not reflecting the real situation you can unlock a branch or the database

using a special function that should be used carefully. From the Static Database run the form

“Administration”. This function should be restricted to the administrator of the application

and normal users should not be aware of this function.



APPENDIX 1 : Additional interface files

BDL-CDR system deals with some additional files to facilitate the integration with the

member's IT systems.

Usage of these files is optional. They are not used with CDR 5.0 application. The member's

IT team should make specific development to integrate these files with their systems.

The interface files are of 2 types:

The "MES" files are the one generated by the member IT systems and uploaded to

BDL-CDR system.

The "COM" files are the one downloaded from BDL-CDR system and imported into

the member's IT systems.

Follows the complete list of these interface files and a brief description.

MES_TR Contains bulk requests for credit inquiry report. It contains the

ID information of the clients and the related associates if

applicable and is used to minimize the data entry operation when

searching for a client, defining a new ID and updating an

existing client ID.

COM_RQ It is prepared by the BDL-CDR system on each end of day and

contains the requests received from the member during the

period from the previous preparation date till the date of

preparation of the current file.

COM_PN It is prepared by the BDL-CDR system on each end of day and

contains the requests received from the member and still pending

in BDL as on the date and time of the preparation of the file.



File name : MES_TR


Naming convention: MES_TR_00bbbyymmdd_xx (bbb=bank num, yy=year,

mm=month, dd=day, xx=serial number)


in this file represent bulk requests for credit inquiry report. It contains the ID information of

the clients and the related associates in case of moral persons and is used to minimize the data

entry operation when searching for a client, defining a new ID and updating an existing client

ID.


Bank Header Record

ID data records

ID data records

ID data records


Bank header record (File MES_TR)



Separator Char 1 ?

2 Identification field Char 8 MES-TR

Separator Char 1 ?

3 Bank number Num 3

Separator Char 1 ?

4 Bank name Char 30

Separator Char 1 ?


Separator Char 1 ?



ID data record (File MES_TR)

Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

1 Format character Char 5 CPB: Physical client beneficiary

CPA: Physical client associate

CMB: Moral client beneficiary

CMA: Moral client associate

X

CPB

CPA

CMB

CMA

Separator Char 1 ?

2 Client branch number Num 3 X X X X X

Separator Char 1 ?

3 Empty Char 21 NULL X X X X X

Separator Char 1 ?

4 CRM reference number Char 16 X X X X X

Separator Char 1 ?

5 Purpose of the inquiry request Char 6 X X X X X

Separator Char 1 ?

6 Preparation date Num 8 X X X X X

Separator Char 1 ?

7 Client CDR number Num 8 99999999 or NULL X X X X X

Separator Char 1 ?



X 00 01,02,... 00 01,02, ...

Separator Char 1 ?


Separator Char 1 ?


M: Moral person

X P P M M

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

18 Gender Char 1 M: Male

F: Female

X X

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

26 Resident Char 1 1: Resident

0: Not resident

X X X X X

Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?



Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?

Notes:





Bank control record (File MES_TR)



Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Separator Char 1 ?


Extra

Bit



current one

Zero



File name : COM_RQ


Naming convention: COM_RQ_00bbbyymmdd (bbb=bank num, yy=year,

mm=month, dd=day)


in this file represent the requests received from the member during the period from the

previous preparation date till the date of preparation of the current file.


Bank Header Record

Request ID data records




Bank header record (File COM_RQ)



Separator Char 1 ?

2 Identification field Char 8 COM-RQ

Separator Char 1 ?

3 Bank number Num 3

Separator Char 1 ?

4 Bank name Char 30

Separator Char 1 ?


Separator Char 1 ?



ID data record (File COM_RQ)

Applicability


to all

Physical

benef.

Physical

assoc.

Moral

benef.

Moral

assoc.

1 Format character Char 5 CPB: Physical client ben

Documents

CDR 5.0 & BDL-CDR · 2018. 11. 6. · BANQUE DU LIBAN I.T DEPARTMENT CDR 5.0 Technical document (CDR_50_TDV1.1.doc) Page : 4 II. ABBREVIATIONS BDL Banque du Liban. CDR Centrale des