Skip to Content
author's profile photo Former Member
Former Member

Putting restrictions on Printing

Hello Friends,

Following please find my requirement;

We have developed one programme to Print the labels during GR. Inputs for the Transaction of said programme is Material Document Number and the Year. Programme reads and picks the data from various tables like QALS, MSEG, MCHA, LFA1 and MAKT and prints the Label with details like Material Code, Description, Vendor, Vendor Batch, Material Document Number, Manufacturer, Exp Date, Qty, No. of Packs etc and the User ID by whom the Labels are printed. Now as an organisational policy we want to restrict the Printing of these labels ONLY ONCE to certain User IDs and Flexibility of multiple time printing to selective User IDs. How can we address this requirement?

We are thinking of making the changes in the programme such that it will update particular field in QALS once the Labels are printed for first time by a particular User ID but unfortunately not been able to identify any such field. Any suggestions in this direction or for any other solution are most welcome.

Thanks and regards


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Sep 07, 2007 at 09:33 AM


    I think you will need couple of custom tables to validate printing. Here's a possible solution.

    1. Create a custom table to hold user ID's who are allowed to print only once.

    2. Create another table to hold material doc, year, user ID and date/time of printing.

    Every time a user prints the document, validate userid with ID in table 1.

    a. If ID does not exist continue with printing.

    b. If user ID exists, check in table 2 if the document was printed earlier. If not printed, update the table and continue printing.

    c. If printed earlier, display error message.

    You will have to build this logic into your print program.

    Cheers !

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Rajesh

      Thanks for your input but could resolve the problem by making use of one field from MCHA table which is not used by our client. The Program is made and working satisfactorily. With your input, we did give a thought to creating Z Table but problem with it would have been of handling the quantum of data and the subsequent response of the system. But still your inputs were really useful.

      Thanks and regards.


  • Posted on Sep 10, 2007 at 01:42 AM

    Hi Chandra,

    Using an existing field from MCHA is not recommended. Moreover, you need more than one field to validate user & material doc.

    Cheers !

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.