sc4sap:analyze-cbo-obj

To inventory ABAP CBO assets, supply a CBO package name to scan every project-built element like TABL, DTEL, and CLAS, then persist a structured index and inventory.json to enable downstream reuse.

Preventing duplicate ABAP development requires inventorying every CBO asset within a package and persisting a reusable index, which allows developers to locate and reuse proven tables, structures, and classes instead of recreating them.

Generating a reusable DDIC metadata index involves reading every ABAP element inside a specified CBO package, computing usage signals, and storing the outputs under the .sc4sap/cbo/<MODULE>/<PACKAGE>/ directory structure.

Yes, you can use a CBO package inventory during onboarding, ongoing development, and AMS engagements because it maps shared ABAP objects across programs and flags frequently used assets to boost integration stability.

The inventory focuses strictly on project-built ABAP elements within the specified CBO package, meaning it requires a valid package name to start and persists outputs only to the designated .sc4sap directory for downstream skills.

The CBO inventory persists outputs as both index.md and inventory.json, providing structured asset data that downstream skills like create-program and create-object can consult to find existing DDIC components.