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

Welcome to the Auto id Generation learning unit in T24. In this learning unit, you will learn a out out ow to auto automa matt ca y gene genera rate te or eac eac reco recorr n an app app cat cat on. on.

CUS2.Auto ID Generation In T24-R10.01

1

After completing this course, you will be able to 1.

Explai Explain n the the need need for for Auto Auto IID D Genera Generatio tion n in T24 T24

2.

Unde Unders rsta tand nd how how itit wor works ks

3.

Set it up up for for your your own own appl applica icatio tions ns in T24


2

Each application in T24 is made up of a number of records. Each record is indentified un qu que y w t t e e p o t s . ets ta e an examp e o a customer recor . ow o you diffe ifferrent entiat iate one cust custo ome merr fro from ano another ther? ? You use the the reco recorrd id to iden identtify ify each ach cust custo ome merr uniquely. ly. Now if you had to manually key key in the record id each time for a new custo stomer, it woul wo uld d be diff diffic icul ultt for for the the end end user user to deci decide de upon upon an uniq unique ue id. id. Imag Imagin ine e wh what at wo woul uld d happ happen en if ther here were seve severa rall user users s usin using g T24 T24 at the same same time. ime. Its poss possib ible le that hat mo more re than han one one use user cou could decid ecide e on the same same id for for the cust custo ome mer. r. To avoi avoid d all all this his con confusi fusion on T24 T24 pro provid vides the facili facility ty to gen genera erate te the these se id’s id’s aut automa omatic ticall ally y To summarize, Auto ID Generation is introduced in T24 • To reduce the overhead involved involved in keying in a unique unique id for each record in each application. • And data stored can be accessed easily with the help of a unique id.


3

Now lets see how to set up Auto ID Generation G eneration for an application. As a first step, the multi va ue e , nt e app cat on s popu ate . you ave a new application for which the id is to be generated automatically, then multi value this field and key in the Application ID. Don’t forget to commit and authorize the record. By default, you will find several applications for which the id is generated automatically. 1. ACCOUNT, FUNDS.TRANSFER, FOREX and others have been configured for Auto ID generation. 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 to enforce auto id generation.


4

As a second step, create an entry in another application, AUTO.ID.START for all the app app cat cat ons ons t at supp suppor ortt auto auto gene genera ratt on. on. Through this application the start point for auto numbering is set up. This is particularly required 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 the LOCKING 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 this application. ID: This field identifies the different diff erent 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 an optional input. APPLICATION: This indicates the application for which the start point for auto numbering is to 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 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 m ultivalue field associated with application. It is a mandatory field.


5

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 and B-Z - excluding excluding vowels). vowels). Dependent on the use of the BASE.TABLE and ID.LENGTH fields, the sequence generated will contain alpha, numeric or both in the key, subject to the length allowed. The system will generate a value based on the criteria set and check if it is used. If used, it will retry until a unique 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 system will use numbers in the range 1-9 and alpha characters in the range B-Z. Vowels are excluded 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 the length 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 com bination may extend the id length to provide sufficient unique id's.


6

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. r ea eate a recor n t e with the ID starting at 100000. Don’t forget to AUTO.ID.START application as illustrated with commit and authorize the record. Note that you have not set the ‘Unique No’ field.


7

Now that you have created the record for the customer application in AUTO.ID.START , lets nput put a cust custom omer er reco recorr an un erst erstan an w at app appens. ens. But before you proceed with that, lets take a quick look at the various ways to input a new record. 1.

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

2. The next method to input a new record is by typing typing the followed by a space and the function function for input- ‘I’ , followed by another space and the keys ‘F3’ in the command 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 then type in the application name, name, then the function function followed by Ctrl+F+Enter. This opens a new record for the application


8

Going back to the example of automating the ID generation for customer application, you rst ta e a oo oo at t e sequence t at was as ast use y oo oo ng at t e application. 1.

A record record for the customer customer applicatio application n is presen presentt in the LOCKING application as illustrated. From the record you understand that the last id generated for the customer is 1000045. The field CONTENT holds the last id generated for an application.

2.

Now lets lets understand understand what happen happens s when you you input a customer customer record record using one one of the the ways 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. Thus 1000046 is the new customer’s record id.

3.

This inform informati ation on is upda updated ted in the the LOCKING application as well. The content in the FBNK.CUSTOMER record now holds the new value, value, 1000046, the last generated customer number.


9

1.

If you you look look care careful fully ly at at the the recor record d in COMPANY 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 ew applications 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 instanc instance e lets lets a look at the ID for a Loans and Deposit Deposits s applicatio application. n. The id id has the the format LD followed by the year year in 2 digits and the Julian Date in 3 digits and finally a 5 Digit Sequence Number. The ID is not straight s traight numeric.

3. For such applications the ID ID generation logic is built into the application application itself. The subroutine EB.FORMAT.ID is invoked to accomplish this.


10

Lets Lets lear learn n how how to enfo enforc rce e auto auto id gene genera rati tion on for for an appl applic icat atio ion. n. Lets Lets take take the the exam exampl ple e of the the app cat on on aga n. n. o en or o rce auto generat on on su x t e app cat on on w t ‘ mean me anin ing g ma mand ndat ato ory. ry. If you do not not suf suffix fix ‘M’ ‘M’ to your our app applica licattion, ion, then hen a reco record rd can can be inp input with with the the id ente entere red d by the the user user as we well ll as it can can be gene genera rate ted d auto automa mati tica call lly y.


11

If you attempt to input a new recor cord with an id of your choice, ce, it shows an error messa ssage. In t s ustrat on, a customer recor s nput w t an an t s ows t e message “New “New Reco Record rd By Auto Autom. m.Id Id only only”. ”.


12

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

Attach Attach the the ap applicat plication ion to to the the PGM PGM AUTOM AUTOM ID ID field field in the COMPANY application as illustrated.

2.

As a seco second nd step step,, a recor record d is crea created ted in the the AUTO.ID.START application and the field Unique 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 any alphabet excluding vowels. Since the base table is blank in this illustration, the FT record id with contain both alphabets and numbers generated randomly.

3. A new record record is created created in the LOCKING Application with id as FUNDS.TRANSFER.UNIQUE as shown. This record is used to ascertain the length of the ID.


13

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 generate should contain only numbers or alphabets, use the ‘Base Table’ field to set it up as explained before.


14

1.

Let Lets mo modify dify 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 or orget to comm t an aut or ze the record

2. The contents 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 would be 90003.


15

1.

For For the FUNDS.TRA TRANS NSF FER applica licattion you have ave not enforced auto id generation by su x ng t e app ca c at on w t ‘ w e sett ng t up n t e recor n t e application. So one can input an id to cre create a new record as well. ll. Here a new record has been created with the ID containing 90005 as the sequence number. Is the applic icat atio ion n upda update ted d with with the the id that that the the user user type typed d in? in? No No.. LOCKING appl

2.

The The cont conten ents ts in the the LOCKING application remains unchanged. The LOCKING application is only updated with the id’s that are generated using any one of the methods that you learnt before.


16

If you attempt to generate a record using the new deal icon, it will follow the sequence pres presen entt n t e app app cat cat on. on. o t e sequ sequen ence ce num num er use use to crea create te a new new contract is 90003. Use of the new deal icon follows the old sequence.


17

What if the sequence approaches an id that was already generated manually and a record ex sts sts The existing record is displayed to the user instead of a new blank record. Lets understand the same using the FT contract. 1.

The last last id used in the sequenc sequence e of auto auto id generati generation on is 90008. 90008. The next id id that should should be generated is 90009. But a record has already been input with this id.

2.

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


18

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 starting the new sequence


19

1. What if the sequence number that we follow for all contract based applications isn’t su c ent ent or a ays ays tran transa sact ct ons 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 (W ithout A E I O U) thus giving more ID’s per day in T24 4. Letters to be part of the ID is decided by users using the fields Unique ID, Base Table, ID Length available in AUTO.ID.START . 5. Not all applications in T24 support this sort of ID generation


20

As seen earlier, the following has to be setup for generating more ids. 1. ‘Unique No’ field must be set to ‘YES’ ‘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 Base Table field are TRSBW12349 , 87631TRNG , 1234567895 , BCDFGHJKLM , 25DDW1671Y. 5.Zero is included even without having in the Base Table field.


21

1. An application that supports supports auto id generation will have its name name specified in the field field PGM AUTOM ID in the COMPANY record – True / False Answer : 2. The FBNK.CUSTOMER record in the LOCKING LOCKING application holds the list of customer ids - True True / False False Answer: 3. The FUNDS.TRANSFER application has its own built-in id generation generation logic - True / False Answer: 4. To make auto id generation mandatory , specify the application name in the COMPANY record record – True / False Answer: 5. The characters allowed in the unique id are specified in the BASE.TABLE field of AUTO.ID.STAR AUTO.ID.START T application application - True / False Answer:


22

1.

Applicatio Application n that support supports s auto id id generatio generation n will an entry entry in the field PGM PGM AUTOM ID of the COMPANY record

2.

Applicatio Applications ns that support support auto auto id generat generation ion should should have have an entry entry in AUTO.ID.S AUTO.ID.START TART

3.

To make Auto Auto ID generat generation ion mandator mandatory, y, suffix suffix applicat application ion name with M in the COMPANY record

4.

Last Last gener generate ated d id is upda updated ted in LOCKI LOCKING NG record record

5.

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


23

You have learnt about automatic auto 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


24


25


26

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

Recommend Documents