Results for “alloc_id”

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

Overview

GL_ALOC_EXP_V is an APPS-owned database view in Oracle E-Business Suite, defined in the Process Manufacturing Financials (GMF) product family. In ETRM 12.1.1 and 12.2.2 it carries a VALID status and is documented as a view that enables the master-detail relationship on the Expenses to Allocate form. Functionally, the view flattens the relationship between allocation expense records and their parent allocation masters, joining each allocation to its legal entity and resolving the entity name through a GMF legal entities view.

Rather than storing data, GL_ALOC_EXP_V projects a distinct set of allocation-to-legal-entity combinations. Its primary role is therefore a form-enabling and reporting convenience object: the Expenses to Allocate form relies on it to present the defined expense amounts alongside allocation and legal entity context, and report or integration developers can reuse it where the same allocation/legal entity context is required without re-deriving multi-table joins.

Underlying Base Objects

The view is defined over three referenced objects as documented in ETRM 12.2.2:

• GL_ALOC_EXP (SYNONYM) — the synonym resolving to the allocation expense detail, aliased as EXP in the view text.
• GL_ALOC_MST (SYNONYM) — the synonym resolving to the allocation master, aliased as MST, which carries the allocation identifier and code.
• GMF_LEGAL_ENTITIES_VW2 (VIEW) — a GMF legal entities view, aliased as GLE, used to resolve the legal entity name.

The documented view text is:

SELECT DISTINCT MST.LEGAL_ENTITY_ID, MST.ALLOC_ID, MST.ALLOC_CODE, GLE.LEGAL_ENTITY_NAME FROM GL_ALOC_EXP EXP, GL_ALOC_MST MST, GMF_LEGAL_ENTITIES_VW2 GLE WHERE EXP.ALLOC_ID = MST.ALLOC_ID AND GLE.LEGAL_ENTITY_ID = MST.LEGAL_ENTITY_ID

Two joins drive the result set: GL_ALOC_EXP is joined to GL_ALOC_MST on ALLOC_ID, and GMF_LEGAL_ENTITIES_VW2 is joined to GL_ALOC_MST on LEGAL_ENTITY_ID. The DISTINCT keyword deduplicates the projected rows, so the view returns unique allocation/legal entity combinations rather than one row per expense line.

Key Columns

• LEGAL_ENTITY_ID — the identifier of the legal entity associated with the allocation master; drives the join to GMF_LEGAL_ENTITIES_VW2 and is the key master-level attribute on the form.
• ALLOC_ID — the allocation identifier taken from GL_ALOC_MST; links back to the allocation master record and to the expense rows in GL_ALOC_EXP.
• ALLOC_CODE — the user-facing allocation code, useful for display on forms, reports, and lookups, and the column typically referenced when users search by allocation code.
• LEGAL_ENTITY_NAME — the descriptive legal entity name retrieved from the GMF legal entities view, providing readable context alongside the numeric entity identifier.

Common Use Cases and Queries

Typical uses include supporting the Expenses to Allocate form, feeding allocation-by-legal-entity listings into reports, and validating allocation-to-entity mappings during setup or reconciliation. A simple listing by allocation code is shown below.

SELECT alloc_code, alloc_id, legal_entity_id, legal_entity_name FROM apps.gl_aloc_exp_v WHERE alloc_code = :alloc_code ORDER BY alloc_code, legal_entity_name;

A query to enumerate entities per allocation supports master-detail validation:

SELECT alloc_code, legal_entity_id, legal_entity_name FROM apps.gl_aloc_exp_v ORDER BY alloc_code;

Because the view returns DISTINCT allocation/legal entity pairs, it should be treated as a context list rather than an aggregation source. When row-level expense amounts are needed, join ALLOC_ID back to GL_ALOC_EXP.