Search Results validate_table

Overview

FEM_SOURCE_DATA_LOADER_PKG is an Oracle EBS Applications (APPS) schema PL/SQL package within the Enterprise Performance Foundation (FEM) / Enterprise Tax, Risk, and Management (ETRM) product family. Its principal business function is to load and stage source data into the FEM data model. In practice, this package drives the extraction, transformation, and population of dimension, hierarchy, ledger, calendar, and dataset information from external or feeder source systems into the FEM repository so that downstream analytics, allocations, and reporting processes can operate against a consistent, validated data set.

The package is categorized under API classification OTHER, indicating it is an internal engine package rather than a formally published public API. It owns the orchestration of the loading process, including parameter validation, dynamic SQL generation, execution, and post-processing, and it registers its own execution so that process control and monitoring records are maintained. The package is validated and currently VALID in the E-Business Suite environment, and it is referenced by FEM_INTF_DIM_VALIDATION_PKG as well as by itself, confirming that it participates in an integrated validation and interface loading chain.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. MAIN serves as the primary entry point and top-level driver for the loading run. VALIDATE_LOADER_PARAMETERS performs upfront checks on the input parameters supplied to the loader. REGISTER_PROCESS_EXECUTION creates or updates the process execution record used for tracking and monitoring the run. POPULATE_XDIM_INFO_TBL populates an internal cross-dimension information table used during loading. SET_MP_CONDITION, PREPARE_DYNAMIC_SQL, PROCESS_DATA, and POST_PROCESS make up the core execution path: they set multi-period or multi-process conditions, build the dynamic SQL statement, process the actual data, and perform cleanup or finalization tasks. GET_PUT_MESSAGES manages the retrieval and output of informational or error messages generated during execution.

The remaining procedures are validation routines invoked before or during the load. VALIDATE_OBJ_DEF and VALIDATE_TABLE verify object definitions and target tables. VALIDATE_EXEC_MODE confirms the requested execution mode is permitted. VALIDATE_LEDGER, VALIDATE_CAL_PERIOD, VALIDATE_DATASET, and VALIDATE_SOURCE_SYSTEM check that the specified ledger, calendar period, dataset, and source system exist and are consistent with the loading context. Parameter lists are not published in the metadata and should not be assumed.

Tables Accessed

The package reads and writes an extensive set of FEM configuration and control tables through APPS synonyms. Calendar validation relies on FEM_CAL_PERIODS_B and FEM_CAL_PERIODS_ATTR. Dataset handling uses FEM_DATASETS_B and FEM_DATASETS_ATTR. Dimension and hierarchy processing references FEM_DIMENSIONS_B, FEM_DIMENSION_GRPS_B, FEM_HIERARCHIES, and FEM_GLOBAL_VS_COMBO_DEFS. Ledger validation uses FEM_LEDGERS_B and FEM_LEDGERS_ATTR. Process orchestration and execution tracking depend on FEM_MP_PROCESS_CTL_T, FEM_MP_OBJ_STEP_METHODS, and FEM_DATA_LOADER_OBJECTS, while object metadata is resolved through FEM_OBJECT_CATALOG_B and FEM_OBJECT_DEFINITION_B. Together these tables supply the parameters the loader needs to build and execute its dynamic SQL safely.

Usage Notes

FEM_SOURCE_DATA_LOADER_PKG is typically invoked indirectly rather than by end users. It is called from concurrent programs and from the FEM interface processing framework, particularly in conjunction with FEM_INTF_DIM_VALIDATION_PKG, which references it during interface dimension validation. Forms-based or scheduled loads that submit FEM source data loading requests ultimately route execution to this package's MAIN routine. Custom code may reference it, but because it is classified as OTHER rather than a published API, direct invocation is not recommended; integrators should use the supported concurrent program and interface entry points so that process registration, messaging, and validation behavior remain consistent.