Handling Deletion Scenarios at Item Level in SAP ASAPIO Outbound Integration to Solace AEM

[farihakazi]

Handling Deletion Scenarios at Item Level in SAP ASAPIO Outbound Integration to Solace AEM

In complex SAP integration scenarios, managing item-level deletions effectively is essential for maintaining data accuracy across connected systems. This blog explores how ASAPIO’s Outbound Integration framework can be configured to detect, process, and publish deletion events at the item level toward Solace AEM (Advanced Event Mesh). We’ll use the Change Document–based event model (CDHDR/CDPOS) and review how to ensure deleted line items are correctly represented in outbound payloads.

Understanding ASAPIO Outbound Messaging

ASAPIO’s Outbound Messaging framework integrates tightly with SAP’s Business Object and Change Document architecture. When a data change occurs, ASAPIO listens to the event (e.g., through SWEC or SWE2 linkage), captures it as a change pointer, and transforms it into an outbound message—usually in JSON format—to external systems such as Solace AEM.

The Challenge: Deletion at Item Level

Deletion events at the item level can be tricky because SAP’s Change Document entries often represent deleted items with blank item numbers. Without proper filtering and mapping, this can result in incomplete or missing data in the outbound message. To address this, we configure the SWEC event linkage and apply field restrictions to correctly trigger deletion events.

Configuration Steps

1. **SWEC – Events for Change Documents**
      - Define the Change Document Object relevant to the business object (e.g., Sales Order, Purchase Order).In this case, we are using custom BO for opportunity and for item level we have created two events Edit and Deleted . We are interested in the deletion scenario here.

   - Apply a field restriction on the *Item Number* field, which will be blank upon deletion. We have also added Item type to limit the number of events raised only for a particular type.

Change Document History in Tcode CRMD_ORDER 

1. **Event Linkage (SWE2)**
      - Create an event linkage between the Business Object and the outbound configuration.
      - Receiver Function Module: `/ASADEV/ACI_EVENTS_TRIGGER`
      - Activate the linkage to ensure deletion events are captured.

1. **Outbound Object Configuration**
      - Transaction: `/ASADEV/68000202`
      - Define Extraction FM: `/ASADEV/ACI_GEN_PDVIEW_EXTRACT`
      - Message Type: Custom message type created in WE81/BD50.

The ASAPIO payload designer adds value by allowing configuration-based access to design query. Below is an example payload designed for this opportunity object, the item level tables have outer joins to enable payload preview as inner join would yield no data after deleting the item level table.

1. **Header Attributes**
      - Configure endpoint-specific attributes:
        - `SOLACE_TOPIC`: Name of the Solace AEM topic.
        - `ACI_CP_INFO`: X (to include change pointer metadata)                                                                                                                          - `CLOUD_EVENTS` attributes to indicate type of object changed

1. **Field Mapping and Formatter Sequence**
      - If you are using dynamic topics , you can design a uniform topic convention and apply to the Replication Object.
      - Use formatter sequence to add multiple formatters. We are conforming to the cloud events schema for interoperability using FM /ASADEV/ACI_CLOUDEVENT_FM 

Before and After:

When we trigger the deletion of the product which is at item level the change indicator shows up as ‘D’

The payload is restricted to show only the GUID and other details are absent despite data being present in the header level table. (CRMD_ORDERADM_H)

In order to enable details of the opportunity we update table /ASADEV/ACI_CP_I using SM30

After this setting, the change indicator turns into U

And the payload now shows up correctly.

Event-driven architecture