Search Results igi_bud_profile_codes




Overview
Explore in AI Chat

Overview

IGI.IGI_BUD_PROFILE_CODES is a table in the Oracle E-Business Suite database, owned by the IGI schema, which supports the IGI - Public Sector Financials International product. As documented in the ETRM metadata, the table "holds details of profile codes" used within the budgeting functionality of that module. In Oracle EBS 12.1.1 and 12.2.2, this table functions as a reference or definition entity: it stores the master list of budget profile codes that are subsequently associated with periods and other budgeting attributes through dependent child tables. The table carries the status VALID in the documented environment, confirming the account has been validated against the data dictionary.

From a data-modeling perspective, the heuristic Data Vault classification mined from its foreign key structure is hub-leaning. This suggests the table behaves as a central definition or reference hub, holding the business keys that satellite or link tables reference. The primary key IGI_BUD_PROFILE_CODES_PK is a composite key that anchors each unique profile code per set of books.

Key Information Stored

The table comprises ten documented columns. The most significant are outlined below, distinguishing the composite primary key from descriptive and audit attributes.

  • SET_OF_BOOKS_ID — Part of the composite primary key. Identifies the ledger (set of books) to which the profile code belongs, ensuring profile codes are scoped correctly across legal entities in a multi-organization environment.
  • PROFILE_CODE — Part of the composite primary key and the principal business-key candidate. This is the user-facing identifier for the profile code definition.
  • DESCRIPTION — Provides the human-readable name or explanation of the profile code, typically surfaced in list-of-values and reporting outputs.
  • START_DATE_ACTIVE — The date on which the profile code becomes active for use within the ledger.
  • END_DATE_ACTIVE — The date on which the profile code ceases to be active; together with START_DATE_ACTIVE, it supports date-effective filtering.
  • CREATION_DATE — Standard audit column recording the row creation timestamp.
  • CREATED_BY — Audit column recording the user who created the record.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification to the row.
  • LAST_UPDATED_BY — User who performed the most recent update.
  • LAST_UPDATE_LOGIN — Audit column capturing the login session associated with the last update, useful for traceability in concurrent-user environments.

The composite primary key (SET_OF_BOOKS_ID, PROFILE_CODE) serves as the surrogate-uniqueness mechanism, while PROFILE_CODE combined with the ledger context represents the practical business key.

< >

Common Use Cases and Queries

Typical uses include validating active profile codes, joining profile codes to their associated periods, and reporting on the configuration of budget profile definitions per ledger.

  • Retrieving all active profile codes for a given ledger:
    SELECT PROFILE_CODE, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE FROM IGI.IGI_BUD_PROFILE_CODES WHERE SET_OF_BOOKS_ID = :ledger_id AND TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
  • Reporting on the count of profile codes defined per set of books:
    SELECT SET_OF_BOOKS_ID, COUNT(*) FROM IGI.IGI_BUD_PROFILE_CODES GROUP BY SET_OF_BOOKS_ID;
  • Joining to the periods child table to list every period tied to each profile code:
    SELECT c.PROFILE_CODE, p.* FROM IGI.IGI_BUD_PROFILE_CODES c JOIN IGI.IGI_BUD_PROFILE_PERIODS p ON p.SET_OF_BOOKS_ID = c.SET_OF_BOOKS_ID AND p.PROFILE_CODE = c.PROFILE_CODE WHERE c.SET_OF_BOOKS_ID = :ledger_id;
  • Auditing recent configuration changes:
    SELECT PROFILE_CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM IGI.IGI_BUD_PROFILE_CODES ORDER BY LAST_UPDATE_DATE DESC;

Related Objects

The documented foreign key relationship identifies IGI_BUD_PROFILE_PERIODS as the primary dependent object. It references IGI_BUD_PROFILE_CODES through the composite columns SET_OF_BOOKS_ID and PROFILE_CODE, meaning each period record must correspond to an existing profile code definition. This parent-child linkage is central to the budgeting model, allowing a single profile code to govern multiple period definitions.

The following related objects are significant within the IGI budgeting area:

  • IGI_BUD_PROFILE_PERIODS — Child table; foreign key on (SET_OF_BOOKS_ID, PROFILE_CODE). Holds period-level detail for each profile code.
  • IGI_BUD_PROFILE_CODES_PK — The primary key constraint and supporting index on (SET_OF_BOOKS_ID, PROFILE_CODE).
  • Budgeting and ledger reference objects within the IGI schema that consume profile codes for period-level budget processing.
  • Standard Oracle EBS audit/security views and FND tables that resolve CREATED_BY and LAST_UPDATED_BY to usernames.

Because the documented relationship data confirms only one foreign-key dependency, IGI_BUD_PROFILE_PERIODS should be treated as the principal downstream consumer. Any insertion into that child table must be preceded by the existence of the corresponding row here, and deletion of a profile code is generally constrained while dependent period records exist.