Results for “check_user_status”

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

Overview

The APPS.OTA_TAV_BUS package is a core business logic component within the Oracle E-Business Suite (EBS) Training Administration (OTA) module, residing in the APPS schema. It centralizes the validation rules and business logic that govern Activity Version records (TAV), which represent the time-based, schedulable instances of an activity definition. In Oracle EBS 12.1.1 and 12.2.2, OTA_TAV_BUS acts as the runtime decision layer that is invoked by the activity version insert, update, and delete handlers (OTA_TAV_INS, OTA_TAV_UPD, OTA_TAV_DEL) before any data is committed to the underlying tables. Its documented status is VALID, and it is classified as an OTHER API type rather than a public self-service API, meaning it is primarily intended for internal consumption by the Training Administration forms and dependent packages. By consolidating cross-field validation—date ranges, uniqueness, superseding versions, durations, and multilingual constraints—into a single package, the application enforces consistent data integrity across all entry points.

Key Procedures and Functions

The ETRM documentation catalogues 33 procedures and functions. These may be grouped by purpose:

• Value and range validation: CHECK_MIN_MAX_VALUES enforces minimum and maximum bounds on numeric attributes; CHECK_DURATION and CHECK_DURATION_UNITS validate that a version's duration and its unit of measure are internally consistent and legal.
• Date validation: CHECK_START_END_DATES, CHECK_DATES_UPDATE_PLE, CHECK_DATES_UPDATE_TBD, and CHECK_DATES_UPDATE_EVT verify that start and end dates fall within valid ranges for price list entries, time-based definitions, and events respectively.
• Uniqueness and existence checks: CHECK_UNIQUE_NAME, CHECK_IF_EVT_EXISTS, CHECK_IF_OFF_EXISTS, CHECK_IF_TBD_EXISTS, CHECK_IF_PLE_EXISTS, CHECK_IF_TPM_EXISTS, and CHECK_IF_TAV_EXISTS confirm the presence or absence of related records before proceeding with a transaction.
• Versioning logic: CHECK_SUPERSEDING_VERSION ensures that a superseding version is legitimate and does not create a circular or conflicting hierarchy.
• Lookup retrieval: GET_ACTIVITY_VERSION_ID and GET_ACTIVITY_VERSION_NAME resolve identifiers by name or vice versa.
• Status and criteria: CHECK_USER_STATUS, CHECK_SUCCESS_CRITERIA, and CHECK_LANGUAGE enforce user-defined status rules, completion criteria, and language restrictions.

No parameter lists are documented in the ETRM metadata; the summaries above describe purpose only.

Tables Accessed

Access is performed via APPS synonyms. The package reads and writes:

• OTA_ACTIVITY_VERSIONS: the primary TAV table storing scheduled activity instances.
• OTA_ACTIVITY_DEFINITIONS: the parent definitions from which versions are derived, used for validation and lookups.
• OTA_CATEGORY_USAGES: supports categorisation and applicability checks.
• OTA_PRICE_LIST_ENTRIES: underpins the CHECK_DATES_UPDATE_PLE and CHECK_IF_PLE_EXISTS checks that tie versions to pricing.
• OTA_TAV_SHD: the shadow table referenced as a dependency, supporting multi-row / date-tracked storage.

Usage Notes

OTA_TAV_BUS is normally invoked indirectly. It is referenced by OTA_ACTIVITY_VERSION_SWI and OTA_ACTIVITY_VERSIONS_V, and calls made by the OTA_TAV_INS, OTA_TAV_UPD, and OTA_TAV_DEL handlers drive insert, update, and delete operations through it. Custom extensions that need to validate activity version data should call these documented procedures rather than re-implementing rules. Because it is not a public API, versions 12.1.1 and 12.2.2 rely on it as internal plumbing, and direct calls should be restricted to supported extension points.