Search Results required_end_date

Overview

AHL_PP_REQUIREMENT_V is an Oracle E-Business Suite reporting view owned by the APPS schema and delivered as part of the AHL (Complex Maintenance Repair and Overhaul) product family. Its purpose is to expose operation resource requirements — the materials, labor, and equipment that work orders consume at the operation level — in a single denormalized result set suitable for reporting, inquiry, and integration. The naming convention "PP" refers to the Production/planning-related requirement concept, and the view consolidates data from work order headers, work order operations, operation resources, the BOM resource master, and associated lookup and unit-of-measure reference data.

In EBS 12.1.1 and 12.2.2 the view carries a status of VALID and is documented in the ETRM repository. It is read-only by definition and should never be used as a DML target; it is intended strictly for SELECT-based consumption in reports, concurrent programs, and inbound or outbound interfaces that need a flattened picture of resource demand against scheduled maintenance or repair work.

Underlying Base Objects

The view is defined over a mixture of AHL synonyms and shared manufacturing tables. The documented base objects are AHL_WORKORDERS, AHL_WORKORDER_OPERATIONS, AHL_OPERATION_RESOURCES, BOM_RESOURCES, MFG_LOOKUPS (exposed through FND_LOOKUP_VALUES_VL for the resource type meaning), and MTL_UNITS_OF_MEASURE. Additional referenced objects include AHL_OPERATIONS_VL, WIP_OPERATIONS, and WIP_OPERATION_RESOURCES.

The driving table is AHL_OPERATION_RESOURCES, joined to AHL_WORKORDER_OPERATIONS on WORKORDER_OPERATION_ID and to the work order header on WORKORDER_ID. BOM_RESOURCES is joined on RESOURCE_ID to supply the resource code, description, type, and unit of measure. The lookup join to MFGL is an outer join keyed on LOOKUP_TYPE = 'BOM_RESOURCE_TYPE', and the unit-of-measure join is also outer, so rows survive missing lookup or UOM definitions. This outer-join structure is important: it guarantees that every operation resource row is returned even when reference data is incomplete.

Key Columns

• REQUIREMENT_ID — Sourced from AHL_OPERATION_RESOURCES.OPERATION_RESOURCE_ID; the unique identifier of the resource requirement.
• RESOURCE_ID / RESOURCE_CODE / RESOURCE_NAME — The BOM resource key and its descriptive attributes.
• JOB_ID / OPERATION_ID / OPERATION_SEQUENCE — Work order and operation identifiers, with sequence for ordering.
• OPERATION_STATUS_CODE / STATUS / JOB_STATUS_CODE / JOB_STATUS_MEANING — Status fields at both operation and work order (job) level.
• REQUIRED_START_DATE / REQUIRED_END_DATE, OPERATION_START_DATE / OPERATION_END_DATE — Scheduled requirement windows versus the parent operation schedule.
• RESOURCE_TYPE_CODE / RESOURCE_TYPE_NAME — Resource classification and its lookup meaning.
• DURATION, QUANTITY, TOTAL_REQUIRED — Duration, quantity, and the computed product (DURATION * QUANTITY).
• UOM_CODE / UOM_NAME — Unit of measure code and description.
• VISIT_TASK_ID — Link back to the visit task driving the work order.

Common Use Cases and Queries

Typical uses include resource loading reports, maintenance scheduling dashboards, and extraction feeds into planning systems. A representative query returns requirements for a given work order:

SELECT requirement_id, resource_code, resource_name, operation_sequence, required_start_date, quantity, uom_code FROM ahl_pp_requirement_v WHERE job_id = :p_workorder_id ORDER BY operation_sequence, resource_sequence;

For capacity analysis, aggregate by resource type and date window:

SELECT resource_type_name, required_start_date, SUM(total_required) FROM ahl_pp_requirement_v WHERE required_start_date BETWEEN :p_from AND :p_to GROUP BY resource_type_name, required_start_date;

Because joins to lookup and UOM data are outer, filters on RESOURCE_TYPE_NAME or UOM_NAME should account for possible NULLs. Always constrain queries by JOB_ID, date range, or status to avoid full scans across large maintenance histories.