Results for “ben_pstn_rt”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BEN_PSTN_RT is an Oracle E-Business Suite Advanced Benefits (BEN) view owned by the APPS schema. It exposes the current effective rows of the position rate entity, which associates a variable rate profile with a specific position and an exclusion flag. In the Advanced Benefits data model, position rates are used by the benefits engine during eligibility and rate calculation processing; they allow organizations to override the standard variable rate assigned to a position for a defined effective period.
The view does not store data independently. It is a reporting and integration facade over the base table BEN_PSTN_RT_F, applying a date-filtering predicate that restricts the returned rows to those effective as of the session effective date. This design makes BEN_PSTN_RT the preferred access point for concurrent programs, BI Publisher extracts, and custom APIs that must see only date-effective (non-history) position rate records without explicitly coding the effective-date logic.
Because the view is defined with a USERENV('SESSIONID') subquery, correct results depend on a valid FND_SESSIONS context. Queries executed outside a normal EBS application session — for example, directly in SQL*Plus against the APPS schema without initializing session context — may return no rows or fail to resolve the effective date.
Underlying Base Objects
The view is defined over two documented objects:
- BEN_PSTN_RT_F (SYNONYM) — the base table holding the position rate rows. The view selects from this table using the alias PST. The trailing _F denotes a date-effective (non-versioned) table that carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns.
- FND_SESSIONS (SYNONYM) — the Oracle Application Object Library session table. Two correlated subqueries retrieve SS.EFFECTIVE_DATE for the current USERENV('SESSIONID'), supplying the effective date used to filter the base table.
The view text selects ROWID from the alias PST along with the entity columns and the standard audit and concurrency columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER). The effective-date filter is: PST.EFFECTIVE_START_DATE <= session effective date AND PST.EFFECTIVE_END_DATE >= session effective date. The view is documented as VALID in the ETRM metadata for 12.2.2 and is unchanged in substance for 12.1.1.
Key Columns
- PSTN_RT_ID — primary key of the position rate record, sourced from BEN_PSTN_RT_F.
- EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range for which the row is valid. These drive the view's filtering predicate.
- BUSINESS_GROUP_ID — identifies the business group (HR security organization) owning the row.
- VRBL_RT_PRFL_ID — foreign key to the variable rate profile applied to the position.
- POSITION_ID — foreign key to the HR position (PER_ALL_POSITIONS) to which the rate applies.
- EXCLD_FLAG — indicates whether the position is excluded from the associated rate profile.
- ORDR_NUM — sequencing number used to order multiple position rate rows.
- PST_ATTRIBUTE_CATEGORY and PST_ATTRIBUTE1 through PST_ATTRIBUTE30 — descriptive flexfield (DFF) segments for customer-defined data.
- ROW_ID — the row identifier of the underlying base table row, exposed for update/delete operations through the view.
- OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Forms and OAF layers.
Common Use Cases and Queries
Typical uses include rate profile validation, position-based benefits reporting, and integration extracts that must reflect only the currently effective position rate configuration. A simple query retrieves the active position rates for a business group:
SELECT pstn_rt_id, effective_start_date, effective_end_date, position_id, vrbl_rt_prfl_id, excld_flag, ordr_num FROM ben_pstn_rt WHERE business_group_id = :p_business_group_id ORDER BY position_id, ordr_num;
To inspect the rate profile assigned to a specific position as of today:
SELECT position_id, vrbl_rt_prfl_id, effective_start_date, effective_end_date FROM ben_pstn_rt WHERE position_id = :p_position_id;
Because the effective date comes from FND_SESSIONS, results reflect the session effective date rather than SYSDATE. Analysts comparing history should query the base table BEN_PSTN_RT_F directly, since the view by design hides rows whose effective range does not include the current session date. Any query joining to per_all_positions, per_all_people_f, or ben_vrbl_rt_prfl should join on the exposed foreign keys and respect the business group for multi-organization installations.
-
View: BEN_PSTN_RT 12.2.2
APPS.BEN_PSTN_RT·↳ BEN_PSTN_RT_F·↳ FND_SESSIONS·Explore BEN module →
-
View: BEN_PSTN_RT 12.1.1
APPS.BEN_PSTN_RT·↳ BEN_PSTN_RT_F·↳ FND_SESSIONS·Explore BEN module →
-
SYNONYM: PUBLIC.BEN_PSTN_RT 12.1.1
-
VIEW: APPS.BEN_PSTN_RT 12.2.2
-
VIEW: APPS.BEN_PSTN_RT 12.1.1
-
SYNONYM: APPS.BEN_PSTN_RT_F 12.1.1
-
SYNONYM: APPS.BEN_PSTN_RT_F 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.FND_SESSIONS 12.1.1
-
SYNONYM: APPS.FND_SESSIONS 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - BEN Tables and Views 12.1.1
Start and End periods.
-
eTRM - BEN Tables and Views 12.2.2
Start and End periods.
-
eTRM - BEN Tables and Views 12.1.1
Start and End periods.
-
eTRM - BEN Tables and Views 12.2.2
Start and End periods.