Results for “pst_attribute30”

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

Overview

BEN_PSTN_RT_X is a date-effective (current-record) view owned by the APPS schema within the BEN — Advanced Benefits product of Oracle E-Business Suite. It exposes position rate records used by Oracle Advanced Benefits to associate a variable rate profile with a specific position, effectively driving eligibility and rate determination at the position level. The view presents only those rows whose effective date range includes the current system date, since its defining query filters the underlying base table with TRUNC(SYSDATE) BETWEEN PST.EFFECTIVE_START_DATE AND PST.EFFECTIVE_END_DATE. This makes BEN_PSTN_RT_X the standard "as-of-today" reporting interface for position rate configuration data.

In EBS 12.1.1 and 12.2.2, Advanced Benefits follows a datetrack pattern in which each business object is stored in an _F (full) table that carries all historical and future-dated versions, while an _X view filters that table down to the currently active version. The "_X" suffix denotes this single-row-per-key projection rather than a purely technical synonym. The view is therefore read-only in practice and is the object that forms and reports should query when current, effective-dated position rate information is required.

Underlying Base Objects

The view is defined solely over the base table BEN_PSTN_RT_F, which is referenced through a synonym. The defining SELECT projects PST.ROWID along with a fixed column list from BEN_PSTN_RT_F, aliased as PST, and restricts the result set using the SYSDATE-based BETWEEN predicate on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. Because only the base _F table is referenced, no joins are performed; the relationship is a straightforward one-to-many reduction in which many dated rows in BEN_PSTN_RT_F collapse to at most one current row in BEN_PSTN_RT_X as of the query execution date. The base table retains the complete history, whereas the view provides the temporal slice appropriate for transactional and operational consumption.

Key Columns

• PSTN_RT_ID — the primary identifier for the position rate record; this is the column most frequently used in searches and joins.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack boundaries that determine whether a row is included by the view.
• BUSINESS_GROUP_ID — the operating business group (enterprise) to which the record belongs; essential for multi-organization filtering.
• VRBL_RT_PRFL_ID — foreign key to the variable rate profile associated with the position.
• POSITION_ID — the position to which the rate profile assignment applies.
• EXCLD_FLAG — indicates whether the record is excluded from processing.
• ORDR_NUM — the ordering sequence used to resolve multiple rate assignments.
• PST_ATTRIBUTE_CATEGORY and PST_ATTRIBUTE1 through PST_ATTRIBUTE30 — the standard descriptive flexfield (DFF) context and segment columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — the standard who-columns and optimistic locking column maintained across EBS.
• ROW_ID — the base row identifier exposed by the SELECT, useful for direct row addressing.

Common Use Cases and Queries

Typical scenarios include reporting the current variable rate profile assigned to each position, validating position-level rate configuration before a benefits run, and resolving a PSTN_RT_ID obtained from a form or interface back into its effective position and profile context.

Retrieve the current record for a known identifier:

• SELECT pstn_rt_id, position_id, vrbl_rt_prfl_id, effective_start_date, effective_end_date
• FROM ben_pstn_rt_x WHERE pstn_rt_id = :p_pstn_rt_id;

List all active position rate assignments for a business group:

• SELECT pstn_rt_id, position_id, vrbl_rt_prfl_id, ordr_num, excld_flag
• FROM ben_pstn_rt_x WHERE business_group_id = :p_bg_id ORDER BY position_id, ordr_num;

Join to the base table to compare current versus historical versions, or join POSITION_ID to HR_ALL_POSITIONS_F to obtain position names. Because the view has no effective-date bind parameters, historical analysis must query BEN_PSTN_RT_F directly with an explicit date predicate rather than BEN_PSTN_RT_X.