Results for “funds_check_level_code”

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

Overview

GL_SUMMARY_BC_OPTIONS is a General Ledger configuration table owned by the GL schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the summary account budget and funds-check options associated with a given budget template, allowing Oracle General Ledger to define how summarized balances are validated and consolidated for budgetary control purposes. Each row links a budget template (TEMPLATE_ID) to a funding budget version (FUNDING_BUDGET_VERSION_ID), and holds the rules governing how summary accounts participate in funds checking, debit/credit treatment, amount selection, and boundary conditions.

Because the table's primary key is a composite of two foreign-key-like identifiers and the table carries no independent transactional event of its own, the ETRM metadata classifies it heuristically as a standalone Data Vault structure. Under a Data Vault modeling suggestion, this object behaves most like a satellite or configuration reference attached to the template-to-budget-version relationship, rather than a hub or link. It is a low-volatility setup table populated during budget template and budget version configuration.

Key Information Stored

The table contains eleven documented columns. The two-part primary key, enforced by GL_SUMMARY_BC_OPTIONS_PK, consists of:

• TEMPLATE_ID — the budget template identifier.
• FUNDING_BUDGET_VERSION_ID — the specific funding budget version to which the options apply.

The same two columns form the unique index GL_SUMMARY_BC_OPTIONS_U1, confirming them as the business-key candidates and the natural grain of the table. The remaining configuration attributes drive funds-check behavior:

• FUNDS_CHECK_LEVEL_CODE — indicates the level at which funds checking is performed.
• DR_CR_CODE — determines whether summary balances are evaluated for debit or credit activity.
• AMOUNT_TYPE — identifies the amount basis (for example, budget, actual, or encumbrance) used during summarization.
• BOUNDARY_CODE — specifies the boundary handling rule applied to the summary calculation.

Standard EBS audit columns are also present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and LAST_UPDATE_DATE. There is no separate surrogate key beyond the composite TEMPLATE_ID and FUNDING_BUDGET_VERSION_ID pair.

Common Use Cases and Queries

The table is typically queried during diagnosis of budget template behavior, funds-check results, or summary account configuration. A common pattern retrieves all options for a template/version combination:

• SELECT * FROM gl_summary_bc_options WHERE template_id = :template_id AND funding_budget_version_id = :version_id;
• Reporting joins to budget template and version tables to display funds-check and DR/CR rules alongside template names.
• Verification that a funds check is configured at the required level by inspecting FUNDS_CHECK_LEVEL_CODE and AMOUNT_TYPE for a given template.
• Audit queries using LAST_UPDATED_BY and LAST_UPDATE_DATE to track configuration changes over time.

Because the object is configuration-oriented and low volume, queries should always be constrained by the composite key to avoid full scans.

Related Objects

As a standalone structure, its relationships are driven by the two key columns. Relevant referencing objects include:

• GL_BUDGET_TEMPLATES (or the budget template definition table) — joined on TEMPLATE_ID.
• Funding budget version tables — joined on FUNDING_BUDGET_VERSION_ID.
• GL_SUMMARY_ACCOUNTS — summary account definitions affected by the boundary and amount rules.
• GL_BUDGET_VERSIONS — version metadata linked via FUNDING_BUDGET_VERSION_ID.
• Funds available / budgetary control APIs — which consume these options when executing funds checks.

Consult the ETRM for exact physical join columns, as some relationships are enforced functionally rather than through database-level foreign keys.