Results for “ece_profile_options”

18 results




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

Overview

ECE_PROFILE_OPTIONS is a reporting and inquiry view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is catalogued under the EC — e-Commerce Gateway product and is documented as valid in the ETRM repository. The view presents the set of Oracle EBS profile options whose names begin with the prefix ECE_, which are the configuration settings used by the e-Commerce Gateway to control outbound and inbound transaction processing, mapping behavior, and interface enablement.

Because profile options are normally maintained through the standard System Administrator profile forms, this view provides a denormalized, query-friendly projection of profile metadata joined to their currently defined values. Its principal role is to allow developers, DBAs, and support analysts to inspect e-Commerce Gateway configuration through direct SQL rather than navigating multiple concurrent programs and forms. It is especially relevant to users searching for sql_validation, since the view exposes the SQL_VALIDATION column — the validation string that constrains permissible values for a given profile option.

Underlying Base Objects

The view is defined over two documented base objects in the APPS schema: FND_PROFILE_OPTIONS_VL, which is the translatable profile-option definition view, and FND_PROFILE_OPTION_VALUES, referenced through a synonym. The profile-option definition side supplies the option's identity, description, validation, and level enablement flags, while the values side supplies the single stored value at the site level.

The join is implemented with outer-join syntax on FND_PROFILE_OPTION_VALUES using the (+) operator, keyed on PROFILE_OPTION_ID. Two filters further constrain the result set: FPOV.LEVEL_ID(+) = 10001, which designates the Site level, and FPOV.APPLICATION_ID = 175, which corresponds to the e-Commerce Gateway application. The driving predicate is FPO.PROFILE_OPTION_NAME LIKE 'ECE_%', which restricts the view to e-Commerce Gateway profile options only. Because the value join is outer, profile options with no site-level value still appear, with PROFILE_OPTION_VALUE returned as NULL.

Key Columns

Common Use Cases and Queries

The most frequent use is auditing e-Commerce Gateway configuration, particularly the validation applied to each option. A representative query retrieving option identity, description, validation, and current site value is:

SELECT profile_option_name,
       user_profile_option_name,
       sql_validation,
       profile_option_value
FROM   apps.ece_profile_options
ORDER  BY profile_option_name;

To isolate options that carry a SQL validation string — the typical intent behind a "sql_validation" search — the following filter is useful:

SELECT profile_option_name, sql_validation
FROM   apps.ece_profile_options
WHERE  sql_validation IS NOT NULL;

Analysts comparing configured values against expected baselines can list only options that are enabled at Site level and currently set:

SELECT profile_option_name, profile_option_value
FROM   apps.ece_profile_options
WHERE  site_enabled_flag = 'Y'
AND    profile_option_value IS NOT NULL;

Because the view is a simple join with no PL/SQL or context dependencies, it is safe for read-only reporting, custom concurrent programs, and ad hoc diagnostics. It should never be used to update profile values; changes must be made through the supported profile-option maintenance forms to preserve the integrity of FND_PROFILE_OPTION_VALUES.