Follow up action to set delete flag after UD (QS41, QS51)

[Former Member]

Hi all,

If user give UD as 'not good' for Equipment (eg Vernier Caliper) then he has to set delete flag for maintenance plan no and Equipment no through IP02 and IE02 respectively

now he want that, above delete flag should set automatically after giving UD so particular maintenance plan or equipment should not release in future.

I got one follow up action 'QM_PM' in transaction QS51 due to this after giving UD for Inspection lot, plan get technically complete (TECHO)

so how to make changes so i'll achieve above functionality

plz tell me about catalog, follow up action, QS41

thanks....

[Former Member]

Hi, Anmol,

There is one standard Follow up action is available is QM_PM.

Assign this follwo-up action to your relevant Code in the Selected set (QS51).

OR

Configure new follow-up action by using the function module "QFOA_ORDER_TECHNICAL_COMPLETE" that is standard function module from SAP to "Follow-Up Action: Technically Complete PM Order". And then assign this Follo-up action to your selected set.

I hope that will work for you. Pls reward points if helpfull

Regards,

Shyamal

[Former Member]

Hi Shyamal,

i am already using QM_PM follow up action which is doing Inspection lot TECHO (Technicaly complete)

but i want to set delete flag for both maintanance plan and equipmen, after giving UD as 'Not Good' for perticular equipment.

currently we are doing these activities by seperate transaction IP02 and IE02 respectively.

How to confugure follow-up action, do i need to make changes in function module "QFOA_ORDER_TECHNICAL_COMPLETE" or else?

thanks,

[Former Member]

Hi Amol,

Sorry I missed that part of your thred that you are aware about the readymade Follow-up action QM_PM.

Anyways, you need to some enhancement to incorporate you requirement and I think following function module and/or the User exists may help you.

Function modules;

CC_SET_DELETE_FLAG_HIERACHY Sets all deletion flags for all linked changes in a hierarchy

CLS_POPUP_DELETE_ATTRIBUTE Confirm to delete

CLS_POPUP_DELETE_REPORT_DEF Confirm to delete

COM_ATTRIBUTE_TAB_DELETE delete one attribute

DB_CLUSTER_DELETE Function module to delete a cluster table

DB_CLUSTER_DELETE_S Function module to delete a cluster table

PP_ORDER_REORG_CHECK Check PP order for ability to be deleted

User Exits

QEVA0010 UD: Usage decision check

MENUQA00 QM: Enhancement in QA00 Area Menu (Quality Inspection)

QEVA0008 Usage decision: Customer function key (e.g. to cancel UD)

Regards,

Shyamal

[Former Member]

Hi Shyamal,

thanks , i will check...

if queries occur, i will get back to this thread

[Former Member]

Hi all,

i got one solution on which i am working

Steps:

1.The solution is to use the User Exit namely QEVA0010 and use the logic as mentioned below.

2. Test and use the above mentioned user exit.

3. The first condition should be checked for Inspection Type - 14 and for UD code NG.

4.Logic to be used To set the deletion flag for the Equipment.

Go to Table QAPP - Pass inspection lot Number and get the Equipment no.

Go to Table EQUI - Pass Equipment no and get OBJNR

Go to Table JEST - Pass the Objnr - The value for deletion flag status is active is I0076 and the value for deletion flag inactive is I0320.

In order to set the deletion Flag,use help of FM - STATUS_CHANGE_INTERN to code.

5.Logic to be used To set the deletion flag for the Maintenance Plan.

Go to Table QALS - Pass inspection lot no and get the order no.

Go to Table AFIH - Pass order no - Get maintenance Plan.

Go to Table MPLA - Pass the maintenance plan and get the Objnr no.

JEST - Pass the Objnr - The value for deletion flag status is active is I0076 and the value for deletion flag inactive is I0320.

In order to set the deletion Flag,use help of FM - STATUS_CHANGE_INTERN to code.

[Former Member]

Dear Amol,

Congratulation for discovering the solution!!!

And lots lots of thanks for sharing it to the forum. It is really fully appreciable and the best example to those forum members who just post their threads and then show annoy and chafe towards the further dicussion and involvement. That discourage people to answer the thread.

But the triumph like your this thread (most importantly the last last one in wihich you described the solution also) is the one which is the actual motivational factor to answer the thread.

Best of luck!!!

Keep it up!!!

Regards,

Shyamal