Representative engine outputs. Every example is a real transformation—verified, compiled, and tested against Clean-Core Engine v1.7.4.
A sales operations team needs to query open standard orders (type 'OR') from SAP to populate a real-time order fulfillment dashboard. The legacy ABAP directly reads the VBAK database table — a non-released internal structure that breaks during S/4HANA upgrades. The engine transforms this into a clean CDS view consuming the released I_SalesOrder API, preserving the exact filter logic while making it upgrade-safe and unit-testable.
" Direct table read — violates Clean Core
SELECT vbeln, erdat, netwr
FROM vbak
INTO TABLE @DATA(lt_orders)
WHERE auart = 'OR'.define view entity ZI_SalesOrderCustom
as select from I_SalesOrder
{
key SalesOrder as SalesOrderNumber,
CreationDate as OrderDate,
TotalNetAmount as NetAmount
}
where SalesOrderType = 'OR';CLASS ltcl_sales_order DEFINITION FINAL FOR TESTING
DURATION SHORT RISK LEVEL HARMLESS.
PRIVATE SECTION.
CLASS-DATA environment TYPE REF TO if_cds_test_environment.
CLASS-METHODS class_setup.
CLASS-METHODS class_teardown.
METHODS test_order_filter FOR TESTING.
ENDCLASS.
CLASS ltcl_sales_order IMPLEMENTATION.
METHOD class_setup.
environment = cl_cds_test_environment=>create( i_for_entity = 'ZI_SALESORDERCUSTOM' ).
ENDMETHOD.
METHOD class_teardown.
environment->destroy( ).
ENDMETHOD.
METHOD test_order_filter.
" Arrange — insert test double data
DATA lt_mock TYPE STANDARD TABLE OF I_SalesOrder.
lt_mock = VALUE #(
( SalesOrder = '100' SalesOrderType = 'OR' )
( SalesOrder = '200' SalesOrderType = 'RE' ) ).
environment->insert_test_data( i_data = lt_mock ).
" Act — read via CDS projection
DATA lt_result TYPE STANDARD TABLE OF ZI_SalesOrderCustom.
SELECT * FROM ZI_SalesOrderCustom
INTO TABLE @lt_result.
" Assert — only type OR should pass the filter
cl_abap_unit_assert=>assert_equals( act = lines( lt_result ) exp = 1 ).
ENDMETHOD.
ENDCLASS.Table VBAK → Resolved to released API I_SalesOrder (SAP API Business Hub).
Every feature listed here is live and free to use—start with 5 transformations or bring your own API key for unlimited access.
Intelligently classifies legacy custom logic against SAP Clean Core guidelines, automatically separating In-App ABAP Cloud (RAP) from Side-by-Side BTP (CAP) tracks.
Directly maps legacy database table operations to released, public standard SAP APIs with interactive links to official API Hub listings.
Generates clean In-App ABAP Cloud RAP handlers formatted as standard abapGit directories (src/ and abapgit.xml) for local ADT import, or decoupled BTP CAP Node.js services.
Quantifies technical debt and custom IP value. Features an interactive C-Level TCO & ROI calculator predicting upgrade-impact savings based on Clean Core Scores.
Provides a visual compliance HUD flagging complex SQL joins, OO inheritance chains, and syntax quirks. Generates local ABAP-Unit test classes to verify execution.
Maps modernized processes into standard BPMN 2.0 XML with swimlanes. Features a two-stage blueprint layer mapping RACI matrices, Level 5 SOP narratives, and internal compliance controls.
European hosting, GDPR-compliant by design, zero data retention. We built the security architecture the way we'd want it for our own SAP systems.
All workspaces, analytical engines, and database systems are hosted strictly in the europe-west1 GCP region (Belgium) ensuring high-speed processing.
Full enforcement of Art. 17 DSGVO. Purge all user footprints, uploads, and data in Settings. Transactional emails are securely routed via Resend API with DSGVO imprints.
Community-driven prototyping platform. Free access for SAP architects and developers to prototype decoupling strategies without licensing overhead.
Your BYOK API credentials are encrypted in transit, proxied securely server-side, and never trained or exposed to public LLM builders.
Start immediately with 5 free transformations, or bring your own API key to unlock unlimited access and full exports.
Register with name and email — approval within 24 hours.
Bring your own Google Gemini API key — saved locally in your browser.
Tenant connections are restricted to OData metadata reads and test execution. No write operations.
Learn moreCredentials and code are processed in memory only. Nothing is persisted on our servers.
Learn moreEvery tenant connection request is manually reviewed and approved to prevent misuse during the pilot phase.
Learn moreA complete, importable abapGit package generated by the Clean-Core Engine. Contains the Sales Order (VBAK → I_SalesOrder) CDS view, typed reader class, and 3 ABAP Unit tests with CDS Test Environment doubles. Import it directly into Eclipse ADT.
~5 KB · Ready for Eclipse ADT import