R12.2 Upgrade - ADZDPSUM.sql & ADZDPMAN.sql produce EBS_SYSTEM related exceptions post AD/TXK Delta 13. (Doc ID 2953638.1)

Last updated on SEPTEMBER 05, 2024

Applies to:

Symptoms

On : 12.2.12 version, Upgrade related issues

When attempting to run ADZDPMAN.sql & ADZDPSUM.sql respectively during E-Business suite applications upgrade to 12.2,

the following exceptions are reported:

DOC>
DOC> **********************************************************************
DOC> SECTION-3
DOC> **********************************************************************
DOC>
DOC> Unregistered schemas that depend on EBS Objects
DOC>
DOC> The listed schemas are not currently registered as Custom EBS Schemas,
DOC> but contain objects which depend on EBS objects. The Online Patching
DOC> enablement process requires that Custom EBS Schemas be registered with
DOC> EBS and enabled for editioning.
DOC>
DOC> For each schema reported below, please do one of the following:
DOC>
DOC> - If the schema should be retained and will continue to depend on
DOC> EBS objects, then register it as a Custom EBS Schema. Custom EBS
DOC> Schemas will need to comply with new EBS Custom Development
DOC> Standards. See the ADZDPCUST.sql template file instructions
DOC> on how to register custom schemas.
DOC> - If the schema should be retained, but should not depend on EBS
DOC> objects, then leave the schema unregistered and correct any
DOC> object-level violations in the next phase of the readiness check.
DOC> - If the schema is unused, drop it.
DOC>
DOC> Oracle recommends you perform the chosen fix by customizing template file
DOC> $AD_TOP/sql/ADZDPCUST.sql
DOC>
DOC> EBS objects in CTXSYS get dropped as part of EBR enablement, and will not
DOC> show up here due to that
DOC>
DOC>#

Schema Object Type Number of Objects
-------------------- -------------------- -----------------
EBS_SYSTEM PACKAGE BODY 2
  SYNONYM 1


2 rows selected.

Elapsed: 00:00:06.17

Start Time: 03-05-2023 20:29:03

PL/SQL procedure successfully completed.

DOC> Online Patching Enablement: Readiness Report - Manual Fixes
DOC>
DOC>#
DOC> DISCLAIMER: Customers should not attempt to fix any E-Business Suite code
DOC> violations. E-Business Suite objects listed in sections that
DOC> instruct to perform manual fixes should be reported to Oracle
DOC> Support.
DOC>
DOC> Note: If you are running this report prior to the E-Business Suite 12.2
DOC> Upgrade, you can ignore all the E-Business Suite objects listed in
DOC> the report. The Upgrade process will address any violation to the
DOC> EBR rule on the E-Business Suite code.
DOC>==========================================================================
DOC>#
DOC>
DOC> **********************************************************************
DOC> SECTION-1
DOC> **********************************************************************
DOC>
DOC> MANUAL FIX: Objects in Non-EBS schemas that depend on Editioned
DOC> Objects of EBS.
DOC>
DOC> To fix these violations, do one of the following:
DOC> - Register object schema (owner) as a Custom EBS Schema, please refer to
DOC> report ADZDPSUM.sql
DOC> - Drop object, if not required
DOC> - Redefine object to remove dependency
DOC> - Move the object to a registered Custom EBS Schema
DOC>
DOC> Oracle recommends you perform the chosen fix by customizing template file
DOC> $AD_TOP/sql/ADZDPCUST.sql
DOC>
DOC>#

Owner Object Name Object Type Reference Owner Reference Object Name Reference Object Type
-------------------- ------------------------------ -------------------- -------------------- ------------------------------ ---------------------
EBS_SYSTEM AD_DIR_OBJ_UTIL PACKAGE BODY APPLSYS FND_ORACLE_USERID# VIEW
EBS_SYSTEM AD_ZD_SYS PACKAGE BODY APPLSYS FND_ORACLE_USERID# VIEW
EBS_SYSTEM FND_ORACLE_USERID SYNONYM APPLSYS FND_ORACLE_USERID# VIEW

3 rows selected.

Elapsed: 00:00:02.64

Changes

Upgrading to E-Business suite applications 12.2.x with AD/TXK Delta 13 or above.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.