EPY: Why are classic plus patches being pulled as prerequisites when applying a tax update? (Doc ID 3065784.1)

Last updated on DECEMBER 31, 2024

Applies to:

Goal

There is a list of unwanted updates included when creating a change package for Tax Updates 24-B, 4-C, and 24-D.
They include the following:
Patch 29518267 - CLASSIC PLUS VIEW: META SQL %EFFDTCHECK GIVES SQLSTATE=01552 WARNING ON DB2
Patch 29393062 - CLASSIC PLUS VIEWS' BUILD SEQUENCE NUMBERS EXCEED 99
Patch 27735627 - CLASSIC PLUS PUM AE RESETS THE COMPONENT BACK TO CLASSIC WHEN DATA RESUBMITTED
Patch 27639136 - PI26- APPLYING THE CLASSIC PLUS THEME FAIL DURING MAKE ME CURRENT FOR MSS PLATFO
Patch 27511225 - AUDIT ERROR FOR EOCP_SETCP PRCSCMP STEP10 S.1
Patch 27400718 - CLASSIC PLUS PEOPLETOOLS COMPONENT SETTING API UPTAKE
Patch 27398836 - CLASSIC PLUS WORKCENTER API UPTAKE - PUM AE
Patch 27392434 - CLASSIC PLUS WORKCENTER API UPTAKE
Patch 27264626 - ENTERPRISE COMPONENTS SETUP: HCM CLASSIC PLUS DATA
Patch 27164539 - CLASSIC PLUS -ENABLE CLASSIC PLUS CHECK BOX NOT WORKING ON SETUP PAGE
Patch 27059376 - ADD DATA TYPE TO IDENTIFY SYSTEM DATA FOR CLASSIC PLUS CONFIGURATION
these are for classic plus and we don't use it.
Are these mandatory, or is there a way to exclude them?
 

Solution

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