Results for “igi_bud_profile_defaults”

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

Overview

IGI_BUD_PROFILE_DEFAULTS is a table owned by the IGI schema, the database account associated with the Oracle EBS product IGI – Public Sector Financials International. The table is documented as VALID in Oracle EBS 12.1.1 and 12.2.2 and its stated purpose is to hold default profile codes used by the budgetary execution and public-sector financials functionality. In practice, the table serves as a configuration store that maps a General Ledger accounting combination to a pair of budget profile codes — one designated as the primary profile and one as the latest profile — within a specific set of books. This allows the application to resolve, for any given account and ledger, which budget profile should be treated as authoritative when budget execution transactions, appropriations, or budgetary control checks are processed.

From a data-warehouse modeling perspective, the metadata's heuristic classification places this object as standalone, meaning it does not participate in the referenced foreign-key network as a dependent child and is not documented as a hub or link. This suggests modeling it as a standalone reference or configuration entity — loosely a satellite-like dimension — rather than as a transactional fact or a relationship link. Analysts building an ETRM or public-sector reporting layer should treat it as a low-volume, slowly changing configuration table.

Key Information Stored

The physical schema documented in ETRM 12.2.2 comprises nine columns. The most significant are:

• CODE_COMBINATION_ID — the identifier of the GL accounting flexfield combination to which the default profile applies. This is the account-level key of the record.
• SET_OF_BOOKS_ID — the ledger (set of books) context for the default, scoping the configuration to a specific accounting book.
• PRIMARY_PROFILE_CODE — the code identifying the profile treated as the primary or default budget profile for the combination.
• LATEST_PROFILE_CODE — the code identifying the most recently applied or most current budget profile for the combination.
• CREATION_DATE, CREATED_BY — standard audit columns capturing when and by whom the record was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification and the login context of the change.

The documented primary key is IGI_BUD_PROFILE_DEFAULTS_PK, defined on the composite of CODE_COMBINATION_ID and SET_OF_BOOKS_ID. The metadata lists this same composite as the sole unique index, and therefore the only business-key candidate; there is no separate single-column surrogate key. Consequently, uniqueness of a profile default is guaranteed per account combination per ledger.

Common Use Cases and Queries

Typical reporting scenarios include reconciling which budget profile is being applied to a given account, auditing profile default changes, and joining profile codes to descriptive profile definitions for management reporting. A common query pattern retrieves all defaults for a ledger:

• SELECT code_combination_id, primary_profile_code, latest_profile_code FROM igi.igi_bud_profile_defaults WHERE set_of_books_id = <ledger_id>;
• Joining to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to render the account string alongside the profile codes.
• Joining to profile definition tables (referenced by PRIMARY_PROFILE_CODE and LATEST_PROFILE_CODE) to obtain descriptions for reporting.
• Audit queries filtering on LAST_UPDATE_DATE or LAST_UPDATED_BY to detect recent configuration changes.

Because the table is standalone with no documented foreign-key children, it is safe to query directly without concern for cascade or dependency effects.

Related Objects

• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to resolve the account combination.
• GL_SETS_OF_BOOKS / FND_SETID_SETS — joined on SET_OF_BOOKS_ID to resolve ledger context.
• The IGI profile definition table referenced by PRIMARY_PROFILE_CODE and LATEST_PROFILE_CODE.
• Standard audit/system columns implicitly link to FND_USER via CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• Other IGI budget execution tables in the IGI schema that consume these default profile codes during budgetary control processing.