How to Set Up Collective Confirmations in SAP Repetitive Manufacturing

Master Your Production Flow with Smart Confirmation Timing

Let’s Talk About Collective Confirmations - Why They Matter

If you’ve ever found yourself wondering why your SAP system slows down during confirmations or why some post-production processes feel sluggish, the answer may lie in how your collective confirmations are configured.

In SAP Repetitive Manufacturing, collective confirmations are a behind-the-scenes hero. They govern when crucial processes like backflushing, goods receipt, and cost determination happen after confirming a production order. Set them up right, and your system hums. Get them wrong, and performance can nosedive, especially in high-volume environments.

Now, you might be thinking: “How exactly do I control when these things run?” Let’s walk through it together.

Where to Configure: Step-by-Step in SPRO

To access the settings, hop into the SAP GUI and go to:

TCode: SPRO 

  • Production 
  • Shop Floor Control 
  • Confirmation 
  • Define Time for Confirmation Processes
This is where the magic happens. You’ll be able to control when SAP executes key confirmation-related processes—either instantly, shortly after, or later in the background.

What You Can Control Here (And Why It Matters)

In this configuration screen, you’ll be defining the execution timing for the following processes:
  • Automatic Goods Receipt
  • Component Backflushing
  • Actual Cost Calculation
Each can be scheduled using three execution options:
  • Immediately Online - Happens instantly during confirmation (real-time, but can slow down users).
  • Immediately as Update - Runs right after confirmation (less disruptive but still immediate).
  • Later in Background - Offloaded to a background job (ideal for performance in large-scale ops).
Default SAP behavior: All processes run online. But here's the thing, this setup isn’t ideal if you’re running a large shop floor or pushing high transaction volumes.

Let’s Optimize: Creating Control Keys That Work for You

To make SAP confirmations more efficient, you’ll want to create a control key that defines exactly how each process runs.

Here’s how to do it:

  1. Create a Custom Control Key

    2. Assign execution timing to each process.
    Set the correct order category: 
    • 10 = Production Order
    • 20 = Network
    • 30 = Maintenance Order
    • 40 = Process Order
  2. Assign the Control Key to Your Order Type

    3. Go to the confirmation parameters for your specific order type.
    Plug the control key into the Process Control field. 
  3. Enable Parallel Processing

    4. If you want some tasks to run in parallel (and you should, for speed), define a parallelization type. 
  4. Schedule the Background Job

    5. Program: CORUPROC
    Set this up in transaction SM36.
    Create different variants if you want to split confirmations by process (like one for goods receipt, one for backflush). 

Real-World Insight: Why Background Jobs Are Game-Changers

Running everything online might seem simpler, but when your system is choking under load, that simplicity becomes a bottleneck.

Here’s a quick comparison:

Scenario Online Execution Background Execution
Performance Slower under load Much faster
User Experience Delays during confirmations Smooth and responsive
Flexibility Limited control Fully customizable

Pro Tip: Don’t Forget to Test

After implementing control keys and background jobs, always run test orders in a sandbox. Check that:
  • All confirmations execute as expected
  • Jobs finish successfully (no dumps!)
  • Posting logic aligns with your financial and logistics flows

Final Thoughts

Getting collective confirmations right in SAP isn’t just a “tech thing”, it’s a strategic move. With just a few configuration tweaks, you can:
  • Reduce system load
  • Speed up production order confirmations
  • Improve user experience on the floor
  • Enhance data consistency and processing reliability
If you're serious about optimizing repetitive manufacturing, this setup is non-negotiable.

FAQ

Q: What is the purpose of control keys in SAP confirmations?
A: Control keys define when processes like backflushing, goods receipt, and cost calculation run, either instantly, as updates, or in the background.

Q: What does CORUPROC do in SAP?
A: CORUPROC is the background job program that processes deferred confirmation tasks based on your control key settings.

Q: Can I improve SAP performance with background jobs?
A: Absolutely. Moving heavy processes like cost calculation or component backflushing to background execution reduces online processing time and improves performance.

Read Also:
Control Regular Entry for Material Consumption

Goto:
SAP MRP - Materials Requirements Planning Configuration Hints and Tips 

Back to:
SAP PP (Production Planning) Configuration Hints and Tips

Return to :-
SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips

(c) www.gotothings.com All material on this site is Copyright.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
All product names are trademarks of their respective companies.  The site www.gotothings.com is in no way affiliated with SAP AG.
Any unauthorised copying or mirroring is prohibited.