Results for “calculation_effective_date”

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

Overview

GL_AUTO_ALLOC_SET_HISTORY is a General Ledger table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments that stores the historical record of automatic allocation set executions. Each row captures a single run of an allocation set, preserving the runtime parameters, ledger context, period context, and the concurrent request that produced it. Because allocations redistribute balances across accounts according to defined formulas and targets, this table provides the audit and traceability layer that lets users answer when a set was run, against which ledger, for which period, and under which budgeting or access-set context.

From a Data Vault modeling perspective, the metadata suggests this object behaves primarily as a link, with a heuristic classification of link mined from its foreign-key structure. The table connects concurrent requests, allocation sets, ledgers, budget versions, access sets, and management segment upgrade records, making it a junction of several business entities rather than a pure hub or satellite. In practice it functions as an execution-history fact for allocation processing.

Key Information Stored

The primary key is composed of REQUEST_ID, enforced by GL_AUTO_ALLOC_SET_HISTORY_PK1 and reinforced by the unique index GL_AUTO_ALLOC_SET_HISTORY_U1. In this schema the surrogate identifier is therefore the concurrent request ID, which simultaneously acts as a business-key candidate because it ties the row to a specific submission.

• REQUEST_ID — the concurrent request identifier, primary key and link to FND_CONCURRENT_REQUESTS.
• ALLOCATION_SET_ID — identifies the allocation set that was run; links to GL_AUTO_ALLOC_SETS.
• ALLOCATION_CODE and ALLOCATION_SET_NAME — the short code and descriptive name of the allocation set.
• ALLOCATION_SET_TYPE_CODE — classifies the allocation set type.
• LEDGER_ID — the ledger against which the allocation executed.
• PERIOD_NAME and GL_PERIOD_NAME — the accounting period context of the run.
• BUDGET_VERSION_ID — the budget version used when the allocation targeted budget balances.
• ACCESS_SET_ID — the access set context in secured environments.
• CHART_OF_ACCOUNTS_ID — the chart of accounts associated with the allocation.
• JOURNAL_EFFECTIVE_DATE and CALCULATION_EFFECTIVE_DATE — effective dating for the run.
• USAGE_CODE — indicates how the allocation set was used.
• MONITOR_URL — a URL pointing to the concurrent request monitoring page.
• LEDGER_CURRENCY and BALANCING_SEGMENT_VALUE — currency and balancing segment data for the ledger.

Common Use Cases and Queries

Typical reporting scenarios include auditing historical allocation runs, reconciling allocation output against the originating concurrent request, and troubleshooting failed or misconfigured allocations by reviewing the stored context.

• List recent runs for a given allocation set: SELECT request_id, period_name, ledger_id FROM gl_auto_alloc_set_history WHERE allocation_set_id = :set_id ORDER BY creation_date DESC;
• Trace a specific concurrent request back to its allocation set and ledger.
• Report allocation activity by period to support period-close review.
• Join to FND_CONCURRENT_REQUESTS to obtain run status, completion time, and requestor.

Related Objects

The foreign-key metadata identifies the principal related objects that reference or are referenced by this table:

• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID.
• GL_AUTO_ALLOC_SETS — joined on ALLOCATION_SET_ID.
• GL_BUDGET_VERSIONS — joined on BUDGET_VERSION_ID.
• GL_ACCESS_SETS — joined on ACCESS_SET_ID.
• GL_MGT_SEG_UPGRADE_H — joined on CHART_OF_ACCOUNTS_ID.