Search Results ozf_quota_pub




Overview
Explore in AI Chat

Overview

APPS.OZF_QUOTA_PUB is a public PL/SQL API package within the Oracle EBS Trade Management (formerly Oracle Sales and Marketing) module, schema APPS. It provides the programmatic interface for creating, maintaining, and deleting quota records in the Oracle Trade Management / Channel Revenue Management (OZF) product family. Quotas represent the volume or revenue targets assigned to an organization, sales channel, or territory, and they drive downstream trade promotion, accrual, and settlement logic.

The package is classified as a PUB (public) API, indicating it is intended for direct invocation by external callers — forms, concurrent programs, and custom extensions — rather than being restricted to internal module use. It conforms to the standard Oracle EBS API conventions, depending primarily on FND_API for error handling and message stack processing, and collaborating with OZF_FUNDS_PUB for fund-related operations. The package status is VALID in the EBS 12.1.1 / 12.2.2 environment.

Key Procedures and Functions

The package exposes seven documented entry points, organized as a CREATE/UPDATE/DELETE triad across the quota header and its two allocation-spread child entities.

  • CREATE_QUOTA — Creates the quota header record, establishing the top-level quota definition.
  • UPDATE_QUOTA — Modifies an existing quota header, allowing attributes such as targets, dates, and status to be revised.
  • DELETE_QUOTA — Removes a quota and its dependent data, completing the lifecycle management triad.
  • CREATE_QUOTA_PRODUCT_SPREAD — Creates the product-level spread of a quota, distributing the quota target across products.
  • UPDATE_QUOTA_PRODUCT_SPREAD — Modifies an existing product spread, supporting repartitioning of targets.
  • CREATE_QUOTA_ACCOUNT_SPREAD — Creates the account-level spread of a quota, distributing the target across customer accounts.
  • UPDATE_QUOTA_ACCOUNT_SPREAD — Modifies an existing account spread.

No parameter lists are documented in the ETRM metadata; integrators should reference the package specification in the database (or the Oracle Trade Management User/Implementation guides) to confirm exact parameter signatures before coding.

Tables Accessed

The package reads and writes via APPS synonyms a set of quota and allocation tables. The principal write targets are OZF_ACCOUNT_ALLOCATIONS and OZF_ACCOUNT_ALLOCATIONS_S (account-level splits of quota), OZF_PRODUCT_ALLOCATIONS and OZF_PRODUCT_ALLOCATIONS_S (product-level splits), OZF_TIME_ALLOCATIONS and OZF_TIME_ALLOCATIONS_S (periodic distribution), together with OZF_ACT_METRICS_ALL (actual metrics used to measure attainment), OZF_THRESHOLDS_ALL_B (threshold definitions), and OZF_TERR_LEVELS_ALL (territory levels for quota assignment).

Supporting reference tables include HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, and JTF_RS_RESOURCE_EXTNS for customer and resource validation, AMS_ACT_PRODUCTS for product context within activities, and OZF_FUNDS_ALL_B for linkage between quotas and trade funds.

Usage Notes

OZF_QUOTA_PUB is normally invoked indirectly from the Oracle Trade Management HTML/forms user interface when a user defines or edits quotas and their product/account/time spreads, the corresponding form calls this public API to persist the data. It may also be called from concurrent programs that bulk-load quota data or recalculate spreads, and from custom PL/SQL or EBS-integration code where a programmatic quota definition is required.

Because the package follows FND_API conventions, callers should initialize the standard API error-handling context, pass the expected parameters, and inspect the returned success/failure flag and message stack before committing. The package is referenced by no other packages in the documented dependency set, making it a leaf-level API intended for external invocation. Always invoke through the APPS schema rather than the base OZF schema, and validate all setup prerequisites (funds, territories, customer accounts, products) prior to calling the create procedures.