Search Results campaign_routing




Overview
Explore in AI Chat

Overview

PV_BG_PARTNER_MATCHING_PUB is a public PL/SQL package in the APPS schema that provides the core partner-matching and campaign-routing engine for Oracle EBS Partner Management within the Enterprise Territory Management (ETRM) and TeleSales / Sales Leads footprint. The package resolves the business problem of automatically determining which channel partners, resources, groups, or campaigns should be associated with an incoming sales lead or opportunity. It evaluates partner profiles, resource group definitions, role relationships, and campaign source codes to derive the correct assignment and to route leads to the appropriate owner or partner organization. The package is classified as a public (PUB) API, meaning its procedures are intended for invocation by external callers such as other public packages, workflow activities, forms, and custom extensions, rather than being reserved for internal use.

Key Procedures and Functions

The package exposes four documented procedures. The parameter lists are not published in the metadata and should be confirmed directly from the package specification in the target instance before use.

  • START_PARTNER_MATCHING — Initiates the partner-matching process for a lead or opportunity. It serves as the entry point that sets up the matching context and triggers evaluation of eligible partners.
  • PARTNER_MATCHING — Performs the actual matching logic, comparing lead or opportunity attributes against partner profiles and resource definitions to identify the best-fit partner or resource.
  • START_CAMPAIGN_ASSIGNMENT — Begins the campaign-assignment routine, establishing context for evaluating whether a lead should be tied to a marketing campaign.
  • CAMPAIGN_ROUTING — Executes campaign routing, determining the campaign and associated assignment for the lead based on source codes, statuses, and workflow configuration.

Tables Accessed

The package reads and writes a defined set of tables via APPS synonyms. Partner and resource configuration is sourced from PV_PARTNER_PROFILES, 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, which together define partner profiles, resource groups, membership, usages, resources, and role hierarchies. Lead and workflow data is managed through AS_LEADS_ALL, AS_STATUSES_B, PV_LEAD_WORKFLOWS, and PV_LEAD_WORKFLOWS_S. Campaign and activity associations draw on AMS_ACT_PARTNERS and AMS_SOURCE_CODES. DUAL supports scalar lookups, and PLITBLM is the standard PL/SQL table/list utility used for in-memory collections.

Usage Notes

PV_BG_PARTNER_MATCHING_PUB is referenced by AS_SALES_LEADS_PUB, AS_SALES_LEAD_ENGINE_PVT, PV_OPPORTUNITY_VHUK, and itself (recursive or documented self-reference). This dependency chain indicates the package is invoked in the lead and opportunity lifecycle, typically from the Sales Leads engine and the opportunity view/entity handler. It is normally called indirectly by those public APIs rather than by end users, and it also participates in Oracle Workflow-driven lead routing. Because it is a PUB API, custom code should call it through its public procedures rather than accessing dependent tables directly. Developers should verify the exact specification signatures, commit/rollback behavior, and any FND_API-based error handling before integrating, since the metadata does not expose parameter lists or return values.