Results for “ota_bulk_enr_req_members”

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

Overview

The OTA_BULK_ENR_REQ_MEMBERS table is a core staging and transactional object within the Oracle E-Business Suite Learning Management (OTA) module. It stores the individual learner records associated with a bulk enrollment request. When an administrator initiates a bulk enrollment action to place multiple learners into a Class, Learning Path, or Learning Certification, the parent request is recorded in the bulk enrollment request header, and each targeted learner is captured as a row in OTA_BULK_ENR_REQ_MEMBERS. This table therefore acts as the line-level detail of the bulk enrollment process, holding the identity of each requested learner together with the processing status and any diagnostic feedback generated during enrollment.

The object operates within the OTA schema and is classified as VALID in ETRM 12.2.2, containing 14 documented columns. From a Data Vault modeling perspective, the heuristic classification for this table is standalone, suggesting it can be modeled as an independent link or transactional entity rather than a dependent satellite. Its role is chiefly operational: it records the outcome of each enrollment attempt and supports both real-time processing and post-process reporting and reconciliation.

Key Information Stored

Each row represents a single learner within a bulk enrollment request. The most significant columns include:

• BULK_ENR_REQUEST_ID — Identifies the parent bulk enrollment request; forms part of the composite business key.
• PERSON_ID — The learner (person) selected for enrollment; completes the composite business key.
• ASSIGNMENT_ID — The learner's assignment context at the time of enrollment, used to determine eligibility and organizational placement.
• ENROLLMENT_STATUS — The outcome state of the individual enrollment attempt (for example, successful, pending, or failed).
• ERROR_MESSAGE — Diagnostic text explaining why an enrollment could not be completed.
• BOOKING_ID — Links the member row to the resultant booking record upon successful enrollment.
• MBR_BG_ID — Reference to the member background/group association used during processing.
• PERSON_ACTION_ID — The person action resulting from the enrollment; uniquely enforced by the index OTA_BULK_ENR_REQ_MEMBERS_U1.
• ACTION_STATUS_CD — The status code of the associated person action.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking row provenance and change history.

The surrogate-style uniqueness of the row is anchored by the composite unique index OTA_BULK_ENR_REQ_MEMBERS_UK on (BULK_ENR_REQUEST_ID, PERSON_ID), which serves as the primary business-key candidate. A secondary unique index, OTA_BULK_ENR_REQ_MEMBERS_U1, enforces uniqueness on PERSON_ACTION_ID.

Common Use Cases and Queries

Typical scenarios include monitoring the progress of a bulk enrollment request, identifying learners whose enrollments failed, and reconciling successful members against booking records.

To list the members of a specific request with their status:

SELECT PERSON_ID, ENROLLMENT_STATUS, ERROR_MESSAGE
FROM   OTA_BULK_ENR_REQ_MEMBERS
WHERE  BULK_ENR_REQUEST_ID = :request_id;

To isolate failed enrollments requiring remediation:

SELECT PERSON_ID, ERROR_MESSAGE
FROM   OTA_BULK_ENR_REQ_MEMBERS
WHERE  BULK_ENR_REQUEST_ID = :request_id
AND    ENROLLMENT_STATUS = 'FAILED';

Reporting use cases include bulk enrollment success-rate dashboards, audit trails linking persons to actions via PERSON_ACTION_ID, and cross-checking BOOKING_ID values to confirm downstream booking creation.

Related Objects

• Bulk enrollment request header table — The parent record joined on BULK_ENR_REQUEST_ID.
• PER_ALL_PEOPLE_F — Resolves PERSON_ID to the learner's biographical record.
• PER_ALL_ASSIGNMENTS_F — Resolves ASSIGNMENT_ID to assignment and organizational details.
• Booking tables (e.g., OTA_BOOKINGS) — Joined on BOOKING_ID to confirm the resulting enrollment booking.
• Person action tables (e.g., PER_PERSON_ACTIONS) — Linked via PERSON_ACTION_ID to trace workflow outcomes.
• Learning Management enrollment APIs — Consume these member rows to perform actual class, learning path, and certification enrollment.
• OTA_BULK_ENR_REQ_MEMBERS_U1 / _UK indexes — Enforce uniqueness on PERSON_ACTION_ID and the (BULK_ENR_REQUEST_ID, PERSON_ID) pair respectively.