Search Results check_person_visible

Overview

APPS.OTA_TDB_BUS2 is a server-side PL/SQL package within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Oracle Training Administration (OTA) module. Its name follows the OTA_TDB naming convention, where TDB denotes the Training Delivery and Booking subsystem. This package functions as a business-rule validation library: it centralizes a set of reusable "check" routines that validate person, customer, organization, address, enrollment, and booking data before transactional records are committed. The package is classified as OTHER in the ETRM API classification and is documented with status VALID in the APPS schema. Rather than acting as an end-user API itself, OTA_TDB_BUS2 is invoked internally by enrollment self-service pages, booking APIs, and waitlist processing so that a single, consistent validation layer is applied across the training enrollment and booking lifecycle.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions. Their names and purposes are as follows:

• CHECK_PERSON_ADDRESS — verifies that a person's address information is present and valid for enrollment purposes.
• OTHER_BOOKINGS_CLASH — detects scheduling conflicts between a proposed booking and a person's existing bookings.
• OVERDRAFT_EXCEEDED — evaluates whether a booking or enrollment would exceed an allowed enrollment or financial overdraft limit.
• CHECK_PERSON_VISIBLE — confirms that the person is visible to the calling business group or organization.
• CHECK_ENROLLMENT_TYPE — validates that the requested enrollment type is permitted for the learner or event.
• CHECK_ORGANIZATION_DETAILS — verifies required organization attributes used in booking and delegation.
• CHECK_CUSTOMER_DETAILS — validates customer records used when training is booked on behalf of an external customer.
• CHECK_CONTACT_ADDRESS — checks contact address data associated with a customer or delegate.
• CHECK_ORG_BUSINESS_GROUP — confirms that an organization belongs to the expected business group.
• CHECK_SPON_DEL_VALIDITY — validates sponsor and delegate relationships for booked training.
• CHK_OLD_EVENT_CHANGED — determines whether an event's details have changed since a prior booking, supporting rescheduling logic.
• CHECK_COMMITMENT_DATE — verifies commitment date rules applicable to a booking or enrollment.
• CHECK_LOCATION — validates the training location against organization and address data.

Because the metadata documents only routine names and not full signatures, no parameter lists are asserted here; consumers should inspect the package specification for exact arguments.

Tables Accessed

The package references its data primarily through APPS synonyms. HR tables — HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL, and PER_ADDRESSES — supply organization, location, and address context for the organization, location, and address checks. PER_ALL_PEOPLE_F provides the person records validated by CHECK_PERSON_ADDRESS and CHECK_PERSON_VISIBLE. The TCA tables HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_LOCATIONS, HZ_PARTY_SITES, and HZ_RELATIONSHIPS underpin the customer, contact, and relationship validation routines. Booking and event tables — OTA_BOOKING_DEALS, OTA_BOOKING_STATUS_TYPES, OTA_DELEGATE_BOOKINGS, and OTA_EVENTS — provide the booking, delegate, status, and event-change data used by the clash, overdraft, sponsor/delegate, and old-event checks.

Usage Notes

OTA_TDB_BUS2 is referenced by seven dependent packages, including OTA_EL_ENROLL_SS, OTA_ENROLL_IN_TRAINING_SS, OTA_LEARNER_ENROLL_SS, OTA_TRNG_ENROLL_SS, OTA_TDB_BUS, OTA_TDB_WAITLIST_API, and OTA_OM_TDB_WAITLIST_API. These are predominantly self-service enrollment and waitlist processing units. Consequently, the package is typically invoked indirectly through learner self-service enrollment flows, booking and waitlist APIs, and administrator-facing enrollment pages rather than called directly by end users. Customizations that need identical validation behavior should call OTA_TDB_BUS2 rather than reimplementing these business rules, ensuring consistency with seeded OTA enrollment and booking processing in both 12.1.1 and 12.2.2.