Select Two (Multi-Select) Questions

The demand forecast consumption rate.

Why it fails: Demand forecast consumption relates to how actual orders reduce forecasted quantities. While important for planning, it is not a direct factor in the Min/Max replenishment logic, which is purely reactive to the current physical inventory balance relative to the static minimum and maximum values defined for the item.

The previous quarter's sales volume.

Why it fails: Historical sales volume is used for forecasting purposes but is not a functional parameter used in the Min/Max calculation logic. Master planning looks at current and projected stock balances, not historical data, when deciding whether to trigger a new order based on defined stock level thresholds.

The vendor's average delivery performance.

Why it fails: Vendor performance impacts lead time calculations and scheduling, but it does not influence the replenishment quantity itself in the Min/Max model. The quantity triggered is determined solely by the difference between current inventory and the specified maximum level, regardless of how quickly the vendor can deliver the goods.

A storage dimension group that includes Site and Warehouse.

Why it fails: Storage dimensions determine where inventory is stored and tracked, such as site and warehouse. They do not drive variant generation for color and size. A product can have a storage dimension group and still lack variants, so this element is not required to create the color and size combinations described.

A unit sequence group that includes each variant's unit of measure.

Why it fails: A unit sequence group defines the sequence of units for conversions and order entry, but it does not generate product variants. Variants are created from product dimensions, not from unit sequences. Configuring a unit sequence group would not produce color and size combinations, so it is not one of the required elements here.

A tracking dimension group that includes Batch and Serial.

Why it fails: Tracking dimensions such as Batch and Serial control how inventory is tracked, not how product variants are generated. They are unrelated to creating color and size combinations. Including them would not cause the system to generate variants and could add unnecessary tracking overhead, so this is not a required element for the scenario.

A product dimension group with Configuration set as active to drive variant creation.

Why it fails: A product dimension group is needed only when the product will have variants based on configuration, size, color, or style. The scenario describes a single product tracked by batch, not a variant product. Adding a configuration dimension would create unnecessary variants and does not address batch tracking or warehouse financial behavior.

A coverage group with positive days and negative days set to default values for master planning.

Why it fails: A coverage group controls master planning behavior such as coverage time fences and is assigned on the released product's plan data. It is not a prerequisite for batch tracking or for enabling financial inventory on the warehouse dimension. While useful for planning, it does not satisfy the scenario's configuration prerequisites.

An item model group configured with the standard cost inventory model and FIFO fallback.

Why it fails: An item model group is required for a released product, but the scenario does not specify a costing method, and standard cost with a FIFO fallback is not a valid combination. The requirement is about batch tracking and warehouse financial behavior, which are governed by the tracking and storage dimension groups, not by choosing a specific inventory model.

Set the 'Automatically create work' option to Yes on the wave template.

Why it fails: The 'Automatically create work' option controls whether work is created for the wave after processing. While it is essential for generating picking work, it does not specifically enable replenishment. Replenishment work is created by the 'Replenish' method, not by this option. Therefore, this setting alone will not cause the system to replenish picking locations during wave processing.

Set the 'Wave template' query to include only open sales orders.

Why it fails: The wave template query determines which orders are included in the wave. While it is important to select the correct orders, it does not affect replenishment. Replenishment is triggered by the 'Replenish' method and its associated template, not by the query. Restricting the query to open sales orders might limit the wave scope but will not enable or disable automatic replenishment of picking locations.

Set the 'Wave template type' to 'Shipping'.

Why it fails: The wave template type determines the overall purpose of the template, such as Shipping or Production. While a shipping wave template is used for outbound orders, setting the type alone does not enable automatic replenishment. Replenishment is controlled by specific wave step methods, not by the template type. Therefore, this setting is necessary for outbound processing but not sufficient to trigger replenishment during wave execution.

Automatic freight cost calculation.

Why it fails: Freight cost calculation is a function of the Transportation Management module and is completely independent of whether license plates are used in the warehouse. While a license plate holds data about the shipment, the rate calculation is performed by the engine based on carrier master data.

Elimination of the need for wave templates.

Why it fails: License plates are a tracking mechanism and do not replace the need for wave templates. Wave templates remain necessary to manage order release, work creation, and the overall dispatching flow regardless of whether the underlying inventory uses license plate tracking or not.

Automatic generation of customer invoices.

Why it fails: Invoice generation is a financial process in the Accounts Receivable module. It is triggered by order fulfillment and posting, not by the warehouse-level tracking of license plates. License plates are strictly for logistics and warehouse management, not for financial document processing or accounting automation.

Create a new inventory dimension for consignment.

Why it fails: Inventory owner is an existing inventory dimension; you do not create a new dimension. Creating a new dimension is not supported for this purpose and would require customization. The standard approach uses the Owner dimension, which is already available when the configuration key is enabled.

Enable the 'Consignment' parameter in the Inventory and warehouse management parameters.

Why it fails: There is no global parameter called 'Consignment' in Inventory and warehouse management parameters. Consignment is enabled through inventory owner setup and item configuration, not a single parameter. Enabling such a parameter does not exist, so it is not a valid configuration step.

Assign the inventory owner to the item's default order settings.

Why it fails: The inventory owner is not assigned through default order settings. Default order settings control purchasing, sales, and inventory policies like minimum and maximum quantities. While they are important for item setup, they do not control ownership. Ownership is managed through inventory dimensions and owner assignment on transactions.

Route plan

Why it fails: A route plan defines the sequence of stops for a route. It is used for route planning and scheduling, not for rating or carrier selection. While it can influence transportation, it does not provide the cost or transit time data needed to select a carrier. Therefore, it is not required for automatic rating and carrier selection.

Accessorial charge

Why it fails: Accessorial charges are additional fees for services like liftgate or inside delivery. They are part of the rate master configuration but are not standalone components required for rating. They are optional and only apply when specific services are requested. They do not enable automatic rating or carrier selection by themselves; the rate master and transit time engine are the core components.

Load template

Why it fails: A load template defines how loads are built, such as the maximum weight or volume, and how items are grouped. It is used during load planning but does not directly participate in rating or carrier selection. While it affects the load structure, it does not provide rates or transit times. Therefore, it is not required for automatic rating and carrier selection.

Mileage engine

Why it fails: The mileage engine calculates distances for routing and rating. While it is important for transportation management, it is not directly involved in fuel surcharge calculation. The mileage engine provides distance data used in rate determination, but the fuel surcharge specifically relies on the fuel index and the fuel surcharge configuration, not the mileage engine.

Accessorial charge

Why it fails: Accessorial charges are additional fees for services like loading or waiting time. They are not used for fuel surcharges. While they can be part of a rate route, they do not provide the dynamic fuel-based adjustment required here. Configuring an accessorial charge would not fulfill the need for a fuel surcharge tied to a fuel index.

Rate break

Why it fails: Rate breaks define the pricing tiers based on weight or volume. They are used to determine the base transportation rate, not the fuel surcharge. While rate breaks are essential for overall rate setup, they do not enable dynamic fuel surcharges. The fuel surcharge is typically applied as a separate charge, so rate breaks alone are insufficient.

Enable the 'Automatic return order processing' parameter in the warehouse management parameters.

Why it fails: There is no 'Automatic return order processing' parameter in warehouse management parameters. Return order processing is controlled by work templates and location directives, similar to other work order types. Enabling a non-existent parameter is not a valid configuration. The system uses standard work creation logic based on the work order type and associated configurations.

Set up a wave template for returns that includes a put-away step.

Why it fails: Wave templates are typically used for outbound processes, such as sales order picking. While waves can be used for inbound in some advanced scenarios, return order put-away work is not generated via wave templates. The standard method is through work templates and location directives for the 'Return order' work order type. Using a wave template would not automatically create put-away work for returns in the typical configuration.

Configure a reservation hierarchy that includes the returns location as the first dimension.

Why it fails: Reservation hierarchy is used to reserve inventory for outbound orders, not for put-away of returns. Including the returns location in the reservation hierarchy would not trigger put-away work creation. Put-away work is generated based on work templates and location directives. Therefore, this configuration is not required and would not achieve the desired outcome.

Only one category hierarchy of each type can exist at a time, and it must contain every product in the legal entity.

Why it fails: Multiple category hierarchies can exist, and products are not required to belong to every category. A hierarchy organizes a subset of products according to its purpose. Claiming only one hierarchy per type can exist and must contain all products is incorrect and does not match the flexibility the system provides.

Attribute values entered on a category are automatically copied to every product assigned to that category and cannot be changed per product.

Why it fails: Attribute values assigned at the category level provide defaults that products inherit, but they can be overridden per product. Saying they are copied automatically and cannot be changed is incorrect. Products retain the ability to specify their own attribute values, so this statement misrepresents how inheritance works.

A category hierarchy must be linked to a product dimension group before attributes can be assigned to its categories.

Why it fails: Category hierarchies and product dimension groups serve different purposes and are not linked in this way. Attributes are assigned directly to categories, independent of dimension groups, which govern variant dimensions. Requiring a dimension group link is not part of the configuration and would not enable attribute assignment.

Set the 'Wave template' to 'Default' for the warehouse.

Why it fails: Setting a wave template as default for a warehouse means it will be used when no specific template is selected. However, this does not ensure that the template contains the necessary steps for work creation. It is an administrative setting that simplifies selection but does not affect the internal logic of the wave template. It is not a requirement for automatic work creation.

Set the 'Wave template type' to 'Shipping'.

Why it fails: The wave template type determines the purpose of the wave, such as Shipping, Production, or Kanban. While Shipping is appropriate for sales orders, it alone does not ensure automatic work creation. The type primarily controls which order types can be processed. It is a necessary but not sufficient condition; other settings like wave steps are required to create work.

Set the 'Automatically create wave' option to 'Yes'.

Why it fails: The 'Automatically create wave' option controls whether a wave is automatically created when sales orders are released to the warehouse. While useful for automation, it does not directly create picking work; it only creates the wave. Work creation is handled by wave steps. This setting is about wave generation, not work creation, so it does not meet the specific requirement.

Set the 'Storage dimension group' to include the same dimensions as the product dimension group.

Why it fails: Storage dimension groups govern physical tracking dimensions such as Site, Warehouse, and Location. They are separate from product dimensions like Size and Color. Aligning storage and product dimension groups is not required to use product dimensions for variants or planning; the two serve different purposes and should be configured based on physical versus product characteristics.

Enable the 'Variant' generation option in the Inventory and warehouse management parameters.

Why it fails: Variant generation is performed at the product master level through the product dimension group and dimension values, not through a global parameter. There is no single parameter that enables variant generation for all products. This option misrepresents where the configuration is performed and would not achieve the required outcome.

Create a tracking dimension group that includes 'Batch' and 'Serial' for the product master.

Why it fails: Tracking dimension groups control batch and serial number tracking, which are inventory tracking dimensions, not product dimensions used for variants. Including Batch and Serial does not define variant dimensions such as Size or Color and is unrelated to planning and costing based on product dimensions. This action would not satisfy the requirement.

Replenish

Why it fails: Replenish is used to move inventory from a bulk location to a picking location when there is insufficient quantity. It does not create picking work for outbound orders. The scenario does not mention replenishment needs, so this method is not required.

Process wave

Why it fails: Process wave is not a standard wave template method. Wave templates consist of methods like Create work, Allocate, Replenish, and Containerize. Processing the wave is an action performed after the wave is created, not a method within the template itself.

Allocate

Why it fails: Allocate is used to reserve inventory for the sales order lines. While allocation is important, it does not create picking work. The scenario specifically requires work creation and immediate processing of that work, which are handled by other methods.

Reorder point

Why it fails: Reorder point is a fixed quantity threshold that triggers replenishment when inventory falls below it. While it acts as a buffer, it is not a safety margin setting in Master Planning; it is part of Min/Max coverage. It does not dynamically adjust planned orders based on variability, and it is not considered a safety margin configuration.

Maximum inventory

Why it fails: Maximum inventory is used in Min/Max coverage to define the upper limit for replenishment. It does not add a safety buffer; it simply caps the order quantity. It does not protect against variability in demand or lead time, and it is not a safety margin setting.

Lead time

Why it fails: Lead time is the time required to replenish an item. It affects the timing of planned orders but does not add a buffer quantity or time margin. It is a fundamental parameter for scheduling, but it does not provide protection against demand variability beyond its inherent offset.

Set the item model group to 'Physical inventory'.

Why it fails: Physical inventory is a standard inventory dimension setting and does not specifically enable cycle counting workflows. While it is necessary for tracking stock, it is not a configuration step unique to cycle counting, and failing to set this would impact general operations, not specifically cycle count automation.

Enable the 'Batch reservation' setting.

Why it fails: Batch reservation is used for managing inventory batches and FIFO/FEFO picking strategies. It has no functional role in the cycle counting process, which is concerned with verifying the physical presence of inventory rather than managing the reservation of specific batches for outbound or production order requirements.

Enable the 'Variant' flag in the Inventory model group.

Why it fails: Inventory model groups control stock valuation, costing methods, and reservation logic, but they do not manage variant generation or definition. While vital for accounting, the model group is independent of the product master configuration for variants, which relies entirely on dimension groups and the product lifecycle processes.

Set the Tracking dimension group to include Color, Size, and Style.

Why it fails: Tracking dimensions monitor inventory serials, batches, and owners, not the physical product attributes that define variants. The system architecture separates product definitions (variants) from inventory tracking (batches/serials), so including them in the tracking group would be functionally incorrect and would not enable product variant generation as required.

Enable 'Configuration' in the Storage dimension group.

Why it fails: Storage dimensions pertain to physical warehouse locations, sites, and zones. Adding configuration here does not facilitate product variant creation. The system relies on Product dimension groups to handle attributes like color, size, and style, ensuring clear separation between warehouse logistics and product identity management for retail operations.

User security roles.

Why it fails: Security roles determine access to system forms and data but have no impact on the background execution of the Master Planning engine. The planning engine operates under a system-level process that is independent of individual user permissions, so security configurations cannot be the cause of calculation errors.

Warehouse location barcodes.

Why it fails: Warehouse location barcodes are used for inventory tracking and warehouse operations (WMS). They are irrelevant to the supply requirements calculation performed by the Master Planning engine, which focuses on item quantities and demand dates rather than the physical location of the stock within the warehouse.

Warehouse work user

Why it fails: A warehouse work user is an employee who performs tasks in the system but is not a component of the warehouse setup itself. You can have thousands of locations without any specific user assigned to them. This is an authentication and access entity, not a required configuration for a warehouse.

Warehouse mobile device menu

Why it fails: Mobile device menus define the screens and actions available on the handheld terminal. While essential for execution, they are not a mandatory component required to create a warehouse location. You can define all your physical locations in the system without ever creating a single mobile device menu or device user.