Search Results fnd_svc_comp_param_vals_p1

Overview

FND_SVC_COMP_PARAM_VALS is a table in the APPLSYS schema within Oracle E-Business Suite, belonging to the FND — Application Object Library product. Its documented description is "Service Component Parameter Values," indicating that it stores the configurable parameter settings associated with service components in the Oracle EBS Service component framework. Service components are the building blocks used by the Service framework to define runtime behavior — for example, email delivery, workflow notification, or concurrent processing services — and each component exposes parameters whose values are persisted in this table.

The table is listed with a status of VALID and exposes twelve documented columns in the ETRM 12.2.2 schema. It is a standalone object from a referential perspective; the metadata's heuristic Data Vault classification identifies it as standalone, meaning it does not participate in a parent-child FK chain within the mined relationship set. In Data Vault modeling terms, it is best treated as a satellite-like structure that records parameter values keyed to a component and parameter pair, rather than as a hub or link.

Key Information Stored

The table's primary key is the surrogate column COMPONENT_PARAMETER_ID, enforced by the index FND_SVC_COMP_PARAM_VALS_P1. Two unique indexes act as business-key candidates and identify the natural identity of each record: FND_SVC_COMP_PARAM_VALS_U1 keys on COMPONENT_PARAMETER_ID and ZD_EDITION_NAME, while FND_SVC_COMP_PARAM_VALS_U2 keys on COMPONENT_ID, PARAMETER_ID, and ZD_EDITION_NAME. The U2 index is especially significant because it confirms that a parameter assignment is unique per component and edition.

The most important columns include COMPONENT_ID, which identifies the parent service component; PARAMETER_ID, which identifies the parameter definition being set; and PARAMETER_VALUE, which holds the actual configured value. CUSTOMIZATION_LEVEL indicates whether the row is a seeded/system value or a customer-level override, a critical distinction when diagnosing configuration drift after patching. ZD_EDITION_NAME supports edition-based configuration, allowing different parameter values to coexist across editions. Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record row lifecycle and user activity, while OBJECT_VERSION_NUMBER provides optimistic locking for concurrent updates.

Common Use Cases and Queries

Typical uses include auditing service component configuration, comparing seeded versus customized parameter values across environments, and generating configuration baselines for cloning or migration. A common query resolves the parameter values for a given component:

• SELECT component_id, parameter_id, parameter_value, customization_level, last_update_date FROM fnd_svc_comp_param_vals WHERE component_id = :component_id;
• SELECT * FROM fnd_svc_comp_param_vals WHERE customization_level = 'C'; — lists customer-customized parameter values for change review.
• SELECT component_id, parameter_id, COUNT(*) FROM fnd_svc_comp_param_vals GROUP BY component_id, parameter_id HAVING COUNT(*) > 1; — validates uniqueness before assuming a single value per component and parameter.

Reporting use cases include environment-difference reports (11.5.10 to 12.1.1, or 12.1.1 to 12.2.2) and post-upgrade reconciliation of seeded values against the current configuration.

Related Objects

Because the metadata classifies FND_SVC_COMP_PARAM_VALS as standalone, no foreign keys are documented. The most significant related objects are those implied by the columns and by the Service framework itself:

• FND_SVC_COMPONENTS — joined on COMPONENT_ID to resolve the parent service component definition.
• FND_SVC_COMP_PARAMS — joined on PARAMETER_ID to resolve parameter definitions and metadata.
• FND_SVC_COMP_PARAM_VALS_U2 — the composite unique index used to enforce component/parameter/edition uniqueness.
• FND_SVC_SERVICE_PARAMETERS and related service configuration tables used by the Service framework.
• FND_LOOKUP_VALUES — often joined to decode customization_level and similar coded columns.
• FND_USER — joined on CREATED_BY or LAST_UPDATED_BY for audit attribution.

In 12.1.1 the ZD_EDITION_NAME column is absent; edition support is introduced with 12.2.x, so queries should be version-aware when comparing the two releases.