TENURED BY IGNITE9 · RUN · SAP PRODUCTION SUPPORT
SAP production support, with the whole process in view.
Tenured takes the SAP ticket, follows it across the applications the process runs through, makes and tests the fix in development, and hands your IT team a tested change for production.
Tenured by Ignite9 provides digital employees for enterprise applications: production support, modernization and compliance, and SAP is where most of the process runs. Its digital employees take the SAP ticket, follow it across Ariba, Concur, SuccessFactors and the general ledger, build the change in development with its unit test, and move it to QA once you approve the proof. Your IT manager deploys the tested change to production.
01 / THE TICKET IS RARELY ONLY ABOUT SAP
A fix in one module can stop the quarter close.
SAP application management is usually staffed module by module: one team for FI, another for MM, another for Ariba or Concur. Each team knows its own transactions, and the ticket moves between them until someone finds the cause. The change that fixes one module is rarely tested against the next one.
Tenured works the other way round. Its digital employees read the process end to end, so the payment run, the goods receipt, the invoice and the expense payout are one chain, not four queues. Procure-to-pay, travel-and-expense and record-to-report maps come with Tenured and give them that chain once your administrators bind the steps to your systems and verify them.
02 / WHAT TENURED DOES ON AN SAP TICKET
From the first message to a tested change, handed over.
- 1
Answers in the requester’s language
A clerk in Frankfurt writes in German and gets the answer in German. Your SAP team reads a translation into your working language beside the original.
- 2
Places the ticket in the process
Tenured finds the step on your business map, for example the F110 payment run in procure to pay, and walks the dependencies upstream and downstream. Your administrators verify what goes on the map; anything unverified is shown apart, as possible or as a gap, never assumed.
- 3
Builds and unit-tests the fix in development
The digital employee makes the change in your SAP development system with its own SAP user, through machine routes first and SAP’s own screens where needed, and releases its transport. SAP’s authorizations decide what it may do there. Tenured keeps the session inside development, refusing transport imports, copies into other clients, RFC calls from SAP’s screens and operating-system commands; give development no RFC destinations that reach QA or production with stored credentials or trusted RFC. The change package records the transport, the unit test before and after, and the rollback values.
- 4
Asks for missing access
If SAP refuses a transaction your Basis or security team owns, such as SM37 or ST22, Tenured sends that team SAP’s refusal and asks for the least access for the shortest time. It never grants or approves its own access.
- 5
Hands over a complete work package
When access is not granted, the owning team gets everything to do the work itself: what the requester needs, the proposed solution with its transactions, the testing, the impacted areas and the rollback plan.
- 6
Shows what else the fix touches
The systems the change may reach on your business map are listed with the tests they need, such as Concur expense payouts in the same payment run, or the GR/IR balance in the general ledger. That impact goes with the proof you approve before the change moves to QA.
- 7
Moves to QA on your approval
Once you approve the proof, the digital employee imports the transport into QA and smoke-tests it there. Your user then tests it, and Tenured verifies that test in SAP before the user approves the tested change. In QA, SAP’s screens are otherwise display-only for digital employees.
- 8
Hands over to a named person
In the delivery flow, your IT manager deploys each change to production from its handover package; digital employees never deploy it. Routine standard changes you list in advance, such as unlocking a user, run in production within that listing; other writes follow the authority your administrators give each digital employee. Every action with an effect, and every approval, goes on a sealed audit trail.
03 / WHAT YOU GET
What the work leaves behind.
A reference for every request
INC- for an incident, ENH- for an enhancement, PRJ- for a project, and INFO- for a look-up, with an acknowledgement.
Triage evidence
The probable cause, with the competing causes and the evidence for and against each.
Change package
The transport Tenured read itself, the unit test before and after, and the rollback values.
Handover package
What changed and why, the test trail and both approvals, with the deployment steps and rollback plan for your IT team.
04 / WHAT DIGITAL EMPLOYEES DO IN SAP
Agentic operations in SAP, from the first read to the handover.
Digital employees work in SAP ECC and SAP S/4HANA the way your own team does: with their own SAP users, under the authorizations your SAP team grants, and with your people deciding at each approval.
Work in SAP’s own screens
Digital employees work in SAP GUI for HTML in a browser session, each with its own SAP user and the authorizations your SAP team grants, just as your own staff do. SAP GUI for Windows is out of scope.
Machine routes before screens
Digital employees use machine routes first: your vendor’s MCP servers and APIs, then SAP transports and tables read through your system’s SOAP-RFC service, with SAP’s screens as the fallback. A screen opens only after the connected route that could do the step was tried, or with the reason none covers it, and each application’s page in the console lists the routes connected and each missing one with its remedy.
Diagnose incidents from SAP’s own logs
Before changing anything, digital employees read SAP’s own logs, such as ST22 dumps, the SM21 system log and SM37 job logs, and record the probable cause with its evidence.
Configuration changes in development
A digital employee builds the configuration change and unit-tests it in your SAP development system, releases its transport, and Tenured reads that transport itself before it goes to your requester as proof.
QA, user test and handover
On the requester’s approval, the digital employee imports the run’s own transport into QA and smoke-tests it; Tenured verifies your user’s test in SAP before the tested change is approved and handed to your IT manager, who deploys it to production.
Routine work in production
Standard changes your administrators list in advance, such as unlocking a user or re-running a failed job, run in production within that listing.
Explaining your custom code from the code itself
Digital employees find a system’s custom objects, search its code and read ABAP source, exits and enhancements in display, and explain what the code does, citing the code.
ABAP code changes
Code changes are made in development and carry coverage and vulnerability-scan evidence through the same two approvals as any other change. Your own custom objects (Z and Y names) are never gated.
RAP and CDS on your own objects
Digital employees build RAP business objects and CDS views on your own objects in development, through the same delivery flow.
SAP ECC and SAP S/4HANA
The SAP pack covers SAP ECC as well as SAP S/4HANA, through SAP GUI for HTML and the same machine routes.
Analyses written up as documents
Ask for an analysis, such as a process diagram of how procurement is configured in your SAP S/4HANA system, and a digital employee reads your system and answers with a Word and PDF document: the process map, every fact about your system sourced to a read of it, SAP’s standard steps labelled as standard, and what could not be read, with what IT can grant, followed by a workbook of the rows it read.
A business map your people verify
Tenured keeps a map of your processes, systems, interfaces and dependencies. People add to it, CMDB exports are imported and digital employees propose what they observe; nothing counts as verified until an administrator verifies it, and a second administrator does wherever four-eyes is on.
Vendor policy: SAP’s rules, nothing stricter
On vendor policy, Tenured adds no restriction of its own: SAP’s authorizations decide what a digital employee can do. Your own custom objects and SAP’s screens are never gated. An interface SAP’s published policy prohibits is used once you confirm with SAP that your contract permits it and an administrator records that.
05 / VENDOR POLICY · YOUR CONTRACT WITH SAP DECIDES
No vendor-policy restriction of Tenured’s own.
On vendor policy, Tenured adds no restriction of its own: SAP’s authorizations decide what a digital employee can do, as they do for your team. SAP’s published APIs, your own services and the routes SAP endorses, such as the MCP Gateway on SAP Integration Suite, are reviewed and enabled like any other connector. Your own custom objects (Z and Y names) are never gated, because they are your organization’s own code, and SAP’s screens are never gated. An interface SAP’s published policy prohibits, such as ODP-RFC or SAP’s development (ADT) interfaces on SAP’s own objects or data, is used once you confirm with SAP that your contract permits it and an administrator records that confirmation; SAP’s written permission lifts it too.
Digital employees do the SAP work the way your team does: through SAP’s published APIs with the technical user your SAP team sets up, and in SAP’s own screens with their own SAP users, each held to the authorizations your SAP team grants. In Tenured’s delivery flow they build and unit-test in development, import the approved transport into QA, and hand the tested change to your IT manager for production. SAP’s QA and production screens are display-only for them, apart from importing a change’s own approved transport into QA and, in production, routine standard changes you list in advance.
Connector profiles for SAP S/4HANA Cloud, SAP Ariba, SAP Concur and SAP SuccessFactors come with Tenured. Like every connector, each one is reviewed and enabled by your administrators before use.
06 / ALSO PART OF SAP SUPPORT
The rest of the team’s day.
Global affiliates, local languages
Twelve launch languages with automatic detection, for the affiliates who write in their own language. How languages work.
Your ticketing system stays the record
Tickets arrive from ServiceNow or Jira, and progress and resolutions are written back there. How the sync works.
Evidence for audit
Approvals, segregation of duties and a sealed audit trail for every change. Security and governance.
A desk that never goes silent
The AI desk answers 24/7, people answer during your support hours, and backup models you register take over when a provider is down.
07 / HOW TO START
Start with a read-only assessment.
Tenured’s capabilities are delivered through design-partner engagements: scope and timing are confirmed when we scope your work.
Start with a read-only assessment
Tell us the system and the work. We scope what Tenured reads, read-only, and what it needs from your people, before anything changes.
Start with a read-only assessment
NEXT STEP
Bring one ticket that bounced between five teams.
In a 30-minute demo we show Tenured at work, walk through how it would handle yours, answer your security team’s first questions and agree the scope of a design-partner engagement.
