Last updated on SEPTEMBER 08, 2017
Applies to:Oracle Project Costing - Version 22.214.171.124 to 126.96.36.199 [Release 11.5.10]
Information in this document applies to any platform.
After applying <Patch 9667497> (PALDLC - NEGATIVE EXEMPT EXCESS COST MUTLIPLIER NOT CALCULATED CORRECTLY) the package PA_INTEGRATION (PAXPINTB.pls) is invalid and will not compile.
Compilation of the package results in the following error:
Error(144,20): PLS-00306: wrong number or types of arguments in call to 'GET_INVOICE_STATUS'
The invalid package may result in a number of symptoms within the applications:
1. Users are unable to transfer expenditures from one project/task to another in the PAXTRAPE Expenditure Inquiry form. Doing so encounters error:
ORA-04063: package body "APPS.PA_INTEGRATION" has error
ORA-06508: PL/SQL: could not find program unit being called "APPS.PA_INTEGRATION"
ORA-06512: at "APPS.PA_ADJUSTMENTS", line 1854
2. When running PRC: Interface Supplier Costs, the below error is shown in the log file:
Error in import1 procedure
08:48:58: Import1: log_message: Stage=In OTHERS exception of import1
08:48:58: Import1: log_message: ORA-06508: PL/SQL: could not find program unit being called
08:48:58: transaction import failed with sqlcode =
08:48:58: ORA-20003: import1_prog:ORA-06508: PL/SQL: could not find program unit being calledIn OTHERS exception of import1
Application of <patch 9667497> or any similar patch which includes the file PAXPINTB.pls version 115.21.
Some, like 9667497, will correctly indicate the fix for AP <bug 8529082> as a pre or co-requisite, others do not mention this requirement in their README files.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms