Results for “gl_bc_option_details_v”

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

Overview

GL_BC_OPTION_DETAILS_V is an Oracle EBS General Ledger (GL) view owned by the APPS schema and documented with the status VALID. Its ETRM metadata describes the object as "10SC ONLY," indicating that the view is associated with a localized (10SC) configuration and that the underlying base table, GL_BC_OPTION_DETAILS, may not be populated or relevant in all environments. Functionally, the view exposes budget/balance check option detail records that govern how the General Ledger applies funds checking at the journal source and journal category level. It presents the stored transactional detail rows from GL_BC_OPTION_DETAILS while joining to reference and lookup objects to translate internal codes into user-facing descriptions.

In reporting and integration terms, the view provides a denormalized, read-only projection suitable for inquiry screens, extracts, and downstream reconciliation. Because it resolves raw codes (journal source name, journal category name, and funds check level code) into descriptive values, the view is well-suited for user-facing reports without requiring additional joins in the consuming query.

Underlying Base Objects

The view is defined over four documented objects. The primary driving object is GL_BC_OPTION_DETAILS (referenced through a synonym, aliased D), which supplies the option detail rows, the surrogate key BC_OPTION_ID, the funds check level code, the override and tolerance attributes, and the descriptive flexfield (CONTEXT and ATTRIBUTE1–ATTRIBUTE15) columns. Three supporting objects enrich those rows:

• GL_JE_SOURCES (alias S) — joined on JE_SOURCE_NAME to supply USER_JE_SOURCE_NAME.
• GL_JE_CATEGORIES (alias C) — joined on JE_CATEGORY_NAME to supply USER_JE_CATEGORY_NAME.
• GL_LOOKUPS (a view, alias L) — joined where LOOKUP_TYPE = 'FUNDS_CHECK_LEVEL' and LOOKUP_CODE = FUNDS_CHECK_LEVEL_CODE, supplying USER_FUNDS_CHECK_LEVEL.

All joins are equijoins on name or code. Column projection includes ROW_ID derived from D.ROWID, together with audit columns and the flexfield attributes.

Key Columns

• BC_OPTION_ID — surrogate identifier of the option detail record.
• JE_SOURCE_NAME / USER_JE_SOURCE_NAME — journal source code and its descriptive name.
• JE_CATEGORY_NAME / USER_JE_CATEGORY_NAME — journal category code and its descriptive name.
• FUNDS_CHECK_LEVEL_CODE / USER_FUNDS_CHECK_LEVEL — funds check level code and its lookup meaning.
• OVERRIDE_AMOUNT — the amount threshold governing override behavior.
• TOLERANCE_PERCENTAGE and TOLERANCE_AMOUNT — the tolerance controls applied to funds checking. The column the user searched, TOLERANCE_AMOUNT, stores the absolute monetary tolerance permitted when validating a journal against available funds.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

A typical inquiry retrieves funds check tolerances by source and category:

• Reporting configured tolerance amounts and percentages per journal source/category for audit review.
• Feeding read-only extracts into reconciliation or security-related reporting.
• Validating the descriptive lookup mapping of funds check levels.

Sample SQL:

SELECT bc_option_id, user_je_source_name, user_je_category_name, user_funds_check_level, override_amount, tolerance_percentage, tolerance_amount FROM apps.gl_bc_option_details_v;

To isolate rows with a monetary tolerance defined, add WHERE tolerance_amount IS NOT NULL and optionally filter by user_je_source_name. Because the view is documented as "10SC ONLY," confirm availability of populated data before relying on results in a given instance.