Search Results pipeline_movement




Overview
Explore in AI Chat

Overview

AS_PIPELINE_MOVE_PUB is a public PL/SQL package in the APPS schema that drives the "Pipeline Movement" concurrent program within the Oracle E-Business Suite Advanced Sales (AS) / TeleSales and Sales Online product family. Its business purpose is to reassign sales pipeline records — specifically sales credits and access records — from one salesforce (user/group combination) to another. This capability is used when sales representatives leave, change territories, or when accounts are redistributed across sales organizations, requiring the systematic transfer of opportunities and credits without manual re-keying.

The package header comment (asxppmvs.pls, version 120.1, dated 2005/06/05) documents that the script moves sales credits and access records between salesforces. The original creation date recorded in the history is 02/27/01. The package is the "main package for the concurrent program 'Pipeline movement'" (the phrase "pipeline_movement" corresponds to the PIPELINE_MOVEMENT procedure described below).

Although the ETRM metadata classifies this package with two documented procedures, the source comments indicate an older procedural interface accepting ordered parameters (from/to user name, from/to group name, win-probability range, decision-date range, and a comma-separated status list). This reflects a lineage where the logic originally existed as a SQL script invoked with positional parameters before being packaged as a public API.

Key Procedures and Functions

Two documented procedures are exposed by this package:

  • PIPELINE_MOVEMENT — The primary routine that performs the transfer of pipeline records between salesforces. Based on the source header, it accepts inputs identifying the "from" user login and group name and the "to" user login and group name, together with filtering criteria: a win-probability range (defaulting to 0 through 100 when unspecified), a decision/close-date range (defaulting to 01-JAN-1900 through 01-JAN-4712 when unspecified), and a list of lead/opportunity statuses provided as a comma-separated string. The procedure acts only on records matching these criteria, moving the associated sales credits and access records. No parameter list is asserted here beyond what the documentation records.
  • PIPELINE_SC_MOVEMENT — A companion routine handling the movement of sales-credit ("SC") counterparts associated with the pipeline records. Its name indicates it is the sales-credit-specific movement path invoked alongside or within the broader pipeline movement operation.

Both are public (API classification PUB), meaning they are callable from outside the package and intended as supported entry points for reassignment logic.

Tables Accessed

The package reads and writes the following tables, via APPS synonyms:

  • AS_LEADS_ALL — The central lead/opportunity table; pipeline records selected by status and date/win-probability ranges are updated to reflect the new salesforce ownership.
  • AS_SALES_CREDITS — Stores revenue and quota credit assignments; credits tied to moved opportunities are reassigned to the destination salesforce.
  • FND_USER — Resolves the "from" and "to" user login names to application user identities.
  • JTF_RS_GROUPS_B — Holds salesgroup (resource group) definitions; used to validate the from/to group names that bound a salesforce.
  • JTF_RS_GROUP_MEMBERS — Maps users to resource groups; used to identify the members comprising each salesforce.
  • JTF_RS_RESOURCE_EXTNS — The resource extension table providing resource-level attributes for users/groups participating in the move.
  • DUAL — Used for singleton lookups and validation queries.

Usage Notes

AS_PIPELINE_MOVE_PUB is normally invoked through the "Pipeline Movement" concurrent program rather than called directly. Administrators submit the program, supplying the from/to salesforce users and groups plus the filtering ranges (win probability, decision date, statuses) so that only the intended subset of pipeline records is reassigned. The ETRM metadata records no other packages referencing this package (referenced by 0 other packages), confirming it is a top-level entry point not embedded in a larger call chain.

Because the package writes to AS_LEADS_ALL and AS_SALES_CREDITS, it should be executed during controlled administration windows, and its results validated against sales-credit and territory reporting after completion. Custom integrations may call PIPELINE_MOVEMENT or PIPELINE_SC_MOVEMENT directly, but should treat the parameter interface as legacy (positional, per the source header) and confirm behavior against the target release (12.1.1 or 12.2.2) before relying on it in automation.