Oracle Inventory Management

Each (EA) is a standard Unit of Measure in Oracle Inventory and other ERP systems, used for counting individual items. Quantity is a concept, not a UOM itself. Part number is an identifier, not a measurement unit.

Oracle Inventory supports multiple replenishment methods including Replenishment Counting, Kanban, and Min-Max Planning. MRP is a separate planning methodology, and Safety Stock is a setting, not a replenishment method per se.

When an attribute is controlled at the Item Master level, you can still override or update it at the organization level unless the control level specifically prohibits it. Master-level control doesn't automatically lock all organization-level updates.

Min-Max planning CAN be performed at the sub-inventory level in Oracle Inventory. This allows organizations to maintain different stock levels for different storage locations within the same organization.

Oracle Inventory supports all three types of Move orders: Move order requisitions (for material requests), Replenishment Move orders (generated by min-max or Kanban), and Pickwave move orders (for batch picking).

ATP (Available to Promise) is a standard supply chain concept indicating the quantity available for customer orders after considering current inventory, existing commitments, and planned receipts. It's not about procurement or processing.

Oracle Inventory requires exactly 6 mandatory flexfield segments (also known as the key flexfield structure) for the Item flexfield. These typically include segments like Item, Organization, etc., that form the item's unique identifier.

Economic Order Quantity (EOQ) is specifically associated with Re-order point planning in Oracle Inventory. It calculates the optimal order quantity to minimize total inventory costs. Min-Max planning uses different logic, and ATP is unrelated.

ABC Analysis is the inventory management technique of ranking items based on criteria (usually annual usage value) and grouping them into classes (A, B, C) for different control levels. Cycle analysis refers to inventory counting cycles.

Stockable, Purchasable, and Build in WIP are all valid item status attributes in Oracle Inventory. 'Receivable' is not an item status - receivables relate to customer invoices, not item attributes.

Oracle Inventory module provides cost information to Oracle Costing for calculating transaction rates. When inventory transactions occur (receipts, issues, transfers), the cost data flows from Inventory to Costing to maintain accurate cost accounting. Identifying part numbers and item components are setup functions, while demand forecasting is a planning function - not the costing integration point.

Oracle Inventory Planning includes both Min-Max Planning (maintains stock between minimum and maximum levels) and Reorder Point Planning (triggers reorder when stock falls below a threshold). These are the two primary manual planning methods available in the module. Option C correctly combines both methods.

Min-Max Planning can be used as a simpler alternative to complex MRP (Material Requirements Planning) or MPS (Master Production Schedule) calculations. It's suitable for items with stable demand where maintaining minimum/maximum levels is sufficient. Min-Max is not limited to sub-inventory level and is distinct from EOQ models.

In Oracle Applications, the Inventory responsibility is specifically used to set up organizations within the Inventory module. General Ledger Super User handles financial setup, System Administrator is for technical configuration, and Order Management Super User manages order processing - none of these handle organization definition for inventory purposes.

In-transit receipts in Oracle Inventory are received from the Purchasing module when goods are shipped from a supplier but not yet delivered to the final destination. While Order Management and Work in Process handle inventory movements, they are not sources for in-transit receipts. Option C correctly identifies Purchasing as the single source.

Oracle Inventory allows flexible configuration of stock locator segments, letting organizations decide which segments (like subinventory, locator, aisle, bin) must be entered during transactions. This flexibility accommodates different warehouse management needs - from detailed tracking to simplified setups. The statement is true.

In Oracle Inventory and warehouse management, stock locators are structured and configured using key flexfields to identify specific physical storage locations.

In Oracle Inventory, pull sequences define the source and replenishment chain for kanban locations, while generating and printing cards are standard kanban execution tasks. Min-Max and Re-order point planning do not use these kanban-specific steps, making Kanban Planning correct.