SAP Library / QM / Cheat sheet
SAP QM cheat sheet
21 objects in 3 groups. Each links to its full reviewed page.
T-Codes13
- QA01QA01 manually creates a quality inspection lot for a material and plant, using the same lot-creation engine that automatic triggers (goods receipt, in-process confirmation, stock transfer) call in the background. It is used when no automatic trigger exists for the situation - audits, complaint samples, stability testing - and it fails with the same setup errors automatic creation would if the inspection type is not maintained.
- QA02QA02 changes an existing inspection lot's header data: sample size, inspection specifications, deadlines, stock posting rules, and quantities. It does not record characteristic results (QE01/QE51N) or post the usage decision (QA11/QA12). Most fields become read-only once results exist or a usage decision has been posted, which is the main source of confusion when a field will not open for edit.
- QA03QA03 is the display-only transaction for an existing quality inspection lot. It shows lot header data, characteristic results, usage decision status, and stock quantities, but every field is greyed out. Consultants use it to check lot status without risk of altering data; anyone needing to enter results, record a usage decision, or change quantities must use QA02 or QE51N instead.
- QA11QA11 records the usage decision on a quality inspection lot, the action that closes the lot and tells the system what to do with the inspected stock: release to unrestricted use, block, scrap, or return to vendor. Saving a usage decision can trigger an automatic stock posting through the inventory management interface, so the UD is a business-critical closing step, not a status label.
- QA32QA32 is the ALV worklist transaction for inspection lots in change mode. It is used to select a group of lots by plant, material, lot origin, or status and then act on them together, such as entering a mass usage decision or releasing several lots at once, rather than editing a single lot number by number as in QA02.
- QE01QE01 records inspection results against one inspection lot number entered by the user. It has no worklist or selection screen, unlike QE51N. It is used when the lot number is already known, typically from a goods receipt slip or a batch program, and is kept for legacy setups and single-lot troubleshooting rather than day-to-day shop-floor recording.
- QE51NQE51N is the results recording transaction in Quality Management, used to enter measured or attribute values against inspection characteristics for an inspection lot, physical sample, or piece of equipment, before a usage decision is made. It is a single unified screen that replaced the older separate QE0x family of transactions.
- QM01QM01 creates a quality notification (customer complaint, complaint against vendor, or internal problem report) tied to a notification type such as Q1, Q2, Q3 or a custom Z-type. It is a shell transaction: the tabs, catalogs, partner fields and follow-on actions that appear are entirely driven by the customizing behind the chosen notification type, not by the transaction itself.
- QM02QM02 changes an existing quality notification created in QM01 - adding or editing defect items, tasks, activities, causes and partners. The notification type fixed at creation determines the tab layout and field selection and cannot be changed here. Editing is gated by system and user status; a completed or closed notification shows most fields greyed out until the status is reset.
- QM03QM03 opens a quality notification (complaint, defect record, or internal problem report) in read-only mode. It shows the same header, item, cause, task and activity structure as QM02, but every field is greyed out. Most confusion around QM03 comes from mistaking a locked, non-editable screen for missing or deleted data.
- QP01QP01 creates a quality inspection plan, a task list that defines which characteristics, work centers, sampling procedures and specifications apply when a material is inspected at a given plant. It is master data setup, not lot creation. Inspection lots generated later by QA01, goods receipt or production confirmation read this plan to determine what gets inspected and how.
- QP02QP02 changes an existing quality inspection plan: its operations, characteristics, sampling procedures, and material assignments. Inspection plans are identified by a plan group and group counter, not by material, so the same plan can serve several materials through a separate allocation table. Changes only take effect for inspection lots created after the change, not for lots already open.
- QP03QP03 displays an existing quality inspection plan (task list type Q) either by material and plant or by plan group and group counter, showing the operations, inspection characteristics, and sampling procedures attached to it. It is read-only; use QP02 to change the same object.
Key Tables5
- QALSQALS is the header table for inspection lots in SAP Quality Management. One row represents one inspection lot: the material, plant, batch, lot quantity, origin type (goods receipt, in-process, goods issue, audit, and so on), creation date, and the object number used to look up its status. Usage decisions, characteristic results, and defect data sit in separate tables joined on the lot number.
- QAMRQAMR stores characteristic-level inspection results for inspection lots. SAP documentation names QAMR 'Characteristic: Results'. It contains the summarized or result state for a characteristic after results recording, while individual single values are stored separately in QASE. The record must be interpreted together with the corresponding QAMV specification and inspection-lot context.
- QAMVQAMV stores inspection-lot characteristic specifications: the characteristic-level requirements copied or generated for an inspection lot before results are recorded. SAP documentation describes QAMV as 'Characteristic: Specifications'. It does not store individual measured values; single values are stored in QASE, while characteristic results and valuations are held in results structures such as QAMR.
- QAVEQAVE stores usage decisions for inspection lots or partial lots. SAP documentation identifies QAVE as 'Usage decisions', including the decision code and timestamp used when the inspection is completed. It is not the characteristic-level pass or fail valuation table; characteristic specifications, results, and single values are handled in QAMV, QAMR, and QASE.
- QMELQMEL stores the header-level master and process data of quality notifications, including notification number, notification type, dates, status object, material or technical reference, organizational data, and responsible context. Notification defects, causes, tasks, activities, partners, and status history are stored in companion tables such as QMFE, QMUR, QMSM, QMMA, IHPA, JEST, and JCDS.
Common Issues3
- Inspection lot not created at goods receiptNo inspection lot is generated because the goods receipt did not meet the conditions QM checks at posting time: an active QM view with inspection type 01 switched on and given an active control key, the correct plant, a QM-relevant movement type, and a purchase order item created after those settings existed. If any one of these is missing, stock posts straight to unrestricted-use with no lot.
- Results recording not possible for the characteristicThe message means the inspection lot, the specific characteristic, or its master setting is in a state that does not allow a value or skip code to be entered right now. The usual causes are a lot not yet released, a characteristic whose recording indicator is switched off, a characteristic already closed, or a specification validity gap. It is rarely a program error.
- Stock stuck in quality inspection after usage decisionThe usage decision was saved and the inspection lot shows a decision code, but the goods movement that should move quantity out of quality stock either never fired, failed, or only partially fired. Check the lot's stock posting status on the usage decision screen and the stock quantities in MMBE against the lot quantity before touching anything else.