Consuming RepositoryFrameworkWS web service in WebDynpro for ABAP

HI All,
I would like to consume the below web service in Web Dynpro ABAP provided by SAP from Web Services Navigator.
RepositoryFrameworkWS
Using this web service I would like to write a file in KM repository. I am new to Web Dynpro ABAP and I am not sure how to use the below methods. The below methods will be shown once we import the Web Service on to SE80.
Please help writing the code for following methods in Web Dynpro ABAP.
CREATE_DOCUMENT
GET_CONTENT_NEXT_CHUNK
GET_CONTENT_FIRST_CHUNK
SET_CONTENT
Thanks
Krish

Hi,
I am able to call the service and create a document in KM . I am providing userid and password in HTTP destination as this service requires basic authentication. Right now I am giving the userid and password in SM59. But I want to pass the userid and password from program itself for logged in user. Please help me with the code for this.
Thanks
SK

Similar Messages

Dynamic destinations for adaptive web service in webdynpro for java

Hi,
Please advice me on how to create dynamic destination for adaptive web service model in webdynpro for java.
Regards,
Patana

Hi,
If this is the case, then use the HTTP destination for this.
What you need to do is:
1. Create one HTTP destination in visual administrator at services-> Destinations. Provide HTTP url of the your web service and the security options.
2. Specify this HTTP destination in the code before executing web service model.
Write following code for that:
wdContext.current<node name>Element().modelobject()._setHTTPDestination(<Specify HTTP destination name>);
Then execute your web service model.
Now, whenever you want to change the server on which your web service is running, make change in the HTTP Destination in visual administrator.
Refer this link,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b2bc0932-0d01-0010-6d8e-cff1b2f22bc7
Regards,
Sunaina Reddy T

Consuming EJB Web Service in WD ABAP component

Hi,
I have a scenario where I have Portal KM access methods exposed as EJB Web Service. This web service is deployed on J2EE engine.
And I have to consume this web service from my WD ABAP component controller.
Any idea how this can be achieved?
Thanks and regards,
Amey

This doesn't really have anything to do with Web Dynpro. Normal ABAP functionality is used for the consumption of a web service. In ABAP we create a proxy class based off the WSDL of the web service. This proxy class can then be called from within Web Dynpro like any other ABAP class. You can read about consuming a web service in the online help:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/9e/c7a3591dc74a679bbc9716354e42af/frameset.htm

ABAP code and konfiguration for consuming secure web services

I need some help/links on how to create an abap program (on 4.6 or WAS 620, or 640 if not possible in older releases) to consume a web service with authentication using certificates based on WS security (<a href="http://www.oasis-open.org/committees/wss">http://www.oasis-open.org/committees/wss</a>) or client certificates. The request must include attachment in DIME or base64 format (preferably DIME).
On 4.6 I have used the FM HTTP_POST with the if_ixml interface to consume web services, but I don't know if it can handle https authentication and attachements.
Message was edited by: Robert

check out this weblog.
<a href="/people/thomas.jung3/blog/2005/05/13/calling-webservices-from-abap-via-https">Calling WebServices from ABAP via HTTPS</a>
Regards
Raja

Error while consuming Web Service (returning XML ) in ABAP

Hi,
i am trying to consume a web service in ABAP. ( webservice which takes a request and return a XML string back).
I created a proxy class in SE80. and i tested it successfully.
When i tried to use the class in my program, it is giving dump.
i am not sure what is the problem. I guess it is not able to handle null values in XML.if that is the case. how to handle it..

The dump says:
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Except.                CX_SY_REF_IS_INITIAL
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught and
    therefore caused a runtime error.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "LO_CLIENTPROXY").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
I think this dump is because of the default value ( space) in some elements. How to avoide that.
wheni catch CX_SY_REF_IS_INITIAL it is not giving any dump. But this is not my requirement. Because it is not getting anything into response string.

Webdynpro for ABAP versus Enterprise Services

Hi,
With ECC 6.0 the WebDynpro for ABAP will be available. After converting my well-known ABAP-dynpro screens to WebDynpro I will have the possibility to expose all R/3 functionality from within the portal.
Two years from now the Enterprise Services will be there. What will be the reason(s) for using enterprise services instead of WebDynpro for abap to make R/3 functionality available in the portal? I think at the end both functionalities can co-exist but what are the criteria to use one or both methods?
Greetings Theo

Theo,
This is not a discussion relegated to the bar...
First the short methodology is correct... Id the processes, expose major entry points as Services, orchestrate, publish Service Desc, endpoints, etc., repeat...
The real question remaining is, if I believe my entire process is incorporated with a single SAP system why would I expose Services (and add the additional layer)?
I agree with the comment where if a process completely executes in a single environment there is no need to change its strategy and force it to be an orchestrated set of Service interactions. That is not inconsistent with providing Service interfaces along the process so that it can be composed into other processes either not yet in place or requiring cross-system interaction. ESA is not saying "break open the container and make every little piece operate as Enterprise Services", instead it guides us to Service enable components so that others can consume them in a standard way, regardless of implementation / execution environment.
As we think about leveraging ESA for the benefit of our businesses (our enterprise and the ecosystem of business partners and customers) we have to acknowledge that we do not and will not know where every step of a busines process will execute throughout time. There may be tremendous value in executing part of a process that could be performed in that same SAP system in a completely different environment. The main benefit of Service enabling is business agility for a reasonable cost. I would argue that at least the main entry and exit points to major processes should have Service interfaces, followed by a more comprehensive assessment of internal process steps - looking for opportunities.
The other side of the equation is determining what additional consumers of the process could be found if major parts of the process exposed Service interfaces. To say, "my process executes inside this one system, so I should not expose it as a set of Services", ignores the potential benefit of other systems being able to incorporate that process in their execution (or parts of a process). As we expose more, well defined Services that represent aspects of enterprise business processes we create an environment where there is low cost, opportunistic integration based on standards.
Or put more briefly, make sure to execute your business process in an efficent computing manner, but do not let that constraint limit your thinking when it comes to Services. They are two different (yet related) issues. Services simply give us another way to leverage an asset we already have. Make the asset available and if it has value to the organization, it will be consumed.
Hope that helps...
David

Consuming a Web Service with PasswordDigest Authentication in ABAP

Hello,
I need to consume a web service in ABAP from a non-SAP application. The web service uses wsse:UsernameToken with PasswordDigest in the SOAP Header for authentication. However, I havent seen any documentation for using Password Digest in ABAP.
Is it possible to use Password Digest in ABAP?
Thanks
Ajay

Hi Marc,
Here is the ABAP Code to build the SOAP header.
FUNCTION Z_GET_SOAP_REQUEST_HEADER.
*"*"Local Interface:
*" EXPORTING
*"     VALUE(ER_SECURITY_ELEMENT) TYPE REF TO IF_IXML_ELEMENT
*date and time data
data: lv_sys_date like sy-datum,
        lv_sys_time like sy-uzeit,
        lv_year(4) type c,
        lv_month(2) type c,
        lv_date(2) type c,
        lv_hour(2) type c,
        lv_min(2) type c,
        lv_sec(2) type c.
data : lv_created type string,
        lv_snonce type string,
        lv_b64nonce type string,
        lv_webservice_password type string,
        lv_webservice_userid type string,
        lv_spassword type string,
        lv_xpassword type xstring,
        lv_hpassword type hash160x,
        lv_b64password(255) type c,
        lv_xpasslen type i,
        lv_hpasslen type i.
*xml declartions
data : lv_sheader type string,
        lv_xheader type xstring,
        xml_document TYPE REF TO if_ixml_document,
        xml_root TYPE REF TO if_ixml_element,
        xml_element TYPE REF TO if_ixml_element,
        xml_node TYPE REF TO if_ixml_node.
*get the c-link password.
CALL METHOD ZCL_CDB_SYNC_CFG_READER=>GET_USERID_PASSWORD
IMPORTING
    EV_USER_ID = lv_webservice_userid
    EV_PASSWORD = lv_webservice_password
*Evaluate created date time
lv_sys_date = sy-datum.
lv_sys_time = sy-uzeit.
lv_year = lv_sys_date(4).
lv_month = lv_sys_date+4(2).
lv_date = lv_sys_date+6(2).
lv_hour = lv_sys_time(2).
lv_min = lv_sys_time+2(2).
lv_sec = lv_sys_time+4(2).
CONCATENATE lv_year '-' lv_month '-' lv_date 'T' lv_hour ':' lv_min ':' lv_sec '.000Z' into lv_created.
*Create and encode the nonce
CALL FUNCTION 'GENERAL_GET_RANDOM_STRING'
    EXPORTING
      NUMBER_CHARS = 24
    IMPORTING
      RANDOM_STRING = lv_snonce.
CALL METHOD cl_http_utility=>ENCODE_BASE64
    EXPORTING
      UNENCODED = lv_snonce
    RECEIVING
      ENCODED   = lv_b64nonce.
*create the password to be sent to web service
CONCATENATE lv_snonce lv_created lv_webservice_password into lv_spassword.
*encode password to xstring
CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
    EXPORTING
      TEXT   = lv_spassword
    IMPORTING
      BUFFER = lv_xpassword.
lv_xpasslen = xstrlen( lv_xpassword ).
CALL FUNCTION 'CALCULATE_HASH_FOR_RAW'
    EXPORTING
      ALG      = 'SHA1'
      DATA     = lv_xpassword
      LENGTH   = lv_xpasslen
    IMPORTING
      HASHX    = lv_hpassword
      HASHXLEN = lv_hpasslen.
CALL FUNCTION 'SCMS_BASE64_ENCODE'
    EXPORTING
      INPUT            = lv_hpassword
      INPUT_LENGTH     = lv_hpasslen
    IMPORTING
      OUTPUT           = lv_b64password
    EXCEPTIONS
      OUTPUT_TOO_SMALL = 1
      OTHERS           = 2.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* build the header
CONCATENATE
'<soap-env:Header xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">'
'<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">'
'<wsse:UsernameToken wsu:Id="########" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">'
'<wsse:Username>'
lv_webservice_userid
'</wsse:Username>'
'<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">'
lv_b64password
'</wsse:Password>'
'<wsse:Nonce>'
lv_b64nonce
'</wsse:Nonce>'
'<wsu:Created>'
lv_created
'</wsu:Created>'
'</wsse:UsernameToken>'
'</wsse:Security>'
'</soap-env:Header>'
INTO lv_sheader.
*Build the xml header element
lv_xheader = cl_proxy_service=>cstring2xstring( lv_sheader ).
TRY.
      CALL FUNCTION 'SDIXML_XML_TO_DOM'
        EXPORTING
          xml           = lv_xheader
        IMPORTING
          document      = xml_document
        EXCEPTIONS
          invalid_input = 1
          OTHERS        = 2.
      IF sy-subrc = 0 AND NOT xml_document IS INITIAL.
        xml_root = xml_document->get_root_element( ).
        er_security_element ?= xml_root->get_first_child( ).
        gr_soap_security_header = er_security_element.
      ENDIF.
    CATCH cx_ai_system_fault .
ENDTRY.
ENDFUNCTION.

Consume a Web Service in ABAP

Hi,
We have a Web Service URL on PI. Run time of this Web Service in a Portal Server.
We need to access the Same URL from ECC using ABAP Programming?
Can any one tell me how we can call the same Web Service?
I need to pass few values to the web service using ABAP Code and I need to get back the result into some variables.
any code available for verify?
Thanks,
Sekhar.J

Hi,
Steps involved in Consuming a Web Service in ABAP.
1. You will need to create a Service Consumer Proxy in the ECC system.
The procedure for this is available in the documentation link [http://help.sap.com/saphelp_erp60_sp/helpdata/en/46/9743916d1115ece10000000a114a6b/frameset.htm] in the section Consuming a Web Service.. The URL access path of the WSDL can be used to generate the Service Consumer Proxy in ABAP.
2. Using transaction SOAMANAGER create the Logical Port for the Consumer Proxy created in Step 1.
3. Code the Consumer Proxy call in the ABAP program. Check section Consuming a Web Service --> Programming with Client and Server Proxies --> Sending a Message in the link specified above.
The Video link [Consuming Services in ABAP |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/media/uuid/20eb3174-41ab-2a10-a383-907faf60eed3] will provide good conceptual knowledge, steps involved and Logical port maintenance..
In case you face any problems, shoot your queries.
regards
Nitesh

Consuming a Web Service with ABAP in WAS 6.40 (SS3)

Hi Everyone,
     Has anyone successfully consumed a web service (based on an EJB) that is published to the J2EE engine of their WAS 6.40 server by creating a proxy from the ABAP layer?
     We are encountering the following problem: When executing method of the proxy to call the Web Service on the J2EE engine, the CX_AI_SYSTEM_FAULT exception is triggered with the message "Unallowed RFC-XML Tag (SOAP_EINVALDOC)".
     This same problem has occurred with multiple web services, even though the proxy generation seems to execute without a problem. Is there some system setting that could cause this? We have run the SOAP Runtime trace, but only receive the same basic information about the problem.
     If anyone has any thoughts at all, I'd be grateful to hear them.
     Thanks,
        --Greg

Hi,
We encountered problems when consuming a foreign WS. It seems to be that RPC style WSDL isn't supported by the WAS 6.4 WS proxy. An interesting reading on this is
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/the difference between rpc and document style wsdl.article
Eddy

WebDynpro Consuming a Web Service via SSL (https)

Hello dovelopers,
i want to consume a Web Service in a WebDynpro Application via https.
can anybody give me a few links to pdfs etc.
Thank You
Michel

Try this:
Are you trying to create https trust relation ship between two SAP Portals or SAP Portal to Non Sap Portal?
Help on How to Consume a Web Service in SAP Portal?
http://help.sap.com/saphelp_nw04/helpdata/en/f5/30c5aca7f92f418d889b99ccc9ee08/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/df/a08340d990ce62e10000000a155106/content.htm
http://www.sapportalguide.com/web_services.html
Here the documents helps you how to integreate https authentication betweeen two portals:
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/2235260b413fe1e10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/62/881e3e3986f701e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/29236de1864c6e8d46e77192adaa95/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/d3/41c8efb31d11d5993800508b6b8b11/frameset.htm
Thanks
Krishna

Web-site as iframe in webdynpro for abap

Hello,
we want to integrate an external website like google maps as iframe in webdynpro for abap-window.
Is it possible?
Regards
Oliver
Edited by: Oliver Prodinger on Apr 18, 2010 11:41 AM

Hi,
Please be aware that this UI element is deprecated and is not to be used. But we can use it in unavoidable cases.
Refer to the below link for step by step procedure on how to use the iFrame element.
http://divulgesap.com/blog.php?p=MTI5
Regards,
Lak

Handling of SOAP Faults in SOAP Clients consuming PI Web services

Hi there,
the following is in regards to SOAP fault error handling in a SOAP client that consumes a Web Service published by PI.
I have been reading a number of threads and blogs in regards to this topic and I am still left with some open questions which I hope to get some final answersclarifications through this thread.
In particular the blogs
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI      - Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
XI: Propagation of meaningful error information to SOAP Client     - XI: Propagation of meaningful error information to SOAP Client
have caused by attention.
Both of these threads are realating to the Fault Message type one can use to return errors back to a SOAP Client (.Net, Java, etc.).
In our scenario we published a number of Web Services through PI that provide functionality to integrate with an R3 back-end system using inbound ABAP Proxies.
The services are standardised and will be consumed by a number of .NetJava applications and systems. The reason for the use of ABAP proxies is the customer specific application logic that is executed in the backend system. The Web services are synchronous and don't use ccBPM in the middle. Transformations are performed in PI combined with various lookups to set default values before the message is passed into the ABAP Framework of the R3 back-end system. The lookups are done against the R3 back-end system using the PI RFC Lookup feature.
The inbound proxies currently return application errors as part of the response message back to the SOAP client. For more critical errors we introduced the use of Fault message types as the method to return the information back to the SOAP Client. This is all working satisfactory.
The questions I have are as follows.
1. When an error occurs at the IE level (e.g. mapping error), ABAP Proxy framework level (e.g. conversion from XML to ABAP format) or Adapter Framework level (Adapter releated error) a different SOAP fault message structure is returned to the SOAP Client than the one    used for the application errors. The SOAP fault message structure used in this case is the standard SOAP fault used by PI to return system errors back to the caller. For those SOAP fault messages there is no payload generated that could be mapped to the SOAP fault structure used for the application errors. This would be preferrable as there would be only one Fault message structure used for both inbound ABAP proxy generated fault messages and PI generated fault messages.
Also the error messages generated by PI can be quite cryptic and difficult to interpret at the client end and could be filtered     ranslated during message mapping if the payload of the PI generated SOAP fault message could be accessed in a message mapping.
Point 3 of the above thread 2759 indicates that this would be possible but doesn't outline how. Could somebody please clarify this for me as I don't believe that this is really possible ???.
My idea instead was to use the PI SOAP fault message structure to also return application errors. Therefore I would create a Fault message type that matches the PI SOAP fault structure. This would enable the SOAP Client to handle only one SOAP Fault error structure. Would that be something to look into instead ?????.
2. We have been looking at using the integrated WEB AS SOAP adapter instead of using the AF Sender SOAP adapter. While playing with this we encountered differences in the content returned through the SOAP fault generated by PI. A sample is below. Shouldn't the content of these SOAP faults be the same if the error that caused it is the same. Also the SOAP fault returned by the IE SOAP adapter is much more    useful in this particular case. Both errors below are the same, a conversion error from XML to ABAP took place in the inbound ABAP proxy framework of the back-end system.
SOAP fault returned when using SOAP Sender adapter of AF
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:PARSE_APPLICATION_DATA:
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
     at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
SOAP fault using integrated SOAP adapter of PI IE
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>System Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context/>
               <code>ABAP.PARSE_APPLICATION_DATA</code>
               <text>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXSBE20FF604BAFEF8D990A XML Bytepos.: 564 XML Path: ns1:CreatePORequest(1)POHEADER(2)COMP_CODE(1) Error Text: Data loss occurred when converting ############################## Kernel ErrorId: CONVT_DATA_LOSS))</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I have been reading threads for hours without being able to find one that answers questions 1 or provides a blog that outlines the approach one should take for error handling in SOAP clients that consume PI Web Services (and covers both PISystem generated faults and faults raised in Proxies).
There may already be a blog or thread and I just missed it.
Any comments are welcome.
Thanks. Dieter

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread

Consuming a Web Service with WEB AS 6.40

Hello,
i try to consume a Webservice from the internet. I have configured the logical port and i created the client proxy as shown in the following real good weblog from
Thomas Jung.
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
But when i try to test the proxy in SE80 I retrieve the following error:
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SOAP:111</CODE>
<ERRORTEXT>Unallowed RFC-XML Tag (SOAP_EINVALDOC)</ERRORTEXT>
What's wrong here? Someone can help me?
Thanks for your help!
Klaus

We had the same error message for one of our Proxy Web Service calls.
We tried to use an RFC instead of the URL, and performed a TEST CONNECTION. And low and behold, we received an error message that was much more helpful than the "Unallowed RFC-XML Tag (SOAP_EINVALDOC)" message.
The problem for us was that the Server that we were trying to consume the Web service from was blocking the IP address of our Web Application Server.
We contacted the administrator, he verified that was the case, removed the restriction, and all is good now.
Here was the message we saw when we tested it in the RFC:
The Web server you are attempting to reach has a list of IP addresses that are not allowed to access the Web site, and the IP address of your browsing computer is on this list. Please try the following: Contact the Web site administrator if you believe you should be able to view this directory or page.
Hope this helps!

Uploading PDF into webdynpro for ABAP

Hello,
I have a small Webdynpro for ABAP with an Interactive Form. I can fill my fields in this form. Now I downloaded the PDF to my local drive, changed the fields and tried to upload it again. Thats where my problem is:
I cant upload my changes. I used a File_upload UI Element which is binded to a attribute FORM.FILE type xstring. This attribut I binded to the Interactive_Form element field pdfsources. I implemented a button with an action for my server roundtrip.
I thought thats it but unfortunetly not. Can anybody tell me what I am missing.
Thanks in advance.
regards
stefan

Hi Stefan
Web Dynpro ABAP development recommends that you create a <a href="http://service.sap.com/message">customer message</a> on component BC-WD-ABA.
Best regards,
Markus Meisl

Consume a Web Service: No receiver could be determined

Hello,
I have a successful running Web Service on a JAVA stack. Now I want to consume this web service within the ABAP Stack. For this purpose I generated the appropriate proxy object from the WSDL.
However, while running my ABAP test program I am receiving an error: RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determined
Does anybody know, what to do? Do I need to register the generated proxy somewhere? Or what went wrong?
Best Regards!

you dont need to do any settings in LPCONFIG
just create client proxy and <b>activate</b> the proxy class
then in LPCONFIG
enter the client proxy name and port name (port name can be any text) and check the checkbox "default" and click create and activate the same.
now you are ready to consume the webservice.
Regards
Raja
assigning points to helpful answers by choosing the appropriate radiobuttons in the answers in the SDN way of saying thanks.

Consuming RepositoryFrameworkWS web service in WebDynpro for ABAP

Similar Messages

Maybe you are looking for