Search Results load_initial_seed_data




Overview
Explore in AI Chat

Overview

AMW_PARAMETERS_PVT_PKG is a private PL/SQL package in the APPS schema that manages the persistence and lifecycle of configuration parameters used by Oracle E-Business Suite's Approval Management Engine (AME) and its associated process organization framework. The package encapsulates the low-level insert, update, initialization, and defaulting logic for records stored in the AMW_PARAMETERS table, which drives runtime behavior of AME processing options such as approval routing and automatic approval configuration. By centralizing access to parameter data through a private API layer, the package allows the AME application modules to maintain consistent, validated parameter values across multiple organizations without exposing direct DML on AMW_PARAMETERS to external callers. The package was last modified under version 120.1 (2005) and carries no ship flag, indicating it is an internal (non-public) component rather than a published extension API.

Key Procedures and Functions

The package exposes seven documented procedures:

  • INSERT_PARAMETER — Creates a new parameter row, accepting a parameter name, value, and up to five primary key context values (p_pk1 through p_pk5) that identify the owning entity.
  • UPDATE_PARAMETER — Updates an existing parameter's value using the same name/value/primary-key context scheme.
  • INITIALIZE_ORG_PARAMETERS — Seeds organization-level AME parameters. It takes the process approval option and process auto-approve settings plus primary key context, and follows the standard FND_API error-handling convention with x_return_status, x_msg_count, and x_msg_data outputs. Defaults include p_commit = FND_API.G_FALSE and p_validation_level = FND_API.G_VALID_LEVEL_FULL.
  • UPDATE_ORG_PARAMETERS — Amends existing organization-level parameter records. Its signature mirrors INITIALIZE_ORG_PARAMETERS, including the optional primary key arguments and FND_API return-status outputs.
  • LOAD_INITIAL_SEED_DATA — Loads predefined seed parameter values, returning owner and last-update-date information alongside the supplied parameter name, value, and primary key context.
  • DEFAULT_ORG_PARAMETERS — Applies default parameter values to an organization, added as a bug fix for issue 4336520.
  • UPDATE_ALL_ORG_PARAMS_CP — A concurrent-program entry point (the "_CP" suffix denoting concurrent program) that drives the bulk update of organization parameters across the enterprise. This is the procedure most frequently targeted by administrators and developers searching the ETRM repository.

Tables Accessed

The package operates against the AME parameter and process-organization data model. AMW_PARAMETERS is the principal store for parameter name/value pairs and is the direct target of INSERT_PARAMETER, UPDATE_PARAMETER, and the org-level init/update/default routines. AMW_PROCESS_ORGANIZATION and AMW_PROCESS_ORGANIZATION_S (and its revision counterpart, AMW_PROCESS_ORG_REV_S) hold the organization-to-process definition mappings; the "_S" variants are the translated/language-specific shadow tables. AMW_PROCESS_LOCKS is referenced to provide concurrency protection during parameter maintenance, preventing simultaneous updates from corrupting organization parameter sets. Collectively, these tables support both single-organization parameter changes and bulk, all-organization updates.

Usage Notes

This is a private package and is not documented against the APPS public API standard; no other packages are documented as referencing it, so it is not intended for direct customer invocation. In practice it is called by AME setup forms and by the concurrent program associated with UPDATE_ALL_ORG_PARAMS_CP, which runs when an administrator needs to propagate parameter changes across all organizations. Custom code should avoid calling this package directly and should instead use the supported AME setup user interfaces; direct calls bypass intended validation sequencing and may conflict with the process locking mechanism. When investigating the "update_all_org_params_cp" search, note that this procedure is a concurrent-program wrapper, meaning its execution is scheduled and logged through the standard concurrent manager rather than invoked interactively.