QA33 Certificate background printing error

[former_member224035]

Hello experts,

At initial screen of transaction code QA33 “Inspection Lot Selection” suitable input is inserted. Then at the following screen “Display data for inspection lot: Worklist for Inspection Lots” the “certificate” button is pressed for inspection lot with status that is not allowed for certificate printing.

At screen “Quality Certificate for the Inspection Lot”

1. 1.       If foreground execution is selected.

The popup window “Status check error” appears with information about the printing certificate ( Detailed info: "Insp.lot/part.lot for certif." is not allowed ). Pressing the “close” or “cancel” button the window disappears.

1. 2.       If background execution is selected (following the path “Program” à “Execute in Background”)

The above window “Status check error” appears again, but this time if the “close” or “cancel” button is pressed “Status check error” will be replaced from the new window “Background Print Parameters”. If we continue and eventually send the program to background job this will run forever and we can only stop that by canceling the job. From the job log we can find that the program is trapped inside an endless loop giving the message "Insp.lot/part.lot for certif. is not allowed”.

This is a serious bug of the system which ends up with a endless loop at background consuming memory and prevent other applications from running.

I have already communicated with sap but they have answered the following message:

"If you want to prevent, that a user executes the process with an
inspection lot without UD, you can implement an additional check for
the status, which avoids user to continue the process."

Has anybody else found in the same situation but I don't think that solves the problem. Is anyone familiar with the above problem;

Is there a solution for preventing a user execute background Certificate printing with an inspection lot without UD?

Thanks in advance.

[former_member42743 · Accepted solution]

There are several possible ways to do this I would think.

Some of these exits might be employed.  Depending on how you send and create certs you might need to put checks into more than one exit.

QC100001 QM certificates: User exit for list of batches used          

QC100002 QM certificates: User-defined initialization option         

QC100003 QM certificates: Before and after cert. profile determinatn 

QC100004 QM Certificates: User-Exit Before Call-Up of Form Printout  

QC100006 QM Certificates: User-Exit After Selecting Delivery Data    

QC100007 User-Exit for Changing Certififcate Profile Characteristics 

QC100008 QM certificates: User exit for changing the customer number 

QCE10001 Enhancement Modules: Electronic Certificate Dispatch        

QCE10002 QM: Enhancement to IDoc Type QALITY02                       

QCE10003 QM: Quality Data Exchange of Electronic Cert. in Insp. Lot  

QCPA0001 Certificates: Assign control data of certif. profile char.

A low tech way to accomplish this would be if  you always require them to utilize a delivery when creating the certs.  Then in the delivery, you make sure you have a batch search strategy to only allow batchs with certain UD codes on them. 

Craig