Results for “invoice_limit_flag”

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

Overview

PA_AGREEMENTS_ALL is the master table in the Oracle Projects (PA) schema that stores customer contracts serving as the basis for work authorization. Each row represents a distinct agreement between an operating unit and a customer, defining the commercial terms under which project work is funded, billed, and recognized as revenue. Because funding, billing, and revenue recognition in Oracle Projects all trace back to an agreement, this table sits at the center of the Project Billing and Project Costing flows.

From a dimensional modeling perspective, the mined foreign-key structure suggests classifying PA_AGREEMENTS_ALL as a hub. The Agreement ID is a stable business key referenced by many downstream transactional tables, while descriptive attributes (customer, terms, currency, limits, dates) function as satellite context. The table is multi-organization enabled, carrying an ORG_ID column to support operating-unit level security and reporting.

Key Information Stored

The table contains 55 documented columns. The most significant are:

• AGREEMENT_ID – Surrogate primary key (PA_AGREEMENTS_PK). Unique index PA_AGREEMENTS_U1 enforces uniqueness; this is the value propagated to all dependent funding, billing, and revenue tables.
• AGREEMENT_NUM – User-visible agreement number; combined with CUSTOMER_ID, AGREEMENT_TYPE, and ORG_ID it forms the business-key candidate PA_AGREEMENTS_U2.
• CUSTOMER_ID – The customer on the contract; referenced against both RA_CUSTOMERS and HZ_CUST_ACCOUNTS.
• AGREEMENT_TYPE – Classification of the agreement, validated against PA_AGREEMENT_TYPES (for example, standard billing agreements).
• TERM_ID – Payment terms inherited from RA_TERMS_B, controlling invoice due dates and discounting.
• AGREEMENT_CURRENCY_CODE – Currency in which the agreement is denominated; drives conversion during billing and revenue processing.
• AMOUNT and ADVANCE_AMOUNT – Contract value and any prepayment amount associated with the agreement.
• START_DATE and EXPIRATION_DATE – The active window of the agreement; used to validate whether funding is still valid at transaction time.
• REVENUE_LIMIT_FLAG and INVOICE_LIMIT_FLAG – Control whether revenue and invoicing are capped at the funded AMOUNT.
• ADVANCE_REQUIRED – Indicates whether an advance payment must be collected before billing proceeds.
• BILLING_SEQUENCE – Ordering rule for generating invoices across multiple agreements.
• LINE_OF_ACCOUNT and PAYMENT_SET_ID – Link to payment processing and general ledger account derivation.
• OWNED_BY_PERSON_ID – The employee responsible for administering the agreement.
• ORG_ID – Operating unit that owns the agreement, central to MOAC security.

Common Use Cases and Queries

Typical uses include reviewing active funding for a project, reconciling invoiced versus funded amounts, and auditing expired agreements still referenced by draft invoices or revenues.

• Listing active agreements for a customer:
  SELECT agreement_id, agreement_num, agreement_type, amount, expiration_date FROM pa_agreements_all WHERE customer_id = :cust AND org_id = :org;
• Joining to funding to assess remaining contract value:
  SELECT a.agreement_num, a.amount, f.funding_amount FROM pa_agreements_all a JOIN pa_project_fundings f ON f.agreement_id = a.agreement_id WHERE f.project_id = :proj;
• Identifying agreements approaching expiration for renewal reporting, using START_DATE/EXPIRATION_DATE filters.
• Reconciling unbilled revenue by joining PA_DRAFT_REVENUES_ALL and PA_DRAFT_INVOICES_ALL on AGREEMENT_ID.

Related Objects

• PA_PROJECT_FUNDINGS – References PA_AGREEMENTS_ALL.AGREEMENT_ID; defines the funded amounts available to projects.
• PA_BUDGET_VERSIONS – Linked by AGREEMENT_ID; budgets can be tied to specific agreements.
• PA_DRAFT_INVOICES_ALL – References AGREEMENT_ID; invoices generated against the contract.
• PA_DRAFT_REVENUES_ALL – References AGREEMENT_ID; revenue distributions tied to the agreement.
• PA_PROJECT_RETENTIONS and PA_SUMMARY_PROJECT_RETN – Track retention amounts by agreement.
• PA_SUMMARY_PROJECT_FUNDINGS – Summarized funding view keyed by AGREEMENT_ID.
• OKE_K_FUNDING_SOURCES – Links agreements to funding sources in Oracle Project Contracts.
• PA_AGREEMENT_TYPES, HZ_CUST_ACCOUNTS/RA_CUSTOMERS, and RA_TERMS_B – Parent reference tables supplying agreement type, customer, and payment terms.