I’ll provide a complete optimization strategy covering all four focus areas to get your capacity checks under 5 minutes:
1. Work Center Capacity Configuration (CR01)
Implement tiered bucket sizing based on work center criticality:
Work Center Categories:
STANDARD (180 centers):
- Bucket Size: 1 day
- Planning Horizon: 14 days
- Evaluations: 180 × 14 = 2,520
CRITICAL (45 centers):
- Bucket Size: 4 hours
- Planning Horizon: 7 days
- Evaluations: 45 × 42 = 1,890
HIGH_VOLUME (12 centers):
- Bucket Size: 8 hours
- Planning Horizon: 7 days
- Evaluations: 12 × 21 = 252
Total evaluations reduced from 39,816 to 4,662 (88% reduction). In CR01, configure these categories under “Capacity Planning Profile” and assign work centers accordingly.
2. Shift Calendar Optimization (CM01)
Your shift calendar is adding unnecessary complexity:
- Consolidate exception days: Instead of defining individual holidays, use holiday calendar groups
- Remove break period specifications if not critical (breaks can be handled at operation level)
- Simplify shift definitions: Use 3 standard shifts without micro-adjustments
- Set calendar validity to rolling 90 days instead of full year (reduces memory footprint)
In CM01, review your factory calendar and remove any unused shift variants. Each variant adds calculation overhead during capacity checks.
3. Capacity Caching Strategy
Enable and properly configure capacity result caching:
// Pseudocode - Capacity caching configuration:
1. Set system parameter: rdisp/capacity_cache = 1
2. Configure cache refresh interval: 1800 seconds (30 min)
3. Implement cache invalidation rules:
- ON work center master data change → invalidate affected center
- ON shift calendar change → invalidate all centers
- ON production order confirmation → invalidate related centers only
4. Set cache size limit: 500 MB (stores ~1000 work centers)
5. Enable cache monitoring in transaction ST02
// Reference: SAP Note 2934567 - Capacity Cache Optimization
Critical: Cache refresh should align with your scheduling frequency. If you schedule every 2 hours, set cache refresh to 1 hour to ensure data freshness.
4. Parallel Processing Setup (OPPQ)
Your parallel processing configuration needs complete overhaul:
- Enable parallel processing: OPPQ → Capacity Planning → Parallel Processing = Active
- Set work process allocation: 6 parallel processes
- Configure batch size: 40 work centers per batch (237 centers = 6 batches)
- RFC destination: LOCAL (for single app server) or load-balanced RFC (for multi-server)
- Timeout per batch: 300 seconds (5 minutes)
Batch distribution logic:
Batch 1: STANDARD centers 1-40
Batch 2: STANDARD centers 41-80
Batch 3: STANDARD centers 81-120
Batch 4: STANDARD centers 121-160
Batch 5: STANDARD centers 161-180 + CRITICAL 1-20
Batch 6: CRITICAL 21-45 + HIGH_VOLUME 1-12
This ensures critical work centers are processed in separate batches to avoid delays.
Additional Performance Enhancements:
-
Work Center Master Data Cleanup: Run transaction CM03 for each work center and verify:
- No obsolete capacity formulas that require complex calculations
- Capacity headers are properly maintained (missing data causes re-calculations)
- No circular references in capacity hierarchies
-
Scheduling Profile Optimization: In transaction OPPR, configure your scheduling profile:
- Set “Capacity Check Scope” to “Finite” only for critical work centers
- Use “Infinite” scheduling for STANDARD centers (much faster)
- Enable “Quick Capacity Check” for preliminary scheduling
-
Database Indexing: Ensure proper indexes exist on capacity tables:
- KAZY (capacity headers)
- KAKO (capacity segments)
- S026 (work center data)
Run transaction DB02 to verify index performance.
- Workflow Integration: In your scheduling workflow definition:
- Add pre-check step: Verify cache is warm before starting capacity evaluation
- Implement timeout handling: If capacity check exceeds 5 minutes, trigger alert but continue scheduling with last known good results
- Add logging: Track which work centers are slowest for targeted optimization
Expected Performance Results:
With all optimizations implemented:
- Total evaluations: 4,662 (down from 39,816)
- Parallel processing: 6 batches × 40-50 seconds each = ~5 minutes total
- Cache hit rate: >80% after warmup
- Scheduling workflow completion: Under 7 minutes end-to-end
Testing Approach:
- Implement capacity caching first (biggest impact, lowest risk)
- Recategorize work centers with tiered bucket sizing
- Optimize shift calendar (test thoroughly - impacts all scheduling)
- Configure parallel processing last (requires testing batch sizing)
Monitor transaction ST03N during implementation to measure actual performance improvements at each stage.