CUS2[1].Auto ID Generation In T24-R10.01.pdf

8/11/2019 CUS2[1].Auto ID Generation In T24-R10.01.pdf

1/26

Welcome to the Auto id Generation learning unit in T24. In this learning unit, you will learn

CUS2.Auto ID Generation In T24-R10.01

a out ow to automat ca y generate or eac recor n an app cat on.


2/26

After completing this course, you will be able to


1. Explain the need for Auto ID Generation in T24

2. Understand how it works

3. Set it up for your own applications in T24


3/26

Each application in T24 is made up of a number of records. Each record is indentified

un que y w t t e e p o t s . ets ta e an examp e o a customer recor . ow o youdifferentiate one customer from another? You use the record id to identify each customer

uniquely. Now if you had to manually key in the record id each time for a new customer, itwould be difficult for the end user to decide upon an unique id. Imagine what would happen if

there were several users using T24 at the same time. Its possible that more than one user

could decide on the same id for the customer. To avoid all this confusion T24 provides thefacility to generate these ids automatically

To summarize, Auto ID Generation is introduced in T24

To reduce the overhead involved in keying in a unique id for each record in each

application.

And data stored can be accessed easily with the help of a unique id.



4/26

Now lets see how to set up Auto ID Generation for an application. As a first step, the multi

va ue e , n t e app cat on s popu ate . you ave a newapplication for which the id is to be generated automatically, then multi value this field and

key in the Application ID. Dont forget to commit and authorize the record. By default, youwill find several applications for which the id is generated automatically.

1. ACCOUNT, FUNDS.TRANSFER, FOREX and others have been configured for Auto IDgeneration. These applications do not enforce auto id generation. The user can input an id of

his choice or use the id generated by auto id generation. You will learn later about how toenforce auto id generation.



5/26

As a second step, create an entry in another application, AUTO.ID.START for all the

app cat ons t at support auto generat on.

Through this application the start point for auto numbering is set up. This is particularlyrequired where the key of the application file with auto numbering is not a straight numeric.

Key generation can be either the standard type which read and update a record on theLOCKING file to be able to produce sequential id's or using UNIQUE.NO that creates an id

using a table of characters which is unique enough to remove the need for a locking update.Records in this application are company specific. Lets take a look at the fields in thisapplication.

ID: This field identifies the different records maintained on this application.

DESCRIPTION: This field is provided so that the user may load any notes that are useful

about what the record is to be used for.

It can contain upto 35 alphanumeric characters, type 'A'. It is a multivalue field. It is anoptional input.

APPLICATION: This indicates the application for which the start point for auto numbering isto be loaded.

It can contain upto 32 alphanumeric characters, type 'A'. It is a multivalue field associated

with ID.START. It is a mandatory input.

Must be a valid application with an optional DEPT.ACCT.OFFICER in the format:APPLICATION-DEPT.ACCT.OFFICER.

The application name must be present on the PGM.FILE with a type of H, U or W.

ID.START: This field is the key of the application file from which auto-numbering is to start. It

can contain upto 35 alphanumeric characters. It is a multivalue field associated withapplication. It is a mandatory field.



6/26

UNIQUE NO: This field can be YES or NULL. If set to YES this will invoke the generation

of transaction id's based on system generated values.

When set YES, it triggers auto generation of sequences using default characters (1-9 andB-Z - excluding vowels).

Dependent on the use of the BASE.TABLE and ID.LENGTH fields, the sequence generatedwill contain alpha, numeric or both in the key, subject to the length allowed. The system willgenerate a value based on the criteria set and check if it is used. If used, it will retry until aunique value is found.

There is no exclusive lock placed on the LOCKING file when the next available sequence is

requested. A record will be written to the LOCKING file with a name like.UNIQUE .

BASE TABLE: It is used only when UNIQUE.NO is set. It contains a list of characters that

can be used in the building of the unique id. If left blank and UNIQUE.NO is set the systemwill use numbers in the range 1-9 and alpha characters in the range B-Z. Vowels areexcluded

ID.LENGTH: It is used in conjunction with UNIQUE.NO to restrict the maximum length of

any generated id.

If settings in UNIQUE.NO and BASE.TABLE are made it may be advisable to restrict thelength of the id to the standard format of 12, 14 or 16 depending on the application. If left

blank the UNIQUE.NO & BASE.TABLE combination may extend the id length to providesufficient unique id's.



7/26

Lets attempt to automatically generate the id for the CUSTOMER application. You have

a rea y a e t s app cat on to t e recor n app cat on. reate a recor n t eAUTO.ID.START application as illustrated with the ID starting at 100000. Dont forget to

commit and authorize the record. Note that you have not set the Unique No field.



8/26

Now that you have created the record for the customer application in AUTO.ID.START, lets

nput a customer recor an un erstan w at appens.

But before you proceed with that, lets take a quick look at the various ways to input a newrecord.

1. As you must be aware of by now, the most frequently used method to input a newrecord is to click on the new deal icon when the application is launched. In thisillustration you have launched the CUSTOMER application and a new customer can beinput by clicking the new deal icon.

2. The next method to input a new record is by typing the followed by a

space and the function for input- I , followed by another space and the keys F3 in thecommand line.

3. If you are invoking a version created for the application then a record can be input by

typing I F3 in the command line

4. If you are working in a classic mode then type in the application name, then the functionfollowed by Ctrl+F+Enter. This opens a new record for the application



9/26

Going back to the example of automating the ID generation for customer application, you

rst ta e a oo at t e sequence t at was ast use y oo ng at t eapplication.

1. A record for the customer application is present in the LOCKING application as

illustrated. From the record you understand that the last id generated for the customer is1000045. The field CONTENT holds the last id generated for an application.

2. Now lets understand what happens when you input a customer record using one of theways mentioned earlier. The value maintained in the LOCKING application for the

customer is incremented by one and returned as the id for the new record. Thus1000046 is the new customers record id.

3. This information is updated in the LOCKING application as well. The content in the

FBNK.CUSTOMER record now holds the new value, 1000046, the last generatedcustomer number.



10/26

1. If you look carefully at the record inCOMPANY where you entered the applications for

w c auto generat on as to e tr ggere , you w not ce t at t ere are a ewapplications for which there is no record in AUTO.ID.START but has an entry in

COMPANY. Then how do you suppose the ids are automatically generated?

2. For instance lets a look at the ID for a Loans and Deposits application. The id has theformat

LD followed by the year in 2 digits and the Julian Date in 3 digits and finally a 5 DigitSequence Number. The ID is not straight numeric.

3. For such applications the ID generation logic is built into the application itself. The

subroutine EB.FORMAT.ID is invoked to accomplish this.



11/26

Lets learn how to enforce auto id generation for an application. Lets take the example of the

app cat on aga n. o en orce auto generat on su x t e app cat on w t meaning mandatory. If you do not suffix M to your application, then a record can be input

with the id entered by the user as well as it can be generated automatically.



12/26

If you attempt to input a new record with an id of your choice, it shows an error message. In

t s ustrat on, a customer recor s nput w t an an t s ows t e messageNew Record By Autom.Id only.



13/26

Lets trigger auto id generation for another application namely Funds Transfer.

1. Attach the application to the PGM AUTOM ID field in theCOMPANY application as

illustrated.

2. As a second step, a record is created in the AUTO.ID.START application and the fieldUnique No is set to YES.

The field Base Table should contain a minimum of 10 characters from which the unique

id is to be formed. It can be numbers entered as 123456789 or can contain anyalphabet excluding vowels. Since the base table is blank in this illustration, the FTrecord id with contain both alphabets and numbers generated randomly.

3. A new record is created in the LOCKING Application with id as

FUNDS.TRANSFER.UNIQUE as shown. This record is used to ascertain the length ofthe ID.



14/26

Now when you input an FT contract you see that the sequence number part of the id

- s a com nat on o a p a ets an num ers. t e sequence num er generateshould contain only numbers or alphabets, use the Base Table field to set it up as

explained before.



15/26

1. Lets modify the FUNDS.TRANSFER record so that the sequence number starts with

. emove t e c ec rom t e un que no e . on t orget to comm t an aut or zethe record

2. The contents of the LOCKING application for FT is illustrated. The last id used in the

generation of FT contracts is 90002. The next sequence number in the sequence wouldbe 90003.



16/26

1. For the FUNDS.TRANSFER application you have not enforced auto id generation by

su x ng t e app cat on w t w e sett ng t up n t e recor n t eapplication. So one can input an id to create a new record as well. Here a new record

has been created with the ID containing 90005 as the sequence number. Is theLOCKING application updated with the id that the user typed in? No.

2. The contents in the LOCKING application remains unchanged. The LOCKINGapplication is only updated with the ids that are generated using any one of the

methods that you learnt before.



17/26

If you attempt to generate a record using the new deal icon, it will follow the sequence

present n t e app cat on. o t e sequence num er use to create a newcontract is 90003. Use of the new deal icon follows the old sequence.



18/26

What if the sequence approaches an id that was already generated manually and a record

ex sts

The existing record is displayed to the user instead of a new blank record. Lets understandthe same using the FT contract.

1. The last id used in the sequence of auto id generation is 90008. The next id that shouldbe generated is 90009. But a record has already been input with this id.

2. When you attempt to create a new record by clicking the new deal icon, it opens theexisting FT contract input previously.



19/26

1.What if you want to change the sequence of numbers being generated?

2. Do you create a new record in AUTO.ID.START for our application?

2.1 NO

3. You must edit the existing record in AUTO.ID.START

4.When modified and authorized, it changes the LOCKING record accordingly, thus startingthe new sequence



20/26

1. What if the sequence number that we follow for all contract based applications isnt

su c ent or a ays transact ons

2. You must remember that the Julian date will change only during COB

3. Sequence number can now contain letters of the English Alphabet (Without A E I O U)thus giving more IDs per day in T24

4. Letters to be part of the ID is decided by users using the fields Unique ID, Base Table, IDLength available in AUTO.ID.START.

5. Not all applications in T24 support this sort of ID generation



21/26

As seen earlier, the following has to be setup for generating more ids.

1. Unique No field must be set to YES

2.No Special Characters like ampersand, dollar, hash, asterisk and others are allowed.

3.BASE.TABLE field must have a minimum of 10 digits.

4. Example values for Base Table field are TRSBW12349 , 87631TRNG , 1234567895 ,BCDFGHJKLM , 25DDW1671Y.

5.Zero is included even without having in the Base Table field.



22/26

1. An application that supports auto id generation will have its name specified in the field

PGM AUTOM ID in the COMPANY record True / False

Answer :

2. The FBNK.CUSTOMER record in the LOCKING application holds the list of customer ids- True / False

Answer:

3. The FUNDS.TRANSFER application has its own built-in id generation logic - True / False

Answer:

4. To make auto id generation mandatory , specify the application name in the COMPANYrecord True / False

Answer:

5. The characters allowed in the unique id are specified in the BASE.TABLE field of

AUTO.ID.START application - True / False

Answer:



23/26

1. Application that supports auto id generation will an entry in the field PGM AUTOM ID of

the COMPANY record

2. Applications that support auto id generation should have an entry in AUTO.ID.START

3. To make Auto ID generation mandatory, suffix application name with M in theCOMPANY record

4. Last generated id is updated in LOCKING record

5. Letters to be part of the ID can be decided by users using the fields Unique ID, BaseTable, ID Length in AUTO.ID.START



24/26

You have learnt about automatic auto id generation for each record in an application. You

will now be able to,

1.Explain the need for Auto ID Generation in T24

2. Understand how it works

3. Set it up for your own applications in T24



25/26CUS2.Auto ID Generation In T24-R10.01


26/26

CUS2[1].Auto ID Generation In T24-R10.01.pdf

Documents

Transcript of CUS2[1].Auto ID Generation In T24-R10.01.pdf