abap-cloud
Skill0 starsChanged 3 months agoMITView on GitHub
Desarrollo en el modelo ABAP Cloud respetando el clean core: released APIs, lista de uso, ABAP SQL restringido y los tres niveles de extensibilidad. Úsala cuando el usuario trabaje en S/4HANA Cloud, ABAP Environment (Steampunk), pregunte por released APIs, usage list, clean core, o qué está permitido en la nube.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- dovoanhtruong/abap-agent-claudecode-workspacetheir own version, first seen Oct 12, 2026
- likweitan/abap-skillstheir own version, first seen Jul 14, 2026
- williamcorrea23/sap-router-skilltheir own version, first seen Jul 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- likweitan/abap-skills★ 72same name
- dovoanhtruong/abap-agent-claudecode-workspace★ 3same name
- williamcorrea23/sap-router-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- abap-cloud-migrationSkill
- abapgitSkill
- abap-sql-amdpSkill
- abap-unit-testingSkill
- atc-cloudificationSkill
- authorization-iamSkill
- cds-view-entitiesSkill
- clean-abapSkill
- odataSkill
- rap-business-eventsSkill
- rapSkill
- released-abap-classesSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 74
C4 Deprecated: no usar.
- Very specific: line 79
No copies una vista I_* estándar a ZI_..._MyVersion para modificarla: pierdes estabilidad de upgrade.
- Very specific: line 80
No fuerces acceso a tabla cruda como atajo: solo es legítimo en tu capa Basic ZP_* propia o sobre tablas Z.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ABAP Cloud / Clean Core
Marco para desarrollar en ABAP Cloud (S/4HANA Cloud, ABAP Environment) sin romper el clean core: solo APIs liberadas, ABAP restringido al lenguaje for Cloud Development y extensiones sobre el modelo de datos virtual (VDM).
Cuándo y cómo usarla
- Identifica el objetivo: crear un objeto nuevo en ABAP Cloud, comprobar si algo está permitido, o decidir el nivel de extensibilidad adecuado.
- Sitúa el contexto: Public Edition (todo es Tier 1 por construcción) o Private Edition/on-stack (donde puede convivir código legacy vía Tier 2).
- Aplica las reglas: consume solo objetos liberados, valida con la variante ATC
ABAP_CLOUD_READINESSoABAP_CLOUD_DEVELOPMENT_DEFAULT, y encapsula lo no liberado en wrappers.
Los tres pilares del clean core
- Released APIs: solo puedes consumir objetos marcados como liberados para Cloud Development (C1). Clases, CDS y tablas no liberadas no compilan en un paquete Cloud.
- ABAP for Cloud Development: versión restringida del lenguaje. Se prohíben sentencias obsoletas o inseguras (acceso a dynpros clásicos,
CALL FUNCTIONa módulos no liberados, SQL nativo, etc.). - Extensibilidad en capas: On-Stack Developer Extensibility, Side-by-Side (BTP) y Key User. Elige el nivel según quién mantiene la extensión y qué acopla.
Consumir el VDM en lugar de tablas
Toda lectura productiva pasa por vistas CDS liberadas I_*, nunca por la tabla estándar directamente.
// SI: consumir vista I_* liberada (clean core)
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Financial Document Items - Z'
define view entity ZI_FINANCIAL_DOC
as select from I_JournalEntryItem
{
key Ledger,
key CompanyCode,
key FiscalYear,
key AccountingDocument,
GLAccount,
AmountInCompanyCodeCurrency,
CompanyCodeCurrency
}Acceder directo a ACDOCA, BSEG, MARA o VBAK desde una CDS Z rompe el contrato de upgrade, pierde las autorizaciones integradas y falla el ATC Cloud.
Modelo Tier 1 / Tier 2 y el patrón wrapper
Cuando necesitas una funcionalidad que solo existe en una API no liberada (por ejemplo un BAPI legacy), en Private Edition la envuelves en un Software Component Tier 2 y la expones a tu código Tier 1 mediante una clase.
" Tier 2 (no cloud): wrapper que aísla la llamada legacy
CLASS zcl_wrapper_bapi DEFINITION PUBLIC.
PUBLIC SECTION.
METHODS create_document
IMPORTING header TYPE zif_doc_header
RETURNING VALUE(result) TYPE zif_doc_result.
ENDCLASS.
CLASS zcl_wrapper_bapi IMPLEMENTATION.
METHOD create_document.
CALL FUNCTION 'BAPI_LEGACY_CREATE' " no liberado, encapsulado aquí
EXPORTING header = header
IMPORTING result = result.
ENDMETHOD.
ENDCLASS.Tu código Tier 1 nunca llama al BAPI directamente: llama al wrapper a través de una factory o interfaz liberada.
Marcado de liberación (release contract)
- C1 Use-In-Cloud-Development: consumible desde Tier 1. Es lo que buscas.
- C2 Use-System-Internally: solo dentro del mismo Software Component.
- C3 Use-In-Key-User-Apps: extensiones Key User.
- C4 Deprecated: no usar.
Buenas prácticas y errores comunes
- Ejecuta ATC con la variante Cloud antes de liberar: es el filtro que decide si tu código es cloud ready.
- No copies una vista
I_*estándar aZI_..._MyVersionpara modificarla: pierdes estabilidad de upgrade. Extiende con CDSextendo joina desde unaZI_*propia. - No fuerces acceso a tabla cruda como atajo: solo es legítimo en tu capa Basic
ZP_*propia o sobre tablas Z. - En Public Edition no existe Tier 2 accesible: si no hay API liberada para tu caso, abre incidente con SAP.
- Comprueba la release state de cada objeto en el SAP API Business Hub (api.sap.com) o filtrando las CDS liberadas en el Project Explorer de ADT.
Referencias
- Cursos y másters SAP de Logali Tech: https://logalitech.com/masters
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

