Mapping-Lookup to ABAP-Proxy
Using Mapping-Lookups is a powerful tool to gather data within an integration scenario. But is it possible to perform Mapping-Lookups using ABAP Proxies?
Help content does not provide any information about it, so we gave it a shot. Within a B2B customer order scenario, we want to look up order details out of several SAP ERP clients using ABAP Proxies.
Good news first, it is possible. You can use a SOAP channel with message protocol XI 3.0 (available since PI 7.11), within your java mapping. Details on how to program the java mapping can be found here.
The important part for Proxy-Lookups is these 2 LOC:
// 4. Set the operation name and namespace; optional step, // only necessary if the used adapter needs these parameters. accessor.setOperationName(“myInterfaceName”);
These are needed to call the proxy, otherwise the XI header does not provide the information about the interface and operation to call, which is needed by the local integration engine.
During runtime, ABAP proxy lookup calls, can be identified within the local MONIS (SXMB_MONI) by sender component name “Mapping” and the receiver component name is the name of the system which the integrations calls later on. This is the receiver determined within the routing. Afaik, it is not possible to override these header informations. But imho, it’s nice to know, where the journey is going to, after the Lookup has been performed.