Could not find flow to be reversed in TPM10

[Former Member]

Dear All,

Business Scenario:

A forward contract is created. This forward contract should be settled once created but the user A forgot to settle this. On maturity of this forward contract, another user has executed TPM18. Then, to close this transaction, user A realized this has not been settled. User A realized when he needs to perform TBB1.[Rightfully - TPM18 must be done after TBB1]. After TBB1, another TPM18 was carried out by User B. Note that the TBB1 and TPM18 was done in a mass and not by by transaction. So now, in GL, there is 2 transactions coming from TPM18. One of which needs to be reversed.

I have investigated and need to find some solution - why is TPM18 can be executed before TBB1? Why is it that TPM18 is allowed for 2nd time? But for now, I'm interested to reverse the transaction first - which is double in GL.

What I've done - Research and reading some OSS note on TPM18 and TPM10 eg OSS 797735:

I run TPM13 and I've selected - OTC Trans. and flows to be reversed. I can see that there are a few transactions to be reversed - ToR. When I use this transaction in TPM10 - Business Transaction to be reversed - I get the following message:

You have not selected any business transactions

Message no. TPM_TRD1026

Some of the correction notes is not applicable since we are using ECC 600.

Anyone has similar problem and manage to rectify? Thanks.

Regards

Fauzi

[Former Member · Accepted solution]

Hi,

What I understand from your post that derived flows have been posted using TPM18 for single transaction multiple times.

Firstly, if its the case, there may be a program error or a customization error which caused generating flows in duplicate - if so you have to notify this to sap or correct the customization duly identified.

Secondly, if the case is with different transactions, you have to probably reverse the transaction which duplicated, then only flows will be marked with ToR and can be fully marked as reversed by running TPM10.

Regards

Prasad AV

[jasmine_li · Accepted solution]

Hi,

It is in fact the standard behavior that you are able to post the

derived business transaction with TPM18 before the main flows are

posted.

During TBB1, the posting of the main flows will cause a recalculation of

these derived flows as the rates might have changed.

This means that the 'old' posted flows will be set to 'to be reversed'

and new ones will be generated that you may fix afterwards with TPM18.

The 'old' posted flows with status 'to be reversed'

have to be reversed with TPM10 now.

For reversing the derived business transactions with tpm10, please

make sure to select via the the option

'Limit by Subledger Position'.

If you want to avoid that you may post with TPM18 before TBB1, please

see soft modification note 944311.

The coding of note 944311 may be already on your system - but as it

is a soft modification note, you will have to activate it as described

in the long text of the note and in 732499.

After the activation, you will not be able anymore to post the derived

flows (e.g. gains and losses) before you have posted the main flows.

If I understand correctly, this is what you require.

Best regard,

Jasmine

[Former Member · Accepted solution]

Hi Jasmine,

Thanks for your reply. FYI - I've contacted SAP, and their advised is the same as your advise - to use the u2018Limit by Sub Ledger Positionu2019 BUT I feel you have explained better and have given me other options (OSS notes to refer) to avoid this problem to occur in future.

Problem solved and points were awarded for your answer.

Thank you.