Sr 3 2057791987 price lease opportunity ora-06503 plsql function returned without value in package okl-pricing_u

Page Printed:
November 15, 2010
4:25:49 PM GMT+07:00
SR 3-2057791987: Price Lease Opportunity: ORA-06503:
PL/SQL: Function returned without value in Package
OKL_PRICING_U
Information
Request
Number 3-2057791987 Filed By THUNTD_ALC2@PYTHIS.COM
Primary
Contact Thu Nguyen Tran Dan
Primary Contact
Phone (084) 384-8460 x8
Alternate
Contact duy pham
Alternate Contact
Phone 08 3 8484608
Status Resolved with solution Severity 2
Support ID 16474694
Legacy SR
Number
Opened
August 27, 2010 10:54:09 AM
GMT+07:00 Last Update
October 1, 2010 7:26:55 PM
GMT+07:00
Product
Oracle Lease and Finance
Management Product Version 12.1.2
Platform Linux x86
History
Oracle Support - October 1, 2010 4:05:32 AM GMT+07:00 [Information]
Generic Note
------------------------
Created Note 1224143.1 for the setup issue.
We have the other two SRs to document the 11i code in R12 issue if need be.
Closing this SR as requested as the issue is resolved.
Oracle Support - October 1, 2010 3:57:06 AM GMT+07:00 [ODM Solution/Action Plan]
=== ODM Solution / Action Plan ===
Using the seeded Credit Management Super User responsibility select the Policy Management tab and
then the System Options sub-tab.
Complete the setup in this page selecting a value for Default Customer Credit Classification and save the
changes.
Note that Aging Bucket is a required field in this page a this value can NOT be changed once saved.
Before saving this setup a decision must be made on which value to use for Aging Bucket.
Oracle Support - October 1, 2010 3:54:47 AM GMT+07:00 [ODM Proposed Solution Justif]
=== ODM Proposed Solution Justif ===
Once this setup is complete there will be a value available for the function to find and it will not return
without a value.

Oracle Support - October 1, 2010 3:54:03 AM GMT+07:00 [ODM Proposed Solution(s)]
=== ODM Proposed Solution ===
Complete the System Options setup in Credit Management.
Oracle Support - October 1, 2010 3:53:27 AM GMT+07:00 [ODM Cause Justification]
=== ODM Cause Justification ===
In OKL_PRICING_UTILS_PVT.price_standard_quote_asset a call is being made to to a function named
okl_lease_app_pvt.get_credit_classfication which will ultimately try to get the Default Customer Credit
Classification from the Credit Management System Options setup.
This function is returning with a value because this setup is not completed in Credit Management.
Oracle Support - October 1, 2010 3:48:34 AM GMT+07:00 [ODM Cause Determination]
=== ODM Cause Determination ===
The setup for Credit Management's System Options has not been completed or is missing a value for
Default Customer Credit Classification.
Oracle Support - October 1, 2010 3:42:43 AM GMT+07:00 [ODM Issue Verification]
=== ODM Issue Verification ===
Verified in the screen shots provided.
Oracle Support - October 1, 2010 3:42:07 AM GMT+07:00 [ODM Issue Clarification]
=== ODM Issue Clarification ===
On : 12.1.2 version, Sales & Origination
When attempting to validate and price a Quote within a Lease Opportunity,
the following error occurs.
ERROR
-----------------------
ORA-06503: PL/SQL: Function returned without value in Package OKL_PRICING_UTILS_PVT procedure
price_standard_quote
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a Quote within a Lease Opportunity.
2. Complete the entry into the Quote as required.
3. Click the Validate and Price button in the Quote.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot price the Quotes which prevents further processing of the Quote.
Oracle Support - October 1, 2010 3:22:57 AM GMT+07:00 [Information]
Generic Note

------------------------
We had a few issues in a few SRs, most of which seemed to be caused by the 11i OKL code in the R12
instance.
However, this one persisted after we compiled the R12 code and was determined to be a valid R12
setup issue.
I need to document that in a note and then close this SR as requested.
DUYPM@PYTHIS.COM - September 28, 2010 12:26:19 PM GMT+07:00 [Close Requested By
Customer]
Hi,
The issue is resolved.
Thanks for your help!
DuyPM
Oracle Support - September 26, 2010 11:24:18 PM GMT+07:00 [Information]
Generic Note
------------------------
Duy,
In my instance the only field that cannot be updated, because this setup has already been saved, if the
Aging Bucket. In your shot that also seems to be the one that you're asking about.
I got this from the help link for the OCM System Options page:
--------------------------------------------------------------------
Aging Bucket
Specify which aging buckets to use when presenting aging data in Credit Management. Credit
Management presents aging data as data points in several pages, such as from the Aging Details and
Credit Summary pages.
Note: To ensure that credit review comparisons display consistent aging data, you cannot change this
system option once you have saved it.
--------------------------------------------------------------------
If you have no values available in the Aging Bucket field, those are defined in Receibles using this
navigation:
Setup > Collections > Aging Buckets and Interest Tiers
If you have values but don't know which to pick then there's not much I can do to help with that as that
would depend on your business requirements. You may want to run this buy the Business to see what
they would like to use. The other option would be to just select one, I believe one with the name
"Standard" may be seeded, and use that in this instance. It may not be exactly what the users want, but
it would get things working and the value can be set differently in the next instance if required.
Kenny

DUYPM@PYTHIS.COM - September 26, 2010 11:02:45 PM GMT+07:00 [Update from
Customer]
Hi,
My system have values as picture (I uploaded). Please help to give standard values for solving these
issues what is values I need to setup?
Thanks
DuyPM
Customer]
Uploaded Attachment 9_26_2010_10_55_55_PM.png in GTCR
Oracle Support - September 26, 2010 7:01:02 PM GMT+07:00 [ODM Action Plan]
=== ODM Action Plan ===
Duy,
Using the Credit Management Super User responsibility select the Policy Management tab and then the
System Options sub-tab. Please verify that a value is defined in the Default Customer Credit
Classification field. If this is not set please select a value in this field, save and then re-test this issue.
Kenny
Oracle Support - September 26, 2010 6:47:19 PM GMT+07:00 [ODM Research]
=== ODM Research ===
Bug 6474290 and 6060742 both mention the following solution for the same error:
----------------------
setup 'Default Customer Credit Classification' using following navigation Credit management > Policy
Management > System Options.
----------------------
Checking that setup now.
Customer]
Hi,
The issue is still for all. In document, you can see error in LO1176 picture, this LO is created new.
Please review document erro_picture_01.doc (I uploaded).
Please give me solution resolve for all of case!
Thanks
DuyPM
Customer]

Uploaded Attachment error_picture_01.doc in GTCR
Duy,
Going by the Lease Opportunity Numbers in the screen shot you provided today (LO55) and the one you
provided when the SR was opened (LO80) it appears that you are using existing Lease Opportunities
and Quotes. I believe that those may have been created incorrectly due to the number of files we had
with incorrect versions. Can you please create a fresh test case for these and let me know if those hit
the same error? Please do not copy from an any existing Lease Opportunity or Quote to complete this
test.
Thanks,
Kenny
DUYPM@PYTHIS.COM - September 26, 2010 11:10:15 AM GMT+07:00 [Update from
Customer]
Hi,
The issue is still. Please review Document file (error_picture.docx).
Please have a look and give me solution!
thanks
DuyPM
Customer]
Uploaded Attachment error_picture.docx in GTCR
Oracle Support - September 26, 2010 9:25:54 AM GMT+07:00 [Information]
Generic Note
------------------------
Duy,
The apps check looks a lot better. There are a couple invalids, both of which are related to Vendor
Program Agreements and should not impact any of the issues that we have in the 3 open SRs that I
have with you and Thu. Before you start testing it might be a good idea to complete the steps below.
We've done a lot of compiling so I think its probably a good idea to make sure other application files
are valid by compiling with adadmin, then bouncing apache and clearing the cache to get a fresh start
there. Please complete these steps to do that:
1. Compile the APPS schema using adadmin.
2. Bounce apache.
3. Log into the applications and select the Functional Administrator responsibility. From there:
a. Select the Core Services tab.
b. Select the Caching Framework sub-tab.

c. Select Global Configuration in the left pane.
d. Click the Clear All Cache button in the Cache Policy section of this page.
e. Click Yes in the confirmation page that opens.
Once these steps are completed please re-test the issues in all of our open SRs and update each of the
SRs to let me know if the issue still exists. In the meantime I'll see what I can find on these last OKL
two packages that are invalid.
Thanks,
Kenny
Oracle Support - September 26, 2010 9:18:42 AM GMT+07:00 [ODM Data Collection]
Name
--------
ODM Data Collection
Apps Check Output
FileName
----------------
Diagnostics__Apps_Check_260910_0045.txt
FileComment
----------------------
Two invalids, different ones that we've had before:
-----------------------------------------------------------------------
OKL_VP_K_ARTICLE_PUB_W OKLUCARB.pls 120.3 BODY INVALID
Errors for PACKAGE BODY OKL_VP_K_ARTICLE_PUB_W
PLS-00306: wrong number or types of arguments in call to 'ROSETTA_TABLE_COPY_IN_P3'
PL/SQL: Statement ignored
PLS-00306: wrong number or types of arguments in call to 'ROSETTA_TABLE_COPY_OUT_P3'
PLS-00306: wrong number or types of arguments in call to 'ROSETTA_TABLE_COPY_OUT_P3'
-----------------------------------------------------------------------
OKL_VP_SYNC_CR_PVT OKLRCRSB.pls 120.15 BODY INVALID
Errors for PACKAGE BODY OKL_VP_SYNC_CR_PVT
PLS-00306: wrong number or types of arguments in call to 'DELETE_K_ARTICLE'
PLS-00306: wrong number or types of arguments in call to 'CREATE_K_ARTICLE'
-----------------------------------------------------------------------

These packages are related to Vendor Program Agreements.
While they should be valid, they would not impact any of the issues we have in this or the relates SRs.
Generic Note
------------------------
Reviewing --Kenny
Customer]
Uploaded Attachment Diagnostics__Apps_Check_260910_0045.txt in GTCR
Customer]
Hi,
I removed the lines for OKLVSHKS.pls and OKLVSHKB.pls. And ran shell script without these lines. I
upload Diagnostice apps check file again. Please review it!
Please have a look!
Thanks
DuyPM
Generic Note
------------------------
Duy,
Actually, you can remove the lines for OKLVSHKS.pls and OKLVSHKB.pls. I checked OKLVSHKS.pls and
that file has been stubbed out to have nothing in it. So we didn't need OKLVSHKS.pls or OKLVSHKB.pls.
Kenny
Generic Note
------------------------
Duy,
Please remove the line with OKLVSHKB.pls in the shell script. I added this because the file
OKLVSHKS.pls was in the list and I assumed that if there was a spec there would be a body. For
whatever reason in this case that seems to not be the case.
Kenny
Customer]
Hi,

I uploaded Diagnostice apps check. Please review it.
When I complie package, I can't find package $OKL_TOP/patch/115/sql/OKLVSHKB.pls.
Please check and give me solution as soon as possible!
Thanks
DuyPM
Customer]
Uploaded Attachment Diagnostics__Apps_Check_260910.txt in GTCR
Duy,
I have uploaded a couple of files to the SR. Those were File_Comparisons.xls and oklcompile.sh. I
created File_Comparisons.xls in Excel to build a list of files in the instance that have one file version
compiled in the database and another version in the $OKL_TOP/patch/115/sql directory. In this sheet I
built the list of these files and then reviewed that list to make sure that we're compiling everything we
need.
I then took the final list in File_Comparisons.xls and created oklcompile.sh to compile all files in the list
of mismatched versions. Please download a copy of oklcompile.sh from the SR. Before running this file
please open it and use the Find > Replace function in a text editor to update the value for the apps
password. I used the value apps_pw for this, so you can find that string and replace it with the actual
password. Once all of the "apps_pw" values are updated, please save the changes and execute this file
at the unix prompt. Once this completes all of your compiled pls versions should match the versions in
OKL_TOP. This should also resolve most, if not all, of the issues in our open SRs.
Please update to let me know. Please also provide the information requested in the last action plan.
Thank you,
Kenny
Oracle Support - September 25, 2010 10:52:44 PM GMT+07:00 [Notes]
Uploaded Attachment oklcompile.sh in GTCR
Uploaded Attachment File_Comparisons.xls in GTCR
Duy,
We're down to only 2 invalids, both hitting errors referencing ORIG_CONTRACT_LINE_ID. This string is

used in two ways in these files. In some cases it is used as part of a record type, in other cases it is
used as a field in the table OKL_K_LINES. I believe we have the record fixed, but to be sure I'll need to
know exactly where these two files are erroring.
Please run this command at the SQL prompt:
SQL> alter package OKL_COPY_CONTRACT_PVT compile body;
I expect that to error. After you get the error please use this command to print the errors
SQL> show errors
Please copy the entire output of these errors to the SR. These errors indicate the line numbers of where
the error is being hit which will tell me exactly what use of ORIG_CONTRACT_LINE_ID is causing the
error.
Then repeat the same for OKL_CREATE_STREAMS_PVT:
SQL> alter package OKL_CREATE_STREAMS_PVT compile body;
SQL> show errors
Copy these errors into the SR too.
I am now going through the apps check provided to make sure that the pls file versions that you have
compiled match the versions that you have in $OKL_TOP. We have everything just about valid now, but
there's still a chance that some files are not in the correct versions. And while the differences in them
may not be enough to cause them to be invalid, they could cause other issues within the application. I
hope to have that matching completed shortly.
Thanks,
Kenny
Oracle Support - September 25, 2010 9:29:39 PM GMT+07:00 [ODM Data Collection]
Name
--------
ODM Data Collection
Apps Check, down to 2 invalids...
FileName
----------------
Diagnostics__Apps_Check_250910_2117.txt
FileComment
----------------------
OKL_COPY_CONTRACT_PVT OKLRCOPB.pls 120.50.12010000.5 BODY INVALID
Errors for PACKAGE BODY OKL_COPY_CONTRACT_PVT
PLS-00302: component 'ORIG_CONTRACT_LINE_ID' must be declared

PL/SQL: SQL Statement ignored
OKL_CREATE_STREAMS_PVT OKLRCSMB.pls 120.30.12010000.8 BODY INVALID
Errors for PACKAGE BODY OKL_CREATE_STREAMS_PVT
Generic Note
------------------------
Thanks Duy, I am reviewing now. --Kenny
Customer]
Hi,
I uploaded Diagnostics apps checks. please check again and give me solution as soon as possible!
Thanks
DuyPM
Customer]
Uploaded Attachment Diagnostics__Apps_Check_250910_2117.txt in GTCR
Thu and Duy,
I kept digging into the errors with ORIG_CONTRACT_LINE_ID and determined that the error is probably
not due to this field missing from the table. I found that it is not defined in the record type being used
in these packages. I have modified the last action plan so that we can now address that problem.

We still need to compile these from the last action plan:
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLPCSMS.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLPCSMB.pls
Now to get the ORIG_CONTRACT_LINE_ID errors resolved we need to compile these:
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLSKLES.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLSKLEB.pls
Once those are in place the other files should compile without issue.
We could compile these with adadmin, but since we're already using the above method we can just
keep going with that:
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRCOPB.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRCSMB.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRSBPB.pls
Once those are compiled we should be left with one OKL invalid, the package body
OKL_SIMPLE_PRICING_PVT.
This package is obsolete, and was only compiled when we compiled all pls files in OKL_TOP.
So to get rid of this invalid we can simply drop it using this command at the SQL prompt:
drop package OKL_SIMPLE_PRICING_PVT;
Please upload another Apps Check output after this action plan has been completed so that I can verify
that all packages are valid and have an up to date snapshot of the instance.
Thanks,
Kenny
Thu and Chuong,
Please run the following at the unix prompt (substituting the apps password):
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLPCSMS.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLPCSMB.pls
After these are compiled the package body for OKL_LA_STREAM_PVT should now be valid.
Next we need to check to see if the field ORIG_CONTRACT_LINE_ID exists in the table okl_k_lines.
To do that please run this select statement in the instance:
select ORIG_CONTRACT_LINE_ID
from okl_k_lines;
If you get an error like this:

ORA-00904: "ORIG_CONTRACT_LINE_ID": invalid identifier
then we need to get this field into this table using OKLCONR.odf.
I'll work to get the syntax to do that once we confirm that we need it.
Please update to let me know if this select statement runs with or without error.
Thanks,
Kenny
Research
========
In OKLRSGAB.pls 120.141.12010000.32:
IF p_orp_code IS NOT NULL
THEN
l_csm_loan_header.orp_code := OKL_CREATE_STREAMS_PUB.G_ORP_CODE_UPGRADE;
ELSE
l_csm_loan_header.orp_code := OKL_CREATE_STREAMS_PUB.G_ORP_CODE_BOOKING;
END IF;
-- l_csm_loan_header.orp_code := OKL_CREATE_STREAMS_PUB.G_ORP_CODE_BOOKING;
Looks like G_ORP_CODE_UPGRADE is not in the spec for OKL_CREATE_STREAMS_PUB.
Spec for OKL_CREATE_STREAMS_PUB is OKLPCSMS.pls and according to the apps check the compiled
version is 120.1.
And the version in OKL_TOP is 120.1.12010000.2.
So we need to compile OKLPCSMS.pls from OKL_TOP, which means we then need to compile
OKLPCSMB.pls from here too.
The rest of the packages that are invalid all reference ORIG_CONTRACT_LINE_ID.
And as I mentioned yesterday, that field should have been added to okl_k_lines via OKLCONR.odf.
Apps Check shows OKLCONR.odf is version 120.51.12010000.7, which is fine.
So we'll check for this field and if its not there we need to load this odf.
Name
--------
ODM Data Collection
Apps Check Output
Down to 4 that matter (OKL_SIMPLE_PRICING_PVT is obsolete)
FileName
----------------
Diagnostics__Apps_Check_250910.txt
FileComment

----------------------
--------------------------------------------------------------------------
OKL_COPY_CONTRACT_PVT OKLRCOPS.pls 120.3.12010000.1 SPEC VALID
--------------------------------------------------------------------------
--------------------------------------------------------------------------
OKL_LA_STREAM_PVT OKLRSGAB.pls 120.141.12010000.32 BODY INVALID
Errors for PACKAGE BODY OKL_LA_STREAM_PVT
PLS-00302: component 'G_ORP_CODE_UPGRADE' must be declared
PLS-00302: component 'G_ORP_CODE_UPGRADE' must be declared
--------------------------------------------------------------------------
OKL_SUBSIDY_PROCESS_PVT OKLRSBPB.pls 120.27.12010000.7 BODY INVALID

Errors for PACKAGE BODY OKL_SUBSIDY_PROCESS_PVT
--------------------------------------------------------------------------
Generic Note
------------------------
Reviewing --Kenny
Customer]
Contact Info: Hi,
Please update contact to us as below:
- Contact information :
- Technical resource (primary contact) :
- Duy
- skype : ptshcm_duypm
- email: duypm@pythis.com
- Cell : (84) 907 58 11 59 (VietNam)
- Functional :
- thu
- skype : ptshcm_thuntd
- email: thuntd@pythis.com
- cell : (84) 979 597 799 (VietNam)
Please send all information about SR to emails duypm@pythis.com and thuntd@pythis.com
Time zone is GMT +7
Thanks
DuyPM
Customer]
Hi,
I completed the action plan but the issue is still. Please check logfiles!
Note: We upgraded my system to R12.1.3 but the issue is still. I uploaded log file patch
R12.AD.B.DELTA.3 Patch 9239089. Please review it!
Please have a look and give me solution as soon as possible!
Thanks
DuyPM

Customer]
Uploaded Attachment log.zip in GTCR
Customer]
Oracle Support - September 25, 2010 4:26:35 AM GMT+07:00 [ODM Action Plan]
Thu and Chuong
Can you please complete the action plan below and update with the requested information?
Thanks,
Kenny
1. Please execute the following statements at the unix prompt to compile these pls files in the instance
used to provide the latest Apps Check output you uploaded. Be sure to change the second "apps" to
your actual apps user's password.
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRLAUS.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRLAUB.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRSGAS.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRSGAB.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRCFES.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRCFEB.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRCOPS.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRCSMS.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRLFES.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRLFEB.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRPIGS.pls
sqlplus apps/apps @$OKL_TOP/patch/115/sql/OKLRPIGB.pls
2. Once these complete please compile the APPS schema using adadmin. Please upload the adadmin log
file and the log files for all workers.
3. Bounce apache.
4. Log into the applications and select the Functional Administrator responsibility. From there:
a. Select the Core Services tab.
b. Select the Caching Framework sub-tab.
c. Select Global Configuration in the left pane.
d. Click the Clear All Cache button in the Cache Policy section of this page.
e. Click Yes in the confirmation page that opens.

5. Re-test the issues in this SR and the related Lease Management SRs.
6. Please upload a new output for the Diagnostics: Apps Check report run for Lease Management.
We'll want to verify the status of everything after the compilations completed above.
7. Please also provide the adpatch log, and the logs for all workers for the application of
Patch 7303033 (12.1.2) and patch 9451692 (OKL RUP2) if you have them. We will need these
to help figure out what caused this issue.
Generic Note
------------------------
Called Thu at the number in the SR, (084) 384-8460 x8.
Call was answered by a machine with a greeting.
Unable to understand the greeting.
Greeting ended, followed by a disconnection.
84-985 353 625 provided by Chuong earlier in the SR.
Sounded like he answered but he was unable to hear me.
84 -8 -985 353 625 - answered by what sounded like a fax machine
84 -8 - 979 597 799 - answered by what sounded like a fax machine
Found milestone and contact info in the SR:
- Next milestone to UAT is September 27
- chuong
- skype : ptshcm_chuongnh
- Cell : 84 -8 -985 353 625 (VietNam)
- Functional :
- thu
- cell : 84 -8 - 979 597 799
Action Plan
===========
Thu,
Please execute the following statements at the unix prompt to compile these pls files in the instance
used to provide the latest Apps Check output you uploaded. Be sure to change the second "apps" to
your actual apps user's password.

Once these complete please compile the APPS schema using adadmin. Please upload the adadmin log
file and the log files for all workers. Please also provide the adpatch log, and the logs for all workers for
the application of Patch 7303033 (12.1.2) and patch 9451692 (OKL RUP2) if you have them.
To escalate this issue to a Severity 1 we will need 24/7 contact information for a functional and technical
resource. We will also need some information on your project milestones (CRP, UAT, etc.), with dates.
We would also usually need information on why you can't continue with this issue, but in this case I
think that's pretty clear. Can you please update to provide the contact and milestone information? In the
meantime I am going to be researching this issue.
Thanks,
Kenny
Oracle Support - September 25, 2010 1:32:27 AM GMT+07:00 [ODM Research]
Research
========
Have Need
OKLRLAUS.pls 120.12 120.12.12010000.4
OKLRLAUB.pls 120.18.12010000.2 120.18.12010000.7
OKLRSGAS.pls 120.13.12010000.2 120.13.12010000.8
OKLRCFES.pls 120.2.12010000.5 120.2.12010000.6
OKLRCOPS.pls 120.3 120.3.12010000.1
OKLRCSMS.pls 120.11 120.11.12010000.5
OKLRLFES.pls 120.0.12010000.5 120.0.12010000.6
OKLRSGAS.pls 120.13.12010000.2 120.13.12010000.8
OKLRPIGS.pls 120.9 120.9.12010000.2
Apps Check also shows versions in OKL_TOP:
patch/115/sql/OKLRLAUS.pls 120.12.12010000.4
patch/115/sql/OKLRLAUB.pls 120.18.12010000.8
patch/115/sql/OKLRSGAS.pls 120.13.12010000.8
patch/115/sql/OKLRCFES.pls 120.2.12010000.6
patch/115/sql/OKLRCOPS.pls 120.3.12010000.1

patch/115/sql/OKLRCSMS.pls 120.11.12010000.5
patch/115/sql/OKLRLFES.pls 120.0.12010000.6
patch/115/sql/OKLRSGAS.pls 120.13.12010000.8
patch/115/sql/OKLRPIGS.pls 120.9.12010000.2
So we have what we need, we just need to compile these pls files.
Research
========
----------------------------------------------------------------------
Error #1
OKL_ACTIVATE_CONTRACT_PUB OKLPACOB.pls 120.26.12010000.7 BODY
INVALID
Errors for PACKAGE BODY OKL_ACTIVATE_CONTRACT_PUB
PLS-00302: component 'CHECK_REBOOK_UPGRADE' must be declared
In this file:
OKL_LLA_UTIL_PVT.check_rebook_upgrade
In Apps Check OKL_LLA_UTIL_PVT is OKLRLAUS.pls 120.12 and OKLRLAUB.pls 120.18.12010000.2.
check_rebook_upgrade introduced in OKLRLAUB.pls 120.18.12010000.7 and OKLRLAUS.pls
120.12.12010000.4 via Bug 8756653.
Patch 7303033 contains OKLRLAUB.pls 120.18.12010000.8 and OKLRLAUS.pls 120.12.12010000.4
So these should be in OKL_TOP.

----------------------------------------------------------------------
Error #2
OKL_BOOK_CONTROLLER_PVT OKLRBCTB.pls 120.8.12010000.4 BODY
INVALID
Errors for PACKAGE BODY OKL_BOOK_CONTROLLER_PVT
PLS-00302: component 'UPDATE_EXTERNAL_ID' must be declared
PLS-00302: component 'UPGRADE_ESG_KHR_FOR_PRB' must be declared
In OKLRBCTB.pls 120.8.12010000.4:
OKL_LLA_UTIL_PVT.update_external_id(p_chr_id => l_chr_rec.orig_chr_id,
OKL_LA_STREAM_PVT.upgrade_esg_khr_for_prb
UPDATE_EXTERNAL_ID is in the version of OKLRLAUB.pls noted in Error #1.
Apps check shows OKL_LA_STREAM_PVT is OKLRSGAS.pls 120.13.12010000.2 and OKLRSGAB.pls
120.141.12010000.32 (invalid).
OKLRSGAB.pls seems to be the correct version.
However, OKLRSGAS.pls 120.13.12010000.2 is the 12.1.1 version.
Patch 7303033 contains 120.13.12010000.8, and this version will work.
----------------------------------------------------------------------
Error #3
OKL_CNTRCT_FIN_EXTRACT_PVT OKLRCFEB.pls 120.2.12010000.19 BODY
INVALID
Errors for PACKAGE BODY OKL_CNTRCT_FIN_EXTRACT_PVT
PLS-00323: subprogram or cursor 'PULL_EXTRACT_DATA_CONC' is declared in a package specification
and
PLS-00323: subprogram or cursor 'PULL_EXTRACT_DATA' is declared in a package specification and
must
For this one the error says that the procedure is in the spec but not the body.
I checked this version of OKLRCFEB.pls and these procedures are there.
So there must be a signature mismatch.
Apps check says we have OKLRCFES.pls 120.2.12010000.5
Patch 7303033 contains version 120.2.12010000.6, which is the one we want as there are changes to
the parameters for these procedures.
----------------------------------------------------------------------
Error #4
OKL_CONTRACT_BOOK_PVT OKLRBKGB.pls 120.63.12010000.6 BODY INVALID

Errors for PACKAGE BODY OKL_CONTRACT_BOOK_PVT
In this file:
Same as in Error #1.
----------------------------------------------------------------------
Error #5
ORIG_CONTRACT_LINE_ID is in a few places.
Apps Check shows OKLRCOPS.pls 120.3.
We want 120.3.12010000.1, which is in Patch 7303033.
----------------------------------------------------------------------
Error #6
PLS-00201: identifier 'G_ORP_CODE_UPGRADE' must be declared
PLS-00302: component 'DATE_PAID' must be declared

Again, all over, apps check shows OKLRCSMS.pls 120.11.
We want 120.11.12010000.5 from Patch 7303033.
----------------------------------------------------------------------
Error #7
OKL_DEAL_CREAT_PVT OKLRDCRB.pls 120.5.12010000.9 BODY INVALID
Errors for PACKAGE BODY OKL_DEAL_CREAT_PVT
PLS-00302: component 'GET_LAST_ACTIVATION_DATE' must be declared
In this file:
--Bug# 8370699
X_DEAL_VALUES_REC.LAST_ACTIVATION_DATE :=
OKL_LLA_UTIL_PVT.GET_LAST_ACTIVATION_DATE(p_chr_id => p_chr_id);
Need the same file as in Error #1.
----------------------------------------------------------------------
Error #8
OKL_K_LINE_FIN_EXT_PVT OKLRLFEB.pls 120.0.12010000.38 BODY INVALID
Errors for PACKAGE BODY OKL_K_LINE_FIN_EXT_PVT
and
must
Apps Check shows OKLRLFES.pls 120.0.12010000.5.
----------------------------------------------------------------------
Error #9
PLS-00313: 'GENERATE_PASSTHRU_EXP_STREAMS' not declared in this scope
PLS-00302: component 'PROSP_ADJ_ACC_STRMS' must be declared

Apps check shows OKLRSGAS.pls 120.13.12010000.2.
----------------------------------------------------------------------
Error #10
OKL_MASS_REBOOK_PVT OKLRMRPB.pls 120.33.12010000.5 BODY INVALID
Errors for PACKAGE BODY OKL_MASS_REBOOK_PVT
In this file:
Same as #1
----------------------------------------------------------------------
Error #11
OKL_PRB_UPGRADE_PVT OKLRPRBB.pls 120.0.12010000.6 BODY INVALID
Errors for PACKAGE BODY OKL_PRB_UPGRADE_PVT
In this file:
OKL_LLA_UTIL_PVT.update_external_id(p_chr_id => l_esg_upg_cntrcts_tbl(i).khr_id,
Same as #1

okl_la_stream_pvt.upgrade_esg_khr_for_prb
As in #2, we want OKLRSGAS.pls 120.13.12010000.8 from Patch 7303033.
----------------------------------------------------------------------
Error #12
OKL_PRICING_PVT OKLRPIGB.pls 120.76.12010000.4 BODY INVALID
Errors for PACKAGE BODY OKL_PRICING_PVT
PLS-00302: component 'GET_DAY_COUNT_METHOD' must be declared
PLS-00306: wrong number or types of arguments in call to 'COMPUTE_BK_YIELD'
PLS-00323: subprogram or cursor 'GET_LOAN_AMORTIZATION' is declared in a package specification
and m
From this file:
okl_pricing_utils_pvt.get_day_count_method(
okl_pricing_utils_pvt.compute_bk_yield(
Apps check says okl_pricing_utils_pvt is OKLRPIUS.pls 120.8.12010000.3 and OKLRPIUB.pls
120.75.12010000.4.
These seem fine, not sure yet why we're getting these. Moving on, maybe they will go away when we
get everything
else in order. I must be missing something with these.
And the error for GET_LOAN_AMORTIZATION implies that the spec for this file is incorrect.
Apps check says that is OKLRPIGS.pls 120.9, we want 120.9.12010000.2 from Patch 7303033.
----------------------------------------------------------------------
Error #13
OKL_QA_DATA_INTEGRITY OKLRQADB.pls 120.153.12010000.24 BODY INVALID
Errors for PACKAGE BODY OKL_QA_DATA_INTEGRITY
PLS-00302: component 'GET_PTH_FEE_DUE_AMOUNT' must be declared
In this file:
OKL_LA_STREAM_PVT.get_pth_fee_due_amount(p_chr_id => p_chr_id,
OKL_LA_STREAM_PVT.get_pth_fee_due_amount(p_chr_id => p_chr_id,

----------------------------------------------------------------------
Error #14
OKL_STREAM_GENERATOR_PVT OKLRSGPB.pls 120.101.12010000.14 BODY
INVALID
Errors for PACKAGE BODY OKL_STREAM_GENERATOR_PVT
PLS-00306: wrong number or types of arguments in call to 'GET_LOAN_AMORTIZATION'
PLS-00302: component 'GENERATE_PASSTHRU_EXP_STREAMS' must be declared
In this file:
OKL_PRICING_PVT.get_loan_amortization(p_khr_id => p_khr_id,
OKL_PRICING_PVT.get_loan_amortization(
These two are as mysterious as in Error #12.
OKL_LA_STREAM_PVT.GENERATE_PASSTHRU_EXP_STREAMS
----------------------------------------------------------------------
Error #15
ORIG_CONTRACT_LINE_ID is used as part of this record:
l_sub_klev_rec okl_contract_pub.klev_rec_type;
okl_contract_pub is OKLPKHRS.pls 120.1 and OKLPKHRB.pls 120.2.
Those also look fine.
Digging in more it would seem that maybe table okl_k_lines was not updated during patching to include
column ORIG_CONTRACT_LINE_ID.
This field was added in OKLCONR.odf 120.51.12010000.2, also in Patch 7303033.
Apps Check says we have OKLCONR.odf 120.51.12010000.7.
May need to look into this one more later too.
----------------------------------------------------------------------

Generic Note
------------------------
Thu,
To escalate this issue to a Severity 1 we will need 24/7 contact information for a functional and technical
resource. We will also need some information on your project milestones (CRP, UAT, etc.), with dates.
We would also usually need information on why you can't continue with this issue, but in this case I
think that's pretty clear. Can you please update to provide the contact and milestone information? In the
meantime I am going to be researching this issue.
Thanks,
Kenny
Customer]
Hi,
This issue is very serious. We can't continue project. Please raise this SR to Severity 1 (highest level).
Please have a look!
Thanks
DuyPM
Name
--------
ODM Data Collection
Apps Check Output
Still some invalids remain...
FileName
----------------
Informations.zip
FileComment
----------------------
----------------------------------------------------------------------
OKL_ACTIVATE_CONTRACT_PUB OKLPACOB.pls 120.26.12010000.7 BODY
INVALID
----------------------------------------------------------------------
OKL_BOOK_CONTROLLER_PVT OKLRBCTB.pls 120.8.12010000.4 BODY

INVALID
Errors for PACKAGE BODY OKL_BOOK_CONTROLLER_PVT
----------------------------------------------------------------------
OKL_CNTRCT_FIN_EXTRACT_PVT OKLRCFEB.pls 120.2.12010000.19 BODY
INVALID
Errors for PACKAGE BODY OKL_CNTRCT_FIN_EXTRACT_PVT
and
must
----------------------------------------------------------------------
OKL_CONTRACT_BOOK_PVT OKLRBKGB.pls 120.63.12010000.6 BODY INVALID
Errors for PACKAGE BODY OKL_CONTRACT_BOOK_PVT
----------------------------------------------------------------------
----------------------------------------------------------------------

PLS-00302: component 'DATE_PAID' must be declared
----------------------------------------------------------------------
OKL_DEAL_CREAT_PVT OKLRDCRB.pls 120.5.12010000.9 BODY INVALID
Errors for PACKAGE BODY OKL_DEAL_CREAT_PVT
PLS-00302: component 'GET_LAST_ACTIVATION_DATE' must be declared
----------------------------------------------------------------------
OKL_K_LINE_FIN_EXT_PVT OKLRLFEB.pls 120.0.12010000.38 BODY INVALID
Errors for PACKAGE BODY OKL_K_LINE_FIN_EXT_PVT
and
must
----------------------------------------------------------------------
PLS-00313: 'GENERATE_PASSTHRU_EXP_STREAMS' not declared in this scope
PLS-00302: component 'PROSP_ADJ_ACC_STRMS' must be declared

----------------------------------------------------------------------
OKL_MASS_REBOOK_PVT OKLRMRPB.pls 120.33.12010000.5 BODY INVALID
Errors for PACKAGE BODY OKL_MASS_REBOOK_PVT
----------------------------------------------------------------------
OKL_PRB_UPGRADE_PVT OKLRPRBB.pls 120.0.12010000.6 BODY INVALID
Errors for PACKAGE BODY OKL_PRB_UPGRADE_PVT
----------------------------------------------------------------------
OKL_PRICING_PVT OKLRPIGB.pls 120.76.12010000.4 BODY INVALID
Errors for PACKAGE BODY OKL_PRICING_PVT
PLS-00302: component 'GET_DAY_COUNT_METHOD' must be declared
PLS-00306: wrong number or types of arguments in call to 'COMPUTE_BK_YIELD'
PLS-00323: subprogram or cursor 'GET_LOAN_AMORTIZATION' is declared in a package specification
and m
----------------------------------------------------------------------
OKL_QA_DATA_INTEGRITY OKLRQADB.pls 120.153.12010000.24 BODY INVALID
Errors for PACKAGE BODY OKL_QA_DATA_INTEGRITY

----------------------------------------------------------------------
OKL_STREAM_GENERATOR_PVT OKLRSGPB.pls 120.101.12010000.14 BODY
INVALID
Errors for PACKAGE BODY OKL_STREAM_GENERATOR_PVT
PLS-00302: component 'GENERATE_PASSTHRU_EXP_STREAMS' must be declared
----------------------------------------------------------------------
----------------------------------------------------------------------
Generic Note
------------------------
Reviewing--Kenny
THUNTD_ALC2@PYTHIS.COM - September 24, 2010 5:37:58 PM GMT+07:00 [Update from
Customer]
3. Patch 9451692 and its post-install patches are not errors
Customer]
Uploaded Attachment Informations.zip in GTCR
Customer]
Hi,
Must I re-apply patch 9451692:R12.OKL.B and its post-install patches?
Thanks
DuyPM

Customer]
Uploaded Attachment applied_patch.xls in GTCR
Customer]
Hi Thu,
Please do the following:
1. Provide the output of the following SQL:
SELECT DISTINCT a.bug_number, e.patch_name, c.end_date, b.applied_flag
FROM
ad_bugs a,
ad_patch_run_bugs b,
ad_patch_runs c,
ad_patch_drivers d ,
ad_applied_patches e
WHERE a.bug_id = b.bug_id
AND b.patch_run_id = c.patch_run_id
AND c.patch_driver_id = d.patch_driver_id
AND d.applied_patch_id = e.applied_patch_id
AND a.bug_number in (9451692,9843371,9433005)
ORDER BY 1 DESC;
2. Provide Apps Check output run for Oracle Lease Management product as the following:
(R) Oracle Order Management Super User
(N) Reports > Request > Run Request > Single Request
- Choose "Diagnostics: Apps Check", select 'Oracle Lease Management' from the LOV.
3. Confirm the status after applying Patch 9451692:R12.OKL.B and its post-install patches. Do you still
get any errors? If yes, upload screen shot of the error.
Regards,
Wael
Global Support Services
THUNTD_ALC2@PYTHIS.COM - September 24, 2010 8:27:24 AM GMT+07:00 [Update from
Customer]
Hi Kenny,

Patch 9451692 require 2 patch applied in post installation step is :
9843371 and 9433005.
Three patch are already applied onto system.
SQL> select * from ad_bugs where bug_number='9451692';
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BUG_NUMBER CREATION_DATE ARU_RELEASE_NAME
------------------------------ --------------- ------------------------------
CREATED_BY LAST_UPDATE_DAT LAST_UPDATED_BY TRACKABL
---------- --------------- --------------- --------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
394910
9451692 15-SEP-10 R12
5 15-SEP-10 5 okl
--------------------------------------------------------------
---------- --------------------------------------------------
------------------------------ --------------- ------------------------------
---------- --------------- --------------- --------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
393910
9843371 26-AUG-10 R12
5 26-AUG-10 5 okx
---------------------------------------------------------------
---------- --------------------------------------------------
------------------------------ --------------- ------------------------------
---------- --------------- --------------- --------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
394996
9433005 15-SEP-10 R12
5 15-SEP-10 5 ar

Thu,
The file that you hit the error in compiling, OKLRSGPB.pls, is also included in Patch 9451692:R12.OKL.B
which was requested in step 2 of the action plan Wael provided. With that file in this patch any
dependencies that may be causing the error in compilation are likely also included in this patch. So
oplease proceed with the action plan and apply Patch 9451692:R12.OKL.B. The is the latest roll up
patch for OKL on 12.1.2 and is going to be required in most if not all future OKL patches on 12.1.2.
Please also note that the readme for patch 9451692:R12.OKL.B includes a couple patches to be applied
after this one has completed. One is an OKX (Contracts Integration) patch and the other is an AR
patch. Please don't miss these. While they may not impact the current issues we're working they are
required and not having them applied could cause issues in other areas.
Once Patch 9451692:R12.OKL.B is applied please provide run the program Diagnostics: Apps Check
again for Lease Management and upload the output of that report to the SR. This report will show any
errors in compilation for any OKL invalids giving us a better idea of what is going wrong, if anything,
after this patch is applied.
Thank you,
Kenny
Customer]
Uploaded Attachment Up230910.txt in GTCR
Customer]
Hi Weal,
I run all the sql that you give, 1 error return. Please see the uploaded file.
Thanks
Hi Choung,
1. Connect to SQLPLUS as APPS user and run the following files:
SQL> @$OKL_TOP/patch/115/sql/OKLPAPIS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLPAPIB.pls
SQL> @$OKL_TOP/patch/115/sql/OKLPDEGS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLPDEGB.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRPIUS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRPIUB.pls

SQL> @$OKL_TOP/patch/115/sql/OKLRQQCS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRQQCB.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRQQHS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRQQHB.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRQUCS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRQUCB.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRSGPS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRSGPB.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRUTLS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLRUTLB.pls
SQL> @$OKL_TOP/patch/115/sql/OKLSQQLS.pls
SQL> @$OKL_TOP/patch/115/sql/OKLSQQLB.pls
Packages should be created successfully without any errors.
2. Apply Patch OLFM CONSOLIDATED PATCH 9451692:R12.OKL.B
3. Retest the flow and update the SR with the results.
Regards,
Wael
ISSUE ANALYSIS
----------------------
- The current error message is:
ORA-06508: PL/SQL: could not find program unit being called in Package OKL_QUICK_QUOTES_PVT
Procedure handle_quick_quote.
- Ran the following SQL to check on all dependent packages for OKL_QUICK_QUOTES_PVT package
SELECT owner, object_type, object_name
FROM dba_objects
WHERE object_type = 'PACKAGE BODY'
AND object_name like 'OKL%'
AND object_name IN (SELECT referenced_name
FROM dba_dependencies
WHERE name = 'OKL_QUICK_QUOTES_PVT');
OWNER OBJECT_TYPE OBJECT_NAME
---------- --------------------- ---------------------------------------------
APPS PACKAGE BODY OKL_API <- OKLPAPIB.pls
APPS PACKAGE BODY OKL_DEBUG_PUB <- OKLPDEGB.pls
APPS PACKAGE BODY OKL_PRICING_UTILS_PVT <- OKLRPIUB.pls
APPS PACKAGE BODY OKL_SALES_QUOTE_QA_PVT <- OKLRQQCB.pls
APPS PACKAGE BODY OKL_QUICK_QUOTES_PVT <- OKLRQQHB.pls
APPS PACKAGE BODY OKL_LEASE_QUOTE_CASHFLOW_PVT <- OKLRQUCB.pls

APPS PACKAGE BODY OKL_STREAM_GENERATOR_PVT <- OKLRSGPB.pls
APPS PACKAGE BODY OKL_UTIL <- OKLRUTLB.pls
APPS PACKAGE BODY OKL_QQH_PVT <- OKLSQQHB.pls
APPS PACKAGE BODY OKL_QQL_PVT <- OKLSQQLB.pls
- Reviewing the uploaded APPS Check for customer file versions against what Patch 9451692 OLFM :
CONSOLIDATED PATCH #2 ON R12.1.2 (SEP/2010) can offer us, found the following files can be
upgraded by this patch.
OKLPAPIB.pls 120.4 <- Latest released.
OKLPDEGB.pls 120.2 <- Latest released.
OKLRPIUB.pls 120.75.12010000.4 <- Latest released.
OKLRQQCB.pls 120.78 <- Patch 9451692 provides version 120.78.12010000.2
OKLRQQHB.pls 120.37.12010000.3 <- Latest released.
OKLRQUCB.pls 120.30.12010000.7 <- Latest released.
OKLRSGPB.pls 120.101.12010000.13 <- Patch 9451692 provides version 120.101.12010000.14
OKLRUTLB.pls 120.7.12010000.3 <- Latest released.
OKLSQQHB.pls 120.2.12010000.4 <- Latest released.
OKLSQQLB.pls 120.1 <- Latest released.
- Now, need to ensure that customer's environment have all the above packages of R12 version and
their status are VALID. Also, need to patch the environment with Patch 9451692
Oracle Support - September 23, 2010 10:14:20 AM GMT+07:00 [Call - Outbound]
Call - Outbound
------------------------------
- Called Choung on +84-985 353 625, he is on customer training and will not be able to join the OWC.
- Confirmed to him that I am going to update the SR with an action plan and based on that we can
decide the next course of actions.
Oracle Support - September 23, 2010 10:04:53 AM GMT+07:00 [Oracle Web Conference]
Oracle Web Conference: STRTC
--------------------------------------------------------
I have started a web conference using Oracle Collaboration Suite - Real Time Conferencing. Please
access this conference by going to:
https://strtc.oracle.com/imtapp/app/cmn_jm.uix?mID=7402601
Oracle Web Conferencing: Conference Key
------------------------------------------------------------------------------
Oracle Support - September 22, 2010 2:07:01 PM GMT+07:00 [Call - Outbound]
Call - Outbound
------------------------------
- Called again on the same number finally got Chuong answered the line.
- Unfortunately, Choung is stuck in some other task and can not have the OWC now.

- Rescheduled the OWC conference to tomorrow, 23-Sep at 10 am (Vietnam time).
Oracle Support - September 22, 2010 1:59:47 PM GMT+07:00 [Call - Outbound]
Call - Outbound
------------------------------
- Called +84-985 353 625, got a message "All the lines to this country is currently busy, please call
later'..!!!
Oracle Support - September 22, 2010 1:57:16 PM GMT+07:00 [Oracle Web Conference]
--------------------------------------------------------
------------------------------------------------------------------------------
Customer]
Hi Wael,
Please reach me at 84-985 353 625.We are ready to move to OWC now.
Thanks
Chuong
Hi Chuong,
OWC today at 2:00 pm your time is fine with me. Please update the SR with a direct number as I have
tried to reach you on +84 -8 -985 353 625 many times without luck.
A valid contract number is very important when I need to start the OWC session at 2:00 pm.
Regards,
Wael
Customer]

Hi Weal,
Now is 12:10PM, we will avaible in 2:00 today PM for OWC. Please send me information.
Thanks
Chuong
Hi Thu,
I have tried to reach either you or chuong on the number listed in your last update without any luck - it
keeps giving me busy lines and sometimes a message saying these are invalid numbers.
I have tried the following numbers:
+84 -8 -985 353 625
+84 -8 - 979 597 799
Please verify if the above cell numbers are valid. Otherwise, please provide a land line number so that I
can call it.
On the other hand, I have started a web conference using Oracle Collaboration Suite - Real Time
Conferencing. Please access this conference by going to:
Regards,
Wael
Oracle Support - September 22, 2010 11:39:28 AM GMT+07:00 [Oracle Web Conference]
--------------------------------------------------------
------------------------------------------------------------------------------
Customer]
Hi Kenny,
I provide information :

- Next milestone to UAT is September 27
- chuong
- skype : ptshcm_chuongnh
- Cell : 84 -8 -985 353 625 (VietNam)
- Functional :
- thu
- cell : 84 -8 - 979 597 799
- We will arrange to open OWC soon.
Thanks
Hi Thu,
I'd like to walk through this issue in an OWC. Please update the SR with your availability and a preferred
contact number, and we will schedule a time for the session.
Thank you,
Wael
Global Customer Services
Oracle Support - September 22, 2010 11:08:10 AM GMT+07:00 [Call - Outbound]
Call - Outbound
------------------------------
- Called +1 84 3848460 4 times, no answer....not sure if this is a correct number..but this is the only
number mentioned in the SR header.
Generic Note
------------------------
Thu,
I have not yet raised the Severity of this SR to a Severity 1. But I assure you that I have been working it
as if it was a Severity 1 issue. I have also been discussing this, and the other OKL SRs that you have,
with my colleague Wael. Wael is working from Australia and will likely be holding an OWC with you
today to continue working this issue. If he decides that an OWC is not required I'm sure that he will be
contacting you in some way to progress this issue.
In order to complete the request for a Severity 1 we'll need to get some idea of your project milestones.
Can you please provide the dates for your next milestones (UAT, CRP, etc)? Please also provide 24/7
contact information for both functional and technical resource(s) that will be available to work this issue.
Thank You,
Kenny

Oracle Support - September 22, 2010 4:17:29 AM GMT+07:00 [Notes]
Uploaded Attachment QQ1210_debug_viscrm08.xls in GTCR
Oracle Support - September 22, 2010 4:06:03 AM GMT+07:00 [ODM Test Case]
=== ODM Test Case ===
Test Case
=========
Tested in viscrm08.
Created Quick Quote Number QQ1206.
Step 1 of 5:
Term: 12
End of Term Option: KH_EOT_USDFTX_INT
Step 2 of 5:
Item Category Name: EQUIPMENT.PANELS
Step 3 of 5
Entered nothing, clicked Next.
Step 4 of 5
No error as shown in the screen shot.
Entered:
Frequency: Monthly
Rate: 5
Periods: 12
Step 5 of 5
Nothing to enter, all looks fine.
Clicked Finish.
Confirmation received confirming the Quote was created.
Repeating this test, with debug on this time.
Generic Note
------------------------
OK, I went to start testing and realized that we seem to be in a different place than when we started.
The original flow was Lease Opportunity > Estimate > Lease Quote > Pricing Error in the Quote.
In the latest screen shots we're in a completely different place, now we're in Quick Quotes.
I'll check out the Quick Quotes for now in this SR, as its pretty clear across all of these SRs that the
main cause is probably all related and we've already got 3 SRs trying to fix what may be the same cause
with a lot of different errors depending on where you happen to be working in OKL.
But in the end we may need a new SR for the Quick Quote issue, because that might just not work if the
file versions are really correct as I seem to have found in my initial review.
I'll test, see what is calling those files, and see if I can reproduce. If I cannot reproduce I'll check the
versions of the calling files and see if there correct and go from there.
Research

========
Checked OKLRQQHS.pls 120.4.
This is the correct, and latest, version of this file.
Comment at the top of this file:
--------------------------------------
| 21-oct-05 viselvar -- changed signature of handle_quick_quotes |
--------------------------------------
I then checked OKLRQQHB.pls 120.37.12010000.3.
This is again the latest available version.
So it would seem that in this case the pls files are fine.
But the file calling them must not be making the right call.
Testing in viscrm08 to determine what file would call this.
Research
========
From the latest Apps Check provided in SR 3-2118221801:
OKL_QUICK_QUOTES_PVT OKLRQQHS.pls 120.4 SPEC VALID
OKL_QUICK_QUOTES_PVT OKLRQQHB.pls 120.37.12010000.3 BODY VALID
Name
--------
ODM Data Collection
Screen Shot
FileName
----------------
Select_Pricing_Option___Error.JPG
FileComment
----------------------
This shot shows the same error as seen in the previous shot Step 4 of 5, Select Pricing Option.
In this page there is an error:
Name
--------
ODM Data Collection

Screen Shots
FileName
----------------
Price_Oppotunity.rar
FileComment
----------------------
Screen shots within this zip file show a Quick Quote being created.
The first shot is at Step 3 of 5, Enter Pricing Options.
No Pricing Options are entered.
The second shot shows Step 4 of 5, Select Pricing Option.
In this page there is an error:
Customer]
Uploaded Attachment Select_Pricing_Option___Error.JPG in GTCR
Customer]
Hi Kenny,
Result of the retesting is the same. The screen appear with same unmoved error.
Thanks
Customer]
Hi Kenny,
I update informations that's required. By the way, i want to rise this SR to Severity 1 (highest level).
Because, it's become emergency.
QL> @$OKL_TOP/patch/115/sql/OKLRQQHB.pls
Package body created.
Commit complete.
Package created.
Commit complete.
--------------------------------------------------------------------------------
/* $Header: OKLRQQHB.pls 120.37.12010000.3 2008/11/13 13:33
--------------------------------------------------------------------------------
SQL> select object_name, status
2 from dba_objects
3 where object_name = 'OKL_QUICK_QUOTES_PVT';
OBJECT_NAME

--------------------------------------------------
STATUS
-------
OKL_QUICK_QUOTES_PVT
VALID
OKL_QUICK_QUOTES_PVT
VALID
Thanks
Hi Thu,
1. Connect to SQLPLUS as APPS user and run the following files:
Packages should be created successfully without any errors.
2. Confirm the version of package OKL_QUICK_QUOTES_PVT in your database using the following SQL:
SELECT text
FROM all_source
WHERE NAME = upper('OKL_QUICK_QUOTES_PVT')
AND TYPE = 'PACKAGE BODY'
AND line = 2;
3. Confirm the status of package OKL_QUICK_QUOTES_PVT in your database using the following SQL:
select object_name, status
from dba_objects
where object_name = 'OKL_QUICK_QUOTES_PVT';
Package status should be 'VALID'.
4. Retest the flow. If you get the same or any new errors, then please update the SR with the following:
a) The error details
b) Your availability for an OWC to walk through this issue.
Please note that I am based in Australia so we are sharing almost the same timzone (with only 1 hour
difference).
So, if you are ready for an OWC tomorrow, Wednesday, 22-Sep at 10:00 am (VietNam) / 11:00am
(Australia) that would be great.
Please confirm.
Regards,

Wael
ISSUE ANALYSIS
------------------------
- Ran the following SQL to check the file name related to OKL_QUICK_QUOTES_PVT included in the new
error message:
SELECT text
FROM all_source
WHERE NAME = upper('OKL_QUICK_QUOTES_PVT')
AND TYPE = 'PACKAGE BODY'
AND line = 2;
File name is OKLRQQHB.pls
- Customer will need to ensure that both files OKLRQQHS.pls & OKLRQQHB.pls are run from
$OKL_TOP/patch/115/sql/ so that he can get the R12 file version into the Database.
Name
--------
=== ODM Data Collection ===
=== ODM Data Collection ===
SCREEN SHOTS
--------------------
See the following error in 'Select Pricing Option' step while creating a LQ.
Procedure handle_quick_quote
FileName
----------------
Price_Oppotunity.rar
URL
------
https://support.us.oracle.com/oip/faces/filedownloadservlet?ObjectType=SR&ObjectNo=3-
2057791987&FileName=Price_Oppotunity.rar
Customer]
Hi Kenny,
Error appear is show is the screen i uploaded. File Price_Oputunity.rar. What is the suitable solution for
this issue.
Thanks
Chuong

Customer]
Hi,
The error still here.
Procedure handle_quick_quote
Please consider, this SR become imergency, and i need to fix this as soon as posible.This very
important.
Thanks
Customer]
Hi ,
/* $Header: OKLRSULS.pls 120.9.12010000.3 2009/07/29 10:10:28 racheruv ship $ */
SQL> @$OKL_TOP/patch/115/sql/OKLRSULS.pls
Package created.
Commit complete.
SQL> @$OKL_TOP/patch/115/sql/OKLRSULB.pls
Package body created.
Commit complete.
SQL> select * from ad_bugs where bug_number ='7303033';
---------- --------------------------------------------------
------------------------------ --------------- ------------------------------
---------- --------------- --------------- --------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
374766
7303033 16-JUL-10 R12
5 16-JUL-10 5 au
---------- --------------------------------------------------
------------------------------ --------------- ------------------------------
---------- --------------- --------------- --------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----

R12
y US
Thanks
Action Plan
===========
Chuong,
Yes that file does have the procedure UPDATE_TRX_STATE, and the file is also the correct version for
your patch level. However the specification for OKL_STREAMS_UTIL, file OKLRSULS.pls does not contain
this procedure in the version you have. According to the Apps Check provided you have OKLRSULS.pls
120.9.12010000.2 compiled in the instance. That is not the correct version for your patch level. You
should have version 120.9.12010000.3, which does contain the procedure UPDATE_TRX_STATE. If the
procedure is not in the specification that it cannot be used in any calls other than those within the body
of OKL_STREAMS_UTIL. In this case the call is being made from outside that package, and it cannot be
found because it is not in the spec.
So here's what I think we need to do.
1. First we want to check to see what version of OKLRSULS.pls is in $OKL_TOP.
Please check that using the following command at the unix prompt:
strings -a $OKL_TOP/patch/115/sql/OKLRSULS.pls |grep '$Header'
a. If the result of that shows OKLRSULS.pls 120.9.12010000.3 then we can simply
compile that file using this command:
sqlplus apps/<apps_password> @$OKL_TOP/patch/115/sql/OKLRSULS.pls
Once that is compiled we'll need to compile the body again, do that with this:
sqlplus apps/<apps_password> @$OKL_TOP/patch/115/sql/OKLRSULB.pls
b. If the result comes back as OKLRSULS.pls 120.9.12010000.2 then compiling this file
in that version will have no impact on the issue. If this is the case, please confirm
that Patch 7303033 Oracle E-Business Suite 12.1.2 Release Update Pack (RUP2) has been
applied. If you have the adpatch log files, and the ad worker files, from the application
of this patch please zip all of those up and upload those to the SR.
2. The next step we'll want to take, assuming that Patch 7303033 is in place, is to apply the
latest OKL roll up patch. This patch was just released last week and will be the required
minimum patch level for any future OKL bug fixes. None of the fixes in this patch really
specifically were designed to address the issues in any of the SRs that I have with you and
Thu at the moment. But this patch does contain a lot of files that are in higher versions than
what you have, which means that many of the files that you have in bad versions will be replaced
by good versions. I usually don't suggest patches like this, but given the circumstances and
the fact that the application of this patch is inevitable, there's really no reason not to apply it.

Now that I've explained why it should be applied, the patch is Patch 9451692 OLFM : CONSOLIDATED
PATCH #2 ON R12.1.2 (SEP/2010). Please apply this patch
I already know that this patch will not fix the issue with the procedure UPDATE_TRX_STATE not being
found.
This patch does not contain OKLRSULS.pls in any version. So if this file is not resolved in step 1
we're going to need to figure out how to get the correct version in your instance. But I honestly believe
that this patch should resolve at least some of the outstanding issues. From there we'll have a better
base, and fewer issues, and we can work on the issues that are left.
Kenny
Customer]
Hi,
i didn't catch up your point in here
"Body for okl_streams_util is OKLRSULB.pls, apps check indicates this version is 120.20.12010000.10.
This version is the latest available for this file.
And this file does have the procedure UPDATE_TRX_STATE."
The procedure UPDATE_TRX_STATE is not available. So, what do i need to do now, i still have some
invalid object about OKL. Is there any solution to solve these.
Tell me if you need any information can help this SR
Thank you so much
Chuong
Research
========
Started with this error:
-------------------------------
OKL_ACTIVATE_CONTRACT_PUB OKLPACOB.pls 120.26.12010000.7 BODY INVALID
PLS-00302: component 'UPDATE_TRX_STATE' must be declared
-------------------------------
In OKLPACOB.pls 120.26.12010000.7:
-------------------------------

(p_api_version => p_api_version,
p_init_msg_list => p_init_msg_list,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_chr_id => l_orig_khr_id,
p_rbk_chr_id => p_chrv_id);
-------------------------------
-------------------------------
okl_streams_util.update_trx_state(l_contract_id, 'BOTH');
-------------------------------
Body for OKL_LLA_UTIL_PVT is OKLRLAUB.pls, apps check indicates this version is 120.18.12010000.2
There is no procdure named check_rebook_upgrade in this version.
Procedure check_rebook_upgrade debuts in version 120.18.12010000.7, via Bug 8756653.
The first released version with this procedure is version 120.18.12010000.8
That version is included in patch 7303033 Oracle E-Business Suite 12.1.2 Release Update Pack (RUP2)
Body for okl_streams_util is OKLRSULB.pls, apps check indicates this version is 120.20.12010000.10.
This version is the latest available for this file.
And this file does have the procedure UPDATE_TRX_STATE.
Reviewed the call against the procedure signature and everything matches up.
Leaving us with the only cause being that the package specification does not have this procedure.
Apps check shows that the spec for this package is OKLRSULS.pls 120.9.12010000.2.
There is no procedure UPDATE_TRX_STATE in this version of the spec.
But there is in the next version, 120.9.12010000.3, also available in patch 7303033 (12.1.2).
OKL RUP2 for 12.1.2 was released 2 days ago and is now the new minimum required for OKL in R12.
Checking that to see if it has enough of these files to resolve all of these errors.
Research
========
Reviewed invalid list, still have OKL invalids that would cause issues throughout OKL.
Apps Check provided in new SR 3-2118221801 yesterday shows that the following OKL packages are
invalid:
OKL_ACTIVATE_CONTRACT_PUB OKLPACOB.pls 120.26.12010000.7
OKL_BOOK_CONTROLLER_PVT OKLRBCTB.pls 120.8.12010000.4
OKL_CNTRCT_FIN_EXTRACT_PVT OKLRCFEB.pls 120.2.12010000.19
OKL_CONTRACT_BOOK_PVT OKLRBKGB.pls 120.63.12010000.6
OKL_COPY_CONTRACT_PVT OKLRCOPB.pls 120.50.12010000.5
OKL_CREATE_STREAMS_PVT OKLRCSMB.pls 120.30.12010000.8
OKL_DEAL_CREAT_PVT OKLRDCRB.pls 120.5.12010000.9
OKL_K_LINE_FIN_EXT_PVT OKLRLFEB.pls 120.0.12010000.38
OKL_LA_STREAM_PVT OKLRSGAB.pls 120.141.12010000.32
OKL_MASS_REBOOK_PVT OKLRMRPB.pls 120.33.12010000.5
OKL_PRB_UPGRADE_PVT OKLRPRBB.pls 120.0.12010000.6
OKL_PRICING_PVT OKLRPIGB.pls 120.76.12010000.4

OKL_QA_DATA_INTEGRITY OKLRQADB.pls 120.153.12010000.24
OKL_SPLIT_ASSET_PVT OKLRSPAB.pls 120.61.12010000.10
OKL_STREAM_GENERATOR_PVT OKLRSGPB.pls 120.101.12010000.14
--This one is not an issue, obsolete
OKL_SIMPLE_PRICING_PVT OKLRSPRB.pls 120.1
This Apps Check Output is from the same instance as the instance used to provide the original Apps
Check output in this SR.
The new Apps Check shows that we now have all R12 file versions compiled, which is good.
But we still have some that are invalid, which is not so good.
Checking into these compilation errors now.
Name
--------
ODM Data Collection
Invalid Objects List
FileName
----------------
Invalid_Ob.txt
FileComment
----------------------
Only listing OKL invalids
OKL_ACTIVATE_CONTRACT_PUB
OKL_CONTRACT_BOOK_PVT
OKL_COPY_CONTRACT_PVT
OKL_CREATE_STREAMS_PVT
OKL_MASS_REBOOK_PVT
OKL_QA_DATA_INTEGRITY
OKL_STREAM_GENERATOR_PVT
OKL_LA_STREAM_PVT
OKL_SIMPLE_PRICING_PVT
OKL_SPLIT_ASSET_PVT
OKL_PRICING_PVT
OKL_BOOK_CONTROLLER_PVT
OKL_DEAL_CREAT_PVT
OKL_CNTRCT_FIN_EXTRACT_PVT
OKL_K_LINE_FIN_EXT_PVT
OKL_PRB_UPGRADE_PVT
Customer]
Uploaded Attachment Price_Oppotunity.rar in GTCR

Customer]
Hi,
The problem occur in step 4 : Select Pricing Option, when create a Quick Quote. I upload 2 screent
shoot for consideration.
Thanks
Chuong
Customer]
Uploaded Attachment Invalid_Ob.txt in GTCR
Customer]
Hi,
I ran 2 scripts you give, s.sh ,b.sh then compile apps schema by adadmin. I upload file list of invalid
object.
Chuong
Generic Note
------------------------
Thu,
I apologize for not having those files uploaded to the SR. I uploaded them to the bug and I must have
forgotten to get them into the SR. But they are in the SR now.
Using adadmin before these scripts won't help this issue until these files are run. That will only
recompile the code that is already in place. Once we have the code in place using these two shell scripts
we will then use adadmin to make sure everything is valid.
Regards,
Kenny
Uploaded Attachment s.sh in GTCR
Uploaded Attachment b.sh in GTCR
Customer]
Hi,

I can not find 2 scrip s.sh, b.sh for compile these object. Please show me, or i can run adadmin to
compile invalid object.
Thanks
Action Plan
===========
Thu,
I updated SR 3-2042979591 to ask whether the issue that SR and this SR were the same instance as the
issue being reported in Pythis SR 3-2007932171 were related. I have since concluded that they are as
the screen shots show the same url being used in the applications. So I am update this SR with the
action plan below that I believe will resolve all three SRs.
I have logged Bug 10113216 with Lease Management Development to ask for a patch or some other
simpler method to do what I will be suggesting below. However, I don't expect that to be provided in
the near future. So to try to get all of your issues moving we'll proceed here. I have just completed
testing everything below in my instance and everything worked out just fine. There were a couple
bumps along the way, and I have documented those and how to get around them below.
From the data provided in SR 3-2042979591, SR 3-2057791987, and SR 3-2007932171 it seems clear
that you have a number of 11i OKL pls files compiled in this instance. This issue has occurred a few
times in R12 installs and the exact cause has not yet been identified. However the solution is fairly
simple. We need to compile all of the pls files for OKL so that all of your compiles packages are using
R12 code. There is probably 100 different ways to accomplish this and after what is now more than a
few attempts my current solution is the steps below.
The main goal in these steps is to recompile all OKL package specifications and bodies. The approach
taken in these steps is to first compile all package specifications in this directory with the file s.sh. Once
that script completes we then compile all package bodies with the file b.sh. If you have steps that you
prefer that will accomplish the same then feel free to use those. As I mentioned there are probably 100
ways to get this done, and this is just the latest in my approaches to getting it done.
These scripts are only compiling files that should have already been compiled by the R12 install patch.
They are making no changes to any code.
Each of these scripts will be compile many hundreds of files and each is going to take some time to
complete.
1. Please download copies of s.sh and b.sh from the SR.
2. Place copies of both of these files in the following directory:
$OKL_TOP/patch/115/sql
3. Execute s.sh from the unix prompt.
This file will compile all of the package specification files in this directory.
4. Once s.sh completes execute b.sh from the unix prompt.
This file will compile all of the package body files in this directory.

There will be two different types of occasions where these shell scripts will pause requiring input.
Whenever you see the script stop you will need to manually get it moving again. The way to do that
depends on the situation:
1. The script will stop with the cursor at the sql prompt. My guess is that this is because
there is no Exit in the pls file that was just compiled. To get the script rolling again
simply type exit and hit enter. This will end the sql plus session and the shell script
will continue.
2. While compiling the scrip with stop and prompt with "Please enter a value for x" where x can be any
number of values.
This seems to be caused by the use of ampersands (&) or other variable substitution characters within
the comments of
the file being compiled. When these are hit you can simply hit enter and the script will continue.
One other other suggestion I can make would be to shut down the instance while these files are being
compiled. This will prevent issues with the packages being locked should anyone be attempting to use
OKL. Any attempt to use OKL while these files are being compiled will no doubt result in errors, so there
is really no use in even trying until these files are compiled.
Once both scripts complete the R12 code will be in place, but there are sure to be some invalids. It
would be just about impossible to manually compile thousands of pls files like we just did without
getting invalids, a most likley a bunch of them.
Please use adadmin to recompile the apps schema. Again we're going to have more than the usual
number of invalids to be recompiled during this process. So adadmin will likely take longer than usual to
compile the apps schema. Once that completes you're ready to bring the instance back up and re-test
the issues in each of the three SRs mentioned above.
If you check for OKL invalids and find that OKL_SIMPLE_PRICING_PVT is invalid that is to be expected.
This package is obsolete and no longer used. If you prefer to not have this package invalid you can
simply drop it.
Please update each SR with the new test results after these actions are completed.
Please complete these steps and re-test the issues in all of these SRs. I am pretty confident at least
some of them are going to be resolved and there's a very good chance it will resolve all of them.
If you have any questions or concerns about this action plan please feel free to let me know.
Thanks,
Kenny
Oracle Support - September 15, 2010 12:48:57 AM GMT+07:00 [Predefect Update]
Defect 10113216 has been created via Defect Workbench iBug portal request id: (2788951).
Oracle Support - September 15, 2010 12:29:55 AM GMT+07:00 [Notes]
Uploaded Attachment Apps_Check__Lease_Management.txt in GTCR

Research
========
Compared screen shots provided in this SR to screen shots provided in SR 3-2007932171.
Both show that the same url is being used in the instance.
The Apps Check provided in SR 3-2007932171 shows that there are numerous 11i pls files compiled.
All of these should be R12 files.
Working on an action plan to get the 11i files to R12 versions.
Generic Note
------------------------
Just updated SR 3-2042979591 with an action plan.
There's some additional information in this SR that may help me confirm my suspicion in that SR.
Reviewing now to see if that's true.
Customer]
Hi,
Please feedback. It's so long for solving this issue. We can't continue our working because of it.
Regards,
Thu
Research
========
Output of LO_debug1.sql for one of the Lease Quotes I created to test this issue this morning:
--------------------------------
L_QUOTE_NUMBER is LQ388
L_QUOTE_ID is 379
cust_details_rec.parent_id is 361
cust_details_rec.prospect_id is 1150
cust_details_rec.cust_acct_id is 1150
cust_details_rec.SALES_TERRITORY_ID is
cust_details_rec.CURRENCY_CODE is USD
L_CREDIT_CLASSFICATION is LOW
EOT_TYPE_REC.id is 379
EOT_TYPE_REC.reference_number is LQ388
EOT_TYPE_REC.end_of_term_name is KH_EOT_USDFTX_INT
EOT_TYPE_REC.eot_type_code is AMOUNT
EOT_TYPE_REC.END_OF_TERM_ID is 219862313782027915479839130690144325409
EOT_TYPE_REC.end_of_term_ver_id is 219862313782029124405658745319319031585

--------------------------------
Record cust_details_rec is populated for my Quotes.
That is because parent_object_code and parent_object_id are populated for this Quote.
Uploaded Attachment viscrm08_LO430.xls in GTCR
Oracle Support - September 9, 2010 7:12:19 PM GMT+07:00 [ODM Test Case]
=== ODM Test Case ===
Test Case
=========
Created Lease Opportunity LO429.
Created Estimate QQ184.
Clicked Create Quote in the Estimate record.
When I clicked Finish to complete the Quote I received this message:
-----------
Successfully created, validated and priced the Quote.
-----------
Quote is priced and validated.
The Validate button and the Validate and Price button were never active when I created this Quote. So I
was never able to select these buttons.
I then opened the Quote and updated the Asset information.
This update was only to enter a value in Model.
No financial changes were made.
The Validate buttons are now active.
Clicked Validate and Price.
Quote was validated and priced without error.
SELECT parent_object_code, parent_object_id
from OKL_LEASE_QUOTES_B
where reference_number = 'LQ387'
PARENT_OBJECT_CODE PARENT_OBJECT_ID
------------------------------ ----------------------
LEASEOPP 360
Need to determine where these fields are being populated.
These are the fields causing the problem in Thu's Quote.
Research
========
The Estimate is a step that I haven't seen used yet.
And that possible explain the null values in okl_lease_quotes_b.parent_object_code and
okl_lease_quotes_b.parent_object_id.

If the Quote was created within the Lease Opportunity without the Esitmate this would probably work
without error.
Name
--------
ODM Data Collection
Screen Shots
FileName
----------------
09SEP2010_Steps_to_create_Quote_from_Lease_Opportunity.docx
FileComment
----------------------
A lease Opportunity is created.
An Estimate is created within the Lease Opportunity.
Create Quote is then clicked in the Estimate record.
Error is received when pricing this quote.
Customer]
Uploaded Attachment 09SEP2010_Steps_to_create_Quote_from_Lease_Opportunity.docx in GTCR
Customer]
Hi,
Please view the uploaded file "09SEP2010-Steps to create Quote from Lease Opportunity" for details.
Regards,
Thu
Action Plan
===========
Thu,
In the SR opening you indicated that you navigated to Sales > Lease Opportunity. The next step that
you mentioned was creating a Quote. Given the navigation I assumed that you were creating this Quote
within a Lease Opportunity. However the script output that you provided is showing that may not be the
case. The we have the Quote Number LQ29 which tells me that was the case. So I'm thinking that you
created the Lease Opportunity then created the Lease Quote within this Lease Opportunity. Can you
please confirm the steps you took to create this Quote?

Please also upload the results of the following select statement to the SR in spread sheet format:
--Statement 1
SELECT *
FROM OKL_LEASE_QUOTES_B
where id = 8;
Thanks,
Kenny
Research
========
Output shows that cursor get_cust_details_csr is not getting any records.
The portion of LO_debug1.sql that is missing in the output is:
------------------------------
for cust_details_rec in get_cust_details_csr(l_quote_id) loop
DBMS_OUTPUT.PUT_LINE('cust_details_rec.parent_id is '||CUST_DETAILS_REC.PARENT_ID);
DBMS_OUTPUT.PUT_LINE('cust_details_rec.prospect_id is '||CUST_DETAILS_REC.prospect_id);
DBMS_OUTPUT.PUT_LINE('cust_details_rec.cust_acct_id is '||CUST_DETAILS_REC.CUST_ACCT_ID);
DBMS_OUTPUT.PUT_LINE('cust_details_rec.SALES_TERRITORY_ID is
'||CUST_DETAILS_REC.SALES_TERRITORY_ID);
DBMS_OUTPUT.PUT_LINE('cust_details_rec.CURRENCY_CODE is '||cust_details_rec.CURRENCY_CODE);
L_CREDIT_CLASSFICATION := okl_lease_app_pvt.get_credit_classfication(
p_party_id => CUST_DETAILS_REC.prospect_id,
P_CUST_ACCT_ID => CUST_DETAILS_REC.CUST_ACCT_ID,
P_SITE_USE_ID => -99);
DBMS_OUTPUT.PUT_LINE('L_CREDIT_CLASSFICATION is '||L_CREDIT_CLASSFICATION);
end loop;
FOR EOT_TYPE_REC IN GET_EOT_TYPE(l_quote_id) LOOP
DBMS_OUTPUT.PUT_LINE('EOT_TYPE_REC.id is '||EOT_TYPE_REC.id);
DBMS_OUTPUT.PUT_LINE('EOT_TYPE_REC.reference_number is '||EOT_TYPE_REC.reference_number);
------------------------------
And that cursor is:
------------------------------
CURSOR get_cust_details_csr( p_lq_id NUMBER )
IS
SELECT lopp.id parent_id ,
lopp.prospect_id prospect_id ,
lopp.cust_acct_id cust_acct_id ,
lopp.sales_territory_id sales_territory_id ,
lopp.currency_code currency_code

FROM okl_lease_quotes_b lq,
okl_lease_opportunities_b lopp
WHERE parent_object_code = 'LEASEOPP'
AND parent_object_id = lopp.id
AND LQ.ID = P_LQ_ID;
------------------------------
The Quote ID used in the script seems valid as the cursor get_eot_type is getting values later in the
script.
So it would seem that the value in okl_lease_quotes_b.parent_object_code and / or
okl_lease_quotes_b.parent_object_id are not so valid.
Generic Note
------------------------
Reviewing --Kenny
Customer]
Hi,
The output of script LO_debug1.sql:
L_QUOTE_NUMBER is LQ29
L_QUOTE_ID is 8
EOT_TYPE_REC.id is 8
EOT_TYPE_REC.reference_number is LQ29
EOT_TYPE_REC.end_of_term_name is EOF 01
EOT_TYPE_REC.eot_type_code is AMOUNT
EOT_TYPE_REC.END_OF_TERM_ID is 235159738464742404367292495399846771388
EOT_TYPE_REC.end_of_term_ver_id is 235159738464743613293112110029021477564
Regards,
Thu
Action Plan
===========
Thu,
Please download a copy of LO_debug1.sql from the SR. This is a debug script that I created based on
the code where the error you are receiving is being hit. The script performs no updates, it will simply
print out debug messages. Please run this script in the same instance used to generate the debug file
that you uploaded to the SR. The script uses dbms_output to print the debug messages. Please be sure
that the tool you use to run this has this output turned on. In SQL Plus the command to turn this on is:
set serveroutput on
For other tools, such as SQL Developer, TOAD, etc. there are usually buttons and / or menu options to

Sr 3 2057791987 price lease opportunity ora-06503 plsql function returned without value in package okl-pricing_u

Sr 3 2057791987 price lease opportunity ora-06503 plsql function returned without value in package okl-pricing_u

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie Sr 3 2057791987 price lease opportunity ora-06503 plsql function returned without value in package okl-pricing_u

Ähnlich wie Sr 3 2057791987 price lease opportunity ora-06503 plsql function returned without value in package okl-pricing_u (20)

Sr 3 2057791987 price lease opportunity ora-06503 plsql function returned without value in package okl-pricing_u