QA07 — Deadline Monitoring of Inspection Lots
QA07 is used to monitor time-related inspection processing such as recurring inspection deadlines and trigger follow-up lot processing. It is most useful when quality teams manage materials that require inspection at defined intervals or dates. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
This ERPClimb practitioner page covers QA07 — Deadline Monitoring of Inspection Lots. It focuses on the transaction's real operational role, the parameters that matter, the evidence needed to diagnose problems, S/4HANA context, and the mistakes that cause most support rework.
Published 19 Sept 2026· 614 words
Esta página aún no está disponible en español.
Purpose
monitor time-related inspection processing such as recurring inspection deadlines and trigger follow-up lot processing. QA07 is most useful when treated as part of an end-to-end process rather than a shortcut. The object status you see here is usually influenced by upstream master data, configuration, planning or document history, so capture those inputs before changing anything.
When it is used
QA07 is typically used when quality teams manage materials that require inspection at defined intervals or dates. It is also valuable during project testing because it exposes a repeatable state that can be compared before and after configuration or master-data changes. In production, narrow the population first and distinguish display/analysis from actions that post, approve, replicate or change status.
How to use it in practice
- Select the intended plant/material population.
- Review lots or batches approaching the inspection deadline.
- Confirm inspection-type/master-data setup.
- Execute only the intended deadline processing.
- Verify resulting inspection lot and stock status.
Key data objects
These are the most useful anchors when working in QA07. Capture them in screenshots, test evidence and incident handovers so another consultant can reproduce the same result and identify whether the issue is data, configuration, status or integration.
- material/batch — verify the exact value, validity/date context and relationship to the affected process.
- inspection lot — verify the exact value, validity/date context and relationship to the affected process.
- inspection date — verify the exact value, validity/date context and relationship to the affected process.
- inspection type — verify the exact value, validity/date context and relationship to the affected process.
- stock/lot status — verify the exact value, validity/date context and relationship to the affected process.
How to prove it in the data
Build an evidence chain rather than relying on one message: identify the source requirement or master record, show the transaction status or worklist entry, then show the resulting document, posting, warehouse object, planning element or replication log. Use the same date and organizational scope throughout. That makes the diagnosis repeatable and separates a true fix from a coincidental retry.
ECC vs S/4HANA
Recurring/deadline inspection remains part of S/4HANA QM where batch and quality processes require it. Where a Fiori app or cloud service becomes the strategic user experience, the SAP GUI transaction can still remain valuable for support, migration and deep technical analysis, but it should not be used to justify a legacy design for new work.
Common pitfalls and how to diagnose them
- Running deadline processing broadly without checking batch/material scope. Return to the exact object status and chronology before applying a workaround.
- Changing dates to suppress overdue inspection instead of addressing it. Return to the exact object status and chronology before applying a workaround.
- Ignoring stock movement consequences after a new inspection lot is created. Return to the exact object status and chronology before applying a workaround.
Whose problem this is
Primary ownership is the QM team, with adjacent functional, Basis, Security or integration teams joining when the evidence crosses system boundaries. Escalate with the object/document number, organization, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/qa07ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.