Search Results ben_acty_rt_pymt_sched_f




Overview
Explore in AI Chat

Overview

BEN_ACTY_RT_PYMT_SCHED_F is a date-tracked (designated by the "_F" suffix) table in the BEN schema of Oracle Advanced Benefits (OAB). It stores the payment schedule definitions that govern how activity rates are paid out. In Oracle Advanced Benefits, an activity rate is the cost or credit associated with a benefit activity — such as an enrollment, a life event, or a rate calculation — and this table records the schedule (frequency, timing, and related rules) by which those rates are disbursed or applied over a defined period. It sits within the rate and payment infrastructure that supports payroll-facing and cost calculations for benefits plans.

Because the table carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE as part of its primary key, it is a fully date-effective entity, meaning each logical payment schedule can have multiple historical and future-dated rows, and queries must apply effective-date filtering to return the correct version. From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as standalone, suggesting it functions either as a hub in its own right or as a descriptive satellite with no tightly coupled parent link in the extracted relationship graph.

Key Information Stored

The table is documented with 44 physical columns. The most significant are the following:

  • ACTY_RT_PYMT_SCHED_ID — the surrogate identifier for the payment schedule. It forms the leading component of the composite primary key BEN_ACTY_RT_PYMT_SCHED_F_PK.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the date-effective boundaries. Together with the surrogate ID they constitute the full primary key and are the business-key candidates surfaced through the unique index.
  • PYMT_SCHED_CD — the payment schedule code, the business identifier classifying the schedule type or frequency.
  • PYMT_SCHED_RL — the payment schedule rule, defining how the schedule is applied or calculated.
  • ACTY_BASE_RT_ID — references the activity base rate to which this schedule is attached, linking the schedule to its underlying rate definition.
  • BUSINESS_GROUP_ID — the operating business group (legislation/enterprise) that owns the row, used for multi-tenant filtering and security.
  • APF_ATTRIBUTE_CATEGORY and APF_ATTRIBUTE1 through APF_ATTRIBUTE30 — a descriptive flexfield (DFF) block allowing customer-specific attributes to be captured without schema changes.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard "WHO" audit columns present on nearly every Oracle EBS transactional table.
  • OBJECT_VERSION_NUMBER — the optimistic-locking version counter used by the OAF/BC4J framework to detect concurrent updates.

Common Use Cases and Queries

The primary use cases involve reporting on and validating how activity rates are scheduled for payment. Typical scenarios include extracting all current schedules for a business group, checking which base rate a schedule is linked to, and reconciling DFF attributes captured by configuration teams.

A standard effective-date-aware query retrieves only the currently active version of each schedule:

  • SELECT ACTY_RT_PYMT_SCHED_ID, PYMT_SCHED_CD, PYMT_SCHED_RL, ACTY_BASE_RT_ID
    FROM BEN.BEN_ACTY_RT_PYMT_SCHED_F
    WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE
      AND BUSINESS_GROUP_ID = :p_business_group_id;
  • Historical/audit query: add ORDER BY ACTY_RT_PYMT_SCHED_ID, EFFECTIVE_START_DATE and drop the SYSDATE predicate to view all versions.
  • Flexfield reporting: select APF_ATTRIBUTE_CATEGORY alongside individual APF_ATTRIBUTEn columns to expose customer-defined data.
  • Rate linkage join: join to the activity base rate table on ACTY_BASE_RT_ID to resolve rate details.

Because date-effective tables accrue multiple rows per logical entity, reports must always constrain or window on the effective dates to avoid duplicate counting.

Related Objects

Although the mined metadata classifies this object as standalone, its column semantics establish practical relationships to other BEN rate objects. The most significant related objects include:

  • Activity base rate table (BEN_ACTY_BASE_RT_F) — joined on ACTY_BASE_RT_ID to resolve the base rate this schedule pays.
  • BEN_ACTY_RT_PYMT_SCHED_F_PK — the primary key index underpinning the table, referenced by any child or dependent rows.
  • Business group reference (HR_OPERATING_UNITS / PER_BUSINESS_GROUPS) — joined on BUSINESS_GROUP_ID.
  • Standard WHO audit columns — LAST_UPDATED_BY and CREATED_BY resolve to FND_USER for audit reporting.
  • APF descriptive flexfield definition — the APF_ATTRIBUTE columns are governed by the registered DFF definition for this table.

Consumers should treat this table as the authoritative source for payment schedule definitions and always respect its date-effective nature when joining, filtering, or extracting data for benefit rate calculations.