Search Results update_obj_exec_status
Overview
APPS.FEM_PL_PKG is the core PL/SQL package that implements the runtime engine of Oracle Enterprise Data Management (formerly Enterprise Planning and Budgeting/EDM) in Oracle EBS 12.1.1 and 12.2.2. Its name derives from "FEM" (Financial Enterprise Management, the schema prefix used throughout the EDM/EPB product) and "PL," denoting the Process Logic layer responsible for managing object definitions, object executions, concurrent request tracking, and dependency resolution. The package provides the programmatic foundation by which EDM objects — such as ledger objects, mapping objects, and consolidation objects — are registered, executed, monitored, and cleaned up.
Beyond orchestration, FEM_PL_PKG enforces edit-lock and approval-lock semantics, determines whether objects and object definitions may be safely deleted, and validates effective dates against existing result data. It is a widely depended-upon package; ETRM metadata indicates it is referenced by 26 other packages, underscoring its role as a shared service layer rather than a single-purpose utility.
Key Procedures and Functions
The 36 documented procedures fall into several functional clusters:
- Edit and approval locks: OBJ_DEF_DATA_EDIT_LOCK_EXISTS, OBJ_DEF_APPROVAL_LOCK_EXISTS, OBJ_EXECUTION_LOCK_EXISTS, and GET_OBJECT_DEF_EDIT_LOCKS detect whether an object definition or execution is currently locked, preventing conflicting concurrent modifications.
- Effective date validation: EFFECTIVE_DATE_INCL_RSLT_DATA (two overloads) verifies whether proposed effective start/end dates overlap existing result data, protecting data integrity during definition changes.
- Deletion eligibility: CAN_DELETE_OBJECT and CAN_DELETE_OBJECT_DEF determine whether an object or object definition may be removed, given its process type and dependencies.
- Object registration: REGISTER_OBJECT_DEF, REGISTER_DEPENDENT_OBJDEFS, REGISTER_OBJECT_EXECUTION, REGISTER_TABLE, REGISTER_UPDATED_COLUMN, REGISTER_CHAIN, and REGISTER_TEMP_OBJECT record the metadata that the engine needs at runtime.
- Execution and error tracking: REGISTER_REQUEST, UNREGISTER_REQUEST, UPDATE_REQUEST_STATUS, UPDATE_OBJ_EXEC_STATUS, UPDATE_OBJ_EXEC_ERRORS, and UPDATE_NUM_OF_OUTPUT_ROWS maintain the lifecycle and diagnostic state of each execution — the update_obj_exec_errors procedure specifically captures and persists error information against an object execution record.
Tables Accessed
FEM_PL_PKG reads and writes a set of FEM tables via APPS synonyms. FEM_PL_OBJECT_DEFS and FEM_OBJECT_DEFINITION_B/TL hold object definition metadata and translations. FEM_PL_OBJECT_EXECUTIONS and FEM_PL_OBJ_EXEC_STEPS store execution instances and their individual steps, which the update procedures modify. FEM_PL_REQUESTS links executions to concurrent request IDs, and FND_CONCURRENT_REQUESTS provides the underlying request status. FEM_PL_CHAINS, FEM_OBJECT_DEPENDENCIES, FEM_PL_TABLES, FEM_PL_TAB_UPDATED_COLS, and FEM_PL_TEMP_OBJECTS support dependency, table-registration, and temporary-object management. FEM_OBJECT_CATALOG_B/TL and FEM_EVENT_ORDER_SEQ provide catalog and sequencing data.
Usage Notes
FEM_PL_PKG is invoked primarily by EDM engine code and EDM-related concurrent programs, and indirectly by the EDM forms-based UI when users create, edit, execute, or delete objects. Customizations and extensions that integrate EDM execution flows should call the API-versioned overloads, respecting the standard FND_API return-status, message-count, and message-data conventions. Because 26 dependent packages call these routines, schema-level changes require careful regression testing. Applications should not update FEM execution tables directly; the update_obj_exec_errors and related procedures are the supported path for recording execution status and errors.