Docs / Outbound Messaging

IDoc Messaging

IDoc messaging enables reliable SAP-to-SAP and SAP-to-any integration by converting IDoc payloads to JSON and vice versa.

Overview

Outbound: SAP IDoc to JSON message
Inbound: JSON message to SAP IDoc

Send IDocs as Outbound JSON Message (SAP GUI)

Create Logical System

Transaction SALE -> Basic Settings -> Define Logical System. Use logical system LOCAL for local routing scenarios.

Create Customer Distribution Model

Transaction BD64: maintain sender, recipient, and message type mapping.

Create IDoc Port

Transaction WE21: create ABAP-PI port and set FM /ASADEV/ACI_IDOC_PORT_TRIGGER.

Create Partner Profile

Transaction WE20: partner type LS, partner number LOCAL, outbound parameter with message type/basic type/port.

Create Outbound Object

In /ASADEV/ACI_SETTINGS maintain outbound object with:

Extraction Func. Module: /ASADEV/ACI_GEN_VIEW_EXTRACTOR
Extraction View Name: EDID4
Formatting Function: /ASADEV/ACI_GEN_IDOC_FORMATTER

Set Up Event Linkage

Linkage uses BOR object /ASADEV/ID and event ACI_TRIGGER_EVENT with receiver FM /ASADEV/ACI_EVENTS_TRIGGER.

Header Attributes (Outbound)

General

Header Attribute	Value
`BOR_ATTRIBUTE_MessageType`	IDoc message type (for example MATMAS)
`ACI_IDOC_DIRECT_COMMIT`	X (optional direct commit behavior)

Azure

AZURE_TOPIC

Confluent/Kafka

KAFKA_TOPIC

Solace

SOLACE_TOPIC, SOLACE_CALL_METHOD, SOLACE_CONT_TYPE, SOLACE_DELIV_MODE

SAP Event Mesh

SAP_EM_TOPIC, SAP_EM_CALL_METHOD, SAP_EM_CONT_TYPE, SAP_EM_QOS

Test Outbound

Use transaction BD10 (material distribution example) and inspect results in /ASADEV/ACI_MONITOR.

Receive IDocs from Inbound JSON Message (SAP GUI)

Create Partner Profile

In WE20 maintain inbound parameters and process code for the inbound message type.

Create Inbound Object

In /ASADEV/ACI_SETTINGS create inbound object with extraction FM /ASADEV/ACI_JSON_TO_IDOC.

Header Attributes (Inbound)

Azure

AZURE_QUEUE_NAME, AZURE_PULL_DURATION, AZURE_PULL_WAIT

Confluent/Kafka

KAFKA_DOWNLOAD_ACCEPT, KAFKA_DOWNLOAD_TOPIC, KAFKA_GROUPNAME, KAFKA_INSTANCE_NAME, KAFKA_MAX_BYTES, KAFKA_TIMEOUT

JSON Schema for IDoc Creation

Use transaction WE60 -> Basic Type -> More -> Documentation -> XML Schema to get field-level IDoc schema. Ensure mandatory EDI control fields are mapped in inbound JSON.

Test Inbound

PUSH-Based

Activate SICF node and POST to:

https://<saphost>:<port>/asadev/<Instance>/<Object>

PULL-Based

Use transaction /n/ASADEV/ACI to trigger connector-side download and inbound conversion.

Event Studio

Event Studio can document and govern interface-level deployment, but IDoc foundation and low-level process code/partner profile setup remain SAP GUI-centered.