Results for “agreement_currency_code”

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

Overview

OKE_AGREEMENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts (Project Contracts / Project Billing) product family. It is defined as a view over the project agreements entity, with the documented description "View for table PA_AGREEMENTS_ALL." Its primary purpose is to denormalize agreement header data together with customer and party attributes and the functional currency of the operating unit's set of books, so that forms, concurrent programs, and custom reports can query project agreements in a single statement without repeating join logic.

The view is documented as VALID in ETRM 12.2.2 metadata and retains the same definitional shape across the Oracle EBS 12.1.1 and 12.2.2 releases. Because it exposes both the agreement currency and the functional (set of books) currency, it is frequently used in amounts-based reporting, revenue and invoice limit enforcement queries, and inbound/outbound integrations that must reconcile agreement values against the ledger currency. The inclusion of descriptive flexfield columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10) also makes it a common source for extracting client-specific agreement attributes.

Underlying Base Objects

The view is constructed from five documented base objects, joined as follows:

• PA_AGREEMENTS_ALL (SYNONYM) — the driving table, aliased A. Supplies agreement identity, type, number, currency, expiration date, limits flags, ownership, and descriptive flexfield values. The _ALL suffix indicates it is partitioned by operating unit via ORG_ID.
• HZ_CUST_ACCOUNTS (SYNONYM) — aliased P. Joined on P.CUST_ACCOUNT_ID = A.CUSTOMER_ID to resolve the customer account.
• HZ_PARTIES (SYNONYM) — aliased Z. Joined on Z.PARTY_ID = P.PARTY_ID to retrieve the trading party name and number.
• PA_IMPLEMENTATIONS_ALL (SYNONYM) — aliased I. Joined using NVL(A.ORG_ID, -99) = NVL(I.ORG_ID, -99), which supplies the set of books for the operating unit and tolerates a null ORG_ID.
• GL_SETS_OF_BOOKS (VIEW) — aliased G. Joined on I.SET_OF_BOOKS_ID = G.SET_OF_BOOKS_ID to expose the functional currency code (G.CURRENCY_CODE, surfaced as FUNCTIONAL_CURRENCY_CODE).

Because PA_IMPLEMENTATIONS_ALL and GL_SETS_OF_BOOKS participate in the join, agreements for an operating unit lacking a valid implementation record may be excluded from the result set. The NVL(-99) pattern guards against null ORG_ID mismatches but does not guarantee a row when no implementation exists.

Key Columns

• AGREEMENT_ID — primary key identifying the agreement in PA_AGREEMENTS_ALL.
• AGREEMENT_NUM / AGREEMENT_TYPE / DESCRIPTION — user-facing agreement number, classification, and description.
• CUSTOMER_ID, PARTY_ID, PARTY_NAME, PARTY_NUMBER — customer account and the resolved trading party identity.
• AMOUNT — the agreement amount, expressed in the agreement currency.
• FUNCTIONAL_CURRENCY_CODE, AGREEMENT_CURRENCY_CODE — the ledger (set of books) currency and the currency in which the agreement is denominated, respectively.
• OWNED_BY_PERSON_ID — the person (resource) who owns the agreement; this is the column returned by the user's search term "owned_by_person_id" and is sourced directly from PA_AGREEMENTS_ALL. It is commonly joined to PER_ALL_PEOPLE_F or JTF_RS_RESOURCE_EXTNS to resolve the owner's name.
• ORG_ID — operating unit that owns the agreement row (multi-org partitioning).
• OWNING_ORGANIZATION_ID — the organization that owns the agreement, distinct from the operating unit.
• REVENUE_LIMIT_FLAG, INVOICE_LIMIT_FLAG, TEMPLATE_FLAG — Y/N indicators controlling whether revenue and invoice limits apply and whether the record is a template.
• EXPIRATION_DATE, TERM_ID, PM_PRODUCT_CODE, PM_AGREEMENT_REFERENCE — term, expiry, and originating Project Manufacturing / product reference data.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE10 — descriptive flexfield context and segment values.

Common Use Cases and Queries

Typical uses include agreement listings filtered by operating unit, currency reconciliation between agreement and functional currency, limit-flag reporting, and owner-based workload analysis. A representative query to list agreements by owning person, resolved to the resource name, is:

• SELECT v.agreement_num, v.party_name, v.amount, v.agreement_currency_code, v.functional_currency_code, v.expiration_date, v.owned_by_person_id FROM oke_agreements_v v WHERE v.org_id = :p_org_id AND v.owned_by_person_id = :p_person_id ORDER BY v.expiration_date;
• Reporting agreements with limits enabled: SELECT agreement_num, party_name, amount, revenue_limit_flag, invoice_limit_flag FROM oke_agreements_v WHERE revenue_limit_flag = 'Y' OR invoice_limit_flag = 'Y';
• Extracting descriptive flexfield data: SELECT agreement_id, agreement_num, attribute_category, attribute1, attribute2 FROM oke_agreements_v WHERE attribute_category IS NOT NULL;
• Cross-currency comparison: SELECT agreement_num, amount, agreement_currency_code, functional_currency_code FROM oke_agreements_v WHERE agreement_currency_code <> functional_currency_code;

Because the view is a read-only projection with no DML capability, it is suitable for queries only. Reports requiring additional owner or resource attributes should join to the resource tables on OWNED_BY_PERSON_ID; reports requiring operating-unit security should always filter by ORG_ID.