Search Results fem_pl_object_executions




Overview
Explore in AI Chat

Overview

The APPS.FEM_INTG_PL_PKG package body is a component of the Oracle Enterprise Tax, Risk, and Management (ETRM) application family, specifically within the Profitability and Cost Management / Financial Management integration layer. The package encapsulates business rules governing the lifecycle of Profitability (PL) object definitions and the execution of Profitability engines. It acts as a bridge between the ETRM integration rules stored in FEM_INTG_DIM_RULES and the runtime execution records captured in FEM_PL_OBJECT_EXECUTIONS, working closely with the core engines in FEM_ENGINES_PKG and the orchestration logic in FEM_PL_PKG. Its primary responsibilities include validating whether dimension rules have been run for a given object, guarding against deletion of an object definition while dependent related data or locks exist, checking whether result data meets effective-date inclusion requirements, and coordinating process-level logging and message propagation through the standard Oracle EBS logging and messaging infrastructure (FND_LOG and FND_MSG_PUB).

Key Procedures and Functions

The package body exposes six documented procedures and functions:

  • OBJ_DEF_DATA_EDIT_LOCK_EXISTS — Determines whether a lock exists that prevents the editing of an object definition's data. This guard is used to protect object definitions from concurrent modification.
  • CAN_DELETE_OBJECT_DEF — Evaluates whether a Profitability object definition may be safely deleted, typically by checking for dependent related data or in-progress activity that would otherwise leave orphaned records.
  • DIMENSION_RULES_HAVE_BEEN_RUN — Verifies whether the dimension integration rules for an object have already been executed, ensuring rule processing sequencing is respected before subsequent processing steps.
  • EFFECTIVE_DATE_INCL_RSLT_DATA — Checks whether result data falls within the required effective-date inclusion window, controlling whether data is considered valid for downstream processing.
  • REGISTER_PROCESS_EXECUTION — Records a new process execution instance, inserting the execution metadata necessary to track a Profitability processing run.
  • FINAL_PROCESS_LOGGING — Performs end-of-process logging, capturing completion status and diagnostic information for the integration workflow.

Tables Accessed

Two application tables are referenced through APPS synonyms:

  • FEM_INTG_DIM_RULES — Read to determine the integration dimension rules configured for a Profitability object, supporting the DIMENSION_RULES_HAVE_BEEN_RUN validation.
  • FEM_PL_OBJECT_EXECUTIONS — This is the operational backbone of the package, capturing execution records registered by REGISTER_PROCESS_EXECUTION and consulted when validating edit locks, deletion eligibility, and final logging. The search term fem_pl_object_executions maps directly to this table.

Usage Notes

FEM_INTG_PL_PKG is invoked indirectly by the Profitability processing stack rather than by end users directly. It is referenced by three other database objects and is not referenced externally beyond those consumers, indicating it is a supporting utility layer. The package is typically called from the Profitability engine orchestration flows built on FEM_PL_PKG and FEM_ENGINES_PKG, and from ETRM concurrent programs that execute Profitability calculations and integration rule runs. Its logging calls into FND_LOG and FND_MSG_PUB integrate its activity with standard Oracle EBS diagnostics, allowing administrators to trace execution from the concurrent manager request log. Custom code should not call these procedures directly without understanding the parent engine state, since the guard procedures enforce invariants that the orchestration layer relies upon.