Results for “csc_plan_enable_setup_v”
22 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.CSC_PLAN_ENABLE_SETUP_V is a reporting and integration object within the CSC – Customer Care product of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It is a denormalized read-only view built on top of the base table CSC_PLAN_ENABLE_SETUP, which stores the configuration that governs which functions are enabled for service plan processing. The view joins that base table to the function and application definition views in the Application Object Library, exposing function names, function types, and application names alongside the enablement flags. Its documented purpose is to support the lock-row event of server-side APIs, which require a queryable representation of the enable-setup records in order to acquire and validate locks against the underlying rows. Because it resolves the numeric foreign keys of the base table into descriptive names, it is also convenient for reporting, data extraction, and diagnostics of service plan function enablement.
Underlying Base Objects
The view is defined over three documented referenced objects:
CSC_PLAN_ENABLE_SETUP(SYNONYM) — the primary transactional base table holding enable-setup rows, including the enablement flags, date ranges, and descriptive flexfield attributes.FND_FORM_FUNCTIONS_VL(VIEW) — the multilingual function definition view, supplyingFUNCTION_NAME,USER_FUNCTION_NAME, andTYPE(exposed asFUNCTION_TYPE), andAPPLICATION_ID.FND_APPLICATION_VL(VIEW) — the multilingual application definition view, supplyingAPPLICATION_NAME.
The join condition is CPES.FUNCTION_ID = FFV.FUNCTION_ID AND FFV.APPLICATION_ID = FAV.APPLICATION_ID. Consequently the view returns only those enable-setup rows whose FUNCTION_ID resolves to a valid registered function and whose owning application is resolvable. Rows referencing an orphaned or unregistered function are excluded.
Key Columns
ENABLE_SETUP_ID— primary identifier of the enable-setup record.FUNCTION_ID— foreign key to the registered function; joined from the base table.FUNCTION_NAMEandUSER_FUNCTION_NAME— the internal and user-facing function names, resolved viaFND_FORM_FUNCTIONS_VL.FUNCTION_TYPE— the function type, sourced fromFFV.TYPE; the value the user searched for (function_type) is exposed here and typically distinguishes form, JSP, and other function classes.START_DATE_ACTIVE/END_DATE_ACTIVE— the effective date range of the enablement configuration.ON_INSERT_ENABLE_FLAG,ON_UPDATE_ENABLE_FLAG,CUSTOM1_ENABLE_FLAG,CUSTOM2_ENABLE_FLAG— flags controlling which plan events trigger the associated function.APPLICATION_IDandAPPLICATION_NAME— the owning application, resolved viaFND_APPLICATION_VL.- Standard WHO columns (
CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN) andOBJECT_VERSION_NUMBERfor optimistic locking. ATTRIBUTE1throughATTRIBUTE15andATTRIBUTE_CATEGORY— descriptive flexfield segments.
Common Use Cases and Queries
Typical scenarios include auditing which functions are enabled for a plan event, filtering by function type, and joining to plan definitions when diagnosing why a server-side API did not fire.
- List active form functions with their applications:
SELECT function_name, user_function_name, function_type, application_name FROM csc_plan_enable_setup_v WHERE function_type = 'FORM' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
- Inspect insert/update enablement flags for a given function:
SELECT enable_setup_id, function_id, on_insert_enable_flag, on_update_enable_flag FROM csc_plan_enable_setup_v WHERE function_name = :p_function_name;
- Join back to the base table for full flexfield detail where the view does not expose every attribute.
Because the view excludes unresolvable function rows, any audit of enable-setup records should be reconciled against CSC_PLAN_ENABLE_SETUP directly to detect orphaned entries.
-
This view is based on CSC_PLAN_ENABLE_SETUP used in lock row event of server side API's
APPS.CSC_PLAN_ENABLE_SETUP_V·↳ CSC_PLAN_ENABLE_SETUP·↳ FND_APPLICATION_VL·↳ FND_FORM_FUNCTIONS_VL·Explore CSC module →
-
This view is based on CSC_PLAN_ENABLE_SETUP used in lock row event of server side API's
APPS.CSC_PLAN_ENABLE_SETUP_V·↳ CSC_PLAN_ENABLE_SETUP·↳ FND_APPLICATION_VL·↳ FND_FORM_FUNCTIONS_VL·Explore CSC module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - CSC Tables and Views 12.2.2
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - CSC Tables and Views 12.1.1
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - CSC Tables and Views 12.2.2
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - CSC Tables and Views 12.1.1
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - FND Tables and Views 12.1.1
No longer used