Results for “outstanding_amount”

6 results




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

Overview

The table JG_ZZ_INT_INV_LINES_ALL is owned by the AR schema and belongs to the JG – Regional Localizations product family within Oracle E-Business Suite. It stores the detail invoice lines that make up interest invoices generated by the regional localization interest calculation processes. Each row represents a single interest line tied to a parent interest invoice, capturing the computed interest charge, the outstanding balance it was assessed against, the relevant date range, and the payment or receivable context in which the interest accrued.

Because interest invoices are typically generated by batch programs that assess late payment interest on overdue transactions, this table functions as the transactional backbone for interest invoicing in localizations that require statutory late-payment interest handling (for example, certain EMEA and Latin American jurisdictions). The metadata suggests a satellite-leaning heuristic Data Vault classification. In that modeling view, JG_ZZ_INT_INV_LINES_ALL would be treated as a satellite hanging off the parent interest invoice hub/link rather than as an independent hub or link, since its rows describe descriptive, time-stamped attributes of an invoice event defined elsewhere.

Key Information Stored

The table contains 18 documented columns. The surrogate primary key is JG_ZZ_INT_INV_LINES_PK, composed of INTEREST_INVOICE_ID, INTEREST_INVOICE_LINE_ID, and ORG_ID. A unique index, JG_ZZ_INT_INV_LINES_U1, covers the same three columns and serves as the business-key candidate for the multilanguage (_ALL) design.

The audit columns follow standard EBS convention and support change tracking and concurrent program auditing.

Common Use Cases and Queries

Typical reporting scenarios include reconciling interest charges against parent invoices, auditing overdue balances by customer, and validating interest calculations during regulatory or localization audits. A join to the parent invoice table is the most common pattern:

  • Interest invoice line detail report for a given operating unit.
  • Reconciliation of INTEREST_CHARGED against AR invoice totals.
  • Aging analysis using DAYS_OVERDUE_LATE and OUTSTANDING_AMOUNT.
  • Rate validation and exception reporting on INTEREST_RATE.

Sample SQL:

SELECT l.interest_invoice_id,
       l.interest_invoice_line_id,
       l.outstanding_amount,
       l.interest_rate,
       l.days_of_interest,
       l.interest_charged
FROM   jg_zz_int_inv_lines_all l
WHERE  l.org_id = :p_org_id
AND    l.interest_charged > 0;

Related Objects

  • JG_ZZ_INTEREST_INVOICES_ALL – Parent invoice header table; joined on INTEREST_INVOICE_ID (documented FK).
  • JG_ZZ_INT_INV_LINES_PK – Primary key constraint enforcing uniqueness.
  • JG_ZZ_INT_INV_LINES_U1 – Unique index on the business-key columns.
  • RA_CUSTOMER_TRX_ALL – Standard AR invoice header created upon interest invoice import.
  • RA_CUSTOMER_TRX_LINES_ALL – AR invoice lines corresponding to interest lines.
  • AR_PAYMENT_SCHEDULES_ALL – Referenced via PAYMENT_SCHEDULE_ID for installment context.
  • AR_RECEIVABLE_APPLICATIONS_ALL – Referenced via RECEIVABLE_APPLICATION_ID.
  • Interest invoice generation concurrent programs and localization APIs that populate this table.