Search Results gl_bc_packets_hists




Overview
Explore in AI Chat

Overview

The GL_BC_PACKETS_HISTS table is a critical data object within the Oracle E-Business Suite General Ledger module, specifically for the Budgetary Control feature. It functions as a historical archive for budgetary control transactions. Its primary role is to store records that have been deleted from the active GL_BC_PACKETS table, ensuring a complete audit trail of all budgetary control activities. This table is essential for maintaining data integrity, supporting compliance, and enabling historical analysis of budget checks, reservations, and funds consumption over time within the application.

Key Information Stored

As a history table, GL_BC_PACKETS_HISTS mirrors the structure of its parent table, GL_BC_PACKETS. It captures the complete state of a budgetary control packet at the time of its deletion. Key columns include identifiers for the ledger (LEDGER_ID), the associated journal entry (JE_HEADER_ID, JE_LINE_NUM, JE_BATCH_ID), and the accounting flexfield (CODE_COMBINATION_ID). It stores the packet amount (PACKET_AMOUNT), currency (CURRENCY_CODE), and the status of the budget check. Crucially, it holds references to the budget versions (BUDGET_VERSION_ID, FUNDING_BUDGET_VERSION_ID) and encumbrance types (ENCUMBRANCE_TYPE_ID) that govern the funds check, along with the concurrent request (REQUEST_ID) that processed it.

Common Use Cases and Queries

The primary use case for this table is historical reporting and troubleshooting of budgetary control. Analysts can query it to review the complete lifecycle of budget reservations, including those that were ultimately reversed or deleted. A common query pattern involves joining to journal entry and code combination tables to produce a historical report of all budget-checked transactions for a specific ledger or account. For example, to analyze deleted packets for a specific period, one might use a SQL pattern such as: SELECT hist.*, jeh.name FROM gl_bc_packets_hists hist, gl_je_headers jeh WHERE hist.je_header_id = jeh.je_header_id AND hist.creation_date BETWEEN :p_start_date AND :p_end_date ORDER BY hist.creation_date DESC;. This table is also indispensable for audit inquiries, where a complete record of all budgetary activity, even deleted items, is required.

Related Objects

GL_BC_PACKETS_HISTS maintains extensive foreign key relationships with core General Ledger and application foundation tables, as documented in the ETRM. These relationships are fundamental for accurate reporting and data validation:

The primary related object is the active transaction table, GL_BC_PACKETS, from which records are moved to this history table upon deletion.