Clarify the behaviour
Describe the business task before choosing the extension pattern.
SAP · UK & EUROPE
SAP BTP & Fiori Consulting
SAP BTP and Fiori consulting for teams deciding how application behaviour and extensions should fit a cleaner SAP core.
THE PROBLEM
What is really going wrong
New functionality can create lasting dependencies when extension choices are made without considering the user requirement, standard SAP behaviour, identity and future support. The question is where the capability belongs and who will own it.
OUR APPROACH
How Liditech solves it
Select each step to see how we would move the work forward without turning it into a larger programme than necessary.
Review the standard option
Check whether existing SAP functionality can meet the requirement.
Design the application boundary
Make APIs, events, access and data ownership explicit for the chosen approach.
Record the support decision
Give each extension an owner, rationale and review point.
WHAT WE EXAMINE
What we look at first
- Business usage and the requirement behind each extension
- Standard, in-app and side-by-side options
- API, event, identity and data boundaries
- Upgrade impact, security and support responsibilities
WHAT YOU RECEIVE
Useful outputs, not shelfware.
We keep deliverables tied to decisions, delivery and ownership. The exact format changes with the workstream; these are the outputs we would expect to leave behind.
01
BTP and Fiori extension decisions
02
Architecture and support guardrails
03
Prioritised application remediation
WHERE WE FIT
We do not need to replace your existing team to be useful.
Bring us in when teams disagree about where functionality should live or existing extensions have become difficult to upgrade and support.
SAP BTP: choosing where extensions belong
BTP extension decisions start with the requirement and the boundary around the SAP core. Standard, in-app and side-by-side options are considered against business usage, upgrade impact and technical dependencies. APIs, events, identity and data ownership need to be explicit before a new extension is added.
The useful outputs are extension architecture and guardrails, a decision register and a prioritised remediation backlog. Each retained exception needs a reason, an owner and a review point.
SAP Fiori: reviewing the application requirement
Fiori consulting examines the business behaviour that an extension needs to support, what is actually used and what standard SAP can already handle. Existing extensions are reviewed for upgrade impact, security, support needs and technical dependencies.
Standardisation, retirement and refactoring are deliberate choices rather than automatic rewrites. The aim is functionality that remains useful to the business without creating an extension model that is difficult for the client team to own.
TALK TO LIDITECH
Tell us what is getting in the way.
The current problem, the outcome you need and what cannot be disrupted are enough to start.