OVERRIDE and NO.OF.AUTH in APPLICATION

Dear all,
Recently I am developing control for FT and TT. The requirement is
1. if total amount under 10k, no authorisation required
2. if over 10k, required another person to authorise with correct override class which is 100k, 250k and 1M

My solution is create version routine which check if total amount over 10k, then set R.VERSION(EB.VER.NO.OF.AUTH) = 1, and another version routine throw override by using CALL STORE.OVERRIDE(CURR.NO)

should I attach reset NO.OF.AUTH routine to validation routine file in VERSION or should I attach it to input routine field?

Hi
the correct solution would be to set up OVERRIDE application. Use 0-auth VERSION. In case the inputting person can't approve OVERRIDE, the transaction goes to INAO status.

I don't have examples near me so please consult the manuals how exactly to do that.

Dear VK,

Thanks for reply.

How about routine for reset NO.OF.AUTH in version? After it attached to VERSION, I found out if total amount over 10k, the record become INAU rather than INAO.

Is that correct? Is there any negative effect to T24 and override system?

Hi
if you set up the OVERRIDE correctly, there's no need for any routine. Anyway, fiddling with global variables isn't a good thing to do...

Dear VK,

If NO.OF.AUTH set to 0 and no routine to reset this field in VERSION, how can avoid a inputer who has OVERRIDE.CLASS to self-authorise transaction?

During test I found a user who has 100k OVERRIDE.CLASS can self-authorise transaction over 100k. Ideally no matter what kind of OVERRIDE.CLASS user has, if transaction over limit, and it required another person with correct OVERRIDE.CLASS to authorise. In this case, need two persons who have 100k OVERRIDE.CLASS to finish a transaction which over 100K

Sorry about my English, I am not sure it is clear enough.

a user who has 100k OVERRIDE.CLASS can self-authorise transaction over 100k

strange, it should have gone to INAO...
Try to report this to Temenos.

You are right SUN, when a user has a certain OVERRIDE.CLASS and the VERSION is 0-authoriser he can do the transaction on his own - without a second person involved or going to INAO.

Setting NoOfAuth with a input routine works OK since years for me !

I was concerned about amending global var NO.OF.AUTH as VK mentioned. Thank for sharing your experience. I will go ahead and let end user test it :)

Hi
Just FYI.
In my case it didn't work for TCIB-generated FTs going to INAO... I don't remember all details but I had to find another way.
Also might depend on T24 release.