Search Results check_dates_conflict

Overview

OTA_TBD_API is a PL/SQL API package in the APPS schema that supports Oracle E-Bookings/Deals functionality within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. The package belongs to the Oracle Training Administration (OTA) product family, which is delivered as part of Oracle Learning Management. OTA_TBD_API provides the programmatic layer through which booking deal records and their associated finance lines are created, validated, and maintained. It encapsulates the low-level business rules governing date conflicts, approver validation, and financial treatment of deals, so that forms, Java-based OAF pages, and concurrent processes can transact against the booking deals schema without embedding raw SQL.

The object is classified as an API in the E-TRM (E-Business Suite Technical Reference Manual) and holds a VALID status in the APPS schema. It depends on APPS.HR_API and on the OTA_BOOKING_DEALS table, and it is itself referenced by the OTA_BOOKING_DEALS_V and OTA_FINANCE_LINES_V views as well as by OTA_TDB_BUS2 and the OTFV_ENROLLMENT_AGREEMENTS and OTFV_FINANCE_LINES objects. Thirteen documented procedures and functions are exposed by the package.

Key Procedures and Functions

The documented callable units cover the full lifecycle of booking deal and finance line maintenance:

• RETURN_API_DML_STATUS — Reports whether the most recent insert, update, or delete performed through the package succeeded, allowing callers to branch on the outcome.
• TFL_PURCHASED, TFL_BALANCE, TFL_FLAG — Finance line (TFL) helpers that determine the purchased value of the deal, the outstanding balance, and set or test an associated flag.
• CHECK_DATES_CONFLICT — Validates that the booking deal's date range does not overlap with existing conflicting records.
• CHECK_APPROVER — Verifies that the designated approver is valid for the deal.
• LCK — Acquires a locking operation against the target deal row to serialize concurrent updates.
• INS, UPD, DEL — The core insert, update, and delete procedures that persist booking deal data and cascade the corresponding finance line changes.

Tables Accessed

The package reads and writes the following tables through APPS synonyms: OTA_BOOKING_DEALS and OTA_BOOKING_DEALS_S (the base and secondary deal tables), OTA_ACTIVITY_VERSIONS, OTA_CATEGORY_USAGES, OTA_DELEGATE_BOOKINGS, OTA_EVENTS, OTA_FINANCE_LINES, OTA_PRICE_LISTS, and ALL_CONSTRAINTS. OTA_BOOKING_DEALS and its _S sibling hold the deal header and its translated/secondary attributes; OTA_FINANCE_LINES holds the financial detail rows that the TFL procedures compute against. OTA_EVENTS, OTA_ACTIVITY_VERSIONS, OTA_CATEGORY_USAGES, OTA_DELEGATE_BOOKINGS, and OTA_PRICE_LISTS supply the pricing, category, and delegate context needed to evaluate a deal, while ALL_CONSTRAINTS is queried to confirm relational integrity and uniqueness rules before DML is committed.

Usage Notes

OTA_TBD_API is not typically invoked directly by end users. It is called from the Oracle Learning Management booking deals form and from the OTA_TDB_BUS2 business-layer package, both of which delegate validation and persistence to this API. The OTA_BOOKING_DEALS_V and OTA_FINANCE_LINES_V views, plus the OTFV_ENROLLMENT_AGREEMENTS and OTFV_FINANCE_LINES objects, reference this package, meaning changes to its documented behavior can propagate to those dependent interfaces. Customizations should respect the HR_API dependency for approver and person validation, invoke LCK before UPD within concurrent logic, and always inspect RETURN_API_DML_STATUS. The package is present and valid in both 12.1.1 and 12.2.2; because 12.2.x uses the same APPS schema architecture and online patching, no separate edition of OTA_TBD_API is required between the two releases.