Results for “gl_alloc_formulas_lov_v”

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

Overview

The GL_ALLOC_FORMULAS_LOV_V view is a dictionary object owned by the APPS schema within Oracle E-Business Suite General Ledger. As indicated by the _LOV_V naming convention, it is purpose-built to supply a List of Values (LOV) — the queryable data source behind a value list window in an Oracle Forms-based concurrent program, allocation setup screen, or custom inquiry. It surfaces the allocation formulas defined in the Allocation module so that a user can select a specific formula by its name or description rather than by an internal numeric identifier.

The documented metadata carries a narrow scope note: 10SC ONLY. This designation restricts the view's intended use to a specific localization or functional context identified in the EBS 12.1.1 and 12.2.2 releases. The view nevertheless remains in VALID status in the ETRM registry and is deployed in the standard APPS schema, meaning it is accessible to any session that holds the appropriate grants on the underlying synonym.

Underlying Base Objects

The view is defined over a single documented base object, the synonym GL_ALLOC_FORMULAS, which resolves to the allocation formula definition table in the General Ledger schema. The view is therefore a thin projection: it exposes a subset of the base table's columns without joins, filters, unions, or aggregation. Because it references only one table and performs no row-level restriction in the view text, the view returns every allocation formula row present in GL_ALLOC_FORMULAS.

This lightweight construction is deliberate. An LOV data source typically needs only the identifier, a display name, and a descriptive label, and the base table carries considerably more data attribute columns than an LOV window requires. By projecting to four columns, the view reduces the fetch payload delivered to the form and avoids exposing configuration attributes that are irrelevant to selection.

Key Columns

• ALLOCATION_FORMULA_ID — The primary identifier for an allocation formula. This is the value that a dependent field stores when the user makes a selection, and it is the column the search term allocation_formula_id targets. It is the effective primary key of the view's result set.
• NAME — The user-defined name of the allocation formula. This is typically the visible display column in the LOV window and the field an end user searches against.
• DESCRIPTION — Free-text descriptive text attached to the formula, providing additional context to distinguish formulas sharing similar names.
• ALLOCATION_BATCH_ID — The identifier of the allocation batch with which the formula is associated. Within the Allocation module, formulas are frequently owned at the batch level, so this column establishes the parent context under which the formula is defined.

Common Use Cases and Queries

The principal use case is populating an LOV in a custom form, OAF page, or concurrent program parameter where the user must choose an allocation formula. A typical parameter LOV query is:

• SELECT name, allocation_formula_id FROM apps.gl_alloc_formulas_lov_v ORDER BY name;

For integration or reporting purposes, the view can be joined to allocation results, journal import staging, or batch headers using ALLOCATION_FORMULA_ID. To resolve a stored identifier back to a readable label and description:

• SELECT name, description FROM apps.gl_alloc_formulas_lov_v WHERE allocation_formula_id = :p_formula_id;

To enumerate the formulas belonging to a particular batch:

• SELECT allocation_formula_id, name, description FROM apps.gl_alloc_formulas_lov_v WHERE allocation_batch_id = :p_batch_id ORDER BY name;

Because the view performs no filtering, callers must apply their own predicates for batch scoping, name pattern matching, or security. Given the 10SC ONLY designation, implementations should confirm that the localization context applies before relying on the view in a supported configuration, and should treat GL_ALLOC_FORMULAS as the authoritative base object for any direct data access.