Results for “override_arule_flag”

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

Overview

SO_AGREEMENTS_B is the foundational base table that stores customer agreement master records within Oracle E-Business Suite Order Entry (OE). The table resides in the OE schema and is documented as VALID in the ETRM reference for releases 12.1.1 and 12.2.2. A customer agreement in Order Entry represents a negotiated commercial arrangement between the enterprise and a buying party, governing pricing, payment terms, invoicing rules, accounting rules, and the administrative contacts and sales representative responsible for the relationship. Purchase orders released against the agreement reference it through the AGREEMENT_ID foreign key on sales order headers and lines, enabling the pricing engine and order management workflow to apply agreement-specific defaults and validations throughout the order-to-cash lifecycle.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key topology is satellite-leaning. SO_AGREEMENTS_B functions as a descriptive container attached to agreement business keys, with a compact set of intrinsic foreign key relationships to reference data rather than a dense web of transitive dependencies. Modelers building a Data Vault layer should treat the agreement business identifier as the hub key and the attribute set here as the initial satellite payload.

Key Information Stored

The table contains 39 documented columns and is uniquely indexed by SO_AGREEMENTS_B_U1 on AGREEMENT_ID, which also serves as the primary key SO_AGREEMENTS_B_PK. AGREEMENT_ID is the system-generated surrogate key that every downstream order, interface, and receivables row carries as a foreign key; it is not a user-visible business number.

The user-facing identifiers and controlling attributes include:

• AGREEMENT_NUM — the human-readable agreement number used in operational and reporting contexts.
• AGREEMENT_TYPE_CODE — classifies the agreement, driving which defaulting and validation logic applies.
• CUSTOMER_ID — the RA_CUSTOMERS reference identifying the buying party.
• PRICE_LIST_ID — the SO_PRICE_LISTS_B price list associated with the agreement for pricing resolution.
• TERM_ID — the RA_TERMS_B payment term applied to invoices generated under the agreement.
• INVOICING_RULE_ID and ACCOUNTING_RULE_ID — RA_RULES references governing invoice generation and revenue recognition, with OVERRIDE_IRULE_FLAG and OVERRIDE_ARULE_FLAG controlling whether line-level values may deviate.
• INVOICE_TO_SITE_USE_ID — the RA_SITE_USES_ALL invoice-to site use for billing.
• INVOICE_CONTACT_ID and AGREEMENT_CONTACT_ID — contact references for billing and agreement administration.
• SALESREP_ID — the RA_SALESREPS_ALL sales representative credited with the agreement.
• SIGNATURE_DATE, START_DATE_ACTIVE, and END_DATE_ACTIVE — define execution and the active validity window.
• PURCHASE_ORDER_NUM — the customer's PO reference captured for reconciliation.

The standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), a CONTEXT column, and fifteen ATTRIBUTE columns complete the structure for auditability and descriptive flexibility.

Common Use Cases and Queries

Order management reporting frequently joins SO_AGREEMENTS_B to SO_HEADERS_ALL or SO_LINES_ALL on AGREEMENT_ID to attribute booked orders to the governing agreement, and to RA_CUSTOMERS for customer naming. A typical pattern retrieves active agreements for a customer:

• Select AGREEMENT_NUM, AGREEMENT_TYPE_CODE, START_DATE_ACTIVE, and END_DATE_ACTIVE from SO_AGREEMENTS_B where CUSTOMER_ID equals a bind variable and SYSDATE falls between the active dates.
• Join to SO_PRICE_LISTS_B and RA_TERMS_B on PRICE_LIST_ID and TERM_ID respectively to report negotiated pricing and payment terms per customer.
• Outer join to RA_TERMS_B and RA_RULES to identify agreements with missing or overridden invoicing and accounting rules, supporting setup audits.
• Aggregate SO_LINES_ALL by AGREEMENT_ID to measure agreement utilization against negotiated volume commitments.

Because SO_HEADERS_INTERFACE_ALL and SO_LINES_INTERFACE_ALL also carry AGREEMENT_ID, the table is consulted during order import validation to confirm that an interface row references an existing, active agreement.

Related Objects

The most significant related objects are:

• RA_CUSTOMERS — joined via SO_AGREEMENTS_B.CUSTOMER_ID to identify the agreement's customer.
• RA_TERMS_B — joined via TERM_ID for payment terms.
• RA_RULES — two joins, via INVOICING_RULE_ID and ACCOUNTING_RULE_ID, for invoicing and revenue rules.
• RA_SITE_USES_ALL — joined via INVOICE_TO_SITE_USE_ID for the invoice-to site use.
• RA_SALESREPS_ALL — joined via SALESREP_ID for the responsible sales representative.
• SO_PRICE_LISTS_B — joined via PRICE_LIST_ID for the associated price list.
• SO_HEADERS_ALL and SO_LINES_ALL — order headers and lines reference the agreement through AGREEMENT_ID.
• SO_HEADERS_INTERFACE_ALL and SO_LINES_INTERFACE_ALL — interface tables carrying AGREEMENT_ID for import validation.
• RA_CUSTOMER_TRX_ALL — receivables transactions reference the agreement via AGREEMENT_ID, linking billing documents back to the originating agreement.