Results for “agreement_num”

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

Overview

SO_AGREEMENTS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, residing in the Order Entry (OE) product family. It presents header-level information for sales agreements — the customer-facing documents that establish negotiated pricing, terms, and invoicing conditions for future orders. Because agreements carry descriptive text that must be translatable across installed languages, Oracle stores the base attributes in a "_B" table and the language-dependent name in a "_TL" table; SO_AGREEMENTS_VL joins the two so that a single query returns a complete, user-language-aware record.

In both 12.1.1 and 12.2.2, the view status is VALID and is a standard component of the OE data model. It is not a transactional table and holds no data of its own; it is a read-optimized presentation layer intended for reporting, concurrent programs, and integration extracts that need agreement headers without performing the translation join manually.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, exposed to APPS through synonyms:

• SO_AGREEMENTS_B — the base table holding non-translatable agreement attributes (identifiers, dates, flags, foreign keys).
• SO_AGREEMENTS_TL — the translation table holding the language-specific agreement name, keyed by AGREEMENT_ID and LANGUAGE.

The view text joins these on B.AGREEMENT_ID = T.AGREEMENT_ID and filters T.LANGUAGE = USERENV('LANG'), so each row is returned only once, in the session's current language. All columns prefixed "B." originate from the base table; only NAME is contributed by the translation table. The ROW_ID column is derived from the base table ROWID, providing a physical row locator for the agreement record.

Key Columns

• AGREEMENT_ID — primary key and join key to both base and translation tables; the anchor for all related lines, pricing, and history.
• AGREEMENT_NUM — the user-visible agreement number used in order entry and customer communication.
• NAME — the translatable agreement name, sourced from SO_AGREEMENTS_TL for the session language.
• AGREEMENT_TYPE_CODE — classifies the agreement (for example, standard pricing, blanket, or promotion), driving downstream pricing behavior.
• CUSTOMER_ID, INVOICE_TO_SITE_USE_ID, INVOICE_CONTACT_ID, AGREEMENT_CONTACT_ID, SALESREP_ID — party and responsibility references identifying the customer, billing site, contacts, and owning sales representative.
• PRICE_LIST_ID, TERM_ID, INVOICING_RULE_ID, ACCOUNTING_RULE_ID — pricing and financial defaults applied to orders released against the agreement.
• START_DATE_ACTIVE, END_DATE_ACTIVE, SIGNATURE_DATE — effective-dating and execution attributes used to determine whether an agreement is currently in force.
• OVERRIDE_IRULE_FLAG, OVERRIDE_ARULE_FLAG — indicate whether invoicing and accounting rules may be overridden on downstream orders.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns for customer-extended agreement attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes agreement validation reports, active-agreement dashboards, integration extracts feeding CRM or pricing engines, and lookups that resolve an agreement number to its internal ID. Because the view already applies the language predicate, no additional translation handling is required.

• Retrieve all active agreements for a customer:

SELECT agreement_id, agreement_num, name, start_date_active, end_date_active
FROM   apps.so_agreements_vl
WHERE  customer_id = :p_customer_id
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE);

• Resolve an agreement number to its identifier and pricing defaults:

SELECT agreement_id, agreement_type_code, price_list_id, term_id
FROM   apps.so_agreements_vl
WHERE  agreement_num = :p_agreement_num;

• List agreements by sales representative with audit information:

SELECT agreement_num, name, salesrep_id, last_update_date, last_updated_by
FROM   apps.so_agreements_vl
WHERE  salesrep_id = :p_salesrep_id
ORDER  BY last_update_date DESC;

When querying outside the EBS session context (for example, from an external tool), the caller must supply an appropriate language value, since USERENV('LANG') resolves to the connected session's language. In all cases, the view should be accessed through the APPS synonym to respect the standard EBS security and grant model.