Search Results operation_end_date




Overview
Explore in AI Chat

Overview

APPS.AHL_PP_ASSIGNMENT_V is a reporting and integration view within the Oracle E-Business Suite AHL (Complex Maintenance Repair and Overhaul) product. It consolidates work assignment records with the operation resource requirements they satisfy, producing a single denormalized result set that joins employee assignment data to the production plan requirements for a maintainable unit. In EBS 12.1.1 and 12.2.2 the view is registered as VALID under the APPS schema and is exposed to reporting tools, concurrent programs, and custom extensions without requiring the consumer to reconstruct the multi-table join themselves.

The view is particularly relevant when resolving the frequently searched operation_resource_id column. That identifier is the foreign key that binds an assignment row in AHL_WORK_ASSIGNMENTS to the specific resource requirement row in the AHL production plan, and the view surfaces it under the alias OPERATION_RESOURCE_ID so that both the assignment and its associated requirement context are available together.

Underlying Base Objects

The documented view text is a UNION of two SELECT statements over the same four sources, differing only in whether the employee name attributes are populated. The referenced objects are:

  • AHL_WORK_ASSIGNMENTS (synonym) — the driving table, aliased AWAS, supplying assignment identifiers, employee references, assignment start and end dates, instance and serial number, and the OPERATION_RESOURCE_ID link.
  • AHL_PP_REQUIREMENT_V (view) — aliased APRV, supplying job, operation, sequence, operation status, scheduled start and end dates, resource type, resource, and requirement identifiers.
  • PER_PEOPLE_F (view) and PER_PERSON_TYPES (synonym) — used to resolve the employee number and full name, restricted to the system person type 'EMP'.
  • HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (packages) — invoked indirectly through the PER_PEOPLE_F and PER_PERSON_TYPES layers to enforce person type and security filtering.

The join predicate AWAS.OPERATION_RESOURCE_ID = APRV.REQUIREMENT_ID is the structural core of the view, and the UNION branch returns NULL for employee number and name where no matching employee record applies. This supports both named-employee assignment reporting and generic resource assignment reporting from a single object.

Key Columns

Common Use Cases and Queries

Typical scenarios include resource utilization reporting, workload leveling, assignment-to-operation reconciliation, and integration extracts into scheduling or MES systems. Because the view already joins employees and resources, it removes substantial query complexity.

  • List all assignments for a given operation resource: SELECT assignment_id, employee_name, resource_code, assignment_start_date FROM ahl_pp_assignment_v WHERE operation_resource_id = :p_requirement_id;
  • Find assignments for a maintainable unit: SELECT serial_number, operation_sequence, resource_name, employee_name FROM ahl_pp_assignment_v WHERE instance_id = :p_instance_id ORDER BY operation_sequence, resource_sequence;
  • Report open operation assignments for an employee: SELECT operation_id, operation_status_meaning, assignment_end_date FROM ahl_pp_assignment_v WHERE employee_id = :p_employee_id AND operation_status_code NOT IN ('COMPLETE','CLOSED');

Consumers should note that the view inherits HR security through the PER_PEOPLE_F layer, so row visibility respects the operating user's person security profile, and that all access should be performed through the APPS schema synonym or with appropriate APPS credentials.