Professional Documents
Culture Documents
Debit Application File Processing: Field Format Description Mandat Ory/o
Debit Application File Processing: Field Format Description Mandat Ory/o
Debit Application File Processing: Field Format Description Mandat Ory/o
The debit application file batches are for creation of debit application using batches instead of the
debit application screen.
◼ You don’t need to approve the applications after file integration; we create the applications
with the status Approved.
◼ The Debit Application Validation is for validate all data existing in the file, validate the
format, length, and existing data in the system …
◼ After validation, you have to execute the debit application integration file, it will take the
data from the validation file generated previously to create a debit application row in debit
application table.
◼ The debit application file integration will may generate an error file in case we have any
failed controls.
◼ After the 2 batches you have to continue the process normal to create the card, that’s mean,
you have to execute the Debit Application Validation batch then cardholder EOD.
Mandat
Field Format Description
ory/O
Bank Id N(10) Bank number in MXP M
Example : 00006
Branch Id AN(20) Bransh Id in MXP M
Example : ET0010222
Application Date DATE(8) Actual date M
RRMMDD Example : 20190221
Customer Type AN(1) Possible Value : M
- O : OLD Customer (Already Has a
card)
- N : New customer
Customer Id AN(24) Customer identification number M
Example : 1003213890
(*)
Parent Customer AN(24) The identification parent of this O
Customer
Example :space
Customer Parent N (2) Possible Values : O
Relation 01 - Son
02 - Grand Son
03 - Daughter
04 - Grand Daughter
05 - Father
06 - Step Father
07 - Mother
08 - Step Mother
09 - Grand Father
10 – Grand Mother
11 - Sister
12 - Brother
- 13 - Wife
Gender AN(1) M - Male M
F - Female
Example: APPLICATION.00006.20190226