By: Rahul Gandhi
The SAP QM component contains functions for recording and processing different types of problems (for example, problems resulting from poor-quality goods or services). You can use the notifications to analyze the recorded defects and monitor the correction of these problems. In particular, the notifications can help you process internal or external problems such as:
- Describes a business object's nonconformance with a
quality requirement and contains a request to take appropriate action.
- A customer complaint is a quality notification type
(Q1) that deals with a problem involving poor quality goods or services
delivered to a customer.
- A complaint against a vendor is a quality notification
type (Q2) that deals with a problem involving
poor-quality goods or services delivered by a vendor
or manufacturer.
- A user-specific quality notification is one that does
not belong to one of the standard notification types predefined in the
QM component.
And it also deals with customer specific problems in service notifications. And maintaince a track what happend to that notification like whether it is in process or investigation is going on or activity is completed and so on.If same complaint is there more than once can be refered to previous.
And most of the time all these sequence of steps are configured in workflow and process will be going on a smoother manner.
Mainly deals with problems in equipment at all levels. And is integrated with other modules.
The following is the process overview of the SAP Quality Management Module -
1) Master Data maintenance -
- Maintain material master QM view with required inspection
types as 01/0101/0130 for procurement, 03/04 for in process, 10/11/12 for
delivery. Assign characteristics as per requirement (post to inspection
stock, check characteristics, automatic assignement etc) (Transaction MM01
/ MM02).
- Maintain sampling scheme (transaction QDP1 / QDP2)
& sampling procedure (Transaction QDV1 / QDV2)
- Maintain inspection method (QS31)
- Maintain catalogue (Transaction QS31 for code group)
& QS41 for selected set).
- Maintain master inspection characteristics (Transaction
QS21).
- Maintain Quality Info Record for Vendor (Transaction
QI01) & for Customer (Transaction QV51)
- Maintain Inspection Plan (Transaction - QP01)
- Maintain inspection operation & inspection characteristics
for the same in routing for production (Transaction CA01).
2) Process for Procurement -
- Create purchase order (Transaction ME21N). The quality
master data is copied to purchase order (like stock type, certificate required).
- If required create source inspection lot manually (transaction
QI07)
- Carry out source inspection & post the source inspection
results (Transaction QE51N). Take usage decision for the source inspection
results (Transaction QA11).
- Post GRN (Transaction MIGO).
- Inspection lot is created & stock posted to inspection
depending on the settings in material master & quality info record).
- Check the material & post the inspection results
(Transaction - QE51N). Take usage decision & post the stock to required
stock type (Transaction QA11).
3) Process for Inprocess inspection -
- Create &release Production order (Transaction -
CO01)
- Post the operation results (Transaction - CO11N)
- Post the quality inspection results (Transaction QE51N)
- Take usage decision (Transaction - QA11)
- Confirm Production Order
4) Process for Sales & Distribution -
- Create Sale Order (Tranaction - VA01)
- Create delivery (transaction - VL01N) when material
is ready
- Inspection lot is generated. Post inspection results
(QE51N)
- Take usage decision (QA11)
- Post the goods issue (VL02N)
