Search Results insupd_enroll

Overview

APPS.PQP_RIW_ENROLL_WRAPPER is a public PL/SQL wrapper package belonging to the Oracle Learning Management (OLM) module, part of the Oracle E-Business Suite Human Resources family. Its principal responsibility is to provide a controlled, Web-ADI-facing entry point for the creation and update of training enrollments — termed bookings — that originate outside the standard OLM forms. The package header carries the source stamp pqpriwenwr.pkh 120.0.12010000.3, indicating an Application Technology Group incarnation delivered during the 12.1.1 development cycle and carried forward into 12.2.2.

The header comment is explicit about the design intent: the package exists so that the Web-ADI spreadsheet interface can create or update an enrollment in Oracle Learning Management from data entered directly in a spreadsheet or downloaded from an external XML source. Rather than embedding business logic in the spreadsheet layer, Oracle publishes this wrapper so that inbound bulk data is validated and persisted through supported APIs. The API classification in ETRM is recorded as OTHER, reflecting that it is an integration surface rather than a purely internal helper.

Key Procedures and Functions

Three documented entry points are exposed by the package:

• INSUPD_ENROLL — The primary insert-or-update procedure. Despite its name, it is a single procedure (not a function) that accepts a null-safe p_effective_date and a large optional parameter set covering booking identity, delegate and contact details, business group, event, customer and third-party references, booking status and status-change dates, number of places, priority, comments, attendance result, language, source of booking, and special instructions. The wrapper decides internally whether the row represents a new booking or an amendment to an existing one, based on the supplied booking identifier and object version number. It is the object that a search for the string "insupd_enroll" resolves to.
• CREATE_DELEGATE_BOOKING — Creates a delegate booking record for an enrollment, encapsulating the delegate-level attributes that sit beneath the parent booking. It exists to separate delegate placement from the broader booking lifecycle handled by INSUPD_ENROLL.
• UPDATE_DELEGATE_BOOKING — The complementary procedure that modifies an existing delegate booking, supporting corrections and status transitions without forcing a full re-insert.

The split between the general enrollment procedure and the two delegate-specific procedures mirrors the OLM data model, in which a booking can carry one or more delegates whose individual data is held separately.

Tables Accessed

ETRM documents three base tables reached through APPS synonyms:

• OTA_DELEGATE_BOOKINGS — The core OLM table for delegate-level booking rows. It is the principal write target for CREATE_DELEGATE_BOOKING and UPDATE_DELEGATE_BOOKING and is also touched by INSUPD_ENROLL when delegate details accompany the booking payload.
• PER_PERSON_TYPES — Used to validate and resolve person type information for the delegate, ensuring the individual is correctly classified within the HR person model before the booking is committed.
• BNE_INTERFACE_COLS_B — The Web-ADI interface column definition table, consulted to map inbound spreadsheet or XML columns to their target attributes. This reference is the strongest evidence that the package is purpose-built for the Web-ADI upload path rather than for interactive form use.

Usage Notes

PQP_RIW_ENROLL_WRAPPER is invoked programmatically. Its documented caller is the Web-ADI spreadsheet, which invokes INSUPD_ENROLL to push enrollment rows into OLM in bulk. It is also a natural target for custom PL/SQL integration code that loads training bookings from external systems such as an XML feed, a learning management front end, or a third-party training provider. ETRM records zero other packages referencing it, so it should be treated as a leaf-level integration API rather than a shared internal utility. Because the parameters carry defaults throughout, callers may supply only the attributes relevant to their scenario; bookkeeping fields such as p_object_version_number should be carried accurately to avoid unintended overwrites. The package is not designed to be called from an OLM form directly — standard form navigation uses the underlying OLM business logic instead. In 12.1.1 and 12.2.2 the file location and API surface are unchanged, so existing customizations that reference APPS.PQP_RIW_ENROLL_WRAPPER remain valid across the upgrade boundary.