Search Results so_agreements_b




Overview
Explore in AI Chat

Overview

The SO_AGREEMENTS_B table is the core database table for storing master data for customer agreements within Oracle E-Business Suite Order Entry (OE) module. It represents a foundational entity for establishing formal, long-term commercial contracts between a business and its customers. These agreements serve as a central reference point, enabling the automatic application of pre-negotiated business terms—such as pricing, payment schedules, and invoicing rules—to sales orders and transactions. Its role is critical for streamlining order processing, enforcing contractual terms, and maintaining consistency across all customer transactions linked to the agreement.

Key Information Stored

The table's primary key is AGREEMENT_ID, which uniquely identifies each agreement record. As indicated by the foreign key relationships, the table stores essential pointers to other master data entities. Key foreign key columns include CUSTOMER_ID (linking to RA_CUSTOMERS), PRICE_LIST_ID (linking to SO_PRICE_LISTS_B), and SALESREP_ID (linking to RA_SALESREPS_ALL). It also holds references to rule-based terms, such as TERM_ID (RA_TERMS_B), INVOICING_RULE_ID, and ACCOUNTING_RULE_ID (both in RA_RULES). Furthermore, it stores operational details like INVOICE_TO_SITE_USE_ID (RA_SITE_USES_ALL) for the ship-to address and references to specific contacts (AGREEMENT_CONTACT_ID, INVOICE_CONTACT_ID). This structure consolidates the commercial, operational, and financial rules governing a customer relationship into a single record.

Common Use Cases and Queries

A primary use case is validating and reporting on the terms applied to an order. For instance, to identify all sales orders created under a specific agreement with its associated price list, a common query would join SO_HEADERS_ALL to SO_AGREEMENTS_B. Another critical scenario is analyzing agreement utilization, such as listing agreements that have not been used in recent transactions. Support and implementation teams often query this table to diagnose order entry issues related to incorrect term derivation. A sample query pattern is:

  • SELECT sa.agreement_id, sa.customer_id, sa.price_list_id, sh.order_number
  • FROM oe.so_agreements_b sa, oe.so_headers_all sh
  • WHERE sa.agreement_id = sh.agreement_id
  • AND sh.order_date > SYSDATE - 30;

Related Objects

SO_AGREEMENTS_B is a central hub with extensive relationships. It is directly referenced by key transactional and interface tables, including SO_HEADERS_ALL, SO_LINES_ALL, RA_CUSTOMER_TRX_ALL, and their corresponding interface tables (SO_HEADERS_INTERFACE_ALL, SO_LINES_INTERFACE_ALL). This demonstrates its integral role in both order management and receivables transactions. As per the metadata, it draws its attributes from several foundational modules: customers and sites (RA_CUSTOMERS, RA_SITE_USES_ALL), pricing (SO_PRICE_LISTS_B), sales force (RA_SALESREPS_ALL), and financial rules (RA_TERMS_B, RA_RULES). The corresponding TL table (SO_AGREEMENTS_TL) stores translated descriptive data for multilingual implementations.