Search Results ap_aud_rule_sets_pk

Overview

AP_AUD_RULE_SETS is a Payables (AP) module table in the AP schema that stores audit rule set definitions. Audit rule sets are the configuration backbone of Payables Invoice Audit, governing how invoices are selected for review, which violations trigger auditor involvement, when holds or notifications are raised, and whether receipt documentation (paper or image) is mandatory. Each row defines a named rule set that can be assigned to operating units, suppliers, or user responsibility through the assignment table AP_AUD_RULE_ASSIGNMENTS_ALL. In Oracle EBS 12.1.1 and 12.2.2 the object retains the same 76-column physical definition and the VALID status within the AP schema.

Using heuristic Data Vault classification mined from the foreign key structure, this table presents a satellite-leaning profile. It centers on a single surrogate key with descriptive, time-bounded attributes; the currency reference to FND_CURRENCIES acts as a small supporting lookup rather than a true hub-link relationship. This classification is a modeling suggestion only, not a physical constraint in EBS.

Key Information Stored

The primary key is the surrogate RULE_SET_ID, enforced by AP_AUD_RULE_SETS_PK. A unique index, AP_AUD_RULE_SETS_U1, also exists on RULE_SET_ID; RULE_SET_NAME serves as the natural business identifier used by administrators. The most significant columns include:

• RULE_SET_NAME and RULE_SET_TYPE — the identifying name and classification of the rule set.
• START_DATE / END_DATE — the effective date range during which the rule set applies.
• RANDOM_AUDIT_FLAG / RANDOM_AUDIT_PERCENTAGE — control random sampling of invoices for audit.
• AUDIT_ALL_VIOLATIONS_FLAG, AUDIT_ALL_FROM_AUDIT_LIST_FLAG, AUDIT_ALL_OLD_RECEIPTS_FLAG and AUDIT_ALL_RECEIPT_DAYS_LIMIT — define the "audit all" cohorts.
• AUDIT_ALL_AMOUNT_CODE, AUDIT_ALL_AMOUNT_LIMIT, AUDIT_ALL_AMOUNT_CURRENCY_CODE — threshold-based selection, with currency validated against FND_CURRENCIES.
• MONTHLY_TOTAL_ALLOWED, MONTHLY_VIOLATIONS_ALLOWED, MONTHLY_REPORTS_ALLOWED — tolerance limits tracked per period.
• AUDIT_TERM_DURATION_DAYS — the audit window duration.
• HOLD_CODE, NOTIFY_DOCUMENT_REQUIRED_CODE, NOTIFY_RESPONSE_OVERDUE_DAYS — hold and notification behavior.
• RECEIPT_DELAY_DAYS, CASH_LIMIT, CARD_LIMIT, MILEAGE_LIMIT and their _ENABLED flags — expense and receipt constraints.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on reviewing active rule sets and their audit triggers. A common pattern lists currently effective configurations:

• SELECT rule_set_id, rule_set_name, rule_set_type, start_date, end_date FROM ap.ap_aud_rule_sets WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

Reporting queries frequently join to the assignment table to show which rule set applies to which operating unit or supplier:

• SELECT rs.rule_set_name, ra.rule_set_id, ra.org_id FROM ap.ap_aud_rule_sets rs, ap.ap_aud_rule_assignments_all ra WHERE rs.rule_set_id = ra.rule_set_id;

Auditors also query the threshold and sampling columns (for example RANDOM_AUDIT_FLAG, AUDIT_ALL_AMOUNT_LIMIT) to validate that configuration matches audit policy, and use the WHO columns to track who last modified a rule set.

Related Objects

The table participates in a small, focused set of relationships:

• FND_CURRENCIES — joined via AP_AUD_RULE_SETS.AUDIT_ALL_AMOUNT_CURRENCY_CODE to resolve the currency of amount-limit rules.
• AP_AUD_RULE_ASSIGNMENTS_ALL — references RULE_SET_ID; the child table that assigns rule sets to organizational contexts.
• AP_AUD_RULE_SET_ITEMS (and related audit rule item tables) — hold the line-level rule elements that compose a rule set.
• Payables Invoice Audit concurrent programs and the Invoice Workbench — consume the rule set configuration at runtime.
• AP Invoice audit reports and the Audit List inquiry — rely on this table for selection and hold behavior.

Because the table is a configuration satellite, custom reports should treat it as read-only reference data and modify rules only through the standard Payables Audit Rule Sets setup UI.