Results for “payment_set_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_AGREEMENTS_V is an APPS-owned view in the Oracle E-Business Suite Projects (PA) module. Per its ETRM metadata it is documented as "10SC Only" and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view presents project agreement records — the contractual instruments that define customer funding, revenue limits, invoice limits, and billing terms for project work — enriched with descriptive attributes resolved from related customer, term, person, organization, and operating unit sources. Rather than exposing the raw PA_AGREEMENTS columns alone, the view performs the joins required to render an agreement in a reporting-friendly form: customer name and number, the agreement owner's full name, the payment term name, and the owning organization name.

The view is the primary read interface used by Project Billing and Project Contracts inquiry pages, and by external extracts and integrations that need agreement headers without reproducing the underlying join logic. Because the view text enforces effective-dating and date-range predicates, it returns only currently valid descriptive rows for the owner, the organization, and the operating unit.

Underlying Base Objects

The documented base objects for this view are HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), MO_GLOBAL (package), PA_AGREEMENTS (synonym), PA_CUSTOMERS_V (view), PA_ORGANIZATIONS_PROJECT_V (view), PER_ALL_PEOPLE_F (synonym), and RA_TERMS (synonym). PA_AGREEMENTS is the driving table, supplying all agreement-level attributes. PA_CUSTOMERS_V supplies CUSTOMER_NAME and CUSTOMER_NUMBER, RA_TERMS supplies TERM_NAME, and PER_ALL_PEOPLE_F supplies OWNED_BY_PERSON_NAME. PA_ORGANIZATIONS_PROJECT_V and HR_ORGANIZATION_UNITS resolve the owning organization and operating unit names, with the organization join written as an outer join bounded by an effective date range. HR_GENERAL, HR_SECURITY, and MO_GLOBAL are referenced indirectly, providing the multi-org (operating unit) and security context applied at runtime.

Key Columns

• ROW_ID — the row identifier of the underlying PA_AGREEMENTS row.
• AGREEMENT_ID / AGREEMENT_NUM / AGREEMENT_TYPE — the agreement's primary key, user-facing number, and classification.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER — the customer the agreement is raised against.
• OWNED_BY_PERSON_ID, OWNED_BY_PERSON_NAME — the internal owner of the agreement.
• TERM_ID, TERM_NAME — the payment term attached to the agreement; TERM_NAME is the descriptive value most commonly reported.
• AMOUNT, REVENUE_LIMIT_FLAG, INVOICE_LIMIT_FLAG, ADVANCE_REQUIRED, ADVANCE_AMOUNT — funding controls governing billing against the agreement.
• START_DATE, EXPIRATION_DATE — the agreement's effective window.
• AGREEMENT_CURRENCY_CODE, BILLING_SEQUENCE, PAYMENT_SET_ID, CUSTOMER_ORDER_NUMBER, LINE_OF_ACCOUNT — billing and reference attributes.
• ORG_ID, OWNING_ORGANIZATION_ID — operating unit and owning organization, the latter accompanied by its resolved NAME.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE25 — the DFF/SDF descriptor columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — audit columns.

Common Use Cases and Queries

Typical uses include listing active agreements for a customer, reporting agreements by payment term, and reconciling revenue and invoice limits by operating unit. The following example lists agreements with their customer, term, and owner for a given operating unit:

• SELECT agreement_num, agreement_type, customer_name, term_name, owned_by_person_name, amount, start_date, expiration_date FROM pa_agreements_v WHERE org_id = :p_org_id AND NVL(expiration_date, SYSDATE + 1) > SYSDATE ORDER BY agreement_num;
• SELECT customer_number, customer_name, COUNT(*) FROM pa_agreements_v WHERE revenue_limit_flag = 'Y' GROUP BY customer_number, customer_name;
• SELECT agreement_num, term_name, agreement_currency_code, advance_required, advance_amount FROM pa_agreements_v WHERE agreement_type = :p_type;

Because the view is secured by MO_GLOBAL and HR_SECURITY and applies effective-date logic to the owner and organization joins, queries should filter on ORG_ID and be prepared for a small number of agreements whose owning organization is null (the organization join is outer).