Docs / Outbound Messaging
CloudEvents Format
The ASAPIO Integration Add-on supports CloudEvents-compatible outbound payloads. This feature is available since release 9.32310.
Overview
CloudEvents provides a standard event envelope so downstream consumers can process events consistently across brokers and platforms. ASAPIO applies this envelope in the outbound formatter sequence.
Via SAP GUI
In the outbound object configuration, go to Formatter Sequence and add the two formatter entries in this order:
| Sequence | Function Module | Purpose |
|---|---|---|
| 1 | /ASADEV/ACI_GEN_VIEW_FORM_CB | Generates the base JSON payload |
| 2 | /ASADEV/ACI_CLOUDEVENT_FM | Wraps payload using the CloudEvents envelope |
The formatter type is derived automatically by customizing once the sequence entries are saved.
Optional Additional Attributes
If you need to adjust CloudEvents type composition, maintain these optional header attributes in the outbound object:
| Header Attribute | Description |
|---|---|
CLOUDEVENTS_OBJECT_NAME | Logical object name used in CloudEvents type |
CLOUDEVENTS_OPERATION | Operation/event action segment used in CloudEvents type |
CLOUDEVENTS_VERSION | Version segment used in CloudEvents type |
Via Event Studio
Event Studio deploys interfaces using the same backend formatter pipeline. Configure the target interface and connector in Event Studio, then maintain the same CloudEvents-related header attributes in the interface deployment settings when needed.
Use Event Studio for lifecycle and deployment convenience; use SAP GUI when you need direct low-level control over formatter sequence details.