cancel
Showing results for 
Search instead for 
Did you mean: 

no action got executed corr to SubmitToSap button of Interactive forms

Former Member
0 Kudos

Hi

I am Using Interactive Forms and used button SubmitToSap of WD ActiveX,

written code on the action to save the doc on server,

but whn m pressing the submit button corresponding action/method is not getting executed.

even i had set the submit and check properties of interactive form to corresponding action.

but still on submit corresponding method is not getting executed.

kindly reply asap.

Regards,

Amit.

Accepted Solutions (0)

Answers (9)

Answers (9)

amolgupta
Active Contributor
0 Kudos

hi,

check these two articles....

[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f03414f8-d4ce-2a10-d4b6-ab201b329d98]

[https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/other-topics/how%20to%20check%20if%20the%20adobe%20document%20service%20is%20running%20correctly.pdf]

this will confirm if the ADS is running fine.

regards,

-Amol Gupta

Former Member
0 Kudos

Hi Amol,

It was the XACF version on my pc, that was causing the problem.

But thanks for the Links, they will be handy.

Regards,

Hanoz

Former Member
0 Kudos

Hi Amit,

If you have found out the solution of the submit to SAP button not working, even after binding it to an event, then please post it here.

Regards,

Hanoz

thomas_vanhaaren
Explorer
0 Kudos

Hi Amit,

Can you post your solution on this message as well. Would be fare since you posted a question don't you think?

Thomas

Former Member
0 Kudos

Hello,

I have the same problem. How did you resolve the problem?

Thank you in advance

Former Member
0 Kudos

I'have got the same problem.

I followed the steps in the previous msg and every installation gone well.

A button on the web page activate a function GET.. which break the debug.

The submit button on a pdf inside that same page, should activate the same

function GET... with the event OnSubmit but as the debug don't break and no

result appear, that function seem not to be even called.

Former Member
0 Kudos

your ADSUSER may have an expired password, check note 1004321

john

Former Member
0 Kudos

Hi Gianluca Barile,

thx for helping me again!!!

i did that conf part of ADS again but now m getting some error on the Load of Page earlier page was getting displayed but now it does'nt.

kindly find below the error detail:

Root Cause

The initial exception that caused the request to fail, was:

<b><b> " java.lang.Exception: Incorrect content-type found 'text/html' "</b></b>

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode(ClientMimeMessage.java:120)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:951)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)

at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)

at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)

... 36 more

See full exception chain for details.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1)

Version null

DOM version null

Client Type msie6

Client Type Profile ie6

ActiveX enabled

Cookies enabled

Frames enabled

Java Applets enabled

JavaScript enabled

Tables enabled

VB Script enabled

Server

Web Dynpro Runtime Vendor: SAP, build ID: 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:12:34[UTC], changelist=421181, host=pwdfm101), build date: Mon Jan 22 10:33:04 GMT+05:30 2007

J2EE Engine 7.00 patchlevel

Java VM Java HotSpot(TM) Server VM, version:1.4.2_09-b05, vendor: Sun Microsystems Inc.

Operating system Windows 2003, version: 5.2, architecture: x86

Session & Other

Session Locale en_US

Time of Failure Tue Feb 06 18:13:09 GMT+05:30 2007 (Java Time: 1170765789811)

Web Dynpro Code Generation Infos

local/CustomerDetails

SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:59:42[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)

SapDictionaryGenerationTemplates (unknown)

SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:48:59[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)

SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:05:10[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)

SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:49:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)

SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:49:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)

SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:57:39[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)

SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:02:09[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)

SapWebDynproGenerationCTemplates 7.0006.20060111154644.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:18:53[UTC], changelist=384368, host=pwdfm101)

SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:05:21[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)

SapWebDynproGenerationTemplates 7.0006.20060111154644.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:18:53[UTC], changelist=384368, host=pwdfm101)

sap.com/tcwddispwda

No information available null

sap.com/tcwdcorecomp

No information available null

Detailed Error Information

Detailed Exception Chain

com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to UPDATEDATAINPDF

at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:398)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:887)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:752)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

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:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

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:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process Render Request.

at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)

at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:98)

at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:121)

at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:342)

... 29 more

Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:

java.lang.Exception: Incorrect content-type found text/html

at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)

at com.sap.tc.webdynpro.pdfobject.core.PDFObject.render(PDFObject.java:3900)

at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:148)

at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)

... 32 more

Caused by: java.rmi.RemoteException: Service call exception; nested exception is:

java.lang.Exception: Incorrect content-type found 'text/html'

at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)

at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)

at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)

... 35 more

Caused by: java.lang.Exception: Incorrect content-type found 'text/html'

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode(ClientMimeMessage.java:120)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:951)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)

at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)

can you help me to resolve this issue.

Kind Regards,

Amit.

Former Member
0 Kudos

Amit,

Did you get it to work? Am facing the same problem. My submit button doesnt seem to do anything. Can you tell me what you did? Also, when importing RFC Model, did you give the login id as 'ADSUser' or something else?

Thanks,

Former Member
0 Kudos

Hi Amit,

could you check if this OSS Note <b>1004321</b>, solve your problem.

It talks about: ADS error: Incorrect content type found 'text/html'

PS: Don't forget to award points for good answers.

Best regards,

Gianluca Barile

Former Member
0 Kudos

Hi Gianluca Barile,

first of all thanks for your helpful reply,

but as i told earlier m not getting any error as such on click of button.

but on click event of button corresponding action(method) bind to on submit event is not getting executed.

can u tell me how i can check the binding or how can i bind the method to an Action.

kindly help me in this.

Regards,

Amit.

Former Member
0 Kudos

Hi Amit,

the only way for binding a method to an Action is done by WD Framework because WD Runtime can fire an Event. I think it's no possible to create an Event as we want but only follow the WDR generation.

The best you can do now is put a breakpoint into your code and see what happens when you press the button.

I suggest you to verify the configuration of ADS because in most cases the dump are had to this step, that's not properly planned.

Best regards

Gianluca Barile

Former Member
0 Kudos

Hi Amit,

you can try to check the R/3 and ADS connectivity configuration.

You can refer to Notes No:944221, 682619 which determine the steps to test the ADSconfiguration and troubleshoot.

After you must install on client the latest versione af Adobe Reader and the right version of ACF (downloadable from marketplace).

Hope this help you.

Regards.

Gianluca Barile

Former Member
0 Kudos

Hi Gianluca Barile,

Thx for Quick Reply,

but i m not using R/3 since m just passing string data to text fields on the form.

and the value that is passed on load of form is getting displayed without any problem but button used to save the file on server is not working even the code is tested and is fine that i used for this.

i have used ACF and Conf is also done.

can u send me the procedure writtn in SAP Notes u suggested.

Thanks & Regards,

Amit.

Former Member
0 Kudos

hi Amin,

I report to you the overall note's content:

Contact your system administrator and ask them to correct the configuration.

2. Generated PDF with additional information

As of SAP NetWeaver 2004s Support Package Stack 06, you can generate a PDF with attachments that allow a detailed error analysis.

SAP NetWeaver 2004s Support Package Stack 06/07/08

  • Extend your application URL with the "sap-wd-adsTrace=4" addition.

Note that there will then only be a display if the system can create a PDF. If this is not the case, follow the instructions that are contained in Notes 742674 and 846712.

SAP NetWeaver 2004s Support Package Stack 09 and higher

  • Set the Trace Level for Web Dynpro to 'ALL'. You can find detailed information about setting the Trace Level in Note 742674.

SAP NetWeaver '04

  • In these versions, the system does not display any PDFs with additional information, however, the trace files contain the notes that you require regarding the cause of the problem. Set the Trace Level for Web Dynpro to 'ALL'. You can find detailed information about setting the Trace Level in Note 742674.

Further information is given in the documentation for the Problem Analysis Scenario for Adobe Document Services - Adobe Rendering Error under:

http://help.sap.com/saphelp_nw2004s/helpdata/en/a6/4fbf6c5f644561a080e29070db9e97/frameset.htm

-> Attach these files (PDF with attachment) to a message with the component BC-WD-JAV, including an precise description of the problem.

Header Data

Release Status: Released for Customer

Released on: 22.12.2006 11:03:37

Priority: Recommendations/additional info

Category: Help for error analysis

Primary Component: BC-SRV-FP Forms Processing

Secondary Components: BC-WD-JAV Web Dynpro Java

Releases

Release Independant

Related Notes

1022238 - Formular FP_TEST_42 für einfachen Test einiger Fonts

1007116 - Form output in incorrect language

1004321 - ADS error: Incorrect content type found 'text/html'

959462 - ISR/Adobe: Configuration problems

934378 - SIBUIN: Broken layout in ERP2004 Unicode environment

915399 - com.adobe.ProcessingError: File not found on: URL location:

846712 - Analysis when Adobe Forms does not show values

842878 - Switch on traces for Web Dynpro session management in NW04

836174 - ISR/Adobe: Support for troubleshooting

742674 - Required information for web dynpro problem reporting

685571 - Printing PDF-based forms

-

-


682619



Summary
Symptom

You configure the Adobe Document Service with SAP NetWeaver '04 and to do this, you use the Adobe Document Configuration Guide Services.
Other terms

Adobe, ADS, PDF, Interactive Forms, forms, installation
Reason and Prerequisites

You use the Adobe Document Services with SAP NetWeaver '04.
Solution

This note is an addition to the Configuration Guide for the Adobe Document Service. It includes points that are not yet contained in the guide.
Versions of the Configuration Guide:

Version 1.7 of the Configuration Guide for SAP NetWeaver '04 Support Package Stack 14 is currently available on the SAP Service Marketplace, at http://service.sap.com/nw04installation -> SAP Web AS -> SAP Web AS 6.40 SR1 and Related Documentation -> Adobe Document Service. Version 1.4, which was valid for the Adobe Document Services in Support Package Stack 9, 10 and 11 is attached to this note.
We recommend that you always use the most recent version that is available on the SAP Service Marketplace.
Problem analysis

If an error occurs during or after the configuration, use the problem analysis scenario (PAS) to analyze and solve the problem. You find the PAS descriptions at http://help.sap.com -> Documentation for SAP Netweaver -> Solution Lifecycle management -> SAP Netweaver Problem Analysis Guide (PAG) -> SAP Web Application Server Problem Analysis Scenarios -> Adobe Document Services Problem Analysis Scenarios.

Server: Adobe Document Services Support Package Stack 12

For differences between Support Package Stack 11 and Support Package Stack 12, and for information about which problems are corrected with Support Package Stack 12, see Note 848539.

Server: Adobe Document Services Support Package Stack 9 (SR 1), 10 and 11

If you want to configure the status of the Adobe Document Service on Support Package Stack 9, 10 or 11, use the Configuration Guide attached to this note for Support Package Stack 11.

The current version for each is available on the SAP Service Marketplace (Support Package Stack 12 or higher).

Front end: Adobe Reader

To use Interactive Forms, Adobe Reader must be installed on the respective front end. For information on the version of Reader required, see Note 834573.

Header Data

Release Status: Released for Customer

Released on: 03.11.2005 10:56:34

Priority: Recommendations/additional info

Category: Installation information

Primary Component: BC-SRV-FP Forms Processing

Releases

Software

Component

Release

From

Release

To

Release

And

subsequent

SAP_BASIS

60

640

640

X

Related Notes

925741 - Adobe document services (ADS) with non-supported platforms

900945 - Error occurs during registration of aliases for certificates

899808 - Exception for creating alias on DocumentServiceConfiguration

873761 - Information for ADS SP-13

863872 - Adobe document services on OS/400

848539 - Changes on ADS SP-12

834573 - SAP Interactive Forms by Adobe: Acrobat/Reader version

789859 - ISR with Adobe: System requirement

766191 - Active Component Framework Installation

763772 - Installing SAP IS-M/AMC 1.0 on SAP NetWeaver 04

727168 - Adobe Document Services: Patches

Hope this help you.

Regards.

Gianluca Barile