Results for “crp_resource_v”

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

Overview

CRP_RESOURCE_V is an internal Oracle EBS view owned by the APPS schema within the CRP (Capacity) product module. It is documented in ETRM as a performance-oriented construct rather than a functional interface, and its status is VALID across Oracle EBS 12.1.1 and 12.2.2. The view provides a unified, consolidated result set of resource planning rows drawn from three distinct source objects, allowing capacity and material planning logic to query a single structure instead of issuing separate statements against each contributing table. Because the view is described as internal for performance, it should be treated as a supporting object rather than a supported end-user or integration interface; direct dependencies on it are typically limited to Oracle-supplied capacity planning programs and concurrent processes.

Underlying Base Objects

Per the documented view text, CRP_RESOURCE_V is defined as a UNION ALL over three referenced base objects, all resolved through SYNONYM entries in the APPS schema: CRP_RESOURCE_PLAN, MRP_SUGG_REP_SCHEDULES, and MRP_RECOMMENDATIONS.

• CRP_RESOURCE_PLAN — the primary capacity planning source, contributing resource plan rows directly (alias RES).
• MRP_SUGG_REP_SCHEDULES — supplies repetitive schedule suggestions (alias SUGG), synthesized into the unified column list.
• MRP_RECOMMENDATIONS — supplies planning recommendations (alias MR), filtered so that only rows with a disposition status other than 2, a non-null LINE_ID, and an ORDER_TYPE not in (13, 16, 4) are included.

Because the definition uses UNION ALL, duplicate rows are preserved and no distinct processing is applied. Literal substitutions are used to satisfy the shared column list for the second and third branches: TRANSACTION_ID and RESOURCE_ID receive -2 for MRP_RECOMMENDATIONS and -1 for MRP_SUGG_REP_SCHEDULES. This is directly relevant to the search term mrp_sugg_rep_schedules, which appears as one of the three documented source objects behind this view.

Key Columns

The view exposes a fixed eight-column projection. The documented columns are:

• ROW_ID — the ROWID of the originating base table row, carried through from each branch (RES.ROWID, SUGG.ROWID, MR.ROWID).
• TRANSACTION_ID — the originating transaction identifier; hard-coded to -1 for repetitive schedule suggestions and -2 for MRP recommendations.
• ORGANIZATION_ID — the inventory organization context for the planning row.
• COMPILE_DESIGNATOR — the plan or compile designator under which the row was generated.
• DEPARTMENT_ID — the department associated with the capacity row; mapped from REPETITIVE_LINE for repetitive schedules and LINE_ID for recommendations.
• RESOURCE_ID — the resource identifier; only populated from CRP_RESOURCE_PLAN, with -1 for the other two branches.
• ASSEMBLY_ITEM_ID — the assembly item; sourced from ASSEMBLY_ITEM_ID for resource plan rows and INVENTORY_ITEM_ID for the other branches.
• SOURCE_TRANSACTION_ID — the upstream transaction from which the capacity row originated.

Common Use Cases and Queries

Practical use is concentrated in capacity planning diagnostics and reconciliation. A typical query retrieves all rows for an organization and plan, using SOURCE_TRANSACTION_ID to trace how repetitive schedule and recommendation data fold into the capacity picture. Note that the negative TRANSACTION_ID sentinel values identify which underlying source produced each row.

A representative query:

• SELECT transaction_id, organization_id, compile_designator, department_id, resource_id, assembly_item_id, source_transaction_id FROM apps.crp_resource_v WHERE organization_id = :org_id AND compile_designator = :designator;
• To isolate repetitive schedule suggestions: SELECT * FROM apps.crp_resource_v WHERE transaction_id = -1;
• To isolate MRP recommendation rows: SELECT * FROM apps.crp_resource_v WHERE transaction_id = -2;
• To isolate native resource plan rows: SELECT * FROM apps.crp_resource_v WHERE transaction_id <> -1 AND transaction_id <> -2;

Queries should be used for investigation and validation only. The internal designation and the reliance on ROWID-based retrieval mean consumers should prefer documented base tables for persistent integration requirements.