Results for “using_assembly”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CRP_FORM_QUERY_V view is a denormalized reporting object within the Oracle E-Business Suite Capacity (CRP) module. Its documented purpose is to present a consolidated view of detailed resource requirements, joining the working table CRP_FORM_QUERY to descriptive masters such as departments, resources, production lines, WIP entities, and item flexfields. Rather than exposing raw surrogate identifiers alone, the view resolves those identifiers into human-readable codes and meanings, which makes it suitable for capacity planning reports, form-driven queries, and downstream integrations that need requirement detail without performing the joins themselves.

Because the view belongs to the APPS schema and is distributed as a standard seed object in EBS 12.1.1 and 12.2.2, it can be queried directly by custom reports, concurrent programs, and BI Publisher data templates. It is not a transactional table; all data is derived, and the view does not own or persist any rows of its own.

Underlying Base Objects

The view is defined over nine referenced objects. The driving table is CRP_FORM_QUERY (referenced via synonym CFQ), which stores the resource requirement rows. The remaining objects are joined with outer-join (+) syntax, meaning the base requirement rows are retained even when descriptive data is missing:

• BOM_DEPARTMENTS (BD) — joined on DEPARTMENT_ID to supply DEPARTMENT_CODE.
• BOM_RESOURCES (BR) — joined on RESOURCE_ID to supply RESOURCE_CODE.
• WIP_LINES (WL) — joined on LINE_ID and ORGANIZATION_ID to supply LINE_CODE.
• WIP_ENTITIES (WE) — joined on WIP_ENTITY_ID and ORGANIZATION_ID to supply WIP_ENTITY_NAME.
• MTL_ITEM_FLEXFIELDS (IIF1 and IIF2) — joined on inventory item and organization to supply ITEM_NUMBER for the primary and, where applicable, the using assembly.
• MFG_LOOKUPS (L1 and L2) — joined on lookup code to resolve meaning values; L2 is restricted to lookup type SYS_YES_NO, while L1 selects between CRP_REQUIREMENTS_TYPE and MRP_ORDER_TYPE based on the value in NUMBER9.

Key Columns

The view exposes a broad set of columns. Among the most significant for requirements reporting are:

• QUERY_ID, ROW_ID — surrogate identifiers for the underlying row.
• ORGANIZATION_ID — the inventory organization in which the requirement applies.
• DEPARTMENT_CODE, DEPARTMENT_ID, RESOURCE_CODE, RESOURCE_ID, LINE_CODE, LINE_ID — describing the department, resource, and line associated with the requirement.
• RESOURCE_START_DATE, RESOURCE_END_DATE, SCHEDULE_START_DATE, RATE_END_DATE — the scheduling and rate date boundaries for the requirement.
• REQUIRED_HOURS, LOAD_RATE, DAILY_RESOURCE_HOURS, SCHEDULE_QUANTITY, DAILY_RATE — the capacity load and rate metrics used in capacity planning.
• REQUIREMENT_TYPE — the lookup meaning that classifies the requirement (for example, based on CRP_REQUIREMENTS_TYPE or MRP_ORDER_TYPE). This column is the one most commonly referenced when filtering or grouping requirements by type.
• ORDER_TYPE, ORDER_NUMBER, USING_ASSEMBLY, SO — order and sales-order context.
• FIRM, OP_SEQ_NUMBER — firming status and operation sequence.

Common Use Cases and Queries

The view is typically used to report resource requirements by organization, department, resource, or requirement type, and to reconcile capacity loads against scheduled production. A representative query filtering by the requirement type is shown below:

• SELECT organization_id, department_code, resource_code, requirement_type, required_hours, resource_start_date FROM apps.crp_form_query_v WHERE requirement_type = :p_requirement_type AND organization_id = :p_org_id ORDER BY resource_start_date;
• SELECT requirement_type, SUM(required_hours) FROM apps.crp_form_query_v GROUP BY requirement_type;

Because the view joins several master tables, queries should be filtered by ORGANIZATION_ID and date range to limit the result set. All columns are read-only, and any custom reporting should treat the view as a reporting surface rather than a source for updates.