Search Results as_accesses_s




Overview
Explore in AI Chat

Overview

PV_SLSTEAM_MIGRTN_PVT is a private (PVT classification) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, documented against the 12.2.2 reference set. Its name identifies it as the private implementation component for migrating sales-team and lead-assignment data within the Partner/Channel Management (PV) product family. The package reconciles legacy sales-lead and sales-team access records into the current partner-profiling and lead-workflow model. As a private package, it is intended for internal invocation by the public Partner APIs and concurrent programs rather than for direct customer use. The status is VALID and the package is not referenced by any other database object, confirming that it sits at the top of its call hierarchy and executes on behalf of callers rather than exposing a reusable interface of its own.

Key Procedures and Functions

The documented interface exposes a single program unit, EXT_SLSTEAM_MIGRTN. Based on its name and dependencies, this routine extracts sales-team and access records from the legacy tables, resolves each record to the corresponding party and resource identities, and inserts or updates the target partner-profile and lead-assignment structures. It performs message handling and writes progress and error details to the migration log through the FND_MESSAGE and PV_ACCESS_MIGRATION_LOG mechanisms. Parameter signatures are not published in the available metadata and should be derived from the package specification or the calling concurrent program before any direct use.

Tables Accessed

  • AS_ACCESSES_S / AS_ACCESSES_ALL — the legacy sales-access and territory assignment records that constitute the migration source; the _S synonym provides the sequence for new primary keys.
  • AS_LEADS_ALL / AS_SALES_LEADS — legacy lead headers and sales-lead detail rows used to identify owned leads and their original assignees.
  • HZ_PARTIES / HZ_RELATIONSHIPS — party master and relationship resolution for both the owning organization and the assigned sales resource.
  • JTF_RS_RESOURCE_EXTNS — resource extension data validating that the assigned salesperson is an active resource.
  • PV_PARTNER_PROFILES — the current partner profile records targeted by the migration.
  • PV_LEAD_ASSIGNMENTS / PV_LEAD_WORKFLOWS — destination tables for migrated lead ownership and the workflow rows that drive assignment routing.
  • PV_ACCESS_MIGRATION_LOG / PV_ACCESS_MIGRATION_LOG_S — logging tables recording each migrated or rejected row, with the sequence supplying log identifiers.
  • FND_LOOKUP_VALUES / FND_MESSAGE / FND_FILE / FND_GLOBAL — lookup validation, translatable messages, concurrent-program log output, and session context.
  • PLITBLM — the standard PL/SQL table-type package used for in-memory collections.

Usage Notes

The package is normally invoked indirectly. Customers upgrading or consolidating sales-team data run the associated Partner Management concurrent program, which calls EXT_SLSTEAM_MIGRTN in batch mode and returns output through the FND_FILE log. It may also be called from the Partner Management forms during access maintenance, or from custom migration scripts written for one-time data conversion. Because PV_SLSTEAM_MIGRTN_PVT is a private package, it carries no compatibility guarantee: callers should wrap invocations in their own exception handling, commit only after the migration log is reviewed, and confirm that the package remains VALID after any patch or upgrade. Review the migration log tables before committing, as rejected rows are recorded there rather than raising errors to the caller.