Search Results fem_time_dimension_group_key_s

Overview

APPS.FEM_DIM_CAL_UTIL_PKG is a utility package body within the Oracle Enterprise Performance Management (EPM) / Enterprise Resource Planning (ERP) Integrator foundation commonly referred to in Oracle E-Business Suite as the Enterprise Tax, Treasury, and Risk-oriented "FEM" (Financial Enterprise Management) schema family. In EBS 12.1.1 and 12.2.2, this package supports the definition and maintenance of analytical calendars and time dimensions used by the FEM engine, which underpins financial consolidation and dimensional data structures. The package encapsulates the low-level business logic required to instantiate new calendar records, associate calendar definitions with a time group type code, and register a time dimension group in the underlying dimension tables. Its header history indicates that the API surface was extended during Bug 4106880 (17-JAN-05), when the New_Calendar, New_Time_Group_Type_Code, and New_Time_Dimension_Group APIs were added. The package is classified as OTHER, reflecting its supporting role rather than a published end-user API. Instrumentation constants reference FND_GLOBAL (RESP_APPL_ID, USER_ID, Login_Id) and the FND logging framework, indicating standardized logging and session attribution.

Key Procedures and Functions

The documented procedures represent the creation side of the FEM calendar and time-dimension model. Parameter lists are not reproduced here; only names and purposes are stated.

• NEW_CALENDAR — Creates a new calendar definition within the FEM calendar attribute structures, establishing the basis for period-to-date and year-to-date time intelligence in consolidation.
• NEW_TIME_GROUP_TYPE — Defines a new time group type code, which classifies how calendars are grouped for processing (e.g., fiscal versus reporting conventions).
• NEW_TIME_DIMENSION_GROUP — Registers a new time dimension group, binding a calendar definition to the time-dimension hierarchy used by FEM_XDIM_DIMENSIONS and associated group tables.

Additional helper logic exists within the body for parameter validation (see exceptions e_bad_param_value and e_null_param_value), package-level constants, and logging variables such as v_session_ledger_id and v_module_log. These support consistent error handling and trace statements across the three public APIs.

Tables Accessed

The package reads and writes a tightly scoped set of FEM dictionary and attribute tables via APPS synonyms:

• FEM_CALENDARS_ATTR — stores calendar attribute definitions created by NEW_CALENDAR.
• FEM_DIMENSIONS_B — the base dimension table for all FEM dimensions, including time.
• FEM_DIMENSION_GRPS_B and FEM_DIMENSION_GRPS_B_S — the base and synonym tables for dimension group definitions.
• FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTR_VERSIONS_B, FEM_DIM_ATTR_VERSIONS_B_S — attribute and version metadata for dimensions.
• FEM_TIME_DIMENSION_GROUP_KEY_S — the key sequence for time dimension groups.
• FEM_TIME_GROUP_TYPES_B and FEM_TIME_GRP_TYPES_ATTR — time group type and attribute storage.
• FEM_XDIM_DIMENSIONS — extended dimension table referenced during group creation.
• DUAL — used for singleton reads and sequence selections.

Usage Notes

In practice, this package is invoked from FEM Setup forms and from other FEM PL/SQL packages (it is referenced by one other package) rather than called directly by end users. Because it performs inserts into core dimension and calendar attribute tables, it is typically executed within the privileges of the APPS schema under a responsibility that owns the FEM setup function. The use of FND_GLOBAL.USER_ID and RESP_APPL_ID ensures that created calendar and time group records carry proper audit attribution. The appearance of default_hierarchy in a search for this object most likely reflects the hierarchy attributes applied when a new time dimension group is registered. Custom code should not bypass these APIs when creating calendars, as they enforce the consistency between FEM_DIMENSIONS_B, the group tables, and the time group type attributes.