Search Results validation_status

Overview

GL_ALLOC_FORMULAS_V is an APPS-owned reporting view in the Oracle E-Business Suite General Ledger module. It exposes allocation formula definitions maintained by the MassAllocation/MassBudgeting engine, presenting header-level attributes of each allocation formula together with user-facing descriptions resolved from related General Ledger setup tables. The view carries a status of VALID in both the 12.1.1 and 12.2.2 releases and is documented under the ETRM repository.

The view is principally used for inquiry, reporting, and integration. Rather than query the base table GL_ALLOC_FORMULAS directly and manually join to journal category, conversion type, and lookup tables, consumers can query this view and receive denormalized, descriptive values. In particular, the validation_status column searched by the user is surfaced both as the raw lookup code (VALIDATION_STATUS) and as its decoded meaning (SHOW_VALIDATION_STATUS), enabling reports and interfaces to display readable status information without an additional lookup join.

Underlying Base Objects

The documented view text defines GL_ALLOC_FORMULAS_V over the following objects, all referenced through APPS synonyms except the lookup view:

• GL_ALLOC_FORMULAS — the primary driver table, aliased AF, supplying the allocation formula header attributes.
• GL_ALLOC_FORMULA_LINES — aliased AFL, joined on ALLOCATION_FORMULA_ID with the constraint LINE_NUMBER = 4.
• GL_JE_CATEGORIES — aliased CAT, joined on JE_CATEGORY_NAME to resolve the user journal entry category name.
• GL_DAILY_CONVERSION_TYPES — aliased DCT, joined with an outer (+) operator on CONVERSION_TYPE to resolve the user conversion type.
• GL_LOOKUPS — a view, aliased L, filtered on LOOKUP_TYPE = 'VALIDATION_STATUS' and matched to AF.VALIDATION_STATUS to supply SHOW_VALIDATION_STATUS.

Because the formula lines join is restricted to LINE_NUMBER = 4, the view is effectively pinned to the fourth line of each allocation formula. This behavior is inherited from the seeded definition and should be accounted for when interpreting row counts or missing formulas.

Key Columns

• ROW_ID — the ROWID of the underlying GL_ALLOC_FORMULAS row.
• ALLOCATION_FORMULA_ID / ALLOCATION_BATCH_ID — primary identifier of the formula and its parent batch.
• NAME / DESCRIPTION — the formula name and descriptive text.
• JE_CATEGORY_NAME / USER_JE_CATEGORY_NAME — the journal category code and its user-facing name.
• TRANSACTION_CURRENCY — currency in which the allocation is expressed.
• CONVERSION_METHOD_CODE / CURRENCY_CONVERSION_TYPE / USER_CONVERSION_TYPE — conversion method and the conversion type code and description.
• RUN_SEQUENCE — execution ordering of the formula within its batch.
• FULL_ALLOCATION_FLAG — indicates whether the formula performs a full allocation.
• VALIDATION_STATUS / SHOW_VALIDATION_STATUS — the raw lookup code and decoded meaning of the formula's validation state.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include auditing allocation formulas prior to running MassAllocation, identifying formulas by validation state, and feeding downstream extracts. The following query lists validated formulas with their descriptive attributes:

SELECT allocation_formula_id,
       name,
       je_category_name,
       user_je_category_name,
       transaction_currency,
       user_conversion_type,
       run_sequence,
       full_allocation_flag,
       validation_status,
       show_validation_status
FROM   apps.gl_alloc_formulas_v
WHERE  validation_status = 'V'
ORDER  BY allocation_batch_id, run_sequence;

To report formulas that have not yet been validated, substitute the WHERE clause with validation_status <> 'V'. Because the LINE_NUMBER = 4 restriction is applied within the view, join back to GL_ALLOC_FORMULA_LINES on ALLOCATION_FORMULA_ID when full line-level detail is required, or query the base table directly if formulas with fewer than four lines must be included.