Search Results status_change_normal

Overview

APPS.OTA_EVT_BUS is a business-layer PL/SQL package within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 OTA (Oracle Training Administration) module. Its documented object status is VALID, and it is classified under ETRM as an OTHER API. The package encapsulates the core business rules governing event creation, validation, and lifecycle state transitions within the training administration domain. It functions as the validation gatekeeper for event records, ensuring that title uniqueness, scheduling consistency, session placement, enrollment windows, and parent-child event relationships comply with institutional training policies before data is committed to the OTA_EVENTS entity. The package also participates in workflow and concurrent processing flows, since it is referenced by the OTA_EVT_DEL, OTA_EVT_INS, and OTA_EVT_UPD event-level triggers, as well as by OTA_TRB_BUS and other packages — four dependent packages in total according to the ETRM metadata. Because it is owned by APPS and depends on OTA_EVT_SHD (a shadow/audit table for events) and the SYS.STANDARD package, it operates squarely within the standard EBS MULTI-ORG security framework via SET_SECURITY_GROUP_ID.

Key Procedures and Functions

The ETRM repository documents 36 procedures and functions in OTA_EVT_BUS. The following are explicitly named and can be described by their evident intent:

• SET_SECURITY_GROUP_ID — establishes the Oracle Application Object Library security group context, including the operating unit, for the session.
• RETURN_LEGISLATION_CODE — retrieves the applicable legislation code used for date and regulatory validation.
• UNIQUE_EVENT_TITLE and CHECK_TITLE_IS_UNIQUE — enforce that no two active events share the same title.
• RESOURCES_AFFECTED — identifies resources impacted by an event change.
• STATUS_CHANGE_NORMAL — validates that a proposed status transition follows the permitted normal path.
• ENROLLMENT_DATES_EVENT_VALID, CHECK_ENROLLMENT_DATES, ENROLLMENT_AFTER_EVENT_END, ENROLLMENT_DATES_ARE_VALID — govern enrollment window integrity relative to event start and end dates.
• CHECK_EVENT_STATUS — confirms the event is in a status that permits the requested operation.
• GET_PROG_TITLE — returns a program title for display or validation purposes.
• COURSE_DATES_ARE_VALID, CHECK_UPDATED_COURSE_DATES, COURSE_DATES_SPAN_SESSIONS — validate that course-level dates contain and properly span their constituent sessions.
• SESSION_VALID and CHECK_SESSION_WITHIN_COURSE — verify session scheduling falls within the parent course dates.
• CHANGE_TO_WAIT_STATUS — moves a booking or delegate to waitlisted status.
• VALID_PARENT_EVENT and CHECK_PARENT_EVENT_IS_VALID — validate parent-child event relationships.

Tables Accessed

Through APPS synonyms, OTA_EVT_BUS reads and writes the following documented tables, among others:

• OTA_EVENTS — the primary entity for event records; the package validates and may update this table.
• OTA_ACTIVITY_VERSIONS — version history of event activity definitions.
• OTA_ACT_CAT_INCLUSIONS — category inclusion rules for activities.
• OTA_ATTEMPTS and OTA_DELEGATE_BOOKINGS — delegate enrollment and attempt tracking.
• OTA_BOOKING_DEALS and OTA_BOOKING_STATUS_TYPES — booking financial terms and status codes.
• OTA_CATEGORY_USAGES, OTA_CONFERENCES, and OTA_EVALUATIONS — categorization, conference linkage, and evaluation data.
• FND_USER — for user identity/audit context.
• HR_ALL_ORGANIZATION_UNITS, HR_LOCATIONS_ALL, HR_ORGANIZATION_INFORMATION — for organization and location validation.
• OE_ORDER_LINES_ALL — where training events are tied to order lines for commercial bookings.

Usage Notes

OTA_EVT_BUS is not typically invoked directly by end users; it is called by OTA forms, event triggers (OTA_EVT_INS, OTA_EVT_UPD, OTA_EVT_DEL), concurrent programs, and other OTA business packages such as OTA_TRB_BUS. Developers writing custom extensions or interfaces into OTA should call the documented validation routines before inserting or updating OTA_EVENTS to preserve referential and policy integrity. Because it maintains security context through SET_SECURITY_GROUP_ID and depends on OTA_EVT_SHD, custom code should ensure the correct operating unit is initialized prior to invocation.