Search Results RA_TERMS_B

Overview

The RA_TERMS_B table is a core master data table within the Oracle E-Business Suite (EBS) Receivables (AR) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for defining and storing payment terms, which are critical business rules dictating the due dates and potential discount schedules for customer invoices. The table's role is foundational to the order-to-cash cycle, as payment terms defined here are referenced throughout the application to automatically calculate invoice due dates, discount eligibility, and payment schedules. Its central importance is evidenced by its extensive integration across multiple EBS modules, including Order Management, Inventory, and Projects.

Key Information Stored

The table's primary key is the TERM_ID, a unique identifier for each payment term definition. While the provided metadata does not list specific columns, based on its function and related objects, the table typically stores attributes such as the term name (NAME), description, status (e.g., Active), and the base calculation method (e.g., from the invoice date or receipt of goods). The detailed structure of a payment term, including its installment lines and discount rules, is stored in related child tables: RA_TERMS_LINES for payment schedules and RA_TERMS_LINES_DISCOUNTS for early payment discounts. These tables are linked to RA_TERMS_B via the TERM_ID foreign key.

Common Use Cases and Queries

A primary use case is reporting and validating the payment terms applied to transactions. A common query involves joining RA_TERMS_B to transaction tables to list invoices and their associated terms. For example, to analyze open invoices and their due dates, one might query:

• SELECT trx.trx_number, trx.trx_date, terms.name, ps.due_date FROM ra_customer_trx_all trx JOIN ra_terms_b terms ON trx.term_id = terms.term_id JOIN ar_payment_schedules_all ps ON trx.customer_trx_id = ps.customer_trx_id WHERE ps.status = 'OP';

Another critical scenario is troubleshooting integration issues, such as when payment terms from Order Management (OE_ORDER_HEADERS_ALL.PAYMENT_TERM_ID) do not align with those defaulted for a customer site (RA_SITE_USES_ALL.PAYMENT_TERM_ID), which requires queries joining these tables back to RA_TERMS_B.

Related Objects

As detailed in the metadata, RA_TERMS_B is a heavily referenced parent table. Key foreign key relationships include:

• Transaction & Customer Data: RA_CUSTOMER_TRX_ALL, AR_PAYMENT_SCHEDULES_ALL, RA_CUSTOMERS, and RA_SITE_USES_ALL.
• Order Management: OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and various interface/acknowledgment tables (OE_HEADERS_IFACE_ALL, OE_HEADER_ACKS).
• Pricing & Agreements: QP_LIST_HEADERS_B (Advanced Pricing), SO_AGREEMENTS_B (Sales Agreements), and PA_AGREEMENTS_ALL (Projects).
• Inventory: MTL_SYSTEM_ITEMS_B, linking terms directly to items.
• Child Tables for Term Structure: RA_TERMS_LINES and RA_TERMS_LINES_DISCOUNTS, which store the detailed schedule and discount rules for each TERM_ID.