A Minimum of 10% of SAP Tickets Fixed in Minutes. From Month One.
SELECCIÓN AAS · Autonomous Application Service
SELECCIÓN AAS puts a specialist agent on each routine SAP ticket type, working inside your SAP. A failed IDoc gets reprocessed. A stuck batch job gets diagnosed and rerun. Your SAP CoE decides which ticket types the agents handle, and your experts keep the complex work. It runs on ECC and S/4HANA side by side, as part of SELECCIÓN AMS, and SELECCIÓN owns the SLA.
The Real Bottleneck
Routine SAP tickets rarely have a skills problem. They have a waiting problem.
The fix takes a minute. The wait takes days. We removed the wait.
It is not a people problem. It is how routine support is built, and it shows up in four ways.
!
Waiting
For a routine SAP ticket: an IDoc error, a stuck batch job, a locked user. Most take minutes to fix once the right person looks at them. The wait is for that person.
!
Zero
Resolution at 2am on a Sunday. Human teams have shifts and timezones. AI agents don't have office hours.
!
Lost
Every time a key resource leaves. Support knowledge lives in people's heads, and every departure is a service risk.
!
Pulled Away
Experienced SAP people want project work, and S/4HANA is where the interesting problems are. Routine support pulls them away from it.
What Changes with SELECCIÓN AAS
A Specialist per Ticket Type
Every ticket type gets its own specialist agent, built for that one job. Each agent resolves only its own type.
Same Response, 2am or Noon
No shifts, no timezones, no holidays. A ticket raised at 2am is worked the same way as one raised at noon.
Many Tickets at Once
A human team queues when tickets stack up at month-end close. Agents work many tickets at the same time.
Knowledge That Stays
Knowledge lives in the system, not in one person's head. When people move on, the fixes stay, and every resolution improves the next.
A minimum of 10% of SAP tickets fixed in minutes, from month oneBest SAP people back on projects, not L1 ticketsSELECCIÓN owns the SLA, with every action logged
What Makes SELECCIÓN AAS Different
Built to work inside SAP, under your rules.
Built Agentic From Day One
Not a chatbot bolted onto a ticketing tool, and not RPA scripts wrapped in a UI. Each agent is architected ground-up with its own identity, scope, and audit trail.
Native Execution, Inside Your SAP
SELECCIÓN AAS works through SELECCIÓN MCP+, an ABAP add-on with SAP clean core certification that runs natively inside your SAP system. It reaches standard SAP function modules, transactions, and tables the way your own developers do.
No New Integration Project
Works across SAP ECC and S/4HANA side by side. You do not need a long project to enable and expose integrations across SAP before you see value.
Handles Your Customizations
How customized your system is does not matter. Custom Z-transactions and custom BAPIs are handled exactly as they exist today.
Your Cloud, Your LLM
SELECCIÓN AAS runs in your cloud and uses your own LLM. It is cloud and LLM agnostic, and MCP is a standard protocol, so your security, agent framework, and tooling fit your own architecture.
Your SAP CoE decides which ticket types the agents handle. Every action executes within the acting user's SAP authorization profile, so an agent can never exceed what that role permits. Every action is logged and attributable, end to end.
How SELECCIÓN AAS Earns Autonomy
Autonomy is earned. Your CoE promotes the agent.
Before Go-Live
1. Learn
SELECCIÓN AAS learns from your ticket history
Environment, landscape & integration discovery
Classification trained before the first live ticket
Baseline SLAs and escalation paths agreed with your team
Your Team Approves
2. Human-in-the-Loop
The agent proposes a resolution; your team reviews & approves
Confidence rises with every validated match
Your CoE decides which ticket types move forward, one at a time
Full transparency: nothing goes live unsupervised
Your CoE Promotes
3. Autonomous
Once your CoE promotes an agent, it resolves that ticket type on its own
High-impact work stays off limits. Your team owns escalations, architecture & P1 root cause
Knowledge stays in the system, and every resolution improves the next
Every action logged and attributable
See SELECCIÓN AAS Live
Watch agents work real SAP tickets, and talk to the team behind them.
ASUG Tech Connect
November 2 to 4 in Fort Worth. Two sessions and live demos at booth #123.
The questions we hear most from teams migrating off ECC.
Many AMS vendors now offer AI-assisted support. The useful questions are how many tickets the AI actually resolves, whether it acts natively inside SAP, and whether you can see every action it takes. We can show you all three on your own landscape. If your current vendor can show them too, that is a good sign. If not, that is the gap worth testing.
Your SAP CoE decides which ticket types the agents handle. Agents start small, earn trust over time, and only then work on their own. Every ticket type has its own specialist agent, and each agent only resolves its own type.
SELECCIÓN AAS runs support as part of SELECCIÓN AMS, independently of your migration team, so your best SAP people stay on the migration instead of getting pulled into L1 tickets. It is built for exactly this: freeing internal capacity during the highest-demand phase of a program.
Yes. SELECCIÓN AMS, with SELECCIÓN AAS, can take on full ECC support, including tickets your internal team would otherwise have to context-switch into, while your migration team stays focused on the S/4HANA build.
Both, without switching models. SELECCIÓN AAS runs on ECC and S/4HANA the same way, so you are not standing up a new support approach partway through your migration.
SELECCIÓN AAS continues running during cutover and hypercare, with human escalation paths in place for the higher-stakes issues that come up during go-live. This is a phase where human oversight matters most, and our model keeps humans at that checkpoint.
Yes. If your migration is phased, SELECCIÓN AAS can support both environments in parallel, since it is not tied to a single system's architecture.
SELECCIÓN AAS learns from your ticket history during onboarding, before it handles a live ticket, so it starts with landscape knowledge already in place rather than a slow ramp-up. Exact timelines depend on your ticket volume and landscape complexity, and we size this for your environment.
It is a fair instinct to assume that adding AI during a migration adds risk. In practice it is the opposite. SELECCIÓN AAS starts in a human-in-the-loop mode, where the agent proposes resolutions and your team reviews and approves every one, with autonomy expanding only as your CoE promotes agents, ticket type by ticket type. Nothing goes live unsupervised, and the audit trail gives you more visibility into support activity during the migration, not less.
It learns from your ticket history, along with your environment, landscape, and integration details, before classification is trained and any live ticket is handled.
Your team owns escalations, architecture decisions, P1 root cause investigation, and high-impact configuration changes. The judgment-heavy work stays with certified consultants. SELECCIÓN AAS handles the documented, repeatable patterns that make up the majority of ticket volume, not the exceptions.
The intent is redeployment, not reduction. Freeing your best SAP people from L1 ticket volume means they are available for the migration, for optimization work, or for the next project.
SELECCIÓN AAS runs as part of SELECCIÓN AMS. Talk to us and we will scope it for your landscape and ticket mix.
Why Run Your SAP AMS With SELECCIÓN Consulting, Now?
0Minimum share of SAP tickets fixed in minutes, from month one
24x7Support around the clock, with SELECCIÓN owning the SLA
Your CoEDecides which ticket types the agents handle