Search Results dot_attribute30

Overview

BEN_DPNT_OTHR_PTIP_RT_X is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BEN (Advanced Benefits) product family. The view presents a date-effective, security-filtered projection of dependent other participant plan-type rate records stored in the Advanced Benefits module. Its name decomposes as BEN (Advanced Benefits), DPNT (dependent), OTHR (other/alternate), PTIP (participant plan type), and RT (rate), with the "_X" suffix indicating that the view is translated or joined against a session context object rather than being a simple one-to-one mapping of a single table.

The object is recorded in the ETRM metadata as VALID with a status of VIEW and is documented for both Oracle EBS 12.1.1 and 12.2.2. Its principal function is to expose the effective-dated rows of the underlying BEN_DPNT_OTHR_PTIP_RT_F table that are current as of the system date, while also exposing the full set of 30 descriptive flexfield (DFF) attribute columns that the base table carries. Because the "_X" views in Advanced Benefits are commonly consumed by forms, concurrent programs, and OAF-based pages, BEN_DPNT_OTHR_PTIP_RT_X serves as the runtime access path for dependent participant rate configuration data.

Underlying Base Objects

The ETRM documentation identifies exactly two referenced base objects, both accessed through APPS synonyms:

• BEN_DPNT_OTHR_PTIP_RT_F — the base table holding dependent other participant plan-type rate rows, aliased as DOT in the view definition.
• FND_SESSIONS — the Oracle Application Object Library sessions table, aliased as SE, used to establish the session context for the view.

The view text joins DOT to FND_SESSIONS and applies the predicate TRUNC(SYSDATE) BETWEEN DOT.EFFECTIVE_START_DATE AND DOT.EFFECTIVE_END_DATE. This restricts output to records whose effective date range encloses the current date, so the view always returns the currently effective configuration. The ROWID of the underlying table row is exposed as ROW_ID, which allows downstream tooling to identify and update the physical source row.

Key Columns

The view exposes the primary key and control columns of the base table, together with the standard descriptive flexfield segment.

• ROW_ID — the ROWID of the underlying BEN_DPNT_OTHR_PTIP_RT_F row.
• DPNT_OTHR_PTIP_RT_ID — the surrogate primary key of the dependent other participant plan-type rate record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range that governs visibility of the row.
• EXCLD_FLAG — indicates whether the record is excluded from processing.
• ORDR_NUM — the ordering sequence applied to the record.
• PTIP_ID — foreign key to the participant plan type definition.
• VRBL_RT_PRFL_ID — foreign key to the variable rate profile used to calculate the rate.
• BUSINESS_GROUP_ID — the business group that owns the row.
• DOT_ATTRIBUTE_CATEGORY and DOT_ATTRIBUTE1 through DOT_ATTRIBUTE30 — the descriptive flexfield context and its thirty attribute segments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — the standard WHO and optimistic locking columns.

The DOT_ATTRIBUTE30 column specifically is the thirtieth descriptive flexfield segment, and it is the column most frequently referenced when users search for "dot_attribute30". It is a generic VARCHAR2 segment whose meaning is determined by the value in DOT_ATTRIBUTE_CATEGORY, which points to a flexfield context defined in the Descriptive Flexfields setup.

Common Use Cases and Queries

Report developers and integration architects query this view to retrieve currently effective dependent participant rate records together with their flexfield attributes. Typical uses include extracting configuration for interfaces, validating effective-dated rate setup, and reporting on flexfield usage.

A straightforward query selecting the key columns and the thirtieth DFF segment:

• SELECT ROW_ID, DPNT_OTHR_PTIP_RT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, PTIP_ID, VRBL_RT_PRFL_ID, DOT_ATTRIBUTE_CATEGORY, DOT_ATTRIBUTE30 FROM BEN_DPNT_OTHR_PTIP_RT_X;

To isolate rows whose thirtieth attribute is populated:

• SELECT DPNT_OTHR_PTIP_RT_ID, DOT_ATTRIBUTE_CATEGORY, DOT_ATTRIBUTE30 FROM BEN_DPNT_OTHR_PTIP_RT_X WHERE DOT_ATTRIBUTE30 IS NOT NULL ORDER BY DPNT_OTHR_PTIP_RT_ID;

Because the view filters on SYSDATE, developers needing historic or future-dated rows must query the base table BEN_DPNT_OTHR_PTIP_RT_F directly rather than the view. The view should therefore be treated as a current-effective read path rather than a historical reporting source.