SAP IBP Supply Planning Interview Questions

Supply Planning in SAP IBP covers the design and operation of unconstrained and constrained supply plans that translate demand signals into feasible production, procurement, and distribution recommendations across a multi-echelon network, using the planning area, key figures, master data, and optimizer/heuristic run engines within SAP IBP cloud and its integration with S/4HANA. Key lesson areas: Configuring and Sequencing Supply Planning Operators (Heuristic vs Optimizer); Configuring Supply Planning Master Data, Key Figures, and Time Series for Constrained Planning; Introduction to Supply Planning in SAP IBP: Purpose, Planning Model, and Key Figures Learn how supply planning operators (heuristic and optimizer) are configured, sequenced, and run in SAP IBP, including scope selection, run parameters, and how operator choice affects supply plan outcomes and performance. Learn how to configure the master data, key figures, and time-series structures required to move from a basic unconstrained supply view to a constrained supply planning setup that respects capacity and sourcing rules. Understand why Supply Planning exists in SAP IBP, how it fits into the broader IBP planning model, and what the core key figures and master data represent before configuring or running any supply plan.

Understand why Supply Planning exists in SAP IBP, how it fits into the broader IBP planning model, and what the core key figures and master data represent before configuring or running any supply plan. Deep explanation: Supply Planning in SAP IBP answers a fundamental business question: given a demand signal, what is the most feasible and cost-effective way to source, produce, and move product across a network of locations, considering capacity, lead time, and inventory constraints? It sits downstream of Demand Planning and upstream of Response and Deployment in the typical IBP process chain, and it is the engine that converts a statistical or consensus forecast into an executable supply proposal. At the heart of SAP IBP is the planning area, a container that holds master data types (location, product, customer, resource, and so on), key figures, and time profiles. Supply Planning does not exist as an isolated module; it is a set of key figures and a run configuration layered on top of the same planning area used for Demand Planning, S&OP, and often Inventory Optimization. This shared-model design is a defining characteristic of IBP: everything lives in one in-memory model, so a planner working in Supply Planning sees the same product and location master data, and potentially the same demand key figures, that a demand planner populated earlier in the process. Core key figures a beginner must understand include: Demand (the consensus or unconstrained forecast fed into supply), Supply Proposals (production, procurement, or transportation quantities the system proposes), Confirmed/Constrained Demand (the portion of demand the network can actually fulfill given constraints), Inventory (projected on-hand and safety stock), and various capacity consumption key figures tied to resources. These key figures are time-phased and stored at specific planning levels (for example, product-location-week), and the granularity chosen has direct performance and usability consequences later. Master data objects central to Supply Planning include Location (plants, distribution centers, customers), Product, Location Product (product-specific attributes at a location, such as lot size or safety stock method), Resource (production or transportation capacity), and Production Data Structure elements such as Production Process Model or Production Source, which describe how a product is made or sourced and what resources it consumes. Beginners often first encounter Supply Planning through the unconstrained heuristic, a simpler run type that propagates supply without hard capacity limits, before progressing to constrained heuristic runs or the optimizer, which explicitly respects capacity and can consider costs. A critical conceptual point: Supply Planning in IBP is not a single monolithic transaction like an ECC MRP run. It is a configurable combination of a planning run profile, selected key figures, a run type (heuristic or optimizer), and a time horizon, executed either interactively for a planner working in Excel-based UI or in the background as part of a periodic batch job. Understanding this modularity early prevents the common misconception that 'running supply planning' always means the same calculation; the outcome depends heavily on which run profile and constraints are configured. Finally, beginners should understand that IBP is a cloud-only, multi-tenant SaaS product from SAP; there is no on-premise equivalent of IBP itself, though it integrates with S/4HANA (on-premise, private cloud, or public cloud editions) and ECC for master data and transactional data exchange. Behavior, available run types, and integration content can differ by IBP release and by whether the customer uses SAP-delivered planning area templates (like SAP7) or a custom-built planning area, so any configuration guidance must be validated against the specific tenant's model rather than assumed universal. Recommended practices: • Always confirm the planning level (time and location-product granularity) with business stakeholders before key figures are built out. • Reuse demand key figures as supply inputs where the process design calls for it, rather than duplicating data unnecessarily. • Document which run type (heuristic vs. optimizer) is intended for each planning scenario early, since it affects master data completeness requirements. • Validate assumptions about delivered content (e.g., SAP7 template) against the actual tenant configuration rather than generic documentation. • Start pilot configurations at a coarser granularity and refine only if business need is demonstrated, to control performance and maintenance overhead. Common mistakes to challenge: • Assuming Supply Planning is a single fixed transaction rather than a configurable combination of run type, run profile, and key figures. • Confusing the unconstrained heuristic with a capacity-aware calculation, leading to unrealistic supply proposals being presented to planners as final. • Not understanding the shared planning area model, causing teams to duplicate key figures instead of reusing existing demand key figures as supply run inputs. • Treating master data setup (Location Pro

A consumer goods client used the Heuristic for standard distribution planning across regional distribution centers, but capacity-constrained co-packing plants caused frequent stockouts because the Heuristic processed nodes without balancing shared constrained capacity. The project team introduced a segmented process chain: the Heuristic ran first for unconstrained finished-goods flows, and the Optimizer was scoped specifically to the constrained co-packing plants with tuned penalty costs so higher-margin SKUs were prioritized when capacity was insufficient. Runtime was managed by limiting the optimizer scope to a rolling 13-week horizon and running it as a nightly batch job rather than interactively. A consumer goods company is rolling out IBP Supply Planning as the first phase of an S&OP transformation. The project team spends the first two weeks purely on model literacy: mapping which key figures in the delivered planning area template correspond to unconstrained demand versus constrained demand, and confirming with the business which planning level (product-location-week vs. product-location-day) will be used for the pilot region. This foundational alignment prevents rework later when the team configures heuristic and optimizer runs, because changing planning levels after key figures are populated and reports are built is costly. An automotive parts supplier is extending its IBP model from unconstrained supply planning to a constrained heuristic run because capacity at a bottleneck resource is repeatedly exceeded in initial pilot results. The consulting team audits Location Product and Production Process Model records and discovers several products are missing resource consumption rates, causing the heuristic to treat those products as having zero capacity impact. After correcting the master data and re-running, the exception key figures for late confirmation drop significantly, and the business gains confidence in the constrained proposals before extending the approach to additional plants. Interview focus: Interview questions at this level often ask candidates to explain the practical difference between constrained heuristic and optimizer runs, and what master data gaps typically cause infeasible or unrealistic results. Strong answers connect specific master data objects (Production Source, resource capacity) to specific run behaviors rather than giving only textbook definitions. Interviewers commonly probe whether a candidate understands that IBP Supply Planning is model-driven rather than transaction-driven, and whether they can explain the diffe

First understand the current business requirement, dependencies, configuration or code path, integrations, production usage, and known pain points. Do not redesign before establishing the existing behavior. Lesson areas to review: Configuring and Sequencing Supply Planning Operators (Heuristic vs Optimizer); Configuring Supply Planning Master Data, Key Figures, and Time Series for Constrained Planning; Introduction to Supply Planning in SAP IBP: Purpose, Planning Model, and Key Figures Known mistakes: • Assuming Supply Planning is a single fixed transaction rather than a configurable combination of run type, run profile, and key figures. • Confusing the unconstrained heuristic with a capacity-aware calculation, leading to unrealistic supply proposals being presented to planners as final. • Not understanding the shared planning area model, causing teams to duplicate key figures instead of reusing existing demand key figures as supply run inputs. • Treating master data setup (Location Product, Production Source) as an afterthought rather than a prerequisite for any meaningful supply run. • Assuming behavior seen in one customer's IBP tenant (e.g., SAP7 template) applies universally to all tenants, without checking the actual planning area configuration. • Enabling a constrained or optimizer run before verifying that all relevant Production Sources, Transportation Lanes, and resource capacities are complete. • Defining key figures at a planning level that does not match the granularity of the underlying master data, causing misleading aggregation. • Ignoring frozen or firmed horizon settings, resulting in near-term supply proposals that change unpredictably between runs and erode planner trust. • Assuming the optimizer will simply 'work around' missing cost or capacity data instead of producing infeasible or misleading results. • Skipping incremental validation (heuristic first, then constrained heuristic, then optimizer) and jumping straight to the most complex run type. • Running the Optimizer across the full network and full horizon by default, causing excessive runtime and support escalations • Leaving penalty/cost key figures at default or blank values, producing optimizer plans that look arbitrary or unbalanced • Assuming Heuristic sequencing follows product priority automatically when it actually depends on the configured bill of distribution or node sequence • Not validating total supply versus total demand immediately after a run, missing large infeasibilities until planners notice stockouts later • Mixing constrained and unconstrained scope in a

Learn how supply planning operators (heuristic and optimizer) are configured, sequenced, and run in SAP IBP, including scope selection, run parameters, and how operator choice affects supply plan outcomes and performance. Deep explanation: In SAP IBP Supply Planning, the actual generation of a feasible supply plan happens through operators executed against the planning area's time series or order-based data. The two primary engines are the Supply Heuristic and the Optimizer, and choosing between them, and sequencing them correctly within a process chain, is one of the most consequential design decisions a consultant makes. The Heuristic is a rule-based, capacity-check-optional propagation engine. It processes supply chain nodes in a defined sequence (typically following the bill of distribution or a heuristic profile) and generates supply proposals to cover net demand, respecting lot sizing, minimum/maximum stock levels, and basic constraints if configured. It is fast, deterministic, and easy to explain to business users, but it does not truly optimize cost or globally balance constrained capacity, it satisfies demand node by node in sequence. The Optimizer, by contrast, solves a linear/mixed-integer programming problem across the entire scoped network simultaneously, considering costs (production, transportation, storage, non-delivery penalty), capacity constraints, and priorities, to produce a plan that minimizes total cost or maximizes a defined objective while respecting hard and soft constraints. It is more powerful for constrained, multi-echelon situations with real trade-offs, but it is computationally heavier and its output can be harder for planners to intuitively trace, especially when penalty costs are miscalibrated. Design and configuration: Operators are configured in the application as background or interactive runs. You define the scope (planning area, version, time horizon, and filter on planning object structure attributes such as location, product, or customer), select key figures to read and write, and set operator-specific parameters. For the Heuristic, this includes the sequence of processing (often driven by a bill of distribution or explicit node priority), safety stock and lot size handling, and whether it should consider resource capacity. For the Optimizer, you configure cost key figures, capacity key figures, and priority or penalty settings that shape the objective function; a poorly tuned penalty cost is a very common cause of counterintuitive optimizer results. Runtime flow: A typical process chain runs demand consensus first (writing a consensus demand key figure), then supply planning reads that demand as an input key figure, generates supply proposals (production, procurement, and stock transfer quantities) written to output key figures, and these can feed a response planning step or downstream S/4HANA execution via order conversion or interface integration. Operators can be chained: for example, run the Heuristic first for unconstrained categories, then the Optimizer for capacity-constrained categories, using different filters to segment the network and control total runtime. Integration and S/4HANA differences: In S/4HANA integration (whether on-premise, private cloud, or via CI-DS/API integration to public cloud IBP), the supply plan key figures are typically mapped and released to S/4 as planned independent requirements or stock transfer/purchase requisitions, depending on the integration scenario configured. The underlying planning engine behavior itself does not change based on the S/4 deployment, but data volumes, master data alignment (location, product, resource mapping), and the frequency/timing of integration jobs materially affect how fresh the supply plan input is when the operator runs. Troubleshooting and production support: Common production issues include runs that take excessively long (often due to overly broad scope or too many time buckets), infeasible optimizer results (constraints too tight, causing the run to fail or return a large non-delivery quantity), and heuristic results that look sensible per-node but leave downstream nodes short because the sequence or bill of distribution is misconfigured. Verification should always include checking a small representative scope first, reviewing key figure values before and after the run, and comparing total supply to total demand to catch obvious imbalances early. Recommended practices: • Segment the planning scope so the Optimizer is only applied where real cross-node capacity constraints exist, keeping unconstrained flows on the faster Heuristic • Deliberately calibrate cost and penalty key figures with business stakeholders rather than accepting technical defaults • Start operator testing on a small, representative scope before scaling to full network and horizon • Always compare pre-run and post-run key figure totals as a first-line sanity check after any batch run • Document the node processing sequence and bill of distribution logic so planners can explain Heuristic outcomes to business users Common mistakes to challenge: • Running the Optimizer across the full network and full horizon by d

Learn how to configure the master data, key figures, and time-series structures required to move from a basic unconstrained supply view to a constrained supply planning setup that respects capacity and sourcing rules. Deep explanation: Moving from conceptual understanding to a working constrained supply plan requires deliberate configuration of several interdependent layers: master data, key figures, time profiles, and the run profile that ties them together. This lesson focuses on what an intermediate consultant configures and validates before a constrained heuristic or optimizer run can produce trustworthy results. Master data first. Location Product records must carry attributes such as lot sizing rules, safety stock parameters, and shelf life if relevant, because these directly influence how supply proposals are rounded, batched, and timed. Production Source and Transportation Lane (or equivalent sourcing) records define which plants can produce which products and which lanes can move them between locations, along with lead times and, where applicable, cost fields used by the optimizer. Resource master data defines available capacity per time bucket (for example, hours per day per line), and Production Process Model or Production Data Structure elements define resource consumption rates per unit produced. Any gap here—such as a missing transportation lane or an incomplete resource calendar—will either cause the run to silently ignore a valid sourcing option or, worse, produce infeasible or unrealistic results that look plausible. Key figures come next. A constrained run typically needs, at minimum: a demand input key figure (often the consensus or constrained demand from an upstream process step), a supply proposal key figure (often split by production, procurement, and transportation), a capacity consumption key figure linked to resources, and inventory-related key figures such as projected stock and safety stock. Many implementations also configure exception-driven key figures, such as late confirmation or unmet demand, to help planners quickly identify infeasibilities after a run. Key figures must be correctly typed (stored vs. calculated), assigned to the right aggregation/disaggregation behavior, and placed at the correct planning level; a key figure defined at a coarser level than the master data it should reflect will produce misleading aggregated numbers. Time profiles and planning horizons matter significantly in Supply Planning because capacity and lead times are inherently time-phased. Consultants must configure the planning horizon (how far into the future the run considers), the time bucket (day, week, month), and often a separate frozen or firmed horizon inside which the system should not change already-committed supply proposals. Getting the frozen horizon wrong is a frequent source of planner distrust, since a run that keeps changing near-term proposals every cycle undermines confidence in the process. Run profile configuration ties these elements together: it specifies whether the run is unconstrained heuristic, constrained heuristic (which respects capacity but uses priority-based logic rather than true optimization), or optimizer-based (which can minimize cost or maximize service subject to constraints, using linear or mixed-integer programming). The choice affects both the required master data completeness and expected run time; optimizer runs are more sensitive to data quality issues such as missing costs or inconsistent unit-of-measure conversions, because infeasibilities can cause the solver to fail or return degenerate solutions. Validation before go-live should include running the heuristic first to sanity-check basic supply flow, then progressively enabling constraints and comparing proposal quantities against known capacity limits, and finally reviewing exception key figures for unexpected values. Differences across SAP IBP releases and template versions (for example, availability of certain optimizer cost key figures) mean this configuration should always be verified against the specific tenant rather than assumed identical to another project's setup. Recommended practices: • Complete and validate master data (sourcing, resources, lead times) incrementally before enabling capacity constraints. • Configure frozen/firmed horizons deliberately in partnership with planners to balance stability and responsiveness. • Build exception key figures early so infeasibilities and unmet demand are visible immediately after each run. • Validate constrained results against known real-world capacity limits before trusting the run for planning decisions. • Progress run complexity incrementally: unconstrained, then constrained heuristic, then optimizer, validating at each stage. Common mistakes to challenge: • Enabling a constrained or optimizer run before verifying that all relevant Production Sources, Transportation Lanes, and resource capacities are complete. • Defining key figures at a planning level that does not match the granularity of the underlying master data, causing misleading aggregation. • Ignoring frozen or firmed horizon settings, resulting in near-term supply propos

Start by reproducing and scoping the issue, then validate the relevant master/configuration/runtime data and isolate the failing step before changing anything. Common failure patterns from the lesson set: • Assuming Supply Planning is a single fixed transaction rather than a configurable combination of run type, run profile, and key figures. • Confusing the unconstrained heuristic with a capacity-aware calculation, leading to unrealistic supply proposals being presented to planners as final. • Not understanding the shared planning area model, causing teams to duplicate key figures instead of reusing existing demand key figures as supply run inputs. • Treating master data setup (Location Product, Production Source) as an afterthought rather than a prerequisite for any meaningful supply run. • Assuming behavior seen in one customer's IBP tenant (e.g., SAP7 template) applies universally to all tenants, without checking the actual planning area configuration. • Enabling a constrained or optimizer run before verifying that all relevant Production Sources, Transportation Lanes, and resource capacities are complete. • Defining key figures at a planning level that does not match the granularity of the underlying master data, causing misleading aggregation. • Ignoring frozen or firmed horizon settings, resulting in near-term supply proposals that change unpredictably between runs and erode planner trust. • Assuming the optimizer will simply 'work around' missing cost or capacity data instead of producing infeasible or misleading results. • Skipping incremental validation (heuristic first, then constrained heuristic, then optimizer) and jumping straight to the most complex run type. • Running the Optimizer across the full network and full horizon by default, causing excessive runtime and support escalations • Leaving penalty/cost key figures at default or blank values, producing optimizer plans that look arbitrary or unbalanced • Assuming Heuristic sequencing follows product priority automatically when it actually depends on the configured bill of distribution or node sequence • Not validating total supply versus total demand immediately after a run, missing large infeasibilities until planners notice stockouts later • Mixing constrained and unconstrained scope in a single Heuristic run without segmenting by capacity sensitivity, hiding true bottlenecks Checks and practices: • Always confirm the planning level (time and location-product granularity) with business stakeholders before key figures are built out. • Reuse demand key figures as supply inputs where the

• Always confirm the planning level (time and location-product granularity) with business stakeholders before key figures are built out. • Reuse demand key figures as supply inputs where the process design calls for it, rather than duplicating data unnecessarily. • Document which run type (heuristic vs. optimizer) is intended for each planning scenario early, since it affects master data completeness requirements. • Validate assumptions about delivered content (e.g., SAP7 template) against the actual tenant configuration rather than generic documentation. • Start pilot configurations at a coarser granularity and refine only if business need is demonstrated, to control performance and maintenance overhead. • Complete and validate master data (sourcing, resources, lead times) incrementally before enabling capacity constraints. • Configure frozen/firmed horizons deliberately in partnership with planners to balance stability and responsiveness. • Build exception key figures early so infeasibilities and unmet demand are visible immediately after each run. • Validate constrained results against known real-world capacity limits before trusting the run for planning decisions. • Progress run complexity incrementally: unconstrained, then constrained heuristic, then optimizer, validating at each stage. • Segment the planning scope so the Optimizer is only applied where real cross-node capacity constraints exist, keeping unconstrained flows on the faster Heuristic • Deliberately calibrate cost and penalty key figures with business stakeholders rather than accepting technical defaults • Start operator testing on a small, representative scope before scaling to full network and horizon • Always compare pre-run and post-run key figure totals as a first-line sanity check after any batch run • Document the node processing sequence and bill of distribution logic so planners can explain Heuristic outcomes to business users Relevant lesson areas: Configuring and Sequencing Supply Planning Operators (Heuristic vs Optimizer); Configuring Supply Planning Master Data, Key Figures, and Time Series for Constrained Planning; Introduction to Supply Planning in SAP IBP: Purpose, Planning Model, and Key Figures A strong answer should connect the technical or functional choice to maintainability, upgrade impact, performance, security, supportability, and clean-core principles where applicable.

Advanced capstone for Supply Planning, connecting the existing lesson areas: Introduction to Supply Planning in SAP IBP: Purpose, Planning Model, and Key Figures; Configuring Supply Planning Master Data, Key Figures, and Time Series for Constrained Planning; Configuring and Sequencing Supply Planning Operators (Heuristic vs Optimizer). The goal is to move from feature knowledge to architecture, integration, production support and governance decisions. Recommended design and operating practices: • Always compare pre-run and post-run key figure totals as a first-line sanity check after any batch run • Always confirm the planning level (time and location-product granularity) with business stakeholders before key figures are built out. • Build exception key figures early so infeasibilities and unmet demand are visible immediately after each run. • Complete and validate master data (sourcing, resources, lead times) incrementally before enabling capacity constraints. • Configure frozen/firmed horizons deliberately in partnership with planners to balance stability and responsiveness. • Deliberately calibrate cost and penalty key figures with business stakeholders rather than accepting technical defaults • Document the node processing sequence and bill of distribution logic so planners can explain Heuristic outcomes to business users • Document which run type (heuristic vs. optimizer) is intended for each planning scenario early, since it affects master data completeness requirements. • Progress run complexity incrementally: unconstrained, then constrained heuristic, then optimizer, validating at each stage. • Reuse demand key figures as supply inputs where the process design calls for it, rather than duplicating data unnecessarily. • Segment the planning scope so the Optimizer is only applied where real cross-node capacity constraints exist, keeping unconstrained flows on the faster Heuristic • Start operator testing on a small, representative scope before scaling to full network and horizon • Start pilot configurations at a coarser granularity and refine only if business need is demonstrated, to control performance and maintenance overhead. • Validate assumptions about delivered content (e.g., SAP7 template) against the actual tenant configuration rather than generic documentation. • Validate constrained results against known real-world capacity limits before trusting the run for planning decisions. Failure patterns that must be challenged: • Assuming behavior seen in one customer's IBP tenant (e.g., SAP7 template) applies universally to all tenants, without checking the actual planning area configuration. • Assuming Heuristic sequencing follows product priority automatically when it actually depends on the configured bill of distribution or node sequence • Assuming Supply Planning is a single fixed transaction rather than a configurable combination of run type, run profile, and key figures. • Assuming the optimizer will simply 'work around' missing cost or capacity data instead of producing infeasible or misleading results. • Confusing the unconstrained heuristic with a capacity-aware calculation, leading to unrealistic supply proposals being presented to planners as final. • Defining key figures at a planning level that does not match the granularity of the underlying master data, causing misleading aggregation. • Enabling a constrained or optimizer run before verifying that all relevant Production Sources, Transportation Lanes, and resource capacities are complete. • Ignoring frozen or firmed horizon settings, resulting in near-term supply proposals that change unpredictably between runs and erode planner trust. • Leaving penalty/cost key figures at default or blank values, producing optimizer plans that look arbitrary or unbalanced • Mixing constrained and unconstrained scope in a single Heuristic run without segmenting by capacity sensitivity, hiding true bottlenecks • Not understanding the shared planning area model, causing teams to duplicate key figures instead of reusing existing demand key figures as supply run inputs. • Not validating total supply versus total demand immediately after a run, missing large infeasibil