Search Results chk_prtnr_qflr_enabled
Overview
APPS.PV_TERR_ASSIGN_PUB is a public PL/SQL API package in Oracle EBS Channel Revenue Management / Partner Relationship Management (PRM). Its stated purpose, per the package header, is to serve as "a public API for manipulating Channel Team related info into PRM." It provides the programmatic interface for creating, updating, and assigning territory-based channel teams, and for resolving partner and resource information associated with those teams. The package encapsulates specification for PL/SQL records and tables together with the public access and channel team manipulation APIs.
The package is classified as PUB (public), meaning it is intended for external invocation and is referenced by five other packages. It carries the version identifier $Header: pvxpptab.pls 120.6 2006/05/04 and has a revision history spanning creation in July 2003, API restructuring in July 2005, and SQL Repository violation fixes in December 2005. It is available in both 12.1.1 and 12.2.2, with the same eleven documented program units in each.
Key Procedures and Functions
The package exposes eleven documented program units. Several are helper or main-wrapper pairs used internally by the public entry points.
- CHK_PRTNR_QFLR_ENABLED — this is the function the user searched for. It determines whether a supplied partner qualifier is enabled in Qualifier Setup. It returns a VARCHAR2 flag and accepts a single partner qualifier identifier as input. It queries JTF_QUAL_USGS_ALL for the seeded qualifier, filtering on organization, seeded qualifier ID, and a fixed qualifier type usage ID, and returns the enabled flag defaulting to 'N'.
- GET_RES_FROM_TEAM_GROUP — retrieves the resources belonging to a given team group, supporting downstream team membership resolution.
- GET_PARTNER_DETAILS — returns party-related information for a partner, drawing on the HZ party model.
- CREATE_CHANNEL_TEAM — the public entry point for creating a channel team.
- DO_CREATE_CHANNEL_TEAM — the internal worker that performs the actual creation logic invoked by CREATE_CHANNEL_TEAM.
- CREATE_ONLINE_CHANNEL_TEAM — public entry point for creating an online channel team.
- DO_CR_ONLINE_CHNL_TEAM — internal worker supporting the online channel team creation.
- CREATE_VAD_CHANNEL_TEAM — public entry point for creating a Value Added Distributor channel team.
- UPDATE_CHANNEL_TEAM — updates an existing channel team.
- ASSIGN_CHANNEL_TEAM — assigns a channel team to the appropriate territory or partner context.
- PROCESS_SUB_TERRITORIES — handles processing of subordinate territories associated with a team assignment.
A private logging helper, WRITE_LOG, wraps FND_FILE output and is used throughout for diagnostic messages.
Tables Accessed
The package reads and writes across three functional table families, all accessed through APPS synonyms.
- Oracle Trading Community (HZ) tables — HZ_PARTIES, HZ_PARTY_SITES, HZ_ORGANIZATION_PROFILES, and HZ_RELATIONSHIPS supply partner identity, site, and relationship data used by GET_PARTNER_DETAILS and team creation.
- Resource Manager (JTF_RS) tables — JTF_RS_TEAMS_B, JTF_RS_TEAM_MEMBERS, JTF_RS_TEAM_USAGES, JTF_RS_GROUPS_B, JTF_RS_GROUP_MEMBERS, JTF_RS_GROUP_USAGES, JTF_RS_RESOURCE_EXTNS, JTF_RS_ROLES_B, and JTF_RS_ROLE_RELATIONS hold the team definitions, memberships, group mappings, and resource details that these APIs create and maintain.
- Qualifier and attribute tables — JTF_QUAL_USGS_ALL supports the qualifier-enabled check, while PV_ENTY_ATTR_VALUES stores entity attribute values used during team processing.
Usage Notes
Because the package is classified PUB and its header explicitly states it is "for public use," it is the supported integration point for channel team manipulation. It is typically invoked from PRM-related Oracle Forms, from concurrent programs that build or refresh channel teams, and from custom PL/SQL that needs to create or assign teams without writing directly to the underlying JTF_RS and HZ tables. The presence of internal DO_* workers indicates the public procedures wrap validation and logging around the core DML, so callers should invoke the public entry points rather than the workers. Since five other packages reference it, modifications carry cross-package impact. The fixed literal filters embedded in CHK_PRTNR_QFLR_ENABLED — including a hard-coded organization ID and qualifier type usage ID — reflect its internal, environment-specific origin and should be validated against the target instance before use. Implementers should also review the 12.1.1 to 12.2.2 upgrade path, as the JTF_RS and HZ table structures evolved between releases.