generate-rap-logic

Generate RAP Business Logic

Generate RAP determination, validation, and custom action implementations for an existing behavior definition. Reads the RAP stack, identifies empty method stubs (or missing handler signatures) in the behavior pool, and generates ABAP Cloud implementation code.

This skill replicates SAP Joule's "RAP Logic Prediction" capability by combining ARC-1 (SAP system access) with mcp-sap-docs (documentation & best practices).

Smart Defaults (apply silently, do NOT ask)

Setting	Default	Rationale
Entity access	IN LOCAL MODE always	Inside behavior pool, no auth check needed
Message style	Hardcoded text via new_message_with_text()	Simplest for prototyping; use MSAG for production (see Notes)
Scope	All empty methods	User can narrow after seeing the list
Error handling	FAILED + REPORTED structures	Standard RAP error propagation

Input

The user provides a behavior definition name (e.g., ZI_TRAVEL).

Only the behavior definition name is required. If the user provides just a BDEF name, apply Smart Defaults and proceed to read the stack and present available methods.

Optionally, the user may specify:

• Specific determination/validation (default: list all and let user choose)
• Behavior description — natural language description of desired logic (e.g., "calculate total price from line items", "validate status transitions")

Step 1: Read the RAP Stack

Read the behavior definition, CDS view, and behavior pool to understand the complete RAP context.

1a. Read the behavior definition

SAPRead(type="BDEF", name="<bdef_name>")

⚠️ FAIL-FAST GATE: If the BDEF read fails with 404, the object may not exist — verify the name via SAPSearch. If it fails with 415, check SAPManage(action="probe") for system info and inform the user about the issue.

Parse the BDEF source to identify:

• Scenario: managed / unmanaged / abstract
• Determinations: determination <Name> on (modify|save) { ... }
• Validations: validation <Name> on save { ... }
• Actions: action <Name> ...
• Draft status: with draft present or not
• Entity aliases: alias <Alias>
• Persistent table: persistent table <table_name>
• Behavior pool class: implementation in class <class_name> unique