Skip to main content

๐Ÿ”Ž AI@CustomCode Analysis

The Analysis page shows the ATC Analysis report of a cycle: one entry per finding, with the AI application's proposal. Here the leads decide whether each proposal can be implemented.

Analysis page โ€” finding list of CYCLE-01 (demo data)


Cycle and Versionโ€‹

FieldDescription
CycleThe cycles found in the reports, with the name from Config โ€บ Cycles. A closed cycle is marked (closed) and can no longer be signed.
VersionThe original report, or one of its review files. The latest review file opens by default, so you continue where the last reviewer stopped.

The line under the selection shows which file you are looking at, who saved it and when.


The Finding Listโ€‹

The chips above the list count the findings by complexity, review status and decision.

ColumnContent
ATC IDID of the entry in the report, e.g. ATC-0003
DescriptionTitle of the finding, with its tags
ObjectObject type and name, e.g. FUGR ZSD_DELIVERY_BLOCK
FindingsNumber of ATC messages grouped in the entry
CallsTotal production calls of the object (SCMON)
ModuleSAP module
PriorityATC priority P1โ€“P3
ComplexityC1 โ€“ simple code change ยท C2 โ€“ functional review ยท C3 โ€“ functional design
Review statusNot started, Ongoing (at least one comment or signature) or Done (all required signatures)
DecisionPending, Approved, With reserves or Rejected
Sign-offOne badge per required role: โœ“ signed, โ—‹ open
  • Search finds text in the ID, title, object, fields, module and tags.
  • Filters: module and tags (multiple choice), priority, complexity, review status and decision.
  • Sort: click a column header to sort ascending, again for descending, a third time to return to the report order. Empty values are always last. The sort is remembered.
  • Export CSV exports the filtered list with module, tags, calls, findings, decisions and signatures.

Click a row to open the finding.


The Finding Detailโ€‹

โ† Back to list, โ€น Previous and Next โ€บ move through the findings in the order of the list, with its filters and sort.

Finding detail โ€” classification, module and tags (demo data)

SectionContent
ClassificationComplexity, review status, priority, ATC check title and message, object, include, line, total number of calls, number of findings, SAP notes
Module & tagsSAP module and tags, see below
ATC finding descriptionWhat the code does and why ATC flags it
SAP note โ€“ symptom / solutionSummary of the SAP note
ABAP codeThe original code and the proposed modification side by side, with removed and added lines highlighted
DependenciesCallers, related objects and other findings
Functional impactsRisks for the business process
Functional proposed actionsWhat the functional team should confirm or test
Review & sign-offSignatures and the review log, see below

ABAP code โ€” original and proposed modification (demo data)


Module and Tagsโ€‹

Signed-in reviewers can:

  • change the module of a finding. The change is shown with its author and time (e.g. Changed: SD โ†’ LE). The implementation takes the module over from the analysis review.
  • add or remove tags from the list in Config โ€บ Tags.

Changes are written to the review file when you click Save review file.


Review and Sign-offโ€‹

Review & sign-off โ€” signatures and review log (demo data)

  1. Sign in on the Config page.
  2. Open a finding and choose Approved, With reserves or Rejected.
  3. Enter a comment โ€” mandatory unless Approved. Comments are read by the AI application and the project team.
  4. Click Validate & sign. A signature is not final: you can sign again later, and the latest signature of each role counts.
  5. When you are done, click Save review file.

Older review files may contain drafts from an earlier version of the workbench. They are shown as DRAFT โ€“ not counted, and the list shows how many findings have an unsigned draft. Open the finding โ€” your decision and comment are prefilled โ€” and click Validate & sign to make it count.

The required signatures follow the sign-off rules: the Dev Lead for C1, the Dev Lead and the Functional Lead for C2 and C3. The review log lists every comment and signature with name, role, user ID and time; the latest signature of each role counts.

Review filesโ€‹

Save review file writes ATC_Analysis_<CYCLE>_review_<date>_<time>.md to the Review output folder. The report itself is never changed.

  • Several reviewers can work at the same time. When you save, the workbench takes the newest review file and adds everyone's signatures, tag and module changes to it, so nobody's work is lost โ€” even if you had an older version open.
  • If parallel versions still exist (for example because a synced folder updated late), a banner shows N review versions were saved in parallel. Click Merge all versions to combine them into one new review file.
  • Review files are never changed or deleted; every save and every merge writes a new file.
  • The AI application reads the latest review file before the implementation, so decisions and comments flow into the next step.