on 07-07-2009 12:54 PM
Hi,
I generated a class on my SAP ECC 6.0 system (via transaction SPROXY) based on my SAP PI 7.1 outbound synchronous service interface.
I've read a lot of blogs here and they all state that EXECUTE_SYNCHRONOUS must be used when calling the method via an ABAP report.
But when I check my generated class, the only method I see is my Service Interface name.
Please advice.
Thanks a lot
Dimitri
There is no EXECUTE_ASYNCHRONOUS function in ERP 6.0. The function name is same as the Message Interface name. Use that.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kindly check this Guide [https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/e03dde13-29dc-2b10-e5a4-9a52caea06af&overridelayout=true]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I will use the Service interface instead of the execute_synchronous.
Then, I checked the document "Consumer and Provider ABAP Proxy Service to Multiple
SAP NW PI Systems using Process Integration 7.1"...
I start the SOAMANAGER and look for my consumer proxy. Found it...
I go to the configuration tab to create a logical port.
The name, I take SAP<XI SID> (in my case SAPSXD).
I take the WSDL based configuration, via HTTP access.
Then I check the WSDL URL in the Sender Agreement and copy-paste it to SOAMANAGER.
I get this error:
Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL.
What's wrong?
Thanks a lot
Dimitri
Hi Ravi,
When I check transaction SPROXY on the back-end system, I see a green light for my service interface.
The only thing I see is that the "state" is set to "not released".
When I double-click on the proxy name, I see status implemented/active for the class.
On the properties tab, I see the following:
instantiation: public
final: blank, not ticked
released internally: blank, not ticked
Shared Memory-Enabled: blank, not ticked
Then I start the SOAMANAGER transaction from the back-end system.
I create a nex logical port.
URL for WSDL access (got from Sender Agreement): http://scxxidci.securex.erp:50000/dir/wsdl?p=1_a64303ebbecf3c4c81a86337a7853c3e_portTypeBindingServi...
When I apply the changes --> same error.
What about the logical port name? Can it be chosen freely?
Thanks
Dimitri
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.