on 04-09-2009 11:47 AM
Hi all,
In "In-process" inspection (03), while doing the results recording, system gives the following information.
The previous operation has not yet been confirmed
Message no. QT215
This is an INFORMATION message. Client requirement is to get an ERROR message here, as PP user has not confirmed the previous operation. Please guide me.
Best Regards
Sam
Dear Sam
There is no standard solution for the same nor there is any possiblity of converting the message into error. You will have to do a development.
My suggestions for the development are
1) BADI : while saving Result Recording : QE_SAVE
If message QT 215 is getting triggered during saving the result recording convert the message into Error or give an error message so that result recording is not saved.
Or
2 ) Use the same BADI
Get the order Number AUFNR by passing Inspection lot number in QALS. Table
Pass Order Number to CAUFV Table to get Group (PLNNR)
Pass PLNNR in PLPO Table to get Control key STEUS = QM control key and the corresponding Operation Number VORNR. Check for the operation prior QM control key . Pass the VORNR and order Number A in AFRU table.
If there is an entry in the table then allow Save otherwise error message not allow Save.
Hope this helps
Regards
gajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sam,
You can do the following setting in customization ( PP ) for your requirement in OPK4.
Production -> Shop floor control -> Operations -> Confirmation -> Define Confirmation parameter
Select your Production order type and plant and in the general valid settings tab page change the operation sequence field from information to error when the operation sequence is not adhered to.
Regards
Sravan
Edited by: Sravan on Apr 10, 2009 6:15 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.