Search Results activity_date

Overview

GL.GL_SHARES_ACTIVITY is a General Ledger table that records stock split and dividend events affecting ledger balances. In Oracle EBS 12.1.1 and 12.2.2, it stores the corporate actions that alter the number of outstanding shares or distribute earnings, providing the activity register that supports equity-related consolidation and reporting. Each row represents a discrete split or dividend activity keyed to a specific ledger and effective date.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. The table's natural key — LEDGER_ID combined with ACTIVITY_DATE and ACTIVITY_TYPE_CODE — describes an event tied to an existing ledger hub, and the surrounding ratio and percentage columns capture descriptive, time-stamped attributes rather than independent entities. This suggests the object behaves like a satellite table anchored to GL_LEDGERS.

Key Information Stored

The table contains 27 columns. The most significant are the business-key and descriptive attributes:

• LEDGER_ID — identifies the ledger to which the corporate action applies; also the foreign key to GL_LEDGERS.
• ACTIVITY_DATE — the effective date of the split or dividend; central to the composite primary key and a frequent filter predicate.
• ACTIVITY_TYPE_CODE — distinguishes the nature of the activity (split versus dividend).
• SPLIT_RATIO_FROM and SPLIT_RATIO_TO — the before/after share ratios defining a stock split.
• DIVIDEND_PERCENT — the dividend percentage applied when the activity is a dividend.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns tracking row provenance.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns for extensible, client-defined attributes.

The surrogate primary key is defined by GL_SHARES_ACTIVITY_PK (LEDGER_ID, ACTIVITY_DATE, ACTIVITY_TYPE_CODE). This same column set is also enforced by the unique index GL_SHARES_ACTIVITY_U1, making it the business-key candidate — the combination that uniquely identifies a corporate action.

Common Use Cases and Queries

Typical usage centers on retrieving and reporting corporate actions by ledger and date range. A common pattern joins the table to its parent ledger and filters on the activity date:

• Enumerating splits and dividends for a ledger within a fiscal window: SELECT ledger_id, activity_date, activity_type_code, split_ratio_from, split_ratio_to, dividend_percent FROM gl_shares_activity WHERE ledger_id = :ledger_id AND activity_date BETWEEN :from_date AND :to_date;
• Auditing recent setup changes via the audit columns: SELECT created_by, creation_date, last_updated_by, last_update_date FROM gl_shares_activity WHERE ledger_id = :ledger_id;
• Isolating splits only: filter on ACTIVITY_TYPE_CODE and select SPLIT_RATIO_FROM/SPLIT_RATIO_TO.
• Reporting dividends: filter on type and select DIVIDEND_PERCENT.

Because ACTIVITY_DATE is part of both the primary key and the unique index, queries filtering on it benefit from index-driven access paths.

Related Objects

The primary relationship is the foreign key to the ledger definition. The most significant related objects are:

• GL_LEDGERS — joined on GL_SHARES_ACTIVITY.LEDGER_ID = GL_LEDGERS.LEDGER_ID; the documented foreign key.
• GL_SHARES_ACTIVITY_PK — the composite primary key constraint.
• GL_SHARES_ACTIVITY_U1 — the unique index backing the business key.
• GL_LEDGER_RELATIONSHIPS and GL_LEDGER_CONFIG_DETAILS — related ledger metadata commonly queried alongside share activity for consolidation reporting.
• GL_DIVIDENDS / GL_DAILY_RATES — supporting reference objects for dividend processing and currency conversion where applicable.

Beyond these, the table participates in consolidation and reporting logic that depends on the ledger's share structure to compute adjusted balances.