on 2011 Sep 27 12:06 PM
Hi everybody,
I am facing a problem I am a little overstrained with. I made a web service for read only access of sales order data. After some struggle with the authorization, I now get a SOAP error message as response.
<CX_SOAP_CORE>
<E_LOCATION>
<CLASS>CL_SRT_WSP_RT_CONFIG</CLASS>
<METHOD>DETERMINE_OPERATION_NAME</METHOD>
<ID>1</ID>
</E_LOCATION>
<E_TEXT><no error message available>: ("Message "SalesOrderViewNameReadByIDQuery_sync{http://sap.com/xi/SAPGlobal20/Global}" nicht unterstützt (Interface: "ZZBY002657_SALESORDER" Binding-Schl.: "0000000000011EE0B69046BD753F85D3")")</E_TEXT>
<E_ID>1033</E_ID>
<E_FAULT_LOCATION>1</E_FAULT_LOCATION>
<E_AREA>OTHERS</E_AREA>
<E_HOST>0</E_HOST>
<E_PROCESS_CONTROL></E_PROCESS_CONTROL>
</CX_SOAP_CORE>
I am not sure if the sales order Interface in general is not supported yet or just a missing query. I built the web service via wizard so in my opinion I donu2019t have to create a special query. Well, I hope so.
If somebody can figure out the reason of the error. Please inform me.
Best Regards
Jochen
Hi Jochen,
I think you should open an incident for that error cause if you generated the webservice class from a WSDL file, all operations of the webservice class should work.
As workaround, can you use an alternative query operation of the webservice or do you need exactly this query?
Regards,
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have a fundamental question. I am not sure, may be I made a mistake while creating the service. I built a READ service, is this the right type?
I am not sure why I get a QUERY error on a READ request. Sure there must be some kind of query behind the scenes but may be this is the reason?
Best regards,
Jochen
Edited by: JochenS on Oct 4, 2011 12:32 PM
Hi,
so here is a part of my WSDL:
Link: [https://gist.github.com/ea93c556a769639faaa9]
And the request:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
<soap:Header/>
<soap:Body>
<glob:SalesOrderViewNameReadByIDQuery_sync>
<SalesOrder>
<ID schemeID="?" schemeAgencyID="?" schemeAgencySchemeAgencyID="?">1101</ID>
</SalesOrder>
</glob:SalesOrderViewNameReadByIDQuery_sync>
</soap:Body>
</soap:Envelope>
Thanks a lot. Best regards,
Jochen
Edited by: JochenS on Oct 5, 2011 12:56 PM
Hi,
I would try to recreate the webservice or create another view cause the error message sounds like a problem by creating the webservice, not a runtime problem.
I have currently a general problem with webservices in my development system so I can`t test it but I will if it is fixed.
Regards,
Andreas
I got the same problem, even after creating the service again, I get the same error message - on a different function....
Anyone understands the root of the problem? I've been trying several service solutions (You all know, the whole check / activate/ delete and recreate methods) but none have worked.
Hi,
sorry that I don`t see that before but you should try the following request without the attributes in ID tag:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
<soap:Header/>
<soap:Body>
<glob:SalesOrderViewNameReadByIDQuery_sync>
<SalesOrder>
<ID>1101</ID>
</SalesOrder>
</glob:SalesOrderViewNameReadByIDQuery_sync>
</soap:Body>
</soap:Envelope>
Additional I tested a simple sales order webservice (only with ID) in my FP3.0 development tenant and it works. Have you created a "Webservice Authorization" and have assigned the view to a workcenter?
Best regards,
Andreas
I've been able to load Sales Order information with this call:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
<soap:Header/>
<soap:Body>
<glob:SalesOrderByIDQuery_sync>
<SalesOrder>
<ID>12345</ID>
</SalesOrder>
</glob:SalesOrderByIDQuery_sync>
</soap:Body>
</soap:Envelope>
against the ManageSalesOrderIn2 wsdl.
Hope this helps -
User | Count |
---|---|
105 | |
8 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.