SAP Development
SAP extensions, interfaces and automation from a registered SAP Application Development Partner.
An interface is only finished when it survives the next release.
The challenge: landscapes that grew
SAP covers the standard case. Connecting it to everything that sits beside it stays your job.
In most organisations that "beside it" is large: a line-of-business system from before the last migration, a database one department runs itself, a program belonging to a customer or supplier. Until somebody connects them, a person acts as the interface, and that person is on holiday when the figures are needed.
A line-of-business system with no SAP link
Data maintained in two places
One report from three exports
Custom code with no documentation
What we build
Cross ALM is a registered SAP Application Development Partner and an SAP Silver Partner. Our consultants and developers carry an extension from problem analysis through to rollout.
What separates this from plain development work happens before the first line of code. We settle which system owns which record, what the standard already does, and what the next release will do to it. Building comes after that.
Extensions
Add functions where the standard leaves a gap, release-safe and without surgery on the core. At the edge of the standard, not inside it.
Interfaces
Connect existing systems, databases and external programs to SAP, in both directions and over the routes SAP provides for it.
Automation
Take repeated steps off the team without anyone learning a new interface.
How it works: what we actually build
On the SAP side we work through OData services in our own namespace, not through table access and not by driving a user interface from a script. That is why our products survive release changes, and it is the same route we take at your site.
Every interface comes with a record: which fields it touches, what it relies on, what needs checking at the next release. When a system is replaced later, the connection sits in a named place rather than in someone's head. How far DevOps practice carries in SAP landscapes is covered in New Webinar: DevOps with Jira and SAP.
- Which systems should understand each other, and in which direction
- Which system is the source of truth for which record
- Which interface SAP officially provides for it
- What the standard already covers, even where that looks inconvenient
- Which fields the interface touches, written down
- What needs checking at the next release of the systems involved
- How testing and acceptance work
- Who maintains the extension after handover
What a well-planned interface gives you
The systems you already own understand each other. That removes the second place to maintain and the errors that come with it.
The second gain shows up later. When a system gets replaced, what hangs off it is known. Without that record, every replacement turns into a search whose end nobody can predict.
Where extensions attach
At the edge of the standard, not in its core. That is why they survive the next release.
What we have already built
Our Cross Connectors are running products rather than case studies. They are listed on the Atlassian Marketplace and in the ServiceNow Store, and they run in customer operations.
- CC4 links SAP Solution Manager with Jira and ServiceNow, for ChaRM, ITSM, Focused Build and Quality Gate Management
- CC5 drives SAP transports from inside Jira, one at a time on the issue or in bulk from the Release Management Cockpit
- C³F, C³O and C³B connect SAP Cloud ALM to Jira Cloud: features, operations events, tasks
- The Cross Archiver stores changes, tests and transports from Solution Manager as searchable, audit-proof PDFs
How CC5 reached the Atlassian Marketplace is described in SAP Cross-Connector Jira / TMS is now on Atlassian Marketplace; why we built the Cross Archiver, in Archiving Change Documents in Solman.
Our own products
Four product lines maintained over years, across SAP support packages and platform releases. The same people build your extension.
Out of the SAP world
Cross ALM grew out of a team of former SAP employees and SAP specialists, based in Berlin.
Three partnerships
Registered SAP Application Development Partner and SAP Silver Partner, plus Atlassian Gold Solution Partner and ServiceNow Select Build Partner.
Starting in three steps
The first two steps establish whether anything needs building at all.
Record
Which systems should understand each other, which one leads, and what the standard can already do today.
Design
The provided interface, the fields it touches and the dependencies, written down, before anyone develops.
Build and hand over
Development, testing against the catalogue, training and handover to named people in your organisation.
From customer projects
How our development work runs in real landscapes is written up in the project reports: SAP Transport Management System – Jira Integration at HUK-Coburg covers driving transports from Jira, Flexible Cross Connector Jira/SolMan interface solution with LAPP a link that did not exist as a product, and DevSecOps for SAP with ChaRM at Deutsche Bahn a group with demanding governance requirements.
Customers who trust us
You use a different system?
- Which systems should understand each other
- Which side is the source of truth
- What happens at the next release
- Whether a Cross Connector already covers it