Results for “gl_bc_packets”

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

Overview

GL_BC_PACKETS is the budgetary control queue table in the Oracle General Ledger (GL) application of Oracle E-Business Suite. It functions as a staging and orchestration structure through which funds availability checks are performed and stored before they are applied to the ledger. Every accounting distribution subject to budgetary control — journal lines, purchasing commitments, requisitions, and payables invoices routed through encumbrance accounting — is written into this table as a "packet" so the budgetary control engine can evaluate the transaction against budget, encumbrance type, tolerance, and funds check level settings before approving or rejecting it.

Within the ETRM data-model classification, GL_BC_PACKETS exhibits the characteristics of a link entity. Its dense foreign-key structure — referencing GL_LEDGERS, GL_BUDGET_VERSIONS, GL_ENCUMBRANCE_TYPES, GL_JE_HEADERS, GL_JE_LINES, GL_CODE_COMBINATIONS, and GL_SUMMARY_TEMPLATES — indicates that it resolves relationships between ledger, budget, and journal entities rather than standing alone as a business entity hub. Analysts modeling this table in a Data Vault should treat it as a link table joining those dimensions, with the 89 documented columns serving as link-level context and status attributes.

Key Information Stored

The table carries 89 columns. The most operationally significant are:

• PACKET_ID — the surrogate primary key uniquely identifying each budgetary control packet.
• LEDGER_ID — the ledger against which the funds check is performed (FK to GL_LEDGERS).
• BUDGET_VERSION_ID and FUNDING_BUDGET_VERSION_ID — the budget version(s) supplying available funds.
• ENCUMBRANCE_TYPE_ID — the encumbrance type driving commitment balances.
• CODE_COMBINATION_ID — the accounting flexfield combination being checked.
• PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM — accounting period context.
• STATUS_CODE and RESULT_CODE — the processing disposition of the packet (passed, failed, overridden).
• ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR — the monetary amounts submitted for check.
• BUDGET_POSTED_BALANCE, ACTUAL_POSTED_BALANCE, ENCUMBRANCE_POSTED_BALANCE — the post-check balances evaluated.
• FUNDS_CHECK_LEVEL_CODE, TOLERANCE_PERCENTAGE, TOLERANCE_AMOUNT, OVERRIDE_AMOUNT — control parameters governing acceptance.
• JE_HEADER_ID, JE_LINE_NUM, JE_BATCH_ID — linkage back to the source journal entry.
• REQUEST_ID — the concurrent request that produced the packet (FK to FND_CONCURRENT_REQUESTS).

The business-key candidates are those columns that, in combination, uniquely identify the underlying transaction — typically JE_HEADER_ID and JE_LINE_NUM joined to LEDGER_ID and PERIOD_NAME — while PACKET_ID remains the technical surrogate.

Common Use Cases and Queries

Typical reporting uses include tracing failed funds checks, reconciling encumbrance balances, and diagnosing stalled budgetary control concurrent programs. A common diagnostic query examines packets not yet resolved:

SELECT packet_id, ledger_id, code_combination_id, period_name, status_code, result_code, entered_dr, entered_cr FROM gl_bc_packets WHERE status_code IS NULL OR result_code IS NULL;

For a transaction trace, joining back to the journal header and line links a failed check to its source entry:

SELECT b.packet_id, b.je_header_id, b.je_line_num, h.name, b.result_code FROM gl_bc_packets b, gl_je_headers h WHERE b.je_header_id = h.je_header_id AND b.ledger_id = :ledger_id;

Budget-override audits filter on OVERRIDE_AMOUNT and TOLERANCE_AMOUNT to identify distributions that proceeded despite insufficient funds.

Related Objects

• GL_LEDGERS — joined via LEDGER_ID; supplies the ledger context.
• GL_BUDGET_VERSIONS — joined via BUDGET_VERSION_ID and FUNDING_BUDGET_VERSION_ID.
• GL_ENCUMBRANCE_TYPES — joined via ENCUMBRANCE_TYPE_ID.
• GL_JE_HEADERS and GL_JE_LINES — joined via JE_HEADER_ID (and JE_LINE_NUM).
• GL_JE_BATCHES — joined via JE_BATCH_ID.
• GL_CODE_COMBINATIONS — joined via CODE_COMBINATION_ID.
• GL_SUMMARY_TEMPLATES — joined via TEMPLATE_ID.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID.
• GL_JE_CATEGORIES_TL and FND_CURRENCIES — joined via JE_CATEGORY_NAME and CURRENCY_CODE respectively.