Search Results dot_attribute1




Overview
Explore in AI Chat

Overview

BEN_DPNT_OTHR_PTIP_RT is an APPS-owned view within the Oracle Advanced Benefits (BEN) module. It presents the date-tracked, session-filtered representation of dependent and other participant records associated with variable rate profiles and plan-type-in-plan (PTIP) configurations. The view is a runtime (RT) object, meaning it returns only those rows whose effective date range encompasses the effective date of the current user session, as recorded in FND_SESSIONS. This behavior enforces the standard Oracle EBS date-tracked pattern, ensuring that callers always see the version of a record that is valid as of the session's effective date.

From a reporting and integration perspective, the view is the primary read interface for runtime access to the underlying _F (base) table. External interfaces, concurrent programs, and personalizations that need to resolve the attribute columns — most notably DOT_ATTRIBUTE1 through DOT_ATTRIBUTE30 — should read from this view rather than the base table to benefit from the date-effective filter. The user query "dot_attribute1" maps directly to the DOT_ATTRIBUTE1 column exposed here, a descriptive flexfield (DFF) segment associated with the DOT_ATTRIBUTE_CATEGORY.

Underlying Base Objects

The view is defined over two referenced objects, both resolved through APPS synonyms:

  • BEN_DPNT_OTHR_PTIP_RT_F — the date-tracked base table holding the persisted rows, including the DFF attribute columns and audit columns. The view selects directly from this table (aliased DOT) without joins.
  • FND_SESSIONS — referenced twice in the WHERE clause via correlated subqueries on EFFECTIVE_DATE, keyed by USERENV('SESSIONID'), to establish the current session effective date for the date-effective filter.

Two predicates restrict the result set: EFFECTIVE_START_DATE must be less than or equal to the session effective date, and EFFECTIVE_END_DATE must be greater than or equal to it. The ROWID of the base table is exposed as ROW_ID, enabling the view to support updateable contexts where the caller needs to identify the underlying physical row.

Key Columns

  • ROW_ID — the ROWID of the base table row, used for identity and DML targeting.
  • DPNT_OTHR_PTIP_RT_ID — primary identifier for the dependent/other PTIP runtime record.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range enforced by the view's filter.
  • EXCLD_FLAG — indicates whether the record is excluded from the associated configuration.
  • ORDR_NUM — ordering sequence for the record.
  • PTIP_ID — foreign key to the plan-type-in-plan definition.
  • VRBL_RT_PRFL_ID — foreign key to the variable rate profile.
  • BUSINESS_GROUP_ID — the operating unit / business group context for multi-tenant row isolation.
  • DOT_ATTRIBUTE_CATEGORY and DOT_ATTRIBUTE1 … DOT_ATTRIBUTE30 — the descriptive flexfield context and segment values. DOT_ATTRIBUTE1 is the first segment and is commonly referenced in client SQL, reports, and interfaces for filtering or display.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER support concurrency control and audit reporting.

Common Use Cases and Queries

Typical scenarios include resolving DFF attribute values for a participant's PTIP record, validating variable rate profile assignments, and feeding downstream integrations that must respect the session effective date. A representative query selecting the attribute of interest:

  • SELECT d.DPNT_OTHR_PTIP_RT_ID, d.PTIP_ID, d.VRBL_RT_PRFL_ID, d.DOT_ATTRIBUTE_CATEGORY, d.DOT_ATTRIBUTE1, d.EFFECTIVE_START_DATE, d.EFFECTIVE_END_DATE FROM APPS.BEN_DPNT_OTHR_PTIP_RT d WHERE d.BUSINESS_GROUP_ID = :p_bg_id AND d.DOT_ATTRIBUTE1 = :p_value;
  • SELECT d.DPNT_OTHR_PTIP_RT_ID, d.DOT_ATTRIBUTE1, d.ORDR_NUM FROM APPS.BEN_DPNT_OTHR_PTIP_RT d WHERE d.PTIP_ID = :p_ptip_id AND d.EXCLD_FLAG = 'N' ORDER BY d.ORDR_NUM;

Because the view applies the FND_SESSIONS date-effective predicate automatically, callers should not add their own EFFECTIVE_START_DATE/EFFECTIVE_END_DATE range checks unless they intend to override the session context. When historical or future-dated rows are required, query the base table BEN_DPNT_OTHR_PTIP_RT_F directly instead.