SPECIAL CHARGES AND TAXES HANDLING IN TT

  • jcosta
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 11 months ago #9563 by jcosta
Hi: our customer needs to have several commission and/or taxes attached to some TELLER.TRANSACTIONS, but they want to waive any of them (T24 waives ALL or none). If the waived value is a tax, it should be waived to the customer , but the bank will be paying, this means instead of debiting the customer accounts (debited for the rest of charges and the transaction), the waived tax has to be debited from PL.
Our solution: Create several LOCAL FIELDS to let the inputter flag which individual COMM/TAG will be waived and let T24 calculate each comm/tax amount. Create a VERSION ROUTINE to update the TT set of CHARGE FIELDS(32-39) to only include those that are not waived, BUT IT DOES NOT WORK...T24 will charge the customer ALL the comm/tax values. The routine was included either as validation, input, before auth or auth with the same results. The accounting part would be solved using EB.ACCOUNTING in an auth routine, but first we should only charge the non waived commissions/taxes.

Thanks for any help. Regards
JCOSTA

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

More
12 years 11 months ago - 12 years 11 months ago #9567 by jpb
Did you try to do

TT$CROSS.VAL.FLAG = 1
CALL TT.PERFORM.DEF.PROCESSING

[and use I_TT.COMMON]

after you change the fields 32-39 in your routine attached as input.rtn ??

Might work 'cause the charges (and attached tax) should only be recalculated for those hat are already filled (and they must be defined in TELLER.TRANSACTION). But I can't tell if other fields will be reset with this call.
Last edit: 12 years 11 months ago by jpb.

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

  • jcosta
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 11 months ago #9578 by jcosta
Thanks Andreas for your reply. I tried and didn´t work, after calling the TT.PERFORM.DEF.PROCESSING all 32-39 fields showed the original information, meaning the information BEFORE the change made by the INPUT routine. BTW, in TT.COMMON I didn't have the variable TT$CROSS.VAL.FLAG, but I included it, however the result was the same with or without the variable. To be in the same page, we are in R09.

Meanwhile, it is always good a workaround, but I don't like this workaround:
Change WAIVE.CHARGES core TT field to YES (T24 won´t charge any commision or tax) and using an AUTH.ROUTINE do the accounting of COMMISSIONS and TAXES calculated in LOCAL.FIELDS.

Hope we can find a better alternative.

Kind Regards,
JCOSTA

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

More
12 years 11 months ago #9601 by jpb
Sorry, the flag isn't part of I_TT.COMMON but defined in the routine we use and obviously also in TT.PERFORM.DEF.PROCESSING / TT.CROSSVAL.

Try including

COMMON/TT.CRSVAL/TT$CROSS.VAL.FLAG

in your code.
The following user(s) said Thank You: jcosta

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

  • jcosta
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 10 months ago #9842 by jcosta
THANK YOU VERY MUCH!! Your solution works PERFECT!!

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

  • Humble
  • Visitor
  • Visitor
12 years 10 months ago #10018 by Humble
Hello : Does this same solution work for FT?? What if I need to ask T24 in a routine to do the related COMM and TAX calculations? Thanks for your Help.

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

More
12 years 10 months ago #10019 by jpb
There is a routine FT.COMPLETE.XVALIDATION that is used in FT (so it expects R.NEW), but I'm not sure how to call and use it.

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

Time to create page: 0.090 seconds