sc4sap:create-object

SC4SAP Create Object

Guided ABAP object creation workflow. Hybrid mode: confirms transport and package interactively, then auto-creates, writes initial code, and activates the object.

<Response_Prefix> Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary>] per ../../common/model-routing-rule.md § Response Prefix Convention. </Response_Prefix>

<Phase_Banner> Multi-phase skill. Before each Agent(...) dispatch, emit ▶ phase=<id> (<label>) · agent=<name> · model=<Opus 4.7|Sonnet 4.6|Haiku 4.5> per ../../common/model-routing-rule.md § Phase Banner Convention. </Phase_Banner>

<Use_When>

• User says "create", "new class", "new program", "create object", "add a function module", "new table", etc.
• A new ABAP development artifact needs to be created from scratch
• User knows what they want to build but needs the creation scaffolded correctly </Use_When>

<Do_Not_Use_When>

• Modifying an existing object -- use direct MCP Update* tools (UpdateClass, UpdateProgram, UpdateInclude, etc.)
• Creating multiple interdependent objects -- use /sc4sap:create-program for a full program with includes
• User just wants to understand what type to use -- ask a module consultant agent directly </Do_Not_Use_When>

<Session_Trust_Bootstrap> MANDATORY — runs as Step 0 before any MCP call or user interaction.

Invoke /sc4sap:trust-session with parent_skill=sc4sap:create-object to pre-grant all MCP tool + file-op permissions for this session (eliminates per-tool "Allow this tool?" prompts during Create* + activation flow).

• If .sc4sap/session-trust.log already has a line within the last 24h, skip silently.
• Otherwise run it and surface the one-line confirmation.

Full spec: see ../trust-session/SKILL.md. </Session_Trust_Bootstrap>

<Supported_Object_Types>

Type	MCP Create Tool	Description
Class	CreateClass	ABAP OO class (local or global)
Interface	CreateInterface	ABAP OO interface
Program	CreateProgram	Executable program (report)
Function Module	CreateFunctionModule + CreateFunctionGroup	RFC-capable function module
Table	CreateTable	Transparent database table
Structure	CreateStructure	ABAP structure (type definition)
Data Element	CreateDataElement	Domain-based data element
Domain	CreateDomain	Value domain with fixed values or ranges
CDS View	CreateView	Core Data Services view
Service Definition	CreateServiceDefinition	OData service definition
Service Binding	CreateServiceBinding	OData service binding (UI5/API)
Behavior Definition	CreateBehaviorDefinition	RAP behavior definition
Screen	CreateScreen	Dynpro screen (selection screen or dialog)
GUI Status	CreateGuiStatus	PF-Status (menu bar, toolbar, function keys)
</Supported_Object_Types>

<ECC_DDIC_Fallback> MANDATORY: Read ../../common/ecc-ddic-fallback.md before creating any Table / Data Element / Domain. It defines when the ECC branch triggers, the helper-program naming rules, the strict template format (mirroring the files under ecc/), and the hard constraints ($TMP only, no activate, no CTS). </ECC_DDIC_Fallback>

<Field_Typing_Rule> MANDATORY for every Table / Structure / Table Type field-type decision (standard MCP flow and ECC helper-program fallback): read ../../common/field-typing-rule.md.

Priority: Standard DE (1) → existing CBO DE (2) → new CBO DE (3) → Data Type + Length (4, last resort). Raw primitives like LIFNR CHAR 10 / MATNR CHAR 40 / BUKRS CHAR 4 are forbidden when an authoritative SAP data element exists. Before each field, run SearchObject against DTEL and check .sc4sap/cbo/<MODULE>/<PACKAGE>/inventory.json. </Field_Typing_Rule>