Upgrade from 11i to 12.1 Failing PAY Related Ldt files For Foreign Territories (Doc ID 1510296.1)

Last updated on DECEMBER 22, 2016

Applies to:

Oracle Payroll - Version 12.1.3 and later
Information in this document applies to any platform.
Patch 6678700 - 12.1.1 : Upgrade Patch

Symptoms

On : 12.1.3 version, Patch Application Issues

Patch 6678700 failing py-related ldts for foreign territories

When running 6678700 during upgrade from 11.5.10.2 to 12.1.1 using Maintenance Wizard 2.20, we are experiencing patch failures that were not incurred during the last round of testing. The difference now from the last iteration of testing is that we have applied the HRMS FP RUP 7, YEPP Phase I patches to the 11.5.10.2 EBS. After the application of these patches, the patch is unable to update territories we do not use. We are US only.

ERROR
-----------------------

ORA-06508: PL/SQL: could not find program unit being called: "APPS.HR_PAYMENTS"
ORA-06512: at "APPS.PAY_PAYMENT_TYPES_BRUI", line 3
ORA-04088: error during execution of trigger 'APPS.PAY_PAYMENT_TYPES_BRUI'

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl pynlpymt.ldt Skip & restart
  2 Run AutoPatch R120 pl pynopymt.ldt Skip & restart
  3 Run AutoPatch R120 pl pycnpytt.ldt Skip & restart
  4 Run AutoPatch R120 pl pyfipymt.ldt Skip & restart
  5 Run AutoPatch R120 pl pydkpymt.ldt Skip & restart
  6 Run AutoPatch R120 pl pysapymt.ldt Skip & restart
  7 Run AutoPatch R120 pl pynlptt.ldt Skip & restart
  8 Run AutoPatch R120 pl pyaepymt.ldt Skip & restart

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl pysepymt.ldt Skip & restart

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl pykwpymt.ldt FAILED TERRITORY_CODE = KW
  2 Run AutoPatch R120 pl pyjppytt.ldt FAILED TERRITORY_CODE = JP
  3 Run AutoPatch R120 pl pydepymt.ldt FAILED EUR, TERRITORY_CODE = DE
  4 Run AutoPatch R120 pl pyhkpytt.ldt FAILED TERRITORY_CODE = HK
  5 Run AutoPatch R120 pl pyitpymt.ldt FAILED EUR, TERRITORY_CODE = IT
  6 Run AutoPatch R120 pl pybepymt.ldt FAILED EUR, TERRITORY_CODE = BE
  7 Run AutoPatch R120 pl pyfrlptt.ldt FAILED EUR, TERRITORY_CODE = FR
  8 Run AutoPatch R120 pl pycapyttt.ldt FAILED TERRITORY_CODE = CA

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl pyplpymt.ldt FAILED TERRITORY_CODE = PL
  2 Run AutoPatch R120 pl pypytcheque.ldt FAILED TERRITORY_CODE = ,
  3 Run AutoPatch R120 pl pypytcash.ldt FAILED TERRITORY_CODE = ,

workers 4 - 6... had the same type of errors - see Doc ID 1174964.1
ERROR at line 1:
ORA-06501: PL/SQL: program error
ORA-06512: at "APPS.HR_API_USER_HOOKS_UTILITY", line 891
ORA-06512: at line 1

  4 Run AutoPatch R120 pl pyelersd.sql FAILED
  5 Run AutoPatch R120 pl peaeirsd.sql FAILED
  6 Run AutoPatch R120 pl peaddasd.sql FAILED



More of the same errors. See Doc ID: During 12.1.1 Upgrade From 11.5.10 RUP 4 Peaeirsd.Sql Fails with PLS-00201: identifier 'INVALID_SEE_COMMENT_IN_SOURCE' must be declared [ID 888701.1]
...For Customer who have already upgraded to 12.1.1, should apply the patch <> to remove any invalid objects (KR legislation only), NL Legislation needs to request <>

ORA-06501: PL/SQL: program error
ORA-06512: at "APPS.HR_API_USER_HOOKS_UTILITY", line 891
ORA-06512: at line 1

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl penzlhee.sql FAILED
  2 Run AutoPatch R120 pl pyuseehd.sql FAILED
  3 Run AutoPatch R120 pl ghuseled.sql FAILED
  4 Run AutoPatch R120 pl pycnentd.sql FAILED
  5 Run AutoPatch R120 pl pyfrel2d.sql FAILED
  6 Run AutoPatch R120 pl pyieuhee.sql FAILED
  7 Run AutoPatch R120 pl peaeihcd.sql FAILED
  8 Run AutoPatch R120 pl pyusched.sql FAILED

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl pqpeehcd.sql FAILED Restarted
  2 Run AutoPatch R120 pl peruaddd.sql FAILED Skipped
  3 Run AutoPatch R120 pl peesaddd.sql FAILED Skipped
  4 Run AutoPatch R120 pl pekraeid.sql FAILED Restarted
  5 Run AutoPatch R120 pl pesgaeid.sql FAILED Restarted
  6 Run AutoPatch R120 pl peinentd.sql FAILED Skipped
  7 Run AutoPatch R120 pl peaulhee.sql FAILED Skipped
  8 Run AutoPatch R120 pl pepladdd.sql FAILED Skipped

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl pqpeehcd.sql FAILED Skipped
  2 Run AutoPatch R120 pl pqnlasgd.sql FAILED Skipped
  3 Run AutoPatch R120 pl Wait
  4 Run AutoPatch R120 pl pekraeid.sql FAILED Skipped
  5 Run AutoPatch R120 pl pesgaeid.sql FAILED Skipped
  6 Run AutoPatch R120 pl pekraexd.sql FAILED Skipped
  7 Run AutoPatch R120 pl Wait
  8 Run AutoPatch R120 pl peaevald.sql FAILED Skipped

Worker Code Context Filename Status
------ -------- ----------------- -------------------------- --------------
  1 Run AutoPatch R120 pl Wait
  2 Run AutoPatch R120 pl Wait
  3 Run AutoPatch R120 pl Wait
  4 Run AutoPatch R120 pl Wait
  5 Run AutoPatch R120 pl pyelepsd.sql FAILED Skipped
  6 Run AutoPatch R120 pl Wait
  7 Run AutoPatch R120 pl Wait
  8 Run AutoPatch R120 pl gmfpostimportaad.sql Running




STEPS
-----------------------
We followed this note: 12.1.1 Upgrade Patch Fails With: "Error loading seed data for PAY_PAYMENT_TYPE..." [ID 1493231.1] first and skipped the workers.
However, it seems to just cascade the errors.
Now we cannot run HRGLOBAL successfully.
We also reviewed Doc. ID 849871.1 Known HRMS Issues for 12.1.1. Maintenance Pack, and applied two patches, 8429275 as preinstall, and patch 14844264 as preinstall, and 8940461 as preinstall.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:

We are just a few days from go-live on the 12.1.3 upgrade. We are experiencing errors with our last test run that we did not see prior to this cycle. As noted, the difference is the HR year end patches. If we cannot get this resolved in a timely fashion, we will have to postpone our upgrade to sometime next year.

Changes

 Applied Patch 6678700 - 12.1.1 : Upgrade Patch

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms