cancel
Showing results for 
Search instead for 
Did you mean: 

Migration 7.31. to 7.40 Adobe forms.

Former Member
0 Kudos

Dear experts.

After migration from nw 7.31 to 7.40 some adobe forms with java-script code ( used to fill a table and calculate values in columns ) add lines at end of the table with ZERO value in calculated columns.

Is it a known migration problem? Before de migration this form is created fine but it is possible that code is a bit robust or ... other documented issue.

Do you have any idea?

Thanks and regards David.

Accepted Solutions (0)

Answers (1)

Answers (1)

SandySingh
Active Contributor
0 Kudos

Hello David,

What is the version of Adobe life cycle designer? I think this issue could be due to incompatible Designer version and net weaver release.

Refer to following SAP notes

SAP Note 1317925 - "Maintaining backward compatibility with Designer"


SAP Note 1863816 - "Adobe LiveCycle Designer 10.4 - Installation" (SAP NetWeaver 7.31 SP-7 and higher, SAP NetWeaver 7.40 SP-2 and higher)


Regards

Sandy

Former Member
0 Kudos

Hello Sandy.

My version of Adoble Life Cycle Designer is

Stack Java (Sap Portals)  is 7.40 and ADS is 1040.20140522041433.909128.

I think that is compatible with oss note 1317925.

The adobe form was developed in 7.02 nw abap. And this develop contains zcode Java Script.

Is this Java Script code one probably cause of error?

Is one good practice do not develop Java Script in Adobe Forms?

Thanks for you help and best regards.

David Sánchez.

SandySingh
Active Contributor
0 Kudos

Hello David,

You can use both Form Calc or Javascript in adobe forms as scripting language.

You can comment out the Javascript code and see if the problem persists.

Take a backup of the form. Try to delete the table and recreate it. You can copy the scripts from old form to new forms in table section.

Regards

Sandy

Former Member
0 Kudos

Thanks Sandy,

I make this test. And I generate data test. I locate the problem in one structure SFPDOCPARAMS. The field to fill is "SFPDOCPRAMS-DYNAMIC".

My problem is that this adobe form is called since one webdynpro and in this case i do not know how can i fill it. For me is not clear. Why this structure is filled autmatic for the system in two ways depending of the version NW?

This WebDynpro only has One Window, and de Window has onve View.This view only call adobe form. It is means that I can not call function module FP_JOP_OPEN.

I will try to add this structure to de context of WD.

If you have better idea, please tell me.

Thanks and regards David Sánchez.

SandySingh
Active Contributor
0 Kudos

Hello David,

Are you using dynamic table in the adobe forms. If so then check the settings mentioned in the following document. Looks like SFPDOCPRAMS-DYNAMIC parameter is set from "Form properties> XDP Preview Format> Dynamic

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/802f0ed1-a17a-2c10-7db4-d515a5b04...

Regards

Sandy

Former Member
0 Kudos

Thanks Sandy,

I was readed this document. In it explain that I need use the function module FP_JOB_OPEN to fill structure. But my webdynpro - window call directly adobe form. It means that this function module in not called.

Is other way to fill this structure?

Thanks and regards David Sánchez.

Former Member
0 Kudos

Hi Sandy,

I am currently working with David in this problem. Just wanted to add some more data.

We launch the Adobe Form in our WebDynpro, we have an InteractiveForm component and in the templateSource field we are using our Adobe Form. This Adobe Form is producing empty lines in some tables with zero as value, as stated by David.

This morning we tried to launch the function module generated automatically for our Adobe Form (/1BCDWB/SMXXXXXXX) I noticed that in the function module we can inform the "1BCDWB/DOCPARAMS" structure, this structure appears in every interface but it doesn't appear on the Adobe Form or in the WebDynpro related context (generated automatically for the Adobe Form).

If we launch the Adobe Form this way AND we only inform the "DYNAMIC" field of the structure the Adobe Form works just fine, if instead we inform "DYNAMIC, UPDATE_INTERACTION_CODE and FILLABLE" fields we get the same errors as when we launch the Adobe Form in our WebDynpro.

Hence:

- By default this structure seems to inform all three fields for the Adobe Form, triggering the error.

- If somehow we can set the values of this structure in our WebDynpro we will probably solve our problem.

We have checked many posts of people which seem to launch the Adobe Form in their WebDynpro directly by calling its related function module (/1BCDWB/SMXXXXXXX), but we are not making this, we just map the data to the WebDynpro's context and the Adobe Form is called automatically.

Is there any way to set the values of structure "1BCDWB/DOCPARAMS" from the WebDynpro? Or maybe set its values by default to only the Dynamic field informed.

We are looking to solve this, if we find the solution we will post it here.

Thanks for your help,

Regards.

SandySingh
Active Contributor
0 Kudos

Hello David,

Have you tried setting the 'Dynamic" value via SFP   Form properties> XDP Preview Format> Dynamic ?

Also if you are calling the adobe form in Webdynpro then ensure that adobe form has ZCI layout and 'webdynpro script" is added in SFP > Layout> and button is added from the webdynpro native form library. Then update the form layout using program FP_ZCI_UPDATE.


Run report FP_CHK_REPORT to check the Zero Client Installation (ZCI)

Regards

Sandy

Former Member
0 Kudos

Thanks for your help.

I Think that i can solve it.

David.