Search Results effect_on_funds_code




Overview
Explore in AI Chat

Overview

GL_BC_PACKETS_V is an APPS-owned database view in the Oracle E-Business Suite General Ledger module. Its ETRM description is "10SC ONLY", indicating it is delivered to support the budgetary control and funds checking functionality associated with the U.S. federal Standard General Ledger (USSGL) and specifically the 10SC (Treasury) budgetary accounting model. The view exposes budget/encumbrance packet rows held in GL_BC_PACKETS along with decoded accounting amounts, giving report writers and integrators a stable, query-friendly interface to budgetary control packets without directly accessing the underlying base table.

The view is documented as VALID and exists in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it carries no data of its own; every row retrieved is derived at runtime from GL_BC_PACKETS and its foreign key references. It does not appear on any standard concurrent program, so it is primarily consumed by customer-built reports, extracts, and interfaces.

Underlying Base Objects

The documented base objects referenced by GL_BC_PACKETS_V are:

Column-level provenance shows a direct one-to-one projection from GL_BC_PACKETS for most fields (PACKET_ID, LEDGER_ID renamed to SET_OF_BOOKS_ID, JE_SOURCE_NAME, JE_CATEGORY_NAME, STATUS_CODE, and so on). The remaining base objects supply referential detail for foreign key columns such as BUDGET_VERSION_ID, ENCUMBRANCE_TYPE_ID, and TEMPLATE_ID, and for lookups such as JE_SOURCE_NAME and JE_CATEGORY_NAME. The underlying table uses ROWID to expose ROW_ID.

Key Columns

  • PACKET_ID — primary key identifying each budgetary control packet.
  • SET_OF_BOOKS_ID — ledger identifier, renamed from LEDGER_ID to preserve 11i/12.1 naming for backward compatibility.
  • STATUS_CODE — the packet processing status. This is the column most often searched under the term status_code_meaning. Documented values include 'C' (complete/confirmed) and 'P' (pending); the DECODE in the view text specifically tests these two values.
  • FUNDS_CHECK_LEVEL_CODE — level at which funds checking occurs; 'N' (none) suppresses the account amounts.
  • EFFECT_ON_FUNDS_CODE — how the transaction affects funds; 'D' denotes a debit/consumption impact.
  • RESULT_CODE — funds check result (for example P01–P09, F20–F29). Codes in these ranges cause the ACCOUNTED_DR/ACCOUNTED_CR projection to return NULL.
  • ACCOUNTED_DR / ACCOUNTED_CR — decoded accounted amounts. They are only populated when STATUS_CODE is not 'C' or 'P', when a funds check level applies, and when the effect-on-funds code is 'D' outside the listed result-code ranges.
  • PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, QUARTER_NUM — accounting period attributes.
  • CURRENCY_CODE, ACTUAL_FLAG — ledger currency and actual/budget/encumbrance indicator.
  • ENTERED_DR / ENTERED_CR — entered amounts.
  • USSGL_TRANSACTION_CODE, ACCOUNT_SEGMENT_VALUE, BOUNDARY_CODE, TOLERANCE_PERCENTAGE — federal budgetary control attributes.

Common Use Cases and Queries

Typical uses include reconciling budgetary control packets, auditing funds check outcomes, and feeding downstream budget execution extracts. A status breakdown by ledger and period is a common starting point:

SELECT SET_OF_BOOKS_ID, PERIOD_NAME, STATUS_CODE, COUNT(*) packets
FROM   APPS.GL_BC_PACKETS_V
GROUP  BY SET_OF_BOOKS_ID, PERIOD_NAME, STATUS_CODE;

To review only completed packets with their accounted balances:

SELECT PACKET_ID, PERIOD_NAME, STATUS_CODE, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR
FROM   APPS.GL_BC_PACKETS_V
WHERE  STATUS_CODE = 'C'
AND    PERIOD_NAME = :period;

Because DECODE logic in the view can return NULL for ACCOUNTED_DR and ACCOUNTED_CR, consumers should test STATUS_CODE and RESULT_CODE alongside the amounts, particularly when the funds check level is not 'N'. Queries should be directed at the view rather than GL_BC_PACKETS to preserve the decoded semantics documented for 10SC processing.