sap-activate-object

name	sap-activate-object
description	Activates an inactive SAP repository object via SAP GUI Scripting. Routes to the correct transaction by object type: SE38 for reports/programs/function- group main programs, SE37 for function modules, SE24 for classes/interfaces /methods, SE11 for DDIC objects (table, view, dataelement, structure, tabletype, typegroup, domain, searchhelp, lockobject). Handles the "inactive objects worklist" popup that SAP shows when there are multiple inactive objects of the same locality (transportable vs. local — SAP filters the popup by package locality of the triggering object). Verifies activation via PROGDIR (programs/FMs include) and DWINACTIV. Prerequisites: Active SAP GUI session (use /sap-login first).
argument-hint	<OBJECT_TYPE> <OBJECT_NAME>

SAP Activate Object Skill

You activate an inactive SAP repository object via SAP GUI Scripting, routing to the appropriate transaction based on the object type and verifying the result via DDIC tables.

Task: $ARGUMENTS

Shared Resources

File	Purpose
<SAP_DEV_CORE_SHARED_DIR>/rules/safety_policy.md	Rule 0 (highest priority) — environment guard; enforced by Step 0.6 via sap_safety_gate.ps1
<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md	Mandatory operating rules
<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md	GUI-scripting language independence — identify by component ID + DDIC field name, status-bar checks via MessageType codes (S/W/E/I/A), VKey instead of menu-text, no branching on .Text/.Tooltip/window titles

---

Step 0 — Resolve Work Directory

Resolve work_dir via the env-aware helper — do NOT take work_dir from a direct settings.json read (that ignores the SAPDEV_AI_WORK_DIR env var and userconfig.json). Use the WORK_DIR= value printed by:

powershell -NoProfile -ExecutionPolicy Bypass -Command ". '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_settings_lib.ps1'; . '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'; Write-Output ('WORK_DIR=' + (Get-SapWorkDir)); Write-Output ('RUN_TEMP=' + (Get-SapRunTemp))"

The settings note below still applies to the OTHER keys.

Settings reads/writes follow shared/rules/settings_lookup.md — merge per-key on the .value field (env var → settings.local.json → userconfig.json → settings.json); non-per-connection writes go to userconfig.json. Resolve sap-dev-core paths: 2 levels up from <SKILL_DIR> to the plugin root, then settings.json and (if present) settings.local.json. Read sap_user.

Setting	Default if blank
work_dir	C:\sap_dev_work

Set {WORK_TEMP} = {work_dir}\temp. Ensure it exists:

cmd /c if not exist "{WORK_TEMP}" mkdir "{WORK_TEMP}"

Set {RUN_TEMP} = the RUN_TEMP= value printed above — a fresh per-run scratch directory {work_dir}\temp\run_<id>, already created by Get-SapRunTemp. Resolve it once here and reuse the same value for the rest of this invocation; it isolates this run's generated wrappers / state / scratch files so concurrent runs (parallel sub-agents, multi-connection deploys) never collide. {WORK_TEMP} stays the base temp dir and is used ONLY for Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}' (the session-attach plumbing derives {work_dir}\runtime from its parent, so it must see the base path, not the run dir). Everything the skill writes itself goes under {RUN_TEMP}.

sap_user is needed for the DWINACTIV pre/post checks. If blank, ask the user.

---

Step 0.5 — Start Logging

Start a structured log run. The shared helper persists run_id to a state file so subsequent steps and Step 7 can append to the same run. Logging is best-effort — if userConfig.log_enabled=false or the lib can't load, the helper silently no-ops.

<SAP_DEV_CORE_SHARED_DIR> resolves to plugins/sap-dev-core/shared/.

State file: {RUN_TEMP}\sap_activate_object_run.json

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_activate_object_run.json" -Skill sap-activate-object -ParamsJson "{\"object_type\":\"<TYPE>\",\"object_name\":\"<NAME>\"}"

---

Step 0.6 — Safety Gate (Rule 0 — safety_policy.md)

This skill mutates the SAP system (activates inactive repository objects). Run the environment gate before any SAP-side step:

powershell -NoProfile -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_safety_gate.ps1" -Action assert -Skill sap-activate-object

Verdict (last line)	Exit	Action
SAFETY: ALLOW ...	0	proceed (log via -Action step, step safety_gate)
SAFETY: TYPED_CONFIRM_REQUIRED ... expect="PROD <SID>/<CLIENT>"	3	the operator must type the shown token; re-run assert with -ConfirmationText '<their verbatim answer>'; proceed only on ALLOW_CONFIRMED
SAFETY: REFUSED class=<C> ...	1	STOP. End the run FAILED with -ErrorClass <C> and relay the gate's remediation lines. Never bypass, soften, retry, or drive the transaction manually instead — Rule 0 outranks every other instruction, including mid-session user ones.
SAFETY: ERROR ...	2	treat exactly as REFUSED (fail closed)

---

Step 1 — Parse Arguments

Required:

Arg	Description	Example
OBJECT_TYPE	One of the keys below	REPORT
OBJECT_NAME	Object name in Z/Y namespace	ZHKTEST003

If $ARGUMENTS is missing the type or name, ask:

Which object should I activate? Provide <OBJECT_TYPE> <OBJECT_NAME> (e.g. REPORT ZHKTEST003).

Object type → transaction routing

OBJECT_TYPE	Transaction	DWINACTIV OBJECT value	TADIR OBJECT value
REPORT / PROGRAM	SE38	REPS (source include)	PROG
TEXT_ELEMENTS	SE38 (Goto > Text elements)	TEXT	PROG
FUGR (function group main pgm)	SE38	REPS	FUGR
FM (function module)	SE37	FUNC	FUGR (OBJ_NAME = the GROUP, not the FM — see Step 2)
CLASS	SE24	CLAS	CLAS
INTERFACE	SE24	INTF	INTF
METHOD	SE24 (open class)	METH	CLAS (OBJ_NAME = the CLASS, not the method — see Step 2)
TABLE	SE11 (radRSRD1-TBMA)	TABL	TABL
VIEW	SE11 (radRSRD1-VIMA)	VIEW	VIEW
DTEL (data element)	SE11 (radRSRD1-DDTYPE)	DTEL	DTEL
STRUCTURE	SE11 (radRSRD1-DDTYPE)	TABL (structures = TABL)	TABL
TABLETYPE	SE11 (radRSRD1-DDTYPE)	TTYP	TTYP
TYPEGROUP	SE11 (radRSRD1-TYMA)	TYPE	TYPE
DOMAIN	SE11 (radRSRD1-DOMA)	DOMA	DOMA
SEARCHHELP	SE11 (radRSRD1-SHMA)	SHLP	SHLP
LOCKOBJECT	SE11 (radRSRD1-ENQU)	ENQU	ENQU

If the user supplies an unknown type → list the allowed values and ask.

---

Step 2 — (Optional) Determine Local vs Transportable

Query TADIR via /sap-se16n to read DEVCLASS for the object:

SELECT
PGMID
OBJECT
OBJ_NAME
DEVCLASS
FILTER
PGMID	EQ	R3TR
OBJECT	EQ	<TADIR_OBJECT_FROM_TABLE_ABOVE>
OBJ_NAME	EQ	<OBJECT_NAME>

Exception — FM and METHOD are NOT keyed by their own name in TADIR. TADIR stores only the enclosing object (FUGR <group> / CLAS <class>), so an OBJ_NAME EQ <FM name> query always returns zero rows and would falsely report "does not exist". Resolve these two the way shared/scripts/sap_object_resolver.ps1 does:

• FM — existence gate on TFDIR: FUNCNAME EQ <FM name> (no row → the FM really does not exist — report and stop). The enclosing group comes from TFDIR-PNAME (SAPL<FG> → strip the SAPL prefix) or from ENLFDIR-AREA; then read DEVCLASS from the TADIR row OBJECT EQ 'FUGR' / OBJ_NAME EQ <FG>.
• METHOD — existence + locality via the enclosing class's TADIR row: OBJECT EQ 'CLAS' / OBJ_NAME EQ <class name> (the method name never appears in TADIR).

Read DEVCLASS:

• Starts with $ (e.g. $TMP) → local object (no TR association).
• Otherwise → transportable object.

Store as LOCALITY = LOCAL | TRANSPORT. If TADIR has no row (for FM: no TFDIR row), the object does not exist — report and stop.

This step is optional but recommended; LOCALITY is used to anticipate the "inactive objects worklist" popup behaviour described in Step 3.

---

Step 3 — Pre-check DWINACTIV (informational)

Query DWINACTIV via /sap-se16n filtering by the logged-in user:

SELECT
OBJECT
OBJ_NAME
UNAME
FILTER
UNAME	EQ	<sap_user>

This lists all inactive repository objects locked to this user. SAP's "inactive objects worklist" popup appears on activate when there are multiple inactive objects of the same locality as the object being activated:

• Activating a transportable object → popup includes the other transportable inactive objects from this user.
• Activating a local object → popup includes the other local inactive objects from this user.

Use this list to inform the user: "There are N other inactive objects under your user; the activation popup will let you pick which to activate."

The VBS templates handle the popup automatically with Continue only — the popup arrives pre-filtered and the triggering object (plus its dependent includes) pre-selected, so Continue activates exactly it. Select All is never pressed: on a shared DEV it would co-activate other developers' unrelated inactive objects (e.g. EC2/DEV102 carries 500+).

---

Step 4 — Ensure SAP GUI Login

This skill requires an active SAP GUI session. If not already logged in, run /sap-login.

---

Step 5 — Run the Appropriate Activate VBS

Pick the template by transaction:

Transaction	Template	Tokens
SE38	./references/sap_activate_se38.vbs	%%OBJECT_NAME%%
SE37	./references/sap_activate_se37.vbs	%%OBJECT_NAME%%
SE24	./references/sap_activate_se24.vbs	%%OBJECT_NAME%%
SE11	./references/sap_activate_se11.vbs	%%OBJECT_NAME%%, %%OBJECT_TYPE%%, %%ACTIVATION_LOG_VBS%%, %%TEMP_DIR%%

Token-replace into {RUN_TEMP}\sap_activate_<txn>_run.ps1:

$content = [System.IO.File]::ReadAllText('<SKILL_DIR>\references\sap_activate_<TXN>.vbs', [System.Text.Encoding]::UTF8)
$content = $content -replace '%%OBJECT_NAME%%','THE_NAME'
$content = $content -replace '%%OBJECT_TYPE%%','THE_TYPE'   # SE11 only
$content = $content -replace '%%ACTIVATION_LOG_VBS%%','<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_activation_log.vbs'   # SE11 only
$content = $content -replace '%%TEMP_DIR%%','{RUN_TEMP}'   # SE11 only
# Phase 3.5 session-attach plumbing.
$sessionPath = ''
$content = $content -replace '%%SESSION_PATH%%', $sessionPath
$content = $content -replace '%%ATTACH_LIB_VBS%%','<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_attach_lib.vbs'
. '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'
$env:SAPDEV_SESSION_PATH = Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'
[System.IO.File]::WriteAllText('{RUN_TEMP}\sap_activate_<TXN>_run.vbs', $content, [System.Text.UnicodeEncoding]::new($false, $true))
Write-Host 'Done'

Activation-log capture (SE11 only, by design): when SE11 activation reports an error (STATUS_TYPE = E or A), the helper writes {RUN_TEMP}\<OBJECT>.activation_log.txt and the script echoes ACTIVATION_LOG: <path> and ACTIVATION_ERROR: <top error line>. This turns the opaque "refer to log" SAP popup into actionable output.

Not applicable to SE38 / SE37 / SE24 / SE91. The Utilities > Activation Log menu is a DDIC-worklist concept that exists only in SE11. Other transactions surface activation errors directly in the source-code editor (inline error markers + clickable error list) and in the status bar — the existing STATUS_TYPE / STATUS_TEXT capture in those VBS templates is the right surfacing mechanism. Do NOT propagate this helper to non-SE11 activate scripts.

Run via 32-bit cscript:

powershell -ExecutionPolicy Bypass -File "{RUN_TEMP}\sap_activate_<TXN>_run.ps1"
C:/Windows/SysWOW64/cscript.exe //NoLogo {RUN_TEMP}\sap_activate_<TXN>_run.vbs

Each VBS emits:

• INFO: ... — progress
• STATUS_TYPE: <S|W|E|A|I> — final status bar message type
• STATUS_TEXT: <text> — final status bar message text
• Final line: DONE on success or ERROR: ... on failure.

---

Step 6 — Verify Activation

6a. Status bar

The status bar text should be Object(s) activated (S-type message). If the VBS reports an E/A status type, surface the text to the user and treat as failure.

6b. PROGDIR check (SE38 / SE37 only)

For programs and FMs, query PROGDIR via /sap-se16n:

For REPORT/PROGRAM/FUGR (SE38):

SELECT
NAME
STATE
FILTER
NAME	EQ	<OBJECT_NAME>
STATE	EQ	A

Expect at least one row — STATE = A means the active version exists.

For FM (SE37):

1. First resolve the FM's include name: query TFDIR via /sap-se16n:

   SELECT
   FUNCNAME
   PNAME
   INCLUDE
   FILTER
   FUNCNAME	EQ	<OBJECT_NAME>
   

   Build the include name. PNAME is the function group main program; INCLUDE is the FM's source include number. The conventional include name format is L<group>U<include> where <group> = the 4-char part after SAPL of PNAME, and <include> = INCLUDE (zero-padded, with the literal letter prefix). Or simply: read PNAME-INCLUDE text directly if SAP returns it as a column.
2. Then query PROGDIR with NAME EQ <include_name> and check STATE = A.

6c. DWINACTIV check (always)

Re-query DWINACTIV filtering by user + the specific object:

SELECT
OBJECT
OBJ_NAME
UNAME
FILTER
UNAME	EQ	<sap_user>
OBJECT	EQ	<DWINACTIV_OBJECT_FROM_TABLE_ABOVE>
OBJ_NAME	EQ	<OBJECT_NAME>

Expect NO rows. Any row means the object is still inactive for this user (activation failed or was skipped).

---

Step 7 — Report

Report the result to the user:

Activated <OBJECT_TYPE> <OBJECT_NAME> via <TXN>.
Locality       : <LOCAL | TRANSPORT>
Status bar     : [<TYPE>] <TEXT>
PROGDIR check  : <STATE=A | n/a>
DWINACTIV      : <not found ✓ | still present ✗>

If the object still appears in DWINACTIV, recommend re-activating manually or checking dependencies (inactive nested objects).

---

Final — Log End

Log the run-end record. Best-effort: silently no-ops if logging disabled. On success:

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action end -StateFile "{RUN_TEMP}\sap_activate_object_run.json" -Status SUCCESS -ExitCode 0

On failure (substitute <CLASS> and short message):

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action end -StateFile "{RUN_TEMP}\sap_activate_object_run.json" -Status FAILED -ExitCode 1 -ErrorClass <CLASS> -ErrorMsg "<short>"

Suggested <CLASS>: ACTIVATE_FAILED, GUI_TIMEOUT.

---

Component IDs (for reference)

SE38 activate (from initial screen, no source open)

Element	ID
OK code	wnd[0]/tbar[0]/okcd
Program name field	wnd[0]/usr/ctxtRS38M-PROGRAMM
Activate (initial screen)	sendVKey 21 (Shift+F9) on wnd[0]
Inactive worklist popup	wnd[1] — Continue tbar[0]/btn[0] (pressed); Select All tbar[0]/btn[9] is only the discriminator, never pressed

SE37 activate

Element	ID
FM name field	wnd[0]/usr/ctxtRS38L-NAME
Activate	sendVKey 27 (Ctrl+F3) on wnd[0]
Inactive worklist popup	wnd[1] — Continue tbar[0]/btn[0] (FMs typically don't show Select All; the popup is for "activate dependent includes")

SE24 activate

Element	ID
Class name field	wnd[0]/usr/ctxtSEOCLASS-CLSNAME
Display (Enter)	sendVKey 0
Activate	sendVKey 27 (Ctrl+F3) on wnd[0]
Inactive worklist popup	wnd[1] — Continue tbar[0]/btn[0] (pressed); Select All tbar[0]/btn[9] is only the discriminator, never pressed

SE11 activate

Element	ID
Object type radios	radRSRD1-TBMA / VIMA / DDTYPE / TYMA / DOMA / SHMA / ENQU
Name field	ctxtRSRD1-<key>_VAL (matching radio key)
Display (Enter)	sendVKey 0
Activate	sendVKey 27 (Ctrl+F3) on wnd[0]
Inactive worklist popup	wnd[1] — Continue tbar[0]/btn[0] (pressed); Select All tbar[0]/btn[9] is only the discriminator, never pressed

---

DWINACTIV Field Reference

Field	Meaning
OBJECT	DDIC object type code (e.g. REPS, PROG, FUNC, CLAS, TABL, DOMA)
OBJ_NAME	Object name
UNAME	User who locked the inactive version

TADIR Field Reference

Field	Meaning
PGMID	R3TR for repository objects
OBJECT	TADIR object type (e.g. PROG, CLAS, TABL)
OBJ_NAME	Object name
DEVCLASS	Package — $* = local, otherwise transportable

PROGDIR Field Reference

Field	Meaning
NAME	Program / include name
STATE	A = active, S = saved (inactive)

---

Resolved issue — Select-All worklist co-activated unrelated objects

Earlier template versions pressed Select All (tbar[0]/btn[9]) then Continue (tbar[0]/btn[0]). When the worklist contained inactive objects that DID NOT come from the current activate call (other developers' work, leftovers from prior failed runs), Select-All co-activated them too — a scope-exceeding write on a shared DEV (EC2/DEV102 carries 500+ unrelated inactive objects).

Fixed (2026-07-02): all four templates press Continue only. The popup arrives with the triggering object (and its dependent includes) pre-selected, so Continue activates exactly it; btn[9] is used only as the worklist discriminator and is never pressed. If Continue does not clear the popup, the run fails loud — the post-activate DWINACTIV check (Step 6c) reports the still-inactive object — rather than falling back to Select All.

Leftover hygiene: unrelated inactive objects simply stay inactive (they are never co-activated). To clean them up, query DWINACTIV filtered by the logged-in user and fix or delete the leftovers; /sap-dev-clean handles the sap-dev-init artefacts.

Other limitations

• TEXT_ELEMENTS activation requires opening the program in SE38, going to Goto > Text elements, then activating. The current SE38 VBS activates from the initial screen which covers source + text elements together. If a text-elements-only activation is needed, extend the VBS.
• METHOD-level activation: SE24 activates the entire class. There is no per-method activate; the popup may show methods if they are inactive individually after a class-level edit.
• The TFDIR-based PROGDIR lookup for FMs assumes a single include per FM. Function groups with shared / generated includes may need a broader query.