TELLER.ID in different branches

  • premat_mil
  • Topic Author
  • Offline
  • New Member
  • New Member
More
6 years 2 months ago #21768 by premat_mil
TELLER.ID in different branches was created by premat_mil
Hi,

Is it possible to define same teller.id to work in different branches without getting "teller id not defined in this branch" error ?

R10 T24.

Thank you

Please Log in or Create an account to join the conversation.

More
3 years 8 months ago #23085 by yohan_madu
Replied by yohan_madu on topic TELLER.ID in different branches
Hi

I am wondering did you find a way to overcome the issue you have mentioned long time ago

Please Log in or Create an account to join the conversation.

  • silvergem
  • silvergem's Avatar
  • Offline
  • Elite Member
  • Elite Member
  • TAFC|R12/R13, TAFJ|R20
More
3 years 8 months ago - 3 years 8 months ago #23092 by silvergem
Replied by silvergem on topic TELLER.ID in different branches
You can enable multiple teller id per user. I presume its different Teller ID...

Based on TCSP User Guide related to Multi-Till:
1. Able to link two or more tills belonging to a particular user.
2. Able to open the linked tills automatically when the master till is opened.

Scenario Example:
User LISA2 has two tills - Till 0002 and Till 0003.
Till 0002 is the master till and Till 0003 is called the linked or child till.
Therefore, when Till 0002 is opened, then Till 0003 should also be opened automatically.

NOTE: This is applicable to only opening of tills. Closure of tills has to be done individually following traditional teller concepts.
In the above case, if the user also had one more till , for example 0005, and consider it has not been linked to till 0002, then opening of till 0002 does not result in opening of till 0005,since it has not been linked.

WARNING: Instead of TELLER.ID 0002, if TELLER.ID 0006 is linked (user is LISA2), the system raises a Till does not exist for Current User error at check fields( as shown in the screen shot below)
Last edit: 3 years 8 months ago by silvergem.

Please Log in or Create an account to join the conversation.

Time to create page: 0.069 seconds