alexz/arena-plm-fiori
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ADR-004: back out of on-stack RAP; retarget to starter customizing tenant

Browse Source 
Both tenants belong to the same starter system: my429480 is its
customizing tenant (client 100, key-user extensibility only, no ABAP)
and my431353 is its development tenant (client 080). This package had
recorded my429480 as "productive" and ADR-002 had assumed it offered
developer extensibility; both were wrong.

- ADR-004 withdraws the on-stack RAP route and moves the application to
  a side-by-side runtime against released OData APIs. ADR-002 marked
  superseded.
- Development tenant my431353 parked: all 19 ZARENA_PLM objects left
  active, sources kept in docs/handover/rap/ as reference, so the route
  stays reversible.
- Replacement host left open as OQ-11 (key-user extensibility vs CAP
  side-by-side); recommendation recorded as CAP. No build starts until
  OQ-11 is closed.
- RAP-dependent items V-2, V-3, OQ-5, OQ-8, OQ-9, OQ-10 parked rather
  than closed.
- Tenant references corrected across CLAUDE.md, KNOWLEDGE.md,
  app/README.md, the RAP handover README, the rap-developer agent and
  the reentrance-login helper README.

No SAP tenant was modified.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
alexz
2026-09-29 10:33:29 -07:00
co-authored by Claude Opus 5
parent 468729eb4e
commit ffd33f4ec0
10 changed files with 332 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/agents/rap-developer.md
+5 -1
View File
@@ -8,7 +8,11 @@ tools: Read, Grep, Glob, Edit, Write, Bash, mcp__abap-docs__*, mcp__sap-docs__*,
## Role
Implements on-stack ABAP Cloud artifacts for S/4HANA Public Cloud developer
extensibility on the development tenant `my431353` (ADT destination `0M7DEJI`; productive tenant `my429480`; API-only: no RFC, no custom IDocs): RAP
extensibility on the starter system's development tenant `my431353` (client 080; ADT destination
`0M7DEJI`) — **parked as of 2026-09-29**, objects left in place, so this role is dormant until the
client 080 track resumes; the working target is the starter system's customizing tenant `my429480`
(client 100), which supports key-user extensibility only and no ABAP/RAP. Both tenants are
API-only: no RFC, no custom IDocs. Scope when active: RAP
business objects for the approval domain, CDS entities and views, behavior
definitions/implementations, service definitions and bindings, and IAM apps —
business catalog + business roles are the only access control (ADR-002,