Full questions with full answers — no sign-in required.
hardManufacturing Costing, WIP, Variance, Integration and Support
1. A global rollout uses a shared costing variant across regions, but planned costs on production orders in one region consistently fail to pick up the released standard cost estimate. How do you diagnose and resolve this at an architect level?
I check whether the material has a released standard cost estimate for the relevant plant and costing version, since order costing pulls from the current standard per the valuation variant's strategy sequence. I verify the costing variant's valuation variant strategy order, check if a marked-but-not-released estimate exists, and confirm the order's costing lot size and date don't fall outside the validity period. I also review whether plant-specific pricing strategy overrides were introduced regionally without updating the shared variant.
hardProduction Orders, Process Orders and Shop-Floor Execution
2. When a production order fails an availability check and the system proposes splitting the order into partial quantities, what process steps and tradeoffs must be evaluated before confirming the split?
Before accepting a split, evaluate whether the split preserves correct scheduling (each partial order gets independently scheduled dates based on component availability), whether cost collection and settlement rules apply consistently across resulting orders, and whether the original order's reservations, confirmations, and any partial goods movements are correctly transferred. Tradeoffs include increased administrative overhead (multiple orders to track), potential fragmentation of costing/variance reporting, and risk of double-counting if partial confirmations already occurred before the split. Validate settlement profile behavior on each resulting order and confirm capacity leveling is re-run.
mediumProduction Orders, Process Orders and Shop-Floor Execution
3. A production order's scheduling consistently shows components available late for the first operation despite MRP showing sufficient stock. How would you investigate the interaction between production supply and scheduling parameters?
I'd check the scheduling parameters for the order type/plant combination, specifically whether automatic scheduling considers replenishment lead time or in-house production time for staged components, and whether the order's basic dates were generated with backward vs. forward scheduling causing tight start dates. I'd also review the supply area lead time in the control cycle or storage location assignment feeding the operation, and confirm that reservation availability dates align with the operation's earliest start rather than the order's basic start date.
mediumS/4HANA Manufacturing, PP/DS, IBP, Migration and Architecture
4. Six months after go-live, planners report a growing backlog of unplanned orders in PP/DS heuristics runs, and integration with BTP Integration Suite for external supplier collaboration is delayed. What steps would you take to diagnose and resolve the backlog while assessing migration object impact?
First check PP/DS application log and CDS-based monitoring apps for heuristic run failures or timeouts, then verify the integration model (CIF) queues (SMQ1/SMQ2) aren't stuck, which often causes backlog buildup. Review BTP Integration Suite iFlow logs for message failures affecting supplier confirmations feeding back into PP/DS. Reassess whether migrated master data objects (e.g., PPDS-specific settings) were correctly transferred, since incomplete migration objects can cause heuristics to skip orders.
easyS/4HANA Manufacturing, PP/DS, IBP, Migration and Architecture
5. In an S/4HANA manufacturing transformation adopting Clean Core principles, how does IBP integration with MM typically avoid custom ABAP modifications on the S/4HANA side?
Clean Core avoids custom code in S/4HANA by using standard CIF-based or SAP-delivered IBP integration content (CDS-based extraction, standard APIs) for master and transactional data exchange with MM (material master, stock, batches). Any needed extensions are built via in-app or side-by-side BTP extensibility, keeping the S/4HANA core untouched and upgrade-safe, rather than modifying standard MM tables or function modules.
hardS/4HANA Manufacturing, PP/DS, IBP, Migration and Architecture
6. In an S/4HANA Public Cloud manufacturing rollout using MRP Live with PM integration, what architectural controls should be in place to ensure capacity evaluation performance remains acceptable as maintenance orders and production orders compete for the same work centers?
Architect capacity leveling to run outside peak MRP Live windows, ensure work center capacity categories distinguish production versus maintenance demand where feasible, and use finite scheduling selectively rather than for the full horizon to limit computation load. In Public Cloud, rely on standard scope items for capacity evaluation since custom code is restricted, and monitor job runtime via application job monitoring to detect performance degradation as order volume grows.
