Asynchronous (fire-and-forget) processing in SAP Cloud Integration is achieved by selecting the One-Way message exchange pattern. Within One-Way, the “WS Standard” process setting sends the message without waiting for any synchronous acknowledgement or fault, thereby fulfilling the definition of an asynchronous call. The “Robust” variant, in contrast, still blocks the HTTP connection until the integration flow finishes and can return a SOAP Fault, which is not purely asynchronous.

A. Request-Reply always keeps the HTTP connection open until a response is returned; thus it is synchronous.

B. Same as A; Request-Reply (even with WS Standard) waits for a response, so not asynchronous.

C. One-Way Robust still waits for success/fault feedback before the sender connection is released; therefore not fully asynchronous.

1. SAP Help Portal – SAP Cloud Integration

“SOAP Adapter Configuration

” section “Message Exchange Pattern – One-Way (WS Standard) for Asynchronous Processing

” version 2024 Q2

pp. 5-6.

2. SAP Help Portal – SAP Cloud Integration

Developer Guide

“Robust One-Way Pattern

” paragraph 2 (“connection kept open until fault handling”)

version 2024-04

p. 7.

3. SAP NetWeaver Process Integration 7.5 – Adapter Engine Guide

chap. 8.3.2 “Robust vs. Standard One-Way

” pp. 156-157.

4. W3C Recommendation

“WS-Addressing Core

” section 3.2

describing response requirement in Request-Reply patterns (supporting why A & B are synchronous).