Search Results execute_create_agreement

Overview

PA_AGREEMENT_PUB is a public PL/SQL API package in the APPS schema that centralizes the creation, maintenance, and funding of project agreements and baseline budgets within Oracle Projects. In Oracle EBS 12.1.1 and 12.2.2, agreements represent the commercial terms—such as contracts, grants, and funding arrangements—under which projects are executed. Because agreements frequently integrate with Oracle Order Management and Oracle Contracts modules, direct manipulation of the underlying tables is unsafe; PA_AGREEMENT_PUB provides a controlled, API-driven interface that enforces the business rules, validation logic, and multi-table consistency required when agreements and their associated funding records are inserted, updated, or deleted.

The package is classified as a PUB (public) API and is therefore intended for external invocation by other Oracle EBS modules and by customer extensions. It depends on FND_API for standard API return-status handling, PA_INTERFACE_UTILS_PUB for interface utilities, PA_AGREEMENTS_ALL as its primary persistence table, and SYS.STANDARD. It is referenced by several Oracle Contracts/Order Management packages, including OKE_AGREEMENT_PVT, OKE_ALLOCATION_PVT, and OKE_FUNDSOURCE_PVT, confirming its role as the integration point between Oracle Projects agreements and the OKE (Contracts) schema.

All agreement operations are transactional and return a standard FND_API.G_RET_STS return status along with message tokens, allowing callers to detect and handle errors programmatically.

Key Procedures and Functions

The documented package exposes eighteen procedures and functions, organized around agreement and funding lifecycle management:

• INIT_AGREEMENT, CLEAR_AGREEMENT — Initialize and clear the internal API record structures used to pass agreement data between the caller and the package, supporting the standard EBS API pattern of initializing a global or private record before performing DML.
• LOAD_AGREEMENT, LOAD_FUNDING — Populate the API’s internal record structures with agreement or funding attribute values, separating the act of loading data from the act of validating or executing it.
• FETCH_FUNDING — Retrieve existing funding records for an agreement or project so that callers can present or process them.
• CREATE_AGREEMENT, UPDATE_AGREEMENT, DELETE_AGREEMENT — Perform the core DML operations on agreements in PA_AGREEMENTS_ALL, including validation and cascade handling.
• ADD_FUNDING, UPDATE_FUNDING, DELETE_FUNDING — Manage individual funding lines associated with an agreement, maintaining the relationship between agreements, projects, and their funding sources.
• CHECK_ADD_FUNDING_OK, CHECK_UPDATE_FUNDING_OK, CHECK_DELETE_FUNDING_OK, CHECK_DELETE_AGREEMENT_OK — Perform validation-only checks, allowing callers to verify whether a proposed funding or deletion action is permitted without committing changes; these are typically used to drive UI behavior or pre-flight validation.
• EXECUTE_CREATE_AGREEMENT, EXECUTE_UPDATE_AGREEMENT — Execute the full create or update logic following prior INIT/LOAD steps, providing a higher-level entry point for callers that have prepared their data.
• CREATE_BASELINE_BUDGET — Create a baseline budget for a project associated with an agreement, linking the funding or contract terms to the project’s budget structure.

Each procedure returns a status and message token via the standard FND_API convention; callers must always check the return status before proceeding.

Tables Accessed

PA_AGREEMENT_PUB reads and writes the following tables (referenced via APPS synonyms):

• PA_AGREEMENTS_ALL — the primary table storing agreement headers, including agreement number, type, amounts, dates, and status.
• PA_PROJECT_FUNDINGS, PA_SUMMARY_PROJECT_FUNDINGS — store detailed and summarized funding allocations tied to agreements and projects; these are the core tables for the ADD/UPDATE/DELETE_FUNDING operations.
• PA_PROJECTS_ALL, PA_TASKS — provide project and task context, ensuring funding is applied to valid project/task combinations.
• PA_BUDGET_VERSIONS — used by CREATE_BASELINE_BUDGET to associate a baseline budget version with the project.
• PA_RESOURCE_LIST_MEMBERS — validates resource list membership for funding and budgeting rules.
• PA_IMPLEMENTATIONS — supplies installation-level configuration and operating unit behavior.
• DUAL, PLITBLM — used for PL/SQL scalar evaluation and PL/SQL table handling respectively.

Usage Notes

PA_AGREEMENT_PUB is invoked primarily by Oracle Contracts and Order Management packages (OKE_AGREEMENT_PVT, OKE_ALLOCATION_PVT, OKE_FUNDSOURCE_PVT) when agreements and funding sources are created or updated from the Contracts UI or related concurrent processes. In Oracle Projects forms, agreement and funding maintenance actions ultimately delegate to this package rather than performing direct DML. Custom code should follow the same pattern: call INIT_AGREEMENT or LOAD_AGREEMENT to populate the API structures, invoke the appropriate CHECK_* procedure for validation, then call CREATE_AGREEMENT, UPDATE_AGREEMENT, or the corresponding EXECUTE_* entry point, committing only on a successful return status. Never update PA_AGREEMENTS_ALL or the funding tables directly, as this bypasses the package’s validation and integration logic and can cause inconsistencies with Contracts and Budgetary Control.