ITS Service - Connection failure - no ~transaction parameter found

[Former Member]

Hi all!

I've got a problem with our ITS service named ZSRMADDDATA. Unfortunately we have no permission to view the service definition in transaction SICF. It was created by the external service provider of our customer. So, when I'm testing the service in the SICF, I got the following error:

Communication failure, cancellation type IMC_CANCEL_TX.

Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_ITS===============CP

Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

The error code is: ICF-IE-http-c:010-u:TEST_SRM3-l:-s:H11-i:-w:0-d:20080922-t:153228-v:IMC_CANCEL_TX -e:

I created a internet service in SE80 named ZSRMADDDATA. It contains 2 generated HTML templates for our dynpros. The parameters ~CLIENT, ~LANGUAGE, ~LOGIN, ~PASSWORD are initial and ~AUTOSCROLL = 0 and ~TRANSACTION = ZSRMADDDATA.

When debugging the handler (I know that the service is using CL_HTTP_EXT_ITS), the method IF_HTTP_EXTENSION~HANDLE_REQUEST try to obtain the transaction code.

* --------------------------------------------------------------
* CALL TRANSACTION, lookup sequence
* --------------------------------------------------------------
*      1. check if ~transaction is specified in service parameters
*      2. check for ~transaction parameter in url
*      3. If ~transaction is not set and we are in the webgui
*         service use ~okcode as ~transaction
*      4. ask r3 for a user specific start transaction
*      5. default: start easy access menu

The standard handler is calling the system function DYNP_OKCODE_SET with the transaction code SMEN. It is not able the read the ~transaction parameter and is using the default. When calling DYNP_OKCODE_SET, I obtain the previous mentioned error Communication failure.

Does anybody have got a idea?? Why are there no parameters?

Thanks a lot! Greetings, Florian

[Former Member]

Hi!

I have solved my problem. It was quiet easy. The service provider had not configured "GUI Link" and the parameters ~TRANSACTION and ~THEME in the SICF service.