Results for “expenditure_id”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_ROUTINGS is a Projects (PA) module table that records the individual steps in the approval cycle for online timecards and expense reports within Oracle E-Business Suite 12.1.1 and 12.2.2. Each row captures a discrete routing event in which an expenditure item or report is passed from one approver to another, together with the resulting routing status and any accompanying comment. The table therefore serves as the transactional audit trail of the approval workflow, distinct from the expenditure records themselves.

From a dimensional modeling perspective, the documented foreign key structure suggests a satellite-leaning classification. The table's sole foreign key points to PA_EXPENDITURES_ALL through EXPENDITURE_ID, and its primary key is a composite of EXPENDITURE_ID and START_DATE. This structure indicates that PA_ROUTINGS behaves as a dependent, time-versioned extension of the expenditure record rather than as an independent hub or a link between two business entities.

Key Information Stored

The table contains twelve documented columns. The most operationally significant are listed below.

  • EXPENDITURE_ID — The foreign key to PA_EXPENDITURES_ALL and part of the composite primary key. Identifies the expenditure item, timecard, or expense report associated with the routing step.
  • START_DATE — The effective start date of the routing step and the second component of the composite primary key. It anchors each routing record in time, allowing multiple sequential steps to be stored for the same expenditure.
  • END_DATE — The date on which the routing step concluded or was superseded.
  • ROUTED_FROM_PERSON_ID — The person initiating or forwarding the approval step.
  • ROUTED_TO_PERSON_ID — The person to whom the item was routed for approval action.
  • ROUTING_STATUS_CODE — The status of the routing step, indicating whether it is pending, approved, rejected, or otherwise resolved.
  • ROUTING_COMMENT — Free-text commentary recorded by the approver or the routing process.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified the row and when.

The primary key, PA_ROUTINGS_PK, is defined on (EXPENDITURE_ID, START_DATE). The unique index PA_ROUTINGS_U1 covers the same two columns and is the documented business-key candidate, reinforcing that no two routing steps may begin at the same instant for the same expenditure. No separate surrogate key column is documented; the composite natural key serves as the row identifier.

Common Use Cases and Queries

PA_ROUTINGS is primarily queried to reconstruct approval history, identify current approvers, and analyze cycle times in the timecard and expense approval process.

  • Current routing step for an expenditure: Join PA_ROUTINGS to PA_EXPENDITURES_ALL on EXPENDITURE_ID and filter where END_DATE is null or ROUTING_STATUS_CODE indicates a pending state.
  • Approval history audit: Select all rows for a given EXPENDITURE_ID ordered by START_DATE to display the sequence of approvers between ROUTED_FROM_PERSON_ID and ROUTED_TO_PERSON_ID.
  • Cycle-time reporting: Compute the interval between START_DATE and END_DATE across routing steps to measure approver turnaround.
  • Rejection analysis: Aggregate ROUTING_COMMENT and ROUTING_STATUS_CODE to identify frequent rejection points in the workflow.

A representative query pattern selects EXPENDITURE_ID, ROUTED_TO_PERSON_ID, ROUTING_STATUS_CODE, START_DATE, and END_DATE from PA_ROUTINGS where EXPENDITURE_ID equals a supplied value, ordered by START_DATE.

Related Objects

The following objects are most significant to working with PA_ROUTINGS.

  • PA_EXPENDITURES_ALL — The referenced parent table; joined via PA_ROUTINGS.EXPENDITURE_ID. Provides the expenditure item, timecard, and expense report context.
  • PA_EXPENDITURES — The non-ALL variant frequently used in project expenditure reporting alongside the routing records.
  • PER_ALL_PEOPLE_F — The standard source for resolving ROUTED_FROM_PERSON_ID and ROUTED_TO_PERSON_ID into person names and assignments.
  • PA_EXPENDITURE_TYPES — Classifies the expenditure involved, supporting workflow segmentation by type.
  • PA_PROJECTS_ALL — Links routed expenditures back to their owning projects for project-level approval reporting.
  • FND_LOOKUPS — Typically holds the valid values behind ROUTING_STATUS_CODE for decoding statuses in reports.

Together these objects allow the routing trail to be reported end to end, from approver identity through expenditure, project, and final status.