Results for “ota_tav_bus”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OTA_TAV_BUS is the business-layer PL/SQL package body responsible for validating and managing Activity Version records within the Oracle E-Business Suite Training Administration (OTA) module — historically delivered through Oracle Learning Management and the Enterprise Training Resource Management (ETRM) product family. In OTA, an activity version represents a schedulable or deliverable instance of a training activity, carrying attributes such as start and end dates, duration, duration units, language, user status, superseding-version relationships, and descriptive flexfield (DFF) values. The package encapsulates the row-handler business rules that guard these records against invalid or conflicting data.

The body is catalogued under API classification "OTHER" in the 12.2.2 ETRM documentation, and the source header indicates a build lineage referencing patch set 120.2.12010000.3 (2009). The naming convention follows the standard OTA pattern: OTA_TAV denotes the table/entity (Training Activity Version), while the _BUS suffix identifies the business-rules layer that sits between the row handler / Table Handler (_TH), server-side (_SHD shadow record definitions), and the calling forms or APIs.

Key Procedures and Functions

The documented metadata lists 33 procedures and functions. These fall into several validation and lookup families:

• Date validation: CHECK_START_END_DATES, CHECK_DATES_UPDATE_PLE, CHECK_DATES_UPDATE_TBD, CHECK_DATES_UPDATE_EVT. These verify that version start and end dates are internally consistent and that date changes do not violate constraints imposed by associated price list entries (PLE), test/booking deliverables (TBD), or events (EVT).
• Duration validation: CHECK_DURATION_UNITS and CHECK_DURATION. These confirm that the duration value and its unit of measure are valid and appropriately paired — for example, preventing a numeric duration from being recorded against an incompatible or missing unit code. This logic is central to the check_duration_units reference.
• Existence checks: CHECK_IF_EVT_EXISTS, CHECK_IF_OFF_EXISTS, CHECK_IF_TBD_EXISTS, CHECK_IF_PLE_EXISTS, CHECK_IF_TPM_EXISTS, CHECK_IF_TAV_EXISTS. These determine whether dependent records (events, offerings, test bookings, price list entries, training plan members, or the activity version itself) exist before allowing an operation to proceed.
• Uniqueness and relationship checks: CHECK_UNIQUE_NAME, CHECK_SUPERSEDING_VERSION, CHECK_MIN_MAX_VALUES. These enforce naming uniqueness, validate version-supersession chains, and apply minimum/maximum boundary rules.
• Status and configuration checks: CHECK_USER_STATUS, CHECK_SUCCESS_CRITERIA, CHECK_LANGUAGE.
• Lookup accessors: GET_ACTIVITY_VERSION_ID and GET_ACTIVITY_VERSION_NAME retrieve surrogate identifiers and display names for a given activity version.
• Flexfield validation: the private procedure chk_ddf validates all Developer Descriptive Flexfield values, comparing the incoming record against ota_tav_shd.g_old_rec and raising an application error when the flexfield structure or data values are invalid. It is documented as "Internal Row Handler Use Only" and must be called as the last step of insert_validate and update_validate.

Tables Accessed

The documented tables referenced through APPS synonyms are:

• OTA_ACTIVITY_VERSIONS — the primary entity this package governs; validation and lookup routines read and confirm version attributes.
• OTA_ACTIVITY_DEFINITIONS — the parent activity definition against which a version is created, used by existence and relationship checks.
• OTA_CATEGORY_USAGES — category usage rules influencing validation outcomes.
• OTA_PRICE_LIST_ENTRIES — pricing records whose dates and existence must remain consistent with activity version changes.

Usage Notes

OTA_TAV_BUS is not intended as a public, standalone API. It is invoked indirectly by the OTA Activity Version forms and by the row-handler layer that performs insert_validate and update_validate processing. The package is referenced by five other packages within the OTA schema, confirming its role as a shared validation dependency. Custom code should not call these procedures directly; instead, developers should use the documented public APIs or the forms that drive them. When troubleshooting duration-related errors during activity version maintenance, CHECK_DURATION_UNITS and CHECK_DURATION are the relevant procedures to inspect.