Results for “ap_pol_schedule_options”

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

Overview

AP_POL_SCHEDULE_OPTIONS is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. As stated in the ETRM metadata, the table stores policy schedule-specific rules. It functions as the configuration backbone behind payment policy schedules, holding the discrete constraints, thresholds, and attribute filters that determine how Payables selects, groups, and schedules invoices during payment processing. Each row represents a single rule applied within the context of a parent payment policy header; the collection of rows for a given POLICY_ID defines the complete behavior of that schedule. Because the table captures rules that bind policies to organizational and financial attributes — role, location, currency, vehicle type, and fuel type — it is central to enforcing payment policy compliance and to generating accurate scheduled payment selections.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a link. This is a modeling suggestion rather than a documented Oracle attribute: the table sits at the intersection of several reference entities (policy headers, currencies, jobs, grades, positions, and locations), so it is naturally expressed as a relationship construct connecting those hubs rather than as a standalone descriptive entity.

Key Information Stored

The table is documented with 18 columns. The most operationally significant are:

• SCHEDULE_OPTION_ID — the surrogate primary key, enforced by AP_POL_SCHEDULE_OPTIONS_PK and also carried by the unique index AP_POL_SCHEDULE_OPTIONS_U1. This is the row identifier and the strongest business-key candidate documented.
• POLICY_ID — foreign key to AP_POL_HEADERS, linking each rule to its parent payment policy.
• OPTION_TYPE and OPTION_CODE — classify the rule and its specific value, defining what constraint the row applies.
• THRESHOLD — the monetary or numeric boundary that qualifies or excludes invoices for the rule.
• ROLE_ID — a multi-target foreign key resolving to PER_JOBS, PER_GRADES, or PER_ALL_POSITIONS, tying the rule to a role definition.
• LOCATION_ID — foreign key to AP_POL_LOCATIONS_B, scoping the rule to a location.
• CURRENCY_CODE — foreign key to FND_CURRENCIES, constraining the rule by currency.
• VEHICLE_TYPE_CODE and FUEL_TYPE_CODE — descriptive classifications specific to policy scheduling.
• RATE_TYPE_CODE — identifies the rate basis used by the rule.
• END_DATE and STATUS — control the effective period and active state of the rule.
• The standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — provide WHO-column style change tracking.

Common Use Cases and Queries

Typical uses include diagnosing why an invoice was or was not selected for a scheduled payment, auditing policy configuration across currencies and locations, and reporting on threshold coverage. A common join retrieves all rules for a policy:

SELECT o.schedule_option_id, o.option_type, o.option_code, o.threshold, o.currency_code, o.status FROM ap.ap_pol_schedule_options o WHERE o.policy_id = :policy_id AND o.status = 'A';

Currency-scoped analysis joins FND_CURRENCIES, while location-scoped analysis joins AP_POL_LOCATIONS_B. Effective-dating checks filter on END_DATE to isolate currently valid rules.

Related Objects

The most significant related objects, per the documented foreign keys, are:

• AP_POL_HEADERS — joined on POLICY_ID; the parent policy definition.
• AP_POL_LOCATIONS_B — joined on LOCATION_ID.
• FND_CURRENCIES — joined on CURRENCY_CODE.
• PER_JOBS, PER_GRADES, and PER_ALL_POSITIONS — all joined on ROLE_ID, the multi-target role reference.
• AP_POL_SCHEDULE_OPTIONS_PK and AP_POL_SCHEDULE_OPTIONS_U1 — the primary and unique indexes governing row identity.