Search Results check_start_end_dates

Overview

OTA_BJS_BUS is the business logic layer of the Booking Justification (BJS) entity within the Oracle EBS Learning Management (OTA) product family. It operates as the middle tier of the standard Oracle Application Object Library (AOL) three-layer architecture, sitting beneath the user-facing OTA_BJS_API package and above the persistence layer represented by the OTA_BKNG_JUSTIFICATIONS_B table. The package is owned by APPS and is classified in the ETRM repository as an OTHER API object rather than a public API, which indicates that it is intended for internal consumption by the generated API tier rather than for direct customer invocation.

Its principal responsibility is to enforce the business rules, validation logic, and row-level security derivation required whenever a booking justification record is inserted, updated, or deleted. The $Header line of the package body identifies the file as otbjsrhi.pkb version 120.0, a naming convention characteristic of Oracle's row-handler (RHI/RHU) code generators, which confirms that the package body was produced and subsequently maintained through the Oracle HRMS generator framework.

Key Procedures and Functions

The ETRM metadata documents five procedures and functions within this package. They are named as follows, and none of their parameter lists are restated here.

• SET_SECURITY_GROUP_ID — Derives and assigns the security group (business group) context for a given booking justification. It queries PER_BUSINESS_GROUPS_PERF joined to OTA_BKNG_JUSTIFICATIONS_B to resolve the security group and legislation code from the business group of the record, and validates that the mandatory booking justification identifier has been supplied.
• RETURN_LEGISLATION_CODE — Returns the legislation code associated with the entity, using the package globals g_legislation_code and g_booking_justification_id to cache the value between calls. This supports legislation-sensitive validation and date formatting behavior elsewhere in the API stack.
• INSERT_VALIDATE — Performs pre-insert validation of the booking justification attributes supplied through the API layer before the row is written to the base table.
• UPDATE_VALIDATE — Performs pre-update validation, ensuring that modified attributes remain consistent with the definition and business rules of the booking justification.
• DELETE_VALIDATE — Performs pre-delete validation, confirming that the record may be removed without violating referential or business constraints.

The package also declares the shared globals g_package, g_legislation_code, and g_booking_justification_id, and uses HR_API.MANDATORY_ARG_ERROR and HR_UTILITY.SET_LOCATION for standard error handling and debug tracing.

Tables Accessed

Two base tables are documented as referenced through APPS synonyms. OTA_BKNG_JUSTIFICATIONS_B is the primary entity table and is the target of the insert, update, and delete validations; it is also read by SET_SECURITY_GROUP_ID to obtain the business group identifier. OTA_DELEGATE_BOOKINGS is consulted to support booking-related validation logic, reflecting the relationship between booking justifications and delegated booking records. The package additionally joins PER_BUSINESS_GROUPS_PERF, the HRMS business group view, during security group resolution.

Usage Notes

OTA_BJS_BUS is normally invoked indirectly. Customer and extension code should call OTA_BJS_API, which in turn delegates to the procedures in this package during the validation phase of insert, update, and delete processing. The ETRM metadata records that the package is referenced by four other packages, consistent with its role as a row-handler dependency rather than a top-level entry point.

Typical invocation paths include the Booking Justification maintenance forms in the Learning Management responsibility, which call the public API on save, and concurrent or batch processes that load or maintain booking justifications. Direct calls into OTA_BJS_BUS are not recommended and are unsupported, because the package does not expose the same argument contract or error-handling guarantees as the API tier. The user query term check_start_end_dates refers to date-range validation logic commonly associated with this entity's booking justification definition; such checks are raised through the validation procedures described above rather than exposed as a standalone documented routine in the ETRM procedure list.