Search Results validate_dims

Overview

FEM_INTF_DIM_VALIDATION_PKG is an APPS-owned PL/SQL package that belongs to the Oracle Enterprise Data Management / Enterprise Performance Foundation (FEM) interface layer of Oracle E-Business Suite. Its role is to validate and prepare dimension metadata supplied through the ETRM (Enterprise Tax and Reporting Management / Enterprise Performance Foundation) interface tables before that data is consumed by the FEM consolidation and dimension-processing engine. In practice, the package acts as a gatekeeper: it confirms that the parameters passed by a calling process are complete and internally consistent, confirms that the dimension identifiers reference legitimate dimension definitions, enriches the interface rows with derived dimension information, and enforces numeric formatting rules.

The package is classified as "OTHER" rather than as a public API, indicating that it is an internal utility invoked by FEM interface programs rather than a supported integration point for customer extensions. It is not referenced by any other package, so its consumers are concurrent programs, forms, or top-level PL/SQL drivers within the FEM module.

Key Procedures and Functions

Five entry points are documented:

• MAIN — The primary driver of the package. It coordinates the overall validation cycle, invoking the parameter validation, dimension validation, and dimension-information population steps in the required sequence and returning control to the caller with the accumulated status.
• VALIDATE_PARAMS — Checks the input arguments supplied by the calling concurrent program or interface routine. It ensures that required context values (for example dataset, ledger, source system, and calendar period references) are present and well formed before any table processing begins.
• VALIDATE_DIMS — Validates the dimension members and dimension group references against the FEM dimension and dimension-group definitions, confirming that each dimension used by the interface data exists and is enabled for the target application context.
• POPULATE_DIM_INFO — Derives and stores the dimension-related attributes needed downstream, typically by reading the FEM dimension and object-catalog metadata and writing the resolved values into the interface column-mapping structures.
• IS_NUMBER — A helper function that determines whether a supplied value can be interpreted as a numeric literal, used to screen incoming interface values before arithmetic or conversion logic is applied.

Tables Accessed

The package reads and writes a focused set of FEM application tables through APPS synonyms:

• FEM_DATASETS_B, FEM_LEDGERS_B, and FEM_CAL_PERIODS_ATTR — supply the dataset, ledger, and calendar-period context against which interface data is validated.
• FEM_DIMENSION_GRPS_B, FEM_XDIM_DIMENSIONS, FEM_GLOBAL_VS_COMBO_DEFS, and FEM_OBJECT_CATALOG_B — provide the dimension, dimension-group, and global-versus-combination definitions used by VALIDATE_DIMS and POPULATE_DIM_INFO.
• FEM_SOURCE_SYSTEMS_B — identifies the source system that originated the interface rows.
• FEM_INT_COLUMN_MAP — the interface column-mapping table that receives the resolved dimension information produced by POPULATE_DIM_INFO.
• FND_CONCURRENT_REQUESTS — links validation activity to the concurrent request that invoked the package.
• FND_LOG_MESSAGES — receives diagnostic and error messages written during validation.
• DUAL and PLITBLM — the standard single-row query source and the PL/SQL index-by table used internally for value handling.

Usage Notes

FEM_INTF_DIM_VALIDATION_PKG is normally invoked indirectly. It is executed by FEM interface concurrent programs and by internal ETRM processing flows that load dimension metadata into the FEM interface tables, and it is called before the main interface load so that invalid dimension references are rejected early. Because it is classified as OTHER and is referenced by no other package, it is not intended as a customer-facing API; custom code should not depend on its signatures. When diagnosing validation failures, the FND_LOG_MESSAGES rows written by the package and the associated FND_CONCURRENT_REQUESTS entry provide the primary audit trail. The behavior and dependencies described here are consistent across EBS 12.1.1 and 12.2.2, as the object remains VALID in the APPS schema in both releases.