Search Results ota_booking_deals_efc

Overview

The OTA_BOOKING_DEALS_EFC table is a specialized data object within the Oracle E-Business Suite Learning Management (OTA) module, specifically for versions 12.1.1 and 12.2.2. It serves as a historical snapshot table created and populated by the Euro as Functional Currency (EFC) conversion process. This process was a critical, one-time legal and financial requirement for organizations operating in the European Union to convert their transactional data from legacy national currencies to the Euro. The table is an exact structural copy of the core transactional table OTA_BOOKING_DEALS, which stores details of negotiated pricing agreements or deals for training bookings. Its primary role is to preserve the original, pre-conversion booking deal records in their legacy currency values for audit, compliance, and historical reporting purposes after the EFC process has updated the main transactional table.

Key Information Stored

As a mirror of the OTA_BOOKING_DEALS table, OTA_BOOKING_DEALS_EFC contains identical columns capturing all aspects of a booking deal. The metadata explicitly identifies two columns as part of its primary key. The BOOKING_DEAL_ID is the unique identifier linking the record back to the original booking deal. The EFC_ACTION_ID is a crucial column that ties this snapshot record to a specific run of the EFC conversion process, enabling traceability. Other columns would include all transactional details from the source table, such as associated booking header ID, deal type, discount or fee amounts, currency code, and line-level details, all frozen at their pre-Euro conversion values.

Common Use Cases and Queries

The primary use case for this table is regulatory audit and historical analysis. It allows organizations to reconstruct financial reports as they existed prior to the mandatory Euro conversion. A common query pattern involves joining this table with the current OTA_BOOKING_DEALS table on BOOKING_DEAL_ID to perform comparative analysis or validate the conversion. For instance, an auditor might run a discrepancy report. It is critical to note that, as per the provided metadata stating "Not implemented in this database," this table may not be present in all EBS instances; it only exists in databases that underwent the specific EFC process. Therefore, queries should first check for the table's existence.

Related Objects

• OTA_BOOKING_DEALS: The core transactional table from which this EFC snapshot is derived. They are linked by the BOOKING_DEAL_ID.
• EFC_ACTION_ID Column: This key column relates the snapshot to the central EFC process metadata, likely stored in a global EFC logging or control table.
• Other OTA_%_EFC Tables: Similar snapshot tables exist for other core transactional entities in the OTA module (e.g., OTA_BOOKINGS_EFC, OTA_INVOICE_LINES_EFC) populated by the same EFC process, forming a complete historical dataset.
• OTA Learning Management APIs: Business logic for accessing booking deal information would primarily reference the live OTA_BOOKING_DEALS table, not this historical snapshot.