Skip to Content
0
May 30, 2018 at 06:33 PM

Testing Web Service of RFC /POSDW/CREATE_TRANSACTIONS_EXT from Soap UI

1249 Views Last edit May 30, 2018 at 06:37 PM 2 rev

Hi,

We are working on POSDM setup to receive TLog data from middle-ware system which would send the data to POSDM using the Web Service we created for standard RFC FM '/POSDW/CREATE_TRANSACTIONS_EXT'. On POSDM side, the service definition creation and SOAMANAGER configuration steps have been done. Now we are trying to test the WSDL using SOAP UI.

While doing so, we are getting response as "UNCAUGHT_EXCEPTION". Checking in ST22, we found that exception "CX_SOAP_SEQ_SCD_ERROR" has occured as the system is not able to find an RFC destination per following code:

Class: CL_SOAP_QUEUE_BGRFC, Method: SUBMIT_TO_QUEUE

lv_dest_name = cl_soap_rt_config=>get_rt_config( )->get_inbound_dest( ).
if lv_dest_name is initial.
" if lv_dest_name is intial the WS setup is missing.
" Please run report lv_dest_name = cl_soap_rt_config=>get_rt_config( )->get_inbound_dest( ). if lv_dest_name is initial. " if lv_dest_name is intial the WS setup is missing. " Please run report SRT_ADMIN. For further details see note 1043195 raise exception type cx_soap_seq_scd_error exporting textid = cx_soap_seq_scd_error=>seq_scd_enviro_not_found. endif.SRT_ADMIN. For further details see note 1043195
raise exception type cx_soap_seq_scd_error
exporting
textid = cx_soap_seq_scd_error=>seq_scd_enviro_not_found.
endif.

The SAP note mentioned in the code comment is not applicable as we already are in the higher release version of SAP BASIS 7.40 SP 15. Hence not sure what's the issue is. We have also reached out to Basis to run SRT_ADMIN to setup any missing runtime configuration, but they confirmed all required configurations are present.

Has anyone come across similar issue? Please let me know if I am missing something in WSDL generation or SOAP UI settings.

Additional Info: WSDL is generated with SSL protocol.

While testing from SOAP UI, I have enabled WS-A addressing option with Generate Message ID option without which we were getting error "SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided" in SRT_UTIL

Thanks,

Rajarajan