Search Results get_booking_status_type

Overview

OTA_UTILITY is a shared helper package in the Oracle E-Business Suite OTA (Oracle Training Administration / Learning Management) module, owned by the APPS schema. It provides a library of reusable PL/SQL functions and procedures that encapsulate common queries and validation logic used throughout the OTA product family, including offerings, events, enrollments, bookings, and the associated financial (AR/GL) interfaces. The package does not expose a public API in the traditional sense; its classification is OTHER, reflecting its role as an internal utility layer rather than a documented integration interface. It is referenced by 49 other packages, which indicates its broad dependency footprint across OTA processing logic.

Key Procedures and Functions

The documented functions fall into several functional clusters:

• Counting and aggregation helpers — GET_RESOURCE_COUNT, GET_SESSION_COUNT, and GET_CHILD_COUNT return counts (as VARCHAR2) for resources, sessions, and child objects associated with an event or generic object identified by ID and type.
• Attribute and configuration lookups — GET_DELIVERY_METHOD returns the delivery method for an offering; GET_TEST_TIME converts a numeric time value into a displayable string; GET_DEFAULT_COMP_UPD_LEVEL returns the default competency update level for an object; IS_CON_PROG_PERIODIC determines whether a concurrent program is periodic.
• Billing and financial helpers — GET_DESCRIPTION retrieves enrollment and event information for the AR interface; GET_INVOICE_RULE returns the applicable invoice rule; CHECK_INVOICE and GET_BOOKING_STATUS / GET_BOOKING_STATUS_TYPE support booking and invoicing validation.
• Validation routines — CHECK_ENROLLMENT and CHECK_EVENT verify enrollment and event state; OTHER_BOOKINGS_CLASH detects overlapping delegate bookings; CHECK_WF_STATUS queries workflow status; IGNORE_DFF_VALIDATION alters descriptive flexfield validation behavior for a named DFF.
• Descriptive lookups — GET_LOOKUP_MEANING and GET_BG_NAME resolve lookup codes and business group names respectively.

Tables Accessed

The package reads and writes across OTA, HR, FND, and HZ schemas via APPS synonyms:

• OTA_EVENTS, OTA_ATTEMPTS, OTA_LP_ENROLLMENTS, OTA_DELEGATE_BOOKINGS, OTA_BOOKING_STATUS_TYPES — core training event, enrollment, attempt, and booking data, used by the counting, booking-status, and event-check routines.
• PER_ALL_PEOPLE_F, FND_USER — resolve person and application user identity for ownership and security checks.
• FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS — support IS_CON_PROG_PERIODIC and workflow/request-status checks (CHECK_WF_STATUS).
• FND_LOOKUP_VALUES — supplies lookup meanings for GET_LOOKUP_MEANING.
• HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL — resolve business group and location details (GET_BG_NAME and related logic).
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES — support customer/billing role resolution for the AR-facing routines such as GET_DESCRIPTION and GET_INVOICE_RULE.

Usage Notes

OTA_UTILITY is invoked primarily from OTA forms, concurrent programs, and other OTA PL/SQL packages rather than directly by end users. Forms such as event, offering, and enrollment maintenance call its functions to render counts, delivery methods, and booking statuses. Concurrent programs, including AR interface generation, rely on GET_DESCRIPTION and the invoice routines to populate financial records. Custom extensions referencing OTA functionality should call these helpers rather than re-implementing the underlying queries, since the package centralizes OTA business rules and is a widely depended-upon component (49 referencing packages). Because the routines return VARCHAR2 rather than strongly typed values, callers must handle implicit conversion and potential null results carefully. Note that the package is not a formal public API; Oracle may change signatures between releases, and customers should avoid direct dependencies where a supported interface exists.