Name: leverX Company
Brand: LeverX
Rating: 4.9 (114 reviews)

What changes in SAP S/4HANA when you produce chemicals instead of machinery? Compare the capabilities each production model needs, and see how they work together in plants that use both.

Discrete and process manufacturers cannot rely on an identical set of ERP functions. A system designed around component assembly cannot fully account for production in which ingredients change during processing and the resulting batches may vary. Applying the same production logic to both can distort planned output and lead to delivery commitments the plant cannot meet.

Therefore, these different ways of working require different support from an ERP. SAP S/4HANA supports discrete and process manufacturing through different production workflows. Understanding how they differ helps explain what each type of enterprise can expect from the system in daily work.

TL;DR

SAP S/4HANA manages component assembly differently from mixing or processing ingredients. Each production method needs its own workflows.
Both manufacturing types use bills of materials and quality checks. What changes is how SAP connects them with production.
Discrete manufacturing typically uses SAP PP with production orders, BOMs, and routings. Process manufacturing commonly uses PP-PI with process orders, master recipes, and phases. The production scenario determines the approach; some process manufacturers also use production orders.
Ingredient strength can vary between batches, changing the amount needed. SAP can adjust quantities using recorded batch properties and calculation rules.
Batch tracking helps identify affected products when a quality problem appears. Discrete manufacturers may also need it for purchased components.
Producing several products in one run requires rules for sharing production costs between them.
A company can run both manufacturing types in one SAP system and track materials as they move between production stages.

The Main Differences at a Glance

Discrete manufacturing produces identifiable items through activities such as machining, assembly, and testing. Typical examples include machinery, vehicles, electronics, and medical devices.

Process manufacturing transforms ingredients through mixing, blending, heating, fermentation, or chemical reactions. Food, beverages, pharmaceuticals, and chemicals often follow this model.

However, the production method matters more than the industry label. A life sciences company may manufacture a chemical formulation, assemble a delivery device, or do both. Even within one plant, different stages can require different forms of production control. SAP's overview of production types includes batch-oriented electronics among the uses for process orders. Some process-industry scenarios also use production orders, as SAP's documented manufacturing scenarios show. The operational requirements determine the order design.

The table below compares typical order-based designs. Batch management, serial numbers, and quality controls can apply across both environments; their use depends on the product and process.

Design area	Discrete manufacturing	Process manufacturing
Product and inputs	BOM with parts, assemblies, and required quantities	BOM with ingredients and outputs, used with a master recipe
Production steps	Routing with operations such as machining, assembly, and testing	Master recipe with operations and phases such as charging, mixing, heating, and sampling
Capacity model	Work centers representing machines, lines, or teams	Resources representing vessels, processing equipment, lines, or other production capacity
Execution document	Production order for a defined quantity	Process order for a defined production run
Traceability emphasis	Component history, production lots, and serial numbers where required	Ingredient and output batches, their properties, and their relationships
Quality emphasis	Component, operation, and finished-product inspections	Ingredient, in-process, and finished-batch inspections
Cost analysis	Material consumption and production activities, commonly analyzed by order	Material consumption and production activities, with cost allocation across multiple outputs where applicable

Discrete manufacturers can also use repetitive manufacturing, where production is managed by quantities and periods rather than individual production orders. The comparison here focuses on order-based workflows; a plant producing standardized items repeatedly may need a different execution design.

How SAP S/4HANA Supports Each Stage of Discrete and Process Manufacturing

The differences between discrete and process manufacturing carry through the production cycle. The sections below compare how SAP S/4HANA handles each stage, explaining which functions manufacturers share and where their production methods require different capabilities.

1. Defining the product and production process

SAP S/4HANA uses production data to calculate material requirements and organize the work. Both manufacturing types use bills of materials (BOMs). The main difference concerns how the system describes the production steps.

Discrete manufacturing	Process manufacturing
Product composition
The BOM specifies components and quantities, such as the motor and seals required for a pump.	The BOM specifies ingredients and quantities. It can also include additional outputs obtained during processing.
Production method
A routing defines operations such as machining, assembly, and testing. Work centers provide the associated capacity and costing data.	A master recipe defines operations and detailed steps called phases. Resources represent the equipment used, such as mixing vessels.
Alternative methods
Production versions connect the appropriate BOM with a routing, for example when different assembly lines manufacture the same product.	Production versions connect the BOM with the appropriate master recipe, allowing production methods to differ by equipment or quantity range.

These differences affect implementation work. An assembly plant needs reliable component quantities and operation times. A process plant also needs recipe phases and resource data that reflect how ingredients are handled. Missing or inaccurate production data can leave material and capacity calculations unreliable even when the order type is correct.

2. Calculating material requirements

Material Requirements Planning (MRP) calculates supply requirements in both environments. Process manufacturing may require additional calculations when ingredient properties affect the quantity needed.

Discrete manufacturing	Process manufacturing
Component requirements: SAP calculates quantities from the BOM and planned output. An illustrative order for 100 pumps, each requiring one motor, generates a requirement for 100 motors.	Ingredient requirements: SAP calculates quantities from the BOM. Material quantity calculation can additionally apply formulas where quantities depend on ingredient properties or processing relationships.
Availability checks: Checks identify component shortages for the planned order, helping planners establish whether materials can support production.	Batch-dependent calculations: With active ingredient management and suitable batch data configured, calculations can account for concentration. A lower concentration may increase the quantity required from the selected batch.

Formula-based calculations require maintained rules and measured material properties. For example, material quantity calculation can adjust quantities in a master recipe or process order. Ordinary MRP does not automatically recalculate every ingredient requirement from the properties of the batch later selected for production.

Selecting the right ingredient batch is another part of preparation. Batch determination can find batches that meet configured selection criteria, such as a required material characteristic. Selection and sorting rules can also account for shelf-life information. These functions support both production and process orders. For implementation, the team needs agreed selection rules and reliable batch characteristics; testing then checks whether the system selects suitable batches and handles shortages as intended.

3. Scheduling equipment and production time

SAP must account for the capacity occupied by production. The scheduling functions can serve both manufacturing types, while the equipment constraints represented in the system differ.

Discrete manufacturing	Process manufacturing
Capacity requirements: Routing operations create workload at work centers. A pump plant can account for assembly time and the capacity of a shared test station.	Capacity requirements: Recipe phases create workload at resources. Vessel occupancy can include processing and cleaning activities maintained in the production model.
Detailed scheduling: SAP PP/DS can schedule operations against finite capacity, helping resolve competition for machines or stations.	Production sequence: SAP PP/DS can also consider sequence-dependent changeover times. Configured setup matrices can represent different cleaning durations between product groups. The equipment and setup activities must be configured for this scheduling logic in PP/DS.

SAP PP/DS supports advanced planning and scheduling, including embedded use in SAP S/4HANA On-Premise and SAP Cloud ERP Private. Availability and licensing need to be confirmed for the target landscape. The system needs the relevant capacity and changeover data to represent these constraints.

4. Executing production and recording progress

Manufacturing orders connect planned work with actual production results. SAP uses different order structures to record assembly progress and the outcome of processing steps.

Discrete manufacturing	Process manufacturing
Order types
Production orders organize the manufacture of a specified quantity using the selected component requirements and routing.	Process orders organize a production run using the selected ingredients and master recipe, including its operations and phases.
Progress reporting
Operation confirmations record completed quantities, scrap, and rework. Actual times support progress monitoring and activity costing.	Phase confirmations record output and losses at processing steps, together with actual times. This helps identify where yield or duration differed from the plan.
Detailed execution
Integrated SAP Digital Manufacturing can guide assembly activities and capture component information or nonconformances.	SAP Digital Manufacturing can provide recipe-based instructions and collect execution data. In SAP S/4HANA On-Premise and SAP Cloud ERP Private, classic PP-PI process management also supports control recipes for configured PI sheets or external systems.

SAP Digital Manufacturing provides an additional execution layer and requires the relevant integration. Equipment connections require their own configuration.

Classic PI sheets provide operator instructions within PP-PI process management. They are a different execution approach from SAP Digital Manufacturing, so the project design needs to establish which system guides operators and records each production step.

5. Inspecting output and tracing quality issues

SAP Quality Management (QM) supports both manufacturing types. Differences arise in what the company inspects and how it traces affected products when a problem occurs.

Discrete manufacturing	Process manufacturing
Inspections
SAP QM can support component and finished-product inspections. For a pump, acceptance may depend on a performance test. Inspection decisions can determine the subsequent treatment of stock.	SAP QM can support ingredient and finished-batch inspections. A coating batch may remain in quality inspection stock pending laboratory results and the relevant usage decision.
Traceability
Batch management can trace batch-managed components. Where individual-unit history is required, serialized execution capabilities can capture component serial numbers and related production information.	Batch management connects ingredient batches with output batches through recorded consumption and receipts. The batch where-used list helps identify which finished batches may be affected by an ingredient problem.

Traceability depends on the identifiers and material movements recorded during production. Batch tracking can therefore matter in discrete manufacturing as well as in process industries.

6. Calculating production costs

Both order types can collect material and production activity costs. Additional costing functions become relevant when one production run produces several saleable outputs.

Discrete manufacturing	Process manufacturing
Order costs: Production orders collect component consumption and activity costs. Comparing actual and planned costs can reveal additional material use or longer manufacturing time.	Order costs: Process orders collect ingredient consumption and processing activity costs. Analysis can show the cost impact of lower yield or additional processing.
Multiple outputs: Co-product costing is available where a production order produces several outputs requiring shared-cost allocation.	Co-products and by-products: Apportionment structures distribute shared costs across co-products. By-products use different costing treatment, so their classification affects the calculated product costs.

The costing method follows the production outputs and accounting requirements. Co-product allocation frequently matters in process industries, but SAP also supports it with production orders.

What If Your Plants Run Both Models?

Manufacturers can combine discrete and process production across their plants or within the same site. SAP S/4HANA supports this combination within one environment. Production can follow different methods for individual materials at each plant. The connection between stages must preserve the information needed to track the product through the complete manufacturing flow.

Consider a contract manufacturer that prepares a liquid formulation, fills it into containers, and uses those containers in finished kits. A process order manages the formulation batch. Once the filled product has passed the required quality checks, it becomes available for kit assembly.

A production order then brings together the filled containers, delivery devices, and packaging components. Recording which batch of filled product was consumed connects the finished kits with the earlier processing stages. If a quality issue later affects the formulation, the manufacturer can identify the related kit batches through those recorded relationships.

This arrangement also allows kit assembly to follow a separate schedule. One formulation batch can supply several assembly orders, while SAP tracks its consumption across them.

Build Your SAP Manufacturing Landscape With LeverX

LeverX helps discrete, process, and hybrid manufacturers translate production requirements into a working SAP S/4HANA solution. Our team works with production and quality specialists to define how the system should support each plant, then carries that design through configuration, integration, and go-live.

Engage LeverX for the scope your business needs:

Manufacturing assessment and solution design: Identify which requirements fit standard SAP capabilities, where additional solutions are needed, and what the implementation will involve.
SAP implementation and migration: Configure production workflows and prepare the associated data, with testing that covers material consumption through finished output and costing.
Engineering and shop-floor integration: Connect SAP S/4HANA with engineering applications, warehouse systems, and manufacturing execution tools so production can use the required information across systems.
Rollout and ongoing support: Prepare users for daily work, extend the solution to further plants, and resolve issues after launch.

Whether you need an S/4HANA migration or a connected manufacturing execution solution, LeverX can bring the required expertise into one project team. Contact us to discuss your production requirements and define the SAP scope, delivery approach, and resources your project needs.

FAQ

How long does an S/4HANA migration take for a manufacturer?

SAP’s transformation planning guide gives indicative timelines of 12–15 months for a system conversion and 15–21 months for a new implementation, assuming a single rollout wave. These estimates cover the broader transformation and provide a starting point for planning; individual manufacturing projects can fall outside these ranges.

The final schedule might be affected by the number of plants, integration work, and production testing. Process manufacturers may need to migrate and validate recipes, while either manufacturing type may require batch-data preparation. A rollout using an established template has a different scope from redesigning production across several plants.

The final estimate should include preparation and post-launch support, with system downtime during cutover estimated separately.

Which metrics show a manufacturing S/4HANA project worked?

Useful measures include plan adherence, manufacturing order cycle time, and production data quality. Batch release time and first-pass quality can show whether the relevant quality processes improved. The measures should reflect the project’s agreed scope and use a baseline from before go-live. Comparing similar products and operating conditions helps distinguish the effect of the implementation from changes in demand or production mix.

Can both discrete and process manufacturers use make-to-order (MTO) and make-to-stock (MTS) production in SAP S/4HANA?

Yes. Both can produce against a customer order (MTO) or replenish inventory based on expected demand (MTS). A machinery manufacturer might build custom equipment to order and standard models for stock. A chemical producer could follow the same strategies for customer-specific and standard blends.

Discrete and process manufacturing describe how goods are made. MTO and MTS determine which demand production fulfills. SAP S/4HANA supports these combinations within the scope available for the selected edition and production scenario.