Results for “jg_zz_int_inv_lines_u1”

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

Overview

AR.JG_ZZ_INT_INV_LINES_ALL is a transactional table in the Oracle E-Business Suite Receivables (AR) schema that stores the individual calculation lines belonging to interest invoices generated by the Oracle Legal Entity / Global Interest (JG) interest invoicing engine. Each row captures the computed interest charge for a single payment schedule of a delinquent customer transaction, forming the granular detail beneath a parent interest invoice header. The table resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as JG.JG_ZZ_INT_INV_LINES_ALL, with a status of VALID in both EBS 12.1.1 and 12.2.2. It is multi-org enabled through the ORG_ID column, and its hybrid naming convention — an AR-schema table whose subobject belongs to the JG product family — reflects its role as the persistence target for interest invoice creation and late charge processing.

From a dimensional modeling perspective, the heuristic Data Vault classification for this table is satellite-leaning. A satellite-leaning object typically records descriptive attributes and measured values attached to a parent business key, which matches this table: its rows carry the computed interest metrics subordinate to an interest invoice identifier. Modelers should treat the parent interest invoice identifier as the hub/link anchor and the remaining columns as satellite payload.

Key Information Stored

The table contains 18 documented columns. The most significant are:

• INTEREST_INVOICE_LINE_ID — Surrogate identifier for each individual interest line; the granular key for the row.
• INTEREST_INVOICE_ID — Foreign key to the parent interest invoice header (AR.JG_ZZ_INTEREST_INVOICES_ALL) and the first component of the composite primary key JG_ZZ_INT_INV_LINES_PK.
• ORG_ID — Operating unit identifier, the third component of the composite primary key and the enabling column for multi-org security.
• PAYMENT_SCHEDULE_ID — Links the interest line back to the specific payment schedule installment that triggered the charge; indexed by JG_ZZ_INT_INV_LINES_N1.
• TYPE — Classifies the interest line (for example, the nature of the late or interest charge).
• DAILY_INTEREST_CHARGE, OUTSTANDING_AMOUNT, DAYS_OF_INTEREST, INTEREST_RATE — The rate and base amount inputs used in the calculation.
• DAYS_OVERDUE_LATE — The number of days the item was overdue at calculation time.
• INTEREST_CHARGED — The resulting interest amount posted to the interest invoice.
• PAYMENT_DATE — The date used for interest computation.
• RECEIVABLE_APPLICATION_ID — Links the line to the receipt application that settled or affected the transaction.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and ORG_ID provide WHO-columns and multi-org context.

The unique index JG_ZZ_INT_INV_LINES_U1 (INTEREST_INVOICE_ID, INTEREST_INVOICE_LINE_ID, ORG_ID) duplicates the primary key definition and represents the strongest business-key candidate; the composite includes the surrogate line identifier, however, so it is not a pure natural key. The nonunique index JG_ZZ_INT_INV_LINES_N1 on PAYMENT_SCHEDULE_ID supports schedule-driven lookups.

Common Use Cases and Queries

Typical uses include interest invoice reconciliation, late-charge reporting, aging analysis, and audit of interest calculations by operating unit. Analysts commonly retrieve all lines for a given interest invoice or operating unit:

• Extract header-to-line detail: SELECT l.* FROM AR.JG_ZZ_INT_INV_LINES_ALL l WHERE l.INTEREST_INVOICE_ID = :invoice_id AND l.ORG_ID = :org_id;
• Trace interest charged back to a payment schedule: SELECT * FROM AR.JG_ZZ_INT_INV_LINES_ALL WHERE PAYMENT_SCHEDULE_ID = :ps_id;
• Aggregate interest by operating unit and date range: SELECT ORG_ID, TRUNC(PAYMENT_DATE), SUM(INTEREST_CHARGED) FROM AR.JG_ZZ_INT_INV_LINES_ALL GROUP BY ORG_ID, TRUNC(PAYMENT_DATE);
• Analyze outstanding balances versus days overdue to validate rate application using OUTSTANDING_AMOUNT, DAYS_OVERDUE_LATE, INTEREST_RATE, and INTEREST_CHARGED.

Related Objects

The most significant related objects, based on documented relationship data:

• AR.JG_ZZ_INTEREST_INVOICES_ALL — The parent interest invoice header table; joined on INTEREST_INVOICE_ID (the documented foreign key target).
• APPS.JG_ZZ_INT_INV_LINES_ALL — The APPS-layer synonym/view that references this table and is the normal public access point for reports and concurrent programs.
• Payment schedule objects (AR_PAYMENT_SCHEDULES_ALL) — Related via PAYMENT_SCHEDULE_ID for tracing the installment that generated the charge.
• Receivable application objects (AR_RECEIVABLE_APPLICATIONS_ALL) — Related via RECEIVABLE_APPLICATION_ID for linking to cash application activity.
• Operating unit / organization objects (HR_OPERATING_UNITS) — Related via ORG_ID to resolve the operating unit context.

Because the table does not reference other database objects beyond the documented foreign key, its dependency footprint is intentionally narrow, concentrating all downstream consumption through the parent interest invoice header and the APPS-layer alias.