Results for “item_date”

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

Overview

APPS.PA_REP_RES_SCHHRS_WK_V is a reporting view within the Oracle Projects (PA) module that presents scheduled resource hours aggregated to a global week. It is designed to expose forecast item quantities for resources, distinguishing between confirmed and provisional hours, and aligning each record to the global expense period end date that defines a given global week.

The view is primarily consumed by Oracle Projects reporting and integration components that require a weekly, resource-level rollup of scheduled effort. Because it derives its week definition from PA_REP_PERIODS_V, it is tightly coupled to the global expense (GE) period calendar, which is a standard mechanism in Oracle EBS for organizing project reporting periods across operating units. In EBS 12.1.1 and 12.2.2, the view retains a VALID status and remains owned by the APPS schema.

The user search term "item_date" corresponds directly to one of the view's exposed columns. ITEM_DATE carries the specific forecast item date, derived from PA_FORECAST_ITEMS, and is central to how scheduled hours are bucketed into weekly reporting periods.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_FORECAST_ITEMS (accessed via synonym) — the primary transactional source providing forecast resource hours, item dates, and provisional flags.
• PA_REP_PERIODS_V (view) — supplies period year, month or quarter, and the global expense week date used for the weekly join.
• FND_PROFILE (package) — referenced for profile option resolution.
• PA_PERIOD_PROCESS_PKG (package) — referenced as part of the period processing logic used by the underlying objects.

The join between PA_FORECAST_ITEMS and PA_REP_PERIODS_V is performed on GLOBAL_EXP_PERIOD_END_DATE matching PRPV.GE_WEEK_DT, with the additional constraint that PERIOD_TYPE equals 'GE'. The view text further filters FORECAST_ITEM_TYPE to 'A' and DELETE_FLAG to 'N', ensuring only active, non-deleted scheduled forecast items are reported. Provisional and confirmed quantities are separated using a DECODE on PROVISIONAL_FLAG.

Key Columns

• YEAR — the period year from the global expense period definition.
• MONTH — the month or quarter indicator (MON_OR_QTR) associated with the period.
• GLOBAL_WEEK — the global expense week end date (GLOBAL_EXP_PERIOD_END_DATE).
• ITEM_DATE — the forecast item date from PA_FORECAST_ITEMS, representing when the scheduled resource effort applies.
• CONFIRMED_HOURS — item quantity returned when PROVISIONAL_FLAG is 'N' (otherwise zero).
• PROVISIONAL_HOURS — item quantity returned when PROVISIONAL_FLAG is 'Y' (otherwise zero).
• RESOURCE_ID — identifier of the resource to which the scheduled hours belong.

Common Use Cases and Queries

Typical uses include weekly resource scheduling reports, project effort forecasting, and reconciliation between confirmed and provisional scheduled hours. Because the view separates confirmed and provisional quantities into distinct columns, report authors can sum each independently for a given global week and resource.

Example query returning scheduled hours for a resource across global weeks:

SELECT year, month, global_week, item_date,
       confirmed_hours, provisional_hours, resource_id
FROM   apps.pa_rep_res_schhrs_wk_v
WHERE  resource_id = :p_resource_id
ORDER  BY global_week, item_date;

Example aggregation of total scheduled effort per week:

SELECT global_week,
       SUM(confirmed_hours)   AS confirmed_total,
       SUM(provisional_hours) AS provisional_total
FROM   apps.pa_rep_res_schhrs_wk_v
GROUP  BY global_week
ORDER  BY global_week;

When filtering on ITEM_DATE, note that it reflects the forecast item date rather than the global week end date; the two may differ within the same weekly bucket. Reports should therefore select both columns when precise item-level timing is required.