Somewhere in your SAP system is a model that was built two decades ago.
It started simple — a few characteristics, some dependencies, a pricing variant here and there. Over time, it grew. It adapted. It worked.
But now? It barely makes sense even to the people who built it.
If you’re running SAP ECC and relying on Legacy Variant Configuration (LO-VC) to run your quote, order, or manufacturing process, this blog is for you. Because what once gave you flexibility might now be your biggest source of rigidity.
Let’s talk about why your 20-year-old VC model is no longer serving your business — and what that means for your future.
How We Got Here: The Evolution of a “Working” VC Model
Most LO-VC models didn’t start as monsters.
They were built thoughtfully — sometimes even elegantly — to support business complexity. Over time, the business evolved:
- New product lines were introduced
- Exceptions were added
- Dependencies were copied and edited
- Costing logic was hard-coded
- Documentation faded
And the model became unwieldy.
“We can’t change this — it works.”
“Only two people understand how it functions.”
“We just copy and adjust the old one for new products.”
“It’s too risky to touch.”
Sound familiar?
You’re not alone. But that’s not a reason to keep going — it’s a reason to take a hard look.
Signs Your LO-VC Model Has Outlived Its Purpose
- It’s become harder to update than to work around.
Sales and engineering teams are building Excel tools outside SAP because updating dependencies is “too risky.”
- Quote turnaround time has slowed down.
What once took hours now takes days — not because of effort, but because of complexity and unclear logic paths.
- Knowledge is tribal.
One or two experts own the logic. If they leave, no one can safely maintain the model.
- Pricing is inconsistent or disconnected.
Manual overrides are common because the model can’t keep up with exceptions.
- There’s no clean documentation.
Most people are afraid to touch the model — or even look at it too closely.
A model that can’t be safely evolved isn’t a solution. It’s a liability.
What Customers Get Wrong About Product Configuration Longevity
There’s a common belief in many SAP ECC shops:
“If it’s working, don’t touch it.”
But the deeper truth is this: working ≠ scalable, sustainable, or modern.
The LO-VC model might still generate configurations, but:
- Can it support new business models?
- Can it integrate with modern CPQ tools or eCommerce portals?
- Can it adapt to global pricing, market localization, or new manufacturing scenarios?
- Can new employees understand it without shadowing veterans for 6 months?
If the answer is “not really,” it’s time to rethink.
What Happens When You Try to Lift-and-Shift the Old Model
Let’s say you’re moving to S/4HANA — Public Cloud or Private Cloud. What should you do with your legacy VC models?
Here’s what not to do: try to migrate them as-is.
Why?
- Advanced Variant Configuration (AVC) is not a one-to-one replacement for LO-VC.
- Your old dependencies, constraints, and custom logic often don’t map cleanly.
- More importantly, you’re locking in 20 years of process assumptions — even the broken ones.
Migration without redesign is like porting your old Excel pricing sheet into a new system and expecting transformation.
What Smart Customers Are Doing Instead
In working with manufacturing and ETO companies facing this exact challenge, here’s what sets the successful ones apart:
1. They accept that the model is technical debt.
They don’t shame themselves for the past. They honor the model’s legacy — and then set it down.
2. They re-engage business users.
Sales, engineering, costing, and operations are brought into the conversation to redesign how configuration should work today.
3. They prioritize flexibility, not exhaustiveness.
Instead of covering every edge case, they build models that are easier to adapt as products evolve.
4. They integrate configuration into a broader quoting vision.
This includes SAP CPQ, guided selling, visuals, and faster approvals — not just backend BOM logic.
Real Conversation: “We’re Afraid of Losing 20 Years of IP”
A VP of Engineering once told me:
“Our variant configuration model is like our DNA. It’s our competitive advantage.”
I asked: “When was the last time you read through that DNA?”
He admitted it had been years. “We just don’t touch it unless something breaks.”
It’s a powerful metaphor — but here’s the problem:
DNA that no one understands isn’t an advantage. It’s a risk.
The truth? Much of the value is not in the code — it’s in your people, your process knowledge, and your willingness to rethink what works.
What to Do if You’re Running a Legacy LO-VC Model
Here’s a pragmatic way to start rethinking your legacy configuration model:
| Step | Action |
| 1 | Identify all current models actively in use |
| 2 | Interview the teams who use and maintain them |
| 3 | Document the known pain points, delays, and workarounds |
| 4 | Categorize models by business impact (High, Medium, Low) |
| 5 | Choose one representative model to redesign as a pilot in S/4HANA with AVC or CPQ |
You don’t need to solve it all at once. But you do need to start.
And that means facing the truth: your old model isn’t aging well.
Final Thought: What Got You Here Won’t Get You There
If your business is changing — products, markets, sales channels, expectations — then your configuration logic has to evolve too.
The LO-VC model that once gave you an edge may now be standing in the way. Not because it’s broken, but because it was built for a world that no longer exists.
The question isn’t: can we keep using it?
The question is: does it still serve who we are today?
If not, it’s time to let it go — and build something better.