Search Results pm_agreement_reference




Overview
Explore in AI Chat

Overview

PA_AGREEMENTS_AMG_V is a single-organization (Single-Org) view owned by the APPS schema in Oracle EBS Projects (PA). It presents information about legally binding documents received from customers that serve as the basis of work authorization for projects. In Oracle EBS multi-org architecture, Single-Org views are created by the Multi-Org (MO) security layer to expose only the data belonging to the organization (operating unit) to which the current responsibility is restricted. The suffix _AMG_V is the standard signature applied automatically by the Multi-Org initialization and view generation process, distinguishing these secured views from their multi-org counterparts. Reporting tools, Oracle Forms, and integration routines that must respect organization-level data security query this view rather than the underlying _ALL table, ensuring that session-based org context (ORG_ID) is enforced at query time. The view is marked VALID in the documented metadata and reflects the 12.1.1 / 12.2.2 EBS release perspective.

Underlying Base Objects

According to the documented view text, PA_AGREEMENTS_AMG_V is defined over the PA_AGREEMENTS synonym, which resolves to the PA_AGREEMENTS_ALL base table. PA_AGREEMENTS_ALL is the repository for project agreements — customer contracts, funding documents, and other work authorizations — that drive project funding, revenue limits, and invoice limits. The mechanism operates as follows:

  • The generated view text selects from PA_AGREEMENTS (the synonym) and includes the ORG_ID column, which is the discriminator used by Multi-Org security.
  • At runtime, an implicit organization filter is applied so that only rows whose ORG_ID matches the operating unit of the current responsibility are returned.
  • The view is a read-only projection of the columns listed in the metadata; no additional joins or calculated columns are documented.

Key Columns

The view exposes the full business column set of the agreement record. Notable columns include:

Common Use Cases and Queries

Typical scenarios include reporting on active customer agreements for a specific operating unit, validating funding ceilings for a project, and extracting integration data keyed by PM reference. Because org security is enforced, the view is appropriate for use inside EBS responsibilities and concurrent programs.

Sample query listing agreements by customer and reference:

  • SELECT agreement_id, agreement_num, pm_agreement_reference, customer_id, amount, agreement_currency_code FROM apps.pa_agreements_amg_v WHERE pm_agreement_reference = :p_ref;
  • SELECT a.agreement_num, a.amount, a.revenue_limit_flag, a.invoice_limit_flag FROM apps.pa_agreements_amg_v a WHERE a.expiration_date > SYSDATE ORDER BY a.agreement_num;
  • SELECT agreement_id, pm_product_code, org_id FROM apps.pa_agreements_amg_v WHERE customer_id = :customer_id AND template_flag = 'N';

These queries respect the current operating-unit context. Where cross-organization reporting is required, the multi-org base table PA_AGREEMENTS_ALL must be queried instead, with explicit ORG_ID handling by the calling program.