Middleware communication

The communication of this solution is asynchronous, i.e. we will have to configure 3 Service Consumers for our sending to the TCI and 3 Service Definitions to deal with the TCI response.

These are the three Service Consumers that we have to configure:

• /EDGE/CO_EIHU_FURECEPCION_FACT
• /EDGE/CO_EIHU_FUSE_QINRECEPCIO
• /EDGE/CO_EIHU_FUSERECEPCION_AN

We will have to create a logical port for each Service Consumer.

Example of /EDGE/CO_EIHU_FURECEPCION_FACT :

T-code SOAMANAGER.

Select Web Service Configuration (in other SAP versions it may be called Web Service Administration).

Select the corresponding Service Consumer:

Select the Consumer Proxy:

We will create the corresponding logical port:

The name of the logical port is indifferent but we recommend that in order to distinguish the three Service Consumer ports, they should be named as follows:

• /EDGE/CO_EIHU_FURECEPCION_FACT → MANAGE_INVOICE

• /EDGE/CO_EIHU_FUSE_QINRECEPCIO → QUERY_INVOICE

• /EDGE/CO_EIHU_FUSERECEPCION_AN  → ANNUL_INVOICE

The logical port must always be checked by default, otherwise the Service Consumer will not work.

Para eso seleccionar el siguiente botón:

Finally it has to be marked like this (in other SAP versions this setting may be somewhere else).

The configuration of the logical port has to be as follows:

The user and password is provided by the TCI communications equipment.

The Messaging configuration has to look like this:

Finally Transport Settings should be configured as follows, the URL will be provided by the TCI communications team.

This configuration will be similar for the other two Service Consumers, except for the URL provided by the TCI communications team.

We will also have to configure the three Service Definitions:

• /EDGE/SP_EI_HU_WS_INVOICE_RESP

• /EDGE/SP_EI_HU_WS_QUERY_RESP

• /EDGE/SP_EI_HU_WS_ANNUL_RESP

To configure the Service Definitions, go to the same tab as the Service Consumer tab and click the following button (this may be different in other SAP versions):

This is the only configuration needed for each of the three Service Definitions to be configured:

In order for the communications equipment to communicate with our ERP system, SAP must provide it with a user with certain permissions, these permissions are as follows:

• Rol → SAP_XI_APPL_SERV_USER

• Rol Z created by us which has the authorisation object S_SERVICE with the permissions of the three Service Definitions.

To do this second role correctly, the following function module must be executed:

AUTH_TRACE_WRITE_USOBHASH

Example for /EDGE/SP_EI_HU_WS_INVOICE_RESP:

It will have to be executed once for each Service Definition , SERVICE_TYPE will always be WS while SERVICE will have the following values according to the Service Definition:

• /EDGE/SP_EI_HU_WS_INVOICE_RESP//EDGE/FM_EI_HU_WS_INVOICE_RESP

• /EDGE/SP_EI_HU_WS_QUERY_RESP//EDGE/FM_EI_HU_WS_QUERY_RESP

• /EDGE/SP_EI_HU_WS_ANNUL_RESP//EDGE/FM_EI_HU_WS_ANNUL_RESP

The Z role, similar to this one, will have to be created:

This Role called ZROL_RFC has the authorisation object S_SERVICE , which has been manually added with the three Service Definitions:

Once the user has been configured with these two roles (in our case the user FUSEKOBAK), we will provide it to the TCI communications team so that they can communicate with our ERP.