Search Results ap_terms_lines_u1

Overview

AP.AP_TERMS_LINES is a seed-data table in the Oracle Payables (AP) schema that stores the detailed line-level definition of payment terms. Each row represents a single scheduled payment that Oracle Payables will generate for an invoice, and terms configured as split terms span multiple rows — one per installment — within this table. The table resides in the APPS_TS_SEED tablespace, which reflects its role as a reference and setup object that participates in seed data and configuration-driven processing rather than high-volume transactional activity. Column families such as DUE_DAY_OF_MONTH, DUE_MONTHS_FORWARD, and the three tiers of discount attributes support proxima-style terms, where payment and discount dates are computed from relative day, month, and calendar offsets rather than fixed intervals.

From a Data Vault modeling perspective, the mined metadata classifies AP_TERMS_LINES as a standalone object (heuristic classification). This suggests treating it as a satellite-like detail entity attached to the payment terms header, with TERM_ID inheriting link semantics to the parent terms definition and SEQUENCE_NUM providing the ordering key for the schedule. No foreign-key dependencies were detected in the heuristic relationship scan, so the object is self-contained within the AP schema for dependency purposes.

Key Information Stored

The documented physical schema contains 48 columns. The most significant columns are the following:

• TERM_ID (NUMBER) — Term identifier; the surrogate component that links each line to its parent payment terms record.
• SEQUENCE_NUM (NUMBER) — Number of the payment term line; orders the installments within a split term.
• DUE_PERCENT (NUMBER) — Percentage of the payment due by the calculated due date.
• DUE_AMOUNT (NUMBER) — Maximum payment amount due by the calculated due date.
• DUE_DAYS (NUMBER) — Number of days after the terms date used to derive the payment line due date.
• DUE_DAY_OF_MONTH (NUMBER) — Day of month used to calculate the due date; primarily relevant to proxima terms.
• DUE_MONTHS_FORWARD (NUMBER) — Number of months ahead applied when calculating the due date.
• DISCOUNT_PERCENT (NUMBER) — Percentage used to compute the discount available on the payment line.
• DISCOUNT_DAYS (NUMBER) — Days after the terms date used to establish the discount date.
• DISCOUNT_DAY_OF_MONTH and DISCOUNT_MONTHS_FORWARD (NUMBER) — Proxima-style offsets for the discount date calculation.
• DISCOUNT_AMOUNT (NUMBER) and DISCOUNT_CRITERIA (VARCHAR2) — Fixed discount value and its criteria for the first discount tier.
• DISCOUNT_PERCENT_2 / _3, DISCOUNT_DAYS_2 / _3, DISCOUNT_AMOUNT_2 / _3, DISCOUNT_CRITERIA_2 / _3 — Second and third discount tiers, enabling multi-tier early-payment discounts.
• FIXED_DATE and CALENDAR — Fixed-date and calendar attributes supporting date derivation rules.
• ATTRIBUTE1 — ATTRIBUTE15 — Standard descriptive flexfield (DFF) columns for extensibility.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide audit tracking.

The surrogate primary key is AP_TERMS_LINES_PK (TERM_ID, SEQUENCE_NUM). The unique index AP_TERMS_LINES_U1 (TERM_ID, SEQUENCE_NUM) is the candidate business key, enforcing the same uniqueness across the natural schedule identifiers and confirming that TERM_ID plus SEQUENCE_NUM uniquely identifies each installment.

Common Use Cases and Queries

Typical usage involves validating payment term setup, replicating terms across operating units, and diagnosing invoice scheduling discrepancies. A common query pattern retrieves all lines for a given term:

• SELECT sequence_num, due_percent, due_days, discount_percent FROM ap.ap_terms_lines WHERE term_id = :term_id ORDER BY sequence_num;
• Listing split terms: SELECT term_id, COUNT(*) FROM ap.ap_terms_lines GROUP BY term_id HAVING COUNT(*) > 1;
• Discount tier reporting: query DISCOUNT_PERCENT, DISCOUNT_DAYS, DISCOUNT_PERCENT_2, DISCOUNT_DAYS_2, DISCOUNT_PERCENT_3, DISCOUNT_DAYS_3 to document multi-tier discount behavior.
• Audit and change tracking via LAST_UPDATE_DATE and LAST_UPDATED_BY.
• DFF extraction using ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Related Objects

The metadata reports no detected foreign-key relationships, so the following associations are based on the documented TERM_ID and sequence semantics rather than enforced constraints:

• AP_TERMS — Parent payment terms header, joined on AP_TERMS.TERM_ID = AP_TERMS_LINES.TERM_ID.
• AP_TERMS_LINES_U1 — Unique index over TERM_ID and SEQUENCE_NUM, the business-key enforcement mechanism.
• AP_TERMS_LINES_PK — Primary key constraint over the same two columns.
• AP_INVOICE_TERMS / AP_INVOICE_PAYMENTS_SCHEDULE — Invoice-level schedules generated from terms lines.
• AP_PAYMENT_TERMS API (AP_TERMS_PKG) — PL/SQL API used to create and maintain terms and their associated lines.
• AP_TERMS_TL / AP_TERMS_SCHEDULES — Supporting terms setup and schedule objects relevant when maintaining term definitions.

Because AP_TERMS_LINES is flagged as standalone in the mined relationship data, implementers should treat it as a dependent detail entity of the payment terms header and rely on TERM_ID plus SEQUENCE_NUM as the stable join criterion for all reporting and integration work.