Search Results oe_upgrade_misc_new




Overview
Explore in AI Chat

Overview

OE_UPGRADE_MISC_NEW is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as a miscellaneous upgrade utility rather than a runtime Order Management API. Its name and dependency footprint identify it as a one-time data migration helper used during an upgrade into Release 12.1.1 or 12.2.2, performing currency conversion and cleanup of order-related data that earlier releases stored inconsistently. The package is marked VALID and referenced by no other database object, confirming that it is invoked manually or from a driver script during the upgrade cycle and is not part of the functional call stack of Order Management or Advanced Pricing.

The package resolves currency and set-of-books context, rounds monetary amounts to the appropriate precision, rebuilds freight-related records, and touches price adjustment and pricing list data inherited from the pre-upgrade model. In the 12.2.2 data model, much of this responsibility moved into standard pricing and order capture APIs, so OE_UPGRADE_MISC_NEW remains an environment-specific remediation utility rather than a supported integration point.

Key Procedures and Functions

The documented API surface consists of four programs:

  • CONVERT_CURRENCY — Converts monetary values from a source currency into the target currency, relying on the currency definitions and conversion machinery accessible through GL_CURRENCY_API and FND_CURRENCIES. It supports the bulk revaluation of pre-upgrade order and adjustment amounts.
  • CREATE_FREIGHT_RECORD — Builds or repairs freight charge records associated with orders, ensuring that freight handling data migrated from the prior release is represented in the upgraded Order Management tables.
  • ROUND_AMOUNT — Applies currency-appropriate rounding to an amount, a necessary step before currency conversion so that stored values comply with the precision and extended precision rules of the target currency.
  • GET_SOB_CURRENCY — Returns the functional currency of a set of books (ledger), used to determine the default currency context for conversion and rounding operations.

Parameter signatures are not documented in the ETRM metadata and should not be assumed; consumers should treat each program as a helper with a narrow, upgrade-specific purpose.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

  • AR_SYSTEM_PARAMETERS_ALL — source of operating unit–level currency and rounding preferences.
  • FND_CURRENCIES — currency definitions supplying precision and extended precision values used by ROUND_AMOUNT.
  • GL_SETS_OF_BOOKS — provides the ledger needed by GET_SOB_CURRENCY.
  • OE_PRICE_ADJUSTMENTS and OE_PRICE_ADJUSTMENTS_S — the adjustment header and its translation table, updated as part of the pricing data migration.
  • QP_LIST_HEADERS_B, QP_LIST_HEADERS_TL, and QP_LIST_LINES — Advanced Pricing list headers, their translations, and list lines, consulted or corrected so that price lists align with converted order data.
  • DUAL — used for scalar currency and rounding lookups.

Additional internal dependencies include OE_CODE_CONTROL, OE_DEBUG_PUB, OE_SYS_PARAMETERS_PVT, and GL_CURRENCY_API, which supply code generation control, debugging output, system parameter access, and the supported currency conversion call respectively.

Usage Notes

OE_UPGRADE_MISC_NEW is not referenced by any database object, so it is never called automatically by Order Management or Advanced Pricing. It is typically executed by an upgrade driver or by a DBA or technical consultant during a controlled upgrade window, most often after standard upgrade steps have been applied and before users are granted access to the environment. Because the package manipulates historical order and pricing records directly, it should be run only on a backed-up, non-production instance first, with the results validated against source-system totals. Custom code should not depend on this package; any new development requiring currency conversion or rounding should use the supported GL currency APIs and Order Management public APIs instead. Presence of this package on a 12.2.2 instance is normal, but its execution outside an upgrade context is not supported and can corrupt pricing and freight data.