Search Results create_fulfillment

Overview

OKL_FULFILLMENT_PUB is the public API package for the Oracle Lease and Finance Management (OKL) fulfillment subsystem in Oracle E-Business Suite 12.1.1 and 12.2.2. In the leasing lifecycle, fulfillment represents the point at which an approved contract or quote is converted into a deliverable communication — commonly a notification email, letter, or document dispatched to a customer, vendor, or internal party. The package provides the sanctioned, programmatic entry point for creating such fulfillment records without requiring callers to interact directly with the underlying fulfillment tables.

The package follows the standard EBS PL/SQL API architecture: it exposes a thin public wrapper that validates the API version and message list initialization, then delegates the substantive work to a private implementation package, OKL_FULFILLMENT_PVT. This separation allows Oracle to evolve internal processing logic while preserving a stable public contract for customers and integrators.

The header comment dates the source at version 115.11 (April 2004), reflecting the long-stable lineage of the OKL module across both 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The package body documents a single public procedure:

• CREATE_FULFILLMENT — Creates a fulfillment record and initiates the associated fulfillment request. As a PL/SQL API, it accepts the standard EBS API preamble parameters (p_api_version, p_init_msg_list, p_commit) alongside a set of fulfillment-specific inputs. These include the agent and server identifiers that determine the execution context, a content identifier that links the fulfillment to its source template or document, addressing fields such as the from address, subject line, and recipient email, and three parallel PL/SQL collections that carry bind variable names, values, and types for runtime substitution into the fulfillment document. The procedure returns an outgoing request identifier along with the standard return status, message count, and message data columns. Internally it performs a forward call to OKL_FULFILLMENT_PVT.CREATE_FULFILLMENT, inspects the returned status, and raises OKL_API.G_EXCEPTION_ERROR or G_EXCEPTION_UNEXPECTED_ERROR as appropriate so that callers receive consistent error semantics.

Tables Accessed

The provided ETRM metadata does not enumerate base tables for this package, which is consistent with its role as a delegating public wrapper — the actual DML against the OKL fulfillment and request tables occurs inside the private package. Based on the documented parameters, the procedure logically writes an OKL fulfillment record (carrying agent, server, and content identifiers), persists the address and subject details, and registers the resulting concurrent or workflow request whose identifier is returned through x_request_id. The bind variable collections indicate that extracted document content is generated from templates whose placeholders are resolved at runtime rather than stored pre-rendered.

Usage Notes

CREATE_FULFILLMENT is typically invoked from OKL forms events, concurrent programs, workflow activities, or custom PL/SQL extensions that need to dispatch a fulfillment communication as part of a larger business flow — for example, issuing a lease quotation or contract notification after approval. Callers should adhere to EBS API conventions: pass an initialized message list when nested error reporting is required, use p_commit = OKL_API.G_FALSE when the call participates in a larger transaction, verify x_return_status before proceeding, and resolve any outstanding messages through FND_MSG_PUB before reporting failure to the end user.

The package is referenced by five other OKL packages, indicating it is a shared dependency within the module and that changes to its signature would have wide impact.