Search Results custom_mode
Overview
APPS.PO_CLM_SEED_DATA_PKG is a seeding and configuration utility package belonging to the Purchasing (PO) module of Oracle E-Business Suite. Its principal responsibility is to load Oracle Purchasing's Contract Lifecycle Management (CLM) seed data and associated application messages into the EBS repository during installation, upgrade, or patching activities. The package version referenced (120.5.12020000.3) was last shipped in February 2013 and is present across the 12.1.1 and 12.2.2 code lines.
The package is guarded by the profile option PO_CLM_INSTALLED. When this profile evaluates to 'Y', the package proceeds with its loading logic; otherwise, execution is effectively bypassed. This design ensures that CLM seed data is populated only in environments where the Procurement Contracts / CLM functionality is licensed and enabled, preventing unnecessary data from being loaded in non-CLM installations.
Key Procedures and Functions
The ETRM metadata documents one public procedure, PROCESS, along with a helper function, SUBMIT_REQUEST, used internally.
- PROCESS — The main entry point of the package. It accepts a processing mode and a style identifier, and, after confirming that the CLM profile option is enabled, submits one or more concurrent requests to load CLM seed data. In the excerpt, the LOAD mode submits a FNDLOAD request with the message loader control file afmdmsg.lct and the data file CLMpomsg.ldt, writing status information and the returned request ID to the concurrent manager log via FND_FILE. A second FNDLOAD invocation references the CLM lookup data file CLMpolkup.ldt. The procedure follows the standard concurrent program signature (errbuf, retcode) so it can be registered as a concurrent executable.
- SUBMIT_REQUEST — A thin wrapper around FND_REQUEST.SUBMIT_REQUEST. It accepts up to ten positional arguments and the usual application/program/description/start_time/sub_request parameters, returning the numeric request identifier. It standardises request submission for the package's loading tasks.
The literal token CUSTOM_MODE=FORCE_SEED appears as an argument to the FNDLOAD call, instructing the loader to overwrite existing seed rows rather than merge them. This is the parameter users often search for when troubleshooting seed-data conflicts, as it forces the loader to replace prior seeded content with the current shipped definitions.
Tables Accessed
The documented metadata does not list any tables referenced directly through APPS synonyms. The package operates primarily through the FNDLOAD utility and FND_REQUEST.SUBMIT_REQUEST, both of which handle their own data manipulation internally. No package is recorded as referencing PO_CLM_SEED_DATA_PKG, indicating it is a terminal utility rather than a shared API consumed by other PL/SQL code.
Usage Notes
PO_CLM_SEED_DATA_PKG is intended for administrative seeding scenarios rather than day-to-day transactional processing. It is typically invoked during patching or installation when CLM messages and lookup codes must be refreshed, or manually by a system administrator via a concurrent program that wraps the PROCESS procedure. Because the package submits child concurrent requests and logs to the standard concurrent output, the submitted requests and their IDs are visible in the Concurrent Requests form. When diagnosing seed-data problems, note that the CUSTOM_MODE=FORCE_SEED argument will overwrite existing CLM nomenclature message and lookup rows, so any site-specific customisations to those seeded records should be reviewed before execution.
-
PACKAGE BODY: APPS.PO_CLM_SEED_DATA_PKG
12.2.2
-
PACKAGE: APPS.GCS_ELIM_RULE_STEPS_PKG
12.1.1
-
PACKAGE: APPS.GCS_TREATMENTS_PKG
12.1.1
-
PACKAGE: APPS.GCS_FORMULA_STATEMENTS_PKG
12.1.1
-
PACKAGE: APPS.GCS_LEX_MAP_STRUCTS_PKG
12.1.1
-
PACKAGE: APPS.GCS_ELIM_RULES_PKG
12.1.1
-
PACKAGE: APPS.GCS_FORMULA_VARIABLES_PKG
12.1.1
-
PACKAGE: APPS.GCS_LEX_MAP_COLUMNS_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_FORMULA_VARIABLES_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_LEX_MAP_STRUCTS_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_FORMULA_STATEMENTS_PKG
12.1.1
-
PACKAGE: APPS.GCS_INTERCO_RULES_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_LEX_MAP_COLUMNS_PKG
12.1.1
-
APPS.GCS_LEX_MAP_STRUCTS_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.GCS_CURR_TREATMENTS_PKG
12.1.1
-
APPS.GCS_FORMULA_STATEMENTS_PKG SQL Statements
12.1.1
-
APPS.GCS_FORMULA_VARIABLES_PKG SQL Statements
12.1.1
-
APPS.GCS_LEX_MAP_COLUMNS_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.GCS_HIERARCHIES_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_ELIM_RULE_STEPS_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_ELIM_RULES_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_TREATMENTS_PKG
12.1.1
-
PACKAGE: APPS.GCS_DATA_TYPE_CODES_PKG
12.1.1
-
PACKAGE: APPS.GCS_CATEGORIES_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_SYSTEM_TASKS_PKG
12.1.1
-
APPS.GCS_ELIM_RULE_STEPS_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.GCS_DATA_TYPE_CODES_PKG
12.1.1
-
PACKAGE BODY: APPS.GCS_CATEGORIES_PKG
12.1.1
-
APPS.GCS_DATA_TYPE_CODES_PKG SQL Statements
12.1.1
-
APPS.GCS_ELIM_RULES_PKG SQL Statements
12.1.1
-
APPS.GCS_TREATMENTS_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.GCS_SYSTEM_TASKS_PKG
12.1.1
-
APPS.GCS_SYSTEM_TASKS_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.GCS_INTERCO_RULES_PKG
12.1.1
-
PACKAGE: APPS.FND_LOAD_UTIL
12.1.1
-
APPS.GCS_CATEGORIES_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.FND_LOAD_UTIL
12.2.2
-
PACKAGE BODY: APPS.GCS_CURR_TREATMENTS_PKG
12.1.1
-
PACKAGE BODY: APPS.MSD_PLAN_TYPE_VIEWS_PKG
12.1.1
-
PACKAGE BODY: APPS.MSD_PLAN_TYPE_VIEWS_PKG
12.2.2
-
APPS.GCS_CURR_TREATMENTS_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.FND_LOAD_UTIL
12.2.2
-
APPS.GCS_INTERCO_RULES_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.MSD_LEVELS_PKG
12.1.1
-
PACKAGE BODY: APPS.MSD_LEVELS_PKG
12.2.2
-
APPS.AMS_CUSTOM_SETUP_PURPOSE_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.ICX_NONCAT_TEMPLATES_PKG
12.1.1
-
PACKAGE BODY: APPS.ICX_NONCAT_TEMPLATES_PKG
12.2.2
-
PACKAGE BODY: APPS.OKE_APPROVAL_PATHS_PKG
12.1.1
-
PACKAGE BODY: APPS.OKE_APPROVAL_PATHS_PKG
12.2.2