This blog is about Background Processing Framework (bgPF) Is Replacing IDoc for Intercompany Payables Posting in S/4HANA Cloud, Public Edition and it describes What’s changing, who’s impacted, and how to adopt safely with 2602.2 and beyond.

SAP is transitioning intercompany payables posting for “classic” intercompany invoices from the legacy IDoc-based mechanism to the background processing framework (bgPF). Starting with release 2602.2 in SAP S/4HANA Cloud, public edition, customers can activate a new feature that enables bgPF to automatically post payables to the selling company’s Accounts Payable. Over time, bgPF will become the default and ultimately the system standard, fully replacing IDocs for this use case. The bgPF solution is easier to configure, more flexible, and helps you adjust to future business requirements.

• Short term (2602.2): Feature is opt‑in via Activate Features.
• Upcoming: Feature will be activated by default (with an option to deactivate).
• Future: bgPF becomes standard; IDoc-based posting retired.

Important: Once you activate the feature, the system can no longer post payables via IDoc. Post any unposted payables before activation to avoid stranding documents mid-flow.

 What’s changing

As of today, the Intercompany payables posting can run via IDoc. With the 2602.2, bgPF can be used to automatically post payables to the selling company’s AP. The Activation of this feature named Payables Posting for Classic Intercompany Invoice via bgPF with technical id S4HC_SDBIL_ICO_IDOC_REMOVAL is controlled in the Activate Features app and is not automatic. The bgPF option will first become the default (with an opt‑out), and later the only available mechanism, replacing the IDoc-based solution entirely.

 Impacted scope items

The change affects intercompany processing in Order-to-Cash and Returns scenarios:

• Intercompany Sales Order Processing – Domestic (1HO)
• Intercompany Sales Order Processing – International (1MX)
• Extended Intercompany Processes for Sales (1WO)
• Intercompany Process for Customer Returns (2F4)
• Intercompany Billing for Cross‑Company Cost Accounting Postings (4AN)

 Activation guidance (2602.2)

Because the feature is opt‑in at this stage, the activation of the feature has to be done manually.

Prerequisites:

• We recommend closing out unposted payables created via IDoc by posting the corresponding intercompany invoice to financial accounting.

Activation steps:

1. Activate the feature in the Activate Features activity in Implementation activities app:

• Feature name: Payables Posting for Classic Intercompany Invoice via bgPF
• Technical ID: S4HC_SDBIL_ICO_IDOC_REMOVAL





2. Setup Output determination:

• Define the business rules for output determination in the Output Parameter Determination app which will enable the use of output channel EDI instead of output channel IDOC.             

3. Enable monitoring of bgPF messages:

• In order to enable monitoring of bgPF messages by business users, the Assign Recipients to Users app should be used to assign the recipient name EDI_FIN_IC_AP_IN_RECIPIENT to the users. For setup instructions, please check the scope item 1HO.

Rollback/opt‑out:

• In an upcoming release, the feature will be activated by default with an option to deactivate. Use that opt‑out only if a critical issue is discovered and log a corrective action plan. Note that the long‑term direction is bgPF standardization.

 Recommendations

• After activation, payables can no longer be posted via IDoc for the affected scope.
• Post all outstanding IDoc-triggered payables before activation to prevent mixed-mode exceptions.
• Recommend complete testing of the end-to-end process in your quality system before enabling the feature in production system.