Results for “ra_terms_lines”

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

Overview

RA_TERMS_LINES is a Receivables (AR) module table that stores the line-level detail for payment terms defined in Oracle E-Business Suite. Each row represents a single installment (a "term line") belonging to a payment term header, capturing when a portion of an invoice amount becomes due relative to the invoice date. The table is owned by the AR schema and is classified as VALID in both release 12.1.1 and 12.2.2.

In Oracle Payments and Receivables, a payment term typically consists of one or more lines that together define how an invoice should be paid — for example, an "immediate" term with one line, a "net 30" term with one line, or a "2% 10, net 30" term with multiple lines representing discount and net segments. RA_TERMS_LINES holds these definitions at the installment level, making it a foundational reference table for due date calculation, aging, and collections processing.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This is consistent with the table acting as a dependent child of a business entity (the payment term header in RA_TERMS_B), describing descriptive attributes of that entity rather than serving as an independent hub or a many-to-many link.

Key Information Stored

The table is documented with 29 columns. The most operationally significant columns are described below.

• TERM_ID — Foreign key to RA_TERMS_B; identifies the parent payment term to which the line belongs.
• SEQUENCE_NUM — Ordinal position of the term line within its parent term. Together with TERM_ID, it forms the primary key RA_TERMS_LINES_PK and the unique business key RA_TERMS_LINES_U1.
• RELATIVE_AMOUNT — The portion of the invoice amount attributable to this term line (for example, a percentage split across installments).
• DUE_DAYS — Number of days from the invoice date (or other base date) when this installment becomes due.
• DUE_DATE — An explicit target due date, where applicable.
• DUE_DAY_OF_MONTH — A monthly anchor day (for example, the 15th) used to compute due dates on recurring terms.
• DUE_MONTHS_FORWARD — Number of months forward from the base date for computing the due date.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns, enabling customers to capture supplementary, site-specific term line information.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording record creation and modification.
• ZD_EDITION_NAME — Editioning/partitioning column present in the 12.2.2 documented schema, appearing in the unique index RA_TERMS_LINES_U1 (TERM_ID, SEQUENCE_NUM, ZD_EDITION_NAME).

The surrogate primary key is RA_TERMS_LINES_PK (TERM_ID, SEQUENCE_NUM). The business key candidate is RA_TERMS_LINES_U1, which extends the same columns with ZD_EDITION_NAME.

Common Use Cases and Queries

RA_TERMS_LINES is primarily consumed during invoice creation and due date derivation. The AutoInvoice process and the Receivables due date engine read these lines to schedule installments for each invoice, and collections and aging reports rely on the resulting schedules.

A typical pattern retrieves all lines for a term:

SELECT term_id, sequence_num, relative_amount,
       due_days, due_date, due_day_of_month, due_months_forward
FROM   ar.ra_terms_lines
WHERE  term_id = :term_id
ORDER BY sequence_num;

To join term header and line information:

SELECT b.name, b.description, l.sequence_num,
       l.relative_amount, l.due_days
FROM   ar.ra_terms_b b,
       ar.ra_terms_lines l
WHERE  b.term_id = l.term_id
AND    b.term_id = :term_id;

Because RELATIVE_AMOUNT and the due date offsets drive downstream payment schedules, discrepancies in this table frequently cause invoice due-date errors and aging misclassification, making it a common target for data validation audits.

Related Objects

• RA_TERMS_B — Parent payment terms header; joined on RA_TERMS_LINES.TERM_ID = RA_TERMS_B.TERM_ID.
• RA_TERMS_TL — Stores translatable name and description for the same term, reached through the parent header.
• RA_CUSTOMER_TRX — Invoice header table; the payment term and derived schedules apply to its invoices.
• RA_CUSTOMER_TRX_LINES — Invoice lines whose due dates are calculated from term lines.
• AR_PAYMENT_SCHEDULES_ALL — Holds the resulting installment schedules generated using RA_TERMS_LINES definitions.
• AR_TERMS_API / AR_TERMS_PUB — Public APIs that create and maintain payment terms and lines.

Together, these objects form the payment terms hierarchy and its downstream effects on invoice scheduling and collections within Oracle Receivables.