Results for “oe_agreements_b”

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

Overview

OE_AGREEMENTS_B is the foundational table in the QP (Advanced Pricing) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores all information about pricing agreements — the negotiated commercial arrangements between a selling organization and its customers that govern pricing, invoicing, accounting, and shipping terms over a defined effective period. In the EBS order-to-cash flow, rows in this table act as the master definition of a customer agreement, referenced downstream by sales orders, order lines, order acknowledgement records, and order import interface rows.

The ETRM metadata records the table owner as QP with 65 documented columns and a primary key constraint, OE_AGREEMENTS_B_PK, on AGREEMENT_ID. A unique index, OE_AGREEMENTS_B_U1, also exists on AGREEMENT_ID. Under the heuristic Data Vault classification mined from the foreign-key structure, the table is assessed as satellite-leaning. As a modeling suggestion, this implies OE_AGREEMENTS_B behaves primarily as a descriptive attribute carrier attached to a central business key (the agreement), holding terms, dates, and contextual attributes, while also acting as a hub for several outbound references. Analysts designing enterprise data vault or analytical models should treat AGREEMENT_ID as the core business key and the surrounding columns as satellite attributes.

Key Information Stored

The surrogate primary key is AGREEMENT_ID, generated by the OE_AGREEMENTS_B_PK constraint. The unique index OE_AGREEMENTS_B_U1 provides the business-key candidate on the same column, confirming AGREEMENT_ID as the natural identifier for each agreement record.

Among the 65 documented columns, the most operationally significant include:

• NAME, AGREEMENT_NUM, AGREEMENT_TYPE_CODE — the agreement's descriptive label, external number, and type classification.
• PRICE_LIST_ID — foreign key to QP_LIST_HEADERS_B, linking the agreement to the price list whose pricing rules apply.
• INVOICING_RULE_ID and ACCOUNTING_RULE_ID — foreign keys to RA_RULES that determine invoicing and revenue accounting treatment.
• SALESREP_ID — foreign key to RA_SALESREPS_ALL identifying the responsible sales representative.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective dating window for the agreement.
• SIGNATURE_DATE, REVISION, REVISION_DATE, REVISION_REASON_CODE — versioning and execution tracking for negotiated revisions.
• OVERRIDE_IRULE_FLAG and OVERRIDE_ARULE_FLAG — flags controlling whether agreement-level invoicing and accounting rules supersede defaults.
• FREIGHT_TERMS_CODE, SHIP_METHOD_CODE, PURCHASE_ORDER_NUM — commercial logistics terms.
• INVOICE_TO_ORG_ID, SOLD_TO_ORG_ID, INVOICE_TO_CUSTOMER_ID — organizational and customer context.
• AGREEMENT_SOURCE_CODE and ORIG_SYSTEM_AGR_ID — origin tracking for imported or externally sourced agreements.
• ATTRIBUTE1–15 and TP_ATTRIBUTE1–15 (with TP_ATTRIBUTE_CATEGORY) — the standard EBS descriptive flexfield and Trading Partner flexfield segments used for customer-specific extensions.

Common Use Cases and Queries

Typical reporting scenarios include identifying active agreements as of a given date, reconciling agreements to their associated price lists, and tracing sales orders back to the governing agreement. A common pattern filters on the active window and joins to the price list header:

• SELECT a.agreement_id, a.name, a.agreement_num, l.name price_list FROM oe_agreements_b a, qp_list_headers_b l WHERE a.price_list_id = l.list_header_id AND SYSDATE BETWEEN a.start_date_active AND NVL(a.end_date_active, SYSDATE + 1);
• SELECT o.order_number, o.agreement_id FROM oe_order_headers_all o WHERE o.agreement_id IS NOT NULL; — confirms which orders were placed against agreements.
• Revision analysis: SELECT agreement_id, revision, revision_date, revision_reason_code FROM oe_agreements_b ORDER BY agreement_id, revision;
• Sales representative performance: join SALESREP_ID to RA_SALESREPS_ALL to attribute agreement volume to representatives.
• Flexfield extraction: query ATTRIBUTE and TP_ATTRIBUTE columns for downstream analytics or integrations.

Related Objects

The FK metadata identifies four tables referenced by OE_AGREEMENTS_B and four tables that reference it:

• QP_LIST_HEADERS_B — referenced via OE_AGREEMENTS_B.PRICE_LIST_ID; supplies the price list definition.
• RA_RULES — referenced twice, via INVOICING_RULE_ID and ACCOUNTING_RULE_ID, providing invoicing and accounting rule definitions.
• RA_SALESREPS_ALL — referenced via SALESREP_ID, identifying the sales representative.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — reference OE_AGREEMENTS_B through AGREEMENT_ID, linking order headers and lines to their governing agreement.
• OE_HEADERS_IFACE_ALL and OE_HEADER_ACKS — reference OE_AGREEMENTS_B via AGREEMENT_ID, supporting order import and acknowledgement processing.

Together these relationships make OE_AGREEMENTS_B a central master-data object spanning Advanced Pricing, Order Management, and Receivables rule definitions.