Search Results pv_tap_batch_chg_partners




Overview
Explore in AI Chat

Overview

PV_TAP_BATCH_CHG_PARTNERS is a table in the PV (Partner Management) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It holds updated partner information produced during batch partner-change processing. In practice, the table functions as a staging and persistence area for rows that represent partner records intended to be applied or reconciled against the master partner data. It carries the standard EBS concurrency and audit columns (WHO columns) plus batch-context columns that tie each row back to the concurrent request and program that created or modified it.

From a Data Vault modeling perspective, the schema relationship metadata classifies this object heuristically as standalone. This should be read as a modeling suggestion rather than a documented design decision: the table is not an obvious hub-and-link participant, but it does carry a business-key candidate (PARTNER_ID via a unique index) and a foreign key to FND_SECURITY_GROUPS, so it can be treated as a satellite of the partner business key within the appropriate security group context.

Key Information Stored

The table is documented with a primary key constraint, PV_TAP_BATCH_CHG_PARTNERS_PK, defined on PARTNER_ID. A separate unique index, PV_TAP_BATCH_CHG_PARTNERS_U1, also exists on PARTNER_ID, confirming that this column is both the surrogate primary key and the business-key candidate for the row.

Common Use Cases and Queries

Typical usage centers on troubleshooting and auditing batch partner-change runs. Common patterns include identifying unprocessed rows for a given request, tracing a partner record back to the program that created it, and confirming security-group scoping.

  • Find unprocessed batch rows for a request:
    • SELECT partner_id, vad_partner_id, security_group_id FROM pv_tap_batch_chg_partners WHERE processed_flag = 'N' AND request_id = :request_id;
  • Reconcile staging rows to master partner data via PARTNER_ID.
  • Audit which concurrent program produced or last updated a row using PROGRAM_ID and PROGRAM_APPLICATION_ID.
  • Report on security-group distribution by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; the only documented foreign key relationship.
  • FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to resolve concurrent request details.
  • FND_CONCURRENT_PROGRAMS — joined via PROGRAM_ID and PROGRAM_APPLICATION_ID to identify the driving program.
  • FND_APPLICATION — resolves the application behind PROGRAM_APPLICATION_ID.
  • FND_USER — resolves CREATED_BY and LAST_UPDATE_BY.
  • PV_TAP_BATCH_CHG_PARTNERS_PK / PV_TAP_BATCH_CHG_PARTNERS_U1 — the primary key constraint and unique index enforcing the PARTNER_ID key.