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

SapScripts

Former Member
0 Likes
528

Hi All

I am facing a peculiar problem. Here is the descrition.

WHile printing a billing document for an invoice only half of the page is getting printed but there are all together 3 pages to be printed. where as when i use a different invoice number. no problem complete invoice is getting printed. All the other parameters are same for both the invoices.

PLease help me solve this

regards

sree

4 REPLIES 4
Read only

Former Member
0 Likes
465

Hi Sree

When it is working for one invoice number properly, and not for another invoice number that means some conditions are getting failed which to me, seems to be problems not with script but with the way data is maintained.

What you can do is, debug the SapScript form seperately for both invoice numbers and see what is the difference, you may make out what condition fails for 'problematic' invoice number.

See, in which 'Element' of script it fails and do some reverse engineering from script to printing program to reach at the bottom of problem.

Regards

Ashish Jain

Read only

0 Likes
465

Hi Ashish

Thanks for your sincere efforts. Actually i debugged the invoice and found that all the variables are corrected populated both in the print program and layput set.

Any other alternative to be looked in

Thanks

Sree

Read only

Former Member
0 Likes
465

hi

try debugging the script for both invoice numbers. There may be some codition in script that might be failing in problematic case.

Just see in which 'ELEMENT' of script it happens or alternatively see till which element it is printing and whats the next element that is not getting printed.

Then, find this 'element' in print program (in Call function 'Print_Form'). Put a breakpoint there for current testing-iteration, then move backwards (putting breakpoints) in print program in next testing-iterations.

With this approach, you may be able to identify the source of problem. Don't forget to compare the results with other invoice number.

Regards

Ashish Jain

Read only

Former Member
0 Likes
465

For debugging the script, go to SE71, just enter form name, from Utilities -> degugging on

Regards

Ashish Jain