Search Results create_object_definition

Overview

The APPS.FEM_OBJECT_CATALOG_UTIL_PKG package is a utility API within the Oracle Enterprise Performance Foundation (also referenced as Enterprise Resource Management / FEM) schema family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its business function is to manage the lifecycle of object catalog entries and object definitions used by the EBS analytical and performance-management infrastructure. The object catalog is the registry through which folders, dependents, and origin metadata are organised so that downstream components can reference business objects in a consistent, versioned manner.

The package exposes a small, focused public interface consisting of four procedures: CREATE_OBJECT, CREATE_OBJECT_DEFINITION, VALIDATE_OBJ_DEF_EFFDATE, and DELETE_OBJECT. These procedures provide programmatic maintenance of catalog objects together with their effective-dated definitions, allowing callers to register new objects, attach definitions with valid date ranges, validate effective-date changes, and remove objects that are no longer required.

Key Procedures and Functions

• CREATE_OBJECT — Creates a new catalog object. It accepts the object's type code, owning folder, local-versus-combination identifier, access and origin codes, name, description, effective dates, and an object-definition name. It returns the generated object identifier and object-definition identifier along with the standard message-count, message-data, and return-status outputs.
• CREATE_OBJECT_DEFINITION — Creates a definition record for an existing object. It takes the object identifier, effective start and end dates, definition name, and object-origin code, and returns the new object-definition identifier. This procedure is the target of interest for callers searching on create_object_definition.
• VALIDATE_OBJ_DEF_EFFDATE — Validates a proposed effective-date range for an object definition. It evaluates a new start date and end date against the existing definitions for the supplied object identifier and returns a flag indicating whether the date range is valid, guarding against overlaps or gaps in effective dating.
• DELETE_OBJECT — Removes a catalog object identified by its object identifier, honouring the supplied API version and commit flags and returning the standard status and message outputs.

All four procedures follow the EBS API convention of returning x_msg_count, x_msg_data, and x_return_status, and they accept p_api_version and p_commit to control version compatibility and transaction commit behaviour.

Tables Accessed

• FEM_OBJECT_CATALOG_B and FEM_OBJECT_CATALOG_TL — base and translation tables that store the object catalog header and its language-specific text.
• FEM_OBJECT_DEFINITION_B and FEM_OBJECT_DEFINITION_TL — base and translation tables for object definitions, including effective-dated rows.
• FEM_OBJECT_DEFINITION_ID_SEQ and FEM_OBJECT_ID_SEQ — sequence objects that supply primary keys for definitions and catalog objects.
• FEM_OBJECT_DEPENDENCIES — records dependency relationships between objects, consulted during creation and deletion.
• FEM_OBJECT_TYPES_B — validation source for the object type code.
• FEM_USER_FOLDERS — supplies the folder context for a new object.
• FND_LOOKUP_VALUES — validates coded values such as access and origin codes.
• DBMS_UTILITY and DUAL — utility and single-row sources used for message handling and defaults.

Usage Notes

The package is classified as a general-purpose (OTHER) API and is referenced by at least six other packages in the FEM schema, which suggests it is most often invoked programmatically rather than directly through a form. Typical invocations occur from EBS forms, concurrent programs, or custom PL/SQL that must register catalog objects and their effective-dated definitions. Callers should always inspect x_return_status and the associated message stack before committing, and should supply realistic effective dates because definition rows are validated by VALIDATE_OBJ_DEF_EFFDATE. The source header indicates shipping version 120.2 (July 2005), so the interface has remained stable across the 12.1.1 and 12.2.2 releases.