- Forum
- T24 Technical Discussions
- T24 Development & Customization
- Version customization in Teller module
×
Discuss on Template programming, jBASE programming, Enquiries, No-File enquiry, Enquiry routines, Version, Version routines, Menus, Abbriviations, Creating local reference fields, Fast path enquiries, Creating charts and graphs, Generating Reports, Deal slips, Straight through processing, Multi Company and Multi Book setup, Tabbed screens, Composite Screens, T24 API, etc...
Version customization in Teller module
- pokharel
- Topic Author
- Offline
- Senior Member
-
Less
More
- Posts: 49
- Thank you received: 1
9 years 6 months ago #16422
by pokharel
Version customization in Teller module was created by pokharel
Hello all,
I am trying is customize version of TELLER,TEST. I want to add category filed (only for display) as no input filed based on account number input by teller. In TT module, there is no category filed. How I can get category in this version based on account number input?
Thank you
Best,
Suresh Pokharel
I am trying is customize version of TELLER,TEST. I want to add category filed (only for display) as no input filed based on account number input by teller. In TT module, there is no category filed. How I can get category in this version based on account number input?
Thank you
Best,
Suresh Pokharel
Please Log in or Create an account to join the conversation.
- jpb
-
- Offline
- Moderator
-
- TAFj-R20 - 'unix'
Less
More
- Posts: 2854
- Thank you received: 649
9 years 6 months ago #16431
by jpb
Replied by jpb on topic Version customization in Teller module
Define a local field on TELLER as
USR.FIELD.NAME = ACC.2.CAT
USR.TYPE = I
USR.FIELD.NO-1 = ACCOUNT.2;
USR.FIELD.NO-2 = SUBR('ENQ.TRANS','ACCOUNT',@1,'CATEGORY')
then define in your VERSION at the location of ACCOUNT.2 --> I.LINK = ACC.2.CAT
and insert after this the new field with
FIELD.NO = ACC.2.CAT
COLUMN = <your choice>
I.DESC = YES
Should work with ACCOUNT.1 as well but only when not used as MV.
USR.FIELD.NAME = ACC.2.CAT
USR.TYPE = I
USR.FIELD.NO-1 = ACCOUNT.2;
USR.FIELD.NO-2 = SUBR('ENQ.TRANS','ACCOUNT',@1,'CATEGORY')
then define in your VERSION at the location of ACCOUNT.2 --> I.LINK = ACC.2.CAT
and insert after this the new field with
FIELD.NO = ACC.2.CAT
COLUMN = <your choice>
I.DESC = YES
Should work with ACCOUNT.1 as well but only when not used as MV.
The following user(s) said Thank You: pokharel
Please Log in or Create an account to join the conversation.
- pokharel
- Topic Author
- Offline
- Senior Member
-
Less
More
- Posts: 49
- Thank you received: 1
9 years 6 months ago #16477
by pokharel
Replied by pokharel on topic Version customization in Teller module
Dear jpb,
Can you please elaborate on creating local field in teller as you specified. I am using R10.
Head Office LOCAL.TABLE INPUT
TABLE.NO.......... ACC.2.CAT
1. 1 GB DESCRIPTION. ACC.2.CAT
2. 1 GB SHORT.NAME.. ACC.2.CAT
3 MAXIMUM.CHAR...... 5
4 MINIMUM.CHAR......
5 CHAR.TYPE......... A
6. 1 VETTING.TABLE..
7. 1. 1 GB REMARK...
8. 1 APPLICATION....
As, I am confused on this:
Define a local field on TELLER as
USR.FIELD.NAME = ACC.2.CAT
USR.TYPE = I
USR.FIELD.NO-1 = ACCOUNT.2;
USR.FIELD.NO-2 = SUBR('ENQ.TRANS','ACCOUNT',@1,'CATEGORY')
Thank you
Best,
Pokharel
Can you please elaborate on creating local field in teller as you specified. I am using R10.
Head Office LOCAL.TABLE INPUT
TABLE.NO.......... ACC.2.CAT
1. 1 GB DESCRIPTION. ACC.2.CAT
2. 1 GB SHORT.NAME.. ACC.2.CAT
3 MAXIMUM.CHAR...... 5
4 MINIMUM.CHAR......
5 CHAR.TYPE......... A
6. 1 VETTING.TABLE..
7. 1. 1 GB REMARK...
8. 1 APPLICATION....
As, I am confused on this:
Define a local field on TELLER as
USR.FIELD.NAME = ACC.2.CAT
USR.TYPE = I
USR.FIELD.NO-1 = ACCOUNT.2;
USR.FIELD.NO-2 = SUBR('ENQ.TRANS','ACCOUNT',@1,'CATEGORY')
Thank you
Best,
Pokharel
Please Log in or Create an account to join the conversation.
- jpb
-
- Offline
- Moderator
-
- TAFj-R20 - 'unix'
Less
More
- Posts: 2854
- Thank you received: 649
9 years 6 months ago #16478
by jpb
Replied by jpb on topic Version customization in Teller module
Hi Pokharel,
I'm really talking about a local field to be defined in STANDARD.SELECTION directly, not a LOCAL.TABLE definition.
I'm really talking about a local field to be defined in STANDARD.SELECTION directly, not a LOCAL.TABLE definition.
Please Log in or Create an account to join the conversation.
- pokharel
- Topic Author
- Offline
- Senior Member
-
Less
More
- Posts: 49
- Thank you received: 1
9 years 6 months ago #16479
by pokharel
Replied by pokharel on topic Version customization in Teller module
Hi jpb,
When I commit SS I TELLER, with Accept Overrides
override I-Desc field ACC.2.CAT.1 with Subroutine type is Incompatible with J24.
It works. But It doesn't display category of account of another lead company.
Best Regards,
pokharel
When I commit SS I TELLER, with Accept Overrides
override I-Desc field ACC.2.CAT.1 with Subroutine type is Incompatible with J24.
It works. But It doesn't display category of account of another lead company.
Best Regards,
pokharel
Please Log in or Create an account to join the conversation.
- jpb
-
- Offline
- Moderator
-
- TAFj-R20 - 'unix'
Less
More
- Posts: 2854
- Thank you received: 649
9 years 6 months ago #16480
by jpb
Replied by jpb on topic Version customization in Teller module
Yes I-desc are not liked any more, but we still use them.
If you have to get CATEGORY from another company use a local routine instead of ENQ.TRANS to read it from the correct file.
If you have to get CATEGORY from another company use a local routine instead of ENQ.TRANS to read it from the correct file.
Please Log in or Create an account to join the conversation.
- Forum
- T24 Technical Discussions
- T24 Development & Customization
- Version customization in Teller module
Time to create page: 0.102 seconds