Search Results get_owner_pre




Overview
Explore in AI Chat

Overview

AS_LEAD_ROUTING_WF_CUHK is a customizable PL/SQL package body in the Oracle E-Business Suite (EBS) covering releases 12.1.1 and 12.2.2. In the Oracle TeleSales / Sales Foundation module, the package provides customer-specific logic for assigning an owner to a sales lead. Unlike Oracle's standard lead routing packages, this package is intended to be modified by customers to implement their own rules for determining who should own a given lead. This is particularly relevant when the search term "telesales_agent" is considered: the owner of a lead is typically a resource—such as a telesales agent—who is responsible for following up on that lead. The package supports both Oracle's internal customization and customer-specific customization, and its primary responsibility is to return the correct owner for a lead, giving precedence to resources derived from territory assignments.

Key Procedures and Functions

The package exposes a single documented procedure, GET_OWNER_PRE.

  • GET_OWNER_PRE — This procedure serves as a pre-processing hook that determines the owner of a lead. It accepts standard API input parameters (including API version number, initialization message list, validation level, and commit flag) along with a resource input parameter. The procedure's core logic determines which resource should be returned as the lead owner, applying the business rule that a resource resolved through territory APIs takes higher precedence. This design allows customers to inject custom owner-assignment logic for their telesales agents without altering the standard Oracle code. Because the source is a sample body provided for customers to override, the exact implementation of the owner-determination logic is expected to vary per deployment.

Tables Accessed

The package references the following tables via APPS synonyms, each supporting the owner-resolution process:

  • AS_SALES_LEADS — Stores the sales lead records for which ownership is being determined; the procedure reads or updates lead data to associate the correct owner.
  • AS_TERRITORY_ACCESSES — Provides territory-based access information used to assign resources to leads based on territory assignments.
  • JTF_RS_RESOURCE_EXTNS — Contains resource extension information for the resources (such as telesales agents) being evaluated as potential owners.
  • JTF_TERR_RSC_ALL — Holds the territory-to-resource associations that give territory-derived resources their higher precedence in the owner-determination logic.

Usage Notes

AS_LEAD_ROUTING_WF_CUHK is invoked during lead routing operations, typically as part of the standard Oracle TeleSales lead assignment flow. It is referenced by two other packages, indicating its role as a pluggable customization point within the lead routing architecture. In a typical deployment, the procedure is called when a lead needs an owner assigned, whether through interactive entry or automated processing. Customers implement their own version of the package body to embed site-specific rules—governing which telesales agent receives a lead—and the territory API is used to ensure that resources with valid territory assignments take precedence, preventing incorrect or extra owners from being selected. Because the package is a customer-editable sample, its behavior may differ across organizations, and standard Oracle support does not guarantee its contents.