Results for “gl_xfr_calendar_mappings”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_XFR_CALENDAR_MAPPINGS is a General Ledger (GL) schema table in Oracle E-Business Suite that stores calendar mappings between an EBS ledger and a corresponding Fusion (Oracle Cloud Financials) ledger. It functions as a translation layer that allows period set names and period types defined in the EBS environment to be reconciled with their equivalents in a Fusion target environment, which is essential for cross-platform data transfer, reconciliation, and migration activities between the two systems.

The object is classified as VALID and owned by the GL schema. It contains 12 documented columns and is classified heuristically as a standalone object under the Data Vault modeling scheme. In Data Vault terms, this suggests the table is best modeled as a standalone reference or lookup construct rather than as a hub, link, or satellite integrated into a broader key hierarchy. There is no documented foreign key relationship tying this table to other GL objects, which reinforces this interpretation. It is a mapping or configuration table used by Oracle's EBS-to-Fusion transfer utilities.

Key Information Stored

The table's primary surrogate key is CALENDAR_MAPPING_ID, which is also the primary key of the constraint GL_XFR_CALENDAR_MAPPINGS_PK. Two unique indexes exist and are documented as business-key candidates: GL_XFR_CALENDAR_MAPPINGS_U1 on CALENDAR_MAPPING_ID and GL_XFR_CALENDAR_MAPPINGS_U2 on NAME. The presence of a unique index on NAME indicates that each mapping definition must carry a distinct, user-recognizable identifier in addition to the surrogate key.

The mapping-defining columns capture the source and target period structures. FROM_PERIOD_SET_NAME and FROM_PERIOD_TYPE describe the EBS-side period set and period type, while TO_PERIOD_SET_NAME and TO_PERIOD_TYPE describe the Fusion-side equivalents. Together these four columns define the actual translation rule. The NAME column provides the descriptive label for the mapping, and DESCRIPTION holds supplementary narrative detail. Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — track who created and last modified each mapping row.

Common Use Cases and Queries

The primary use case is supporting the EBS-to-Fusion transfer process, where a valid period mapping must exist before period balances can be translated. Administrators query this table to verify that a given EBS calendar has a defined Fusion counterpart.

A representative query to list all configured mappings is:

• SELECT calendar_mapping_id, name, from_period_set_name, from_period_type, to_period_set_name, to_period_type FROM gl_xfr_calendar_mappings;
• To find the Fusion target for a specific EBS period set: SELECT to_period_set_name, to_period_type FROM gl_xfr_calendar_mappings WHERE from_period_set_name = :set_name;
• To detect unmapped EBS calendars, compare the distinct period set names in GL_PERIOD_SETS or GL_PERIODS against the values in FROM_PERIOD_SET_NAME to identify gaps.
• For audit reporting, join the CREATED_BY and LAST_UPDATED_BY columns to FND_USER to identify who maintained each mapping.

Related Objects

Because the table is heuristically standalone with no documented foreign keys, related objects are primarily functional references rather than enforced dependencies. The most significant are:

• GL_PERIOD_SETS — matches against FROM_PERIOD_SET_NAME and TO_PERIOD_SET_NAME to validate period set existence.
• GL_PERIODS — provides the period rows governed by the period set and period type referenced in the mapping.
• GL_PERIOD_TYPES — validates the FROM_PERIOD_TYPE and TO_PERIOD_TYPE values.
• GL_LEDGERS — associates ledgers with the period sets referenced in the mapping.
• FND_USER — resolves the CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN audit columns.
• Other GL_XFR_* transfer tables — logically grouped with this table as part of the EBS-to-Fusion migration framework.