cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Treasury: Accruals for Cut Over Fixed Deposit Delas

Former Member
0 Kudos

Hello Experts,

I have a query regarding, Posting of Accruals for Fixed Deposit deals uploaded as part of cut over.

Below is the process presently taken care of,

  • We have uploaded all the open deals as on cut over date, i.e. as on 1st January 2017, through T.Code "TBB1_LC".
  • Later for all open deals exists as on 1st January 2017, we have uploaded entire Accrual amount through manual JV posting and not through TBB4. I.e. we have passed direct JV entry.

Now i want to post Accruals as on 30th September 2017, i.e. i am looking to generate accruals from 1st January till 30th September 2017. When i am executing T.Code "TBB4" and selecting particular deal, system is passing entry for fist date of FD creation till 30th September 2017. I.e. if my FD is created as on 1st April 2016 then system is showing accrual entry from 1st April 2016 till 30th September 2017 an not from 1st January 2017.

Can you please let me know, whether our approach towards posting of cut over data for accrual was correct or is there different way for post accruals for Cut Over deals.

If my approach was correct, how can i post accruals for present quarter i.e from 1st January till 30th September 2017.

Regards,

Jignesh

Accepted Solutions (1)

Accepted Solutions (1)

grigoriy_babitskiy
Active Contributor
0 Kudos

Hello,

What about standard legacy data transport?

SPRO => Financial Supply Chain Management => Treasury and Risk Management => Transaction Manager => General Settings => Tools => Legacy Data Transfer => ...

For example you enter all your data for your transactioins in tr. TPM63C and then start TPM63. Then all your deals will get its values.

Former Member
0 Kudos

Hello,

Thank you for your answer.

For Legacy Data transfer, we have uploaded deals through BDC and then posted it through TBB1_LC and it is working fine for fixed deposit.

Regarding my question for Fixed deposit accruals, it is solved now.

Regards,

Jignesh

Answers (0)