The Problem Every Sales Team Knows
Your top sales rep, Elena Richter, just left the company. Or maybe she got promoted. Either way, Marcus Weber is now taking over her book of business — 47 accounts, and across those accounts, 130+ open opportunities.
In the old world, someone on your team now has to open every single one of those opportunities and manually update the responsible owner. One by one. It's tedious, error-prone, and almost always incomplete. Deals get missed. Reports go wrong. Approvals route to the wrong person. The data rot starts the moment the team change happens.
That problem is now solved in SAP Sales Cloud V2.
Introducing Party Realignment (Beta)
Party Realignment is a new capability in SAP Sales Cloud V2 that automatically updates the parties in your business transactions* — such as the responsible sales employee or owner — whenever your account team changes.
When you update who's on an account team, the system takes care of the rest. Every related open transaction* gets updated automatically. No manual work. No missed deals.
A Real-World Example
Let's walk through exactly what happens:
Before the change:
NovaTaste GmbH has Elena Richter as the responsible sales employee. An open opportunity — NovaTaste Flavor Ingredient Supply 2026 — shows Elena as the responsible owner in the Parties section.
The change happens:
You go to the NovaTaste GmbH account and update the account team. Elena is out, Marcus Weber is in. You save the account. That's it — you don't touch a single opportunity.
What the system does next (within ~15 minutes):
- Detects the change — the system sees that an account team relationship has changed on NovaTaste GmbH.
- Triggers a Party Realignment Run — a scheduled process (running approximately every 15 minutes) kicks off automatically.
- Re-determines parties — for every related open opportunity, the system recalculates who the parties should be based on the new account team.
- Updates the opportunities — all affected transactions are updated with the new party data.
- Logs everything — every run gets a full audit trail: which accounts were affected, which opportunities were updated, and the status of each.
The result:
Marcus Weber now appears as the responsible owner on the NovaTaste opportunity. He sees it in his pipeline. Notifications, approvals, and reporting all reflect the correct person — automatically, from that moment forward.
Full Audit Trail — Nothing Is a Black Box
Every Party Realignment Run is logged and visible under:
Admin Settings → Party Processing → Party Realignment Run → Results tab
The log shows you:
- Run ID and status (Created / In Process / Finished / Failed)
- Affected accounts
- Successfully realigned transactions
- Failed transactions with error details
If an opportunity was locked when the run executed — say another user had it open — the system doesn't silently skip it. It automatically queues it for retry in the next scheduled run, with up to 10 retry attempts. Nothing falls through the cracks.
Granular Configuration — You Control the Rules
Party Realignment is designed to be flexible. Administrators can configure exactly how it behaves under:
Admin Settings → Party Processing → Party Realignment Configuration
Setting What It Does
| Team Member Settings | Choose whether to include Account team changes in the realignment trigger |
| Entity Selection | Select which transaction types are in scope (Opportunities supported now; Sales Quotes, Orders coming in future releases) |
| Party Realignment Scope | Decide whether to re-determine only automatically determined parties, or also override manually changed ones |
Need to protect a specific party on a specific transaction? In the Party Schema, you can set an exclude flag on individual party roles. That party will never be touched by realignment — no matter what changes on the account team. Granular control, right down to the party level.
Manual Trigger for One-Off Cases
Sometimes you need to re-determine parties on a single opportunity without waiting for the next scheduled run. That's covered too.
Users with the right authorization can trigger manual party redetermination directly from within an opportunity using a dedicated button in the left header section. This button can be enabled via Adaptation Mode.
What Triggers a Realignment?
In this first release, only account team relationship changes trigger a Party Realignment Run. Changes to other relationships — like Ship-to or Bill-to — do not trigger a run on their own.
Territory Team Changes are planned for a future release.
What's Supported Today (Beta)
Transaction Status
| Opportunity | ✅ Supported |
| Sales Quote, Sales Order, etc. | Planned for future releases |
Getting Started
To enable Party Realignment in your environment:
- Go to Admin Settings → Party Processing → Party Realignment Configuration
- Configure your Team Member Settings and Entity Selection
- Set your Party Realignment Scope preference
- Optionally, configure exclude flags in the Party Schema for parties you want to protect
- Ensure the relevant business roles include the service:
sap.crm.md.service.partyProcessingRealignmentRunService
The Bottom Line
Account teams change — people get promoted, territories get restructured, reps move on. The administrative burden of keeping transactions in sync with those changes has always fallen on someone.
With Party Realignment in SAP Sales Cloud V2, it falls on the system instead.
Your data stays accurate. Your pipeline reflects reality. And your team focuses on selling — not data cleanup.
Party Realignment is currently available as a Beta feature in SAP Sales Cloud V2. Feedback welcome via the SAP Customer Influence portal.
Related Links:
Source link