cancel
Showing results for 
Search instead for 
Did you mean: 

ADS: com.adobe.ProcessingException: PDF is not interactive

Former Member
0 Kudos

Hi All,

I have a ECC 6.0 ABAP SP12Stack installation and a seperate NW04s SP13 Portal installation. I have done all the configuration steps of ADS integration on those 2 systems.

I developed a WebDynpro application and used the interactive form object referring to a simple Adobe form created with transaction SFP. As I test the Webdynpro ABAP application I get the following error "ADS: com.adobe.ProcessingException: PDF is not interactive. Data can only be imported into interactive forms.(201501)" in UPDATE_PDF method of class CL_WD_ADOBE_SERVICES. Do you have any idea for the reason of this error?

Best Regards,

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi.

Can it be applied to AS Java version too? Our system was updated from SPS12 to SPS16, and the following problem comes up:

com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Processing exception during a "MergeData" operation. 
Request start time: Wed Oct 08 16:49:20 BRT 2008 com.adobe.ProcessingException: PDF is not interactive. Data can only be 
imported into interactive forms. Exception Stack Trace: com.adobe.ProcessingException: PDF is not interactive. Data can only be 
imported into interactive forms. at com.adobe.ads.remote.EJB_PDFAgent.importFormData(Unknown Source) at
 com.adobe.ads.operation.MergeData.execute(Unknown Source) at com.adobe.ads.operation.ADSOperation.doWork(Unknown 
Source) at com.adobe.ads.request.Request.processOperations(Unknown Source) at com.adobe.ads.request.Request.process
(Unknown Source) at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source) at 
com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source) at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0_0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0_0.java:120) at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at 
java.lang.reflect.Method.invoke(Method.java:324) at 
com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126) at
 com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157) at 
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79) at 
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92) at 
SoapServlet.doPost(SoapServlet.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet
(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at 
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at 
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at 
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at 
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at 
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at 
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run
(MessageRunner.java:41) 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) 

    at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:400)
    at com.sap.tc.webdynpro.pdfobject.core.PDFObject.inputPDF(PDFObject.java:4003)
    at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInputPDFHandler.handle(PDFDocumentInputPDFHandler.java:139)
    at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
    at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:100)

The Interactive Form was working well before the update. As soon as we set our patched Web Dynpro development environment to use an ADS not yet patched, it works perfectly.

Regards,

Douglas Frankenberger

Former Member
0 Kudos

Hi,

I've gone through all steps of the ADS configuration and all tests are succesfull. What I observed is: If you first create the finterface and the form in SFP and then create your ABAP Webdynpro program where you insert an Interactive form object and bind your existing form it doesn't work for me. But if you first create your ABAP Wbdynpro program and insert an interactive form and type sth for the form in the template source and let the system create the form for you by double clicking on it then it worked.

Afterwards I compared both forms properties but couldn't find any differences...

Edited by: EBI Employee on Mar 4, 2008 4:20 AM

Former Member
0 Kudos

Hello all,

We're facing the same problem as described above after patching to SPS13.

Standard WDA application WDR_TEST_ADOBE sends the same exception as our custom PDF forms.

Did the SAP note 1090486 help you?

Thanks,

Francois

Former Member
0 Kudos

Hi,

we installed the note 1090486 and it works now,

Thank You

Former Member
0 Kudos

Hello,

Indeed, this note also solved our problem.

Regards,

Francois

chintan_virani
Active Contributor
0 Kudos

EBI,

Please reward and mark the thread as answered if your issue is resolved or post an update.

Chintan

Former Member
0 Kudos

To disply Adobe interactive form in your web browser you need following settings

1. Run ActiveX Control and plug-inc must be enabled

2. Script ActiveX controls set to be enabled .

3.Active scripting must be enabled.

To ensure this run FP_PDF_TEST_00 in transaction code se38 .

It should give the version no.

If it is giving the error you need to configure it correctly.

Regards

Shylajan D

Former Member
0 Kudos

How do you exactly do this?

chintan_virani
Active Contributor
0 Kudos

Hi,

Open your application which is accessing the Form in se80 and check the enabled property. For more information refer this [link|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/library/elearning/user-interface-technology/interactive-forms/rig-series-april2007/sap Interactive Forms by Adobe in Web Dynpro for ABAP (Session 3A)/?slide=20]

former_member365727
Active Contributor
0 Kudos

Hi,

Go to SFP transaction and click on Tools->Options, In the new window select 'Document Handling' and in the file options select 'Dynamic file' . This makes the existing non interactive form to Interactive form.

Regards

Srikanth KV

Former Member
0 Kudos

Hi,

i have the same problem.

I didn't find yet the Tools->Options Button in my SFP Transaction,

Thanks for any Help,

Michael

former_member365727
Active Contributor
0 Kudos

Hi,

'Tools' option will come only when you are in 'Layout'.

Regards

Srikanth KV

Former Member
0 Kudos

Hi,

In the form properties please specify it as interactive form.

Regards

sasi