Service 01 · SAP
An SAP estate is six layers, and they all move together.
Noble works across the whole stack rather than at one level of it — because a change to the application layer is a change to integration, to data, to identity and to whoever operates it at the end of the month.
- 01
Experience
Fiori · SAPUI5 · Mobile
The part people touch every day, and the first place a badly configured process becomes visible.
- 02
Application
S/4HANA · Business One · SuccessFactors · Ariba
The business processes themselves — configured against how the organisation works, not against a reference model.
- 03
Extension
ABAP · RAP / CAP · BTP
What standard does not cover, built so that it survives the next upgrade rather than blocking it.
- 04
Integration
Integration Suite · Cloud Integration · APIs · Events
The interfaces to everything SAP is not — which on most estates is where the difficult work lives.
- 05
Data
BW/4HANA · Datasphere · Analytics Cloud · MDG
Migration, master data and the reporting layer above them — the part that decides whether anyone trusts the numbers.
- 06
Platform & operations
HANA · BASIS · Authorisations · RISE deployment models
The database, the basis layer, the authorisations and the people who keep it running afterwards.
How an engagement runs
01
Assess
What is actually running, what it costs to keep running, and what a move would involve. The answer is sometimes that the move should wait.
02
Design
Target architecture, deployment model, integration map and the decision about what stays custom and what returns to standard.
03
Implement
Configuration, data, integration and the cutover, sequenced so the business keeps operating while it happens.
04
Run
Support, releases and the improvements that only become visible once people are using it.
The service, by capability family
Eight families, covering the estate from the core through to the team operating it after go-live. A technology is named where Noble can work on it. Most programmes draw on several families at once, which is why they sit under one delivery team.
SAP ERP and S/4HANA
- New implementations and greenfield builds
- System conversion and selective transition from earlier releases
- RISE with SAP, and the private or public cloud editions it covers
- Deployment model selection, on-premise or hosted
- Landscape transformation, consolidation and multi-entity rollout
- Upgrades, release management and regression testing
- Configuration against real business process
- Test cycles, cutover planning and hypercare after go-live
BTP, extensions and development
- Applications on SAP BTP, including RAP and CAP
- ABAP development and clean-core extension
- Fiori and SAPUI5 interfaces, and the mobile cases behind them
- Side-by-side extension, so the core stays upgradeable
- Custom development where standard falls short
Integration and APIs
- SAP Integration Suite and Cloud Integration (CPI) flows
- API design, publication and lifecycle management
- Event-driven interfaces where the process is asynchronous
- Interfaces to the non-SAP systems around the estate
- Interface monitoring and error handling that does not lose a document
SAP data, analytics and planning
- Data migration, cleansing and reconciliation to the source
- Master data governance
- BW and BW/4HANA reporting
- SAP Datasphere modelling
- SAP Analytics Cloud — reporting, dashboards and planning
- Planning, budgeting and management reporting
SAP business applications
- SAP Ariba — sourcing, procurement and supplier processes
- SAP SuccessFactors — core HR and the modules around it
- Workflows that cross these applications and the core
- Integration between line-of-business applications and finance
BASIS, security and technical operations
- BASIS administration, system copies and refreshes
- HANA database operations, housekeeping and sizing
- Patching, kernel and support-package management
- Role design and authorisation concepts
- Segregation of duties analysis and remediation
- Identity and access alignment with the wider estate
- Performance investigation, tuning and audit support
Automation and intelligence
- Workflow and process automation, including SAP Build Process Automation
- Document processing against SAP transactions and master data
- Prediction and anomaly detection on the operational record
- Intelligence delivered through Fiori and BTP rather than beside them
- Built with the AI service, on data the estate can already reconcile
Managed SAP services
- Managed application support after go-live
- Incident, problem and change handling
- Monitoring across the estate and its interfaces
- Technical operations, maintenance windows and housekeeping
- Continuous improvement against real usage
The service, in depth
Seven specialist pages, one per group of the families above. Each is written to justify its own route — the architecture, the controls and the boundaries of the work.
- S/4HANA & RISENew implementations, system conversions and selective transitions; the deployment decision; data migration, testing, cutover and the weeks after go-live.
- BTP, Integration & ExtensionsExtensions built beside the core rather than inside it; the Integration Suite, APIs and events that connect SAP to everything it is not.
- Data, Analytics & PlanningThe path from the operational record to a figure somebody trusts: migration and master data, BW and BW/4HANA, Datasphere, Analytics Cloud and planning on one metric layer.
- Ariba & SuccessFactorsProcurement on Ariba and the workforce record on SuccessFactors, each connected to the core, to finance and to enterprise identity so that a process crosses them without being re-keyed.
- Security, BASIS & OperationsRoles and segregation of duties, BASIS administration, the transport path, the HANA database and the monitoring that sees all of it — the controls that keep a landscape sound.
- Automation, AI & the Intelligent EnterpriseWorkflow and process automation on BTP, document intelligence at the point of entry, SAP’s AI services and Joule applied inside a process, and the boundary that keeps a model advisory until it has earned more.
- Managed SAP ServicesApplication management, the release cycle, interface monitoring and hypercare after a go-live — a landscape run as a service with a calendar, a register and a named owner for every part of it.
Where SAP meets the rest
An SAP programme is rarely only an SAP programme. These are the services it reaches into, and what it needs from each.
- CloudThe landing zone under it, the network into it, and the operating model that comes with a hosted deployment.
- Data & AnalyticsReporting that reconciles with the source, and the master data work that has to happen before it can.
- SecurityAuthorisations inside SAP have to agree with identity outside it, or the controls exist only on paper.
- AI & Machine LearningOnce the data is trustworthy, the estate is where prediction and document work have something real to run on.
- Managed IT ServicesSomeone operates it after go-live. That is a different discipline from building it, and it is the one that decides whether the build held.
SAP product names are used descriptively to identify the systems Noble works on. All marks belong to their owners.
The work, not a status
This page names the technologies Noble can work on and the kinds of work it does on them.
SAP is not the whole of enterprise applications, and Noble does not present it that way. Broader ERP and enterprise-application work — advisory, implementation, modernisation, migration, integration and managed operations — sits under Digital Transformation. No non-SAP ERP product is named there or here until Noble’s support for it is verified.