How does SAP Variant Configuration support MTU's configurable engine families in ECMS?

• A. It manages features/characteristics of a configurable material, defines dependencies, and enables sales, engineering, and production to handle different variants from a single configurable material.
• B. It handles only pricing.
• C. It stores project schedules.
• D. It defines manufacturing shop floor routes only.

Answer: (A)

Variant Configuration models MTU’s configurable engine families as one configurable material by capturing features (characteristics) that describe the options an engine can have—such as displacement, turbo vs. naturally aspirated, fuel system, emissions level, and other design choices—and then defining dependencies and value rules that ensure only feasible combinations are selectable. This setup lets sales, engineering, and production work from a single configurable material, generating different variants (engine configurations) from that one source rather than managing separate materials for each option set. In ECMS, this also supports integrating the configured variant with engineering data and BOM structures, so changes in requirements or design rules flow consistently across the product and manufacturing processes. The other choices focus on narrow functions—pricing, scheduling, or routing—while miss the core idea of modeling options, enforcing feasible configurations, and enabling cross‑functional handling of multiple variants from a single material.