Results for “ozf_threshold_rules”

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

Overview

The OZF_THRESHOLD_RULES view is a Trade Management (OZF) reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the configuration of threshold rules that govern accrual and settlement behavior within Oracle Trade Management. A threshold rule defines the conditions, limits, and operators under which a threshold accrual is evaluated or applied. The view presents a secured, operating-unit-aware projection of the underlying threshold rule data, filtering rows based on the organization context derived from the session's CLIENT_INFO value. Because it is a view rather than a base table, it is the preferred access point for SQL-based reporting, concurrent programs, and integrations that need to read threshold rule definitions without managing multi-org security filters explicitly. The THRESHOLD_RULE_ID is the primary unique identifier for each rule row and is the column most commonly referenced in foreign-key joins and ad hoc queries.

Underlying Base Objects

The view is defined over a single documented base object, OZF_THRESHOLD_RULES_ALL, referenced through a synonym. It is a row-level secured view: the WHERE clause compares the ORG_ID of each base row against the operating unit resolved from USERENV('CLIENT_INFO'). When the session does not supply a valid organization context, the comparison resolves to -99, which restricts the result set accordingly. The view text also includes ROWID and the full column projection of the base table, ensuring that all descriptive, control, and DFF attribute columns are surfaced. Because the view selects from an _ALL table, it inherits the partitioned-by-operating-unit model of ETRM data: the physical storage contains rows for all operating units, and the view applies the security predicate at query time.

Key Columns

• THRESHOLD_RULE_ID — Surrogate primary key uniquely identifying each threshold rule.
• THRESHOLD_ID — Foreign key linking the rule to its parent threshold definition.
• PERIOD_TYPE, THRESHOLD_CALENDAR, START_PERIOD_NAME, END_PERIOD_NAME — Define the period basis and calendar window over which the rule applies.
• START_DATE, END_DATE — Effective date range for the rule.
• VALUE_LIMIT, OPERATOR_CODE, PERCENT_AMOUNT, BASE_LINE — Define the comparison threshold, the operator applied, the percentage value, and the base measure against which the rule is evaluated.
• ENABLED_FLAG — Indicates whether the rule is active.
• ERROR_MODE, REPEAT_FREQUENCY, FREQUENCY_PERIOD, CONVERTED_DAYS — Control error handling and recurrence behavior.
• ORG_ID, SECURITY_GROUP_ID — Multi-org and security grouping columns.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — Descriptive flexfield columns.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) — Audit trail.

Common Use Cases and Queries

Typical use cases include reporting active rules for a threshold, validating configuration during period close, and integrating rule definitions into downstream accrual calculations. A representative query that lists enabled rules for a given threshold is:

SELECT threshold_rule_id, threshold_id, period_type, operator_code, value_limit, start_date, end_date
FROM apps.ozf_threshold_rules
WHERE threshold_id = :p_threshold_id
AND enabled_flag = 'Y'
ORDER BY threshold_rule_id;

Because the view enforces operating unit security, ensure the session's client information is set (for example via FND_GLOBAL.APPS_INITIALIZE) before querying, or the result set may be incomplete or empty.