Skip to content
Clean-Core.ioFree Community Edition
Demo project — fictitious code, with the engine’s reading on every stage and no model drafts or test runs. Nothing you do here is saved. A demo run is never signed. No signed run, no audit pack and no export comes out of this screen — a signature says a named account analysed a named source, and none of that happened here.Nothing here counts against your five free analyses: the demo is the same for every account, and what you change lives in this browser only.Try an example or your own code
Back to project workspace
DemoPlan only

Demo · Z_MM_PO_APPROVAL — Transformation

22 findings with a target route. The transformed code is a model's work and the demo has none.

Generated package

—objects · none in a demo

The demo stops where the model begins.
Plan from the engine

22of 23 findings with a target option

1 left out — no target option, not guessed at26 places in the code
Released successors

8of 23 named

6 distinct APIs and CDS views
Grounding audit

—no audit in a demo

It checks generated code, and a demo has none.

Codenone in a demoPlanengine, no modelCompilednoRunonly against mocks in Testing

From your code to the generated package

band width = number of findings
  • 1 Direct write to an SAP standard tableReleased API or CDS view
  • 2 Writes to custom tablesCustom persistence
  • 1 Batch input to a transactionNo released successor
  • 7 Direct reads of SAP standard tablesReleased API or CDS view
  • 2 Direct reads of SAP standard tablesNo released successor
  • 2 Calls of classic APIs not released for ABAP CloudNo released successor
  • 1 Decision on the server's date or timeThe project route · In-app ABAP Cloud
  • 1 Explicit transaction controlThe project route · In-app ABAP Cloud
  • 1 File transfer through the SAP GUINo released successor
  • 3 Table accessesCustom persistence
  • 1 Security review taskOutside the project route
  • 1 Authorization checkThe project route · In-app ABAP Cloud
  • Generated · none in a demo
  • The demo stops where the model begins.

Released API or CDS viewNo released successorCustom persistenceThe project route · In-app ABAP CloudOutside the project routemodel proposal

Generated package

In a real run the model writes the package against the plan below. The demo makes no model call, so it has none.

The demo stops where the model begins.

The transformed code comes out of a model call against your source in a real run. Writing a convincing one by hand is the one thing this product may never do — what you see below is what the deterministic engine produced.

From finding to change

your code → target → generated
  1. 240UPDATE eban SET statu = 'H' WHERE banfn = p_banfn AND bnfpo = p_bnfpo
    CriticalSource line 240Direct write to SAP standard table EBAN
    Target · catalog
    API_PURCHASEREQUISITION_SRV
    Released OData API named by the catalog
    Imported· OData API · Clean-Core.io curated mapping, compiled for 2024.FPS02
    Generated change

    The demo stops where the model begins — a real run writes this change; the demo makes no model call.

  2. 353INSERT zmm_po_appr FROM ls_appr
    HighSource line 353Direct write to custom table ZMM_PO_APPR
    Target · your code
    Custom persistence
    ZMM_PO_APPR — where it lives after the move is not determined here
    Generated change

    The demo stops where the model begins — a real run writes this change; the demo makes no model call.

  3. 515CALL TRANSACTION 'ME21N' USING lt_bdc MODE 'N' UPDATE 'S' MESSAGES INTO lt_msg
    HighSource line 515Legacy batch data communication (BDC) to TCode ME21N
    Target · catalog
    No released successor
    Options: Developer Extensibility / RAP · Side-by-Side CAP · Integration Suite
    Generated change

    The demo stops where the model begins — a real run writes this change; the demo makes no model call.

Plan by kindReconstructed· engine

One line per kind of finding: how many there are, and for how many the catalog names a released successor.

  • Direct write to an SAP standard table1 / 1
  • Writes to custom tables0 / 2
  • Batch input to a transaction0 / 1
  • Direct reads of SAP standard tables7 / 9
  • Calls of classic APIs not released for ABAP Cloud0 / 2
  • Decision on the server's date or time0 / 1
  • Explicit transaction control0 / 1
  • File transfer through the SAP GUI0 / 1
  • Table accesses0 / 3
  • Security review task0 / 1
  • Authorization check0 / 1

released successor named none in the catalog