Search Results pv_benft_status_maps




Overview
Explore in AI Chat

Overview

PV_BENFT_STATUS_MAPS is a reference and mapping table owned by the PV schema within the Oracle E-Business Suite Partner Management module. Its documented description is "Benefit status map," which indicates that the table maintains the correspondence between a benefit type and the status values used by vendors and partners within the partner benefits lifecycle. In practical terms, it allows the Partner Management application to translate or align an internal benefit status with the equivalent vendor-side and partner-side status codes, enforcing consistent interpretation of benefit state across the two populations.

The table is registered as VALID in the ETRM repository for release 12.2.2 and is documented with twelve physical columns. Heuristic Data Vault classification mined from the foreign key structure labels this object as standalone. In Data Vault modeling terms, this suggests treating PV_BENFT_STATUS_MAPS as neither a classic hub nor a link with multiple parent hubs, but rather as an independent reference or mapping entity. A satellite treatment around its own business key would be a reasonable modeling suggestion, since its descriptive attributes (benefit type and the two status codes) are non-key context that can change over time.

Key Information Stored

The table is anchored by the surrogate primary key BENFT_STATUS_MAP_ID, enforced by the constraint PV_BENFT_STATUS_MAPS_PK. A second unique index, PV_BENFT_STATUS_MAPS_U1, is defined over BENFT_STATUS_MAP_ID together with ZD_EDITION_NAME; this composite is the documented business-key candidate and reflects the editioning mechanism used in 12.2.x online patching, where multiple editions of a row can coexist.

The most significant business columns are:

Standard EBS WHO columns are also present: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, the latter supporting optimistic locking in the OAF framework.

Common Use Cases and Queries

Typical usage resolves status translation during benefit processing or reporting. A join between benefit transactions and this map aligns vendor and partner statuses for reconciliation:

  • Look up the partner status for a given vendor status and benefit type.
  • Validate that a vendor-supplied status is a recognized mapping before accepting a benefits feed.
  • Report benefit volumes grouped by benefit type and partner status.
  • Reconcile discrepancies where vendor and partner statuses diverge.

A representative query form is: SELECT BENEFIT_TYPE, VENDOR_STATUS_CODE, PARTNER_STATUS_CODE FROM PV_BENFT_STATUS_MAPS WHERE SECURITY_GROUP_ID = :sgid. Reporting extract joins to FND_SECURITY_GROUPS on SECURITY_GROUP_ID, and edition-aware queries should filter ZD_EDITION_NAME to the active edition.

Related Objects

The documented foreign key establishes a single explicit dependency:

  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for data security and multi-tenant filtering.

Beyond that, related objects can be inferred from the Partner Management benefit model. Benefit definition tables that supply BENEFIT_TYPE values, partner and vendor entity tables whose status domains provide VENDOR_STATUS_CODE and PARTNER_STATUS_CODE, and the PV benefits transaction tables that reference this map during status resolution are the most significant functional dependencies. The PV_BENFT_STATUS_MAPS_PK and PV_BENFT_STATUS_MAPS_U1 indexes are the primary access paths for lookups by mapping identifier and by edition-scoped business key.