Search Results delete_obj_tuning_options

Overview

APPS.FEM_ADMIN_UTIL_PKG is an administrative utility package belonging to the Oracle Enterprise Performance Foundation (formerly Enterprise Resource Planning Foundation) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the metadata-driven infrastructure that underpins ETRM (Enterprise Territory and Resource Management) and related Foundation components, in which business objects such as tables, views, and data-loading constructs are described declaratively in repository tables rather than hard-coded. The package provides validation and catalog-maintenance services used by the Foundation administration layer and by any module that registers or classifies objects in the FEM object catalog.

Its responsibilities fall into three broad categories: validating class assignments between objects and their classifying definitions, returning ownership metadata for views and indexes, and maintaining tuning or combination-identifier records. The package is not exposed to end users directly; it is invoked by internal concurrent programs, Forms-based administration screens, and seed data setup routines.

Key Procedures and Functions

• DELETE_OBJ_TUNING_OPTIONS — Removes tuning option records associated with a given object, identified by object ID. Used when an object definition is retired or reconfigured.
• NEW_LOCAL_VS_COMBO_ID — Generates or registers a new local value-set combination identifier for a given GVSC ID.
• VALIDATE_TAB_CLASS_ASSIGNMT — Validates that a table (by name) has a valid class assignment. Acts as an API-style validation entry point returning FND_API status and message data.
• VALIDATE_TAB_CLASS — Determines whether a specified table-class code is valid for a given table name, returning a simple pass/fail flag.
• VALIDATE_VIEW_CLASS — The procedure surfaced by the user's search term "validate_view_class." It determines whether a given tab-class code is valid for a specified view, returning the result through an OUT parameter flag. This is the view-oriented counterpart to VALIDATE_TAB_CLASS.
• VALIDATE_OBJ_CLASS_ASSIGNMT — Validates the class assignment for a generic object by object name, returning FND_API-compliant status information.
• GET_TABLE_OWNER_FOR_VIEW — Returns the Oracle schema owner of the underlying table(s) for a supplied view, supporting metadata resolution.
• GET_INDEX_OWNER_FOR_VIEW — Returns the schema owner associated with indexes for a given view, analogous to the preceding function.

Tables Accessed

The package reads and writes the FEM object catalog and property tables through APPS synonyms. FEM_OBJECT_CATALOG_B and FEM_OBJECT_CATALOG_TL hold the base and translated object catalog entries, while FEM_OBJECT_DEFINITION_B stores object definitions used during validation. FEM_TABLES_B and FEM_TABLES_TL provide base and translated table metadata, and FEM_TABLE_CLASS_PROP, FEM_TABLE_PROPERTIES, FEM_TABLE_PROP_COL_REQ, and FEM_TABLE_PROP_STP describe table property definitions, their required columns, and step configuration. FEM_COLUMN_REQUIREMNT_B records column-level requirements consulted for validation. FEM_DATA_LOADER_OBJECTS and FEM_PB_PARAMETERS relate to data-loader and parameter definitions. FEM_MP_DATA_SLICES and FEM_MP_DATA_SLICE_COLS store multidimensional data-slice metadata, and FEM_MP_PROCESS_OPTIONS stores process tuning options consumed by DELETE_OBJ_TUNING_OPTIONS.

Usage Notes

FEM_ADMIN_UTIL_PKG is invoked internally rather than through a public API contract. Administration Forms in the Foundation/ETRM responsibility call the validation procedures when an administrator saves a table, view, or object class assignment, providing immediate feedback on classification correctness. Concurrent programs that seed or migrate object catalog metadata use the same routines to enforce consistency across FEM_TABLES_B, FEM_OBJECT_CATALOG_B, and FEM_TABLE_CLASS_PROP. The procedures declared in the FND_API style (those carrying p_api_version, p_init_msg_list, p_commit, p_encoded, x_return_status, x_msg_count, and x_msg_data) follow the standard Oracle EBS API error-handling pattern, so callers must inspect x_return_status rather than relying on exceptions. Customizations that register new views or tables in the Foundation metadata schema should call VALIDATE_VIEW_CLASS or VALIDATE_TAB_CLASS before committing catalog rows, ensuring the class code is permitted for that object. Because the package is owned by APPS and references FEM tables via synonyms, it should be invoked with the standard APPS initialization sequence (FND_GLOBAL.APPS_INITIALIZE) in any custom or standalone calling context.