Form size increases with F4 help

[Former Member]

Hello All,

I am facing a performance issue in an interactive form. We have developed an adobe form and linked it to portal through WebDynpro. We have around 10 fields with F4 help on the screen. We achieved the F4 help with a push button next to the corresponding field on the form and linked the field to the View context in WebDynpro and added dictionary search help.

Tha problem here is- as we go on entering the data by clicking on F4 help, by the time we reach 4th or 5th search help the size of the form increases, as shown in the status bar at the bottom of any webpage, up to 5 or 6 MB and it will take a lot of time to load update the form with the selected value from search help. We have incread the ICM parameter to give user more time to fill the form but this is not a good practice as we know.

Is there a way to improve the performance in this case? Following are details of system:

1. ADS - SP 17

2. NetWeaver 7.0/2004s

3. Already activated "Allow form rendering to be cached on server" in form properties in SFP.

Any inputs will be very helpful.

Thanks,

Anil

[Former Member · Accepted solution]

Hi Anil,

Have you maintained binding of "pdfSource" in your webdynpro? It is very performance critical and most

often not necessary: It's necessary only, if the PDF document (in binaryformat!) has to be available in the ABAP backend. If your application is interested on the form DATA only (which is the standard use case) you should NOT bind pdfSource.

To fill this property, the Web Dynproruntime has to make an additional call to the Adobe Document Services

(ADS, located on the JAVA stack!) to get the PDF. This is very time consuming! See SAP note 999998 too.

Because I have faced performnce problem with F4 helps, then I realized the problem is with the binding. Once I removed binding I could see lot of difference in the performance.

Regards,

Ravi.D

[Former Member · Accepted solution]

Hello,

Thanks a lot for all your replies. I will cross check all your inputs. However this is the configuration we are using now:

1. Adobe Reader 9

2. ADS SPS 17, only 18 is the latest one and as per SAP it shouldn't be a big issue

3. ZCI script update- can you please explain me how we do this?

Ravi, can you please tell me where do I maintain this binding option in WebDynpro?

Thanks,

Anil

[OttoGold · Accepted solution]

Click on the Interactive form object and find the parameter pdfSource. Easy. Otto

Edited by: Otto Gold on Mar 18, 2010 9:28 AM

[Former Member · Accepted solution]

Hello Ravi,

I have checked the setting in WebDynpro. We are not using the pdfSource parameter. It is left blank.

What else could be the reason? We have 10 fields with F4 helps. And our complete forms is of 2 pages.

Thanks,

Anil

[Former Member · Accepted solution]

Hello Ravi,

Thank you very much. The issue is resolved now. We were using pfgSource in one of the 7 views and that caused the issue. With your help this issue is resolved

Regards,

Anil

[Former Member · Accepted solution]

Hi Anil,

Good to hear that... Happy Programming with Adobe

Regards,

Ravi.D

[RalfRuth]

Hello Anil,

I don't think that the amount of data Web Dynpro sends to the Adobe Reader increases dramatically - I assume there's a problem with your form / Adobe Reader (what's the Reader version you are using?).

Some users in the forum reported recently that an update of the ZCI script has solved such performance problems.

You could do the following to narrow down the problem:

- analyze the server response times and the amount of data transferred to the browser using a HTTP sniffer (HTTPWatch or fiddlertool): Only the requests containing the name of your Web Dynpro application are of interest.

- If you are using Adobe Reader 8: Watch process AcroRd32.exe with the task manager, esp. the memory consumption.

The following actions could help:

- Update Adobe Reader to the latest version

- Update the ADS and the ZCI script of your form, i.e. update to the latest SAP NetWeaver SP (ABAP + JAVA) and call transaction SFP_ZCI_UPDATE for your form afterwards

- If this doesn't help, you should open an OSS message

Ralf

[Former Member]

i've never done a drop down like that, but it doesn't make sense that your form size would grow - i wonder if it's storing those values in adobe even after you've selected your value from F4.

if you don't have too many entries in your dropdown, there is an alternative way to pass those F4 values to the form.

If you have > 500 entries, one thing you can try is to create a web service to grab those entries for you instead of linking to

otherwise, see if there's some property of the button you can clear after the value is chosen.