Search Results gmp_aps_ds_pull




Overview
Explore in AI Chat

Overview

GMP_APS_DS_PULL is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. Its name and dependencies indicate that it belongs to the Oracle Advanced Planning and Scheduling (APS) and Process Manufacturing (OPM/GMP) integration layer. The package functions as a data staging "pull" utility: it extracts demand, supply, resource, and forecast information from the transactional GMP source tables and writes it into the MSC_ST (Advanced Supply Chain Planning staging) tables consumed by the MSC_CL_PULL runtime engine. This supports the population of planning data collections for batch or continuous manufacturing operations.

The package is classified as OTHER in the ETRM documentation, meaning it is not a formally published public API but an internal integration component. It carries seventeen documented tables, twenty-six procedures/functions, and direct references to SYS.STANDARD plus a dependency on MSC_CL_PULL, confirming its role as a supplier of staged rows rather than as an end-user interface.

Key Procedures and Functions

The documented routines group into several functional clusters:

Parameter lists are not reproduced here; the documentation records signatures only by procedure name.

Tables Accessed

The package reads source data from GMP_DEMANDS_API and GMP_RESOURCE_INSTANCES and writes staged records primarily into the MSC_ST family. Specific targets include MSC_ST_DEMANDS, MSC_ST_DESIGNATORS, MSC_ST_JOB_OPERATIONS, MSC_ST_JOB_OPERATION_NETWORKS, MSC_ST_JOB_OP_RESOURCES, MSC_ST_RESOURCE_CHARGES, MSC_ST_RESOURCE_INSTANCE_REQS, MSC_ST_RESOURCE_REQUIREMENTS, and MSC_ST_SUPPLIES. Utility dependencies on DBMS_SESSION, DUAL, and PLITBLM confirm session context handling and PL/SQL table management. These tables collectively feed ASCP/MSO collection and therefore determine the accuracy of downstream plans.

Usage Notes

GMP_APS_DS_PULL is not invoked directly by end users. It executes as part of the APS data collection concurrent programs and is called from MSC_CL_PULL during the staging pull phase. Because it is classified as OTHER, custom code should avoid direct invocation and instead rely on the standard planning collection request set. In Oracle EBS 12.1.1 and 12.2.2, the package remains valid and unchanged in dependency shape. Any modification risks inconsistency between OPM transactional data and MSC staging, potentially producing inaccurate planning results; it should therefore be treated as an internal, upgrade-managed component.