Event-Driven Extensions with SAP Business Events

Keep this: job aid

Event-driven extension checklist

• Check the SAP Business Accelerator Hub for a standard event and its version before building one.
• Publishing needs an active channel and an outbound binding per topic; one broker instance per stage.
• Custom events: RAP business event in the behavior definition, raised in the save sequence, exposed by an event binding.
• Assume at-least-once delivery: deduplicate by source + id in the same transaction as the effect.
• Prefer set-to-state effects and read current state through the API.
• Acknowledge after the effect is stored, never before.
• Assume out-of-order arrival; compare versions or re-read state.
• Retry transient errors only: few attempts, backoff, jitter. Poison messages to a dead message queue with an owner.
• Test with correlation (order number, event id) and eventual assertions tied to a stated time limit.
• Sign off on duplicates, ordering, outages, poison messages and stage pairing, not just the happy path.