Search Results check_valid_customer

Overview

PA_AGREEMENT_CORE is a core PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It encapsulates the business logic that governs project agreements, funding arrangements, and customer associations within the Oracle Projects (PA) module. An agreement in Oracle Projects represents a contractual or financial arrangement between an operating unit and a customer, and it defines the terms under which revenue is recognized, invoices are raised, and budgets are controlled. The package provides the validation, lookup, and integrity-checking routines that other Oracle Projects components depend upon when agreements are created, modified, or referenced.

The package is classified under the ETRM metadata as an "OTHER" API rather than a formally published public API. This distinction matters: the procedures it exposes are primarily intended for internal consumption by Oracle's own forms, concurrent programs, and dependent packages, not for unrestricted customer extension. Its status is VALID in releases 12.1.1 and 12.2.2, and it depends only on the SYS.STANDARD package, indicating a low-level utility role with no dependency on other APPS packages at compile time.

Key Procedures and Functions

The ETRM documentation records 28 procedures and functions. The documented set divides naturally into validation routines, uniqueness and existence checks, and accessor functions:

• CHECK_VALID_AGREEMENT_ID / CHECK_VALID_AGREEMENT_REF — verify that a supplied agreement identifier or reference is valid before dependent processing proceeds.
• CHECK_VALID_CUSTOMER / CHECK_MULTI_CUSTOMERS — confirm that the customer associated with an agreement is valid, and that multiple-customer scenarios are permitted by the agreement configuration.
• CHECK_VALID_TYPE / CHECK_VALID_TERM_ID — validate the agreement type and the payment terms identifier against their respective setup tables.
• CHECK_UNIQUE_AGREEMENT — enforces uniqueness constraints so that duplicate agreements are not created for the same context.
• CHECK_VALID_OWNED_BY_PERSON_ID — validates the person designated as the agreement owner.
• CHECK_VALID_FUNDING_ID / CHECK_VALID_FUNDING_REF — validate funding references used when agreements are linked to project funding records.
• CHECK_CONTRIBUTION / CHECK_REVENUE_LIMIT / VALIDATE_AGREEMENT_AMOUNT — assess contribution rules, revenue limits, and monetary amounts against the agreement's defined constraints.
• CHECK_BUDGET_TYPE / CHECK_INVOICE_EXISTS / CHECK_ADD_UPDATE — validate budget type associations, determine whether invoicing has already occurred, and gate insert/update operations.
• GET_AGREEMENT_ID / GET_CUSTOMER_ID / GET_PROJECT_ID / GET_TASK_ID — accessor functions returning the identifiers needed by callers.

Tables Accessed

The package reads and writes the principal agreement tables, including PA_AGREEMENTS and its multi-organization view PA_AGREEMENTS_ALL, together with PA_AGREEMENT_TYPES for type validation. Customer linkage is resolved through PA_PROJECT_CUSTOMERS. Funding data is sourced from PA_PROJECT_FUNDINGS and summarized in PA_SUMMARY_PROJECT_FUNDINGS. Invoice existence checks consult PA_DRAFT_INVOICES_ALL, while payment terms are validated against RA_TERMS and currency values against FND_CURRENCIES. DUAL is used for single-row computations.

Usage Notes

PA_AGREEMENT_CORE is invoked indirectly. In ETRM 12.2.2 it is referenced by PA_AGREEMENT_UTILS and PA_FP_CI_IMPLEMENT_PKG, which means agreement maintenance forms, funding and invoicing flows, and the federal projects implementation package all route validation through these routines. Custom code that manipulates agreements should call the supported higher-level APIs in PA_AGREEMENT_UTILS rather than PA_AGREEMENT_CORE directly, since the core package's signatures are not guaranteed as a public interface. Because validation is centralized here, any direct modification of agreement rows that bypasses this package risks introducing data that fails downstream revenue and invoicing processing.