IDoc with Integration Suite, Advanced Event Mesh using the Event Add-On

In modern SAP landscapes, Intermediate Documents (IDocs) remain a foundational pillar for reliable, standardized data exchange—both within SAP systems and between SAP and external systems. The Event Add-on extends this proven SAP mechanism into today’s heterogeneous and event-driven integration architectures by enabling bidirectional IDoc messaging that is code-less, real-time, and flexible. With the Add-On, standard and custom SAP IDocs can not only be processed in their native format but also converted on-the-fly to JSON for seamless delivery to cloud platforms, messaging brokers, or event-driven consumers, and vice versa. This empowers organizations to leverage established SAP interfaces while bridging to modern integration patterns without heavy custom development.

Please also check out the technology comparison in our central blog.

Create Logical System

• Transaction: SALE
• Select the created Connection
• Go to section Basic Settings → Define Logical System
• Add New Entry and specify:
  • Log.System: Name has to be “LOCAL”
  • Name: choose a description

Create Customer Distribution Model

• Transaction: BD64
• Create Model View and specify:
  • Sender: Sending client
  • Recipients: Logical system (LOCAL)
  • Add message type as required (e.g., MATMAS)

Create IDoc Port

• Transaction: WE21
• Select the created Connection
• Go to section ABAP-PI
• Add New Entry and specify:
  • Port: choose a name (e.g., ACI_IDOC)
  • Description: choose a description
  • Function module: /ASADEV/ACI_IDOC_PORT_TRIGGER

Create Partner profiles

Note:

Make sure a Distribution model is available (Transaction BD64)

• Transaction: WE20
• Open folder: Partner Type LS
• Go to section Outbound Options.
  • Receiver port: ACI_IDOC
  • Basic Type: MATMAS07

Create Outbound Object

Note:

In the example below, we want to trigger an outbound message for SAP material master IDocs (IDoc name “MATMAS”), convert the IDoc payload to JSON and send it to an event broker instance.

• Transaction: SPRO
• Goto ASAPIO Cloud Integrator → Connection and Replication Object Customizing
• Or go directly to transaction: /ASADEV/68000202
• Select the created Connection
• Go to section Outbound Objects
• Add New Entry and specify:
  • Object: name of the outbound configuration
  • Extraction Func. Module: /ASADEV/ACI_GEN_VIEW_EXTRACTOR
  • Message Type: Specific message type (Example: Z_SAP_EM_MATMAS)
  • Load Type: Incremental Load
  • Trace: activate for testing purposes
  • Extraction view name: EDID4
• Formatting Function: /ASADEV/ACI_GEN_IDOC_FORMATTER

Set up ‘Event Linkage’

Link the configuration of the outbound object to a Business Object event:

• Navigate to Outbound Objects → Event Linkage or use transaction SWE2.
• Add New Entry and specify:
  • Object Category: BO BOR Object Type
  • Object Type: /ASADEV/ID
  • Event: ACI_TRIGGER_EVENT
  • Receiver Function Module: /ASADEV/ACI_EVENTS_TRIGGER
  • Linkage Activated: tick the checkbox
  • Check Function Module: /ASADEV/ACI_EVENTS_CHECK

Set-up ‘Header Attributes’

Specific for the IDoc Outbound use-case you have to specify the header attributes. For all details check https://asapio.com/docs/idoc/.

Test the outbound IDoc event creation

Start transaction BD10 to test the described formatter

Welcome you IDoc event in SAP AEM using Try-Me.

 In modern SAP landscapes, Intermediate Documents (IDocs) remain a foundational pillar for reliable, standardized data exchange—both within SAP systems and between SAP and external systems. The Event Add-on extends this proven SAP mechanism into today’s heterogeneous and event-driven integration architectures by enabling bidirectional IDoc messaging that is code-less, real-time, and flexible. With the Add-On, standard and custom SAP IDocs can not only be processed in their native format but also converted on-the-fly to JSON for seamless delivery to cloud platforms, messaging brokers, or event-driven consumers, and vice versa. This empowers organizations to leverage established SAP interfaces while bridging to modern integration patterns without heavy custom development.Please also check out the technology comparison in our central blog.Create Logical SystemTransaction: SALESelect the created ConnectionGo to section Basic Settings → Define Logical SystemAdd New Entry and specify:Log.System: Name has to be “LOCAL”Name: choose a descriptionCreate Customer Distribution ModelTransaction: BD64Create Model View and specify:Sender: Sending clientRecipients: Logical system (LOCAL)Add message type as required (e.g., MATMAS)Create IDoc PortTransaction: WE21Select the created ConnectionGo to section ABAP-PIAdd New Entry and specify:Port: choose a name (e.g., ACI_IDOC)Description: choose a descriptionFunction module: /ASADEV/ACI_IDOC_PORT_TRIGGERCreate Partner profilesNote:Make sure a Distribution model is available (Transaction BD64)Transaction: WE20Open folder: Partner Type LSGo to section Outbound Options.Receiver port: ACI_IDOCBasic Type: MATMAS07Create Outbound ObjectNote:In the example below, we want to trigger an outbound message for SAP material master IDocs (IDoc name “MATMAS”), convert the IDoc payload to JSON and send it to an event broker instance.Transaction: SPROGoto ASAPIO Cloud Integrator → Connection and Replication Object CustomizingOr go directly to transaction: /ASADEV/68000202Select the created ConnectionGo to section Outbound ObjectsAdd New Entry and specify:Object: name of the outbound configurationExtraction Func. Module: /ASADEV/ACI_GEN_VIEW_EXTRACTORMessage Type: Specific message type (Example: Z_SAP_EM_MATMAS)Load Type: Incremental LoadTrace: activate for testing purposesExtraction view name: EDID4Formatting Function: /ASADEV/ACI_GEN_IDOC_FORMATTERSet up ‘Event Linkage’Link the configuration of the outbound object to a Business Object event:Navigate to Outbound Objects → Event Linkage or use transaction SWE2.Add New Entry and specify:Object Category: BO BOR Object TypeObject Type: /ASADEV/IDEvent: ACI_TRIGGER_EVENTReceiver Function Module: /ASADEV/ACI_EVENTS_TRIGGERLinkage Activated: tick the checkboxCheck Function Module: /ASADEV/ACI_EVENTS_CHECK Set-up ‘Header Attributes’Specific for the IDoc Outbound use-case you have to specify the header attributes. For all details check https://asapio.com/docs/idoc/.Test the outbound IDoc event creationStart transaction BD10 to test the described formatterWelcome you IDoc event in SAP AEM using Try-Me.Stay tuned and Happy Eventing  Read More Technology Blog Posts by SAP articles 

#SAPCHANNEL