Results for “variance_type”

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

Overview

AX_VARIANCE_STATUSES is a table owned by the AX schema within the Oracle E-Business Suite Global Accounting Engine (AX) module. It stores absorption information used by the Global Accounting Engine to track the disposition of accounting variances against a specific accounting period and organization. The table is documented as VALID and is defined with a composite primary key, AX_VARIANCE_STATUSES_PK, spanning ORGANIZATION_ID, ACCOUNTING_PERIOD_ID, and VARIANCE_TYPE.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests the table functions as an independent hub or reference-style entity rather than a link or satellite, since no explicit parent-child FK relationships were documented in the ETRM metadata. In practice, AX_VARIANCE_STATUSES acts as a status-and-flag registry keyed by the combination of organization, accounting period, and variance type, with the ABSORBTION_FLAG and ABSORBTION_DATE columns capturing the state transition of variance absorption processing.

Key Information Stored

The documented physical schema contains 11 columns. The most significant columns for business and technical purposes include:

• ORGANIZATION_ID — Part of the primary key; identifies the operating unit or inventory organization against which the variance is recorded.
• ACCOUNTING_PERIOD_ID — Part of the primary key; references the accounting period in which the variance status applies. This is the column most commonly used in period-based reporting.
• VARIANCE_TYPE — Part of the primary key; classifies the nature of the variance being tracked (e.g., purchase price, material usage, or absorption variance).
• ABSORBTION_FLAG — Indicates whether the variance has been absorbed.
• ABSORBTION_DATE — The date on which the absorption was executed or recorded.
• PERIOD_YEAR — The fiscal year associated with the accounting period, supporting year-over-year comparative reporting.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit trail and concurrency control.

The surrogate primary key is the composite AX_VARIANCE_STATUSES_PK on (ORGANIZATION_ID, ACCOUNTING_PERIOD_ID, VARIANCE_TYPE). The unique index AX_VARIANCE_STATUSES_U1 on the same three columns confirms this triplet as the business-key candidate, meaning no two status records may exist for the same organization, period, and variance type.

Common Use Cases and Queries

The primary use case is monitoring absorption status across accounting periods. Since the user search targeted accounting_period_id, the most common query patterns filter or group by this column. A typical pattern retrieves unabsorbed variances for a given period:

• SELECT ORGANIZATION_ID, VARIANCE_TYPE, ABSORBTION_FLAG, ABSORBTION_DATE FROM AX.AX_VARIANCE_STATUSES WHERE ACCOUNTING_PERIOD_ID = :period_id AND ABSORBTION_FLAG = 'N';
• SELECT PERIOD_YEAR, ACCOUNTING_PERIOD_ID, COUNT(*) FROM AX.AX_VARIANCE_STATUSES GROUP BY PERIOD_YEAR, ACCOUNTING_PERIOD_ID;
• SELECT ORGANIZATION_ID, VARIANCE_TYPE FROM AX.AX_VARIANCE_STATUSES WHERE ABSORBTION_DATE BETWEEN :from_date AND :to_date;

Reporting use cases include period-close reconciliation, absorption aging analysis, and audit reporting to confirm that all variances were absorbed before period closure. Because the table includes PERIOD_YEAR, year-end roll-forward reports can be generated without joining to a period calendar, though joining via ACCOUNTING_PERIOD_ID to GL_PERIODS is more precise.

Related Objects

The ETRM metadata describes the Data Vault classification as standalone, so no formal FK dependencies were mined. However, in the context of the AX Global Accounting Engine and the columns present, the following objects typically relate to AX_VARIANCE_STATUSES:

• GL_PERIODS — joined on ACCOUNTING_PERIOD_ID = PERIOD_NAME/PERIOD_NUM context for period validation.
• ORG_ORGANIZATION_DEFINITIONS / HR_ALL_ORGANIZATION_UNITS — joined on ORGANIZATION_ID for organization naming.
• GL_LEDGERS — context for the accounting period and organization combination.
• AX_VARIANCE_HEADERS / AX_VARIANCE_LINES — the transaction-level variance details that the status row summarizes, keyed by organization, period, and variance type.
• GL_JE_HEADERS / GL_JE_LINES — journal entries generated upon absorption, referenced by ABSORBTION_DATE.
• FND_USER — joined on CREATED_BY or LAST_UPDATED_BY for audit attribution.

Because the object is a standalone hub in the modeled sense, joins are driven by the business key triplet rather than by constrained foreign keys, and referential integrity is enforced at the application layer.