Search Results ben_prmry_care_prvdr_f




Overview
Explore in AI Chat

Overview

BEN_PRMRY_CARE_PRVDR_F is a date-tracked (datetrack) table in the BEN schema of Oracle E-Business Suite Advanced Benefits. It stores primary care provider details associated with benefit enrollees, covered dependents, and their participation enrollment results. In the context of Oracle EBS 12.1.1 and 12.2.2, this table supports the capture and maintenance of physician or provider information that plan participants designate for managed care, referral, or claims-processing purposes. The "F" suffix denotes a date-effective (flattened) table governed by Oracle's datetrack framework, in which every logical record is represented by two or more physical rows segmented by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. As a modeling suggestion, this indicates that the table is not treated as a classic hub, link, or satellite within a normalized Data Vault design; it behaves as an independent, date-effective entity rather than participating in a documented referential chain. This classification reflects the absence of declared FK relationships in the mined metadata rather than a design intent to isolate the data.

Key Information Stored

The table contains 50 documented columns. Its surrogate primary key is defined by the unique index BEN_PRMRY_CARE_PRVDR_F_PK over the composite of PRMRY_CARE_PRVDR_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. The column PRMRY_CARE_PRVDR_ID serves as the business-key candidate for the logical primary-care-provider entity, while the two date columns provide the datetrack validity window. This combination means that the same PRMRY_CARE_PRVDR_ID may appear in multiple rows, each representing a distinct effective-dated version of the record.

The most significant columns include:

Common Use Cases and Queries

Typical usage centers on retrieving the currently effective provider for a participant or dependent, producing enrollment audit trails, and extracting provider data for carrier feeds. A current-record query filters on SYSDATE within the datetrack window:

  • SELECT PRMRY_CARE_PRVDR_ID, NAME, PRMRY_CARE_PRVDR_TYP_CD FROM BEN_PRMRY_CARE_PRVDR_F WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;
  • An as-of-date variant replaces SYSDATE with a bind variable to reconstruct historical provider assignments for audit or claims re-adjudication.
  • Joining on ELIG_CVRD_DPNT_ID or PRTT_ENRT_RSLT_ID supports dependent-level and enrollment-level reporting.
  • Filtering by BUSINESS_GROUP_ID enforces row-level security in multi-organization deployments.
  • Reporting on PPR_ATTRIBUTE columns enables analysis of client-specific provider attributes such as network tier or referral status.

Related Objects

The mined relationship data classifies this table as standalone, so no parent foreign-key constraints are documented. Logical associations are inferred from the reference columns embedded in the table:

  • BEN_PRMRY_CARE_PRVDR_F_PK — the unique index enforcing the composite primary key.
  • BEN_ELIG_CVRD_DPNT_F — joined via ELIG_CVRD_DPNT_ID to associate providers with eligible covered dependents.
  • BEN_PRTT_ENRT_RSLT_F — joined via PRTT_ENRT_RSLT_ID to tie providers to participation enrollment results.
  • BEN_PTIP_F — participation and eligibility records that typically drive provider assignment.
  • PER_BUSINESS_GROUPS — resolved through BUSINESS_GROUP_ID for organization context.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — validate the PPR_ATTRIBUTE_CATEGORY and descriptor flexfield values where configured.
  • FND_CONCURRENT_REQUESTS — related through REQUEST_ID and PROGRAM_ID for audit lineage of concurrent processes that created or updated rows.