sap-va01

Automate SAP sales order creation and updates via VA01/VA02/VA03 GUI scripting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manages SAP sales orders by automating VA01/VA02/VA03 operations through SAP GUI scripting, reducing manual data entry and human error.

Core Features & Use Cases

  • Create new sales orders (VA01) with header, sales tab, and item data from a field-definition file
  • Update existing orders (VA02) after an existence check (VA03) to ensure correct status and permissions
  • Check order existence (VA03) before updates or status verification
  • Requires an active SAP GUI session (login via /sap-login) and reuses SAP sessions across tasks
  • Supports a tab-separated field-definition format with sections HEADER, SALES, and ITEM_NN for precise data entry

Quick Start

Log in to SAP via /sap-login, then provide an order and a field-definition file to create or update a sales order.

Frequently Asked Questions about sap-va01

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

FAQPage Schema
How do I automate SAP sales order creation using GUI scripting?

Automate SAP sales order creation by using GUI scripting to execute VA01 with header, sales tab, and item data defined in a tab-separated field-definition file. This removes manual data entry errors.

Can I update existing SAP sales orders with VA02 after checking them in VA03?

Yes, you can check order existence and status using VA03 before executing VA02 updates. This ensures correct permissions and prevents errors during the automated sales order modification process.

What field-definition format is needed for SAP VA01 automation inputs?

SAP VA01 automation requires a tab-separated field-definition file structured with HEADER, SALES, and ITEM_NN sections to precisely map data entry fields for automated GUI scripting execution.

Do I need an active SAP GUI session to run VA01 automation scripts?

Yes, VA01 automation requires an active SAP GUI session established via login. The workflow reuses existing SAP sessions across tasks to execute end-to-end order handling operations.

What is the best way to handle end-to-end SAP sales order processing with GUI scripting?

The best approach uses VBScript templates to manage the entire end-to-end workflow: login, data resolution, create or update via VA01/VA02/VA03, and cleanup, reducing manual intervention.

Why does SAP VA02 automation require an existence check before updating sales orders?

VA02 automation requires an existence check via VA03 to verify order status and permissions before modification, preventing data corruption and ensuring the automated update targets a valid record.