Search Results ar_charge_schedules_s

Overview

APPS.AR_LATE_CHARGE_UPG is a PL/SQL package body in the Oracle Receivables (AR) module that supports the late charge feature migration path during Oracle E-Business Suite upgrades and patching. Its primary role is to convert legacy late charge configuration data — historically stored as profile amount and profile class information in the older Receivables architecture — into the schedule-based model introduced with the late charge enhancements in Release 12. Specifically, it seeds the AR charge schedule headers, lines, and related amount tables that drive interest and late charge computation on delinquent transactions. The package is classified as type OTHER (not a public API) and holds a VALID status in the ETRM 12.2.2 registry, with internal helpers for numeric and date conversion supplementing the main upgrade routines. As a body for which no callers exist in the data dictionary, it is intended for direct, controlled invocation by upgrade driver scripts rather than by runtime application logic.

Key Procedures and Functions

The package exposes ten documented subprograms. Two private utilities, F_NUMBER and F_DATE, perform safe conversion of character input into numeric and date values respectively, guarding the upgrade logic against malformed legacy data. The core upgrade routine, UPGRADE_SCHEDULE, builds the charge schedule header and line records that constitute the new late charge definition. UPGRADE_PROFILE_AMOUNT and UPGRADE_PROFILE operate on customer profile amounts and the profile itself, translating legacy profile-level charge parameters into the new structure. UPGRADE_PROFILE_CLASS_AMOUNT and UPGRADE_PROFILE_CLASS apply the equivalent transformation at the profile class level, ensuring shared class definitions are migrated consistently. UPGRADE_LC_SYSP migrates system parameter level late charge settings held in AR_SYSTEM_PARAMETERS_ALL, while UPGRADE_LC_SITE_USE handles late charge configuration attached to customer site uses. UPGRADE_PS_FOR_ADJ reconciles payment schedules in light of adjustments, aligning open balances with the newly seeded charge schedules. No parameter lists are published in the ETRM metadata, and no public signature should be assumed for direct calls without consulting the packaged source.

Tables Accessed

The package reads and writes the AR charge schedule family: AR_CHARGE_SCHEDULE_HDRS and AR_CHARGE_SCHEDULE_HDRS_S, AR_CHARGE_SCHEDULE_LINES and AR_CHARGE_SCHEDULE_LINES_S, plus AR_CHARGE_SCHEDULES and AR_CHARGE_SCHEDULES_S. These hold the migrated late charge definitions and their translated (TL) counterparts. AR_PAYMENT_SCHEDULES_ALL and AR_ADJUSTMENTS_ALL are touched to reconcile installment balances and adjustments during migration. AR_SYSTEM_PARAMETERS_ALL supplies system-level late charge options. Customer data is drawn from HZ_CUSTOMER_PROFILES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_PROFILE_AMTS, HZ_CUST_PROFILE_CLASSES, HZ_CUST_PROF_CLASS_AMTS, and HZ_CUST_SITE_USES_ALL, representing the party model where legacy profile amounts and classes reside. JG_ZZ_II_INT_RATES_ALL provides interest rate reference data, and RA_BATCH_SOURCES_ALL and RA_CUST_TRX_TYPES_ALL support transaction context lookups. Utility dependencies include AD_PARALLEL_UPDATES_PKG for parallel processing, DBMS_SQL and PLITBLM for dynamic SQL construction, and STANDARD and FND_INSTALLATION for standard startup and instance-status checks.

Usage Notes

AR_LATE_CHARGE_UPG is an upgrade-only utility, not a runtime API, and is not referenced by any other database object. It is invoked during the upgrade or patch cycle that enables late charges in Release 12, typically through Oracle-supplied upgrade driver scripts rather than from an application form. DBAs and technical consultants should treat it as non-reentrant production code: it should be run once per upgrade, in a controlled maintenance window, and with parallel processing configured through AD_PARALLEL_UPDATES_PKG where supported. Because the ETRM metadata publishes no parameter interfaces, any custom invocation requires inspection of the packaged source and a full backup of the AR charge schedule and HZ profile tables. The sparse documentation in ETRM — absent procedure signatures and no referencing objects — reinforces that this is internal upgrade machinery intended solely for Oracle-managed migration of late charge data.