Search Results validate_tab_class




Overview
Explore in AI Chat

Overview

FEM_ADMIN_UTIL_PKG is an administrative utility package in the Oracle E-Business Suite Enterprise Territory Management (formerly Enterprise Resource Territory Management / ETRM) module, owned by the APPS schema. It is classified under the API classification OTHER within the ETRM reference documentation, meaning it is not a competing public business API but rather an internal helper package invoked by other ETRM components to validate and maintain administrative metadata used by the territory and object catalog framework.

At a functional level, the package supports the object catalog that underpins territory definition, dimension member creation, and data slicer configuration. Its primary responsibilities include validating the relationship between physical database objects (tables and views) and the class codes attributed to them, validating class assignments for catalog objects, managing local value set combinations, and removing object-level tuning options. By centralizing these validations, FEM_ADMIN_UTIL_PKG ensures that the metadata stored in FEM_OBJECT_CATALOG_B and its related configuration tables remains consistent before downstream processes such as data loading or slicer generation are executed.

Key Procedures and Functions

  • DELETE_OBJ_TUNING_OPTIONS — Removes tuning option records associated with a specific object identified by p_object_id, cleaning up configuration data for an object from the catalog.
  • NEW_LOCAL_VS_COMBO_ID — Generates and returns a new local value set combination identifier, supporting the creation of locally managed value set combinations used in object metadata.
  • VALIDATE_TAB_CLASS_ASSIGNMT — Validates the class assignment for a given table name, serving as the assignment-level counterpart to the singular class validation routine. This is an API-style procedure returning a standard return status and message list.
  • VALIDATE_TAB_CLASS — The primary procedure associated with the search term "validate_tab_class." It validates whether a supplied table class code (p_tab_class_cd) is valid for a given table name (p_tab_name), returning a pass/fail indicator through x_passed_validation. It is commonly called during the definition or modification of a data loading object or table registration.
  • VALIDATE_VIEW_CLASS — Performs the analogous validation for database views, confirming that the supplied view class code is permissible for the named view.
  • VALIDATE_OBJ_CLASS_ASSIGNMT — Validates the object class assignment for a named object, using the standard ETRM API signature with return status, message count, and message data outputs.
  • GET_TABLE_OWNER_FOR_VIEW — Returns the owning schema for a given view, used to resolve ownership metadata in the catalog.
  • GET_INDEX_OWNER_FOR_VIEW — Returns the index owner associated with a view, supporting index administration for the underlying objects.

Tables Accessed

The package reads and writes across the ETRM administration schema. FEM_OBJECT_CATALOG_B and FEM_OBJECT_CATALOG_TL hold the catalog definitions and their translated names, which form the core target of the class and assignment validations. FEM_TABLES_B, FEM_TABLES_TL, FEM_TABLE_CLASS_PROP, FEM_TABLE_PROPERTIES, FEM_TABLE_PROP_COL_REQ, and FEM_TABLE_PROP_STP store table-level metadata, class properties, property requirements, and step information consulted during validation. FEM_OBJECT_DEFINITION_B, FEM_DATA_LOADER_OBJECTS, FEM_COLUMN_REQUIREMNT_B, FEM_MP_DATA_SLICES, FEM_MP_DATA_SLICE_COLS, FEM_MP_PROCESS_OPTIONS, and FEM_PB_PARAMETERS supply the surrounding configuration used by the object catalog and slicer framework.

Usage Notes

FEM_ADMIN_UTIL_PKG is typically invoked indirectly. Forms-based administration pages that register tables, views, or catalog objects call VALIDATE_TAB_CLASS, VALIDATE_VIEW_CLASS, and their assignment-level counterparts before committing records. Concurrent programs that build territory definitions or slicer metadata may call the validation procedures to pre-check object metadata. In 12.1.1 and 12.2.2, custom integrations that insert or update FEM_OBJECT_CATALOG_B and the FEM_TABLE_* configuration tables should follow the same pattern, calling these validation procedures and honoring the x_passed_validation result before performing DML, to avoid corrupting the object catalog used by the Enterprise Territory Management engine.