Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Adobe PDF Form using SD_BIL_PRINT01 - dump msg

Former Member
0 Likes
2,181

Hello,

We are on ECC 6.0 and EH 0.  We do not have immediate plans to upgrade to EH 2 or higher, which would give us more up-to-date standard programs and SFP Forms, like program SD_INVOICE_PRINT01, which we don't have.  We do have program SD_BIL_PRINT01, which I have copied to our own custom version called ZSD_BIL_PRINT01.  I have also created, with txn SFP, an interface and a form for printing ProForma Invoices.  This will be our first developed Adobe PDF Form, so I am new to this.  All other forms in our system are old SAPscript Forms. The current ProForma is in SAPscript, but am re-writing it to get away from pre-printed forms and the old Tally printer. The problem I am now having is when the program ZSD_BIL_PRINT01 calls the SAP-generated function (the form), it dumps with the following message:

The current ABAP program "ZSD_BIL_PRINT01" had to be terminated because it has come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "/1BCDWB/SAPLSM00000011 " in  include "/1BCDWB/LSM00000011F01 " in line 1032:

"Field "EIKP-GRWCU" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement. ."

I looked in the include, on line 1032, and I don't see any code in there referring to table EIKP.  Strange.  In txn NACE, I created a V3 output type called ZD33 to use this program and form.  This function is generated by SAP when I activate/generate the interface, then the form from transaction SFP.  Why would SAP-generated code be giving me a syntax error?

Thanks,

Mark

1 ACCEPTED SOLUTION
Read only

Former Member
1,490

I found my problem.  In txn SFP, in the form, I had "de-activated" many fields in the BIL_S_PRT_INTERFACE structure, thinking I didn't need them.  I read somewhere it would be more efficient to pass less data.   Apparently this caused the dump error because it could not find certain fields defined.  I activated every field, saved and re-activated the form, and then it worked!  Lesson learned for me

1 REPLY 1
Read only

Former Member
1,491

I found my problem.  In txn SFP, in the form, I had "de-activated" many fields in the BIL_S_PRT_INTERFACE structure, thinking I didn't need them.  I read somewhere it would be more efficient to pass less data.   Apparently this caused the dump error because it could not find certain fields defined.  I activated every field, saved and re-activated the form, and then it worked!  Lesson learned for me