Search Results gl_start_date




Overview
Explore in AI Chat

Overview

PA_EXP_CAT_GL_VIEW is a reporting view in the Oracle E-Business Suite Projects (PA) module that presents actual cost and revenue totals for projects and tasks, aggregated by General Ledger period and expenditure category. Its documented description identifies it explicitly as "R10SC Only," indicating that it originated as a release-specific, single-source reporting construct rather than a general-purpose application object. The view consolidates transactional project data into period-level summaries, joining cost and revenue measures alongside budgeted and billable amounts, so that project accountants and reporting tools may compare actuals to budgets at a consistent GL period grain.

In Oracle EBS 12.1.1 and 12.2.2, the view is documented in the ETRM repository as "Not implemented in this database." This is a significant operational fact: although the object appears in the data dictionary metadata, it is not deployed in the reference environment. Consequently, any report or interface that references PA_EXP_CAT_GL_VIEW must first confirm its existence in the target instance. The searched term "gl_start_date" corresponds directly to one of the view's grouping columns, GL_START_DATE, which carries the first calendar date of the GL period to which the summarized amounts belong.

Underlying Base Objects

The ETRM metadata records no referenced base objects for this view ("none documented"), and it is not implemented in the documented database. The view text therefore cannot be resolved into a documented dependency chain within the metadata set. However, the SELECT structure reveals a canonical aggregation pattern over project expenditure and revenue data: a set of measure columns is summed and rounded, then grouped by PROJECT_ID, TASK_ID, GL_PERIOD, GL_START_DATE, GL_END_DATE, and EXPENDITURE_CATEGORY. In the standard Projects data model, such a query is characteristically defined over expenditure and revenue summary sources—typically the expenditure category actuals and project revenue/draft revenue tables joined through the GL period calendar—so that all measure columns inherit the same period and category granularity.

Key Columns

  • PROJECT_ID — Identifier of the project to which the summarized amounts belong.
  • TASK_ID — Identifier of the task within the project; combined with PROJECT_ID it forms the project/task pairing at which totals are reported.
  • GL_PERIOD — The GL accounting period name used as the primary reporting time bucket.
  • GL_START_DATE — The calendar start date of the GL period. This is the column most directly associated with the user search term "gl_start_date" and is included in the GROUP BY clause, so each row carries the period's opening date.
  • GL_END_DATE — The calendar end date of the GL period.
  • EXPENDITURE_CATEGORY — The expenditure category that classifies the summarized cost, revenue, and quantity figures.
  • TOTAL_REVENUE, TOTAL_RAW_COST, TOTAL_BURDEN_COST — Rounded sums of actual revenue, raw cost, and burdened cost respectively.
  • TOTAL_QUANTITY, TOTAL_LABOR_HOURS — Rounded sums of total quantity and total labor hours.
  • BILLABLE_RAW_COST, BILLABLE_BURDEN_COST, BILLABLE_QUANTITY, BILLABLE_LABOR_HOURS — Rounded billable subsets of the corresponding actual measures.
  • BUDGETED_COST, BUDGETED_REVENUE, BUDGETED_LABOR_HOURS — Rounded budgeted amounts reported on the same period and category grain, enabling variance analysis.

Common Use Cases and Queries

Because all measures are aggregated to GL period, project, task, and expenditure category, the view is suited to period-by-period cost and revenue reporting, budget-to-actual comparison, billable versus non-billable analysis, and labor hour trending. A typical query filters on a project and a GL period range using GL_START_DATE, then orders chronologically:

  • SELECT project_id, task_id, gl_period, gl_start_date, gl_end_date, expenditure_category, total_revenue, total_raw_cost, total_burden_cost, budgeted_cost FROM pa_exp_cat_gl_view WHERE project_id = :p_project_id AND gl_start_date BETWEEN :p_from_date AND :p_to_date ORDER BY gl_start_date, task_id, expenditure_category;

For billable margin analysis by category, the billable columns may be compared against budgeted revenue:

  • SELECT expenditure_category, SUM(billable_raw_cost) billable_cost, SUM(total_revenue) revenue, SUM(budgeted_revenue) budget FROM pa_exp_cat_gl_view WHERE gl_period BETWEEN :p_period_from AND :p_period_to GROUP BY expenditure_category;

Before deploying any such query in EBS 12.1.1 or 12.2.2, confirm the object's presence, since the reference metadata states it is not implemented in the database. Where it is absent, equivalent period/category sums must be obtained directly from the underlying project expenditure and revenue summary tables.