Search Results push_legacy_setup_parameters




Overview
Explore in AI Chat

Overview

The APPS.MSD_DEM_PUSH_SETUP_PARAMETERS package is a component of the Oracle E-Business Suite Demand Planning and Sales History data collection infrastructure, part of the MSD (Mobile Supply Chain / Demand Signal Repository) schema family. Its principal business function is to propagate or "push" setup and configuration parameters — such as profile option values and legacy system settings — from a source environment or staging area into the runtime configuration consumed by the demand collection and sales processing packages. In this capacity, the package acts as a bridge between administrative configuration and the operational programs that gather price lists, return history, and sales transaction data.

The package is classified by the Oracle ETRM as an API of classification OTHER. It is not a public, documented integration API in the sense of an open interface table or published business API; rather, it is an internal utility invoked by sibling collection packages during setup and initialization phases. The object is owned by the APPS schema and is reported as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents three procedures within this package:

  • PUSH_SETUP_PARAMETERS — The primary entry point. It transfers the current setup parameter set into the target location used by the demand collection layer, ensuring that downstream programs operate against the correct configuration values.
  • CONFIGURE_LEGACY_PROFILES — Establishes or aligns profile option values that legacy or non-native data sources rely upon. This supports backward compatibility when older collection routines or pre-existing profile definitions must remain consistent with the current setup.
  • PUSH_LEGACY_SETUP_PARAMETERS — The legacy-specific counterpart to the primary push routine, propagating parameters associated with pre-existing or non-standard setup records that were not covered by the standard configuration path.

All three procedures share the common purpose of synchronizing configuration state; none are documented as returning business data values.

Tables Accessed

Two tables are referenced through APPS synonyms:

  • DBA_OBJECTS — Queried to verify the existence, status, and validity of database objects (packages, procedures, or related schema elements) before setup parameters are pushed. This guards against propagating configuration that references invalid or missing objects.
  • PLITBLM — A PL/SQL internal/utility table used for bulk operations and intermediate storage during PL/SQL processing. Its presence indicates that the package performs set-based or batch manipulation of parameter rows rather than purely scalar processing.

No direct dependency on the major demand tables (price lists, return history, or sales data) is documented for this package; those are handled by the packages that call it.

Usage Notes

MSD_DEM_PUSH_SETUP_PARAMETERS is invoked indirectly rather than being scheduled as a standalone concurrent program. The dependency metadata shows it is referenced by three packages: MSD_DEM_COLLECT_PRICE_LISTS, MSD_DEM_COLLECT_RETURN_HISTORY, and MSD_DEM_PROCESS_SALES_DATA. In practice, these collection and processing packages call the setup-push routines during their initialization phase to guarantee that profile and legacy parameters are current before data extraction or transformation begins. The self-reference entry for MSD_DEM_PUSH_SETUP_PARAMETERS indicates internal calls between its own procedures, most likely the legacy-specific routine being invoked from the primary push routine. Administrators should treat the package as internal: direct invocation is not supported, and any custom code should call the parent collection packages rather than this utility. Changes to profile options or legacy settings are therefore propagated automatically the next time the associated demand collection programs execute.