Adobe Form Error FPRUNX001

[Former Member]

Hi everyone,

When trying to print a customer specific sales invoice form, the

following message appears in the log of execution:

"ADS: com.adobe.ProcessingException: com.adobe.ads.excep(200101)"

The message number is "FPRUNX001".

The detail message says to execute the steps of note 944221 but no

improvements after performing these steps.

What is the reason for this message and how can it be solved?

I saw some older threads in the forum talking about this issue but no answers have been given. So I hope that someone knows this one.

Best regards,

Sylvain

[Former Member]

Hi everyone,

Thank you for all your answers. We were able to find the problem. It was due to a field that was defined larger than permitted on the second page of the form. It was defined larger than the sub form and the page width.

The error was not really related to the ADS definition itself and therefore the message text was not relevant in this context.

By the way program FP_TEST_00 was not dumping because of a standard syntax or form error but because some parameters have to be initialized to be able to call the form. If you run the program you will see that no form parameters can be entered. You always pass some parameters (Structures, Tables, Fields, etc.) to a form to run it correctly. Considering this fact, I do not understand how can this program be run?

Best regards,

Sylvain

[Sandra_Rossi]

Thx for the feedback.

About FP_TEST_00, I guess that you entered your own test form, but of course you shouldn't, it can work only with FP_TEST_00 form (or any form with the same interface, but I'm not aware of other such forms). This is a test of ADS, not a test of your own form!

sandra

Edited by: Sandra Rossi on Apr 22, 2010 11:58 AM

[Former Member]

Hi,

Could you please explain the meaning by saying

It was due to a field that was defined larger than permitted on the second page of the form. It was defined larger than the sub form and the page width.

We are facing the same issue and we are not able to resolve the issue.

A prompt reply would be greatly appreciated.

Thanks,

Tirth

[Former Member]

Hi,

Actually program FP_TEST_00 does not run correctly since I receive a dump saying that some paramters have to be entered for a correct form execution. Program FP_TEST_00 does not permit to enter parameters.

Program FP_PDF_TEST_00 runs correctly and a window with the Version Information: 800.20090130093518.519793 appears. So everything sounds good in this step.

Program FP_CHECK_DESTINATION_SERVICE end correctly by saying that 9 303 bytes were transfered for both modes. Everything looks fine here.

I hope that my answer help a bit more in understanding the problem.

Thanks,

Sylvain

[OttoGold]

Hello,

If you are sure your ADS service is running ok, then probably that is the problem of the form. I have experienced it few times before in these cases:

- there was some mismatch in the form (weird binding, weird combination of field settings etc.)

- there was a problem with some data values (weird values were coming from backend)

- combination (weird values into the right fields or the right values but not for the properly typed fields)

How I was debugging the form:

- deactivate parts of your form context, try that with one by one, you will find the one which causes the problem

- understand the use of SFP form trace (debug files attached to the form)

Hope that helps a little. By the way: there is Adobe forms forum under NetWeaver.

Regards Otto

[Sandra_Rossi]

FP_TEST_00 should not dump! (this is an official program that administrators must run to ensure the ADS configuration is okay, as explained in the ADS configuration manual). Usually it works well or gives an error message, but doesn't dump.

[ralf_dillenburger]

I agree with Sandra,

if the FP_TEST_00 dumps, there is an error in your ADS Configuration. I don't think you need to debug your own form as long as the SAP default form generated by FP_TEST_00 dumps.

Try to set the user params as mentioned in note 944221:

FPTRACELEVEL = 04

FPTRACEFILE = <path>\<file>

FPSAVEERRORPDF = X

FPERRORPDFFILE = <path>\<file2>

Then start again FP_TEST_00. After that, maybe there are some logs in the specified path containing more details of your problem.

Regards

Ralf

[Joerg_S]

SFP Trace is very useful ! we faced a problem using Custom XDC File

you can find that information easily using TRACE Level 2 (SFP + Form FP_TEST_00)

"love it"

[Sandra_Rossi]

So, you tried 944221. What are the results of tests? (FP_TEST_00 works? other ones?)

[sap library - Troubleshooting for Runtime Errors FPRUNX001, 002, and 004 |http://help.sap.com/erp2005_ehp_03/helpdata/EN/c2/3b7ba18ea44e13aa9bb252189e2f34/frameset.htm]

Note 717568 - FPRUNX001, 002 or 004 with output of PDF-based forms

Note 748614 - FP_GET_LAST_ADS_TRACE: no trace if an error occurs : what detailed message do you get?