Search Results ar_lc_cust_sites_t

Overview

The AR_LC_CUST_SITES_T table resides in the AR (Receivables) schema and is documented in Oracle E-Business Suite 12.1.1 and 12.2.2 as a Late Charge processing table. It stores the configuration parameters that govern how Oracle Receivables calculates, accrues, and applies late charges (interest and penalties) against overdue customer transactions. Each row associates a set of late-charge rules with a specific customer, customer site use, currency, and customer profile context, allowing organizations to apply differentiated dunning and interest policies across their receivables population rather than a single global rule set.

From a Data Vault modeling perspective, the supplied metadata classifies this object as standalone (its heuristic classification). This can be read as a modeling suggestion: while the physical table carries foreign keys to collectors, profile amounts, and interest schedules, it is not treated as a pure dependent link in the vault sense. Instead, it functions as a satellite-like repository of descriptive late-charge attributes keyed to a customer/site business key.

Key Information Stored

The table contains 47 documented columns. The surrogate primary key is LC_CUST_SITES_ID, enforced through the unique index AR_LC_CUST_SITES_U1 and the constraint AR_LC_CUST_SITES_PK. Business-key context is provided by the customer and site identifiers rather than by the surrogate itself.

• CUSTOMER_ID, CUSTOMER_SITE_USE_ID, and CUSTOMER_PROFILE_ID — identify the customer, site use, and profile to which the late-charge configuration applies.
• CURRENCY_CODE — the currency in which thresholds and amounts are expressed.
• COLLECTOR_ID — links the configuration to a receivables collector.
• LATE_CHARGE_TYPE, LATE_CHARGE_CALCULATION_TRX, and LATE_CHARGE_TERM_ID — define the nature and basis of the charge computation.
• INTEREST_TYPE, INTEREST_RATE, INTEREST_FIXED_AMOUNT, INTEREST_RATE-related INTEREST_SCHEDULE_ID, and INTEREST_PERIOD_DAYS/INTEREST_CALCULATION_PERIOD — govern interest assessment.
• PENALTY_TYPE, PENALTY_RATE, PENALTY_FIXED_AMOUNT, and PENALTY_SCHEDULE_ID — govern penalty assessment.
• MIN_INTEREST_CHARGE and MAX_INTEREST_CHARGE — cap and floor the assessed interest.
• MIN_FC_INVOICE_* and MIN_FC_BALANCE_* columns — set minimum overdue thresholds by type, amount, and percent.
• PAYMENT_GRACE_DAYS, CHARGE_BEGIN_DATE, and LAST_ACCRUE_CHARGE_DATE — control timing of accrual and grace.
• ORG_ID and REQUEST_ID — provide multi-org and concurrent-request context.

Common Use Cases and Queries

Typical usage includes reviewing and auditing late-charge configuration per customer, reconciling which sites will be assessed interest, and feeding reporting on accrued charges. A representative query retrieves the effective policy for a customer:

• SELECT lc.LC_CUST_SITES_ID, lc.CUSTOMER_ID, lc.CUSTOMER_SITE_USE_ID, lc.CURRENCY_CODE, lc.INTEREST_RATE, lc.PENALTY_RATE FROM AR.AR_LC_CUST_SITES_T lc WHERE lc.CUSTOMER_ID = :customer_id;
• Configuration coverage: SELECT ORG_ID, LATE_CHARGE_TYPE, COUNT(*) FROM AR.AR_LC_CUST_SITES_T GROUP BY ORG_ID, LATE_CHARGE_TYPE;
• Exception review of missing schedules: SELECT * FROM AR.AR_LC_CUST_SITES_T WHERE INTEREST_SCHEDULE_ID IS NULL;

Related Objects

The documented foreign keys and primary key expose the most significant relationships:

• AR_COLLECTORS — joined via COLLECTOR_ID.
• HZ_CUST_PROFILE_AMTS — joined via CUST_ACCT_PROFILE_AMT_ID.
• CE_INTEREST_SCHEDULES — joined via INTEREST_SCHEDULE_ID.
• HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL — referenced through CUSTOMER_ID and CUSTOMER_SITE_USE_ID.
• AR_LC_CUST_SITES_T is also referenced by Receivables late-charge concurrent programs and by the collections and dunning workflows that consume its configuration.