Results for “ben_cmbn_ptip_opt_d”

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

Overview

The view BEN_CMBN_PTIP_OPT_D is a denormalized, presentation-oriented object owned by the APPS schema within the Oracle E-Business Suite Advanced Benefits module (product code BEN). Its status is documented as VALID and it is identified in the ETRM as a "Retrofitted" object, indicating it was re-engineered to conform to the OAF (Oracle Application Framework) and multi-org data model conventions introduced across EBS 12.1.1 and 12.2.2. The view exposes combination plan-type-in-plan option configuration records together with resolving descriptive names for the user who last modified the row, the parent program, and the associated plan option. In this sense the view functions as a read-only reporting and integration surface rather than a transactional table: it consolidates rows from the primary combination entity BEN_CMBN_PTIP_OPT_F with foreign-key lookups, sparing downstream reports, extracts, and interfaces from performing the joins themselves.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms: BEN_CMBN_PTIP_OPT_F, BEN_OPT_F, BEN_PGM_F, and FND_USER. The driving table is BEN_CMBN_PTIP_OPT_F, which stores the effective-dated combination of plan type, program, and plan option. The definition uses Oracle outer-join syntax (the legacy (+) operator) so that a combination row is still returned even when its related user, program, or option record is absent or not yet effective. FND_USER resolves the LAST_UPDATED_BY identifier to a user name, while BEN_PGM_F and BEN_OPT_F supply the program and option descriptive names respectively. Because all three lookups are outer-joined, the view preserves the full population of the combination table and does not silently drop orphaned or incomplete configuration rows.

Key Columns

• ROW_ID — the ROWID of the underlying BEN_CMBN_PTIP_OPT_F row, providing a unique physical identifier.
• CMBN_PTIP_OPT_ID — the primary key of the combination plan-type/option record.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the date-effective range governing when the combination is active.
• NAME — the descriptive name of the combination record.
• LAST_UPDATE_DATE and LAST_UPDATED_BY — audit columns recording when and by whom the row was last changed; LAST_UPDATED_BY is resolved to a user via FND_USER.
• PGM_NAME — the resolved name of the associated program (from BEN_PGM_F).
• OPT_NAME — the resolved name of the associated plan option (from BEN_OPT_F).

Note that the view text aliases three source columns as NAME, but only the combination name, program name, and option name are distinguishable by their projected aliases NAME, PGM_NAME, and OPT_NAME. Consumers should reference these aliases explicitly to avoid ambiguity.

Common Use Cases and Queries

Typical uses include Benefits configuration audits, data extracts for interfaces, and ad-hoc reporting on which plan option combinations exist and who maintains them. A standard query filtering to currently effective combinations would resemble the following:

• SELECT cmbn_ptip_opt_id, name, pgm_name, opt_name, last_update_date FROM apps.ben_cmbn_ptip_opt_d WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• SELECT cmbn_ptip_opt_id, name, pgm_name, opt_name FROM apps.ben_cmbn_ptip_opt_d WHERE pgm_name = :p_program_name;
• SELECT cmbn_ptip_opt_id, name, last_updated_by FROM apps.ben_cmbn_ptip_opt_d ORDER BY last_update_date DESC;

Because the view is read-only and resolves its joins through outer joins, it is well suited to reconciliation and data-migration validation, where completeness of the combination set must be verified. It should not be used for DML; changes must be applied to BEN_CMBN_PTIP_OPT_F through the supported Benefits application APIs. Regarding the user's original search concerning whether a given CPT code is valid, that determination is governed by external coding standards and Benefits eligibility setup, not by this view, which records plan configuration rather than clinical procedure validity.