Why train Inspect-to-Release as an end-to-end process?

Because the user-facing step depends on upstream master data, status, integration and period-end controls.

What should support check first when the process fails?

Start with the source document, status, log, master data and authorization before changing configuration.

QM · Quality Management

Inspect-to-Release SAP S/4HANA training

Control inspection lots from creation through result recording, usage decision and stock posting.

Přehled procesu a business kontext

Inspect-to-Release ensures that materials and production outputs meet quality requirements before unrestricted use or customer delivery.

Learners can explain inspection lot creation, results recording, defects, usage decision and follow-up stock postings.

End-to-end tok

1
Create inspection lot
QA01 / Automatic
Fiori aplikace: Manage Inspection Lots
Dopad na ACDOCA: No finance posting; controls quality stock.
2
Record results
QE51N
Fiori aplikace: Record Inspection Results
Dopad na ACDOCA: Captures measured values and acceptance.
3
Record defects
QM01
Fiori aplikace: Manage Quality Notifications
Dopad na ACDOCA: Documents nonconformance and follow-up tasks.
4
Make usage decision
QA11
Fiori aplikace: Make Usage Decision
Dopad na ACDOCA: Releases or blocks quantity and can trigger stock posting.
5
Post follow-up action
QA11 / MIGO
Fiori aplikace: Stock Posting
Dopad na ACDOCA: Moves stock to unrestricted, blocked, scrap or return flow.

Klíčové tabulky

Table	Vysvětlení
QALS	Inspection lot header data.
QAMV	Inspection characteristics and specification data.
QAMR	Recorded inspection results.
QMEL	Quality notification data for defects and complaints.
MSEG / MATDOC	Inventory postings following usage decision.

Postup krok za krokem

Check lot origin

Confirm whether the lot came from goods receipt, production, delivery or manual creation.

Na co si dát pozor: Different origins drive different stock and process effects.

Record complete results

Enter required characteristics, samples and valuation before decision.

Na co si dát pozor: Incomplete results can block usage decision.

Use defects for learning

Create notifications when failure needs root-cause action.

Na co si dát pozor: Skipping defect data hides supplier or production trends.

Decide and post stock

Make usage decision and confirm stock posting proposal.

Na co si dát pozor: Usage decision is a controlled quality release, not just a click.

Běžné chyby a řešení problémů

Usage decision is blocked

Pravděpodobná příčina: Required characteristics are incomplete or rejected.

Postup opravy: Review result recording and characteristic status.

Stock does not move after decision

Pravděpodobná příčina: Stock posting proposal was not accepted or posting failed.

Postup opravy: Check UD stock tab and material document log.

Inspection lot not created

Pravděpodobná příčina: Inspection setup in material master or procurement/production trigger is missing.

Postup opravy: Check QM view and inspection type activation.

Rozdíly ECC a S/4HANA

S/4HANA keeps the inspection-lot lifecycle but improves role-based processing, analytics and integration with purchasing, production and inventory.

Slovník

Inspection lot: Quality object that groups inspection requirements and quantities.
Characteristic: Measured or evaluated quality requirement.
Usage decision: Final decision that accepts, rejects or routes inspected quantity.
Quality notification: Record for defect, complaint or corrective action.

Knowledge check

Pro odemknutí certifikátu dokončete quiz alespoň na 70 %.

Spustit generátor