1Z0-1073-26 Sample Questions & Answers

A UOM interclass conversion defines the conversion between the base UOM of one UOM class and the base UOM of a different class, and it's defined per item (items must exist before interclass or intraclass conversions can be created). Because the weight of a gallon depends on the product's density, the gallon-to-pound relationship can't be a standard conversion, which only relates a unit to the base unit of its own class. Once the base-to-base factor is defined for the item, it's valid for every unit in both classes, so gallons convert to pounds through the class base units. Each class's base UOM must be the smallest unit in that class.

Oracle states that facility schedules create the workday calendars of inventory organizations and gives 'the scheduling of cycle counts and calculating transit time' as examples. A cycle count selects a 'Workday Schedule', schedules (items in the class x counts per year) / working days per year items each day, and moves a count's due date to the next working day. Transit-time calculations use the inventory organization's schedule to move dates off nonworking days, and min-max planning counts only work days when it derives the requested delivery date. Pick release and ship confirm use transportation schedules instead, cost accounting periods come from the ledger, and transfer prices come from transfer pricing rules.

Oracle states that facility schedules create the workday calendars of inventory organizations and gives 'the scheduling of cycle counts and calculating transit time' as examples. A cycle count selects a 'Workday Schedule', schedules (items in the class x counts per year) / working days per year items each day, and moves a count's due date to the next working day. Transit-time calculations use the inventory organization's schedule to move dates off nonworking days, and min-max planning counts only work days when it derives the requested delivery date. Pick release and ship confirm use transportation schedules instead, cost accounting periods come from the ledger, and transfer prices come from transfer pricing rules.

Supply Chain Financial Orchestration (SCFO) acts as the financial engine that decouples physical material movement from financial ownership flows. It evaluates financial trade agreements, establishes transfer pricing, monitors ownership change events, and drives intercompany invoicing across Receipt Accounting and Cost Accounting.

Oracle's View Item Availability window (Manage Item Quantities) uses these formulas:

• Available to Transact = (Quantity On Hand) - Pending Transactions - Reservations = 1,000 - 0 - 300 = 700 units.
• Available to Reserve = (Reservable Quantity On Hand) - Pending Transactions - Reservations. Reservable on hand excludes the 150 units whose material status disallows reservations: (1,000 - 150) - 0 - 300 = 550 units.

Reservations don't reduce the on-hand quantity itself, but both availability figures subtract them.

A reservation that names the subinventory, locator and lot is a low-level (detailed) reservation; a high-level reservation holds only the item and organization, so stock can come from any available subinventory. Reserved material can't be picked for another demand, and when the reservation is to a subinventory and locator it can't be allocated to another supply source or transferred within inventory. Creating a reservation doesn't change the on-hand quantity: Available to Reserve and Available to Transact are reduced by the reserved quantity, and on hand changes only when the material is actually transacted.

False. Material Status Control in Oracle Inventory Cloud is cumulative and operates on the principle of maximum restriction. If any entity level in the hierarchy (Subinventory, Locator, Lot, or Serial) disallows a specific transaction type, the transaction is prohibited, regardless of whether a higher or lower level permits it.