Results for “ozf_time_allocations”

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

Overview

OZF_TIME_ALLOCATIONS is a Trade Management (OZF) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores time-level allocation records. It is the vehicle through which accrual, promotion, or funds allocation amounts are expressed against a specific time dimension (a period bucket or time entry) for an allocation target. In practice, this table occupies the lowest, most granular level of the Trade Management allocation hierarchy, sitting beneath account-level and product-level allocation headers and providing the temporal grain used by accrual calculation, promotional spend reporting, and funds reconciliation.

From a Data Vault modeling perspective, the mined foreign key structure suggests this object functions as a link. It carries a single-column surrogate primary key and two foreign key paths from the same column (ALLOCATION_FOR_ID) into distinct parent allocatable references, which is characteristic of a relationship or association table connecting allocation headers to time/period members rather than a pure descriptive hub or satellite.

Key Information Stored

The table is documented with 32 columns in the 12.2.2 physical schema. The most significant are:

• TIME_ALLOCATION_ID — the surrogate primary key, enforced by OZF_TIME_ALLOCATIONS_PK and mirrored by unique index OZF_TIME_ALLOCATIONS_U1. This is the column returned by the searched key ozf_time_allocations_pk.
• ALLOCATION_FOR and ALLOCATION_FOR_ID — the polymorphic reference identifying the allocation parent, resolved against either account or product allocations.
• TIME_ID — the time dimension member against which the allocation is recorded.
• PERIOD_TYPE_ID — the period type governing the time bucket semantics.
• TARGET — the planned or target allocation quantity/amount for the time bucket.
• LYSP_SALES — last year same period sales, a comparison baseline used in accrual and performance calculations.
• ACCOUNT_STATUS — status flag affecting whether the allocation row participates in downstream processing.
• ORG_ID — the multi-org operating unit discriminator.
• SECURITY_GROUP_ID — the Trade Management security grouping referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OZF business object layer.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard who-column audit set.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS DFF/extension flexfield block.

Note that TIME_ALLOCATION_ID is both the primary key and the only documented business-key candidate; the ALLOCATION_FOR_ID column is not unique because a single parent may have many time-level children.

Common Use Cases and Queries

Typical uses include accrual roll-forward reporting, promotional spend analysis by period, and reconciliation of account- and product-level allocations to their time distribution. A common pattern retrieves all time rows for one allocation header:

• SELECT TIME_ALLOCATION_ID, TIME_ID, PERIOD_TYPE_ID, TARGET, LYSP_SALES FROM OZF_TIME_ALLOCATIONS WHERE ALLOCATION_FOR = :p_type AND ALLOCATION_FOR_ID = :p_id AND ORG_ID = :p_org ORDER BY TIME_ID;
• Point lookup by primary key: SELECT * FROM OZF_TIME_ALLOCATIONS WHERE TIME_ALLOCATION_ID = :p_id;
• Security-filtered reporting joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID.
• Aggregation of LYSP_SALES and TARGET by PERIOD_TYPE_ID for trend and variance dashboards.

Related Objects

• OZF_ACCOUNT_ALLOCATIONS — parent header for account-level allocations; joined via OZF_TIME_ALLOCATIONS.ALLOCATION_FOR_ID = OZF_ACCOUNT_ALLOCATIONS.<pk> when ALLOCATION_FOR indicates an account target.
• OZF_PRODUCT_ALLOCATIONS — parent header for product-level allocations, joined through the same ALLOCATION_FOR_ID column.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID to enforce Trade Management data security.
• OZF_TIME_ALLOCATIONS_PK / OZF_TIME_ALLOCATIONS_U1 — the primary key constraint and unique index that identify rows.
• Time dimension tables supplying TIME_ID and PERIOD_TYPE_ID values consumed by this table.

The polymorphic ALLOCATION_FOR_ID design means joins to OZF_ACCOUNT_ALLOCATIONS and OZF_PRODUCT_ALLOCATIONS must be gated by the ALLOCATION_FOR discriminator value to avoid fan-out errors in reporting queries.