Results for “funds_status”

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

Overview

GL_LOOKUPS_MJE_FUNDS_STATUS_V is a General Ledger lookup view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a curated subset of the underlying GL_LOOKUPS lookup table, filtered to a single lookup type: JE_BATCH_BC_STATUS. The view presents two derived columns — FUNDS_STATUS and SHOW_FUNDS_STATUS — which respectively return the stored lookup code and its user-facing meaning. The object is documented in ETRM with the terse description "10SC ONLY," indicating it is a localized/regional artifact associated with the 10SC (India statutory) localization rather than a globally delivered GL feature. Its practical role is to make the funds-status values used by journal batch Budgetary Control processing available for reporting, validation, and integration without requiring consumers to know the underlying lookup type or column layout.

Underlying Base Objects

The view is defined exclusively over a single referenced base object, GL_LOOKUPS, which itself is a view in the APPS schema rather than a physical table. GL_LOOKUPS is the standard lookups repository shipped with the E-Business Suite, holding all lookup types and their associated codes, meanings, descriptions, and enablement flags. The view applies a filter on LOOKUP_TYPE = 'JE_BATCH_BC_STATUS', thereby restricting the result set to the batch Budgetary Control status values relevant to journal entry processing. Because it references a view rather than a table, no additional join, index, or partitioning characteristics apply beyond those inherited from GL_LOOKUPS. The dependency is recorded in ETRM with GL_LOOKUPS as the sole documented referenced object.

Key Columns

• FUNDS_STATUS — Maps to GL_LOOKUPS.LOOKUP_CODE. This is the internal, system-facing code for each Budgetary Control batch status value within the JE_BATCH_BC_STATUS lookup type. It is the value typically stored on transactional records and compared programmatically.
• SHOW_FUNDS_STATUS — Maps to GL_LOOKUPS.MEANING. This is the display text presented to end users, such as a translated or descriptive label corresponding to the code in FUNDS_STATUS.

The view exposes no other columns, so attributes such as description, enabled flag, start/end dates, and tag are not available through this object. Consumers requiring those attributes must query GL_LOOKUPS directly.

Common Use Cases and Queries

The view is most commonly used to resolve a stored funds-status code into its display meaning, or to populate a values list in a report, concurrent program parameter, or integration payload. A typical lookup query is:

• SELECT funds_status, show_funds_status FROM apps.gl_lookups_mje_funds_status_v ORDER BY funds_status; — retrieves all Budgetary Control batch statuses for list-of-values or reference purposes.
• SELECT show_funds_status FROM apps.gl_lookups_mje_funds_status_v WHERE funds_status = :p_status; — resolves a single code to its user-facing meaning for display in a report or form.

Because the view is a thin projection over GL_LOOKUPS, no DML is permitted against it; it is read-only by nature. Queries should be qualified with the APPS schema and, in a multi-org or localized environment, used only where the 10SC localization is active, consistent with the "10SC ONLY" designation. For any requirement beyond the two exposed columns, the underlying GL_LOOKUPS view should be queried directly with the same JE_BATCH_BC_STATUS filter.