ERPClimb logoERPClimb
Login
PP and QM: confirmation, COGI and inspections
SAP Debugging & Root Cause Analysisadvanced

PP and QM: confirmation, COGI and inspections — Concepts and mental models

Full lesson currently free to read · AI practice limits apply separately

Key takeaway

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 — Concepts and mental models Outcome: Correlate order status, BOM, batch, movement and inspection master data.

In this lessonShow sections

Visual overview

PP and QM: confirmation, COGI and inspections: concept evidence mapOriginal editorial vector showing three context-specific checks for functional debugging.ERPCLIMB • SAP DEBUGGING • CONCEPTPP and QM: confirmation, COGI and inspections1. Understand the business boundaryProduction confirmation can trigger goods movement and backflushpostings. A confirmation may be recorded while an associated goodsmovement fails, leaving follow-up errors visible in COGI. The…2. Identify the execution mechanismQM inspection lot creation depends on inspection type, material masterand event. A missing lot, blocked usage decision or stock posting cannotbe diagnosed solely from the UI. Inspect object…3. Choose evidence, not assumptionsTreat reversal and reposting as business-critical physical-stockactions. Record quantity, unit, batch, storage location, movement andinspection status before approving correction; ensure…Educational flow • SAP edition and permissions vary • test in DEV/QA

What this complete series covers

Three-part SAP Debugging learning journey: understand concepts, follow the guided investigation, resolve a realistic case.

Who it is for
Technical developers, functional consultants, support analysts and solution architects.
Prerequisites
Use only synthetic data and approved non-production systems. Some tools are not available in SAP public cloud.
Final outcome
Backflush errors block production or inspection lots do not progress. Learning outcome: Correlate order status, BOM, batch, movement and inspection master data.
  1. Part 1: PP and QM: confirmation, COGI and inspections — Concepts and mental models

    Backflush errors block production or inspection lots do not progress. Learning outcome: Correlate order status, BOM, batch, movement and inspection master data.

  2. Part 2: PP and QM: confirmation, COGI and inspections — Guided debugger and evidence walkthrough

    Backflush errors block production or inspection lots do not progress. Learning outcome: Correlate order status, BOM, batch, movement and inspection master data.

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

    Backflush errors block production or inspection lots do not progress. Learning outcome: Correlate order status, BOM, batch, movement and inspection master data.

System and release assumptions: SAP edition, Basis release, available transactions and authorization vary by system.

Explanation

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 — Concepts and mental models

Outcome: Correlate order status, BOM, batch, movement and inspection master data.

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

Mental models

1. Understand the boundary

Production confirmation can trigger goods movement and backflush postings. A confirmation may be recorded while an associated goods movement fails, leaving follow-up errors visible in COGI. The error queue is a symptom surface; the cause is often stock, batch, movement type or master-data settings.

2. How this investigation works

QM inspection lot creation depends on inspection type, material master and event. A missing lot, blocked usage decision or stock posting cannot be diagnosed solely from the UI. Inspect object status, inspection plan selection, origin and the link to relevant logistics documents.

3. Evidence-based decisions

Treat reversal and reposting as business-critical physical-stock actions. Record quantity, unit, batch, storage location, movement and inspection status before approving correction; ensure successful correction does not duplicate material documents.

Three common false diagnoses

  • 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.

Synthetic evidence

text
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

Diagnostic flow

  1. Inspect production or inspection document status
  2. Compare confirmation, goods movement and inspection settings
  3. Prove correction with safe stock and document checks

Tools

CO03 · COGI · MD04 · QA03 · Inspection status

Check your understanding

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.

Real project scenario

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.

Common mistakes

  • 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.

Best practices

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.

Interview angle

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.

Practice this lesson

Original educational case studies for SAP consultants, not official SAP certification exam questions. Verify product edition and implementation details against the current SAP documentation.

Quick check

0 of 4 questions attempted

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

2. Where do failed automatic goods movements from production confirmations appear?

3. A material in quality inspection stock can't be used. What releases it?

4. A production order can't be released. What should you check first?

Interview questions

1. How do you resolve goods movement errors from production confirmations?

Answer it in your own words first, then compare.

2. Why is no inspection lot created for a goods receipt?

Answer it in your own words first, then compare.

Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.

More lessons in this topic

Related SAP topics