Believe in yourself, and remember that anything is possible. Believe in what makes you feel good. Believe in what makes you happy. Believe in the dreams you have always wanted to come true.
Posted by: Edi Yanto on: May 28, 2009
SELECT DISTINCT RPAD (ad.bug_number, 11) “Bug Number”,
RPAD (app.patch_name, 11) “Patch Name”,
RPAD (TRUNC (apr.end_date), 12) “End Date”,
RPAD (aprb.applied_flag, 4) “Applied?”
FROM ad_bugs ad,
ad_patch_run_bugs aprb,
ad_patch_runs apr,
ad_patch_drivers apd,
ad_applied_patches app
WHERE ad.bug_id = aprb.bug_id
AND aprb.patch_run_id = apr.patch_run_id
AND apr.patch_driver_id = apd.patch_driver_id
AND apd.applied_patch_id = app.applied_patch_id
AND ad.bug_number = nvl(:p_bug_number,ad.bug_number)
ORDER BY 1 DESC;
June 27, 2009 at 2:29 am
How to find the bug # ?
I mean the :p_bug_number
In RDM there are many customisation like using custom pll, custom discount type in advance pricing and many other things..example when creating SO line, when the engine want to calculate the price for an item that has a discount (Modifier) sometimes, Error messages appears like “Invalid number” / “Invalid Salesperson”, etc.. and many times, we cannot redo the error again eventough the steps are exactly the same, the frequency of the error cannot be predicted. Iman looking the metalink and found a patch for the R11.5.9 in RDM but has not been applied yet (we thought it could be an APPS bug).
But how to find a certain bug # in metalink for some case as above?