Oracle EBS R12: Creating New Branch on New Bank Errors with ORA-06508: Issue Resolution

Oracle Payables – Version: 12.1.1 and later   [Release: 12.1 and later ]
Information in this document applies to any platform.
ARHRELTS.pls 120.2
ARHRELTB.pls 120.4
ARH2RGVB.pls
ARH2RGVS.pls
HZ_RELATIONSHIPS_PKG
HZ_REGISTRY_VALIDATE_V2PUB

In Payables, when trying to save a new bank branch on a newly created bank, users are getting the following online error message:The following SQL error occurred: ORA-06508: PL/SQL: could not find program unit being called.


Payables Manager > Setup: Payment Banks and Bank Branches
Bank Branches Tab > Create
Enter Bank Name, Number and Country
Branch Options > Create New Branch
Enter Branch Name and Branch Type
Click on Save and Next or Finish

The following SQL error appears

ORA-06508: PL/SQL: could not find program unit being called.
Log shows that HZ_RELATIONSHIPS_PKG is the missing program.

Solution

1. Execute HZ_RELATIONSHIPS_PKG to create the database package

       SQL>@ARHRELTS.pls
       SQL>@ARHRELTB.pls

2. Compile HZ_REGISTRY_VALIDATE_V2PUB

     Alter package APPS.HZ_REGISTRY_VALIDATE_V2PUB compile;
     Alter package APPS.HZ_REGISTRY_VALIDATE_V2PUB compile body;

3. Retest the issue.

Reference

R12: Creating New Branch on New Bank Errors with ORA-06508: PL/SQL: Could Not Find Program Unit Being Called; HZ_RELATIONSHIPS_PKG (Doc ID 1291931.1)

Oracle EBS R12 Concurrent Managers Issue Resolution - Execute adrelink

Problem Description -
"Scheduler/Prereleaser Manager" is showing status "System Hold, Fix Manager before resetting counters".

Problem Solution -
To implement the solution, please execute the following steps:

1. Stop all middle tier services including the concurrent managers.
Please make sure that no FNDLIBR, FNDSM, or any dead process is
running.

2. Stop the database.

3. Start the database.

4. Go to cd $FND_TOP/bin
$ adrelink.sh force=y link_debug=y "fnd FNDLIBR"
$ adrelink.sh force=y link_debug=y "fnd FNDFS"
$ adrelink.sh force=y link_debug=y "fnd FNDCRM"
$ adrelink.sh force=y link_debug=y "fnd FNDSM"

5. Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).
Note 134007.1 CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables

6. Execute the following SQL:
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where
CONCURRENT_QUEUE_NAME like 'FNDSM%';

7. Start the middle tier services including your concurrent manager.

8. Retest the issue.