Results for “resource_offset_percent”

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

Overview

The APPS.MRPBV_PLAN_OPERATION_RESOURCES view is a reporting and integration object within the Oracle E-Business Suite MRP (Master Scheduling/MRP) module, exposed in both 12.1.1 and 12.2.2. It presents planned resource requirements at the routing operation level, joined to the organization, item, and system item context needed to interpret planning results. The view is read-only (defined with WITH READ ONLY) and carries a status of VALID in the ETRM metadata. Its purpose is to flatten the normalized planning tables into a single denormalized result set suitable for concurrent program output, BI Publisher reports, Oracle Discoverer workbooks, and custom SQL integrations. The view's naming convention—the "BV" segment and the presence of a key flexfield placeholder column (rendered as "_KF:ITEM_NUMBER") and a row-level security predicate ("_SEC:ROUTING.ORGANIZATION_ID")—indicates it is part of the seeded business view layer used by Oracle's planning workbench and reporting infrastructure rather than a user-facing transactional table.

Underlying Base Objects

The view is defined over five documented base objects (all accessed as SYNONYMs in the APPS schema): HR_ALL_ORGANIZATION_UNITS, MRP_PLANNED_RESOURCE_REQS, MRP_SYSTEM_ITEMS, MTL_PARAMETERS, and MTL_SYSTEM_ITEMS. MRP_PLANNED_RESOURCE_REQS is the primary driver, supplying the routing-level planning data for each operation and resource. MRP_SYSTEM_ITEMS provides the planning context (organization and compile designator) of the assembly, and MTL_SYSTEM_ITEMS supplies the inventory item identity. MTL_PARAMETERS provides the organization code, while HR_ALL_ORGANIZATION_UNITS supplies the organization name. The joins are keyed on ORGANIZATION_ID, COMPILE_DESIGNATOR, and USING_ASSEMBLY_ITEM_ID/INVENTORY_ITEM_ID, ensuring that resource requirements resolve consistently for the assembly being planned. A DISTINCT clause eliminates duplication introduced by the master-data joins.

Key Columns

• ORGANIZATION_CODE / ORGANIZATION_NAME — Warehouse/plant identifier and its descriptive name.
• PLAN_NAME — The MRP plan under which the resource requirement was generated.
• "_KF:ITEM_NUMBER" — The assembly item number surfaced through the item key flexfield.
• ALTERNATE_ROUTING_CODE — Alternate routing designator applied to the assembly.
• OPERATION_SEQUENCE_NUMBER — The routing operation sequence the resource is attached to.
• RESOURCE_SEQUENCE_NUMBER — Ordering of the resource within the operation.
• RESOURCE_OFFSET_PERCENT — Offset percentage used to schedule the resource relative to operation start.
• OPERATION_BASIS — The basis on which resource usage is calculated (per item, per lot, etc.).
• SETBACK_DAYS — Number of days the resource is set back from the operation start.
• ASSEMBLY_USAGE — This column corresponds directly to the user's search term "assembly_usage"; it exposes the assembly usage indicator associated with the planned operation resource, distinguishing how the assembly consumes or drives the resource requirement.
• ORGANIZATION_ID, USING_ASSEMBLY_ITEM_ID, RESOURCE_ID, DEPARTMENT_ID — Surrogate keys enabling joins back to standard master and transactional tables.

Common Use Cases and Queries

Typical applications include extracting planned resource loads by operation for capacity analysis, feeding external scheduling tools, and auditing assembly usage across routings. A basic extraction of resource requirements for a plan might read:

• SELECT organization_code, organization_name, plan_name, "ASSEMBLY_USAGE", operation_sequence_number, resource_sequence_number, resource_offset_percent, operation_basis, setback_days FROM apps.mrpv_plan_operation_resources WHERE plan_name = :p_plan AND organization_code = :p_org;

Because the view is read-only and carries the organization security predicate, queries executed under standard EBS responsibilities automatically filter to organizations the user is authorized to access. Joining RESOURCE_ID to BOM_RESOURCES or DEPARTMENT_ID to BOM_DEPARTMENTS enriches the output with resource and department descriptions for reporting.