1Z0-1073-26 Oracle Inventory Cloud 2026 Implementation Professional Practice Questions

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.

From update 25C, the 'Lot Expiration Actions' page has an 'Automated Action' field with two values, 'Create movement request' and 'Update material status' (for example, to Quarantine). The 'Automated Action' and 'New Material Status' fields are hidden by default and are shown with business rules in VB Studio Express mode. The action runs on the lot expiration action date, which is the lot expiration date plus the item's 'Expiration Action Interval'. You must schedule the 'Initiate Lot Expiration Actions' process for automated actions and expiry notifications to run. Without such a status change, an expired lot can still be transacted; it just can't be reserved for a date beyond its expiration date.

Two serial generation values capture serial numbers only on the way out. 'Entry at inventory pick' creates and assigns serial numbers at pick confirmation (sales order pick, transfer order pick, transfer order return pick, movement request issue), and serial numbers can't be recorded at receipt or put away. 'Entry at sales order, transfer order, or work order issue' creates and assigns serial numbers when the item is issued; they're required at ship confirm, but not for a receipt or a subinventory transfer. 'Predefined serial number' and 'Dynamic entry at inventory receipt' both assign serial numbers at receipt and require them on every later transaction, and serial control is set on the item or organization, not on a subinventory.

Two serial generation values capture serial numbers only on the way out. 'Entry at inventory pick' creates and assigns serial numbers at pick confirmation (sales order pick, transfer order pick, transfer order return pick, movement request issue), and serial numbers can't be recorded at receipt or put away. 'Entry at sales order, transfer order, or work order issue' creates and assigns serial numbers when the item is issued; they're required at ship confirm, but not for a receipt or a subinventory transfer. 'Predefined serial number' and 'Dynamic entry at inventory receipt' both assign serial numbers at receipt and require them on every later transaction, and serial control is set on the item or organization, not on a subinventory.

Approved Movement Requests require allocation before pick slips can be printed. If the pick allocation process has not been executed, or if picking rules find zero unreserved/transactable stock in the source subinventory matching the criteria, the allocation fails and no pick slip lines are generated.

In Oracle Fusion Cloud, an Item Organization stores item definitions, catalogs, categories, and engineering structures without tracking on-hand balances or generating cost accounting entries. This makes it the ideal repository for central engineering/R&D governance prior to assigning items to operational Inventory Organizations.

Each inventory organization is managed by a business unit and mapped to a legal entity and its primary ledger, so separate US and Canadian legal entities keep statutory accounting apart. For item governance, Oracle recommends a single item master that is separate from the organizations that store and transact items - usually an item organization - from which items are assigned to the inventory organizations. Transfers between profit center business units in different legal entities are handled by Supply Chain Financial Orchestration: its financial flows, transfer pricing rules, and documentation and accounting rules (including optional intercompany invoices) separate the financial part of the transfer from the physical transfer order.