Search Results fem_ledger

Overview

APPS.FEM_DIM_CAL_UTIL_PKG is a PL/SQL utility package belonging to the Oracle Enterprise Performance Foundation / Enterprise Resource Tracking Management (ETRM) schema, which underpins the analytical dimensions, calendars, and time hierarchies used by Oracle EBS financial consolidation and management reporting modules. The package encapsulates API-driven creation routines for calendar definitions, time group types, and time dimension groups within the FEM (Financial Enterprise Management) data model. Its source header identifies it as a standard APPLDEV-owned header file (fem_dimcal_pkh.pls, version 120.0), consistent with the EBS 12.1.1 and 12.2.2 code lines.

The package defines a standard FND_API-compliant interface: constants for return status (c_success, c_error, c_unexp), boolean flags (c_true, c_false via FND_API.G_TRUE/G_FALSE), a c_api_version of 1.0, and a c_fem_ledger constant identifying the FEM_LEDGER schema construct. Each public procedure follows the EBS API pattern with p_api_version, p_init_msg_list, p_commit, and p_encoded inputs, and x_return_status, x_msg_count, and x_msg_data outputs, allowing callers to participate in the standard message-stack error handling framework.

Key Procedures and Functions

• NEW_CALENDAR — Creates a new calendar definition. It accepts calendar display code, name, source code, period set name, version name and display code, description, and an include-adjustment-period flag, along with optional default calendar period, member, load member, and hierarchy identifiers. It returns the generated x_calendar_id. It is the primary entry point for provisioning a FEM calendar used by time dimension hierarchies.
• NEW_TIME_GROUP_TYPE — Creates a new time group type, capturing the type code, name, description, number of periods in a year, and version name and display code. This categorizes how time groupings (for example, fiscal versus calendar patterns) are structured within the FEM time dimension.
• NEW_TIME_DIMENSION_GROUP — Creates a new time dimension group, tying a time group to a dimension group definition. This is the object most closely associated with the user's search term new_time_dimension_group, and it is the procedure invoked when a new grouping of time members must be persisted for dimensional analysis and reporting.

Tables Accessed

All tables are referenced through APPS synonyms. The package writes to and reads from FEM_CALENDARS_ATTR (calendar attribute definitions), FEM_DIMENSIONS_B (dimension base rows), FEM_DIMENSION_GRPS_B and FEM_DIMENSION_GRPS_B_S (dimension group base and sequence tables), FEM_DIM_ATTRIBUTES_B and FEM_DIM_ATTR_VERSIONS_B with its _S sequence table (attribute versioning for dimensions), FEM_TIME_DIMENSION_GROUP_KEY_S (the surrogate key source for time dimension groups), FEM_TIME_GROUP_TYPES_B and FEM_TIME_GRP_TYPES_ATTR (time group type base and attribute tables), and FEM_XDIM_DIMENSIONS (the extensible dimension definition table). DUAL is used for single-row lookups and sequence validation. The sequence on FEM_TIME_DIMENSION_GROUP_KEY_S is the key generator that populates the identifier returned by NEW_TIME_DIMENSION_GROUP.

Usage Notes

FEM_DIM_CAL_UTIL_PKG is typically invoked from ETRM administrative setup flows, concurrent programs that seed calendar and time dimension metadata, and custom PL/SQL that provisions FEM structures programmatically. The package is referenced by one other FEM package, indicating it acts as a reusable utility layer rather than a top-level application entry point.

Callers should observe the standard API contract: pass p_init_msg_list to initialize the message stack, inspect x_return_status against FND_API.G_RET_STS_SUCCESS/ERROR/UNEXP_ERROR, and only commit when p_commit is set to FND_API.G_TRUE, otherwise commit from the calling transaction. Because the routines insert into dimension and attribute tables with versioning, they should be invoked during controlled setup windows and validated against existing calendar and dimension group definitions before execution.