PP and QM: confirmation, COGI and inspections — Root-cause case, remediation and assessment

Training simulation: All sample identifiers, logs, requests, transactions, values and cases are fictional. Tools and permissions vary by SAP release; perform any changes only in approved DEV/QA environments.

PP and QM: confirmation, COGI and inspections — Root-cause case, remediation and assessment

Incident: Backflush errors block production or inspection lots do not progress.

Landscape: ECC/S/4HANA PP production orders, confirmation, COGI and QM inspection processing; Fiori alternatives depend on edition.

Fictional incident dossier

Order DEMO-PP-770 | confirmed 5 EABackflush component COMP-A: 10 EA requiredAvailable unrestricted stock: 7 EACOGI: deficit 3 EA; movement 261 pendingQM lot for finished good: created, status not UD

Evidence observations

1. Required 10 EA exceeds available 7 EA, explaining the posting deficit of 3 EA.
2. Confirmation status does not prove a 261 movement was successfully posted.
3. The inspection lot exists; if the usage decision is pending, that is a distinct step from the component deficit.

Three hypotheses

1. Insufficient unrestricted component stock prevents backflush movement.
2. Incorrect batch/storage location or movement determination produces a posting error.
3. QM inspection setup or plan selection blocks lot progression.

Supported: 1.

Evidence-backed root cause

The sample component movement requires 10 EA when 7 EA are available. COGI records an unposted 261 movement; the separate QM lot still awaits its own inspection completion.

Safe remediation

Reconcile physical stock and reservation, obtain approved replenishment or correction, then safely post only the outstanding movement; process QM status independently.

Diagnostic runbook

1. Open production order, confirmation and goods movement overview; confirm whether confirmation posted independently.
2. Inspect COGI item details: material, movement 261, required/available quantity, batch and storage location.
3. Check BOM/component quantity, backflush indicator, stock type, posting period and reservation data.
4. For QM downstream, review inspection lot origin, plan, sample and user status before deciding whether UD should be possible.
5. Resolve stock or production master data through approved process in DEV/test; correct/reprocess the specific pending movement once.
6. Reconcile component movement, production order costs and inspection lot status, then test an insufficient-stock case.

Confirm resolution

• Positive: Adequate stock and correct batch post expected component consumption once.
• Negative: Insufficient stock continues to produce a controlled error without negative phantom stock.
• Cross-process: Order costs, goods movement and inspection-status figures reconcile after correction.

Assessment

Question: Production order confirmation is saved but component 261 posting is pending in COGI. What is the first investigation?

A. Check required/available stock, batch and movement error.
B. Delete the production order.
C. Force a QM usage decision.

Correct: A. Backflush goods movement is a distinct posting step; COGI evidence narrows its problem.

Safety: Never create dummy stock, mass-reprocess COGI, force usage decisions or bypass warehouse/quality approvals to clear queues.

Synthetic case: Backflush errors block production or inspection lots do not progress.

The sample component movement requires 10 EA when 7 EA are available. COGI records an unposted 261 movement; the separate QM lot still awaits its own inspection completion.

• A successfully saved confirmation can coexist with failed backflush movement.
• COGI entry does not prove stock should be moved without material/valuation review.
• A missing inspection lot can reflect inactive inspection setup, not ABAP runtime failure.

Reconcile physical stock and reservation, obtain approved replenishment or correction, then safely post only the outstanding movement; process QM status independently.

• Positive: Adequate stock and correct batch post expected component consumption once.
• Negative: Insufficient stock continues to produce a controlled error without negative phantom stock.
• Cross-process: Order costs, goods movement and inspection-status figures reconcile after correction.

Never create dummy stock, mass-reprocess COGI, force usage decisions or bypass warehouse/quality approvals to clear queues.

Manufacturing debugging: backflush and goods movement errors (COGI), confirmation issues, missing components, inspection lot creation and usage decisions, and how production and quality statuses block processes.