sap-se41

Automate SE41 PF-STATUS subobject management via SAP GUI Scripting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

SE41 PF-STATUS management for SAP GUI scripting can be tedious and error-prone when performed manually. This skill consolidates the PF-STATUS lifecycle (CREATE, UPDATE, DISPLAY, DELETE, ACTIVATE, DEACTIVATE, COPY, CHECK) into a repeatable, script-driven workflow, reducing repetitive clicks and human error.

Core Features & Use Cases

  • One-run operation per PF-STATUS per program, driven by a self-contained VBScript embedded in SKILL.md.
  • Creates and updates statuses from a definition file, applies changes, and ensures activation with built-in handling of prompts and errors.
  • Supports copying statuses across programs and checking existence, with SAP GUI session management and transport/package delegation via /sap-change-package.

Quick Start

Login to SAP with sap-login, then run an SE41 operation (CREATE/UPDATE/DISPLAY/DELETE/ACTIVATE/CHECK) for a given program and status.

Frequently Asked Questions about sap-se41

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

FAQPage Schema
How do I automate PF-STATUS creation and updates in SE41 using SAP GUI scripting?▼

PF-STATUS creation and updates in SE41 are automated using embedded VBScript workflows that apply status definitions and handle SAP GUI prompts. This script-driven approach reduces repetitive clicks and manages the entire lifecycle per program and status pair.

Can I copy a GUI status across different programs with SAP GUI scripting?▼

Yes, you can copy GUI statuses across programs using the COPY operation. The scripting workflow manages the source and target program/status pairs within an active SAP GUI session to duplicate the PF-STATUS subobjects.

What SAP GUI scripting operations are available for managing SE41 GUI statuses?▼

Available SE41 GUI status operations include CREATE, UPDATE, DISPLAY, DELETE, ACTIVATE, DEACTIVATE, COPY, and CHECK. Each operation runs as a self-contained workflow driven by inline VBScript embedded in the skill documentation.

Do I need an active SAP GUI session to run SE41 status activation and deactivation scripts?▼

Yes, an active SAP GUI session is required to execute SE41 status activation and deactivation scripts. You must log in to SAP first, then run the desired operation for a given program and status to ensure proper session management.

Why does my SE41 PF-STATUS script fail during transport or package assignment?▼

SE41 PF-STATUS scripts may fail during package assignment if transport requests are not handled correctly. The workflow delegates transport and package management to the /sap-change-package operation to ensure proper SAP system configuration.

Best way to check if a PF-STATUS already exists for a program before creating a new one?▼

The best way to check if a PF-STATUS exists is to run the CHECK operation for the specified program and status pair. This verifies existence within the active SAP GUI session before attempting a CREATE operation.