Search Results ext_slsteam_migrtn

Overview

The APPS.PV_SLSTEAM_MIGRTN_PVT package is a private (PVT-classified) PL/SQL package belonging to the Oracle Partner Management (PV) module of Oracle E-Business Suite. Its name reflects its purpose: the migration of sales team data (SLSTEAM), where the term "team" refers to the partner sales team members assigned to leads, opportunities, and partner profiles. The package header carries the source control revision identifier pvslmigs.pls 120.1, dated 2005, indicating that the object originated in the early phases of the Oracle Partner Management product line and has remained stable across the 12.1.1 and 12.2.2 releases.

The package exists primarily to support one-time or periodic data migration and conversion activities, moving legacy lead assignment, partner access, and sales team relationship data into the current Oracle Partner Management and Oracle CRM foundation tables. Note that despite the search term "steam art work," this object is unrelated to graphical artifacts; the "SLSTEAM" token is an abbreviation for sales team, and "ART" relates to the lead/assignment semantics, not imagery.

Key Procedures and Functions

The package exposes a single documented procedure, EXT_SLSTEAM_MIGRTN. As the public entry point of this private package, this procedure drives the sales team migration process. Its signature declares three parameters: an error buffer (ERRBUF), a return code (RETCODE), and a mode indicator (P_MODE). This parameter pattern is characteristic of concurrent-program-enabled PL/SQL entry points, where ERRBUF and RETCODE conform to the standard Oracle Application Object Library concurrent program interface, and P_MODE allows the caller to select a migration behavior such as a validation or commit mode. The procedure logs its activity to a file, as indicated by the package-level constant G_LOG_TO_FILE defaulted to 'Y'.

Internally, the package defines two PL/SQL collection types, migration_REC_TYPE and migration_tbl_TYPE, used to stage migration rows in memory before they are processed. The record structure carries an entity name, an entity identifier, a party name, and a resource identifier — a combination that mirrors the columns expected by the lead assignment and resource extension tables. No other procedures or functions are documented in the package specification.

Tables Accessed

The package reads from and writes to several Oracle CRM and Partner Management tables through APPS synonyms. Party and relationship data is sourced from HZ_PARTIES and HZ_RELATIONSHIPS, while resource information is drawn from JTF_RS_RESOURCE_EXTNS. Lead data is read from AS_LEADS_ALL and AS_SALES_LEADS, with access records in AS_ACCESSES_S. Partner-specific data comes from PV_PARTNER_PROFILES, and assignment results are written to PV_LEAD_ASSIGNMENTS and PV_LEAD_WORKFLOWS. Migration audit and status records are maintained in PV_ACCESS_MIGRATION_LOG and PV_ACCESS_MIGRATION_LOG_S. Lookup validation uses FND_LOOKUP_VALUES, and the temporary PL/SQL table PLITBLM is referenced, typically as a parameter to the FND message/logging utilities.

Usage Notes

Because this is a private package, it is not intended for direct invocation by end users or customer extensions. It is normally called by a concurrent program or a wrapper package registered in Oracle Applications, with the standard ERRBUF/RETCODE convention allowing migration results and error messages to be surfaced to the concurrent manager log. The procedure is best executed during implementation or upgrade windows when historical sales team assignment data must be loaded or reconciled against the current schema. The presence of the migration log tables implies that each run is audited, and administrators should review PV_ACCESS_MIGRATION_LOG after execution to confirm successful rows and investigate failures.

As the package is referenced by zero other packages, it is largely self-contained and typically invoked only from a dedicated migration concurrent program or ad hoc SQL*Plus script. Given its link to G_LOG_TO_FILE, developers diagnosing issues should enable file logging before execution to capture diagnostic output.