QM Cycle

[Rakesh Kumar Sahoo]

QM Cycle

1. Goods receipt
2. Check the inspection Lot Number (QA03)
3. Create Q-Info Record (QI01)
4. Create Master Inspection Characteristics (QS21)
5. Create Samling Scheme (QDP1)
6. Create Sampling Procedure (Assign Sampling Scheme to this) (QDV1)
7. Dynamic Modification Rule (QDR1)
8. Create Inspection Plan (Assign Sampling Procedure to this) (QP01)
9. Go back to Inspection lot and assign the task list (QA02)
10. Create Catalog at Client Level (QS41-Create Code Group and Codes)
11. Assign Code Group to Plant (QS51-Slected Sets should be created)
12. Result Recording (QE51N)
13. Usage Decision Codes
14. Usage Decision (QA11)

Post to Inspection type in Mat. Master will be there only when we do GR (for FERT as well as for ROH) 

QS28:  A list to see all the inspection characteristics

QI07: Vendor is given an access for quality inspection

QS31: Create Inspection method

CT04 &CL02: Class

QAC3: Reset Inspection Lot

QM01: Create notification

Catalog is for Qualitative. It is not for Quantitative.

Automatic Usage Decision can be made by the system by two ways: 

1. in Mat. Master, Inspection Setup: Check the Automatic UD and in the Usage decision code we mention the following posting to happen after the Inspection.
2. in Back-end we can setup Automatic UD for a plant.

Automatic UD will trigger the stock posting (from quality to unrestricted) only for passed lots. For failed lots, we have to go to the QA11 and do the manual entry (from quality to blocked and returns) in stock posting. (Even if we maintain Automatic UD is checked in Mat. Master)

QC01: Create a Certificate

QC15: Create certificate profile assignment

Certificate can be created for FERT as well as ROH. If the vendor sends a certificate, then we do not need to create certificate for it.

For HALB, we do not need to do QA11.

Key Date in QA01 should be the date when Inspection Plan is created, otherwise it will not find the Plan (when we do the task list assignment in QA02)

Catalog type "1" is not used for notification. "3", "5", "8","9" etc. are the catalog types which are used for notification types.

Action Box: Create a Action Box; then assign a particular function in that Action box. All the available actions are known as "Follow-Up Action". If something is not provide with standard SAP, then we create Action Box.