Our SAP® RE-FX and LUM operations run but probably not in the best possible way
Does any of that sound familiar?
Our SAP® RE-FX and LUM operations run but probably not in the best possible way
“The backlog of change requests keeps growing.”
Hundreds of small errors every month-end and nobody has the full picture of the system
The system has grown beyond what any single person can still keep in view. PSCD interfaces break at every touchpoint with RE-FX. The same is true for SAP IS-U in infrastructure. A new CAFM project is being added on top without anyone quite saying what it is meant to contribute. And a GIS that half of our processes depend on no longer receives vendor updates.
Every month-end the consequences arrive as hundreds of small errors. Some in PSCD some in ordinary postings and where IFRS 16 applies (typically infrastructure operators postal services large utilities) some there too. Each one is traceable given enough time. Most are known to someone somewhere in the organisation. What no longer exists is an overview. A person or a document that holds the whole system in view at once. Finance is waiting and the investigation starts from scratch every time.
(this section is available for any user)
Our SAP® RE-FX and LUM operations run but probably not in the best possible way
“We’re losing know-how soon..”
Our in-house RE-FX and ILM consultant is leaving soon. The new one will figure it out. They always do.
Our in-house RE-FX and ILM consultant is leaving in six months but we have a good successor lined up. Three handover sessions a few weeks of shadowing and the new person will be up to speed. Changes are documented in change requests anyway.
What those change requests do not contain sits in one person’s head. The reasoning behind a specific condition type. The posting rule altered for one company code three years ago. The settlement variant tuned for one contract cluster. The way RE-FX connects to FI-AA PM IS-U the external CAFM the GIS and now the new DMS.
We tell ourselves the successor will figure it out. To be honest we have told ourselves that before.
(full access for registered users. If you are not registered yet,
you can register as an operator.)
Our SAP® RE-FX and LUM operations run but probably not in the best possible way
“Months have passed and the project has not moved.”
Our new project lead has a plan. The project still is not moving and we are starting to see why.
We brought in someone capable. Or that person was already in the team. The plan is sound. The team is professional experienced and on paper aligned. What is becoming visible month by month is that every meaningful step requires a decision nobody is willing to make first. The colleagues who hold the context have reasons visible and invisible to let things remain as they are. The junior staff who could move faster take their lead from the senior colleagues. Escalations come back with “let us revisit next month”. The project does not fail. It drifts. And our new project lead is learning that pushing harder does not accelerate anything. It only identifies who will not move.
(for registered users. If you are not registered yet,
you can register as an operator.)
Our SAP® RE-FX and LUM operations run but probably not in the best possible way
For public real estate holders and Regulated Network Operators
When Compliance Becomes Operating Reality
Organisations like BImA BIG Fonds du Logement Deutsche Bahn ÖBB or SBB run a configuration fundamentally different from commercial landlords. Lease-in and lease-out under politically determined rent logic. Contracts tied to land parcels as often as to buildings. And underneath it the Land Use Management module of SAP RE-FX. The land register the rights and the encumbrances that define the estate.
For network operators rights-of-way and easements are not edge cases but daily operating reality. In long-lived country-wide infrastructure the GIS layer determines where you can build dig or run a line.
GIS integration is not optional here. When geodata and SAP master data drift apart the question which parcels carry which encumbrances takes days instead of seconds. The unofficial bridge is manual Excel transfer. Until an auditor asks a question it cannot answer cleanly. NIS2 classification and access control are not guidelines but legal obligations that constrain how the system can be touched at all. And procurement discipline rules out quick fixes. The system has to outlast political terms.
Where we step in. A System Health Check establishes whether the RE-FX the Land Use Management and the GIS layer hold up under regulatory scrutiny. Steering Jour Fixe provides recurring senior judgement at a cadence that compliance and procurement can live with. And [Knowledge Induction / Knowledge Retention] our RE-FX and Land Use Management coaching format builds specialist capability directly into your team on the live system on real rights-of-way and encumbrance cases so the expertise stays in-house across the political cycle instead of leaving with the contract.
Our SAP® RE-FX and LUM operations run but probably not in the best possible way
Public real estate (PREM) holders at national, federal and local levels, as well as regulated network operators like railways energy and telecommunications, are covered.