Search Results project_bookings_and_backlog

Overview

APPS.PJI_DEFAULT_PERIOD_SETTINGS_V is a reporting view in Oracle EBS Release 12.1.1 and 12.2.2 that exposes the system-level default period settings used by the Project Intelligence (PJI) reporting framework. The view consolidates, for each PJI report group, the default period type, the default as-of date, and the default billing cycle that the application applies when a report is executed without user-specified period parameters. It effectively flattens the singleton row held in PJI_SYSTEM_SETTINGS into one logical row per report group, joining each group to its descriptive lookup meaning and to the referenced billing cycle name.

Because the definition is a UNION ALL across several PJI report groups — PROJECT_BOOKINGS_AND_BACKLOG, RESOURCE_UTILIZATION, RESOURCE_AVAILABILITY, PROJECT_ACTIVITY, PROJECT_PROFITABILITY, and PROJECT_COST — the view presents a normalized result set where a single MEANING column identifies the report group and a single BILLING_CYCLE_NAME column exposes the resolved billing cycle. This view is a primary reference for anyone searching on the term "billing_cycle_name," since that column is directly projected from PA_BILLING_CYCLES for each of the report groups.

Underlying Base Objects

The view is defined over the following documented base objects:

• PJI_SYSTEM_SETTINGS (synonym) — the source of the default period type, as-of date, and cycle ID columns for each report group. This is the driving table of each branch of the UNION ALL.
• PA_BILLING_CYCLES (synonym) — the source of BILLING_CYCLE_NAME. It is outer-joined (denoted by the (+) operator) to PJI_SYSTEM_SETTINGS on the respective default cycle ID, so a row is still returned even where no billing cycle is configured.
• PJI_LOOKUPS (view) — supplies the lookup meaning for the report groups, filtered on lookup_type = 'PJI_REPORT_GROUP' and the specific lookup_code for each branch.
• FND_GLOBAL (package) — referenced for session/context resolution within the PJI reporting stack.

The relationship is therefore many-to-one from each setting column to PA_BILLING_CYCLES and to PJI_LOOKUPS, with the outer join guaranteeing that unconfigured defaults still appear with a null cycle name.

Key Columns

• MEANING — the descriptive lookup meaning of the PJI report group (for example, Project Bookings and Backlog or Resource Utilization), drawn from PJI_LOOKUPS.
• SETTING_ID — the primary key from PJI_SYSTEM_SETTINGS, identifying the settings row.
• <GROUP>_PERIOD_TYPE — the default period type for the group, such as DFLT_PRJBAB_PERIOD_TYPE, DFLT_RESUTL_PERIOD_TYPE, or DFLT_PRJACT_PERIOD_TYPE.
• <GROUP>_AS_OF_DATE — the default as-of date applied to the group's report, e.g. DFLT_PRJBAB_AS_OF_DATE or DFLT_RESAVL_AS_OF_DATE.
• <GROUP>_CYCLE_ID — the default billing cycle identifier for the group, joined to PA_BILLING_CYCLES.
• BILLING_CYCLE_NAME — the human-readable name of the billing cycle resolved through the outer join to PA_BILLING_CYCLES; this is the column most frequently queried by users seeking billing cycle context.

Common Use Cases and Queries

This view is typically used to audit or document which defaults the PJI framework applies per report group, to populate report headers, or to drive parameter initialization in custom concurrent programs and BI Publisher reports. A representative query lists the configured defaults across all groups:

• SELECT meaning, billing_cycle_name, setting_id FROM apps.pji_default_period_settings_v ORDER BY meaning;
• SELECT meaning, billing_cycle_name FROM apps.pji_default_period_settings_v WHERE meaning = 'Resource Utilization';
• SELECT meaning, billing_cycle_name FROM apps.pji_default_period_settings_v WHERE billing_cycle_name IS NOT NULL;

Because the underlying definition uses an outer join to PA_BILLING_CYCLES, results with a null BILLING_CYCLE_NAME indicate report groups for which no default cycle is configured, a common finding during initial or partial ETRM setups.