Free Practice Questions for Oracle 1z0-1125-2 Exam

According to the Oracle Inventory Management Cloud User Guide, min-max planning is a replenishmentmethod that maintains inventory levels between a minimum and a maximum quantity. Min-max planning can be performed at two planning levels: organization and sub inventory (A). Organization level min-max planning considers all sub inventories within an organization for replenishment. Sub inventory level min-max planning considers only one sub inventory within an organization for replenishment. Min-max planning does not support locator ©, project (B), or item (D) as planning levels.

According to the Oracle Inventory Management Cloud User Guide, material status control is a feature that allows users to restrict transactions for certain items or lots based on their status. A material status can be defined with different transaction types that are allowed or disallowed for items or lots with that status. If intransit shipment transactions are not available under transactions allowed on the edit material status page for active material status, it means that the intransit shipment transaction type is not enabled for status control (D). The active material status usage being set to sub inventory (A) or lot © does not affect the availability of intransit shipment transactions under transactions allowed. The intransit shipment transaction type having a start date or not (B) does not affect the availability of intransit shipment transactions under transactions allowed.

According to the Oracle Manufacturing Cloud User Guide1, non-tracking components are components that do not require lot or serial control, and are not tracked in inventory. Non-tracking components are automatically transacted with two supply types: operation pull (A) and assembly pull (D). Operation pull components are transacted when an operation is completed. Assembly pull components are transacted when a work order is completed.

According to the Oracle Demand Management Cloud User Guide1, decomposition groups are used to simulate demand by making certain changes in holidays, events, or other factors that affect demand patterns. A demand planner can use decomposition groups to create different scenarios and compare them with the base forecast. Forecasting methods (A), forecasting parameters ©, and simulation output (D) are not forecasting profile options that can be used to simulate demand by making changes in holidays.

According to the Oracle Demand Management Cloud User Guide2, publishing demand plan is the process of sending demand management data to an external system such as Oracle Supply Planning Cloud or Oracle Sales Cloud. Publishing demand plan requires selecting a publish plan option that defines what data to publish, how to publish it, and where to publish it. Publishing demand plan allows users to share their approved demand plans with other stakeholders or systems for further analysis or execution. Running demand plan (A), approving demand plan (B), comparing demand plan (D), and archiving demand plan (E) are not processes that can be used to send demand management data to an external system, but rather processes that can be used to generate, validate, evaluate, or store demand plans.