Search Results igi_bud_autocopy_control




Overview
Explore in AI Chat

Overview

The IGI_BUD_AUTOCOPY_CONTROL table is a core data object within the Oracle E-Business Suite (EBS) module IGI - Public Sector Financials International. Its primary function is to manage and control the automatic copying of accounting flexfields (code combinations) during specific budgeting operations. This table acts as a control mechanism, ensuring that the correct accounting segments are replicated from a source budget entry to a target, thereby maintaining data integrity and enforcing budgetary rules within the complex financial structures typical of public sector organizations. It is a transactional table that supports the budgeting processes in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is defined by its primary key and its foreign key relationships, which dictate the data it holds. The two critical columns are BE_HEADER_ID and CODE_COMBINATION_ID, which together form the table's primary key (IGI_BUD_AUTOCOPY_CONTROL_PK). The BE_HEADER_ID column stores a reference identifier that links directly to a specific budget journal header record in the IGI_BUD_JOURNAL_HEADERS table. The CODE_COMBINATION_ID column stores the unique identifier for an accounting flexfield (code combination) that is designated for autocopy in the context of the associated budget journal. This pairing effectively creates a control list, specifying which exact accounting segments are permitted or required to be automatically copied for a given budget entry transaction.

Common Use Cases and Queries

The primary use case involves processes that automate the population of budget lines, such as copying a prior year's budget or replicating budget templates. A system process would query this control table to determine the valid source code combinations for a target budget journal. Common queries include identifying all controlled code combinations for a specific budget header or validating if a particular accounting segment is enabled for autocopy. For example, to audit the autocopy settings for a budget journal, one might use a query such as:

  • SELECT be_header_id, code_combination_id FROM igi.igi_bud_autocopy_control WHERE be_header_id = <header_id>;

Reporting use cases typically focus on process analysis and control verification, ensuring that autocopy rules are correctly configured for ongoing budgetary cycles.

Related Objects

This table has a direct and essential relationship with the IGI_BUD_JOURNAL_HEADERS table, enforced by a foreign key constraint where IGI_BUD_AUTOCOPY_CONTROL.BE_HEADER_ID references IGI_BUD_JOURNAL_HEADERS. The budget journal header record represents the parent transaction for which the autocopy controls are defined. Furthermore, the CODE_COMBINATION_ID column inherently relates to the core EBS table GL_CODE_COMBINATIONS, which stores the master definition of all accounting flexfields. Therefore, any process or report involving IGI_BUD_AUTOCOPY_CONTROL will typically join to these related tables to retrieve descriptive budget journal information and the actual segment values of the controlled code combinations.