Results for “ben_pcp_spclty”

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

Overview

APPS.BENBV_PRMRY_CARE_PRVDR_V is a valid Oracle Applications view owned by the APPS schema, with FND Design Data registration under BEN.BENBV_PRMRY_CARE_PRVDR_V. It is documented as an internal view type in Oracle E-Business Suite 12.1.1 and 12.2.2 and is not intended for direct customer access. Oracle explicitly notes that access to application data through this object is supported only from standard Oracle Applications programs.

The view exposes primary care provider (PCP) information captured against a participant's enrollment results and covered dependents within Oracle Advanced Benefits. It is a business view layered over the underlying PCP entity table and is used internally by Oracle Benefits processes that need to resolve, display, or report the primary care provider associated with a covered person, including the collaborator and care support processes referenced by the user's search context.

Underlying Base Objects

According to the documented view metadata, BENBV_PRMRY_CARE_PRVDR_V is defined over the following referenced base objects:

• BEN_PRMRY_CARE_PRVDR_F — referenced through a synonym. This is the primary care provider entity table and supplies the effective-dated PCP records, names, identifiers, and type codes exposed by the view.
• HR_BIS — referenced as a package. This business intelligence utility package is used within Oracle HRMS-based views to resolve lookup code meanings and other derived display values, such as the PCP specialty meaning column.

The view therefore acts as a consumer of the PCP entity table, applying the standard effective-dating and WHO-column semantics inherited from the base table, while enriching the output with lookup-derived descriptive values.

Key Columns

• PRMRY_CARE_PRVDR_ID — System-generated primary key identifying the primary care provider record.
• NAME — Primary care provider name, exposed as a VARCHAR2(240) attribute.
• EXT_IDENT — External identifier for the primary care provider, VARCHAR2(90).
• PRMRY_CARE_PRVDR_TYP_CD — Provider type lookup code, based on lookup type BEN_PCP_SPCLTY.
• PRMRY_CARE_PRVDR_TYP_CD_M — The lookup meaning corresponding to the provider type code, resolved through HR_BIS.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Effective-dating columns that define the date range during which the PCP record is valid.
• BUSINESS_GROUP_ID — Foreign key to HR_ORGANIZATION_UNITS, identifying the business group context.
• ELIG_CVRD_DPNT_ID — Foreign key to BEN_ELIG_CVRD_DPNT_F, linking the PCP to an eligible covered dependent.
• PRTT_ENRT_RSLT_ID — Foreign key to BEN_PRTT_ENRT_RSLT_F, linking the PCP to a participant enrollment result.
• PROGRAM_UPDATE_DATE and the concurrent program WHO columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID) — Audit attributes identifying the concurrent program that last updated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY — Standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios involve retrieving the primary care provider associated with a participant's enrollment result or covered dependent, and reporting on provider type and specialty for care coordination and collaborator care support processes.

A representative query joining the view to enrollment results is shown below:

• SELECT p.PRMRY_CARE_PRVDR_ID, p.NAME, p.EXT_IDENT, p.PRMRY_CARE_PRVDR_TYP_CD_M, p.EFFECTIVE_START_DATE, p.EFFECTIVE_END_DATE FROM APPS.BENBV_PRMRY_CARE_PRVDR_V p WHERE p.PRTT_ENRT_RSLT_ID = :p_enrt_rslt_id AND SYSDATE BETWEEN p.EFFECTIVE_START_DATE AND p.EFFECTIVE_END_DATE;

A second common pattern resolves the provider for a covered dependent:

• SELECT p.ELIG_CVRD_DPNT_ID, p.NAME, p.PRMRY_CARE_PRVDR_TYP_CD, p.PRMRY_CARE_PRVDR_TYP_CD_M FROM APPS.BENBV_PRMRY_CARE_PRVDR_V p WHERE p.ELIG_CVRD_DPNT_ID = :p_dpnt_id AND p.BUSINESS_GROUP_ID = :p_bg_id;

Because the view is documented as Oracle Internal Use Only, custom queries should be treated as diagnostic or read-only reporting exercises; supported processing should be performed through standard Oracle Benefits programs and APIs rather than by writing to or depending upon this object.