cancel
Showing results for 
Search instead for 
Did you mean: 

QM notification type and movement type relation

Former Member
0 Kudos

Dear Experts,

I am a SAP PP consultant and have one requirement in SAP QM in which we want to link movement types with QM notification of particular 'notification types" . We want to create n rejection notification when we carry out 122 movement type. This should happen automatically.

Is there any standard configuration??

Accepted Solutions (0)

Answers (1)

Answers (1)

rupesh_brahmankar3
Active Contributor
0 Kudos

Hello,

You can return the goods through quality notification please refer this useful document:Vendor Return through Quality Notification

An inspection lot is generated with a goods receipt posting for the purchase order. After that, the usage decision is made and the material is booked. Afterwards, a return delivery is posted for the purchase order. That can, for example, occur via the corresponding MM posting (Movement type 122) or also from a quality notification via the action box.

Refer detailed concept at SAP Help is at Define Follow-Up Actions for Tasks - Notification - SAP Library

Best Regards,
R.Brahmankar

Former Member
0 Kudos

Dear Bhramankar,

Actually our requirement is that, we need a quality "notification" to get generated when we "reject" the "inspection lot" through QA32. This should happen automatically.

Regards,

Ninad.

rupesh_brahmankar3
Active Contributor
0 Kudos

Hello,

In QCC3  Quality Inspection--Inspection Lot Creation----Maintain Inspection Types, enter the notification you want to trigger for inspection type 01 you can set F2 notification when you reject material and do defect recording, automatically notification will be created.

Also please search this forum before posting, as this topic has been discussed many times before.

Best Regards,

R.Brahmankar

busyaban7
Active Contributor
0 Kudos

Hi Ninad,

Your requirement is coming in bits and pieces, and that will create some confusions. Brahmankar has already shared the right inputs to you for your checking. Have you check it?

To start with your new requirement, you should check the below system & masterdata setup -

1. Assign Notification Type to Inspection Type - Please check the below config nodes:

SPRO -----> Quality Management => Quality Inspection => Inspection Lot Creation => Maintain Inspection Types => InspType => Inspection Results - Notification Type. Here, maintain the notification type, against your inspection type you wish to follow this process.

2. Activate Defect Recording for MIC - In QS22, for the MIC, go to control Indicators, under Results Confirmation tab there is a checkbox for 'Defects Recording'. Please activate it and Save this change. Please do this change for both Quantitative MIC and Qualitative MIC.

3. Add Catalog Types for Defect Recording in MIC - This is master data change. In QA22, go to Catalogs and update defect relevant catalogs there.

a) For Quantitative MIC - If your MIC has Upper Limit & Lower Limits activated, then maintain Catalogs for Defects for Rejection for -

* General

* At Upper Specification Limit

* At Lower Specification Limit

b) For Qualitative MIC - Maintain catalogs for General Defects.

4. Confirmation Profile - There should not be anything added as "Required" for confirmation profile, in case you wish to create notification at Background after rejection.

You can check this in the below SPRO node -

Quality Management => Quality Notifications => Defects Recording => Define Confirmation Profile - Check the most relevant Confirmation Profile you wish to you for your case, where 'Required' radio button is BLANK.

5. Define report Type - You can check this in the SPRO node:

Quality Management => Quality Notifications => Defects Recording => Define Report Type -

a) Define Defect Report Type - Select the Report Type and add Confirmation Profile and Catalog Profile. Also Maintain Origin for Catalog Profile as 'QN Type' or "Mat. No."

b) Assign Report Type to the Work Center - For your plant, add the report type and work Center as * and SubSystem checked.

Now when we have all the data and system setup in place, please can you answer the below few questions to understand your present process -

a) You wish to create Defects manually after "rejecting" an MIC value ?

b) You wish to just reject a MIC value, and wish to get the Notification created at background ?

c) You wish to process the inspection lot linked notification manually after it is created?

d) You do not wish to process anything in the Notification and just wish to close it for tracking?

Example:

A) Notification can be created at background after rejection of MIC, without recording the defects manually. To do so, your Confirmation Profile should not have anything as "required" and Defects recording not activated for MIC.

B)  If you wish to do Defects Recording in Dialog Option, then any one parameter form confirmation profile should have a "required Entry". This process has two Variants -

B.1)  Automatic Generation of defect In dialog option -

In this case Defect Recording in activated in MIC and defect Codes maintained for General/Upper/Lower specification levels.

B.2) Prompt for entry of Defect Data - In this case, Defect Recording though active at MIC level, but catalogs for defect recording is NOT added to MIC. System will ask you to add the right codes for it.

Hope you can now implement the complete solution based on your business condition.

Thanks,

Arijit

busyaban7
Active Contributor
0 Kudos

Just wished to add a few more points here -

1. While you add defects for notification, in case if you select "Activate" indicator, then you have to complete the Notification process to get system status "NOCO ATCO..". Then you can put UD for your inspection Lot.

2. In case you have created the notification, but do not wish to complete the Notification processing part, you can try not to "Activate" the icon. This will allow you go ahead with RR and UD for your linked inspection Lot.