Results for “wo_part_number”

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

Overview

The APPS.AHL_WORKORDERS_OSP_V view is a reporting and integration construct within the Oracle E-Business Suite AHL (Complex Maintenance Repair and Overhaul) module. Its documented purpose is to present work order information specifically for the Outside Processing (OSP) flow, while excluding master work orders from the result set. This filtering makes the view suitable for operational reporting where only executable, non-master work orders are relevant, such as reviewing outsourced service or repair activities routed to external suppliers.

The view is owned by the APPS schema and holds VALID status in ETRM 12.2.2 and 12.1.1. Because it joins the AHL visit and work order model to WIP discrete jobs, inventory item instances, and Oracle Projects entities, it acts as a consolidated read-only source for scheduled dates, item details, department ownership, and project context. It is not a base table; no DML should be issued against it.

Underlying Base Objects

The view is defined over a set of AHL, WIP, INV, BOM, and Projects synonyms and views. Documented referenced objects include AHL_WORKORDERS, AHL_VISITS_B, AHL_VISIT_TASKS_B, and AHL_ROUTES_B, which supply the work order, visit, visit task, and routing context. WIP_DISCRETE_JOBS supplies scheduling dates and the owning department identifier, joined to the work order through WIP_ENTITY_ID. BOM_DEPARTMENTS resolves the owning department to its class and code.

Item and instance data come from CSI_ITEM_INSTANCES and MTL_SYSTEM_ITEMS_KFV (referenced twice, for the work order part and for the service item). Project context is drawn from PA_PROJECTS_ALL and PA_TASKS. Organization security is enforced through ORG_ORGANIZATION_DEFINITIONS combined with MO_GLOBAL, HR_GENERAL, and HR_SECURITY, which apply operating unit and client information restrictions.

Key Columns

Identification columns include WORKORDER_ID, JOB_NUMBER (aliased from WORKORDER_NAME), OBJECT_VERSION_NUMBER, and ORGANIZATION_ID. Status and classification are exposed through JOB_STATUS_CODE, DEPARTMENT_ID, DEPARTMENT_CLASS_CODE, and DEPARTMENT_CODE.

Scheduling columns are central to the view. SCHEDULED_START_DATE is sourced from WDJ.SCHEDULED_START_DATE, and the column the user searched for, SCHEDULED_END_DATE, is an alias of WDJ.SCHEDULED_COMPLETION_DATE from WIP_DISCRETE_JOBS. Actual execution dates are provided by ACTUAL_START_DATE and ACTUAL_END_DATE. Item columns include INVENTORY_ITEM_ID, ITEM_INSTANCE_ID, ITEM_INSTANCE_NUMBER, WO_PART_NUMBER, ITEM_DESCRIPTION, SERIAL_NUMBER, and ITEM_INSTANCE_UOM. Service, visit, and project columns include SERVICE_ITEM_ID, SERVICE_ITEM_NUMBER, SERVICE_ITEM_UOM, VISIT_ID, VISIT_TASK_ID, ROUTE_ID, PROJECT_ID, PROJECT_NAME, PROJECT_TASK_ID, and PROJECT_TASK_NAME.

Common Use Cases and Queries

Typical uses include OSP work order lists sorted by scheduled completion, department workload reviews, and project-linked outside processing reports. The following query retrieves open work orders and their scheduled end dates within the current operating unit context.

• SELECT job_number, job_status_code, scheduled_start_date, scheduled_end_date, wo_part_number
• FROM apps.ahl_workorders_osp_v
• WHERE job_status_code NOT IN ('COMPLETE','CLOSED')
• ORDER BY scheduled_end_date;

Because the view applies organization security through ORG_ORGANIZATION_DEFINITIONS and MO_GLOBAL, results are restricted to organizations accessible to the current responsibility and client information. Reports requiring past-due analysis can compare scheduled_end_date against SYSDATE, while project-driven reporting can group by project_name and project_task_name. Querying the view directly avoids reimplementing the multi-table join and ensures consistent exclusion of master work orders.