Search Results create_offering

Overview

The APPS.OTA_OFFERING_API package body is the public application programming interface for the Oracle E-Business Suite Training Administration (OTA) module. It provides a programmatic, server-side mechanism for creating, maintaining, and removing training offerings — the concrete, scheduled instances of a course or learning activity published to a learner audience. In the Oracle Learning Management data model, an offering bridges a defined activity version and the dates, location, delivery mode, pricing, capacity, and enrollment constraints under which that activity is delivered. This package encapsulates the business rules, validation logic, and multi-table inserts required to persist such an offering and its associated child records without requiring callers to manipulate the underlying tables directly.

The package is classified as an API in the ETRM registry, resides in the APPS schema, and is identified as being referenced by two other packages, indicating that it functions as a dependency for higher-level or dependent processing rather than a standalone utility.

Key Procedures and Functions

ETRM documents three public procedures on this package body:

• CREATE_OFFERING — Creates a new training offering. This is the procedure returned when users search for create_offering. It accepts the defining attributes of an offering, including the business group, name, effective date, start and end dates, activity version, owner, delivery mode, language, duration and duration units, learning object, player configuration flags and bitset, minimum, maximum, and internal attendee thresholds, cost and budget figures, currency and price basis, standard price, and a descriptive flexfield attribute category with numbered attribute columns. Most parameters are optional and default to null; a validation-only mode is exposed so that the caller can execute the full business validation without committing data.
• UPDATE_OFFERING — Modifies an existing offering. It applies changes to the same set of offering attributes governed by CREATE_OFFERING, preserving the offering identity and its dependent records while enforcing the same business validations used at creation time.
• DELETE_OFFERING — Removes an offering from the system, applying the deletion and referential-integrity rules that govern offerings and any dependent enrollment, pricing, or scheduling records.

All three procedures are intended to be invoked within the caller's transaction so that the API and any surrounding business logic commit or roll back atomically.

Tables Accessed

The ETRM metadata for this object does not enumerate the underlying tables by name; the package operates against APPS synonyms whose identities are resolved inside the package body. Functionally, CREATE_OFFERING, UPDATE_OFFERING, and DELETE_OFFERING maintain the OTA offering entity and its related detail rows — activity version linkage, scheduling and duration, delivery mode, pricing and currency, and the descriptive flexfield attribute columns passed through the attribute parameters. Because the API performs the multi-table maintenance internally, callers are not required to know the physical table layout and should not write to those tables directly.

Usage Notes

OTA_OFFERING_API is typically invoked from the Oracle Learning Management administrative forms when a training administrator defines or maintains an offering, from concurrent programs that mass-create or synchronize offerings, and from custom PL/SQL that must create offerings as part of an integration or data-conversion routine. Callers should supply p_validate as true during pre-processing to confirm that an offering will pass validation before attempting the real insert, and should always pass a valid business group and effective date so that the API can resolve the correct date-tracked context. Because the API is a documented, supported interface, custom code should call these procedures rather than inserting into the OTA offering tables directly, ensuring that business rules remain intact and that future patches to the package continue to apply.