Vendor Novation in SAP S/4HANA Public Sector Management

[MABecker]

Dear Experts, I am looking for information on the SAP Best Practice for supporting a vendor novation in the S/4HANA Public Sector environment. With SAP SRM sundowning in 2027, when a customer is using S/4HANA and Public Sector Management, what is the best practice for handling vendor novations when there are existing contracts and purchase orders in place, specifically when the commitments cover multiple years. For example, a contract and related purchase orders are created in a given fiscal year, let's assume FY23 with Vendor A, and then in FY24, Vendor A is acquired and merged with Vendor B. How should the public sector customer handle this novation? How should the existing contract with Vendor A and now Vendor B be updated? How would the associated purchase orders under this contract be updated for Vendor B while still reflecting the budgeting as applied in FY23?

Is there a best practice for S/4HANA to support closing the previous purchase orders and opening new purchase orders that still reflect the budget period of FY23 but using the new Vendor B that can be reflected against the updated contract with Vendor B that was originally with Vendor A?

Could this be accomplished using the Financial Management (FM) Multi-Year Budget Execution or is there a different or better option for handling the vendor novation?

Thank you!

[meredithmo24p]

hi MABecker, did you have the solution for it, we face the same issue and seeking for the solution

[MABecker]

Meredith,

      Unfortunately, while I have not yet received an answer through this forum, I was able to find an answer using AI. I hope this helps!

Great question, Mark — and one that’s gaining traction as public sector organizations prepare for the SAP SRM sunset. Here's how best practice is shaping up for vendor novations in SAP S/4HANA Public Sector Management, especially when multi-year commitments and budget periods are involved:

---

🧾 Contract Novation Strategy

When Vendor A is acquired by Vendor B in FY24, and the original contract was created in FY23:

• Amend the Original Contract: Update the vendor master data in the contract to reflect Vendor B. This preserves the contract number and historical linkage to FY23 commitments.
• Use the “Old Contract Number” Field: In S/4HANA, this field helps trace the lineage of the contract from Vendor A to Vendor B, ensuring auditability and compliance.
• Add Novation Texts: Include explanatory notes in the contract header (e.g., “Novation from Vendor A to Vendor B effective FY24”) to document the transition.

---

📦 Purchase Order Handling

For existing POs tied to the FY23 budget:

• Close Original POs: Best practice is to close POs under Vendor A to prevent further processing.
• Create New POs for Vendor B: Clone the original PO structure but assign Vendor B. Use the same contract reference and delivery dates to maintain continuity.
• Preserve Budget Period: SAP allows new POs to inherit the original budget period (FY23) if the commitment was established then. This is supported by Multi-Year Budget Execution in Funds Management.

---

💰 Budget Integrity Across Fiscal Years

To ensure budget alignment:

• Enable Delivery Date-Based Budgeting: Configure update profiles to track budget consumption by delivery date rather than posting date.
• Use FM Derivation Rules: These can help ensure that the budget period from FY23 is retained even when the PO is recreated in FY24.
• Avoid Budget Overruns: SAP will still check availability against FY23 limits, so ensure the new PO doesn’t exceed the original commitment.

---

🛠️ Tools & Configuration Tips

• BidBuy Integration (for U.S. public sector): Some states use BidBuy to manage novation workflows, including cloning POs and updating vendor assignments while preserving obligation numbers.
• SAP Notes & Attachments Tab: Use this to document the legal novation agreement and any internal approvals.

---

If you're working with Funds Management (FM) and Public Sector Management (PSM), this approach ensures compliance, traceability, and budget fidelity. Want to dive deeper into how FM derivation or update profiles are configured for this? I can walk you through it.

Solved: How to use Multiyear Budgeting - SAP Community

Solved: Budgeting for purchase order created for more than... - SAP Community

Solved: Budget check at PO level - SAP Community

Novation Assignment SAP v25.2

[meredithmo24p]

Thank you so much, it's helpfully!