sap-dev-clean

SAP development artefact cleanup removes wrapper FMs, DDIC objects, and utility programs in a reverse-dependency sequence. It applies safety gates and explicit confirmations at each step to preserve operator-added content unless explicitly overridden by optional flags.

Reverse-dependency deletion for SAP GUI scripting artefacts walks the dependency chain backwards, removing function modules, DDIC objects, and function groups in safe sequential order. Anchor-gate validation prevents destructive mis-targets during the removal process.

The best way to remove SAP Dev Init artefacts is a conservative, stepwise cleanup that guides pre-flight checks, deletes objects in reverse order, and performs post-flight validation across multiple object types like packages and utility programs.

Yes, you can use the --dry-run flag to test SAP artefact cleanup without deleting. It allows you to preview the conservative deletion sequence and safety gate checks before applying any actual changes to your environment.

SAP dev clean supports optional flags including --reset for full resets, --force to bypass standard safety gates, --settings to adjust per-connection configurations, and --dry-run for safe previewing of the artefact deletion process.

You should not use the --force flag during SAP development artefact cleanup when you need to preserve operator-added content. Bypassing the conservative safety gates and anchor mismatch guards risks destructive mis-targets across your function groups and DDIC objects.