Search Results ota_hr_gl_flex_maps_uk1

Overview

OTA_HR_GL_FLEX_MAPS is a table in the OTA (Learning Management) schema of Oracle E-Business Suite, present in releases 12.1.1 and 12.2.2. It stores the mapping definitions that allow internal cross charging of training costs by translating Oracle General Ledger Chart of Accounts (COA) structures into the value sets and segments understood by Oracle Human Resources. Without this mapping, the HR side of the cross-charge process cannot resolve a valid accounting distribution for an employee or assignment, because HR key flexfield segments do not exist in the same form as GL accounting flexfield segments.

The table is a child of OTA_CROSS_CHARGES, the parent entity that governs the cross-charge setup for a business group. Each row identifies a GL default segment and the HR cost segment onto which it should be mapped. From a heuristic Data Vault perspective — mined from the foreign-key topology rather than declared by Oracle — the object is satellite-leaning: it carries descriptive mapping attributes (segment, segment number, constant, data source) keyed by a surrogate identifier and a foreign key into the parent cross-charge hub. This classification is a modeling suggestion only, not a statement of Oracle's design intent.

Key Information Stored

The documented schema exposes thirteen columns. The most significant are:

• GL_DEFAULT_SEGMENT_ID — the surrogate primary key of the row, enforced by OTA_HR_GL_FLEX_MAPS_PK. Despite its name it acts as the technical identifier for the mapping record rather than as a reference to a GL segment.
• CROSS_CHARGE_ID — foreign key to OTA_CROSS_CHARGES, tying the mapping to a specific cross-charge definition. Part of the business-key candidate.
• SEGMENT — the segment or value-set context being mapped within the cross-charge definition. Also part of the business-key candidate.
• SEGMENT_NUM — the ordinal position of the segment, used to preserve the ordering of the COA structure. Also part of the business-key candidate.
• HR_DATA_SOURCE — indicates where the HR-side value is sourced (for example, from an element, a constant, or a derived HR value).
• CONSTANT — a literal value supplied when the mapping uses a fixed segment value rather than one derived at runtime.
• HR_COST_SEGMENT — the target HR cost segment that receives the mapped value.
• OBJECT_VERSION_NUMBER — optimistic-locking counter maintained by the OAF/BC4J framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS WHO columns for audit and concurrency.

The unique index OTA_HR_GL_FLEX_MAPS_UK1 on (CROSS_CHARGE_ID, SEGMENT, SEGMENT_NUM) is the true business key: a given cross charge cannot define the same segment position twice.

Common Use Cases and Queries

Typical scenarios include verifying that every cross-charge definition has a complete set of segment mappings before finance runs a cross-charge transfer, and diagnosing failures where HR cannot derive an accounting combination. A representative query lists the mappings for a cross charge in segment order:

• SELECT m.segment, m.segment_num, m.hr_data_source, m.constant, m.hr_cost_segment FROM ota.ota_hr_gl_flex_maps m WHERE m.cross_charge_id = :p_cross_charge_id ORDER BY m.segment_num;
• Completeness check: count distinct SEGMENT_NUM values per CROSS_CHARGE_ID and compare against the expected number of segments in the chart of accounts.
• Joining to OTA_CROSS_CHARGES to report which business groups are configured for internal cross charging and with which constants.
• Audit reporting on CREATED_BY and LAST_UPDATE_DATE to trace who altered a mapping and when, useful during period-close reconciliation.

Because GL_DEFAULT_SEGMENT_ID is the surrogate key and not a looked-up GL identifier, queries that filter on it should treat it as an internal row identifier; business filtering is more reliably performed on CROSS_CHARGE_ID with SEGMENT and SEGMENT_NUM.

Related Objects

• OTA_CROSS_CHARGES — the parent table; joined on OTA_HR_GL_FLEX_MAPS.CROSS_CHARGE_ID = OTA_CROSS_CHARGES.CROSS_CHARGE_ID. This is the only documented foreign key.
• OTA_CROSS_CHARGE_ITEMS and related cross-charge detail tables — define which elements and amounts participate in the cross charge that this mapping serves.
• HR cost key flexfield structures (HR cost allocation information) — consume the HR_COST_SEGMENT and HR_DATA_SOURCE values at runtime.
• GL accounting key flexfield definitions — supply the COA segment context that this table maps into HR terms.
• OTA_CROSS_CHARGE_ACTUALS (and equivalent transfer/actual tables) — hold the results of cross-charge processing and depend on the mappings being complete.
• Cross-Charge Setup UI in OTA — the OAF-based maintenance pages that insert, update, and validate rows in this table.

Oracle ETRM documentation for this object is limited to the structural facts above; application logic that consumes HR_DATA_SOURCE and CONSTANT should be confirmed against the shipped OTA package code for the target release.