Adding a button in QA02/QA03 for Printing

[Former Member]

Hi All,

I have to add a button to QA02/QA03 to print labels. I have identified an enhancement QPL10004 and created a project. In this I have used screen 0100 of program SAPLXQPL to add the button. I have assigned a function code LBLPRINT to the button.

I can see the button on screen and after clicking the same the test code I have written gets executed. However at the end I am getting an error message "Requested function LBLPRINT is not available here". When I debugged the code I found that it is executing a screen control FM and reading data from T185, T185E and T185F tabls and based on the result giving the error.

Can someone please help?

[Former Member]

Hi All,

I have to add a button to QA02/QA03 to print labels. I have identified an enhancement QPL10004 and created a project. In this I have used screen 0100 of program SAPLXQPL to add the button. I have assigned a function code LBLPRINT to the button.

I can see the button on screen and after clicking the same the test code I have written gets executed. However at the end I am getting an error message "Requested function LBLPRINT is not available here". When I debugged the code I found that it is executing a screen control FM and reading data from T185, T185E and T185F tabls and based on the result giving the error.

Can someone please help?

[Former Member]

Hi Abhijit,

You can probably try to clear the sy-ucomm once the control passes to the custom code. Try this and see.

Thanks

Deva

[Former Member]

Hi,

Thats the first thing I tried. Still it is not working because as the control moves to main program's PAI, the fcode value is again populated.

[Former Member]

I had exactly the same problem in the maintenance order transactions when we added a push button there. Basically there are two options as far as I know:

1) Maintain the new function code for program SAPLQPL1 in view V_185. You could use similar settings as for the fcode ENT1. Note: This is considered a SAP modification; subsequent support packages may overwrite/delete the custom entries in tables T185*.

2) Modify the PAI of the calling program to blank out the sy-ucomm or the corresponding function code assigned to the carrier dynpro. This was the option which we chose in the maintenance order programs (modified form ABLAUF).

Hope that helps.

[Former Member]

Hi All,

Thanks for your answers. Some time back I was able to solve it by adding entries in 185.