Apps Initialization Methods in Oracle EBS

 

 

In many times it’s required to initialize to run many of custom programs to fetch correct data.

Below are the different methods which are used frequent basis for Oracle apps initialization which sets the environment for each responsibility we login, and same can be used in custom programs.

 

fnd_global.apps_initialize

fnd_global.initialize

fnd_profile.initialize

dbms_application.set_client_info

 

You can use fnd_profile.get or fnd_profile.value functions to get user id, login id values.

 

For Release 12, you can do the same using

-----------------------------------------------------

BEGIN
MO_GLOBAL.SET_ORG_CONTEXT (204, NULL,'SQLAP')
END

Where 204 is Operating Unit ID
and SQLAP stands for Initializing Payables

 

Please post your Suggestions to improve the article

 

Monitoring file system free space in UNIX

As most of the times Apps Technical/DBA person’s responsibility to monitor UNIX file system to ensure none of the UNIX file system mount points becomes full. If Oracle DBA creates table spaces with the auto extended option then it’s required to monitor UNIX file system instead of ORACLE. Whenever table-spaces are allowed to grow within the UNIX mount point, we must be always cautious to make sure that the file system does not become full.

Using df –k command we can see all the mount points, here is the example






root> df -k


Filesystem                  kbytes        used         avail         capacity   Mounted on
/dev/dsk/rootvol       3009327       1653629    1295512    57%           /               
/proc                        0                   0            0              0%            /proc
mnttab                      0                   0            0              0%            /etc/mnttab
fd                              0                  0             0              0%           /dev/fd
/dev/dsk/rutdsk_1     191611          5985       166465      4%            /global/.devices/node@1


Normally all oracle file system starts with /u0 to minimize the complexity, you can add greep command. Here is the example


root> df -k grep /u0


/dev/uat03/ou01      62914560     53979734        8376410        87%    /5u_ofi_app/u01
/dev/uat03/ou01      107063296   93965411        12346000       89%    /5z_ofi_db/u01
/dev/uat03/o02        107063296   102682991      4213089        97%    /5z_ofi_db/u02
/dev/uat03/ou03      107063296   97055884        9405053        92%    /5z_ofi_db/u03
/dev/uat03/ou04      31457280     27704043        3518713        89%    /5z_ofi_db/u04
/dev/uat03/1-L01     31457280     9159293          20906241      31%    /5z_olp_db/u01


Instead of monitoring manually you can create script to monitor the same and run job using crontab so that it will not required to connect UNIX filesytem and monitor.

Below is one script, u can change according to your requirement


#!/bin/sh
#
#set -xv
LIMIT=90
MAIL_RECIPIENT='asm-support@domain.com'
limit_reached()
{
echo "
==============================================
WARNING : Filesystem threshold reached the $LIMIT% limit !!
MOUNTPOINT : $MOUNTPOINT
FILESYSTEM : $FILESYSTEM
SIZE(GB) : $SIZE_GB
USED(GB) : $USED_GB
FREE(MB) : $AVAIL_MB
CAPACITY(%) : $CAPACITY
==============================================
"
}
df -k
grep -v Filesystem
while read FILESYSTEM KBYTES USED_KB AVAIL_KB CAPACITY MOUNTPOINT
do
PCT_USED=`echo $CAPACITY
cut -d% -f1`
SIZE_GB=`expr $KBYTES / 1048576`
USED_GB=`expr $USED_KB / 1048576`
AVAIL_MB=`expr $AVAIL_KB / 1024`
if [ $PCT_USED -gt $LIMIT ]
then
limit_reached
limit_reached
mailx -s "FS : $MOUNTPOINT is $CAPACITY Full !!" $MAIL_RECIPIENT
fi
done

Accelerator keys(Hot Keys) in E-business suite

Accelerator keys bypass menu and page navigation, and perform an action directly, as if the user has pressed an action/navigation button or link. Accelerator keys are also commonly called "hot keys". Common accelerator keys in a Windows application, such as Internet Explorer, are Ctrl+O for "Open" and Ctrl+P for "Print".

Below are the oracle Standard Hot Keys, Same can be viewed using Help menu.

Table of common default Forms keystrokes on Microsoft Windows

---------------------------------------------------
Action -------------------> Key Stroke
---------------------------------------------------
Save/Commit -----------> Ctrl + S
List of Values------------> Ctrl + L
Count Query-------------> F12
Enter Query -------------> F11
Execute Query ----------> Ctrl + F11
Cancel Query------------->F4
Edit------------------------->Ctrl + E
Clear Field----------------> F5
Clear Record-------------> F6
Clear Block---------------> F7
Clear Form---------------> F8
Delete Record-----------> Ctrl + Up
Insert Record------------> Ctrl + Down
Duplicate Field----------> Shift + F5
Duplicate Record-------> Shift + F6
Next Field----------------> Tab
Next Record-------------> Down Arrow
Next Set of Records (Same as Page Down)àShift + F8
Next Block---------------> Shift + Page Down
Previous Field-----------> Shift + Tab
Previous Record --------> Up Arrow
Previous Block----------> Shift + Page Up
Scroll Down (Same as Shift + F8)
Page Down---------------> Scroll Up
Page Up-------------------> Return
Print----------------------> Ctrl + P
Update Record------------> Ctrl + U
Exit-----------------------> F4
Block Menu---------------> Ctrl + B
Display Error-------------> Shift + Ctrl + E
Display list of Keys-------> Ctrl + K
Window Help-------------> Ctrl + H
List Tab Pages-----------> F2
------------------------------------------------------------

E-Business Suite provides profile 'Forms Keyboard Mapping File'. To run a new mapping file, specify the complete path in addition to the filename for the profile. When running Oracle Forms through the E-Business Suite Professional User Interface, the new mapping file will be used.

Patches applied

There are two tables that contain information about patches applied to your Oracle E-Business Suite applications:

AD_APPLIED_PATCHES contains the list of patches that were directly applied.
AD_BUGS contains the list of all the patches that were directly applied or were contained in the patches that were directly applied.
For example, if you are trying to find out if a certain pre-requisite patch has been applied, query AD_BUGS. If you are trying to find
out patches applied in a date range, query AD_APPLIED_PATCHES.

SELECT *
FROM ad_bugs
WHERE bug_number = 'patch_number‘;

SELECT *
FROM ad_applied_patches
WHERE patch_name = ‘patch_number‘;
Replace patch_number with the number of the patch you want to check.

google 4 things at once

Ever wanted to google four things at once?

Well, now you can! GoogleGoogleGoogleGoogle.com - for true power searchers. Our power searching level is over ...googlegooglegooglegoogle.com/

Try it out yourself

Thanks Google.