SAP QM QA32: user exits, enhancements and standard lot reports
sap qm user exits for qa32
Also searched as
- sap qm lot report
- sap qm standard reports
- qa32 enhancement badi
Short answer
QA32 is the inspection lot list. Before writing code, use layout variants, selection variants and the selection profile; if you need extra fields or logic, search for BAdIs or enhancement spots through the enhancement framework rather than modifying standard code. The standard QM reports for lots and results cover most needs.
Applies to: SAP ECC and S/4HANA QM. Available enhancements differ by release, so check your system.
How to approach a QA32 change
- 1Try layout and display variants first, which add or reorder fields without code.
- 2Save selection variants and, if needed, selection profiles to restrict lots per user group.
- 3If a field or logic is missing, use SE80 or SE18/SE19 to search for BAdIs and enhancement spots in the QM package.
- 4Trace the program with the Enhancement Information System or a debugger to find the implicit or explicit enhancement points.
- 5Implement through a BAdI or enhancement implementation, never a direct modification, and transport it normally.
- 6Test with authorisation roles of real users and document the enhancement.
Variants, then enhancement
Most QA32 requests are layout requests. The ALV list lets you choose from available fields, and a saved variant can be assigned as default. Only when the data does not exist in the list structure do you need an enhancement.
Finding the right exit
Legacy customer exits are found with SMOD/CMOD for the QM enhancement packages; newer enhancements are BAdIs found via SE18 and SE19. Use the Enhancement Framework to see implicit enhancement options. Names differ across releases, so search your own system instead of copying one from a forum.
Standard lot and results reports
QA32 lists lots to change, QA33 displays lists, QA03 shows a single lot, and QE51N is used for results review. Inspection history and quality scores come from the QM information system and analytics. For S/4HANA, check the available Fiori apps for inspection lots and results.
QA32 Change inspection lots (list) QA33 Display inspection lots (list) QA03 Display inspection lot QE51N Results recording and display
Try it here, free
SAP QM Inspection Lot Origins Reference
See which business events create inspection lots in SAP QM and what to check when a lot is missing.
Common pitfalls
- !Modifying standard programs instead of using an enhancement.
- !Copying an exit name from a different release.
- !Putting heavy selects into a list enhancement and slowing QA32.
- !Not testing with limited authorisations.
- !Building a custom report when a standard report exists.
How an ERP-grounded AI assistant handles this
An assistant grounded in your SAP system can explain which enhancements already exist in QM and answer lot questions in natural language, read-only. Netray builds this to run on-prem alongside SAP so quality data stays inside your network.
Frequently asked questions
What is QA32 used for?
It is the list for selecting and changing inspection lots, for example to record results, make usage decisions or review status.
Is there a user exit for QA32?
There can be enhancement options, but the right one depends on release. Search SMOD/CMOD and BAdI definitions in your system.
What are the standard SAP QM reports?
Lot lists (QA32/QA33), single lot display (QA03), results (QE51N), plus QM analytics and information system reports.
Can I add custom fields to the QA32 list?
Only fields in the list structure appear through variants. Anything else requires an enhancement.
Related
SAP QM inspection results report: which tcode shows what
Use QA32 for the list of inspection lots, QE51N or QE03 for recorded results, the QM information system (for example QM12) and QGC2 for evaluations of characteristics over time, and QA11 or QAVE for usage decisions. If none fits, read the tables QALS, QAMV, QAMR and QAVE directly.
How-toHow to release (and cancel) an inspection lot in SAP QM
Open the lot in QA02, check the system status, and use the Release function so the status moves from CRTD (created) to REL (released); only then can results be recorded in QE01 and a usage decision made in QA11. To cancel a lot, use the cancel function in QA02, which only works while no usage decision exists and no stock posting blocks it.
How-toSAP QA11 Usage Decision: Make It and Post Stock Correctly
The usage decision (UD) in QA11 closes an inspection lot, assigns a quality score and a UD code such as accepted or rejected, and posts the lot quantity from quality inspection stock to unrestricted use, blocked stock, scrap or return to vendor. The UD is blocked until required inspection characteristics are closed and results are recorded.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI for SAP Quality Management: Notifications, 8D, and CAPA Without the Manual Drafting
AI grounded on SAP QM data that triages notifications, drafts 8D and CAPA reports, and summarizes inspection trends, deployed on-prem for full traceability.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP QM?
Talk to engineers who work inside SAP QM every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP QM Inspection Lot Origins ReferenceSee which business events create inspection lots in SAP QM and what to check when a lot is missing.
- SAP QM Inspection Types ReferenceLook up the standard SAP QM inspection types, what business event triggers each one and what you must set up in the material master and inspection plan.
- SAP QM Implementation Readiness ChecklistCheck master data, integration points, inspection setup and user readiness before cutting over SAP QM.
ERP fixes and how-tos
- SAP PP and MM Enhancement Examples: User Exits, BAdIs and Enhancement SpotsPractical SAP PP and MM enhancement examples: user exits, BAdIs such as ME_PROCESS_PO_CUST and WORKORDER_UPDATE, how to find them and a PO validation sketch.
- Inspection Results and Inspection Plan Reports in SAP QMWhich SAP QM transactions report inspection results and inspection plans? Use QA32, QE03, QGC1 for evaluation and QP19 for plan lists, plus the QM tables behind them.
- SAP QM inspection results report: which tcode shows whatFind inspection results in SAP QM: QA32 lot list, QE51N results worklist, QM12 and QGC2 evaluations, MIC history, and the QALS, QAMR and QAVE tables.