Foreword
This article Introduces how to reverse payments and postings for cash flows from financial transactions created in Treasury and Risk Management (TRM) solution of S/4HANA Public Cloud, under the circumstance that the relevant payment request has been processed (cleared) by F111 and payment document has been created by F111.
Notes:
Introduction
The following two articles already introduced how to reverse payments and postings for cash flows in transactions, under the circumstances that relevant payment request has NOT been processed by F111 (which mean the corporate-initiated payment has not been really done):
If relevant payment request has been cleared by F111 and payment document has been created by F111, then additional handlings for resetting clearing of payment document created by F111 and resetting the clearing of payment request by F111 are needed before running TPM10 to reverse payment request and posting from TRM side (as already introduced in above two articles).
Example:
Some Screen-shots to Illustrate Current Situation:
TM_53: the nominal interest flow has posting information ‘Posting carried out’ and payment status ‘Paid - payment mode’.
F111: check payment log, the payment document has been created.
F8BT: payment request is ‘cleared’.
TPM13: status of position flows (in all valuation areas) of the nominal interest is ‘F’ (Fixed).
TPM20: posting journal entries are available for this nominal interest in all valuation areas.
Click the object key of payment valuation area to check the journal entry in leading ledger, the line item of payment request clearing account (credit side) has been cleared with the line item of payment request clearing account (debit side) in the payment document created by F111.
Try to Reverse via TPM10:
Follow the steps described in Reverse Payments and Postings from TRM Transactions (2) - via Reversal of Specific Cash Flow, reverse the cash flow of nominal interest in the transaction.
Then execute TPM10, which will raise the error message PZ096 “Payment request XX has been cleared: Reversal not possible”, and TPM10 can’t reverse the posting in leading ledger because its payment request clearing account line item has been cleared.
Under this situation, you have to reverse the payment document and reset clearing of the payment document from FI side, and reset the clearing of payment request, before running TPM10 to reverse the payment request and postings from TRM side.
Step-by-Step Guide:
1. Access FBRA, enter the payment document number relevant information, and then choose Reset cleared items.
Choose Reset and Reverse in the dialog box.
On the next dialog box, choose a Reversal Reason, and the choose Continue.
The following message appears and confirms reversal and reset clearing of payment document have been done.
You may also check the journal entry of nominal interest in leading ledger, and will find that the clearing information for payment request clearing account line item is gone after running FBRA.
2. Access F8BW, enter the parameters, and choose Run.
The following message appears and confirms that clearing of payment request has been set.
About ‘Mark for Cancellation’:
Check in F8BT: now this payment request can only be seen when checkbox ‘Open’ is selected, and another change is that the ‘indicator: Released for Payment’ = ‘X’ is gone after running F8BW, this is due to that ‘Mark for Cancellation’ was flagged when running F8BW. Without ‘indicator: Released for Payment’ = ‘X’, F111 is not able to process this payment request, even though the payment request is ‘Open’.
3. Now it is able to run TPM10 successfully to reverse the payment request and postings arising from nominal interest flow.
After running TPM10, you can also check the following areas:
Since the effects in above mentioned areas are quite similar to descriptions in Reverse Payments and Postings from TRM Transactions (2) - via Reversal of Specific Cash Flow, further screen-shots are not provided here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
7 | |
7 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |