Search Results oe_agreements_b

Overview

The OE_AGREEMENTS_B table is a core data structure within the Oracle E-Business Suite (EBS) Advanced Pricing module (QP). It serves as the primary repository for all pricing agreement definitions. In the context of Oracle EBS 12.1.1 and 12.2.2, a pricing agreement is a contractual arrangement that defines specific pricing terms, such as discounts, price lists, and invoicing rules, for a particular customer or group of customers. This table is fundamental to the order management and pricing engines, as it provides the reference point against which sales orders are validated and priced when an agreement is applied, ensuring contractual pricing compliance is automatically enforced during order entry.

Key Information Stored

The table's primary key is the AGREEMENT_ID, a unique system-generated identifier for each agreement. As indicated by the foreign key relationships, the table stores critical references that define the agreement's commercial terms. The PRICE_LIST_ID links to QP_LIST_HEADERS_B, specifying the master price list applicable under the agreement. The SALESREP_ID references RA_SALESREPS_ALL, associating a sales representative with the agreement. Furthermore, the table holds INVOICING_RULE_ID and ACCOUNTING_RULE_ID, both linking to RA_RULES, which govern the revenue recognition and invoicing schedules for transactions under this agreement. While the provided metadata does not list all columns, typical agreement attributes stored would include agreement number, name, effective dates (start and end), status, and the associated customer party.

Common Use Cases and Queries

A primary use case is validating and reporting on active pricing agreements for a customer during order entry or audit. For instance, to list all active agreements for a specific customer, a query would join OE_AGREEMENTS_B with the customer table (likely HZ_CUST_ACCOUNTS) and filter by SYSDATE between the start and end dates. Another critical scenario involves troubleshooting order pricing; developers often query the agreement details linked to a specific sales order header or line via the AGREEMENT_ID stored in OE_ORDER_HEADERS_ALL or OE_ORDER_LINES_ALL. A common reporting need is to identify agreements expiring within a certain period, which involves filtering on the agreement end date column. Sample SQL to find agreements using a specific price list would be: SELECT agreement_id, name FROM qp.oe_agreements_b WHERE price_list_id = <list_id>;.

Related Objects

OE_AGREEMENTS_B is centrally connected to several key transactional and interface tables. It is referenced directly by the main order entities: OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL. This linkage allows orders to inherit the agreed-upon pricing terms. The table also has dependencies from interface tables like OE_HEADERS_IFACE_ALL and OE_HEADER_ACKS, which handle the import and acknowledgment of orders. As shown in the metadata, it draws foundational rules from other modules: PRICE_LIST_ID from QP_LIST_HEADERS_B (Advanced Pricing), SALESREP_ID from RA_SALESREPS_ALL (Receivables), and accounting/invoicing rules from RA_RULES (Receivables). This makes it a convergence point for data from Pricing, Order Management, and Receivables.