id validation

Is there anyone who has done a routine to validate the National ID number for a customer record. If so you please forward it to This email address is being protected from spambots. You need JavaScript enabled to view it.

It can be achieved thru EB.ALTERNATE.KEY Record ID will be the APP name (CUSTOMER in ur case)

Model Bank EB.ALTERNATE.KEY SEE

APPLICATION....... CUSTOMER

---

1 ALT.KEY.MAX.LENGTH 20
2. 1 ALT.KEY.FIELD.. L.CPR.NUMBER
3. 1 CONCAT.TYPE.... SYSTEM
4. 1 ACCESS.METHOD.. READ
25 CURR.NO........... 9

---

No much info/idea on how the rest of the setup was done... hope someone else, might be able to help!

Just tested the same setup on ACCOUNT application and it works fine. No other setup is required.

It creates a CONCAT file "F.ACCOUNT.FLD.NAME" on authorising the EB.ALT.KEY. When you update any record in the ACNT application with the "National ID" number, system automatically updates the CONCAT file. If u try to assign the same ID to other AC record, it automatically shows that its assigned to other AC

1. Create a Local Ref Field for the "National ID"
2. Attach it to the CUSTOMER app
3. Create an entry in EB.ALTERNATE.KEY table with CUSTOMER as the record id, with the Local Ref field you have created.
4. On authorising, system automatically create2 the CONCAT file

its ready to use . . . there you go

*** Configured and tested on R09 Release ***

Dear leopoge,

If you are looking for a routine to validate, then you have to write of your own. Since the logic followed on generation of Identification Number might differ between countries based on the system they have implemented.

In India we have PAN (Personal Identification Number) and AADHAR, which is a 12 digit unique identification number.

Check the below link, in which a routine for validation of IBAN is provided,
IBAN

May i ask something gm.saran, if i create a CUSTOMER record in the table you mentioned EB.ALTERNATE.KEY SEE, does it affect the records already created under CUSTOMER table. I mean does it check for all duplicates in retrospect?

Dear Leo,

wat i've provided earlier is the setup to use "National ID" as an Alternate Key, which will handle your duplicate validation by default. No extra routine devt required. T24 will handle it directly.

Any New customer records which you create after this setup, the CONCAT file will be automatically updated. Now to update all your existing CUSTOMER records, which are created before this KEY TABLE is setup, you can follow two ways

1. write a Routine and update the "CONCAT" file created during the "EB.ALTERNATE.KEY" setup.
or
2. Create a amend customer version record and through Batch OFS or through DM tool update the NATIONAL id, which in turn will update this CONCAT file

Thank you, gm.saran.

Hello,

I have setup as described above and it works wonderfully. My only problem is the error message.

Legal ID No UNIQUE IS 'SYSTEM' - ALT KEY ALREADY ASSIGNED TO 215295 IN EU0010001

How can i change this to something that the user can understand without calling helpdesk. Something like

The National ID Number entered is already assigned to Customer 215295

Thanks in advance.