rap-business-events
Skill0 starsChanged 3 months agoMITView on GitHub
Eventing empresarial con RAP: publicar eventos de negocio desde el objeto RAP y consumirlos vía SAP Event Mesh. Úsala cuando el usuario implemente eventos RAP, integración event-driven, o publique/consuma business events.
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
- abap-cloudSkill
- abapgitSkill
- abap-sql-amdpSkill
- abap-unit-testingSkill
- atc-cloudificationSkill
- authorization-iamSkill
- cds-view-entitiesSkill
- clean-abapSkill
- odataSkill
- rapSkill
- released-abap-classesSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 86
No uses eventos para lógica que exige respuesta inmediata: el eventing es asíncrono y desacoplado por diseño.
- Distinctive: line 88
No confundas business events con side effects: los side effects refrescan la UI local.
“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
RAP Business Events
Guía para publicar eventos de negocio desde un objeto RAP y consumirlos de forma desacoplada (SAP Event Mesh, Advanced Event Mesh), habilitando integración event-driven sobre el modelo transaccional RAP.
Cuándo y cómo usarla
- Identifica el objetivo: emitir un evento cuando cambia el estado de un BO (por ejemplo "viaje confirmado") o consumir un evento externo.
- Sitúa el contexto: los eventos se declaran en el behavior definition, se emiten desde el behavior pool con EML y se enrutan hacia el broker mediante los bindings de eventos del sistema.
- Aplica el patrón: declara el evento en el BDEF, dispara el
RAISE ENTITY EVENTen una determinación o acción, y define el payload como una entidad abstracta.
Declarar el evento en el behavior definition
El evento forma parte del contrato del BO. Se declara en el BDEF y, si lleva datos, se asocia a una entidad abstracta que describe el payload.
managed implementation in class zbp_r_travel unique;
strict ( 2 );
define behavior for ZR_Travel alias Travel
persistent table ztravel
lock master
authorization master ( instance )
{
create;
update;
delete;
// evento de negocio con payload
event TravelConfirmed parameter ZD_TravelConfirmedParam;
determination raiseConfirmedEvent on modify { field OverallStatus; }
}El payload se modela como entidad abstracta, igual que los parámetros de acción:
@EndUserText.label: 'Travel Confirmed Event Payload'
define abstract entity ZD_TravelConfirmedParam
{
TravelId : /dmo/travel_id;
CustomerId : /dmo/customer_id;
TotalPrice : /dmo/total_price;
ConfirmedAt : timestampl;
}Emitir el evento desde el behavior pool
El disparo se hace con EML (RAISE ENTITY EVENT), normalmente dentro de una determinación que reacciona al cambio de estado.
METHOD raiseConfirmedEvent.
READ ENTITIES OF ZR_Travel IN LOCAL MODE
ENTITY Travel
ALL FIELDS WITH CORRESPONDING #( keys )
RESULT DATA(travels).
LOOP AT travels INTO DATA(travel) WHERE OverallStatus = 'A'.
RAISE ENTITY EVENT ZR_Travel~TravelConfirmed
FROM VALUE #( ( %key = travel-%key
%param = VALUE #( TravelId = travel-TravelId
CustomerId = travel-CustomerId
TotalPrice = travel-TotalPrice
ConfirmedAt = utclong_current( ) ) ) ).
ENDLOOP.
ENDMETHOD.Al ejecutarse dentro del contexto transaccional RAP, el evento se emite solo cuando la transacción se confirma (fase de save), garantizando coherencia con el dato persistido.
Enrutar y consumir
- Publicación externa: en el sistema se define el binding del evento hacia el canal de mensajería (Event Mesh/AEM). El evento sale como mensaje CloudEvents hacia el topic configurado.
- Consumo: un suscriptor (otro sistema, una app en BTP, una iFlow de Integration Suite) recibe el mensaje del topic y reacciona. El productor no conoce al consumidor: acoplamiento mínimo.
- Consumo dentro del stack ABAP: también puedes consumir eventos con un handler ABAP suscrito al evento local.
Buenas prácticas y errores comunes
- Emite el evento en una determinación
on save/on modify, no en una acción síncrona, para que solo salga si el guardado tiene éxito. - Mantén el payload mínimo y estable: envía identificadores y los pocos campos que el consumidor necesita, no la entidad entera.
- No uses eventos para lógica que exige respuesta inmediata: el eventing es asíncrono y desacoplado por diseño.
- Versiona el contrato del evento (nombre y payload) con cuidado: cambiarlo rompe a los suscriptores existentes.
- No confundas business events con side effects: los side effects refrescan la UI local; los eventos integran sistemas.
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.

