Search Results get_sg_id
Overview
AS_PIPELINE_MOVE_PUB is a public PL/SQL package body in the Oracle EBS Applications (APPS) schema, supplied under the Oracle Sales (AS) product family. Its business function is to relocate sales pipeline data — specifically sales credits and access records — from one salesforce to another salesforce. The package exists to support mass reassignment of lead and opportunity ownership when sales representatives change roles, territories are restructured, or accounts are redistributed across sales groups.
The source header identifies the package as "the main package for the concurrent program 'Pipeline movement.'" The creation history dates to 02/27/01 (ACNG), and the file header shows a version of 120.0 last updated 2005/06/02, which is consistent with the code lineage carried into EBS 12.1.1 and 12.2.2. The package is classified as PUB, indicating it is a published, externally callable API rather than a private helper unit.
Key Procedures and Functions
The ETRM metadata documents two procedures in this package body:
- PIPELINE_MOVEMENT — The primary driver routine for relocating pipeline records between salesforces. Based on the documented input description, it accepts a from/to user and sales group pairing together with filtering criteria for win probability range, decision (close) date range, and a comma-separated list of lead statuses. Only records matching those criteria are moved, which allows selective rather than wholesale reassignment.
- PIPELINE_SC_MOVEMENT — The sales-credit movement routine. The "SC" designation corresponds to sales credits, the secondary data category the package is designed to move alongside access records.
The metadata does not expose parameter signatures for either procedure, and parameter lists are therefore not reproduced here. In practice, both are driven by the concurrent program parameters described in the package header comments.
Tables Accessed
ETRM lists seven objects referenced through APPS synonyms:
- AS_LEADS_ALL — The core sales lead/opportunity table. This is the principal source of records whose ownership and pipeline assignment are updated.
- AS_SALES_CREDITS — Stores sales credit allocations; moved by PIPELINE_SC_MOVEMENT so revenue attribution follows the reassigned pipeline.
- FND_USER — Resolves the from/to user login names supplied as concurrent program parameters into valid application user identities.
- JTF_RS_GROUPS_B — The resource group (sales group) base table, used to validate the from/to group numbers.
- JTF_RS_GROUP_MEMBERS — Maps resources to groups; used to confirm group membership and to determine which salesforce members are affected.
- JTF_RS_RESOURCE_EXTNS — The resource extension table holding salesforce/resource attributes for the users being moved.
- DUAL — Standard single-row utility table, typically for validation or default resolution.
Usage Notes
The canonical invocation path is the "Pipeline movement" concurrent program, which submits the package with the nine documented parameters in sequence: from_user_name, to_user_name, from_group_num, to_group_num, from_win_prob (default 0), to_win_prob (default 100), from_close_date (default 01-JAN-1900), to_close_date (default 01-JAN-4712), and a comma-delimited status list. Dates must be supplied in the format DD-MON-YYYY. The package is not referenced by any other documented package, so it is a terminal consumer rather than a shared library.
Because the parameters are not exposed in the metadata, custom code calling the procedures directly should reference the concurrent program definition or the package specification rather than assuming an argument order. Users searching for "get_sg_id" should note that no such function appears in the documented procedure list for this package; group identification here is handled through the JTF_RS resource group tables. Where a sales-group ID lookup is required, it is normally performed through the JTF_RS_GROUPS_B and JTF_RS_GROUP_MEMBERS validation logic used to resolve the from_group_num and to_group_num inputs, not through a named API in AS_PIPELINE_MOVE_PUB itself.
-
PACKAGE BODY: APPS.AS_PIPELINE_MOVE_PUB
12.2.2
-
PACKAGE BODY: APPS.AS_PIPELINE_MOVE_PUB
12.1.1
-
PACKAGE: APPS.JTF_RS_DBI_8I_CONC_PUB
12.1.1
-
PACKAGE: APPS.JTF_RS_DBI_8I_CONC_PUB
12.2.2
-
PACKAGE BODY: APPS.JTF_RS_DBI_CONC_PUB
12.2.2
-
PACKAGE BODY: APPS.JTF_RS_DBI_CONC_PUB
12.1.1
-
PACKAGE: APPS.JTF_RS_DBI_CONC_PUB
12.2.2
-
PACKAGE: APPS.JTF_RS_DBI_CONC_PUB
12.1.1
-
PACKAGE: APPS.OKI_DBI_UTIL_PVT
12.1.1
-
PACKAGE BODY: APPS.JTF_RS_DBI_8I_CONC_PUB
12.2.2
-
PACKAGE BODY: APPS.JTF_RS_DBI_8I_CONC_PUB
12.1.1
-
APPS.JTF_RS_DBI_CONC_PUB SQL Statements
12.1.1
-
APPS.JTF_RS_DBI_CONC_PUB SQL Statements
12.2.2
-
PACKAGE BODY: APPS.OKI_DBI_UTIL_PVT
12.1.1
-
APPS.OKI_DBI_UTIL_PVT dependencies on FII_TIME_ENT_PERIOD
12.1.1
-
APPS.JTF_RS_DBI_8I_CONC_PUB dependencies on JTF_RS_DBI_8I_CONC_PUB
12.2.2
-
APPS.JTF_RS_DBI_8I_CONC_PUB dependencies on JTF_RS_DBI_8I_CONC_PUB
12.1.1
-
APPS.AS_PIPELINE_MOVE_PUB dependencies on JTF_RS_GROUPS_B
12.2.2
-
APPS.AS_PIPELINE_MOVE_PUB dependencies on JTF_RS_GROUPS_B
12.1.1
-
APPS.AS_PIPELINE_MOVE_PUB dependencies on JTF_RS_RESOURCE_EXTNS
12.1.1
-
APPS.AS_PIPELINE_MOVE_PUB dependencies on FND_USER
12.1.1
-
APPS.AS_PIPELINE_MOVE_PUB dependencies on JTF_RS_RESOURCE_EXTNS
12.2.2
-
APPS.AS_PIPELINE_MOVE_PUB dependencies on FND_USER
12.2.2