deployed_codeCustom ABAP engineering for SAP teams
Your business evolves.
Your custom ABAP should too.
Before you can change the code,
you have to piece it together
The challenge
A new business requirement can touch years of custom ABAP. Before implementation, developers must trace existing logic, dependencies, and business rules. Estimates stay uncertain, experts become bottlenecks, and missed context creates late stage rework.
estimate
Time lost before the change begins
Finding the starting point means tracing code and dependencies before effort can be estimated.
experts
Work waits for the same experts
Critical knowledge sits with a few experienced developers, slowing decisions and progress.
rework
Missing context becomes rework
Overlooked rules or dependencies surface during review or testing, causing corrections and delays.
Bring the context together. Move the change forward.
Now you can see how the change fits together.
The context is scattered. Bring the pieces together.
Aceteroid connects the requirement, existing logic and relevant dependencies—giving developers a proposed direction and clear points to validate.
Business value
More capacity.
Less effort. Better economics.
Focus on what changes for the business: engineering capacity, delivery cost and the effort needed to validate the work.
See how Aceteroid contributes to a real custom ABAP change.
Explore the engineering exampleProduct walkthrough
See a custom ABAP change move forward.
Understand. Execute. Validate.
Work through an existing custom ABAP change inside Eclipse/ADT, with developers reviewing the output at each stage.
LOOP AT lt_mseg INTO ls_mseg.
COLLECT VALUE ty_total(
matnr = ls_mseg-matnr
werks = ls_mseg-werks
menge = ls_mseg-menge ) INTO lt_total.
ENDLOOP.
Where does lt_mseg get filled, and what calls this form?
Filled by SELECT in FORM read_movements. Called from START-OF-SELECTION and FORM refresh_alv.
Code explanationDraft for developer review
Know the code behind the change.
Explore what the existing implementation does, ask questions about its behavior, and examine relevant dependencies using the available system context.
Start implementation with a clearer understanding of the code you are working with.
Your code stays yours.
Your team stays in control.
Your code stays private.
No foundation-model training. No sharing across customers.
Access is yours to approve.
Work stays within the scope and access route you authorize.
Your developers decide.
Review, validate and approve which changes move forward.
The people behind Aceteroid
Built on SAP
engineering expertise.
Aceteroid is a product of ERPROOTS, shaped by experience in SAP delivery and custom ABAP development.
ERPROOTSSAP Build partnerGet started
Bring one custom ABAP object you are unsure about.
A 30-minute conversation about one object on your backlog, your environment, and whether Aceteroid fits.
Begin with one object
Book a fit conversationOpens a short form. No source code is needed for the first conversation.
Frequently asked questions
What SAP teams usually ask before the first conversation. Anything else, ask us directly.
What is Aceteroid?
Aceteroid is a Custom ABAP Engineering Platform for SAP teams. It helps developers understand existing code, prepare required changes, and organize the work for technical review and validation inside Eclipse/ADT.
Who is it designed for?
SAP CoEs and application teams with an active custom ABAP backlog and ongoing responsibility for their systems. SAP delivery partners can also evaluate it for approved customer work.
Does Aceteroid replace ABAP developers?
No. Aceteroid supports investigation, implementation, and review preparation. Developers remain responsible for business correctness, technical decisions, testing, and production approval.
Which SAP environments can we evaluate it in?
During technical fit, we confirm your SAP ECC or SAP S/4HANA release, Eclipse/ADT configuration, and required object scope. The evaluation covers the environments and capabilities supported for your use case.
How do we measure the value?
Compare the Aceteroid-assisted workflow with your current approach. Measure total human engineering effort, manual corrections, review time, and whether the output meets the agreed acceptance criteria. Time to an initial suggestion is one milestone; the evaluation also considers the work needed to reach an accepted result.
Is our code used to train AI models?
No. Customer code, prompts, specifications, and outputs are not used to train or fine-tune foundation models and are not shared across customers.
Can Aceteroid change our system on its own?
Write, activation, and deployment actions are separated from analysis and proposal activities and are not enabled by default. Your developers retain approval responsibility through your existing SAP process.
Do we need to share source code for the first conversation?
No. We begin with the requirement, environment, and delivery challenge. Code is shared only after permission and an approved access route are agreed.
What is the next change your business needs from SAP?
Start with the custom ABAP behind it. Discuss the requirement, understand the evaluation scope, and decide whether Aceteroid fits your team’s work.