Search Results firm_quantity

Overview

MTL_GROSS_REQ_COST_V is an APPS-owned database view in Oracle EBS Inventory (INV) that joins gross material requirements to item cost information. Its title and definition indicate it presents gross requirements from the material planning engine enriched with the standard cost of the demanded item, allowing planners and reports to view demand quantities alongside their associated unit cost without manually joining planning and costing schemas. The object is marked "Retrofitted," indicating it was introduced or re-pointed to support a specific release or patch level, and it carries a VALID status in ETRM 12.2.2 metadata. It is not a table: it exposes no independent storage and reflects the state of its base objects at query time. Its role is primarily reporting and integration, where downstream reports, concurrent programs, or custom extensions require a flattened, cost-enriched requirement line.

Underlying Base Objects

The documented base objects are MRP_GROSS_REQUIREMENTS (SYNONYM), CST_CG_ITEM_COSTS_VIEW (VIEW), MTL_PARAMETERS (SYNONYM), and MRP_PROJECT_PARAMETERS (SYNONYM). The view definition shown in the excerpt performs a UNION ALL of at least two legs, each joining MRP_GROSS_REQUIREMENTS to CST_CG_ITEM_COSTS_VIEW on ORGANIZATION_ID and INVENTORY_ITEM_ID, and to MTL_PARAMETERS on ORGANIZATION_ID. The first leg restricts GROSS.PROJECT_ID IS NULL and derives the cost group from MTL_PARAMETERS using DECODE on PRIMARY_COST_METHOD, defaulting to cost group 1 where no default group exists. This structure separates project-related requirements from non-project requirements so the correct cost group assignment is applied in each case. MRP_PROJECT_PARAMETERS governs the project-specific costing behavior referenced by the project leg.

Key Columns

The view exposes the full column set of MRP_GROSS_REQUIREMENTS plus ITEM_COST from CST_CG_ITEM_COSTS_VIEW. Identity and audit columns include DEMAND_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY. Planning attributes include USING_ASSEMBLY_ITEM_ID, USING_ASSEMBLY_DEMAND_DATE, USING_REQUIREMENTS_QUANTITY, ASSEMBLY_DEMAND_COMP_DATE, DEMAND_TYPE, ORIGINATION_TYPE, DEMAND_CLASS, DAILY_DEMAND_RATE, RESERVE_QUANTITY, DEMAND_SCHEDULE_NAME, and PLANNING_GROUP. Costing output is provided by ITEM_COST. Project context is supplied by PROJECT_ID and TASK_ID. The specific column referenced in the user search, FIRM_QUANTITY, represents the confirmed or firmed portion of the gross requirement, paired with FIRM_DATE for the associated firm date. Related quantity columns include OLD_DEMAND_QUANTITY and OLD_DEMAND_DATE, used to trace prior demand values, and SOURCE_ORGANIZATION_ID for inter-org demand origin.

Common Use Cases and Queries

Typical uses include reviewing firmed versus total gross demand, costing projected requirements, and feeding planning reports that must show demand at standard cost. A representative query filtering on the searched column is:

• SELECT DEMAND_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, FIRM_QUANTITY, FIRM_DATE, ITEM_COST FROM APPS.MTL_GROSS_REQ_COST_V WHERE FIRM_QUANTITY > 0 ORDER BY FIRM_DATE;
• Aggregate extended cost: SELECT ORGANIZATION_ID, SUM(FIRM_QUANTITY * ITEM_COST) FROM APPS.MTL_GROSS_REQ_COST_V GROUP BY ORGANIZATION_ID;
• Project-specific demand: SELECT DEMAND_ID, PROJECT_ID, TASK_ID, USING_REQUIREMENTS_QUANTITY FROM APPS.MTL_GROSS_REQ_COST_V WHERE PROJECT_ID IS NOT NULL;

Because the view joins costing and planning objects, queries should filter by ORGANIZATION_ID and INVENTORY_ITEM_ID where possible to limit cost view processing, and results should be validated against the active cost method and default cost group resolved through MTL_PARAMETERS.