Search Results as_lead_routing_wf




Overview
Explore in AI Chat

Overview

AS_LEAD_ROUTING_WF is a PL/SQL package body owned by the APPS schema that provides the server-side workflow integration layer for Oracle E-Business Suite Lead Routing. Within the Oracle EBS 12.1.1 and 12.2.2 environments, this package supports the automated assignment and reassignment of sales leads to resources and resource groups based on availability, workload, rank, and organizational role relationships. It functions as a bridge between the Oracle Workflow engine (WF_ENGINE, WF_CORE) and the Oracle Sales lead data model (AS_SALES_LEADS and its satellite tables), enabling rules-based routing of inbound leads without manual intervention. The package is classified as an OTHER API in the ETRM documentation and is currently VALID in the APPS schema. It depends on a broad set of foundation and CRM objects, including the JTF Resource Manager tables, the AS Sales Leads public and private APIs, and Oracle Workflow core packages, indicating its role as an orchestration point rather than a standalone data-maintenance utility.

Key Procedures and Functions

The documented interface exposes eight procedures and functions that collectively implement the routing lifecycle:

  • STARTPROCESS — Initiates the lead routing workflow process, establishing the workflow context for a given routing activity.
  • GETAVAILABLERESOURCE — Returns a single available resource suitable for receiving a routed lead, based on availability and eligibility rules.
  • GETAVAILABLERESOURCES — Returns the set of available resources, supporting multi-candidate evaluation during routing.
  • GETOWNER — Determines the current or appropriate owner of a lead within the routing context.
  • GETRESOURCEWORKLOAD — Retrieves the current workload for a resource, used to prevent over-assignment of leads.
  • BALANCEWORKLOAD — Distributes leads across resources to maintain an equitable workload balance.
  • UPDATESALESLEADS — Persists routing outcomes back to the sales lead records, applying assignment or reassignment results.
  • ESCALATETOMANAGER — Escalates a lead to a manager when standard routing cannot resolve an assignment, using JTF resource role relations.

Tables Accessed

The package reads and writes through APPS synonyms for the core lead and resource tables. AS_SALES_LEADS and AS_SALES_LEADS_LOG hold the lead records and audit trail updated by UPDATESALESLEADS and AS_SALES_LEADS_LOG_PKG. AS_SALES_LEAD_RANKS_B and AS_STATUSES_B supply ranking and status reference data used during routing decisions. AS_ACCESSES_ALL and AS_ACCESSES_S provide access-control context, while AS_WORKFLOW_KEYS_S stores workflow key mappings associating workflow items with lead entities. On the resource side, 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 provide the group membership, resource attributes, and manager role hierarchy required by GETAVAILABLERESOURCE, BALANCEWORKLOAD, and ESCALATETOMANAGER. DUAL and PLITBLM are used for utility and bulk-collection operations.

Usage Notes

AS_LEAD_ROUTING_WF is typically invoked indirectly through Oracle Workflow rather than called directly from forms. Lead routing workflows configured in the Oracle CRM application reference these procedures as workflow function activities, with WF_ENGINE driving execution. It is also referenced by two other PL/SQL packages, reflecting its role as a shared routing service. Because the package relies on FND_API, FND_GLOBAL, FND_MSG_PUB, and FND_PROFILE, it participates in the standard EBS API error-handling and message-stack conventions. Direct invocation in custom code is possible but should be limited to workflow-compatible contexts, as the procedures assume a valid workflow item key and FND_GLOBAL session context. In 12.2.2, the package remains unchanged in its documented interface relative to 12.1.1, with dependencies resolving through the unified APPS synonym layer.