In the high-stakes environment of SAP S/4HANA Manufacturing, the alignment between market demand and production execution is governed by Planning Strategies. As a Senior SAP Solutions Architect, I have observed that the most common point of failure in digital supply chain transformations is not the software itself, but the misalignment of these strategies with the business’s operational reality.
Choosing a planning strategy is a fundamental decision that dictates how Material Requirements Planning (MRP) behaves, how inventory is valued, and how Sales and Distribution (SD) communicates with Production Planning (PP). This guide provides a deep-seated architectural analysis of the four cornerstone strategies 10, 11, 20, and 40, using a dual-layer approach: Executive Analogies to simplify business logic and Technical Consultant Logic to master the underlying S/4HANA configuration.
1. Key Takeaways: Strategic Overview
- Strategy 10 (Make-to-Stock): A purely forecast-driven approach where sales orders consume Planned Independent Requirements (PIRs) based on a net requirements logic to prevent over-ordering.
- Strategy 11 (Gross Requirements Planning): A rigid production model that ignores existing stock and allows forecasts to drive production regardless of actual sales order volume or inventory on hand.
- Strategy 20 (Make-to-Order): A customer-centric, reactive model where production only begins upon receipt of a Sales Order, with costs and inventory directly pegged to that specific order.
- Strategy 40 (Planning with Final Assembly): The most flexible hybrid model, allowing sub-assemblies to be pre-built based on forecasts while the final finished good is only assembled when a sales order is confirmed.
2. Strategy 10: Make-to-Stock (MTS) for Predictable Demand
2.1. Functional Overview and Business Context
Strategy 10 is the standard “Make-to-Stock” approach, designed for industries where demand is stable and lead times must be kept to an absolute minimum. In this model, the production engine is fueled by the forecast, which SAP identifies as Planned Independent Requirements (PIRs).
Executive Analogy
Imagine a toy manufacturer preparing for the holiday season. They build 10,000 units of a standard doll weeks before December because they know the demand is coming. When a retailer places a real order for 1,000 dolls, the manufacturer doesn’t build 1,000 more; they simply take 1,000 away from the 10,000 they already planned or built.
2.2. Technical Consultant Logic
From a technical perspective, Strategy 10 relies on the net requirements calculation.
- Requirement Types: The system uses LSF for the forecast (PIR) and KSL for the sales order.
- Consumption Logic: The sales order consumes the PIR. If you have a PIR of 100 and a sales order for 20 arrives, the “unconsumed” PIR remains 80.
- MRP Behavior: MRP looks at the PIR, then subtracts available Warehouse Stock. If the stock is 50 and the PIR is 100, MRP generates a planned order for 50.
Architectural Warning: While Strategy 10 is excellent for stability, it requires highly accurate forecasting. If the forecast is too high, you accumulate “dead stock”; if it is too low, you face stock-outs because the system will not automatically increase production just because a sales order exceeds the PIR unless the PIR is manually updated.
3. Strategy 11: Gross Requirements Planning (MTS Gross)
3.1. Functional Overview and Business Context
Strategy 11 is a variation of Make-to-Stock that is significantly more aggressive. Known as Gross Requirements Planning, it is used when production must remain decoupled from current inventory levels. This is common in environments where a specific production target must be hit regardless of what is already in the warehouse.
Executive Analogy
Suppose you are a bakery that must produce 500 loaves of bread every morning to satisfy a contractual obligation with local schools. Even if you have 100 loaves left over from yesterday, you still bake 500 new ones today. You ignore the “leftovers” (stock) and the “walk-in customers” (sales orders) when deciding how much to bake.
3.2. Technical Consultant Logic
- Requirement Types: This strategy utilizes BSF (Gross Forecast) and KSL (Sales Order).
- Consumption Logic: Crucially, sales orders do not consume PIRs in Strategy 11.
- MRP Logic: MRP ignores existing stock and actual sales orders when creating production requirements. It plans specifically for the BSF quantity.
Pro-Tip: This strategy is high-risk for overstocking. It is typically reserved for seasonal builds or for materials with very long production cycles where the shop floor needs a “frozen” plan that cannot be disturbed by the day-to-day fluctuations of the sales department.
4. Strategy 20: Make-to-Order (MTO) for Customization
4.1. Functional Overview and Business Context
Strategy 20 represents a purely reactive business model. Production is triggered exclusively by a customer’s purchase. There is no forecasting (PIR) at the finished good level. This eliminates inventory holding costs for finished products but places the burden of the lead time on the customer.
Executive Analogy
Think of a custom treehouse builder. They don’t have finished treehouses sitting in a lot waiting for buyers. They wait for a family to knock on the door, sign a contract, and specify the dimensions. Only then do they buy the wood and start the construction.
4.2. Technical Consultant Logic
- Requirement Type: The Sales Order is assigned Requirement Type S40.
- Pegging: There is a strict 1-to-1 relationship. The Sales Order number is actually stamped onto the Production Order and the resulting stock. This stock is “special stock” (E) and cannot be sold to another customer without manual re-posting.
- Costing Logic: This is the most significant departure from MTS strategies. Strategy 20 uses Sales-Order-Specific Costing. Instead of standard price variances, all costs (materials, labor, overhead) are settled directly to the sales order, allowing for precise profitability analysis of every individual customer deal.
5. Strategy 40: Planning with Final Assembly (The Hybrid Model)
5.1. Functional Overview and Business Context
Strategy 40 is the “Gold Standard” for modern manufacturing. It allows for a hybrid approach: you forecast and produce the core components (Semi-Finished Goods or SFGs) to save time, but you wait for the Sales Order to perform the final assembly (Finished Good or FG).
Executive Analogy
Imagine a computer manufacturer. They build hundreds of “base” laptop bodies with motherboards and screens (SFGs) based on their sales forecast. However, they don’t put in the RAM, the Hard Drive, or the Keyboard (Final Assembly) until a customer chooses their specific configuration. This allows them to ship a “custom” laptop in 24 hours instead of two weeks.
5.2. Technical Consultant Logic
- Requirement Types: Uses VSF (Forecast) and KSV (Sales order with consumption).
- MRP Reaction: When a sales order (KSV) is entered, it consumes the VSF. MRP then creates a planned order for the final assembly of the FG.
- SFG Stock Logic: One of the most common questions from consultants is: “Do all SFGs need to be in stock for Strategy 40 to work?” The answer is no. If the SFGs are missing, the MRP run for the FG will simply explode the Bill of Materials (BOM) and create the necessary planned orders for the missing components.
6. The Architectural Bridge: Requirement Transfer and SD-PP Integration
The most critical technical link in the SAP ecosystem is Requirement Transfer. This is the process that allows a Sales Order created in the SD module (VA01) to “talk” to the Production Planning module and appear in the Stock/Requirements List (MD04).
6.1. The Configuration Chain
To understand why a sales order behaves the way it does, one must follow the configuration path in the IMG (Implementation Guide):
- Material Master: The material is assigned a Strategy Group (e.g., 40).
- Strategy: The Strategy Group points to a Main Planning Strategy.
- Requirement Type: The Planning Strategy defines the Requirement Type (e.g., KSV).
- Requirement Class: The Requirement Type is linked to a Requirement Class.
The Requirement Class is the “brain” of the operation. It contains the “Transfer of Requirements” flag. If this flag is unchecked, the Sales Order will be invisible to MRP. It also controls whether an “Availability Check” (ATP) is performed and how the costs are settled.
| Requirement Type | Meaning | MD04 Visibility | Strategy |
| VSF | Forecast for final assembly | Visible as independent demand | 40 |
| KSV | Sales order with consumption | Visible as customer demand | 40 |
| LSF | Forecast for MTS | Visible as independent demand | 10 |
| KSL | Sales order without PIR reduction | Visible as customer demand | 10, 11 |
| BSF | Gross forecast | Visible as gross demand | 11 |
| S40 | MTO sales order | Visible as individual customer demand | 20 |
7. MRP Flow and Costing Architecture
7.1. Detailed MRP Flow Analysis
In a live S/4HANA system, the state of the MD04 list changes dynamically based on the chosen strategy.
- Strategy 10/40 Flow: Initially, MD04 shows only the VSF (or LSF) line and the resulting Planned Orders. When a Sales Order is created, the VSF quantity decreases and a KSV line appears. MRP does not create new supply; it merely recognizes that the existing supply is now pegged to a real order.
- Strategy 20 Flow: MD04 is empty until the Sales Order is saved. Once saved, a S40 requirement appears. MRP immediately generates a Planned Order that is uniquely tied to that Sales Order number.
7.2. Financial Integration: The S/4HANA Costing Path
Costing in S/4HANA is not just about the “price tag”. It is about how variances are captured.
- Standard Costing (Strategies 10, 11, 40): Organizations use CK11N to calculate the cost and CK24 to release it. Any difference between the standard price and the actual production cost is posted to a price difference account during production order settlement (CO88).
- Sales-Order Costing (Strategy 20): Here, the production order captures actual costs which are then settled to the Sales Order. This is essential for high-value machinery where every nut and bolt must be tracked against the customer’s budget.
8. Technical Simulation: From MD61 to Production Order
To visualize the lifecycle of a requirement in a Strategy 40 environment, follow this 8-step simulation:
- Demand Entry (MD61): Create a forecast (VSF) for 100 units.
- Audit (MD04): You see a line for VSF with a quantity of 100.
- Supply Generation (MD02): Run MRP. The system generates Planned Orders to fulfill the 100 units.
- Financial Prep (CK11N/CK24): The Architect ensures the standard cost is released so that the production orders have a baseline for variance calculation.
- Sales Intake (VA01): A customer orders 30 units. The system assigns Requirement Type KSV.
- Requirement Transfer: Because the Requirement Class has the “Transfer” flag active, the 30 units appear in MD04 instantly.
- Consumption Observation: In MD04, you will now see the VSF has reduced to 70, and the KSV shows 30. The total requirement remains 100.
- Conversion (CO41): The planner uses CO41 for mass conversion. The Planned Order for 30 is converted into a Production Order for the final assembly.
9. Advanced Troubleshooting: Solving the /SCDL/DL_DBAL_ERROR 024
In advanced S/4HANA environments integrated with EWM (Extended Warehouse Management), you may encounter the error /SCDL/DL_DBAL_ERROR 024. This is a frequent “go-live” blocker related to the Number Range Architecture.
9.1. Error Diagnostics
This error typically surfaces during the creation of deliveries or warehouse tasks. It indicates that the system is trying to assign a document number but finds the number range interval missing or improperly configured in the backend database.
9.2. Resolution Path
- Identify Object: Open transaction SNRO and enter Object /SCDL/PRD.
- Maintain Intervals: Navigate to the “Intervals” maintenance screen.
- Check Interval 02: Ensure that Interval 02 exists.
- Internal Assignment: Confirm that the interval is set to Internal. If it is set to external and no number is provided by the interface, the error will persist.
- EWM Customizing: Cross-reference the EWM number range assignments to ensure that the document type (e.g., Inbound Delivery or Outbound Delivery Order) is specifically mapped to Interval 02.
10. Strategic Summary and FAQ
10.1. Master Strategy Comparison Table
| Strategy | Forecast Necessity | Sales Order Impact | Consumption | Costing Behavior | Industry Standard |
| 10 | High | Low (consumes PIR) | Yes | Standard Cost | FMCG / Food |
| 11 | Critical | None (gross plan) | No | Standard Cost | Seasonal / Pharma |
| 20 | None | Critical (triggers MRP) | N/A | Sales-Order Costing | Special Machinery |
| 40 | High | High (triggers assembly) | Yes | Std + Actual Final | Auto / Tech |
10.2. Frequently Asked Questions (FAQ)
Q: Can Strategy 40 work if I don’t have the sub-components in stock? A: Absolutely. While Strategy 40 is designed to leverage pre-built SFGs, if they are not available, MRP will simply create new requirements (Purchase Requisitions or Planned Orders) for those components when the Sales Order triggers the final assembly requirement.
Q: Why does Strategy 11 ignore stock? A: Strategy 11 is used when the production plan is “sacrosanct.” For example, in some chemical processes, you must run a full batch regardless of current inventory to maintain machine efficiency or meet a minimum gross production volume.
: Does the “Requirement Transfer” happen in real-time? A: Yes. As soon as a Sales Order is saved in VA01, the integration via the Requirement Class ensures the demand is visible in the Stock/Requirements List (MD04).
Q: What happens if a Sales Order is cancelled in Strategy 20? A: Since Strategy 20 is MTO, the production order and any special stock are tied to that order. If cancelled, the stock remains in “Sales Order Stock” (Status E). You must manually move it to “Unrestricted Stock” via a 411 E movement type if you wish to sell it to someone else.
Q: Is it possible to change a strategy after production has started? A: It is technically possible in the Material Master, but it is architecturally dangerous. Changing a strategy (e.g., 10 to 20) while active orders exist can lead to “orphaned” requirements in MD04 and significant reconciliation issues in Financial Accounting.
11. Conclusion
Mastering SAP S/4HANA Planning Strategies requires more than just knowing T-codes; it requires an architectural understanding of how demand flows from a customer’s click to the factory floor. By choosing the correct strategy, whether it’s the predictable flow of Strategy 10, the rigid targets of Strategy 11, the custom precision of Strategy 20, or the hybrid agility of Strategy 40, enterprises can achieve the ultimate goal: a lean, responsive, and profitable supply chain.
