Search Results check_training_plan_costs

Overview

APPS.OTA_TDB_BUS is a business-layer PL/SQL package within the Oracle E-Business Suite Training Administration (OTA) module, part of the Oracle Learning Management (OLM) product family. In EBS 12.1.1 and 12.2.2, the OTA schema stores and processes training event bookings, delegate enrollments, event offerings, resources, and finance lines. OTA_TDB_BUS encapsulates the core business rules governing "training database" (TDB) booking operations, including validation of booking records, enforcement of non-updateable attributes, security group context handling, and various cross-entity checks. It is classified under ETRM as an API classification of OTHER, indicating it is an internal business package rather than a formally published public API, though its procedures are widely reused across the OTA module and by other packages. The header identifies the source file as ottdb01t.pkh, with a revision noting changes made "for eBS." In total, 46 documented procedures and functions constitute the package interface, and it is referenced by 26 other packages, confirming its central role in the training booking subsystem.

Key Procedures and Functions

The package exposes a broad validation and utility surface. Several procedures form the validation backbone: CHK_NON_UPDATEABLE_ARGS ensures that attributes which must not change after creation remain unmodified, raising an application error if any such attribute is altered; CHECK_UNIQUE_BOOKING, CHECK_PERSON, CHECK_ATTENDANCE, CHECK_PLACES, CHECK_RESOURCES, CHECK_INTERNAL_BOOKING, CHECK_FINANCE_LINES, CHECK_TRAINING_PLAN_COSTS, CHECK_FAILURE, and CHECK_TYPE_BUSINESS_GROUP collectively verify booking integrity, delegate eligibility, capacity availability, resource allocation, financial consistency, and business group alignment.

Security and context handling is provided by SET_SECURITY_GROUP_ID, which places the appropriate security_group_id into CLIENT_INFO for the active business group context, and by CHECK_EVENT_BUSINESS_GROUP and CHECK_TYPE_BUSINESS_GROUP, which reconcile event and type definitions against the business group. Informational functions include RETURN_LEGISLATION_CODE, GET_FULL_NAME, BOOKING_STATUS_TYPE, and GET_EVENT_TYPE, the latter returning the event type classification used during booking validation. GET_EVENT_TYPE is frequently the entry point referenced in troubleshooting and integration queries. ASSIGNMENT_OK, EVENT_PLACE_NEEDED, and BOOKING_ID_FOR provide decision support, while OTA-specific lookups such as BOOKING_STATUS_TYPE and BOOKING_ID_FOR support downstream processing.

Tables Accessed

The package reads and writes through APPS synonyms. Booking and event processing relies on OTA_EVENTS, OTA_EVENT_ASSOCIATIONS, OTA_ACTIVITY_VERSIONS, and OTA_OFFERINGS. Booking status history and classification draw on OTA_BOOKING_STATUS_HISTORIES, OTA_BOOKING_STATUS_TYPES, OTA_CATEGORY_USAGES, OTA_DELEGATE_BOOKINGS, and OTA_FINANCE_LINES. Customer and contact validation for delegates and organizations uses HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_ORG_CONTACTS, and HZ_RELATIONSHIPS. Order line data from OE_ORDER_LINES_ALL supports financial and order-linked checks. These accesses underpin the validation logic described above.

Usage Notes

OTA_TDB_BUS is typically invoked from OTA forms (for example, booking and event maintenance screens), concurrent programs, and other PL/SQL packages within the OTA module, rather than directly by end users. Because 26 packages reference it, changes to its logic can ripple across booking workflows. Custom code should call documented procedures only, respect the g_old_rec pre-condition required by CHK_NON_UPDATEABLE_ARGS, and set the security group context via SET_SECURITY_GROUP_ID before performing business group sensitive operations. The presence of GET_EVENT_TYPE among the documented procedures reflects its common use for retrieving event classification during validation and reporting.