sap-cc-inventory

Enumerate SAP custom objects via RFC or GUI exports for migration campaigns.

7|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-cc-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sap-cc-inventory
Source: https://github.com/sapdev-ai/sap-dev/tree/main/plugins/sap-migrate/skills/sap-cc-inventory
Command: npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-cc-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enumerates and classifies the custom (Z/Y / customer-namespace) repository objects in scope for an S/4HANA migration campaign. Reads TADIR (object directory) and TRDIR (program sub-type) over read-only RFC against the campaign's SOURCE system, writes inventory.tsv, and upserts every object into the campaign state ledger (state.tsv) as INVENTORIED — never altering objects already further along, so it is safe to re-run as new custom code appears. No SAP GUI, no writes, no transport request: pure read-only analysis. This is the first SAP-touching step of the sap-migrate pipeline; run it after /sap-cc-campaign init and before /sap-cc-usage. When RFC to the source is blocked, a GUI fallback (--source-mode GUI) ingests /sap-se16n exports of TADIR (+ optional TRDIR) instead -- identical output, no NCo. Scope defaults to the campaign brief's in_scope_packages (object-name prefixes such as Z*, Y*); override with --namespace, --packages (DEVCLASS patterns), --types, and --exclude. Prerequisites (RFC mode): SAP NCo 3.1 (32-bit, .NET 4.0) in GAC; a saved campaign's source connection profile (the campaign's source_profile) or a pinned /sap-login connection. GUI mode needs no NCo -- only a SAP GUI session for the /sap-se16n export step.

Core Features & Use Cases

  • Read-only RFC access to SAP TADIR/TRDIR data for inventory generation.
  • Writes inventory.tsv and upserts state.tsv with INVENTORIED entries, safe for re-runs.
  • GUI fallback using /sap-se16n exports when RFC is blocked, preserving filters and scope.
  • Integrates into the sap-migrate campaign workflow, producing a stable audit trail.

Quick Start

Run the inventory workflow for a campaign using RFC or GUI mode, filtered by your namespace or DEVCLASS patterns.

Frequently Asked Questions about sap-cc-inventory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory custom SAP objects for an S/4HANA migration?

Inventory custom SAP objects by reading TADIR and TRDIR tables via read-only RFC or GUI exports, generating inventory.tsv and upserting state.tsv with INVENTORIED entries without modifying existing records.

Can I inventory SAP custom objects when RFC access is blocked?

When RFC is blocked, inventory SAP custom objects using GUI mode to ingest /sap-se16n exports of TADIR and optional TRDIR, producing identical output without needing NCo.

What prerequisites do I need to extract SAP TADIR data via RFC?

Extracting SAP TADIR data via RFC requires SAP NCo 3.1 (32-bit, .NET 4.0) in the GAC and a saved campaign source connection profile or pinned /sap-login connection.

Is it safe to re-run the SAP custom object inventory process?

Re-running the SAP custom object inventory is safe because it upserts new objects as INVENTORIED while preserving existing state.tsv entries that have already progressed further.

How do I filter SAP custom objects by namespace during migration inventory?

Filter SAP custom objects during inventory using campaign brief defaults like in_scope_packages, or override with --namespace, --packages for DEVCLASS patterns, --types, and --exclude flags.

When should I run the SAP custom object inventory in the migration pipeline?

Run the SAP custom object inventory as the first SAP-touching step of the migration pipeline, after /sap-cc-campaign init and before /sap-cc-usage analysis.