Search Results get_target_pkey

Overview

OZF_ALLOCATION_ENGINE_PVT is a private PL/SQL package in the APPS schema that implements the core allocation engine for Oracle Trade Management (formerly Oracle Marketing) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its responsibility is to distribute trade management targets, funds, products, and time-based allocations across accounts and territories according to the allocation rules configured by the marketing or trade promotions administrator. The package belongs to the OZF (Oracle Funds) module and is classified as a PVT ("private") API, meaning it is intended for internal consumption by other OZF packages rather than as a public, customer-facing API.

In business terms, the engine answers questions such as how much of a promotional fund or quota target should be assigned to each account, how product-level and time-period spreads should cascade through a hierarchy of allocations, and how sales achievements should be retrieved and compared against targets. It underpins quota allocation, funds management, and account/product allocation workflows that drive trade promotion planning and settlement.

Key Procedures and Functions

• SETUP_PRODUCT_SPREAD — Establishes the initial product-level spread used to distribute an allocation across a set of products.
• CASCADE_PRODUCT_SPREAD — Propagates a product spread down through dependent allocation records, applying the spread logic across the hierarchy.
• ALLOCATE_TARGET — Performs the primary allocation of a target value to accounts or territories based on the configured allocation method.
• GET_TARGET — Retrieves the target value associated with a given allocation record.
• GET_TARGET_PKEY — Returns the primary key of the target entity, used for linking and lookups.
• GET_SALES — Fetches sales (actual) figures to compare against allocated targets, leveraging activity metric data.
• GET_PROD_ALLOC_COUNT — Returns the count of product allocation records, typically used to control iteration or validation logic.
• ADJUST_ACCOUNT_TARGETS — Adjusts account-level targets, allowing reallocation or correction after initial distribution.

The package depends on FND_API for standard Oracle Application Object Library error handling and message conventions, and STANDARD for basic PL/SQL utilities.

Tables Accessed

• OZF_ACCOUNT_ALLOCATIONS / _S — Primary stores for account-level allocation records read and written during target allocation and adjustment.
• OZF_PRODUCT_ALLOCATIONS / _S — Product-level allocation data, used by the product spread procedures.
• OZF_TIME_ALLOCATIONS / _S — Time-phased allocation data supporting period-based distribution.
• OZF_FUNDS_ALL_B — Base table of trade promotion funds that provide the source amounts for allocation.
• OZF_ACT_METRICS_ALL and OZF_ACT_METRIC_FACTS_ALL — Activity metrics and facts used by GET_SALES to compare actual performance against targets.
• AMS_ACT_PRODUCTS and AMS_PARTY_MARKET_SEGMENTS — Marketing activity-product associations and party market segmentation used to determine allocation scope.
• JTF_TERR_ALL, JTF_TERR_RSC_ALL, JTF_TERR_RSC_ACCESS_ALL — Territory and territory resource tables used to resolve territory-based allocation targets and access.
• MTL_ITEM_CATEGORIES — Item category data used to group products for allocation.

Usage Notes

Because OZF_ALLOCATION_ENGINE_PVT is a private package, it is not invoked directly through a standard concurrent program submission form; instead, it is called from public OZF APIs and loaders. The documented reference chain shows it is referenced by OZF_ALLOCATION_ENGINE_PVT_W (a wrapper), OZF_PARTY_MKT_SEG_LOADER_PVT, OZF_QUOTA_ALLOCATIONS_PVT, and OZF_QUOTA_PUB, indicating that quota allocation and party market segment loading processes drive its procedures.

Typical invocation occurs when an administrator runs allocation or quota-related concurrent programs, or when the Trade Management allocation UI triggers the public wrapper package. Custom code should call the public packages (such as OZF_QUOTA_PUB) rather than this private package, and should pass the standard FND_API initialization parameters so that error handling remains consistent with Oracle EBS conventions.