Results for “get_funding_rec”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKE_FUNDSOURCE_PVT is the private implementation package body for funding source maintenance within the Oracle E-Business Suite Contracts (OKE) module. Its principal business function is to encapsulate the validation, insert, update, delete, and retrieval logic that governs funding sources associated with contract headers. A funding source represents the financial commitment—a project, agreement, or customer account—against which contract values are allocated and subsequently drawn. Because the object is classified as a PVT package, it is designed to be called only by other packages within the OKE schema rather than directly by external consumers; the public seat for this functionality is OKE_FUNDINGSOURCE_PVT.
The package body was validated in the APPS schema and depends on the standard EBS infrastructure stack (FND_API, FND_GLOBAL, FND_PROFILE, FND_CLIENT_INFO, FND_CURRENCIES, FND_LOOKUP_VALUES, GL_SETS_OF_BOOKS, GL_DAILY_CONVERSION_TYPES). This dependency footprint confirms that the package performs currency conversion, multi-org and client-info resolution, and profile-option lookups as part of its funding-source processing.
Key Procedures and Functions
Six documented subprograms constitute the package interface:
- CREATE_FUNDING — Validates the incoming funding-source attributes and inserts a new funding-source row, preserving the audit and foreign-key relationships required by the contract header.
- UPDATE_FUNDING — Applies changes to an existing funding source, re-running validation rules before committing the modification.
- DELETE_FUNDING — Removes a funding-source record, subject to business-rule checks that prevent deletion when dependent allocations exist.
- FETCH_CREATE_FUNDING — Retrieves the attribute set required to create a funding source, populating the structure that the caller then passes to CREATE_FUNDING; it supports the create-form workflow.
- GET_FUNDING_REC — Returns the full record for a given funding source for display or downstream processing.
- Additional private helper — The remaining documented unit is internal, supporting shared validation and locking logic across the CRUD operations. No parameter lists are documented, and none are inferred here.
Tables Accessed
The package operates against the OKE funding tables and their project-accounting counterparts. OKE_K_FUNDING_SOURCES and its intersection table OKE_K_FUNDING_SOURCES_S hold the funding-source definitions and their header relationships; OKE_K_HEADERS, OKC_K_HEADERS_B, and OKC_K_PARTY_ROLES_B provide contract-header and party-role context. OKE_K_FUND_ALLOCATIONS records the allocations made against each funding source. On the project side, PA_PROJECTS_ALL, PA_AGREEMENTS_ALL, PA_FIN_STRUCTURES_LINKS_V, PA_PROJECT_FUNDINGS, PA_IMPLEMENTATIONS_ALL, and PA_ORGANIZATIONS_PROJECT_V supply project, agreement, and funding-structure information. HR_ALL_ORGANIZATION_UNITS, HZ_CUST_ACCOUNTS, OKX_PARTIES_V, and OKE_POOL_PARTIES resolve owning organizations, customers, and pool parties. FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES are read for currency and rate-type validation, while FND_LOOKUP_VALUES supplies enumerated lookup values. The listing of both OKE_FUNDSOURCE_PVT and OKE_FUNDINGSOURCE_PVT in the dependency view reflects the internal cross-reference between the private and public packages.
Usage Notes
OKE_FUNDSOURCE_PVT is not referenced by any external database object; it is invoked exclusively through the public wrapper OKE_FUNDINGSOURCE_PVT, which in turn is called by the Contracts funding-source forms and by related OKE packages—three of which reference it directly according to the ETRM metadata. Typical invocation points include the Contract Funding Sources form (OKE), allocation processing that calls OKE_ALLOCATION_PVT and OKE_FUNDING_UTIL_PKG, and custom extensions that need to create or amend funding sources programmatically. Because it is a PVT body, customizations should call the public package rather than this object; direct calls risk bypassing validation sequencing and are not supported across 12.1.1 and 12.2.2.