Search Results elapsed_days




Overview
Explore in AI Chat

Overview

PA_ROUTING_HISTORY_V is an Oracle Applications (APPS) view in the Projects (PA) product family. The ETRM metadata classifies its description as "10SC Only," indicating the view exists primarily to support a specific 10SC (Oracle internal / special-consolidation) reporting requirement rather than the mainstream Projects transaction flow. Its status is VALID, and it is owned by the APPS schema in both Oracle EBS 12.1.1 and 12.2.2.

The view presents a denormalized, human-readable history of expenditure routing events. It joins the routing transaction table PA_ROUTINGS to the PER_PEOPLE_F person view and the PA_LOOKUPS lookup view, so consumers can report on who routed an expenditure, to whom it was routed, the routing status (as a decoded meaning), the routing date, and the elapsed time in days. Because it exposes ELAPSED_DAYS, it is commonly queried for aging and turnaround-time analysis of routed expenditures. The view is a reporting/integration convenience layer, not a transactional base table.

Underlying Base Objects

The documented base objects referenced by this view are:

  • PA_ROUTINGS (SYNONYM) — the primary transactional source, aliased RT, supplying routing, person, status, date, and comment columns.
  • PER_PEOPLE_F (VIEW) — joined twice (aliases EF for the routing originator and ET for the routing recipient) to resolve full names.
  • PA_LOOKUPS (VIEW) — aliased RA, providing the decoded meaning for the routing status code.
  • HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), and HR_SECURITY (PACKAGE) — referenced HR utility packages used by the underlying person / security logic.

The view text selects from PA_LOOKUPS, PER_PEOPLE_F (twice), and PA_ROUTINGS, joining on PERSON_ID with an effective-date filter (TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE) and requiring either EMPLOYEE_NUMBER or NPW_NUMBER to be populated. The lookup join uses LOOKUP_TYPE = 'ROUTING STATUS CODE'. Note that the effective-date predicates on both person joins mean only currently effective person records are returned.

Key Columns

Common Use Cases and Queries

Typical uses include aging reports for routed expenditures, workload analysis by recipient, and status summary dashboards. ELAPSED_DAYS is the focal column for turnaround analysis.

  • Open routings aging: SELECT EXPENDITURE_ID, ROUTED_TO_FULL_NAME, ROUTING_DATE, ELAPSED_DAYS FROM APPS.PA_ROUTING_HISTORY_V WHERE ROUTING_STATUS_CODE <> 'CLOSED' ORDER BY ELAPSED_DAYS DESC;
  • Average days by recipient: SELECT ROUTED_TO_FULL_NAME, ROUND(AVG(ELAPSED_DAYS),1) AVG_DAYS FROM APPS.PA_ROUTING_HISTORY_V GROUP BY ROUTED_TO_FULL_NAME;
  • History for one expenditure: SELECT ROUTED_FROM_FULL_NAME, ROUTED_TO_FULL_NAME, ROUTING_STATUS, ROUTING_DATE, ELAPSED_DAYS FROM APPS.PA_ROUTING_HISTORY_V WHERE EXPENDITURE_ID = :exp_id;

Because PER_PEOPLE_F security and effective-dating are embedded, results reflect only currently effective, security-accessible person records. As the view is documented "10SC Only," confirm availability in the target instance before relying on it.