Search Results ota_cross_charges




Overview
Explore in AI Chat

Overview

OTA_CROSS_CHARGES is a table owned by the OTA schema within the Oracle Learning Management module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the configuration details required to enable internal cross charging, a process by which learning and training costs incurred in Oracle Learning Management are mapped and transferred to the correct accounts in Oracle General Ledger. Specifically, the table maps Chart of Accounts details from Oracle General Ledger to Oracle Human Resources, allowing training expenses to be attributed to the appropriate cost centers, departments, or business units.

The table operates as a configuration and mapping entity. Each record defines a cross-charge rule that governs how a particular type of charge is directed from a source to a destination, using a defined set of GL accounting flexfield mappings. The table is referenced by OTA_HR_GL_FLEX_MAPS, which stores the individual account segment mappings associated with each cross-charge definition.

From a Data Vault modeling perspective, the heuristic classification of OTA_CROSS_CHARGES is hub-leaning. It can reasonably be modeled as a hub, with CROSS_CHARGE_ID serving as the business key candidate, and the descriptive and effective-dating attributes carried in an associated satellite. This classification is a modeling suggestion based on the foreign key structure and the presence of a surrogate identifier rather than a prescriptive directive.

Key Information Stored

Every row in OTA_CROSS_CHARGES is uniquely identified by CROSS_CHARGE_ID, which is enforced through the OTA_CROSS_CHARGES_PK primary key. This is a system-generated surrogate key that has no business meaning and exists solely to provide a stable identifier for referential integrity.

A second unique index, OTA_CROSS_CHARGES_UK, enforces a business-key constraint across BUSINESS_GROUP_ID, TYPE, FROM_TO, START_DATE_ACTIVE, and END_DATE_ACTIVE. This combination prevents duplicate cross-charge definitions within the same business group, for the same charge type, source-to-destination direction, and effective date range.

The most significant columns include:

  • CROSS_CHARGE_ID – Surrogate primary key; the unique identifier for each cross-charge rule.
  • BUSINESS_GROUP_ID – Identifies the HR business group to which the cross-charge rule belongs; a key partitioning attribute for multi-organization deployments.
  • GL_SET_OF_BOOKS_ID – References the Oracle General Ledger set of books used as the accounting context for the charge mapping.
  • TYPE – Defines the category or classification of the cross charge, distinguishing how costs should be routed.
  • FROM_TO – Determines the direction of the charge (source to destination), controlling how the mapping is applied.
  • START_DATE_ACTIVE and END_DATE_ACTIVE – Define the effective date range during which the cross-charge rule is active, supporting date-tracked configuration.
  • OBJECT_VERSION_NUMBER – Supports optimistic locking for concurrency control in the OAF framework.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns capturing who created and last modified each record and when.

Common Use Cases and Queries

The most frequent operational use of this table is retrieving active cross-charge rules for a given business group so that the correct GL mapping can be applied during cost transfer processing. Application logic typically filters on the effective date range and business group.

  • Identify active cross-charge rules: Query by BUSINESS_GROUP_ID and test SYSDATE between START_DATE_ACTIVE and END_DATE_ACTIVE.
  • Detect overlapping or duplicate rules: Self-join on BUSINESS_GROUP_ID, TYPE, and FROM_TO where date ranges overlap, to catch configuration conflicts that would violate the spirit of OTA_CROSS_CHARGES_UK.
  • Audit recently modified configurations: Filter on LAST_UPDATE_DATE to review changes made within a period.
  • Reporting: Join to OTA_HR_GL_FLEX_MAPS on CROSS_CHARGE_ID to produce a full picture of each cross-charge rule and its underlying account segment mappings.

A representative pattern is: SELECT cc.CROSS_CHARGE_ID, cc.TYPE, cc.FROM_TO, cc.START_DATE_ACTIVE, cc.END_DATE_ACTIVE FROM ota.ota_cross_charges cc WHERE cc.business_group_id = :p_bg AND SYSDATE BETWEEN cc.start_date_active AND NVL(cc.end_date_active, SYSDATE + 1) ORDER BY cc.type, cc.from_to;

Related Objects

The most significant related object is OTA_HR_GL_FLEX_MAPS, which holds the foreign key OTA_HR_GL_FLEX_MAPS.CROSS_CHARGE_ID referencing OTA_CROSS_CHARGES.CROSS_CHARGE_ID. This child table stores the individual GL account flexfield segment mappings that realize each cross-charge definition, making the parent-child relationship the core of the cross-charging configuration model.

Additional related objects in the cross-charging and GL integration flow include Oracle General Ledger accounting flexfield structures referenced through GL_SET_OF_BOOKS_ID, HR business group definitions referenced through BUSINESS_GROUP_ID, and Oracle Learning Management cost and finance processing components that consume these mappings. The OTA_HR_GL_FLEX_MAPS table, however, is the only documented foreign-key relationship and should be treated as the primary dependent object when designing queries or extensions against OTA_CROSS_CHARGES.