SAP PO Soap to Soap scenario with multiple operations (sync and async)

I don’t know but I was thinking, why in SAP make a simple web service it’s awful task?

In other technologies (Java for example) you can publish one service with multiple operations with synchronous and asynchronous communication, but do this in SAP PO it’s very tricky.

I don’t write how to develop the scenario, instead, I prefer to talk about “that dirty tricks” to achieve this.

For example, you develop a service interface with multiple operations to expose some functionality via Advanced Adapter Engine, I use soap sender adapter for the outbound system (legacy system) and soap receiver for the inbound system (SAP), I’m working on SAP PO 7.5 (in older versions too).

2018-04-05 10_21_52-Enterprise Services Builder (vhephxidci_XID_00)2018-04-05 10_22_38-Enterprise Services Builder (vhephxidci_XID_00) Seguir leyendo


SAP PI Naming Convention

When I start on PI development I feeling very confused by the naming convention of their components, a couple years ago I was thinking if it is a best naming convention but I don’t found anything about it.

Talking to other consultants of PI/PO they are agree this naming is a responsibility of the organization standards, but in some times it’s not the best.

For example, when you implement a Java proxy if you naming convention it’s not clear the java code is very awful and I don’t like that. In the organization when I work this is very common mistake, because every release of new service interface has problems with the other develoment teams to integrate your systems, only by the naming convetion is too large or dificult to read.

I’ve been developing services interfaces around of five years and recently I found (in my opinion) the best naming convention for SAP PI/PO in this website.

The document is like a cheetshet and it’s very clear to read, definitely I recommend this.

If you has problems to access I leave a copy of the document here


SAP PO get SOAP xml payload

Frecuently I need to check xml payload on SOAP service interfaces but the PO it’s configured to not persist this messages.

In old versions of PI (like 7.10) you can use the TraceHTTP parameter in  sender or receiver adapter, in the module, this paramenter write the xml payload in the message log, according to next values:

  • headers: Only HTTP headers are traced for request and response
  • plain: the whole HTTP request and response are traced (including headers and body)
  • hex: A hex dump is traced for whole HTTP request and response

Seguir leyendo

SAP PO mapping Sync SOAP to JDBC

Well, this time I would like to share this tip to create a service interface to retrieve data from Database with SAP PO/PI.

When you develop the message types to get SQL data you must to check the names and the structure of the Data Types, for example, this is a simple structure to do this query:


For the request sender message type you can write your own structure with any label names:

2018-03-07 11_00_30-MM_ConsultarPedidos_ECC_to_DLX_req_ Display Message Mapping Seguir leyendo

SAP PO AEX Standar users

SAP PO user list in standar AEX Installation with default roles.

Dialog Users

Dialog users represent human users (as opposed to service users), who log on through the various user interfaces of the different components of SAP NetWeaver PI, such as, the Enterprise Services Repository, Integration Directory, and System Landscape Directory.

The following dialog user is available:


Assigned UME Roles
















Access to all components of SAP NetWeaver

Seguir leyendo

SAP PI/PO Enable Web Service Compression

Many people don’t know the web services has a feature to compress the information for request and response to exchange data between client and server.

The advantages of using this feature are that you can send high volume information in web services without reducing the performance, for example, you can send an XML payload of size 40 MB compressed in some 800 kb.

To enable this you need to add some headers in your web service consumer client. In case to PI/PO the equivalent is adding these parameters in SOAP module adapter configuration:Screenshot_20170814_174631 Like this:


But you need check which direction of the communication channel is configured, in the previous SAP PI documentation describe the configuration:

The receiver SOAP adapter uses these parameters for the request message; the sender
SOAP adapter uses these parameters for the response message.

If you’re using a Java client with axis you could enable this feature adding this lines into your Out Binding Stub class:

org.apache.axis.client.Call _call = createCall();
// other conf props...
_call.setProperty(HTTPConstants.MC_ACCEPT_GZIP, Boolean.TRUE);
_call.setProperty(HTTPConstants.MC_GZIP_REQUEST, Boolean.TRUE);

This is imperceptible for PI/PO because into the PIMON you can see the message size as normal size, you can check the web service consumer to validate if the request is compressed or not.


SAP PO 7.5 enable sync acknoledgement in async communication channel receiver

Recentrly I had been a SAP  PI 7.1 system to SAP PO 7.5 and some scnearios I had troubles with the acknowldege reponse from other SAP systems.

The problem is with a SOAP XI receiver communitation channel when the message is sended to sap system receiver, I don’t know because the receiver system send to PO a aknowledge with empty content (XML), and this raise a exception in PO.

To fix that I need to add this parameters into adapter module > Tab Module > Module Configuration

Module Key Parameter Name  Parameter   Value
soap        XMBWS.GenerateSysAck        true
soap        MBWS.NoSOAPIgnoreStatusCode true
soap        GenerateSysAck          true
soap        ignoreDuplicate         true

Maybe the parameters sounds to do other actions, but when you set the value ‘true‘the akcnowldege is ignored in PO and the process complete succesfully.