SAPCodeMonkeyThe Payment Run in S/4HANA (F110)
F110 itself barely changed on S/4HANA — but almost everything around it did. Migrations that scope this as a UI swap find the payment-medium layer during testing.
Ask whether the payment run changed on S/4HANA and the honest answer is: F110 itself barely changed, but almost everything around it did. Migrations that scope this as a user-interface swap find the payment-medium layer during testing. The transaction was never the hard part.
F110 wasn't deprecated — it was deployed out of reach
In S/4HANA on-premise, F110 still works: the same four tabs, the same proposal-then-run rhythm, full drill-down into the payment proposal. What removes it is not SAP retiring it but where you run. In public cloud, F110 is not available — not because it was deprecated, but because SAP GUI is not there. On-premise you get to choose; in public cloud the decision is already made for you, and the Fiori gaps below become mandatory rather than optional.
Manage Automatic Payments, and its two gaps
The Fiori equivalent is Manage Automatic Payments (app F0770), and it is genuinely better in the ways people notice first: one screen for every selection option, where F110 makes you walk four tabs. But it has two real gaps you must plan around. First, there is no Printout / data-medium tab — you cannot select program variants at all. Second, there is no drill-down on the proposal: you see one payment and two exceptions without being able to see which documents sit behind them. That second gap is why plenty of AP teams keep using F110 on-premise, and it is a genuine decision rather than resistance to change. Ask your AP team how often they drill into a proposal before you migrate them.
The payment advice trap
Because the Printout tab is gone, SAP hardcoded the app to look for a specific variant name under program RFFOAVIS_FPAYM. If that variant is not in your system, payment advices will not generate — no matter what else you try. It is a silent failure with no obvious error, which is the worst category. KBAs 2863917 and 2794915 cover the scenarios and a workaround involving a BAdI and a template payment run created in SAP GUI. Create the variant and test that advices actually generate before a user reports that suppliers stopped receiving them.
The real change is underneath
The substantive change is not the transaction but the payment-medium layer. The classic payment medium programs — the RFFO* family — are effectively obsolete; the standard formats are now delivered through the Payment Medium Workbench. Data-medium creation is configured in OBPM4, with DMEE and DMEEX for bank-specific format work, and with a PMW payment method F110 launches SAPFPAYM_SCHEDULE rather than a dedicated program per method. The process flow is fundamentally different, which is why this is a conversion workstream rather than a configuration tweak.
Bank determination moved house
Bank determination is still configuration, but it now resolves against bank accounts that are no longer configuration — they are Bank Account Management master data, maintained in production and owned by Treasury, with workflow approval and an audit trail. Which means a payment-run failure can now originate in a bank-account change a Treasury user made in production, without a transport.
What to budget for
Not “learning the new payment run.” Budget for the PMW conversion, which is the substantive workstream; the payment-advice variant, created and tested; the proposal drill-down decision, made with your AP team rather than for them; and cross-module ownership of bank master data — who owns it, who approves changes, and how AP finds out when one happens.
Sources & further reading
- SAP KBA 2863917 — payment advice scenarios (RFFOAVIS_FPAYM)The hardcoded variant behavior that silently stops advices. Login required; KBA number verified in context. [Verify.]
- SAP KBA 2794915 — missing Printout tab workaroundThe BAdI and template-run workaround for the missing tab. Login required; KBA number verified in context. [Verify.]
- SAP Help — Payment Medium Workbench & Manage Automatic PaymentsThe PMW, OBPM4 configuration and the F0770 app. Landing hub verified live; search 'Manage Automatic Payments' for the app page.
App availability, KBA content and PMW scope vary by release. Verify against SAP Help and the referenced KBAs for yours. SAP guidance, transaction availability and dates change between releases and editions. Verify anything here against SAP Help for your own situation before you commit to it. This article is independent commentary and is not affiliated with SAP or any implementation partner.