Results for “ab_journal_type”

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

Overview

APPS.GL_AUTO_ALLOC_SET_HISTORY_V is a reporting and inquiry view in the Oracle E-Business Suite General Ledger module. It exposes the historical record of automatic allocation set runs, joining the persistent allocation history table to descriptive lookups, ledgers, budget versions, and the parent allocation set definition. Because Oracle EBS allocations execute repeatedly across accounting periods, this view provides the audit and reconciliation layer that answers which allocation set ran, under which usage or journal type, against which ledger, and for which period.

The view is significant in that it resolves foreign-key identifiers into human-readable meanings. Rather than returning raw lookup codes, it decorates the allocation set type and the usage code with their translated MEANING values, and it carries the ledger name and budget name forward from their respective master tables. It also applies function-based data security so that allocation history is visible only to users granted access through the FND data security model.

Underlying Base Objects

The view is defined over the following documented base objects:

• GL_AUTO_ALLOC_SET_HISTORY (synonym) — the primary driving table, aliased h, supplying the historical allocation run rows.
• GL_AUTO_ALLOC_SETS (synonym) — the allocation set definition, aliased t, joined on allocation_set_id and used for the security flag and privilege checks.
• GL_LOOKUPS (view) — joined twice: alias l for lookup_type = 'ALLOCATION_SET_TYPE' and alias l2 for lookup_type = 'AB_JOURNAL_TYPE'.
• GL_BUDGET_VERSIONS (synonym) — outer-joined on budget_version_id to resolve the budget name.
• GL_LEDGERS (synonym) — outer-joined on ledger_id to resolve the ledger name.
• FND_DATA_SECURITY (package) and FND_GLOBAL (package) — invoked to compute the VIEW_PRIVILEGE, USE_PRIVILEGE, and MODIFY_PRIVILEGE columns.

The budget and ledger joins are outer joins, so a history row remains visible even when its budget version or ledger reference is absent.

Key Columns

• ROW_ID — the ROWID of the underlying history row.
• REQUEST_ID — concurrent request that generated the allocation run.
• ALLOCATION_SET_ID / ALLOCATION_SET_NAME — identity of the allocation set.
• ALLOCATION_SET_TYPE_CODE / ALLOCATION_SET_TYPE — the code and its translated lookup meaning (lookup type ALLOCATION_SET_TYPE).
• ALLOCATION_CODE — the individual allocation within the set.
• USAGE_CODE / USAGE — the usage value and its decoded meaning, resolved against lookup type AB_JOURNAL_TYPE, matching the searched term.
• LEDGER_ID / LEDGER_NAME and BUDGET_VERSION_ID / BUDGET_NAME — the decoded target ledger and budget.
• PERIOD_NAME / GL_PERIOD_NAME / PA_PERIOD_NAME — the period identifiers relevant to GL and Projects.
• JOURNAL_EFFECTIVE_DATE / CALCULATION_EFFECTIVE_DATE / EXPENDITURE_ITEM_DATE — the effective dating controls for the run.
• VIEW_PRIVILEGE / USE_PRIVILEGE / MODIFY_PRIVILEGE — data security flags derived from the allocation set's security flag.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ORG_ID, DESCRIPTION, OWNER, MONITOR_URL, CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE, ACCESS_SET_ID, BALANCING_SEGMENT_VALUE.

Common Use Cases and Queries

Typical uses include auditing allocation activity, reconciling results to concurrent requests, and restricting output by privilege. A basic query filtered on the AB_JOURNAL_TYPE usage meaning:

SELECT allocation_set_name, usage, ledger_name, period_name,
       journal_effective_date
FROM   apps.gl_auto_alloc_set_history_v
WHERE  usage = 'Actual'
AND    view_privilege = 'Y';

To trace a specific concurrent run:

SELECT request_id, allocation_code, allocation_set_type,
       gl_period_name, calculation_effective_date
FROM   apps.gl_auto_alloc_set_history_v
WHERE  request_id = :request_id
ORDER  BY allocation_code;

To list ledger-level history, filter by ledger_name and period_name. Always apply the privilege columns when exposing the view to end users, since security is enforced through them.