SAP Event Mesh vs Advanced Event Mesh: Topics, Queues, Event Contracts and Testing Asynchronous Flows

Keep this: job aid

Event integration checklist

• Broker per use case: Event Mesh capability for SAP events to BTP with small payloads; advanced event mesh for regions, edge, replay, partitioned ordering, large messages.
• Verify limits on SAP Help for your plan (Event Mesh: 1 MB per message); coexistence of brokers needs an end date.
• Topics: cmc/{domain}/{object}/{event}/{version}/{companyCode}/{key}; * = one level, > = one or more levels at the end.
• Queues: one per consumer app; explicit access type, max redelivery, own DMQ with alert, TTL = dedup window, quota for outages.
• Contracts: CloudEvents envelope, AsyncAPI + JSON Schema, owner and consumers in a catalog (Event Portal where available).
• Breaking = rename, remove, type or meaning change, timing change → new version, dual publish, retire after last consumer.
• S/4HANA: channel in /IWXBE/CONFIG, outbound binding in /IWXBE/OUTBOUND_CFG; custom RAP events need event and outbound bindings.
• Stages: CMD→dev broker, CMQ 100→test, CMP→prod; after every copy repoint channels and run the wrong-stage test.
• Tests: positive and negative routing, DMQ, backlog, ordering per key, replay rehearsal with reference count, TTL.
• Monitor: depth, oldest-message age, DMQ depth, publish failures in S/4HANA, and silence.