Search Results fnd_svc_comp_param_vals_u1

Overview

APPLSYS.FND_SVC_COMP_PARAM_VALS is a Service Component configuration table in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores parameter value configuration data for Service Components, which form the foundation of the Service Provider Framework used by concurrent processing, workflow background engines, the FND service container, and related infrastructure components. Each row records the value assigned to a specific parameter of a given Service Component instance, allowing administrators to tune component behavior without modifying code.

The table resides in the APPS_TS_SEED tablespace with PCTFREE 10, consistent with its role as seed and configuration data. Its FND Design Data reference is FND.FND_SVC_COMP_PARAM_VALS, and its status is VALID. Under the heuristic Data Vault classification mined from the foreign-key structure, the object is assessed as standalone; from a modeling perspective, this suggests it functions as an independent reference or configuration table rather than a hub, link, or satellite within a Data Vault model. This classification reflects that the documented metadata does not show inbound or outbound foreign-key constraints on other tables.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• COMPONENT_PARAMETER_ID — Numeric surrogate identifier and the primary key of the row (enforced by index FND_SVC_COMP_PARAM_VALS_P1).
• COMPONENT_ID — Identifier of the Service Component for which the parameter value has been configured.
• PARAMETER_ID — Identifier of the Service Component-Type parameter definition being valued.
• PARAMETER_VALUE — VARCHAR2(1996) holding the parameter value. The user interface accepts only 665 characters for this field, a documented constraint worth noting for data-loading scripts.
• CUSTOMIZATION_LEVEL — VARCHAR2(30) indicating the extent to which the parameter value has been or can be customized.
• OBJECT_VERSION_NUMBER — Optimistic locking column required by the user interface.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in 12.2.x; it participates in both unique indexes.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide audit history.

Two unique indexes act as business-key candidates. FND_SVC_COMP_PARAM_VALS_U1 enforces uniqueness on (COMPONENT_PARAMETER_ID, ZD_EDITION_NAME), while FND_SVC_COMP_PARAM_VALS_U2 — the index referenced in the user's search term — enforces uniqueness on (COMPONENT_ID, PARAMETER_ID, ZD_EDITION_NAME). The U2 constraint guarantees that, within an edition, a given component cannot hold more than one value for the same parameter, making the (COMPONENT_ID, PARAMETER_ID) pair the effective natural key.

Common Use Cases and Queries

Typical usage centers on reviewing and comparing configuration across Service Components, particularly after cloning, patching, or troubleshooting concurrent manager behavior. A straightforward retrieval lists all parameters for a component:

• SELECT component_id, parameter_id, parameter_value, customization_level FROM applsys.fnd_svc_comp_param_vals WHERE component_id = :component_id;
• SELECT * FROM applsys.fnd_svc_comp_param_vals WHERE component_id = :component_id AND parameter_id = :parameter_id;
• SELECT COUNT(*), component_id FROM applsys.fnd_svc_comp_param_vals GROUP BY component_id ORDER BY 1 DESC;

Because ZD_EDITION_NAME is part of both unique indexes, queries intended for a single edition should include an appropriate edition filter. Reporting scripts commonly join COMPONENT_ID and PARAMETER_ID to their respective definition tables to present readable parameter names and descriptions rather than raw identifiers, and administrators use such reports to validate that customized values (identified through CUSTOMIZATION_LEVEL) survive upgrades and clones.

Related Objects

The ETRM metadata records that APPLSYS.FND_SVC_COMP_PARAM_VALS does not reference any database object, and it is referenced only by the editioning view APPLSYS.FND_SVC_COMP_PARAM_VALS#. Consequently, the documented dependency footprint is narrow. Functionally, this table is consumed alongside the Service Component framework's definition objects:

• APPLSYS.FND_SVC_COMP_PARAM_VALS# — the editioning view over the base table, used by the application layer in 12.2.x.
• Service Component and Component-Type definition tables (holding COMPONENT_ID and PARAMETER_ID metadata) — joined via COMPONENT_ID and PARAMETER_ID to resolve names.
• Concurrent processing and Service Provider Framework runtime tables that read parameter values at execution time.
• FND loaders and configuration migration utilities that seed parameter values during environment setup and cloning.

The absence of formal foreign keys in the documented metadata means referential integrity is maintained by the application layer, so joins to definition tables should be written defensively and validated against Oracle ETRM before use in production reporting.