rap-bo-designlisted

# abap-cloud-rap:rap-bo-design Design a new RAP business object end-to-end and create it via the SAP ABAP MCP Server. ## What this command does You are designing a complete RAP business object from a short spec, then creating it in the connected ABAP system. The official ADT MCP Server (in `SAPSE.adt-vscode`) exposes three RAP **generators** that bootstrap a conformant stack in one call — that is the primary path. You then validate the generated stack against the rules in `../CLAUDE.md` and refine it. The "hand-crafted skeleton" path is a **fallback** for cases the generators do not fit. **Tool routing.** Read the `## Tooling` section in `../CLAUDE.md` before the first tool call. This skill is write-heavy, so the official server owns nearly all of it: | Step | Primary | Fallback | |---|---|---| | Generate a full RAP stack in one call | `abap-adt` `abap_generators-*` | none — no other server has the generators | | Create individual objects, activate, transports | `abap-adt` `abap_creation-*`, `abap_activate_objects`, `abap_transport-*` | `arc-1` `SAPWrite` + `SAPActivate` when write scope is enabled (`SAPManage action="create_package"` for the package; syntax-check each artifact with `SAPDiagnose action="syntax"` before writing) | | Confirm the target package exists / inspect it | `arc-1` `SAPRead type=DEVC` | proceed and let creation fail loudly | | **Read back the generated source for the post-generation review** | `arc-1` `SAPRead` (`type=DDLS` / `BDEF` / `SRVD` / `CL