Search Results pa_agreements_all

Overview

The PA_AGREEMENTS_ALL table is a core transactional entity within Oracle E-Business Suite Projects (PA) module, specifically in releases 12.1.1 and 12.2.2. It serves as the master repository for customer contracts that function as the formal basis for work authorization and project funding. As a multi-organization table, denoted by the "_ALL" suffix, it stores records for all operating units, enabling a shared services deployment model. Its primary role is to establish the contractual and financial link between a customer and one or more projects, governing revenue recognition, billing, and funding controls. The integrity of this data is critical for downstream processes in Project Costing, Project Billing, and Project Management.

Key Information Stored

The table's structure captures comprehensive contract details. The primary key is AGREEMENT_ID, a unique system-generated identifier. Essential foreign key columns define critical relationships: CUSTOMER_ID links to the customer in RA_CUSTOMERS or HZ_CUST_ACCOUNTS; AGREEMENT_TYPE references PA_AGREEMENT_TYPES for classification; and TERM_ID connects to RA_TERMS_B for standard payment terms. Other significant columns typically include AGREEMENT_NUMBER (the user-facing contract identifier), START_DATE, END_DATE, CURRENCY_CODE, and descriptive fields like DESCRIPTION. The table also contains standard Oracle EBS audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY, alongside the ORG_ID to segregate data by operating unit.

Common Use Cases and Queries

This table is central to financial and contractual reporting. Common operational queries involve listing all active agreements for a specific customer, validating funding against contract ceilings, and reconciling billed amounts to agreement values. For instance, a report to show agreements and their associated projects would join PA_AGREEMENTS_ALL with PA_PROJECT_FUNDINGS. A critical control query checks total funded amounts against the agreement value to prevent over-funding. Sample SQL to retrieve key agreement details for a specific operating unit is:

• SELECT AGREEMENT_NUMBER, CUSTOMER_ID, START_DATE, END_DATE, DESCRIPTION
• FROM PA.PA_AGREEMENTS_ALL
• WHERE ORG_ID = <operating_unit_id>
• AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);

This table is also fundamental for the generation of draft invoices and revenues, as the agreement defines the billable items and revenue schedules.

Related Objects

As indicated by the foreign key relationships, PA_AGREEMENTS_ALL is a pivotal hub connected to numerous other entities. It is directly referenced by funding and retention tables (PA_PROJECT_FUNDINGS, PA_SUMMARY_PROJECT_FUNDINGS, PA_PROJECT_RETENTIONS, PA_SUMMARY_PROJECT_RETN) and draft transaction tables (PA_DRAFT_INVOICES_ALL, PA_DRAFT_REVENUES_ALL). It also relates to the budget process via PA_BUDGET_VERSIONS. Externally, it integrates with Oracle Contracts (OKE) through OKE_K_FUNDING_SOURCES, where the AGREEMENT_NUMBER provides the link. Key lookup tables include PA_AGREEMENT_TYPES for agreement classification, RA_CUSTOMERS/HZ_CUST_ACCOUNTS for customer data, and RA_TERMS_B for payment terms.