Search Results upgrade_lc_sysp

Overview

AR_LATE_CHARGE_UPG is an Oracle E-Business Suite upgrade utility package owned by the APPS schema. Its business purpose is to migrate legacy late charge configuration data into the Oracle Receivables and Oracle Trading Community (HZ) data model that was introduced with Release 12. Late charges are the interest or finance charges that Receivables applies to overdue customer balances, and the Release 11i to 12 upgrade required both the configuration records (profiles, profile classes, system parameters, and site uses) and the associated transaction-level charge schedules to be converted into the new table structures. AR_LATE_CHARGE_UPG encapsulates that conversion logic. The package header is marked with a "noship" header annotation and a version string dating to 2006, confirming it is an internal, upgrade-only construct rather than a supported runtime API. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user, which allows the upgrade driver to operate across both the AR and HZ schemas under a controlled session.

Key Procedures and Functions

The package exposes two helper functions and eight upgrade procedures, for a documented total of ten program units.

• F_NUMBER — a utility function that converts an incoming character value into a numeric value, used to validate and transform legacy character-based rate and amount columns during conversion.
• F_DATE — the companion utility function that converts a character value into a DATE. This is the object returned when users search on "f_date"; it exists solely to translate legacy date strings into proper Oracle date values during the upgrade.
• UPGRADE_SCHEDULE — populates the late charge schedule structures from the legacy interest rate table, mirroring the ar120lcjgr.sql upgrade script.
• UPGRADE_PROFILE_AMOUNT — migrates customer profile amount records, corresponding to ar120lccpa.sql.
• UPGRADE_PROFILE — migrates customer profile records, corresponding to ar120lccp.sql.
• UPGRADE_PROFILE_CLASS_AMOUNT — migrates customer profile class amount records, corresponding to ar120lccpca.sql.
• UPGRADE_PROFILE_CLASS — migrates customer profile class records, corresponding to ar120lccpc.sql.
• UPGRADE_LC_SYSP — migrates the late charge system parameters held in AR_SYSTEM_PARAMETERS_ALL, corresponding to ar120lcsysp.sql.
• UPGRADE_PS_FOR_ADJ — processes payment schedules and site uses as required for adjustments, corresponding to ar120lccsups.sql.
• UPGRADE_LC_SITE_USE — migrates late charge site use configuration.

The upgrade procedures share a common driver signature: table owner, table name, script name, worker identifier, number of workers, and batch size. This signature supports the parallel, restartable execution model used by the Release 12 upgrade, where multiple workers process disjoint batches of rows and each invocation is identified by its originating SQL script.

Tables Accessed

The package reads and writes late charge configuration and schedule data. On the Receivables side it touches AR_ADJUSTMENTS_ALL, AR_CHARGE_SCHEDULES, AR_CHARGE_SCHEDULES_S, AR_CHARGE_SCHEDULE_HDRS, AR_CHARGE_SCHEDULE_HDRS_S, AR_CHARGE_SCHEDULE_LINES, AR_CHARGE_SCHEDULE_LINES_S, AR_PAYMENT_SCHEDULES_ALL, and AR_SYSTEM_PARAMETERS_ALL. On the Trading Community side it touches HZ_CUSTOMER_PROFILES, HZ_CUST_PROFILE_AMTS, HZ_CUST_PROFILE_CLASSES, HZ_CUST_PROF_CLASS_AMTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL. The schedule tables receive the converted late charge definitions, the profile and profile class tables receive the converted interest and charge terms, AR_SYSTEM_PARAMETERS_ALL receives the migrated system-level late charge options, and the payment schedule and adjustment tables are referenced when deriving charges for existing open items.

Usage Notes

AR_LATE_CHARGE_UPG is not a runtime API and is not referenced by any other documented package. It is invoked during the release upgrade by the parallel upgrade driver, which passes the target owner, table, script name, worker identity, worker count, and batch size for each migration step. It should not be called from forms, concurrent programs, or custom code in a production 12.1.1 or 12.2.2 instance. The only supported re-execution context is a restart of the failed upgrade phase, where the worker and batch parameters allow already-processed batches to be skipped. Direct use of the F_NUMBER and F_DATE helpers outside the upgrade is unsupported, and developers needing date or number conversion should use standard SQL conversion functions rather than these internal utilities.