Results for “fnd_svc_comp_params_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_SVC_COMP_PARAMS_B is a core configuration table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the base-language definitions of service component parameters — the configurable inputs that govern how a service component behaves within the EBS Service Component Architecture (SCA). Service components (defined in the companion table FND_SVC_COMP_TYPES_B) represent runtime services that the framework instantiates, and each component exposes a set of parameters declared here. This table holds the language-independent ("_B") attributes of each parameter, while translated, user-facing text resides in FND_SVC_COMP_PARAMS_TL.

Because the table is primarily a dependent definition store keyed by a surrogate identifier and linked to a parent component type, its heuristic Data Vault classification is satellite-leaning. Under that modeling suggestion, FND_SVC_COMP_PARAMS_B would be treated as a satellite attached to a parent hub/link (the component type), capturing descriptive attributes of each parameter rather than defining an independent business entity.

Key Information Stored

The physical schema documents 15 columns. The most significant include:

• PARAMETER_ID — The surrogate primary key (FND_SVC_COMP_PARAMS_B_PK1) and the unique identifier used by all foreign key relationships.
• PARAMETER_NAME — The programmatic name of the parameter, used by the framework and application code to resolve the input.
• COMPONENT_TYPE — The foreign key to FND_SVC_COMP_TYPES_B indicating the parent service component to which this parameter belongs.
• DEFAULT_PARAMETER_VALUE — The value supplied when the parameter is not explicitly overridden.
• REQUIRED_FLAG — Indicates whether a value must be supplied for the parameter.
• ALLOW_RELOAD_FLAG — Determines whether the parameter may be refreshed at runtime without restarting the component.
• ENCRYPTED_FLAG — Marks parameters whose values are sensitive and stored or transmitted encrypted.
• CUSTOMIZATION_LEVEL — The allowed level of user or customer modification of the parameter.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrency control.
• ZD_EDITION_NAME — The editioning column enabling EBS online patching (introduced in 12.2), which forms part of the unique index FND_SVC_COMP_PARAMS_B_U1.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — record change history.

The business-key candidate is FND_SVC_COMP_PARAMS_B_U1, comprising PARAMETER_ID and ZD_EDITION_NAME; the surrogate key remains PARAMETER_ID alone.

Common Use Cases and Queries

Typical uses include auditing parameter defaults, verifying required vs. optional parameters, and diagnosing encryption or reload behavior for a service component.

• List parameters for a given component type:

  SELECT p.parameter_id, p.parameter_name, p.default_parameter_value
  FROM   applsys.fnd_svc_comp_params_b p
  WHERE  p.component_type = :component_type
  AND    p.zd_edition_name = 'SET1';

• Find required or encrypted parameters:

  SELECT parameter_name, required_flag, encrypted_flag
  FROM   applsys.fnd_svc_comp_params_b
  WHERE  required_flag = 'Y' OR encrypted_flag = 'Y';

• Join to translated descriptions in the TL table using PARAMETER_ID for reporting.

Related Objects

• FND_SVC_COMP_PARAMS_TL — Translation table; joins on PARAMETER_ID = FND_SVC_COMP_PARAMS_TL.PARAMETER_ID to provide language-specific names and descriptions.
• FND_SVC_COMP_TYPES_B — Parent table for the component definition; joined via COMPONENT_TYPE.
• FND_SVC_COMP_TYPES_TL — Translation counterpart of the parent type table.
• FND_SVC_COMPONENTS — Runtime component instances that consume parameter definitions.
• FND_SVC_COMP_PARAM_VALUES — Instance-level parameter values derived from these definitions.

Together these objects form the metadata backbone of the EBS service component framework, with FND_SVC_COMP_PARAMS_B defining what each component can be configured with.