Search Results ams_act_logs_transaction_id_s




Overview
Explore in AI Chat

Overview

OZF_QUOTA_THRESHOLD_PVT is a private (PVT) PL/SQL package body in the APPS schema that supports Oracle EBS Trade Management (formerly Oracle Sales Compensation / Quota Management) functionality. It implements the internal logic used to monitor, validate, and act upon quota thresholds defined for sales organizations, resources, or territories. The package evaluates quota attainment against configurable threshold rules, generates alert notifications when thresholds are crossed, and writes activity log entries to record each threshold evaluation event. It is classified as a private API, meaning it is intended for internal consumption by other Trade Management packages and does not constitute a public integration interface.

Key Procedures and Functions

  • VALIDATE_QUOTA_THRESHOLD — Core validation routine that checks whether a given quota figure satisfies the criteria defined in the threshold rule configuration. It resolves the applicable threshold definition and rules and determines if the condition for triggering an alert has been met.
  • OPERATION_RESULT — Encapsulates the outcome of a threshold evaluation or alert operation, returning a status/result indicator that callers use to branch logic and to drive subsequent processing.
  • VERIFY_NOTIFICATION — Confirms that a notification (alert) has been or should be generated for a threshold breach, preventing duplicate or spurious notifications and validating notification eligibility before alerts are raised.
  • UPDATE_ALERTS — Persists or updates alert records in the quota alert tables, reflecting newly detected threshold breaches or changes in threshold status so that the alerting subsystem remains current.

Tables Accessed

The package reads and writes several Trade Management tables through APPS synonyms. Quota and alert state is stored in OZF_QUOTA_ALERTS and its sequence-backed shadow table OZF_QUOTA_ALERTS_S. Threshold configuration is sourced from OZF_THRESHOLDS_ALL_B and OZF_THRESHOLD_RULES_ALL. Quota, fund, and allocation context is drawn from OZF_FUNDS_ALL_B, OZF_FUND_DETAILS_V, OZF_ACCOUNT_ALLOCATIONS, OZF_PRODUCT_ALLOCATIONS, and OZF_CUST_DAILY_FACTS, while OZF_DASHB_DAILY_KPI supplies KPI facts used in threshold evaluation. OZF_LOOKUPS provides lookup code decoding. The package writes audit and activity records to AMS_ACT_LOGS and its sequence tables AMS_ACT_LOGS_S and AMS_ACT_LOGS_TRANSACTION_ID_S, the latter being the object most commonly associated with this dependency chain, since it supplies the surrogate transaction identifier assigned to each logged activity. Utility and framework dependencies include OZF_UTILITY_PVT, FND_API, FND_DSQL, FND_FILE, FND_GLOBAL, FND_MESSAGE, and FND_MSG_PUB, plus DBMS_SQL, DUAL, and PLITBLM.

Usage Notes

Because OZF_QUOTA_THRESHOLD_PVT is a private package, it is not invoked directly from Oracle Forms or standard concurrent programs. It is called by other APPS-level packages within the quota threshold processing flow — for example, wrapper packages that schedule threshold evaluation, or public APIs that delegate internal validation and alert updating to this body. Typical invocations occur during concurrent quota processing runs, alert generation jobs, and dashboard/KPI refresh routines that need to determine whether quota attainment has crossed a configured threshold. The package uses the FND message stack for error handling and standard FND_API conventions for result reporting. Customizations should avoid calling this package directly; instead, integrators should target the public quota or alert APIs and let this private package handle threshold validation, notification verification, and activity logging internally.