Routing Fundamentals: Purpose, Structure, and Business Value
Understand what a routing is, why it exists, and how its structural elements (header, operations, sequences, work centers) drive planning and execution in manufacturing.
Explanation
A routing (also called a task list in SAP terminology, specifically a 'Routing' when used for discrete/repetitive manufacturing) describes how a material is produced: which operations must be performed, in what sequence, at which work centers, and how long each step takes. Without a routing, the system has no basis for scheduling production orders, calculating capacity requirements, or determining production costs beyond material cost. Business purpose: Manufacturing companies need a repeatable, standardized definition of the production process so that planning (MRP, capacity leveling), execution (order confirmations, goods movements), and costing (activity type consumption) all use the same source of truth. The routing is that source of truth for the 'how' of production, complementing the Bill of Material (BOM) which defines the 'what' (components consumed). Structural elements: - Header data: includes the plant, usage (indicates which application area may use the routing, e.g., production, universal), status (indicates whether the routing is released for use, e.g., created, released, or locked), and validity dates (from/to). The status is critical - an unreleased routing typically cannot be selected by MRP or order creation logic. - Group and group counter: a routing is stored under a 'group' (an internal grouping key) with a 'group counter' distinguishing multiple alternative routings within that group. This allows several alternative routings (e.g., different production lines) for the same material. - Lot size range: each alternative routing can be restricted to a lot-size validity range so that small-batch and large-batch production can use different operation sequences or work centers. - Operations: each operation represents a distinct step (e.g., cutting, assembly, painting) and references a work center where that step is performed. Operations carry standard values (setup time, machine time, labor time) expressed against a formula/key that the work center interprets for scheduling and costing. - Sequences: operations can be structured as a standard sequence, or use parallel and alternative sequences for more complex flows (e.g., rework loops, optional inspection branches). - Control key: attached at the operation level, the control key determines system behavior - whether the operation is relevant for scheduling, costing, capacity planning, confirmation, and printing. This is one of the most operationally important fields because it silently governs what functions 'work' for that operation. Integration touchpoints: routings link to work centers (which supply the capacity, cost center/activity type assignment, and formulas), to BOMs indirectly via the production version (which pairs a specific BOM alternative with a specific routing alternative for a material), and to production/process orders (which copy the routing operations at order creation time, so later routing changes do not automatically alter already-created orders). Why this matters for a consultant: getting routing usage, status, and lot-size validity right is foundational. Many downstream planning and costing problems (wrong lead times, missing capacity requirements, incorrect standard costs) trace back to routing master data issues such as an operation control key that excludes costing relevance, or a routing status that is not released.
Real project scenario
A discrete manufacturing client producing industrial pumps had two production lines: a manual assembly line for low-volume custom pumps and an automated line for high-volume standard pumps. During a rollout workshop, the consultant proposed creating two alternative routings under the same group, each restricted by lot-size validity range, tied to two production versions that also pointed to two BOM alternatives. This let MRP automatically select the correct routing/BOM combination based on the planned order quantity, avoiding manual intervention by planners and ensuring capacity requirements were posted to the correct work center (manual line vs. automated line) for scheduling.
Common mistakes
• Creating a routing but leaving its status as 'created' instead of 'released', causing MRP or order creation to fail to find a usable routing. • Confusing routing group/counter with material number, leading to accidentally reusing an existing group for an unrelated material. • Ignoring lot-size validity ranges, resulting in one routing being used for both very small and very large orders where operation times or work centers should differ. • Assuming a change to the routing automatically updates already-released production orders (it does not, since operations are copied at order creation). • Not aligning routing usage indicator correctly, which can prevent the routing from being found by certain order types or planning transactions.
Best practices
• Always set routing status to released before expecting MRP or order creation to consume it. • Use lot-size validity ranges deliberately to model genuinely different production flows, not just to store alternates without a clear a business reason. • Document routing group/counter conventions in a naming/numbering standard so multiple consultants do not create duplicate or conflicting alternatives. • Review control key settings on every operation type used in the client's process to ensure scheduling, costing, and confirmation relevance flags match business intent. • Use production versions consistently as the single point of BOM-routing pairing to keep planning and costing deterministic.
Interview angle
Interviewers often ask candidates to explain the relationship between routing, BOM, and production version, and why a production version exists as a separate object. A strong answer explains that the production version is the explicit link pairing a valid BOM alternative and routing alternative for a lot-size range, and that this decouples BOM and routing versioning so each can evolve independently while still being selectable together. Candidates should also be ready to explain control key relevance flags (scheduling, costing, confirmation) since this is a frequent scenario-based question.