Archive for the ‘Oracle Queries’ Category

Get Current Patch Set Level of Oracle Applications Products For R12

October 11th, 2020, posted in Oracle EBS Application, Oracle Queries
Share

1) Login to OAM

(Responsibility “Oracle Applications Manager“, menu “OAM Support Cart“)

and Navigate: Support Cart -> Applications Signature -> Collect -> Check “Product Information” box -> Click on “View” (eyeglasses)

In R12

(Responsibility “System Administrator“, Menu “Oracle Application Manager“)
and Navigate : Applications Usage >> Products Installed

This will display the following patchset information :

Application Name
Current Patch Level
Product Version
Status (Installed, Shared Product, Inactive)

2) The patchset level information can be retrieved directly via sqlplus with the following diagnostic script :
$AD_TOP/sql/adutconf.sql

3) Use the below query to pull out the details

SQL>

SELECT fav.application_id,
fav.application_short_name, 
fav.application_name,
fav.basepath,
fav.creation_date,
fpi.status,
fpi.patch_level,
fpi.product_version,
fpi.TABLESPACE,
fpi.index_tablespace,
fpi.temporary_tablespace
FROM fnd_application_vl fav,
fnd_product_installations fpi
WHERE fav.application_id = fpi.application_id(+) 
ORDER BY creation_date DESC
Share

Enable Export Feature in Custom Forms

April 26th, 2020, posted in Oracle Queries
Share

Occurred In Oracle Reports,Oracle Reports,Oracle,Reports,Enable Export Feature in Custom Forms,Enable Export Feature, in Custom Forms,Oracle Custom Forms,Oracle Forms,In Order to Enable Export option, available in Oracle Application forms to export the data into Excel file.
In the custom form at form level trigger write the below code in When-New-Form-Instance trigger.

APP_SPECIAL.ENABLE('FILE.EXPORT', PROPERTY_ON);
Share

Oracle Queries for checking Profile Option Values

April 19th, 2020, posted in Oracle Queries
Share
SELECTatabase, dba imam, dba immam, Imam Dba, ORA-28014: Cannot Drop Administrative Users, Oracle, Oracle DBA, oracle quries
substr(pro1.user_profile_option_name,1,35) Profile,
decode(pov.level_id,
10001,'Site',
10002,'Application',
10003,'Resp',
10004,'User') Option_Level,

decode(pov.level_id,

10001,'Site',
10002,appl.application_short_name,
10003,resp.responsibility_name,
10004,u.user_name) Level_Value,

nvl(pov.profile_option_value,'Is Null') Profile_option_Value

FROM

fnd_profile_option_values pov,
fnd_responsibility_tl resp,
fnd_application appl,
fnd_user u,
fnd_profile_options pro,
fnd_profile_options_tl pro1

WHERE

pro1.user_profile_option_name like ('%Ledger%')
and pro.profile_option_name = pro1.profile_option_name
and pro.profile_option_id = pov.profile_option_id
and resp.responsibility_name like '%General%Ledger%' /* comment this line if you need to check profiles for all responsibilities */
and pov.level_value = resp.responsibility_id (+)
and pov.level_value = appl.application_id (+)
and pov.level_value = u.user_id (+)

order by 1,2;
Share

Difference Between Bitmap and Character Mode Report

April 12th, 2020, posted in Oracle Queries
Share

Here is an example to help explain how Oracle Reports are designed and printed in both the bitmap and character-mode environments.Difference Between Bitmap and Character Mode Report, Occurred In Oracle Reports,Oracle Reports,Oracle,Reports,Difference Between Bitmap and Character Mode Assume you wish to print “Cc” where “C” is a different font and a larger point size than “c” and is in boldface type (where “c” is not). In Oracle Reports Designer, bitmap mode, you can make “C” bold and in a different font and point size than “c”.

This is because you are generating postscript output. Postscript is a universal printer language and any postscript printer is able to interpret your different design instructions. In Oracle Reports Designer, character mode, the APPLICATIONS STANDARDS REQUIRE the report to be designed in ONE FONT/ ONE CHARACTER SIZE. Character mode reports generate ASCII output.

In ASCII you cannot dynamically change the font and character size. The standard is in effect so a report prints as identically as possible from both conventional and postscript printers.

Share

REP-0300: ORACLE Error Occurred In Oracle Reports

March 29th, 2020, posted in Oracle Queries
Share

Imam Dba, Immam Dba, Oracle DBA,

If the below error occurs

REP-0300: ORACLE error occurred.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error: 
REP-300: ORACLE error occurred.

Answer :
Please check the report parameter data types.
It should be correct to overcome the issue.

Share