Search Results invoice_site_use

Overview

APPS.OEFV_ORDER_AGREEMENTS is a reporting view in the Oracle Order Management (ONT) application, registered under FND Design Data as ONT.OEFV_ORDER_AGREEMENTS. It presents pricing and service agreement header information maintained in the Order Management agreements schema, consolidated with related customer, site, currency, and pricing-list attributes for read-only consumption. The view is classified in Oracle E-Business Suite documentation as Oracle Internal Use Only; Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Its status in the APPS schema is documented as VALID, and the view type is described as internal.

The view is most commonly encountered by technical consultants and report developers who need to expose agreement-level attributes — such as agreement number, name, start and end dates, invoicing rules, accounting rules, payment terms, price lists, and invoice-to site details — in custom reports, extracts, and integration feeds. Because the object is not a supported public API, its use should be treated as a read-only convenience over the underlying transaction tables and validated against each specific 12.1.1 or 12.2.2 instance before being embedded in production code.

Underlying Base Objects

The ETRM metadata documents that OEFV_ORDER_AGREEMENTS is defined over the following base objects, referenced through APPS synonyms:

• OE_AGREEMENTS_B — the base table holding agreement header columns, including identifiers and dates.
• OE_AGREEMENTS_TL — the translated table supplying language-dependent attributes such as agreement name.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, and HZ_LOCATIONS — the Trading Community Architecture (TCA) tables supplying invoice-to site, address, and party site details.
• RA_RULES and RA_TERMS_TL — Receivables rule definitions (invoicing and accounting rules) and translated payment terms.
• QP_LIST_HEADERS_TL — translated price list header information from Advanced Pricing.
• OE_BIS_SALESPERSON — a package used to resolve salesperson name information exposed by the view.

The view therefore acts as a join hub, pulling agreement records from Order Management and enriching them with customer, site, terms, rule, and pricing-list descriptions.

Key Columns

• AGREEMENT_NUMBER and AGREEMENT_NAME — the user-defined identifier and descriptive name for the agreement.
• _LA:AGREEMENT_TYPE, _LA:OVERRIDE_ACCOUNTING_RULE, _LA:OVERRIDE_INVOICING_RULE — language-dependent (translated) lookup values exposing the agreement type and the override flags for accounting and invoicing rules.
• START_DATE_CHANGED — a DATE column recorded on the agreement header. It captures the date on which the agreement's start date was most recently changed, making it a useful audit and change-tracking attribute for reconciling agreements whose effective start has been modified after initial entry.
• END_DATE and SIGNATURE_DATE — the agreement's scheduled end date and the date the agreement was signed.
• PURCHASE_ORDER_NUMBER — the customer purchase order reference associated with the agreement.
• INVOICING_RULE_NAME and ACCOUNTING_RULE_NAME — descriptive names of the Receivables rules applied to the agreement.
• INVOICE_TO_SITE_LOCATION, INVOICE_TO_SITE_ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, PROVINCE, COUNTY, COUNTRY — the invoice-to address components sourced from the TCA tables.
• SALESREP_NAME, PAYMENT_TERMS_NAME, PRICE_LIST_NAME — descriptive values for the assigned salesperson, terms, and pricing list.
• Identifier columns — AGREEMENT_ID, CUSTOMER_ID, INVOICE_CONTACT_ID, AGREEMENT_CONTACT_ID, INVOICING_RULE_ID, ACCOUNTING_RULE_ID, INVOICE_TO_ORG_ID, INVOICE_TO_SITE_ID, SALESREP_ID, TERM_ID, PRICE_LIST_ID.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and AGREEMENT_REVISION.

Common Use Cases and Queries

A frequent requirement is identifying agreements whose start date was altered after creation. The START_DATE_CHANGED column supports this directly:

SELECT agreement_number, agreement_name, start_date_changed, end_date, signature_date
FROM apps.oefv_order_agreements
WHERE start_date_changed IS NOT NULL
ORDER BY start_date_changed DESC;

Another common pattern is producing an agreement extract with terms, pricing list, and invoice-to address for reconciliation or audit:

SELECT agreement_number, agreement_name, payment_terms_name, price_list_name,
       invoice_to_site_city, invoice_to_site_country, agreement_revision
FROM apps.oefv_order_agreements
WHERE end_date >= TRUNC(SYSDATE);

Because the view is documented as internal and unsupported for direct access, developers should restrict queries to read-only reporting, avoid placing business logic on it, and confirm column availability in each target instance (12.1.1 versus 12.2.2) before deployment.