Search Results upgrade_insert_errors

Overview

The APPS.OE_UPG_INSTALL_DETAILS package body is a legacy upgrade utility that supports the migration of service and installation detail data during the Oracle E-Business Suite upgrade path from release 11.5.x to 12.1.1 or 12.2.2. Its purpose is to reconcile records stored in the Order Management service line tables with the corresponding entries in Oracle Installed Base, identifying service detail lines that have not yet been propagated to the installed base tables and inserting the missing records. This is a critical data integrity step, since installed base records are required for downstream service contracts, warranty tracking, and depot repair processes.

The package header dates to June 2005 (OEXIUIDB.pls 120.0) and was classified as OTHER in the ETRM registry, indicating that it is not a public application programming interface but an internal, upgrade-only artifact. It is designed to be forward-compatible with both the 11.5.1.A patch driver, which invokes it without parameters, and the 11.5.2 driver, which executes it through parallel workers.

Key Procedures and Functions

• UPGRADE_INSTALL_DETAILS — The main driver procedure. It accepts an optional slab identifier so the upgrade can be partitioned across parallel workers on later patch drivers. It opens a dynamically constructed cursor over SO_LINE_SERVICE_DETAILS joined to OE_ORDER_LINES_ALL, filtering for service detail lines that have no matching row in CS_LINE_INST_DETAILS. For each qualifying line, the procedure constructs the installed base detail record and inserts it. The dynamic SQL is essential to the design, allowing the BETWEEN range clause to be appended only when the slab parameter is supplied.
• GET_LINE_INST_DETAILS — A supporting procedure that derives and returns the installed base line detail information required for the migration, resolving the parent line and header context associated with an order line's service details.
• UPGRADE_INSERT_ERRORS — A private helper (not in the documented procedure count) that logs a header identifier and a comment string into OE_UPGRADE_ERRORS, truncating the comment to 240 characters. This is the routine surfaced when users search for upgrade_insert_errors.

Tables Accessed

• OE_UPGRADE_ERRORS — Receives error rows written by Upgrade_Insert_Errors, capturing the header ID, truncated comment text, and creation date for diagnostic review.
• SO_LINE_SERVICE_DETAILS / SO_LINES_ALL — The source of service detail rows to be migrated.
• OE_UPGRADE_DISTRIBUTION — Tracks upgrade processing distribution, typically used to coordinate parallel workers.
• HZ_CUST_ACCT_SITES_ALL / HZ_CUST_SITE_USES_ALL — Attribute the owning customer account and site usage for the installed base records created.

Usage Notes

This package is invoked exclusively during the upgrade cycle, not at runtime in a production 12.x instance. It is triggered by the upgrade patch driver rather than by an application form or a registered concurrent program; no concurrent program definition is documented for it. On 11.5.2 and later drivers it may be executed by parallel workers, each receiving a distinct slab range so that installations with very large service detail volumes complete within acceptable windows. Administrators should inspect OE_UPGRADE_ERRORS after the upgrade to identify service lines that failed migration, and should not call the package from custom code or extend it, as it is a one-time upgrade artifact whose behavior is tied to the source release. The package is referenced by zero other packages according to the ETRM metadata, confirming its self-contained, transient role.