Results for “job_status_code”

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

Overview

The AHL_WIP_RESOURCE_TXNS_V view in the APPS schema is a reporting and integration object within the Oracle E-Business Suite AHL (Complex Maintenance Repair and Overhaul) product family. It exposes work order resource transaction activity by joining AHL work order header data to the underlying Oracle Work in Process (WIP) transaction tables. Because AHL leverages standard WIP and BOM infrastructure to model maintenance and overhaul execution, this view provides the consolidated perspective required by MRO reporting, cost analysis, and external system integration.

The view is defined as a SELECT DISTINCT over the join of AHL work orders, WIP resource transactions, BOM resource and department definitions, HR person data, units of measure, transaction reasons, cost activities, and WIP operation resource instances. Its status is VALID and it is available in both 12.1.1 and 12.2.2 environments. The view surfaces the JOB_STATUS_MEANING column, which is the user-friendly description behind the work order JOB_STATUS_CODE, a common search target for operational reporting.

Underlying Base Objects

The documented base objects include synonyms and views such as AHL_WORKORDERS, WIP_TRANSACTIONS, WIP_ENTITIES, WIP_OPERATION_RESOURCES, BOM_RESOURCES, BOM_DEPARTMENTS, MTL_TRANSACTION_REASONS, MTL_UNITS_OF_MEASURE, CST_ACTIVITIES, and PER_PEOPLE_F. The view also references FND_LOOKUP_VALUES_VL, MFG_LOOKUPS, and the HR packages HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. Join predicates link WIP_TRANSACTIONS to AHL work orders on WIP_ENTITY_ID, to resources on RESOURCE_ID, to departments on DEPARTMENT_ID, to UOM on PRIMARY_UOM, and to operation resource instances on the combination of WIP entity, operation sequence, and resource sequence. Outer joins preserve transactions lacking a defined reason, activity, or employee.

Key Columns

• TRANSACTION_ID — Unique identifier of the WIP resource transaction.
• WORKORDER_ID, JOB_NUMBER, WIP_ENTITY_ID — Work order identifiers.
• OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM — Operation and resource sequence within the routing.
• EMPLOYEE_ID, EMPLOYEE_NUMBER, FULL_NAME — Personnel who performed the work.
• RESOURCE_CODE, DESCRIPTION, DEPARTMENT_ID, DEPT_DESCRIPTION — Resource and department context.
• QUANTITY, USAGE_RATE_OR_AMOUNT, PRIMARY_UOM, UOM_MEANING — Quantity, usage rate, and unit of measure.
• ACTIVITY_ID, ACTIVITY, REASON_ID, REASON_NAME, REFERENCE — Cost activity, transaction reason, and reference text.
• INSTANCE_ID, SERIAL_NUMBER — Instance-level tracking applied to the resource.
• TRANSACTION_DATE, VISIT_TASK_ID — Transaction timestamp and associated visit task.
• JOB_STATUS_CODE, JOB_STATUS_MEANING — Work order status code and its descriptive meaning, the field commonly retrieved for status reporting.

Common Use Cases and Queries

Typical uses include labor and resource consumption reporting, work order status dashboards, and reconciliation of maintenance execution against cost activities. The following query retrieves resource transactions with descriptive job status:

SELECT job_number,
       job_status_meaning,
       resource_code,
       full_name,
       quantity,
       uom_meaning,
       transaction_date
FROM   apps.ahl_wip_resource_txns_v
WHERE  transaction_date >= TRUNC(SYSDATE) - 30
ORDER  BY transaction_date DESC;

To aggregate resource usage by job:

SELECT job_number,
       job_status_meaning,
       SUM(quantity) total_qty
FROM   apps.ahl_wip_resource_txns_v
GROUP  BY job_number, job_status_meaning;

Because the view applies SELECT DISTINCT, callers should avoid assuming one row per transaction when duplicate join combinations exist; distinct filtering removes redundant rows but can mask intended multiplicity in edge cases.