EBS 12.2 -- Problem with AD_ZD package resulting unexpected 'component must be declared' errors

After applying CLE patches ( 34546768:R12.CLE.C , 28828799:R12.CLE.C) to our TEST instance, we noticed lots of invalid database objects owned by APPS user. Our EBS instance has become unusable due to these invalid objects. 

Tried to compile some of those invalid objects for diagnostics purposes, and noticed that almost all of them were complaining about missing GET_RUN_EDITION function, which was supposed to be there in the AD_ZD package.. It was a foundational deficiency.. Then, we checked the version of the AD_ZD package and we saw that its version was way older than the other EBS instances in the environment.. These were clone environments, cloned from one golden copy (let's say) and that's why it was impossible to have a difference in version (impossible to have an older version of a Standard Package.. Let's put it that way:) of a standard package in any of these instances.

It was obvious that one of these CLE patches recreated the AD_ZD package in this environment, but the AD_ZD code delivered with that patch was probably an old version.. So, there was a mismatch, a patch-environment compatibility problem.. I saw problematic CLE patches earlier, but I have never seen such an obvious failure due to patching.

Following the action below; we could fix the problem;

• Stop Apps Services.
• Run adgrants sql.
• Copy the package (ADZDXS.pls) and package body (ADZDXB.pls) from a problem-free environment to the $AD_TOP/patch/115/sql directory of the problematic environment. (backup the old versioned files, just in case..)
• Compile the package spec and bod codes residing in the ADZDXS.pls and ADZDXB.pls files, by connecting to the database using sqlplus
• Compile APPS using adadmin.
• Check invalid objects and ensure that they are validated.
• Start Apps Services.

Tip: Be careful with CLE patches :)