Results for “gl_bc_packets_hists”

50+ results




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

Overview

GL_BC_PACKETS_HISTS is the historical archive table for Oracle General Ledger's Budgetary Control feature. Budgetary Control in Oracle E-Business Suite enforces funds availability checking against budget and encumbrance balances before transactions are posted. During this process, the General Ledger engine assembles "packets" — intermediate working records that aggregate the account, amount, and balance information required to determine whether sufficient funds exist. The live working rows reside in GL_BC_PACKETS; when those packets are purged or reorganized, the affected records are moved into GL_BC_PACKETS_HISTS so that a durable audit trail of the funds-check computation is retained.

The table is owned by the GL schema and is valid in both release 12.1.1 and 12.2.2. In 12.2.2 the documented physical schema contains 89 columns, reflecting the breadth of context that Budgetary Control must capture: ledger, journal source and category, account combination, currency, period, budget and encumbrance version references, balances at multiple stages, and detailed tolerance and override settings. From a data-vault modeling perspective, the metadata classifies GL_BC_PACKETS_HISTS as a link, since its structure is dominated by foreign-key relationships tying together ledgers, journals, budget versions, encumbrance types, accounts, and concurrent requests.

Key Information Stored

The surrogate primary key of the table is PACKET_ID, which uniquely identifies each archived budgetary control packet. The most significant columns include:

Business-key candidates are implied by the combined journal, account, and period references, though the documented metadata does not enumerate a unique index other than the surrogate PACKET_ID.

Common Use Cases and Queries

The primary use case is funds-check audit and troubleshooting: identifying why a transaction was rejected or accepted, and reconstructing the balance picture at that moment. A typical query joins GL_BC_PACKETS_HISTS to GL_LEDGERS and GL_CODE_COMBINATIONS to report rejected packets for a period.

Sample pattern:

SELECT h.PACKET_ID, h.PERIOD_NAME, h.CODE_COMBINATION_ID,
       h.ENTERED_DR, h.ENTERED_CR, h.RESULT_CODE
FROM   GL.GL_BC_PACKETS_HISTS h
WHERE  h.LEDGER_ID = :ledger_id
AND    h.PERIOD_NAME = :period
ORDER  BY h.PACKET_ID;

Other scenarios include reconciling archived packets to journal batches via JE_BATCH_ID and JE_HEADER_ID, reporting tolerance overrides applied, and correlating packets to the concurrent request that generated them through REQUEST_ID.

Related Objects

  • GL_BC_PACKETS — the live working table from which rows are moved into this history table.
  • GL_LEDGERS — joined on LEDGER_ID.
  • GL_JE_LINES / GL_JE_HEADERS / GL_JE_BATCHES — joined on JE_HEADER_ID, JE_LINE_NUM, and JE_BATCH_ID.
  • GL_BUDGET_VERSIONS — joined on BUDGET_VERSION_ID and FUNDING_BUDGET_VERSION_ID.
  • GL_ENCUMBRANCE_TYPES — joined on ENCUMBRANCE_TYPE_ID.
  • GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID.
  • FND_CURRENCIES — joined on CURRENCY_CODE.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID.
  • GL_SUMMARY_TEMPLATES — joined on TEMPLATE_ID.