Results for “pv_access_migration_log”

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

Overview

PV_ACCESS_MIGRATION_LOG is a table owned by the PV (Partner Management) schema in Oracle E-Business Suite. Its documented purpose is to store the external sales team migration rows generated when partner-facing sales team assignments are moved into, or reconciled against, the EBS access-control model. In releases 12.1.1 and 12.2.2 the object remains a valid, proprietary table in the PV product family, and it is not exposed as a public interface; it functions as an internal staging and audit store behind the sales team migration process.

The table sits logically between the access-control tables (AS_ACCESSES_ALL_ALL, AS_SALESFORCE, AS_LEADS_ALL, AS_SALES_LEADS) and the partner records in PV. Each row captures a single migration event for an access record, recording the action taken, the partner context, and a set of disposition flags. Because its documented foreign keys point outward to master and reference entities while carrying descriptive attributes and flags of its own, the mined Data Vault classification is satellite-leaning. In modeling terms, this suggests treating PV_ACCESS_MIGRATION_LOG as a satellite attached to an access hub (ACCESS_ID) and to salesforce and lead hubs, rather than as a hub or a pure link table. This is a heuristic classification, not a documented constraint, and should be validated against actual usage.

Key Information Stored

The documented physical schema contains 24 columns. The most significant are:

• ACCESS_MIGRATION_LOG_ID — the surrogate primary key for each migration log entry.
• ACCESS_ID — the foreign key to AS_ACCESSES_ALL_ALL, identifying the access record affected by the migration and serving as the primary business-key candidate alongside the log identifier.
• ACTION — the migration operation applied to the access row.
• ACCESS_TYPE — classifies the type of access being migrated.
• CREATION_DATE, CREATED_BY_TAP_FLAG — when the log row was produced and whether it originated from the TAP (Territory Assignment/partner application) path.
• SALESFORCE_ID, SALES_GROUP_ID — the salesforce and sales group context for the migrated team.
• LEAD_ID, SALES_LEAD_ID — pointers to the lead and sales lead records associated with the migration.
• CUSTOMER_ID, ADDRESS_ID, PARTNER_CUSTOMER_ID, PARTNER_ADDRESS_ID, PARTNER_CONT_PARTY_ID — the customer, address, and partner party/contact identifiers that define which business entities the migrated team covers.
• ORG_ID — the operating unit, enabling multi-org filtering.
• Disposition flags: FREEZE_FLAG, REASSIGN_FLAG, TEAM_LEADER_FLAG, OWNER_FLAG, INTERNAL_UPDATE_ACCESS, PRM_KEEP_FLAG, OPEN_FLAG — control attributes indicating whether the row was frozen, reassigned, designated to a team leader or owner, updated internally, retained in PRM, or left open.

Common Use Cases and Queries

Typical uses include auditing which access records were migrated for a given operating unit, diagnosing why a partner sales team assignment was frozen or reassigned, and reconciling migrated rows against the live access and salesforce tables. Example patterns:

• Migration volume by operating unit and action: SELECT ORG_ID, ACTION, COUNT(*) FROM PV.PV_ACCESS_MIGRATION_LOG GROUP BY ORG_ID, ACTION;
• Rows still pending disposition: SELECT ACCESS_ID, ACTION, CREATION_DATE FROM PV.PV_ACCESS_MIGRATION_LOG WHERE OPEN_FLAG = 'Y';
• Trace the access record behind a log entry: SELECT l.ACCESS_MIGRATION_LOG_ID, a.* FROM PV.PV_ACCESS_MIGRATION_LOG l JOIN AS_ACCESSES_ALL_ALL a ON a.ACCESS_ID = l.ACCESS_ID;
• Reconcile to salesforce and lead: join on SALESFORCE_ID = AS_SALESFORCE.SALESFORCE_ID and LEAD_ID = AS_LEADS_ALL.LEAD_ID.

Reports commonly filter by ORG_ID and CREATION_DATE to bound a migration window.

Related Objects

• AS_ACCESSES_ALL_ALL — joined via PV_ACCESS_MIGRATION_LOG.ACCESS_ID; the core access record.
• AS_SALESFORCE — joined via SALESFORCE_ID; the sales team definition.
• AS_LEADS_ALL — joined via LEAD_ID; the lead being covered.
• AS_SALES_LEADS — joined via SALES_LEAD_ID; the sales lead assignment.
• PV partner tables keyed by PARTNER_CUSTOMER_ID / PARTNER_CONT_PARTY_ID, which consume the migrated team data.