Results for “pstn_rt_id”

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

Overview

The BEN_PSTN_RT_D view is a denormalized, display-oriented database object owned by the APPS schema within the Oracle E-Business Suite Advanced Benefits (BEN) product family. Its name follows the standard EBS convention for descriptive ("_D") views: it assembles the foreign-key identifiers stored on a base benefits entity into human-readable names so that users, reports, and integrations do not have to resolve those identifiers themselves. In this case the base entity is the position rate record, and the view resolves three separate lookups — the variable rate profile, the position, and the application user who last touched the row — into meaningful text values. Because the view is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2, it can be relied on as a stable reporting surface across those releases, and because it carries the ROWID of the underlying base row, it also supports updatable-form usage and data-correction scripts where the ROWID is used to target a specific record.

Underlying Base Objects

The view is defined over a single base table and three supporting objects joined by outer joins, so that position rate rows are returned even when a related name cannot be resolved. The documented base objects are:

• BEN_PSTN_RT_F — the position rate base table (the "_F" suffix denoting the date-tracked, effective-dated foundation table). This is the driving table of the view and supplies every displayed column except the resolved names.
• BEN_VRBL_RT_PRFL_F — the variable rate profile foundation table, joined on VRBL_RT_PRFL_ID, supplying the eligibility/variable rate profile name.
• PER_POSITIONS — the HR position view, joined on POSITION_ID, supplying the position name.
• FND_USER — the application user table, joined on LAST_UPDATED_BY, supplying the user name of the last updater.
• HR_GENERAL and HR_SECURITY — PL/SQL packages referenced by the object set; the presence of HR_SECURITY signals that the position lookup is filtered by the caller's security profile, so results can vary by user responsibility.

Key Columns

The view exposes the following columns, each inherited from the base table or resolved through the outer joins:

• ROW_ID — the ROWID of the BEN_PSTN_RT_F row; identifies the physical record.
• PSTN_RT_ID — the primary key of the underlying position rate record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window of the record; critical for as-of-date reporting.
• ELIGY_PRFL_NAME — the variable rate profile name resolved from BEN_VRBL_RT_PRFL_F.
• EXCLD_FLAG — indicates whether the position is excluded from the rate/profile assignment.
• POSITION_NAME — the position name resolved from PER_POSITIONS.
• LAST_UPDATE_DATE — timestamp of the most recent change.
• LAST_UPDATED_BY — the user name resolved from FND_USER, provided the user ID still exists in the application.

Common Use Cases and Queries

The view is typically used to audit which variable rate profiles are assigned to positions, to verify exclusions, and to trace change history. A representative query retrieves the current effective assignments for a position name:

• SELECT posn.position_name, v.eligy_prfl_name, v.excld_flag, v.effective_start_date, v.last_updated_by FROM ben_pstn_rt_d v WHERE v.position_name = :p_name AND SYSDATE BETWEEN v.effective_start_date AND NVL(v.effective_end_date, SYSDATE);
• SELECT position_name, eligy_prfl_name, last_update_date FROM ben_pstn_rt_d WHERE LAST_UPDATE_DATE >= :since ORDER BY last_update_date DESC;

Because a security-driven position join is present, the same query run under different responsibilities may return differing row sets. Note also that the view handles the effective end date as an open value; filters must apply NVL to treat NULL as unbounded.