Partial Confirmations and Operation Scrap

Business scenario

Production order 1000060 for 100 EA of FG-2000 runs over two shifts. Shift 1 finishes 60 EA; shift 2 finishes 35 EA and scraps 5 EA with cracked welds.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

1. 01

   Components issued and work starts open in twin

   100 EA of RM-1000 issued to order 1000060 (261).

   Scrap later will mean these components were consumed without producing good output.

2. 02

   Shift 1: partial confirmation of 60 open in twin

   CO11N: 60 EA yield, not final. Order status PCNF (partially confirmed).

   Planners and capacity planning see how much is done; remaining capacity requirement is reduced.

3. 03

   Shift 2 reports 35 good and 5 cracked open in twin

   How should the 5 cracked units be reported?

   Scrap reduces the quantity expected at the next operations and at goods receipt.

4. 04

   Phantom good units open in twin

   Confirming 40 as good tells the next operations and the goods receipt to expect 100 good units. The 5 cracked units show up later as a stock difference.

   It distorts the order's progress, stock and the scrap statistics that quality needs.

5. 05

   Shift 2: final confirmation with scrap open in twin

   35 EA yield + 5 EA scrap, final. Order status CNF. Total good: 95.

   CO14 shows each confirmation with yield and scrap.

6. 06

   Receive the 95 good units open in twin

   95 EA received: 40 → 135. ₹1,14,000 credited to the order.

   The scrapped units never become stock.

7. 07

   Settle the scrap variance open in twin

   ₹1,20,000 debited, ₹1,14,000 credited: ₹6,000 — the cost of 5 scrapped units.

   Separately reported scrap tells management what poor quality cost.

8. 08

   Order complete open in twin

   Two confirmations, 95 good, 5 scrap, variance explained.

   Planned scrap (assembly or operation scrap in master data) would have raised the planned quantity instead.

SAP documents

Stock impact

Accounting impact

Movement type

• 261GI for orderReversal: 262
• 101GR for orderReversal: 102

Reports production progress and losses accurately, so downstream operations, stock and costs reflect what really happened.

Transactions & Fiori apps

Configuration

• Confirmation tolerances

  Configuration dependent

  Under- and over-delivery tolerances and whether partial confirmations are allowed.

• Variance categories

  Configuration dependent

  Scrap variance reported separately (SCRP, typical).

Prerequisites

• Released order
• Scrap reasons (optional)
• Variance key with scrap variance

Master data

Material master / BOM / routing

Planned assembly, component and operation scrap.

Organizational structure

• Plant 1000
• Work center ASSY-01

Tables

Integration

• MMOnly yield is received into stock.
• COScrap variance at settlement.

Common errors

• “Order shows more good units than received”

  Likely causes: Scrap confirmed as yield; GR not posted for the full yield

  Where to look: CO14 · Order goods movements

Troubleshooting

Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

1. CHECK 1

   Quantities

   • Yield vs scrap entered separately?
   • Tolerances?

Interview questions

• What happens when scrap is confirmed on an operation?

  The scrap quantity is recorded separately from yield; following operations and the expected goods receipt are reduced accordingly; the costs consumed for the scrapped units stay on the order and appear as scrap variance in variance calculation.

Quiz

Related processes

• 261 · 101Production Order
• 343Rework Order

References

• SAP SE — SAP Help Portal: Order Confirmation (source)
• SAP SE — SAP Help Portal: Scrap in Production (source)
• SAP SE — SAP Help Portal: Variance Categories (source)

Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

Version history