Search Results check_add_funding_ok

Overview

PA_AGREEMENT_PVT is a private (PVT) PL/SQL package body owned by APPS that encapsulates the core business logic supporting project agreement and project funding maintenance in Oracle Projects. It is not a public API; rather, it functions as the internal validation and utility layer invoked by public APIs, forms, and interface processes that create, update, and delete agreement and funding records. The package centralizes the referential and validation rules that govern how agreements and their associated funding records are constructed, checked, and persisted.

The package opens with two package-level constants that anchor its behavior. G_PKG_NAME holds the package name ('PA_AGREEMENT_PVT') and is used to prefix error message text. G_AGREEMENT_CODE is a VARCHAR2(9) constant set to 'AGREEMENT' and is used to identify the agreement entity when raising or formatting error messages. Additional global constants capture the runtime FND_GLOBAL user and login identifiers for audit and concurrency purposes. The body also declares a header revision line, confirming that this is the pl/sql source stored in the APPS schema for Oracle E-Business Suite 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes fifteen documented subprograms, organized around four functional concerns: reference resolution, agreement validation, funding validation, and generic checks.

• CONVERT_AG_REF_TO_ID — Converts an agreement reference into an agreement identifier. The header comment documents the source of the logic and shows that it depends on pa_agreement_pvt.fetch_agreement_id and pa_interface_utils_pub.map_new_amg_msg for mapping error text.
• CONVERT_FU_REF_TO_ID — Performs the analogous conversion for funding references into funding identifiers.
• FETCH_AGREEMENT_ID and FETCH_FUNDING_ID — Retrieve the surrogate primary keys for agreements and funding records respectively, serving as the lookup primitives used by the convert procedures.
• CHECK_CREATE_AGREEMENT_OK, CHECK_UPDATE_AGREEMENT_OK, CHECK_DELETE_AGREEMENT_OK — Perform the applicable business-rule checks before an agreement is inserted, modified, or removed.
• CHECK_FUNDING_CATEGORY — Validates the funding category associated with a funding record.
• CHECK_ADD_FUNDING_OK, CHECK_UPDATE_FUNDING_OK, CHECK_DELETE_FUNDING_OK — Mirror the agreement checks for funding records.
• VALIDATE_FLEX_FIELDS — Validates descriptive flexfield and key flexfield values supplied for the agreement or funding entity.
• CHECK_YES_NO — Confirms that a Y/N indicator carries a valid value.
• CHECK_ADD_UPDATE — Applies shared checks common to add and update operations.
• VALIDATE_FUNDING_AMT — Validates the amount entered against a funding record.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• PA_AGREEMENTS_ALL — The primary agreement table; used by the convert and fetch routines to resolve agreement identifiers and by the agreement create, update, and delete checks.
• PA_PROJECT_FUNDINGS — Stores funding records; used by the funding convert, fetch, and validation logic.
• PA_PROJECTS_ALL — Used to confirm that an agreement or funding record relates to a valid project.
• PA_PROJECT_TYPES_ALL — Used to apply project-type-specific rules during validation.
• PA_TASKS — Used when funding or agreement validation requires task-level context.

Usage Notes

PA_AGREEMENT_PVT is classified as a private API and is not intended for direct customer invocation. It is typically called by the public Oracle Projects APIs (such as the agreement and funding public APIs) from Oracle Projects forms, by external interface programs that load agreement and funding data, and by custom extensions that have been granted execute privilege on the APPS package. Because it is a PVT package, Oracle does not guarantee backward compatibility of its signatures, and custom code should prefer the corresponding public API wrappers. The G_AGREEMENT_CODE constant ensures that any error raised within the package is attributed to the AGREEMENT entity in the message stack when surfaced through FND_MSG_PUB.