Results for “pa_bgt_types_it”

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

Overview

PA_BGT_TYPES_IT is a reference table in the Oracle Projects (PA) schema that stores information about budget types used by the Oracle Project Analysis Collection Pack. It holds the set of valid budget type definitions that determine how project and task budgets are categorized and processed across analytical reporting. The table is owned by the PA schema and carries a VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the mined Data Vault classification for this table is hub-leaning. This indicates that PA_BGT_TYPES_IT functions primarily as a durable business entity key repository — a hub — whose natural business key (BUDGET_TYPE_CODE) is referenced by downstream transactional tables rather than being consumed as a descriptive satellite of another entity. Modelers may therefore treat it as a reference hub when building integrated or analytical data models.

The table is a relatively compact reference object; the documented physical schema for release 12.2.2 records 22 columns, most of which are standard Oracle EBS audit, concurrency, and descriptive flexfield infrastructure columns rather than business payload.

Key Information Stored

The most important columns documented for PA_BGT_TYPES_IT are:

• BUDGET_TYPE_CODE — The surrogate primary key and, simultaneously, the business-key candidate. It is enforced by the unique index PA_BGT_TYPES_IT_U1 and by the primary key constraint PA_BGT_TYPES_IT_PK. This is the value propagated to all dependent budget line tables.
• BUDGET_TYPE — The descriptive name of the budget type, used in lists of values and reports.
• STATUS_CODE — The enabled/disabled state of the budget type, controlling whether it remains selectable for new budget entries.
• LAST_UPDATE_DATE — Audit timestamp of the most recent change.
• LAST_UPDATED_BY — The user who performed the most recent update.
• CREATION_DATE — Audit timestamp when the row was created.
• CREATED_BY — The user who created the row.
• LAST_UPDATE_LOGIN — The login session record associated with the last change.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns populated when the row is created or modified by a concurrent request.
• USER_COL1 through USER_COL10 — Attribute placeholder columns reserved for implementation-specific extensions.

The distinguishing key characteristic is that BUDGET_TYPE_CODE serves as both the surrogate primary key and the single unique business key; there is no separate meaningless identifier. All other columns are descriptive or audit-oriented.

Common Use Cases and Queries

Typical usage centers on decoding budget type codes into human-readable names and filtering by status. A common reporting join retrieves project budget lines alongside their type descriptions:

SELECT b.BUDGET_TYPE_CODE, b.BUDGET_TYPE, l.*
FROM PA.PA_PRJ_BGT_LINES_IT_ALL l,
     PA.PA_BGT_TYPES_IT b
WHERE l.BUDGET_TYPE_CODE = b.BUDGET_TYPE_CODE
  AND b.STATUS_CODE = 'ENABLED';

An equivalent pattern applies for task-level budgets using PA_TSK_BGT_LINES_IT_ALL. A list-of-values query used to populate entry forms filters on STATUS_CODE so that only active budget types are presented:

SELECT BUDGET_TYPE_CODE, BUDGET_TYPE
FROM PA.PA_BGT_TYPES_IT
WHERE STATUS_CODE = 'ENABLED'
ORDER BY BUDGET_TYPE;

Additional use cases include validating staging data prior to budget load (confirming every incoming code exists in PA_BGT_TYPES_IT), generating cross-project budget-to-type matrices for analysis, and auditing concurrent program loads via the REQUEST_ID and PROGRAM_ID columns.

Related Objects

The documented foreign key relationships establish PA_BGT_TYPES_IT as a parent reference for budget line detail:

• PA_PRJ_BGT_LINES_IT_ALL — The project-level budget line table for the Analysis Collection Pack; its BUDGET_TYPE_CODE column references PA_BGT_TYPES_IT.
• PA_TSK_BGT_LINES_IT_ALL — The task-level budget line table; its BUDGET_TYPE_CODE column likewise references PA_BGT_TYPES_IT.

These two tables are the principal consumers of the budget type definitions and should be joined on the BUDGET_TYPE_CODE column, which is uniquely indexed in the referenced parent table.