TT.STOCK.CONTROL not updated
- madalina.herghelegiu
- Topic Author
- Offline
- New Member
Less
More
- Posts: 5
- Thank you received: 0
9 years 9 months ago #16851
by madalina.herghelegiu
TT.STOCK.CONTROL not updated was created by madalina.herghelegiu
Hi,
Following repeated withdrawals and deposits, sometimes deleted or authorized, created by a TELLER.ID, TT.STOCK.CONTROL is not properly updated.
Did you ever encounter this situation? Do you know any reason of this behavior? We were not able to replicate.
Thanks in advance!
Following repeated withdrawals and deposits, sometimes deleted or authorized, created by a TELLER.ID, TT.STOCK.CONTROL is not properly updated.
Did you ever encounter this situation? Do you know any reason of this behavior? We were not able to replicate.
Thanks in advance!
Please Log in or Create an account to join the conversation.
- armin
- Offline
- Elite Member
- “So long - and thanks for all the fish!”
Less
More
- Posts: 300
- Thank you received: 57
9 years 9 months ago #16854
by armin
Replied by armin on topic TT.STOCK.CONTROL not updated
I can imagine that its getting confused when you would go below zero depending on the sequence of deposit - withdrawal - reversal (the reversal of the deposit will remove more than is left over after the withdrawal).
But there should be an error when this happens.
But there should be an error when this happens.
The following user(s) said Thank You: madalina.herghelegiu
Please Log in or Create an account to join the conversation.
- madalina.herghelegiu
- Topic Author
- Offline
- New Member
Less
More
- Posts: 5
- Thank you received: 0
9 years 9 months ago #16855
by madalina.herghelegiu
Replied by madalina.herghelegiu on topic TT.STOCK.CONTROL not updated
Yes, there are several restrictions (ex: the denominations units cannot be below 0), and overrides (ex: when you create a withdrawing based on an unauthorized deposit). Also, there are locking triggered on TT.STOCK.CONTROL when a specific TELLER.ID is in use.
But we suppose that this locking isn't working in all cases, and sometimes we have this situations in our live environment.
We assume that the scenario that cause our issue is like this:
- TELLER.ID1 gets an error of insufficient stock during a withdrawal
- TELLER.ID2 tries to transfer to TELLER.ID1 the missing denominations
- The result is TT.STOCK.CONTROL for TELLER.ID2 is successfully updated, but for TELLER.ID1 is not.
Thank you for your response.
But we suppose that this locking isn't working in all cases, and sometimes we have this situations in our live environment.
We assume that the scenario that cause our issue is like this:
- TELLER.ID1 gets an error of insufficient stock during a withdrawal
- TELLER.ID2 tries to transfer to TELLER.ID1 the missing denominations
- The result is TT.STOCK.CONTROL for TELLER.ID2 is successfully updated, but for TELLER.ID1 is not.
Thank you for your response.
Please Log in or Create an account to join the conversation.
Time to create page: 0.080 seconds