Functional and technical together
The functional consultant translates the business process and the ABAP/integration developer builds it, in the same team. The rule is understood before it becomes code.
SAP projects: integration, ABAP and S/4HANA extensions
SAP projects are our house specialty. We bring functional and technical consulting into one team to integrate SAP with other systems, develop in ABAP and extend S/4HANA while keeping the core clean. Everything follows the DEV, QAS and PRD landscape, with controlled transports and testing windows agreed with your IT team.
Particularities
DEV, QAS and PRD landscape
Every change starts in DEV, is validated in QAS and only reaches PRD through a controlled transport, with documented requests and a sequence agreed with your Basis team.
Clean core
We favor extensions outside the SAP standard, such as BAdIs, APIs and side-by-side apps, over core modifications. This protects upgrades and lowers migration risk.
Integration via BAPI, OData and IDoc
We use the interfaces your environment already exposes. The choice between BAPI/RFC, OData or IDoc depends on the version, volumes and business rules.
Testing windows
Integrated tests and key-user acceptance happen in windows agreed with your team, respecting period closings and system freeze periods.
Discovery and development phases
- 01 · 15 days
Sprint Zero
Understand the process, the SAP environment and the available interfaces before any development.
Activities
- Immersion in business processes with key users
- Survey of the landscape, SAP version and available interfaces
- Functional and technical design of integrations and extensions
- Definition of the transport strategy and testing windows
- Prototype of screens or flows validated with your team
Deliverables- Vision Document with functional and technical specification
- Validated prototype
- Roadmap with scope and estimates
- 02 · 8 to 16 weeks
MVP in production
Build and test in short cycles until the MVP runs in PRD.
Activities
- 2-week sprints with a Sprint Review every 15 days
- ABAP development, integrations and extensions in DEV
- Unit and integrated testing in QAS
- Acceptance testing with key users in the agreed windows
- Controlled transport to PRD and go-live support
Deliverables- Working MVP in production
- Documented transport requests
- Updated technical and functional documentation
- 03 · Ongoing
Orbit
Keep integrations and extensions stable and evolve what was built.
Activities
- Monitoring of interfaces and integration queues
- Error handling and reprocessing under defined SLAs
- Adjustments and new requests through the same DEV, QAS and PRD flow
- Support for upgrades and the move to S/4HANA
Deliverables- Monitored operation with SLAs
- Living evolution roadmap
Allocated crew
| Role | Sprint Zero | MVP in production | Orbit |
|---|---|---|---|
| Project managerFocus: Planning, testing windows and communication with IT and business teams. | Leads | Part-time | On call |
| SAP functional consultantFocus: Business process, functional specification and support for acceptance testing. | Full-time | Part-time | On call |
| ABAP developerFocus: ABAP development, BAdIs, reports and extensions following clean core. | Part-time | Full-time | Part-time |
| Integration developerFocus: BAPI/RFC, OData and IDoc interfaces with external systems. | Part-time | Full-time | Part-time |
| QA analystFocus: Unit and integrated testing in QAS and acceptance test scripts. | Not allocated | Full-time | On call |
| Support analystFocus: Interface monitoring, error handling and SLA compliance. | Not allocated | Part-time | Leads |
Technologies
SAP ECC and S/4HANAABAPBAPI / RFCOData APIsIDocSAP BTPMonitoring and observability
Frequently asked questions
Do you work with SAP ECC or only S/4HANA?
Both. What changes is how we integrate and extend, and that is defined in Sprint Zero based on your environment's version and landscape.
How do changes reach production?
Through the DEV, QAS and PRD flow: we develop in DEV, test and validate in QAS, and only then transport to PRD, in windows agreed with your IT team.
Do you modify the SAP core?
We avoid it. We favor extensions and interfaces that preserve the standard. When a change in SAP is unavoidable, it is mapped and approved with your team before development.
Does my company own the source code?
Yes. At the end of the project the source code belongs to the client, and we sign a non-disclosure agreement (NDA) whenever you ask.
Related service
SAP
Enterprise SAP integration: the system large companies already use, connected to yours.
Ready to get your mission off the ground?
Tell us what you need to build. We reply within 48 business hours.