Search Results create_vad_channel_team

Overview

APPS.PV_TERR_ASSIGN_PUB_W is a public PL/SQL wrapper package in the Oracle E-Business Suite Partner and Territory Management (also referred to as Channel Revenue Management / Partner Management) module. It is declared AUTHID CURRENT_USER, meaning execution privileges and name resolution are evaluated against the invoker's schema rather than the package owner, allowing the package to be called from multiple EBS contexts while still referencing APPS-owned objects. Its principal business purpose is to expose and support the territory-assignment operations used when channel (partner) teams and territory-based assignments are created for partners, resources, and online channel records. In Oracle EBS 12.1.1 and 12.2.2 the package is documented with an API classification of OTHER, indicating it is not part of the formally supported public API set but is nonetheless callable and referenced by other application code.

Key Procedures and Functions

The package exposes 22 documented procedures and functions, most of which are internal "Rosetta" conversion helpers used to translate between JTF scalar array types and the nested PL/SQL collection types declared in PV_TERR_ASSIGN_PUB.

• ROSETTA_TABLE_COPY_IN_P15 / ROSETTA_TABLE_COPY_OUT_P15 — Converts JTF_VARCHAR2_TABLE_400, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, and JTF_VARCHAR2_TABLE_500 arrays to and from the partner_qualifiers_tbl_type collection (15-column profile, designated p15).
• ROSETTA_TABLE_COPY_IN_P19 / ROSETTA_TABLE_COPY_OUT_P19 — Corresponding IN/OUT copy routines for the prtnr_qflr_flg_tbl_type collection, using JTF_VARCHAR2_TABLE_100 arrays across its 14 columns (p19).
• ROSETTA_TABLE_COPY_IN_P22 / ROSETTA_TABLE_COPY_OUT_P22 — IN/OUT copy routines for the p22 collection profile.
• ROSETTA_TABLE_COPY_IN_P23 / ROSETTA_TABLE_COPY_OUT_P23 — IN/OUT copy routines for the p23 collection profile.
• ROSETTA_TABLE_COPY_IN_P24 / ROSETTA_TABLE_COPY_OUT_P24 — IN/OUT copy routines for the p24 collection profile.
• ROSETTA_TABLE_COPY_IN_P25 / ROSETTA_TABLE_COPY_OUT_P25 — IN/OUT copy routines for the p25 collection profile.
• ROSETTA_TABLE_COPY_IN_P30 / ROSETTA_TABLE_COPY_OUT_P30 — IN/OUT copy routines for the p30 collection profile.
• GET_RES_FROM_TEAM_GROUP — Retrieves the resource (resource ID/resource record) membership associated with a given team or team group, used to resolve which resources belong to a territory team before assignment processing.
• GET_PARTNER_DETAILS — Returns partner detail attributes for a partner, supporting qualification and team-building logic.
• CREATE_CHANNEL_TEAM — Public entry point for creating a channel team for a partner, orchestrating qualification and territory assignment.
• DO_CREATE_CHANNEL_TEAM — Worker procedure that performs the actual channel team creation invoked by CREATE_CHANNEL_TEAM.
• CREATE_ONLINE_CHANNEL_TEAM — Public entry point that creates an online channel team.
• DO_CR_ONLINE_CHNL_TEAM — Worker procedure implementing the online channel team creation logic.

Tables Accessed

The documented metadata lists a single referenced table, PLITBLM, accessed through an APPS synonym. PLITBLM is a standard EBS multi-org / organization security structure used for organization-level (operating unit) filtering. Its presence in this package indicates that channel-team and territory-assignment creation respects the caller's organization security context, ensuring that partner and resource data visible to the calling session remains constrained by the organization hierarchy. No other base tables are documented as directly referenced, which is consistent with the package's wrapper role: the Rosetta routines operate purely on PL/SQL collection types, while GET_RES_FROM_TEAM_GROUP, GET_PARTNER_DETAILS, and the creation procedures delegate base-table traffic to the underlying PV_TERR_ASSIGN_PUB package.

Usage Notes

PV_TERR_ASSIGN_PUB_W is a wrapper layer around PV_TERR_ASSIGN_PUB and is referenced by at least one other package in the ETRM schema. It is typically invoked indirectly rather than called directly by end users.

• Forms and UI. The channel-team creation routines are called by EBS partner/channel management forms when a user creates or modifies a channel team, propagating the form's JTF array parameters into the strongly typed PL/SQL collections through the Rosetta copy-in routines.
• Concurrent and batch processing. Territory and channel-team mass assignments can be driven from concurrent programs that populate JTF arrays and invoke CREATE_CHANNEL_TEAM or CREATE_ONLINE_CHANNEL_TEAM.
• Custom code. Because the package is AUTHID CURRENT_USER and is referenced by another package, customizations may call the public creation procedures or the GET_* functions directly. Given the API classification of OTHER, these routines are not guaranteed interfaces, and custom code should avoid depending on the Rosetta copy routines, whose signatures are tied to specific collection profiles (p15, p19, p22–p25, p30).
• Version note. The package header carries a 2005 revision tag, so the same wrapper behavior applies to both 12.1.1 and 12.2.2; concurrent program and form invocations should always be executed under a valid organization context because of the PLITBLM organization-security dependency.