Search Results profile_code




Overview
Explore in AI Chat

Overview

The IGI_BUD_PROFILE_CODES table is a core data object within the Oracle E-Business Suite module IGI - Public Sector Financials International. It functions as a master table for defining and storing budgetary profile codes. In the context of public sector financial management, a profile code is a critical configuration element used to model and control the distribution of budget authority across different time periods within a fiscal year. This table establishes the valid profile codes for a specific set of books, serving as the parent definition for detailed period-level rules. Its primary role is to provide a controlled list of profiles that can be assigned to budget accounts, enabling sophisticated budgetary control and forecasting aligned with public sector requirements.

Key Information Stored

The table's structure is designed to uniquely identify a budgetary profile within the ledger context. The primary key is a composite of two columns, which are the most critical fields. The SET_OF_BOOKS_ID column links the profile code to a specific financial ledger, ensuring configurations are ledger-specific. The PROFILE_CODE column stores the unique identifier or name for the budgetary profile (e.g., 'EVEN', 'FRONT_LOADED'). While the provided ETRM excerpt does not list additional columns, typical supporting columns in such a table could include a description (PROFILE_DESCRIPTION), creation date, and user identifiers for auditing. The combination of SET_OF_BOOKS_ID and PROFILE_CODE forms the definitive reference for any profile-related configuration.

Common Use Cases and Queries

This table is primarily referenced during the setup and application of budgetary controls. A common use case is the validation of a profile code entered during budget entry or account setup. System processes will query this table to ensure the provided code is valid for the given ledger. For reporting and analysis, administrators may query the table to list all configured profiles. A typical SQL pattern involves joining to the related periods table to get a complete view of a profile's definition.

  • Listing all profile codes for a ledger: SELECT PROFILE_CODE FROM IGI_BUD_PROFILE_CODES WHERE SET_OF_BOOKS_ID = :ledger_id;
  • Validating a specific profile code: SELECT 'VALID' FROM DUAL WHERE EXISTS (SELECT 1 FROM IGI_BUD_PROFILE_CODES WHERE SET_OF_BOOKS_ID = :ledger_id AND PROFILE_CODE = :profile);

Related Objects

The IGI_BUD_PROFILE_CODES table has a direct parent-child relationship with the IGI_BUD_PROFILE_PERIODS table, as documented by the foreign key. The IGI_BUD_PROFILE_PERIODS table references IGI_BUD_PROFILE_CODES using the composite key of SET_OF_BOOKS_ID and PROFILE_CODE. This relationship is fundamental: the IGI_BUD_PROFILE_CODES table defines the profile header, while the IGI_BUD_PROFILE_PERIODS table holds the detailed percentage or amount rules for each period (e.g., month or quarter) within that profile. Any integration or data extraction concerning budgetary profiles must consider this join to retrieve a complete profile definition.