Search Results update_funding

Overview

OKE_FUNDING_PUB is the public PL/SQL API for the Oracle E-Business Suite Contracts (OKE) funding model. It exposes a versioned, standards-compliant interface through which callers create, maintain, and remove funding source records and their associated funding allocations for a contract or project, and optionally propagate the corresponding agreement records into Oracle Projects (PA). The package follows the Oracle Application Object Library API conventions: it declares G_API_VERSION_NUMBER CONSTANT NUMBER := 1.0, uses G_PKG_NAME and G_PRODUCT_CODE constants for error messaging, and returns status through the standard x_return_status, x_msg_count, and x_msg_data OUT parameters. Because it is classified as a PUB package owned by APPS, it is the sanctioned entry point; the underlying business logic resides in the private packages OKE_FUNDSOURCE_PVT and OKE_ALLOCATION_PVT, whose record and table types the public package re-exposes through SUBTYPE declarations. The source header ($Header: OKEPKFDS.pls 120.0.12000000.1 2007/01/17) indicates the file has been stable across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The package documents seven entry points:

• CREATE_FUNDING — Creates funding records in OKE and, when p_agreement_flag is true, creates the matching agreement records in PA. It accepts a funding input record, an allocation input table, and the agreement type, and returns a funding output record plus an allocation output table.
• UPDATE_FUNDING — Modifies existing funding records in OKE and, subject to the same agreement flag, maintains the corresponding PA agreement records.
• DELETE_FUNDING — Removes funding records, with consistent handling of dependent agreement data.
• ADD_ALLOCATION — Adds a new allocation line against an existing funding source.
• UPDATE_ALLOCATION — Adjusts an existing allocation amount or distribution.
• DELETE_ALLOCATION — Removes an allocation line from a funding source.
• CREATE_PA_OKE_FUNDING — Establishes the PA-side agreement representation for OKE funding, used when the funding/agreement linkage must be built independently.

These procedures are referenced by five other packages, confirming their role as the shared funding interface rather than an application-private implementation.

Tables Accessed

• OKE_K_FUNDING_SOURCES — the funding source header entity; written by CREATE_FUNDING, UPDATE_FUNDING, and DELETE_FUNDING, and read to validate and return funding_rec_out_type.
• OKE_K_FUND_ALLOCATIONS — the allocation detail entity; maintained by CREATE_FUNDING and by the ADD/UPDATE/DELETE_ALLOCATION procedures.
• PA_AGREEMENTS_ALL — the Oracle Projects agreement table; written when the agreement flag is set, linking OKE funding to PA project agreements.
• PLITBLM — the standard Applications message/error table used for token substitution and message retrieval during API error handling.

Usage Notes

OKE_FUNDING_PUB is invoked whenever funding must be established or revised programmatically rather than through the Contracts form. Typical callers are the OKE funding and allocation forms, Oracle Projects integration points, and custom extensions that automate contract funding from external sources. The user's search for "create_funding" indicates the CREATE_FUNDING procedure is the primary interest; it should be called with a valid API version of 1.0, an initialized message list where required, and explicit commit control. Set p_agreement_flag to G_TRUE only when PA agreements are intended, since it triggers writes to PA_AGREEMENTS_ALL. Callers must always inspect x_return_status for OKE_API.G_RET_STS_SUCCESS and drain x_msg_count/x_msg_data before proceeding, and must not update the underlying K-tables directly.