Results for “ota_mandatory_enr_requests”

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

Overview

The OTA_MANDATORY_ENR_REQUESTS table resides in the OTA schema, which supports the Oracle Learning Management (OLM) module of Oracle E-Business Suite. In releases 12.1.1 and 12.2.2, this table serves as the transaction registry for mandatory enrollment requests — records that capture the intent to enroll a specific learner in a specific learning event when that enrollment is driven by an organizational policy, compliance requirement, or prerequisite rule rather than by voluntary self-registration. Each row represents a discrete enrollment request generated by the system or by an administrator, together with the targeting attributes that identify who is being enrolled and why.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling suggestion. Because it stores descriptive request state and history rather than acting purely as a junction between two hubs, it is best modeled as a satellite attached to the learner/event business keys, rather than as a link table. The single documented foreign key to PER_ORG_STRUCTURE_VERSIONS confirms a dependency on the organization hierarchy versioning structures used to resolve population targeting.

Key Information Stored

The documented physical schema for 12.2.2 lists 12 columns. The most significant are:

• MANDATORY_ENR_REQUEST_ID — the surrogate primary key that uniquely identifies each mandatory enrollment request row.
• REQUESTOR_ID — the person or system principal that initiated the request; supports audit and workload attribution.
• EVENT_ID — the learning event (offering) against which the enrollment is requested; the principal business-key component on the event side.
• PERSON_ID — the learner being targeted for enrollment; the principal business-key component on the learner side.
• ENR_PREREQ_TYPE — the classification of the mandatory trigger, distinguishing prerequisite-driven requests from policy or compliance-driven ones.
• ORGANIZATION_ID — the organization to which the targeted population or learner belongs.
• ORG_STRUCTURE_VERSION_ID — foreign key to PER_ORG_STRUCTURE_VERSIONS; ties the request to the effective-dated hierarchy version used for population resolution.
• JOB_ID and POSITION_ID — the job and position attributes used when selection is defined by role rather than by named individual.
• USERGROUP_ID — the learner group or user group used as an alternative targeting mechanism.
• CONC_PROGRAM_REQUEST_ID — the concurrent program request that generated the rows, enabling traceability back to the batch process.
• CREATION_DATE — the timestamp of request generation, used for aging and audit reporting.

The combination of EVENT_ID and PERSON_ID functions as the strongest business-key candidate, since a mandatory request normally targets one learner for one event; the surrogate key exists primarily for referential stability.

Common Use Cases and Queries

Typical scenarios include compliance reporting — identifying all learners with outstanding mandatory enrollment requests — and troubleshooting why a learner was not enrolled in a required event. A common query pattern joins the request table to person and event tables to resolve names:

SELECT r.MANDATORY_ENR_REQUEST_ID, r.PERSON_ID, r.EVENT_ID,
       r.ENR_PREREQ_TYPE, r.CREATION_DATE
FROM   OTA_MANDATORY_ENR_REQUESTS r
WHERE  r.EVENT_ID = :event_id
ORDER BY r.CREATION_DATE;

Reconciliation queries compare the request rows against actual enrollment records to find requests that were never fulfilled. Grouping by CONC_PROGRAM_REQUEST_ID supports batch-run diagnostics, while grouping by ORG_STRUCTURE_VERSION_ID highlights requests tied to outdated hierarchy versions after an organizational restructure.

Related Objects

The most significant related objects include:

• PER_ORG_STRUCTURE_VERSIONS — referenced through ORG_STRUCTURE_VERSION_ID; supplies the effective-dated hierarchy definition used for population selection.
• OTA_ENROLLMENTS / OTA_DELEGATES — the downstream enrollment records created when a mandatory request is fulfilled.
• OTA_EVENTS — the learning event master, joined on EVENT_ID.
• PER_ALL_PEOPLE_F — resolves PERSON_ID to the learner identity.
• HR_ALL_ORGANIZATION_UNITS — resolves ORGANIZATION_ID to the organization name.
• FND_CONCURRENT_REQUESTS — resolves CONC_PROGRAM_REQUEST_ID for batch traceability.
• PER_JOBS / PER_POSITIONS — resolve JOB_ID and POSITION_ID when role-based targeting is used.