How to automatically block for payment a document reopened during FF.5 bank statement import?

[TASM]

Olá Comunidade!

Hello Community!

I'm facing a functional challenge in the Financial Accounting (FI) module of SAP S/4HANA 2023 On-Premise, and I’d appreciate your help!

I'm trying to implement a solution where documents that are automatically reopened during the bank statement import via transaction FF.5 are automatically blocked for payment.

Scenario:

The bank sends, within the statement, a payment rejection instruction.
During the execution of FF.5, based on the configuration in OT83, the system reverses the clearing and reopens the original document.

The business team would like this reopened document not to be picked up again automatically by the F110S payment job, until it is manually reviewed to confirm whether the payment should actually be made.

Objective:

To prevent inadvertently re-paying documents reopened by FF.5, by automatically applying a payment block (ZLSPR) during the FF.5 execution.

---

My question:

Is there any BAdI, user-exit, or configuration that allows documents reopened via FF.5 to be automatically blocked for payment?

Any guidance is much appreciated!

Thanks in advance!

[pmorais1985]

Hello,

Unfortunately not. I recommend you use a specific payment block for bank rejections and create variant run in fbl1n ( or a custom report) with this payment block and payment block is already a mass change field in fbl1n.

What would be very useful would be to write the return reason somewhere in the FI document, because it is only mapped in the febep table ( if you post the pain.002 for the rejections , if you post the bank rejections based on other format like camt.053 I also doubt that it is mapped in standard SAP delivered transformation).

Also what I can say is that int algorythm 060 has limitations and does not cover the down payment request case, so one needs to enhance the algorythm which I have done successfully.

Please note as well that by usinh posting type 9 ( recommended) there is no post processinh in feba bank statement available because SAP feb_bsproc does not read the return configuration... The return configuration is only read during the import.

If you have any ideas you like to share please mail me.

[pmorais1985]

I forgot to say, the users can also check the return reason in feba_bank_ statement though. But you need to use fbl1n and feba in paralell if you dont have some enhancement to write the return reason in the original FI documenthe

[TASM]

Hello Pmorais1985,

[TASM]

Hello Pmorais1985, thank you very much for your kindness in helping!

[TASM]

Hello Pmorais1985, Hello, thank you very much for your kindness in helping!