|
|
In This Document
The most current version of this document can be obtained in Document
389422.1
There is a change
log at the end of this document.
This document outlines the requirements for browsers that are
certified for use with Oracle E-Business Suite R12.
Note: Internet Explorer, Windows desktop operating
system and service pack requirements are available from Microsoft.
Certification Matrix for Internet Explorer
(64-bit) Browsers
The table below outlines the certified combinations of 64-bit
Internet Explorer Browser, Windows Desktop Client Operating System and JRE
(64-bit) streams with minimum versions, where applicable. Please also review
this document for further specific certification information and
requirements:
Certification Matrix for Internet Explorer
(32-bit) Browsers
The table below outlines the certified combinations of 32-bit
Internet Explorer Browser, Windows Desktop Client Operating System and JRE
(32-bit) streams with minimum versions, where applicable. Please also
review this document for further specific certification information and
requirements:
Compatibility with Higher JRE releases
Oracle has certified the Oracle E-Business Suite with the
minimum JRE releases noted above on the JRE 6 (1.6.0.x) stream. Oracle
E-Business Suite end-users may use or upgrade to later production releases of
the JRE plug-in on, either stream, at their discretion. It is recommended to
upgrade to the latest certified JRE releases to uptake the latest security
and functional fixes. For further information on upgrading JRE and it's
requirements and known issues, please reference Document
393931.1 titled, 'Deploying JRE (Native Plug-in) for Windows Clients in
Oracle E-Business Suite Release 12'.
Oracle will continue to test and certify the Oracle E-Business
Suite with selected future versions of JRE releases in advance of their
general availability to the public. Oracle will update this documentation
with known compatibility issues or workarounds as needed.
3rd Party Software
Support Lifecycle
Oracle's certification of the various third party client
operating system, service pack levels and browsers aligns with the respective
vendor's support life cycle. Support timelines are available from Microsoft
Windows 8 (32-bit and 64-bit)
Oracle E-Business Suite is certified on Windows 8 (32-bit &
64-bit) running Internet Explorer 10 in 'Desktop Mode' (running from the
'Metro Screen' (Start Screen) is not supported) with the following patch
requirements:
WebADI and Report Manager Users
WebADI and Report Manager have prerequisite patch requirements
when running on Windows 8, for further information see Document
1077728.1 titled, 'Using Microsoft Office 2007 and 2010 with Oracle
E-Business Suite 11i and R12'..
Known Issues
For known issues see Windows
8 Specific Issues
Internet Explorer 8, 9 & 10 (64-bit)
Internet Explorer 8 (64-bit), Internet Explorer 9 (64-bit) and
Internet Explorer 10 (64-bit) are certified as client browser's on Windows 7
(64-bit) with the following patch requirements:
Internet Explorer 10 (32-bit)
Internet Explorer 10 (32-bit) is certified as a client browser
on Windows 7 (32-bit & 64-bit) with the following patch requirements:
Internet Explorer 9 (32-bit)
Internet Explorer 9 (32-bit) is certified as a client browser on
Windows Vista and Windows 7 (32-bit & 64-bit) with the following patch
requirements:
Internet Explorer 8 (32-bit)
Internet Explorer 8 (32-bit) is certified as a client browser on
Windows XP (32-bit), Windows Vista (32-bit) and Windows 7 (32-bit &
64-bit) with the following patch requirements:
Internet Explorer 7 (32-bit) with Windows
Vista
Internet Explorer 7 (32-bit) is certified as a client browser on
Windows Vista (32-bit) with the following patch requirements:
Recommended Internet Explorer Browser Settings
Security Zones
Microsoft Internet Explorer offers four different security zones
to run your application through. Which zone is used is dependant how you are
accessing your site (Internet or Local Intranet) and set up within the zones
themselves (Trusted sites & Restricted sites).
It is advisable to have the security setting at Medium
for run-time use.
The Security Internet Options on Microsoft Internet Explorer can
be accessed by going to:
Tools -> Internet Options -> Security tab from the
Internet Explorer Menu Bar.
Each zone carries its own default security level that may need
to be adjusted when accessing Oracle E-Business Suite through it. The
defaults are as follows:
It is recommended that Oracle E-Business Suite is run through
the 'Trusted Sites' zone, with a 'Medium' Security Setting.
Setting up Oracle E-Business Suite to run
through the 'Trusted Sites' zone, with a 'Medium' Security Setting. (If
Required)
Step 1: Select Tools -> Internet Options -> Security tab ->
Trusted Sites icon -> Sites button from the Internet Explorer Menu Bar.
Step 2: Set the 'Security Level for this Zone' to 'Medium' if it is not set already. Step 3: In the 'Add this Web site to the zone:' field, enter the 'hostname and domain' of the environment you are running the Oracle E-Business Suite, e.g. https://
(If you are entering an http://... or '*.' domain address, you
must ensure that the 'Require server verification (https:) for all sites in this
zone' is not checked).
Internet Explorer Browser Settings for User
Download of oaj2se.exe
Oracle recommends that customers running Oracle E-Business Suite
through Internet Explorer (IE) should use a 'Medium' security setting through
the 'Trusted Sites' zone in the browser at runtime. This setting does not
automatically download the oaj2se.exe file from the middle tier if the user
does not already have the appropriate version installed on their desktop.
The JRE plug-in will download and install from the webserver on
a medium security setting. After clicking on a 'forms link', a message
similar to the following will appear at the top of the browser window:
'The website wants to install the following add-on: 'J2SE
Runtime Environment 6 Update 3' from 'Sun Microsystems, Inc.'. If you trust
this website and the add-on and want to install it, click here...'
To install the plug-in:-
Alternatively, to
enable the download of this file, the user should temporarily alter the
security settings within their browser using one of the two methods below:
Method A: Change Security Setting to
Medium-low
Method B: Change Individual Parameter Settings
Microsoft Office with WebADI
For patch requirements and required browser settings required to
integrate Microsoft Office with Oracle E-Business Suite, see Document
1077728.1.
Page Refresh
When using Oracle Self-Service products it is important to
ensure that the most current data is being viewed. You may check if the page
has been updated since your last visit by manually refreshing the page,
however it is desirable for this to be done automatically through IE by
setting the following parameter from the browser menu as follows:
IE7 and Higher Users
With this option set Internet Explorer will check if the page
has changed since it was last viewed.
IE6 Users
With this option set Internet Explorer will check if the page
has changed since it was last viewed.
Shared Desktop Security
If multiple users share the same desktop, they may be able to
view a previous users browser content by pressing the 'Back' button on the
browser. To avoid this issue set the Force Page Refresh profile option to Yes at Site level in your Oracle E-Business Suite 12 instance.
For security reasons, if a PC is shared by multiple users it is
also advisable not to save encrypted pages onto the drive by
navigating to
Tools -> Internet Options -> Advanced tab -> Security settings and ticking Do not save encrypted pages to Disk.
Exception: SSL users who export Discoverer Workbooks to
excel must leave the Do not save encrypted
pages to Disk parameter unchecked.
AutoComplete in Internet Explorer
IE can automatically show previous values entered in the same
form field. For privacy and security reasons this feature should be disabled
as follows:
Go to Tools -> Internet Options -> Content
-> AutoComplete -> Settings (button)
Uncheck the Forms and User names and passwords on form check boxes.
HTTP 1.1/Keep Alive Settings
Users should have the HTTP 1.1/Keep Alive option enabled.
To set this option, navigate to the following parameters from
the browser menu and ensure they are checked:
Importing an SSL Certificate into Internet
Explorer on Windows Vista, Windows 7 and Windows 8
Note: Windows 8 users may be required to run with
elevated privileges to install an SSL certificate into the browser
Connecting to a Secure Socket Layer (SSL) enabled environment
requires the certificate to be 'Trusted'. If the certificate is not from a
trusted authority or has not previously been trusted on the client, it must
be verified at runtime. When accessing such an environment it will return the
following warning message: 'There is a problem with this website's security
certificate'. Using the automatic default install button may cause the
certificate to be added to the browser's 'Intermediate Certification
Authorities' folder and not the required 'Trusted Root Certification
Authorities' folder. Therefore the security message will still display.
If the certificate has wrongly been installed into the
'Intermediate Certification Authorities' please remove it through the browser
and re-install into the 'Trusted Root Certification Authorities' folder.
Installing an SSL certificate into the Browsers Trusted
Certificates folder requires the browser's security option 'Enable
Protected Mode' to be disabled (not checked), which is the default
setting in the 'Trusted Sites' zone. This feature is only available in
Internet Explorer for Vista and Windows 7 and does not exist in the XP
versions of the browser. (If required, 'Enable Protected Mode' may be enabled
(checked) after the certificate has been installed for runtime use).
To trust the certificate authority and prevent the error page
appearing on future logins, install it as follows:
If the install button
is not active when trying to install the certificate, it may have been
installed previously using the automatic facility (Into the 'Intermediate
Certification Authorities' zone). To remove the certificate:
Due to issues with right side truncation, Windows 8 is not
certified for BiDi (Arabic and Hebrew) languages. A patch fix for this issue
is in progress.
Trying to post information between Oracle Projects and Microsoft
Projects will currently error when running on Windows 8. A patch fix for this
issue is in progress. For further information see Document
1077728.1 titled, 'Using Microsoft Office 2007 and 2010 with Oracle
E-Business Suite 11i and R12'
To prevent display issues within some FWK pages it is advisable
to run your Oracle E-Business Suite environment through IE 'Compatibility
Mode'. Some of these issues are highlighted below.
IE10 users may see the responsibilities under the main menu
displayed as 'undefined':
IE9 and IE10 users running in 'Browser Mode' may see button and
text misalignment as well as font changes within certain FWK pop ups and
other pages, for example when opening a 'Search and Select' window:
To workaround these issues, set the webpages to run through
Internet Explorer 'Compatibility Mode'. To set this as the default setting
for your domain:
Running through 'Compatibility Mode' should correct any button,
font or other display issues:
The issues outlined in this section are specific to users
running an IE 64-bit browser.
By design Microsoft do not allow the 64-bit version of Internet
Explorer to be set as the default browser on the desktop:
Tools -> Internet Options -> Programs (tab) -> Default
Web Browser
"Internet Explorer (64-bit) cannot be the default
browser."
Opening an HTML window from a third party application will
therefore use the default 32-bit browser which may require the user to login
to the appropriate Oracle E-Business Suite responsibility through this new
session.
Report Manager Default Browser Behavior
Financial Statement Generator reports that drill down into
General Ledger from Adobe Acrobat Reader or Microsoft Excel will open in the
user's default
browser. If the user has an active Oracle E-Business Suite session open
in the default browser, then when the user selects a drill down link, the
corresponding Oracle General Ledger page appears directly. If the user does
not have an active Oracle E-Business Suite session, or if the Oracle
E-Business Suite session is in another browser (e.g. 64-bit), then the Oracle
E-Business Suite login page appears first in the default browser, and the
user must log in and select a responsibility to access the Oracle General
Ledger drill down page. For ease of use, it is recommended that users
requiring this function run Oracle E-Business Suite in their default browser.
Oracle Product Workbench (IE8, 9 and 10)
Oracle Product Workbench will fail to launch when running
through an Internet Explorer 64-bit browser as the browser is unable to load
32-bit ActiveX controls. Please use a 32-bit version of Internet Explorer to
run this product.
Previous releases of Internet Explorer (IE7 and earlier) allowed
users to logon to the same Oracle E-Business Suite environment concurrently
from the same desktop by launching each application session through a new
browser session.
By default the ‘Session Merging’ feature introduced in IE8 prevents this functionality from working by default. This is because the same session id is used when accessing the same Oracle E-Business Suite environment. By default this will occur if you select New Window, New Tab or Duplicate Tab from the the browsers File menu, or if you open another browser window through the desktop browser icon. This can result in unusual behavior with invalid sessions causing errors such as “Your login session has become invalid" , "Unable to authenticate session" and failures to launch forms causing errors such as “FRM-92050: Failed to connect to the server: /forms/formservlet: -1"
To retain the use of multiple sessions through a separate
session id to the same Oracle E-Business Suite environment running IE8 and
higher please use one of the workarounds below to ensure each browser session
remains independent:
Unable to Authenticate Session
If you receive an 'Unable to authenticate session' error in your
browser when running multiple sessions, please set the -noframemerging option as outlined in the Multiple
EBS Sessions section above.
If this does not resolve the problem or you are not running
multiple sessions, please try clearing your browser cache by deleting the
'Temporary Internet Files' through:
Tools -> Internet
Options -> General (tab) -> Browsing History -> Delete (button)
Loosely-Coupled IE (LCIE)
Loosely-Coupled IE (LCIE) is standard IE browser behavior in IE8
and higher. This splits the browsers frame and its tabs into separate
processes on the desktop to improve performance and browser recovery if a tab
crashes. Oracle E-Business Suite users may be affected in the following ways.
Multiple Java Console Windows Open
With the 'Show Console' option set in the Java Control Panel,
launching a forms based application through IE8 or higher may cause two
separate 'Java Console' windows to open. Accessing further applets from the
same Oracle E-Business Suite session may also cause further 'Java Console'
windows to appear. This will not always be seen because not every tab will
necessarily be started in its own process because LCIE will attempt to
balance reliability with performance. Therefore the issue of multiple java
console windows is most likely to be seen if running from a high
specification multi-core processor desktop.
If required you can prevent the java console from appearing by
running the following from your desktop client:
Control Panel -> Java (icon) -> Advanced (tab) -> Java
Console -> select the 'Hide Console' (radio button)
Journal Approval from Email Notification
Due to LCIE, trying to approve a journal from an email
notification may cause the following error when running IE8 and later:
FRM-92050; failed to
connect to the sever;/forums/forums;-1
Steps to reproduce the issue:
To workaround this issue please turn LCIE off through the
registry as follows:
Cross-Site Scripting Error
Oracle E-Business Suite 12.0 and 12.1.1 users may see the
following error in the browser window when launching forms based application:
'Internet Explorer has modified this page to prevent a possible
cross-site scripting attack'
The required Forms 10.1.2.3 servlet components may not have been
deployed properly when Forms 10.1.2.3 was first installed in your Oracle
E-Business Suite Release 12 environment (Bug
8608695).
If your end-users running IE8 or higher encounter this error
when attempting to launch a Forms-based E-Business Suite product, redeploy
the Forms 10.1.2.3 formsapp.ear file by following Document
397174.1 titled, 'Deploying a New Forms .ear File in Oracle Applications
Release 12'.
When using IE9 or IE10 the digital signing of workflow
notifications will error with the message:
Verification of
signature has failed
Users wishing to use this function should remain on IE8 until a
fix is made available.
Note: The password signature for workflow
notifications will continue to work normally using IE9 or IE10.
Some users may find the iRecruitment Applicant Comparison Report
will not open when running Internet Explorer 8.x on Windows XP, the
application stops and you cannot choose whether to save or open the pdf file.
To fix this issue see Document
1579266.1.
The following issues are applicable for users running on Windows
Vista through IE7 or higher, and Windows 7 through IE8 and higher.
Balanced Scorecard Users
The VB client is not supported on Windows Vista or Windows 7.
Discoverer Users
Discoverer (10g) 10.1.2.3 is certified with Windows Vista. For
further information, see Document
456426.1.
Discoverer 10.1.2.2 and earlier are not certified with
Windows Vista or Windows 7.
Financial Analyzer and Sales Analyzer Users
Financial Analyzer and Sales Analyzer client versions (6.4) are
not supported on Windows Vista or Windows 7. Please use the OFA and OSA web
versions, see Document
470992.1.
XML Reports (RTF file extensions)
Windows Vista and Windows 7 users cannot open *.rtf format files
through the browser. When clicking the 'OK' button on the 'Opening *.rtf'
modal window the file will not open and the modal window will come up again.
To correct the problem, associate a different program such as Wordpad,
OpenOffice.org etc. with the .rtf extension on the desktop.
Discoverer Viewer Users
After clicking the drill icon on a worksheet the drill items are
not listed when running Discoverer Viewer through IE7 and higher. To fix this
issue:
Discoverer Viewer 10.1.2.0.2 and 10.1.2.1 and 10.1.2.2 users
should apply Patch 5673463. Please contact support to request this
patch.
Discoverer Viewer 10.1.2.2 Cumulative Patch (CP7) and lower users should apply Patch 5673463. Please contact support to request this patch. This issue is fixed in Discoverer 10.1.2.2 Cumulative Patch (CP8) and Discoverer 10.1.2.3 and higher.
Framework (FWK) Rich User Interface Features
The following Rich User Interface FWK features were introduced
in Oracle E-Business Suite 12.1.2:
Internet Explorer users wishing to utilize these features must
use Internet Explorer 7 or higher. These features are not supported for users
running Internet Explorer 6, please see the matrix below. If you require
further information please see Document
395441.1 titled, 'Oracle Application Framework Support Guidelines for
Customers'.
Certification Matrix for FWK Rich User
Interface Features
Tabbed Browsing in IE 7 and Higher
Forms Windows
IE7 and higher provides a tabbed browsing facility, which can be
enabled from the browser menu through Tools -> Internet Options ->
General Tabs -> Settings. Forms in Oracle E-Business Suite are supported
and launched through a separate frame. Therefore, even with tabs enabled, the
forms navigator and the forms windows will continue to open in a new window and
not in a new tab. This is intended functionality and is not a bug.
Web Based LOV's
When using IE7 or IE8 with the 'Always Open Pop-Ups in a New
Tab' browser option selected, focus is lost after opening the LOV in a new
tab causing the application to freeze. To unfreeze the application and regain
focus within the pop-up window press 'Ctrl & Tab'.
To workaround this issue please select a different value for
'When a pop-up is encountered; in the browser:
Navigate to: Tools
-> Internet Options -> Tabs -> Settings -> Always Open Pop-Ups in
a New Tab
Select either: Let Internet Explorer decide how pop-ups should open or: Always open pop-ups in a new window
Alternatively, to use the tabbed setting upgrade to IE9 or later
where this problem does not exist.
This issue is being evaluated through enhancement request Bug
9773527.
Exporting Data and Opening Attachments
JRE 1.6.0_27 (6u27) adheres more strictly to Internet Explorer
browser settings. Users may find that the File -> Export and Forms
Attachments functionalities (for example opening Word, rtf and Excel attachments)
will not work after upgrading to this Plug-in version when running IE6, IE7
or IE8. Trying to run these functionalities may cause a window to open
briefly before closing again, the 'File Download' window will not open.
To fix this issue please set the following browser setting
within IE under the appropriate security zone (using 'Trusted Sites' as an
example):
This setting no longer exists in IE9 and therefore these
functionalities are not affected when using this browser.
File Association
The file type that you wish to export from E-Business Suite must
be associated with the browser. If the file type is not associated, the
Window will not open or will briefly open and then close immediately. This
may occur for example, when using 'File -> Export' to an excel spreadsheet
or when opening an attachment from E-Business Suite.
To fix this issue, using the 'Trusted Sites' zone as an example,
(which is recommended for running Oracle E-Business Suite through):
Browser Helpers and Toolbars
The use of certain browser helpers and Toolbars may cause the
browser to crash when trying to login to Oracle E-Business Suite due to their
incompatibility with older plug-in versions. To remove a toolbar:
To disable an add-on:
SSL Users
Internet Explorer may display one of the following messages
through a modal window when running Oracle E-Business Suite in an SSL enabled
environment:
Do you want to view only the webpage content that was delivered
securely?
or
This page contains both secure and nonsecure items.
Do you wish to display the nonsecure items?
To stop this message appearing, using the 'Trusted Sites' zone
as an example:
Microsoft Internet Explorer ActiveX Update
912945
For details regarding this Microsoft update and its affect on
Oracle E-Business Suite, see Document
364366.1. This functionality is included by default in IE 7.
Certification
Matrix for Firefox (32-bit) browsers
Firefox: Prerequisite Patch Requirements Firefox: Recommended Browser Settings Firefox: Blocked Plugins in Mozilla Firefox Firefox: Importing an SSL Certificate Firefox: Known Issues
The table below outlines the currently certified Browser,
Desktop Client Operating System and JRE streams with minimum versions,
where applicable. Please also review this document for further specific
certification information and requirements:
1 Windows 7 (64-bit) desktop client operating system is currently
only certified with Oracle E-Business Suite when running 32-bit products e.g.
Client based products, Browsers, JRE plug-in and Microsoft Office.
2 Firefox versions 3.6.x
and higher only support
next-generation java plug-in releases (JRE 1.6.0_10 or higher). Forms based
products cannot be launched using 'classic java' versions (JRE 1.6.0_07 or
earlier). If a 'next generation java' plug-in version is not available on the
desktop client the browser will display the message, 'Additional plugins
are required to display all the media on this page'. If an appropriate
version is available from the Oracle E-Business Suite web server it can be
downloaded and installed in the usual way. Alternatively, clicking the 'Install
Missing Plugins' button or the 'Click here to download plugin' box
will activate the Firefox 'Plugin Finder Service' which will offer the
latest available version of the JRE plug-in for download and install.
3 Firefox ESR XX.x is an Extended Support Release (ESR) which
will be supported by the vendor for approximately a year. For further
information on the support lines and other information please see Mozilla
Firefox ESR Overview
4 Firefox versions 3.0.x, 3.5.x, 3.6.x and ESR 10.x are no
longer supported by the vendor. It is recommended that any users running
these versions upgrade to Firefox ESR 24.x.
3rd Party Software Support Lifecycle
Oracle's certification of the various third party client
operating system and browsers aligns with the respective vendor's support
life cycle.
Firefox versions 3.0.x, 3.5.x, 3.6.x and ESR 10.x are no longer
supported by the vendor. Firefox ESR 17.x is currently due to be de-supported
by the vendor on 3rd December 2013. It is therefore recommended that any
users running Firefox upgrade to Firefox ESR 24.x. Oracle will continue to
offer support for earlier Firefox versions with Oracle E-Business Suite R12
on a 'Best Effort' basis only. Consequently, where issues are due to problems
with the browser, we may, where necessary, require customers to upgrade or
change their browser to resolve the issue.
Compatibility with Higher JRE releases
Oracle has certified the Oracle E-Business Suite with the
minimum JRE releases noted above on the JRE 6 (1.6.0.x) stream. Oracle
E-Business Suite end-users may use or upgrade to later production releases of
the JRE 6 plug-in at their discretion. For further information on upgrading
JRE and it's requirements, please reference Document
393931.1 entitled 'Upgrading JRE (Native Plug-in) with Oracle E-Business
Suite 12 for Windows Clients'.
Oracle will continue to test and certify the Oracle E-Business
Suite with selected future versions of JRE releases in advance of their
general availability to the public. Oracle will update this documentation
with known compatibility issues or workarounds as needed. All current JRE
production versions equal to or higher than the minimum versions stated above
are compatible with Oracle E-Business Suite 12.
Firefox
Windows 8 Users
Firefox ESR 17.x and higher is certified as a client browser on
Windows XP SP3, Windows Vista SP1 & SP2, Windows 7 (32-bit & 64-bit)
and Windows 8 (32-bit and 64-bit) with the following prerequisite
requirements:
WebADI and Report Manager Users
WebADI and Report Manager have prerequisite patch requirements
when running on Windows 8, for further information see Document
1077728.1 titled, 'Using Microsoft Office 2007 and 2010 with Oracle
E-Business Suite 11i and R12'.
Known Issues
For known issues see Windows
8 Specific Issues
Windows XP, Vista and 7 Users
Firefox versions 3.5.x, 3.6.x and ESR 10.x and higher are
certified as client browsers on Windows XP SP3, Windows Vista SP1 &
SP2,Windows 7 (32-bit & 64-bit) with the following requirements:
Shared Desktop Security
If multiple users share the same desktop, they may be able to
view a previous users browser content by pressing the 'Back' button on the
browser. To avoid this issue please set the 'Force Page Refresh' profile
option to 'Yes' at Site level in your Oracle E-Business Suite 12 instance.
Mozilla has changed the way that third party plugins are handled
within Firefox to a 'Click to Play' model. (For further information please
see the Mozilla article Putting
Users in Control of Plugins.)
This function may affect Oracle E-Business Suite users running
Oracle Forms by prompting the user to activate or upgrade the JRE Plug-in
before a form can be launched. Users running the latest version of the JRE
Plug-in will generally not be affected by this change. It is however
recommended that all users trust the JRE Plug-in within Firefox for their Oracle
E-Business Suite environments to prevent this message appearing when running
old or blocked releases. For information on how to do this please see 'How to
always activate a plugin for a trusted website' outlined in the Mozilla
article Why
do I have to click to activate plugins?.
Note: It is recommended
that Oracle E-Business Suite users move to the latest available version of
the JRE Plug-in. For information on upgrading please see:
Document
393931.1: Deploying JRE (Native Plug-in) for Windows Clients in Oracle
E-Business Suite Release 12.
To trust the certificate authority and to stop this error page
appearing on future logins, add an exception:
1. Click the 'Add Exception...' button and the 'Add Security
Exception' window should open.
2. Check 'Permanently store this exception'.
If this checkbox is
grayed out you will first need to turn on History (this can be turned off
again after trusting the certificate) as follows:
Tools -> Options -> Privacy -> Set Firefox will:
Remember history
Click OK button
3. Click the Confirm
Security Exception button.
Internationalization
For information on internationalization issues with Firefox
please see the 'Browsers Notes' section of Document
393320.1 titled, 'Internationalization Update Notes for Release 12'.
Browser Window Opens Behind the Forms Window
Opening an html page from the forms navigator may cause the html
window to open behind the navigator window when using Firefox.
This issue is fixed in JRE 1.6.0_30 (6u30) and higher with the
following browser options set:
Framework (FWK) Rich User Interface Features
The following Rich User Interface FWK features were introduced
in Oracle E-Business Suite 12.1.2:
For browser support information for these features, please see
the matrix below. If you require further information please see Document
395441.1 titled, 'Oracle Application Framework Support Guidelines for
Customers'.
Certification Matrix for FWK Rich User
Interface Features
JRE Plug-in Download Using Firefox
(oaj2se.exe)
Oracle E-Business Suite 12.0.x Users
If using a non-static versioning model (Patch 7567840 has not been applied) and the
correct 'JRE Plug-in' version is not already installed on the client it will not
automatically download from the web server when using a Firefox browser. This
issue is fixed in Oracle E-Business Suite 12.0.6 Release Update Pack (RUP6), Patch 6728000.
To workaround this problem, the user can either download and
install the JRE Plug-in, before launching the Oracle E-Business Suite, or can
still download it from the server as follows.
Clicking on a forms link through Firefox will activate the
'Plug-in Finder Service'. The user will then see the message 'Additional
plug-ins are required to display all the media on this page' in the task
bar.
Forbidden
You don't have permissions to access /OA_JAVA/ on this server.
Multiple Sessions
You may only access a single Oracle E-Business Suite instance
from a single desktop session when using the Firefox browser. Currently 'Internet
Explorer' is the only browser that allows you to access multiple
instances or multiple Application Responsibilities concurrently from the same
desktop session, through the use of multiple browser sessions.
Multiple Desktop JRE Plug-in Versions
Firefox 3.0.x and higher supports 'Next-Generation JRE Plug-in'
technology which is enabled by default when running JRE 1.6.0_10 and higher.
Oracle E-Business Suite 12.0.x Users
It is strongly recommended Oracle E-Business Suite 12.0.x users
running Firefox 3.0 users apply Patch 7567840. Without this patch the latest JRE plug-in
version on the desktop would have to match the JRE plug-in version being
called from the web server to successfully load a form. See Multiple
Desktop JRE Plug-in Versions with Firefox (Static Versioning)
Whilst there is limited backward compatibility, using the
jpi-version attribute of the MIME type to select a particular JRE version is
no longer supported when using the next-generation JRE plug-in (JRE 1.6.0_10
and higher). This patch changes the behavior within Oracle E-Business Suite
Release 12 by removing the jpi-version parameter to overload the usage of the application/x-java-applet MIME type and implement the java_version parameter for JRE version selection. Further information is
available from the JRE
Version Selection page.
This patch changes the behavior of Firefox 3.0 to a 'non-static
versioning' model. Earlier 'classic' java versions can also be run on this
new architecture and they will also then adhere to a non-static versioning
model.
Oracle E-Business 12.1.1 Users
Oracle E-Business 12.1.1 users do not require Patch 7567840. This architectural change is included by
default making Firefox 3.0 adhere to the non-static versioning model.
For further information on static and non-static versioning
please see Appendix A: Static vs Non-Static Versioning and Set Up Options in Document
393931.1, titled, 'Deploying JRE (Native Plug-in) for Windows Clients in
Oracle E-Business Suite Release 12'.
(Return to Prerequisite
Patch Requirements section if required.)
By default, Firefox only uses the latest version of the plug-in
that it finds on the desktop client. Unless Oracle E-Business Suite is set to
use the latest available version of the plug-in, users may not be able to
connect using earlier versions of the plug-in.
To enable Firefox to use multiple versions of the Plug-in from
the desktop client, (thus allowing the use of JRE Plug-ins on the desktop
that are not the latest version installed on that desktop) the following
workaround can be used:
Copy '<jre plug-in install folder>\bin\npjpi<plug-in
version number>.dll' to '<Firefox
install folder>\plugins'.
(Using JRE 1.6.0_03 as an example in a default installation,
this would be) -
Copy C:\Program
Files\Java\jre1.6.0_03\bin\npjpi160_03.dll to C:\Program
Files\Mozilla Firefox\plugins
To check which
versions are available within Firefox type, 'about:plugins' in the address bar.
Note: This workaround is not valid when running
Firefox 3.0 with JRE 1.6.0_10 or higher installed on the desktop client.
Tab functionality in the Firefox Browser
Firefox uses tabbed browsing by default. Forms in Oracle
E-Business Suite are supported and launched through a separate frame.
Therefore, even with tabs enabled, the forms navigator and the forms windows
will continue to open in a new window and not in a new tab. This is intended
functionality and is not a bug.
Personal Homepage Setting
The ICX 'Personal Homepage' setting is not supported with the
Firefox browser.
Rich Text Editing
The Cut, Copy and Paste buttons within the Rich text Editor on
Oracle Applications Framework do not work by default when using a Firefox
browser. This is due to a security feature within Firefox. We recommend that
the keyboard shortcut keys, which do still work by default are used for this
functionality. If you still wish to use the buttons, this can be enabled by
editing the users Firefox preference file. Further information is available
from the Cut, Copy and
Paste Buttons and Security
preferences pages
BIDI Language Users
BIDI Languages are not supported with Self Service Applications
using the Firefox Browser.
Oracle Report Manager
Oracle Report Manager interaction with Excel will not work when
using the Firefox browser. This functionality requires the interaction of
ActiveX through VbScript, which is not supported in Firefox. Oracle Report
Manager users should run Internet Explorer for full functionality. Full
support through Firefox is being investigated.
Windows Vista and Windows 7 with Firefox
Balanced Scorecard Users
The VB client is not supported on Windows Vista or Windows 7.
Discoverer Users
Discoverer 10.1.2.3 is certified on Windows Vista. For further
information please see Document
456426.1.
Financial Analyzer and Sales Analyzer Users
Financial Analyzer and Sales Analyzer client versions (6.4) are
not supported on Windows Vista or Windows 7. Please use the OFA and OSA web
versions, see Document
470992.1.
XML Reports (RTF file extensions)
Windows Vista and Windows 7 users cannot open *.rtf format files
through the browser. When clicking the 'OK' button on the 'Opening *.rtf'
modal window the file will not open and the modal window will come up again.
To correct the problem, associate a different program such as Wordpad,
OpenOffice.org etc. with the .rtf extension on the desktop.
The tables below outlines the currently certified Browser,
Operating System and the certified JRE versions. Please also review this
document for further specific certification information and requirements:
For further information and patch requirements for Apple
Macintosh OS X version 10.7, 10.8 and 10.9, see Document
1533334.1 titled 'Oracle E-Business Suite Release Notes Release 12 for
Apple Macintosh OS X'.
For Internationalization information please see Document
393320.1, titled 'Internationalization Update Notes for Release 12'.
For further information and patch requirements for Apple
Macintosh OS X version 10.4, please see Document
402138.1, titled 'Oracle Applications Release Notes Release 12 for
Apple Macintosh OS X version 10.4'.
For further information and patch requirements for Apple Macintosh
OS X version 10.5 and 10.6, please see Document
864552.1, titled 'Oracle E-Business Suite Release Notes Release 12
(12.0, 12.1) for Apple Macintosh OS X v10.5 and v10.6'.
For Internationalization information please see Document
393320.1, titled 'Internationalization Update Notes for Release 12'.
Performance
From the Safari Menu, go to 'Preferences -> Security ->
Web Content' and select: 'Enable Plug-ins', 'Enable Java' and 'Enable
JavaScript'. Do not select 'Block Pop-Up Windows'. (Selecting this will cause
the Oracle E-Business Suite not to open).
From the Safari Menu go to 'Preferences -> Advanced' and
select 'Press Tab to highlight each item on a webpage'.
Framework (FWK) Rich User Interface Features
The following Rich User Interface FWK features were introduced
in Oracle E-Business Suite 12.1.2:
For browser support information for these features, please see
the matrix below. If you require further information please see Document
395441.1 titled, 'Oracle Application Framework Support Guidelines for
Customers'.
Certification Matrix for FWK Rich User
Interface Features
Related Notes
Document
389422.1 by Oracle E-Business Suite Development
Copyright © 2007, 2014 Oracle | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Thursday, January 23, 2014
Recommended Browsers for Oracle E-Business Suite Release 12
Monday, December 30, 2013
Hijrah Calendar Support in Oracle E-Business Suite Release 12
|
This document describes Hijrah calendar support in Oracle E-Business Suite R12.
In addition, Oracle Forms version must be upgraded to 10.1.2.2 first. Review Oracle MetaLink Note# 437878.1, then apply Forms one-off patch for bug 5843467. Client machine locale must be set to Arabic in order for Arabic text to be rendered correctly. Refer to MetaLink Note#393320.1 for how to set the locale with the Windows regional settings.
The date picker will show the English Hijrah calendar, with the first day of the week as Saturday. If you place the mouse cursor over a date cell, the tooltip shows the corresponding Gregorian date. When you click on the expansion button at the right bottom corner of the date picker, the corresponding Gregorian calendar pane is displayed next to it. 

Also, date type fields show the date in the calendar set to FND: Forms User Calendar. The user of the Hijrah Calendar MUST set "Date Format" preference to one with "MM". Refer to known issue #1 for more detail.
Over a cycle of 30 years there are 11 leap years.
There are 30 days in month number 1, 3, 5, 7, 9, and 11, and 29 days in month number 2, 4, 6, 8, 10, and 12.
In a leap year month 12 has 30 days.
In a 30 year cycle, year 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29 are leap years.
Total of 10631 days in a 30 years cycle.
The table shows the features described above.
Contents
- Scope of Support
- Overview
- Requirements
- Installation
- Deviation Days Setup
- Known Issues
Scope of Support
The support for Hijrah calendars is limited to Forms-based user interfaces. Flexfields embedded in the Forms-based user interface, however, still use the Gregorian calendar. In subsequent E-Business Suite releases, Oracle may enable Hijrah calendar support in flexfields as well as products or components that are based on Oracle Application Framework or BI Publisher. Oracle does not have plans to enable Hijrah calendar support in other E-Business Suite components or technologies such as Oracle CRM Technology Foundation (JTF), WebADI, Oracle Discoverer, or Oracle Reports. Only Hijrah calendars (Arabic and English) are currently supported. In the subsequent E-Business Suite releases, support for additional calendars, such as Thai Buddhist, is planned. Product Specific Information FormsOverview
ARU# 6193444 provides the necessary code to support the Hijrah calendar in EBS forms. The support includes a date picker showing the Hijrah calendarm and date type fields showing Hijrah dates.Requirements
Make sure your system has the following code levels before applying the Hijrah calendar support patch:- R12.AD.A.delta.4
- R12.ATG_PF.A.delta.4
In addition, Oracle Forms version must be upgraded to 10.1.2.2 first. Review Oracle MetaLink Note# 437878.1, then apply Forms one-off patch for bug 5843467. Client machine locale must be set to Arabic in order for Arabic text to be rendered correctly. Refer to MetaLink Note#393320.1 for how to set the locale with the Windows regional settings.
Installation
Apply ARU# 6193444 with adpatch. After patch application, all product Forms will need to be regenerated. Re-generate the FND message files as well. Bounce the oacore service after patch application. Enabling Hijrah Calendar Support: The following three profile options are added for non Gregorian calendar support:- FND: Calendar Week Start Day
- FND: Forms User Calendar
- FND: Tooltip Calendar
- FND: Calendar Week Start Day = "Sat"
- FND: Forms User Calendar = "English Hijrah"
- FND: Tooltip Calendar = "Gregorian"
Also, date type fields show the date in the calendar set to FND: Forms User Calendar. The user of the Hijrah Calendar MUST set "Date Format" preference to one with "MM". Refer to known issue #1 for more detail.
Deviation Days Setup
The setup for Hijrah calendar deviation days needs to be configured both on the database tier and on the Forms tier. Use the same deviation file. Refer to the following steps:- Place deviation file under $ORACLE_HOME/nls on both forms middle tier and database tiers. (Refer to the example of nlt file at the bottom of this section.)
- run lxegen on each tier. e.g. % lxegen It generates lxecalah.nlb and lxecaleh.nlb under the same directory.
- Restart middle tier and database.
- Invoke the date picker and confirm the deviation. For instance, after the setup, Gregorian date 09/01/2008 is Hijrah 1/1/1429. Before, it was Hijrah 30/12/1428
--- Sample of lxecal.nlt --- DEFINE calendar calendar_name = "Arabic Hijrah" DEFINE calendar_deviation deviation_data = { <"Jul-26-2006 ad">:1 <"Nov-21-2006 ad">:11 <"Apr-18-2007 ad">:1 <"May-17-2007 ad">:11 <"Jun-16-2007 ad">:1 <"Jul-15-2007 ad">:11 <"Aug-14-2007 ad">:1 <"Sep-12-2007 ad">:11 <"Oct-12-2007 ad">:1 <"Nov-10-2007 ad">:11 <"Jan-09-2008 ad">:1 } ENDDEFINE calendar_deviation ENDDEFINE calendar DEFINE calendar calendar_name = "English Hijrah" DEFINE calendar_deviation deviation_data = { <"Jul-26-2006 ad">:1 <"Nov-21-2006 ad">:11 <"Apr-18-2007 ad">:1 <"May-17-2007 ad">:11 <"Jun-16-2007 ad">:1 <"Jul-15-2007 ad">:11 <"Aug-14-2007 ad">:1 <"Sep-12-2007 ad">:11 <"Oct-12-2007 ad">:1 <"Nov-10-2007 ad">:11 <"Jan-09-2008 ad">:1 } ENDDEFINE calendar_deviation ENDDEFINE calendar --- end of sample of lxecal.nlt ---Note: this sample covers only recent years.
Freeman-Grenville Hijrah Calendar Calculation Algorithm
A year has 12 months.Over a cycle of 30 years there are 11 leap years.
There are 30 days in month number 1, 3, 5, 7, 9, and 11, and 29 days in month number 2, 4, 6, 8, 10, and 12.
In a leap year month 12 has 30 days.
In a 30 year cycle, year 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29 are leap years.
Total of 10631 days in a 30 years cycle.
The table shows the features described above.
# of month
|
Name of month
|
Number of days
|
1
|
Muharram
|
30
|
2
|
Safar
|
29
|
3
|
Rabi'al-Awwal
|
30
|
4
|
Rabi'ath-Thani
|
29
|
5
|
Jumada l-Ula
|
30
|
6
|
Jumada t-Tania
|
29
|
7
|
Rajab
|
30
|
8
|
Sha`ban
|
29
|
9
|
Ramadan
|
30
|
10
|
Shawwal
|
29
|
11
|
Dhu 'l-Qa`da
|
30
|
12
|
Dhu 'l-Hijja
|
29, but 30 days in years 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29
|
The algorithm is taken from the book, The Muslim and Christian Calendars by G.S.P. Freeman-Grenville.
Known Issues
- The "Date Format" preference for the Hijrah Calendar user MUST NOT include "MMM", the translated SHORT month name. For instance, go to "Preference". Make sure the "Date Format" value does NOT have "MMM". Or, search for the "ICX: Date format mask" option with "System Administrator" > Profile > System. Set the format with all numbers, not the translated short month name. This is because some of the short month names are the same. Also, they might be meaninglessly truncated.
- Hijrah and Thai calendars are only supported for Date Type fields. Character (text) Type fields show Gregorian dates. Similarly, dates embedded in error, informative, alert messages, or title bar may show up in Gregorian irrespective of the user preferred calendar.
- Flexfields embedded in the Forms-based user interface show Gregorian date.
- Oracle Foms UI embedded Beans Areas such as timeline of MRMS Maintain Contingent Workers or Scheduler Workbench of EAM always show Gregorian dates.
- Seeded data for "term" is Gregorian base. e.g. "Jan-00"
- Dates prior to July 16th, 622 AD are not supported in Hijrah calendar.
- While generating all the forms after applied ARU#6193444, one CSI Form gives error: following Oracle Forms objects did not generate successfully: csi forms/XX CSIIRTYP.fmx (XX is the oracle language code you’re generating.) bug#5863264 is tracking this issue, and it is planned to be resolved in the future. The workaround is to set the width and height property to 5 on the calendar canvas of $AU_TOP/forms/XX/CSIIRTYP.fmb. And re-generate it.
Hijrah Calendar Support in Oracle E-Business Suite Release 12
|
This document describes Hijrah calendar support in Oracle E-Business Suite R12.
In addition, Oracle Forms version must be upgraded to 10.1.2.2 first. Review Oracle MetaLink Note# 437878.1, then apply Forms one-off patch for bug 5843467. Client machine locale must be set to Arabic in order for Arabic text to be rendered correctly. Refer to MetaLink Note#393320.1 for how to set the locale with the Windows regional settings.
The date picker will show the English Hijrah calendar, with the first day of the week as Saturday. If you place the mouse cursor over a date cell, the tooltip shows the corresponding Gregorian date. When you click on the expansion button at the right bottom corner of the date picker, the corresponding Gregorian calendar pane is displayed next to it. 

Also, date type fields show the date in the calendar set to FND: Forms User Calendar. The user of the Hijrah Calendar MUST set "Date Format" preference to one with "MM". Refer to known issue #1 for more detail.
Over a cycle of 30 years there are 11 leap years.
There are 30 days in month number 1, 3, 5, 7, 9, and 11, and 29 days in month number 2, 4, 6, 8, 10, and 12.
In a leap year month 12 has 30 days.
In a 30 year cycle, year 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29 are leap years.
Total of 10631 days in a 30 years cycle.
The table shows the features described above.
Contents
- Scope of Support
- Overview
- Requirements
- Installation
- Deviation Days Setup
- Known Issues
Scope of Support
The support for Hijrah calendars is limited to Forms-based user interfaces. Flexfields embedded in the Forms-based user interface, however, still use the Gregorian calendar. In subsequent E-Business Suite releases, Oracle may enable Hijrah calendar support in flexfields as well as products or components that are based on Oracle Application Framework or BI Publisher. Oracle does not have plans to enable Hijrah calendar support in other E-Business Suite components or technologies such as Oracle CRM Technology Foundation (JTF), WebADI, Oracle Discoverer, or Oracle Reports. Only Hijrah calendars (Arabic and English) are currently supported. In the subsequent E-Business Suite releases, support for additional calendars, such as Thai Buddhist, is planned. Product Specific Information FormsOverview
ARU# 6193444 provides the necessary code to support the Hijrah calendar in EBS forms. The support includes a date picker showing the Hijrah calendarm and date type fields showing Hijrah dates.Requirements
Make sure your system has the following code levels before applying the Hijrah calendar support patch:- R12.AD.A.delta.4
- R12.ATG_PF.A.delta.4
In addition, Oracle Forms version must be upgraded to 10.1.2.2 first. Review Oracle MetaLink Note# 437878.1, then apply Forms one-off patch for bug 5843467. Client machine locale must be set to Arabic in order for Arabic text to be rendered correctly. Refer to MetaLink Note#393320.1 for how to set the locale with the Windows regional settings.
Installation
Apply ARU# 6193444 with adpatch. After patch application, all product Forms will need to be regenerated. Re-generate the FND message files as well. Bounce the oacore service after patch application. Enabling Hijrah Calendar Support: The following three profile options are added for non Gregorian calendar support:- FND: Calendar Week Start Day
- FND: Forms User Calendar
- FND: Tooltip Calendar
- FND: Calendar Week Start Day = "Sat"
- FND: Forms User Calendar = "English Hijrah"
- FND: Tooltip Calendar = "Gregorian"
Also, date type fields show the date in the calendar set to FND: Forms User Calendar. The user of the Hijrah Calendar MUST set "Date Format" preference to one with "MM". Refer to known issue #1 for more detail.
Deviation Days Setup
The setup for Hijrah calendar deviation days needs to be configured both on the database tier and on the Forms tier. Use the same deviation file. Refer to the following steps:- Place deviation file under $ORACLE_HOME/nls on both forms middle tier and database tiers. (Refer to the example of nlt file at the bottom of this section.)
- run lxegen on each tier. e.g. % lxegen It generates lxecalah.nlb and lxecaleh.nlb under the same directory.
- Restart middle tier and database.
- Invoke the date picker and confirm the deviation. For instance, after the setup, Gregorian date 09/01/2008 is Hijrah 1/1/1429. Before, it was Hijrah 30/12/1428
--- Sample of lxecal.nlt --- DEFINE calendar calendar_name = "Arabic Hijrah" DEFINE calendar_deviation deviation_data = { <"Jul-26-2006 ad">:1 <"Nov-21-2006 ad">:11 <"Apr-18-2007 ad">:1 <"May-17-2007 ad">:11 <"Jun-16-2007 ad">:1 <"Jul-15-2007 ad">:11 <"Aug-14-2007 ad">:1 <"Sep-12-2007 ad">:11 <"Oct-12-2007 ad">:1 <"Nov-10-2007 ad">:11 <"Jan-09-2008 ad">:1 } ENDDEFINE calendar_deviation ENDDEFINE calendar DEFINE calendar calendar_name = "English Hijrah" DEFINE calendar_deviation deviation_data = { <"Jul-26-2006 ad">:1 <"Nov-21-2006 ad">:11 <"Apr-18-2007 ad">:1 <"May-17-2007 ad">:11 <"Jun-16-2007 ad">:1 <"Jul-15-2007 ad">:11 <"Aug-14-2007 ad">:1 <"Sep-12-2007 ad">:11 <"Oct-12-2007 ad">:1 <"Nov-10-2007 ad">:11 <"Jan-09-2008 ad">:1 } ENDDEFINE calendar_deviation ENDDEFINE calendar --- end of sample of lxecal.nlt ---Note: this sample covers only recent years.
Freeman-Grenville Hijrah Calendar Calculation Algorithm
A year has 12 months.Over a cycle of 30 years there are 11 leap years.
There are 30 days in month number 1, 3, 5, 7, 9, and 11, and 29 days in month number 2, 4, 6, 8, 10, and 12.
In a leap year month 12 has 30 days.
In a 30 year cycle, year 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29 are leap years.
Total of 10631 days in a 30 years cycle.
The table shows the features described above.
# of month
|
Name of month
|
Number of days
|
1
|
Muharram
|
30
|
2
|
Safar
|
29
|
3
|
Rabi'al-Awwal
|
30
|
4
|
Rabi'ath-Thani
|
29
|
5
|
Jumada l-Ula
|
30
|
6
|
Jumada t-Tania
|
29
|
7
|
Rajab
|
30
|
8
|
Sha`ban
|
29
|
9
|
Ramadan
|
30
|
10
|
Shawwal
|
29
|
11
|
Dhu 'l-Qa`da
|
30
|
12
|
Dhu 'l-Hijja
|
29, but 30 days in years 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29
|
The algorithm is taken from the book, The Muslim and Christian Calendars by G.S.P. Freeman-Grenville.
Known Issues
- The "Date Format" preference for the Hijrah Calendar user MUST NOT include "MMM", the translated SHORT month name. For instance, go to "Preference". Make sure the "Date Format" value does NOT have "MMM". Or, search for the "ICX: Date format mask" option with "System Administrator" > Profile > System. Set the format with all numbers, not the translated short month name. This is because some of the short month names are the same. Also, they might be meaninglessly truncated.
- Hijrah and Thai calendars are only supported for Date Type fields. Character (text) Type fields show Gregorian dates. Similarly, dates embedded in error, informative, alert messages, or title bar may show up in Gregorian irrespective of the user preferred calendar.
- Flexfields embedded in the Forms-based user interface show Gregorian date.
- Oracle Foms UI embedded Beans Areas such as timeline of MRMS Maintain Contingent Workers or Scheduler Workbench of EAM always show Gregorian dates.
- Seeded data for "term" is Gregorian base. e.g. "Jan-00"
- Dates prior to July 16th, 622 AD are not supported in Hijrah calendar.
- While generating all the forms after applied ARU#6193444, one CSI Form gives error: following Oracle Forms objects did not generate successfully: csi forms/XX CSIIRTYP.fmx (XX is the oracle language code you’re generating.) bug#5863264 is tracking this issue, and it is planned to be resolved in the future. The workaround is to set the width and height property to 5 on the calendar canvas of $AU_TOP/forms/XX/CSIIRTYP.fmb. And re-generate it.
Hijrah Calendar Support in Oracle E-Business Suite Release 12
|
This document describes Hijrah calendar support in Oracle E-Business Suite R12.
In addition, Oracle Forms version must be upgraded to 10.1.2.2 first. Review Oracle MetaLink Note# 437878.1, then apply Forms one-off patch for bug 5843467. Client machine locale must be set to Arabic in order for Arabic text to be rendered correctly. Refer to MetaLink Note#393320.1 for how to set the locale with the Windows regional settings.
The date picker will show the English Hijrah calendar, with the first day of the week as Saturday. If you place the mouse cursor over a date cell, the tooltip shows the corresponding Gregorian date. When you click on the expansion button at the right bottom corner of the date picker, the corresponding Gregorian calendar pane is displayed next to it. 

Also, date type fields show the date in the calendar set to FND: Forms User Calendar. The user of the Hijrah Calendar MUST set "Date Format" preference to one with "MM". Refer to known issue #1 for more detail.
Over a cycle of 30 years there are 11 leap years.
There are 30 days in month number 1, 3, 5, 7, 9, and 11, and 29 days in month number 2, 4, 6, 8, 10, and 12.
In a leap year month 12 has 30 days.
In a 30 year cycle, year 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29 are leap years.
Total of 10631 days in a 30 years cycle.
The table shows the features described above.
Contents
- Scope of Support
- Overview
- Requirements
- Installation
- Deviation Days Setup
- Known Issues
Scope of Support
The support for Hijrah calendars is limited to Forms-based user interfaces. Flexfields embedded in the Forms-based user interface, however, still use the Gregorian calendar. In subsequent E-Business Suite releases, Oracle may enable Hijrah calendar support in flexfields as well as products or components that are based on Oracle Application Framework or BI Publisher. Oracle does not have plans to enable Hijrah calendar support in other E-Business Suite components or technologies such as Oracle CRM Technology Foundation (JTF), WebADI, Oracle Discoverer, or Oracle Reports. Only Hijrah calendars (Arabic and English) are currently supported. In the subsequent E-Business Suite releases, support for additional calendars, such as Thai Buddhist, is planned. Product Specific Information FormsOverview
ARU# 6193444 provides the necessary code to support the Hijrah calendar in EBS forms. The support includes a date picker showing the Hijrah calendarm and date type fields showing Hijrah dates.Requirements
Make sure your system has the following code levels before applying the Hijrah calendar support patch:- R12.AD.A.delta.4
- R12.ATG_PF.A.delta.4
In addition, Oracle Forms version must be upgraded to 10.1.2.2 first. Review Oracle MetaLink Note# 437878.1, then apply Forms one-off patch for bug 5843467. Client machine locale must be set to Arabic in order for Arabic text to be rendered correctly. Refer to MetaLink Note#393320.1 for how to set the locale with the Windows regional settings.
Installation
Apply ARU# 6193444 with adpatch. After patch application, all product Forms will need to be regenerated. Re-generate the FND message files as well. Bounce the oacore service after patch application. Enabling Hijrah Calendar Support: The following three profile options are added for non Gregorian calendar support:- FND: Calendar Week Start Day
- FND: Forms User Calendar
- FND: Tooltip Calendar
- FND: Calendar Week Start Day = "Sat"
- FND: Forms User Calendar = "English Hijrah"
- FND: Tooltip Calendar = "Gregorian"
Also, date type fields show the date in the calendar set to FND: Forms User Calendar. The user of the Hijrah Calendar MUST set "Date Format" preference to one with "MM". Refer to known issue #1 for more detail.
Deviation Days Setup
The setup for Hijrah calendar deviation days needs to be configured both on the database tier and on the Forms tier. Use the same deviation file. Refer to the following steps:- Place deviation file under $ORACLE_HOME/nls on both forms middle tier and database tiers. (Refer to the example of nlt file at the bottom of this section.)
- run lxegen on each tier. e.g. % lxegen It generates lxecalah.nlb and lxecaleh.nlb under the same directory.
- Restart middle tier and database.
- Invoke the date picker and confirm the deviation. For instance, after the setup, Gregorian date 09/01/2008 is Hijrah 1/1/1429. Before, it was Hijrah 30/12/1428
--- Sample of lxecal.nlt --- DEFINE calendar calendar_name = "Arabic Hijrah" DEFINE calendar_deviation deviation_data = { <"Jul-26-2006 ad">:1 <"Nov-21-2006 ad">:11 <"Apr-18-2007 ad">:1 <"May-17-2007 ad">:11 <"Jun-16-2007 ad">:1 <"Jul-15-2007 ad">:11 <"Aug-14-2007 ad">:1 <"Sep-12-2007 ad">:11 <"Oct-12-2007 ad">:1 <"Nov-10-2007 ad">:11 <"Jan-09-2008 ad">:1 } ENDDEFINE calendar_deviation ENDDEFINE calendar DEFINE calendar calendar_name = "English Hijrah" DEFINE calendar_deviation deviation_data = { <"Jul-26-2006 ad">:1 <"Nov-21-2006 ad">:11 <"Apr-18-2007 ad">:1 <"May-17-2007 ad">:11 <"Jun-16-2007 ad">:1 <"Jul-15-2007 ad">:11 <"Aug-14-2007 ad">:1 <"Sep-12-2007 ad">:11 <"Oct-12-2007 ad">:1 <"Nov-10-2007 ad">:11 <"Jan-09-2008 ad">:1 } ENDDEFINE calendar_deviation ENDDEFINE calendar --- end of sample of lxecal.nlt ---Note: this sample covers only recent years.
Freeman-Grenville Hijrah Calendar Calculation Algorithm
A year has 12 months.Over a cycle of 30 years there are 11 leap years.
There are 30 days in month number 1, 3, 5, 7, 9, and 11, and 29 days in month number 2, 4, 6, 8, 10, and 12.
In a leap year month 12 has 30 days.
In a 30 year cycle, year 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29 are leap years.
Total of 10631 days in a 30 years cycle.
The table shows the features described above.
# of month
|
Name of month
|
Number of days
|
1
|
Muharram
|
30
|
2
|
Safar
|
29
|
3
|
Rabi'al-Awwal
|
30
|
4
|
Rabi'ath-Thani
|
29
|
5
|
Jumada l-Ula
|
30
|
6
|
Jumada t-Tania
|
29
|
7
|
Rajab
|
30
|
8
|
Sha`ban
|
29
|
9
|
Ramadan
|
30
|
10
|
Shawwal
|
29
|
11
|
Dhu 'l-Qa`da
|
30
|
12
|
Dhu 'l-Hijja
|
29, but 30 days in years 2, 5, 7, 10, 13, 16, 18, 21, 24, 26, and 29
|
The algorithm is taken from the book, The Muslim and Christian Calendars by G.S.P. Freeman-Grenville.
Known Issues
- The "Date Format" preference for the Hijrah Calendar user MUST NOT include "MMM", the translated SHORT month name. For instance, go to "Preference". Make sure the "Date Format" value does NOT have "MMM". Or, search for the "ICX: Date format mask" option with "System Administrator" > Profile > System. Set the format with all numbers, not the translated short month name. This is because some of the short month names are the same. Also, they might be meaninglessly truncated.
- Hijrah and Thai calendars are only supported for Date Type fields. Character (text) Type fields show Gregorian dates. Similarly, dates embedded in error, informative, alert messages, or title bar may show up in Gregorian irrespective of the user preferred calendar.
- Flexfields embedded in the Forms-based user interface show Gregorian date.
- Oracle Foms UI embedded Beans Areas such as timeline of MRMS Maintain Contingent Workers or Scheduler Workbench of EAM always show Gregorian dates.
- Seeded data for "term" is Gregorian base. e.g. "Jan-00"
- Dates prior to July 16th, 622 AD are not supported in Hijrah calendar.
- While generating all the forms after applied ARU#6193444, one CSI Form gives error: following Oracle Forms objects did not generate successfully: csi forms/XX CSIIRTYP.fmx (XX is the oracle language code you’re generating.) bug#5863264 is tracking this issue, and it is planned to be resolved in the future. The workaround is to set the width and height property to 5 on the calendar canvas of $AU_TOP/forms/XX/CSIIRTYP.fmb. And re-generate it.
Friday, December 27, 2013
FDM Import Screen Hangs On "Processing.. Please Wait" on Client Workstations
FDM Import Screen Hangs On "Processing.. Please Wait" on Client Workstations
Modified:21-May-2013Type:PROBLEM
In this Document
Symptoms
Cause
Solution
APPLIES TO:
Hyperion Financial Data Quality Management - Version 11.1.2.1.000 and later
Information in this document applies to any platform.
SYMPTOMS
When running an import in FDM for a location that has around 8 pages of source records the FDM Screen hangs with "processing please wait..." and does not return back a gold fish status with the source data. If the same import process is ran locally to the FDM Server or on another server in the same data center the page refreshes properly.
CAUSE
The issue is related to the enabled firewall on the user's PCs. After disabling the firewall, this issue instantly disappeared.
SOLUTION
A) Disable Enabled Firewall on users PC (Symantec, McAffee, etc.)
Modified:21-May-2013Type:PROBLEM
In this Document
Symptoms
Cause
Solution
APPLIES TO:
Hyperion Financial Data Quality Management - Version 11.1.2.1.000 and later
Information in this document applies to any platform.
SYMPTOMS
When running an import in FDM for a location that has around 8 pages of source records the FDM Screen hangs with "processing please wait..." and does not return back a gold fish status with the source data. If the same import process is ran locally to the FDM Server or on another server in the same data center the page refreshes properly.
CAUSE
The issue is related to the enabled firewall on the user's PCs. After disabling the firewall, this issue instantly disappeared.
SOLUTION
A) Disable Enabled Firewall on users PC (Symantec, McAffee, etc.)
FDM Import Screen Hangs On "Processing.. Please Wait" on Client Workstations
FDM Import Screen Hangs On "Processing.. Please Wait" on Client Workstations
Modified:21-May-2013Type:PROBLEM
In this Document
Symptoms
Cause
Solution
APPLIES TO:
Hyperion Financial Data Quality Management - Version 11.1.2.1.000 and later
Information in this document applies to any platform.
SYMPTOMS
When running an import in FDM for a location that has around 8 pages of source records the FDM Screen hangs with "processing please wait..." and does not return back a gold fish status with the source data. If the same import process is ran locally to the FDM Server or on another server in the same data center the page refreshes properly.
CAUSE
The issue is related to the enabled firewall on the user's PCs. After disabling the firewall, this issue instantly disappeared.
SOLUTION
A) Disable Enabled Firewall on users PC (Symantec, McAffee, etc.)
Modified:21-May-2013Type:PROBLEM
In this Document
Symptoms
Cause
Solution
APPLIES TO:
Hyperion Financial Data Quality Management - Version 11.1.2.1.000 and later
Information in this document applies to any platform.
SYMPTOMS
When running an import in FDM for a location that has around 8 pages of source records the FDM Screen hangs with "processing please wait..." and does not return back a gold fish status with the source data. If the same import process is ran locally to the FDM Server or on another server in the same data center the page refreshes properly.
CAUSE
The issue is related to the enabled firewall on the user's PCs. After disabling the firewall, this issue instantly disappeared.
SOLUTION
A) Disable Enabled Firewall on users PC (Symantec, McAffee, etc.)
How to Start and Stop Financial Management (HFM) Server Windows Processes
How to Start and Stop Financial Management (HFM) Server Windows Processes
What are the main Windows processes of an HFM application server?
What happens when I start the HFM Windows Service?
What happens when I stop the HFM Windows Service?
Why should I use the HFM Windows Service?
When should I not use the HFM Windows Service?
Allowing HFM to start and stop as needed.
Why do I see multiple HsvDataSource.exe processes on an HFM application server?
When does the HsvDataSource.exe process stop itself?
Why might the HsvDataSource.exe not stop by itself?
What is the CASSecurity.exe process?
In what order should the HFM processes be stopped?
APPLIES TO:
Hyperion Financial Management - Version 1.0.0.0.00 and later
Information in this document applies to any platform.
PURPOSE
This document describes the starting and stopping of the main Windows processes that are seen in the Windows Task Manager of a HFM application server.
SCOPE
This document is intended for use by Hyperion Financial Management administrators with a good understanding of the Windows Task Manager, in particular the Processes tab.
DETAILS
What are the main Windows processes of an HFM application server?
The main Windows processes of a HFM application server are HsxService.exe, HsxServer.exe, CASSecurity.exe and HsvDatasource.exe.
What happens when I start the HFM Windows Service?
Oracle's Hyperion Financial Management can be started by starting the Windows Service "Hyperion Financial Management - Management Service". When this service is started, a process called HsxService.exe will become visible in the Windows Task Manager, and will remain running until the Windows Service is stopped. The HsxServer.exe, CASSecurity.exe and HsvDataSource.exe processes are also started.
What happens when I stop the HFM Windows Service?
When the Hyperion Financial Management Windows service is stopped, the HsxService.exe process will be stopped along with the HsvDataSource.exe, CASSecurity.exe and HsxServer.exe processes.
Why should I use the HFM Windows Service?
Oracle typically recommends that customers use the Windows Service approach only when their individual applications within their HFM database are known to take several minutes to start up. By starting the Windows Service, the application server will pre-launch each application, which will then be "active" and already started when the first user attempts to connect to the application. In this way, the user will not experience any "delay" while logging in, due to application startup time.
Applications may take longer to start up when their metadata dimensions are very large, when an application server or database is under heavy load, or when the rules file of the application contains a slow performing "NoInput" rules section. This section may take longer to execute if it contains many loop statements through many different metadata Point of View (POV) members. Care should be taken when designing metadata and NoInput rules routines to reduce the start up time of an individual application.
When should I not use the HFM Windows Service?
A potential disadvantage of using the Windows Service approach is that all applications are started, regardless of the true requirement and usage of the end users. If there are many applications that exist in the HFM database, unnecessary memory and CPU cycles may be used launching applications which are not needed by the end users. For this reason, Oracle recommends that customers not keep unused HFM applications in production environment HFM databases, or to not use the HFM Windows Service approach if there are known unused HFM applications in the database.
Allowing HFM to start and stop as needed.
If the HFM Windows Service is not being used as above, Financial Management will start itself when end users attempt to log on to an HFM application. When any end user connects to HFM for the first time on a particular application server, the process HsxServer.exe will be started. This process builds connections to the HFM database repository, authenticates the user connecting, and returns a list of available HFM applications within the database. There will only be one HsxServer.exe process on each application server. If the end user who connected to the HFM application server then proceeds to select an HFM application name to open, the HsxServer.exe process will then launch the HsvDataSource.exe Windows process to start that application. The HsxServer.exe process will remain running until there are no users logged on to that application server and all HsvDataSource.exe processes have also stopped.
Why do I see multiple HsvDataSource.exe processes on an HFM application server?
Hyperion Financial Management opens one HsvDataSource.exe (HSVDAT~1.EXE) process on the HFM server per active application. Connections are application specific. If multiple applications are opened, multiple HsvDataSource.exe processes will be launched.
When an application is opened, a database connection pool is created between the application process and the relational database (SQL Server / Oracle / DB2 etc). However, connections are not released on an application basis - they are released on an application server basis. All connections are not released until the application server has no Financial Management users accessing any application.
When does the HsvDataSource.exe process stop itself?
When an application server determines that all users of a particular application on that application server have correctly logged off or timed out (e.g. web time out), then it sends a signal to the HsvDataSource.exe process running that application to stop itself.
When all HsvDataSource.exe processes on a particular application server have stopped themselves, then the HsxServer.exe and CASSecurity.exe processes will also be stopped. After a short delay, under normal circumstances, all HFM processes will stop themselves. Only when all HFM processes on all HFM application servers have been stopped is it safe to make changes to the relational database for example, copying applications, taking or restoring backups of the database or powering down the database. Changes to the database should NOT be made while any HsvDataSource.exe process is seen running in the Windows Task Manager.
Why might the HsvDataSource.exe not stop by itself?
If end users log off incorrectly, their sessions may not have stopped. Hyperion Reports, Financial Reporting, Web Analysis, Financial Data Quality Management, Shared Services task flows or other modules may be holding open connections to Financial Management applications. All other Hyperion processes and services which may be connecting to Financial Management should be stopped first. Financial Management administrators may like to use the "Users on System" module of Financial Management to stop end user connections. When Financial Management decides that all connections have stopped, it should proceed to shut itself down automatically.
What is the CASSecurity.exe process?
Another Windows process is CASSecurity.exe. This is a process that manages the interface between Financial Management and Hyperion Shared Services modules. It handles some of the authorization and authentication processes of HFM, as well as security related features while the application is running. Important Note: Any change in the Shared Services external provider configuration REQUIRES the CASSecurity.exe process to be recycled in order gain access to the provider changes. Follow the "In what order should the HFM processes be stopped" section.
In what order should the HFM processes be stopped?
If Financial Management appears to have frozen / crashed it may be necessary to stop the processes. Processes should be stopped in the following order:
The Hyperion Financial Management Windows Service (HsxService.exe) should be stopped via the Windows Services if it seen to be running.
The HsvDataSource.exe for each application should be shut down. Ideally it should be observed that the HsvDataSource.exe is using 00% CPU in the Windows Task Manager before it is stopped using "End Process". Care should be taken when stopping running processes.
Any CASSecurity.exe process which is still running in the Windows Task Manager should be stopped using "End Process"
If any HsxServer.exe process is still running, it should be stopped using "End Process"
CAUTION: In a multi-server environment where multiple application servers are connecting to the same relational database, the process of stopping HFM should be repeated on ALL HFM application servers before attempting to restart any HFM processes or "bring up" the applications once again. It is not recommended to stop and start any one server independently but instead to stop the whole environment and then bring it back up.
What are the main Windows processes of an HFM application server?
What happens when I start the HFM Windows Service?
What happens when I stop the HFM Windows Service?
Why should I use the HFM Windows Service?
When should I not use the HFM Windows Service?
Allowing HFM to start and stop as needed.
Why do I see multiple HsvDataSource.exe processes on an HFM application server?
When does the HsvDataSource.exe process stop itself?
Why might the HsvDataSource.exe not stop by itself?
What is the CASSecurity.exe process?
In what order should the HFM processes be stopped?
APPLIES TO:
Hyperion Financial Management - Version 1.0.0.0.00 and later
Information in this document applies to any platform.
PURPOSE
This document describes the starting and stopping of the main Windows processes that are seen in the Windows Task Manager of a HFM application server.
SCOPE
This document is intended for use by Hyperion Financial Management administrators with a good understanding of the Windows Task Manager, in particular the Processes tab.
DETAILS
What are the main Windows processes of an HFM application server?
The main Windows processes of a HFM application server are HsxService.exe, HsxServer.exe, CASSecurity.exe and HsvDatasource.exe.
What happens when I start the HFM Windows Service?
Oracle's Hyperion Financial Management can be started by starting the Windows Service "Hyperion Financial Management - Management Service". When this service is started, a process called HsxService.exe will become visible in the Windows Task Manager, and will remain running until the Windows Service is stopped. The HsxServer.exe, CASSecurity.exe and HsvDataSource.exe processes are also started.
What happens when I stop the HFM Windows Service?
When the Hyperion Financial Management Windows service is stopped, the HsxService.exe process will be stopped along with the HsvDataSource.exe, CASSecurity.exe and HsxServer.exe processes.
Why should I use the HFM Windows Service?
Oracle typically recommends that customers use the Windows Service approach only when their individual applications within their HFM database are known to take several minutes to start up. By starting the Windows Service, the application server will pre-launch each application, which will then be "active" and already started when the first user attempts to connect to the application. In this way, the user will not experience any "delay" while logging in, due to application startup time.
Applications may take longer to start up when their metadata dimensions are very large, when an application server or database is under heavy load, or when the rules file of the application contains a slow performing "NoInput" rules section. This section may take longer to execute if it contains many loop statements through many different metadata Point of View (POV) members. Care should be taken when designing metadata and NoInput rules routines to reduce the start up time of an individual application.
When should I not use the HFM Windows Service?
A potential disadvantage of using the Windows Service approach is that all applications are started, regardless of the true requirement and usage of the end users. If there are many applications that exist in the HFM database, unnecessary memory and CPU cycles may be used launching applications which are not needed by the end users. For this reason, Oracle recommends that customers not keep unused HFM applications in production environment HFM databases, or to not use the HFM Windows Service approach if there are known unused HFM applications in the database.
Allowing HFM to start and stop as needed.
If the HFM Windows Service is not being used as above, Financial Management will start itself when end users attempt to log on to an HFM application. When any end user connects to HFM for the first time on a particular application server, the process HsxServer.exe will be started. This process builds connections to the HFM database repository, authenticates the user connecting, and returns a list of available HFM applications within the database. There will only be one HsxServer.exe process on each application server. If the end user who connected to the HFM application server then proceeds to select an HFM application name to open, the HsxServer.exe process will then launch the HsvDataSource.exe Windows process to start that application. The HsxServer.exe process will remain running until there are no users logged on to that application server and all HsvDataSource.exe processes have also stopped.
Why do I see multiple HsvDataSource.exe processes on an HFM application server?
Hyperion Financial Management opens one HsvDataSource.exe (HSVDAT~1.EXE) process on the HFM server per active application. Connections are application specific. If multiple applications are opened, multiple HsvDataSource.exe processes will be launched.
When an application is opened, a database connection pool is created between the application process and the relational database (SQL Server / Oracle / DB2 etc). However, connections are not released on an application basis - they are released on an application server basis. All connections are not released until the application server has no Financial Management users accessing any application.
When does the HsvDataSource.exe process stop itself?
When an application server determines that all users of a particular application on that application server have correctly logged off or timed out (e.g. web time out), then it sends a signal to the HsvDataSource.exe process running that application to stop itself.
When all HsvDataSource.exe processes on a particular application server have stopped themselves, then the HsxServer.exe and CASSecurity.exe processes will also be stopped. After a short delay, under normal circumstances, all HFM processes will stop themselves. Only when all HFM processes on all HFM application servers have been stopped is it safe to make changes to the relational database for example, copying applications, taking or restoring backups of the database or powering down the database. Changes to the database should NOT be made while any HsvDataSource.exe process is seen running in the Windows Task Manager.
Why might the HsvDataSource.exe not stop by itself?
If end users log off incorrectly, their sessions may not have stopped. Hyperion Reports, Financial Reporting, Web Analysis, Financial Data Quality Management, Shared Services task flows or other modules may be holding open connections to Financial Management applications. All other Hyperion processes and services which may be connecting to Financial Management should be stopped first. Financial Management administrators may like to use the "Users on System" module of Financial Management to stop end user connections. When Financial Management decides that all connections have stopped, it should proceed to shut itself down automatically.
What is the CASSecurity.exe process?
Another Windows process is CASSecurity.exe. This is a process that manages the interface between Financial Management and Hyperion Shared Services modules. It handles some of the authorization and authentication processes of HFM, as well as security related features while the application is running. Important Note: Any change in the Shared Services external provider configuration REQUIRES the CASSecurity.exe process to be recycled in order gain access to the provider changes. Follow the "In what order should the HFM processes be stopped" section.
In what order should the HFM processes be stopped?
If Financial Management appears to have frozen / crashed it may be necessary to stop the processes. Processes should be stopped in the following order:
The Hyperion Financial Management Windows Service (HsxService.exe) should be stopped via the Windows Services if it seen to be running.
The HsvDataSource.exe for each application should be shut down. Ideally it should be observed that the HsvDataSource.exe is using 00% CPU in the Windows Task Manager before it is stopped using "End Process". Care should be taken when stopping running processes.
Any CASSecurity.exe process which is still running in the Windows Task Manager should be stopped using "End Process"
If any HsxServer.exe process is still running, it should be stopped using "End Process"
CAUTION: In a multi-server environment where multiple application servers are connecting to the same relational database, the process of stopping HFM should be repeated on ALL HFM application servers before attempting to restart any HFM processes or "bring up" the applications once again. It is not recommended to stop and start any one server independently but instead to stop the whole environment and then bring it back up.
Thursday, December 26, 2013
These scripts are meant to provide the most commonly requested information.
These scripts are meant to provide the most commonly requested information.
Functional analysts with SQL and Unix access should be able to run these scripts and provide the information to Oracle Support.
User need to log into SQL plus to run the SQL scripts.
QUESTIONS AND ANSWERS
IMPORTANT:
Most of the information provided by the scripts below can be obtained from the RDA diagnostics, which is simple to perform and provides more complete information about the installed software. This should be the privileged set of information provided to Support.
You can find the RDA test for your APPS version in one of the following:
R12.0.6+ : All RDA Data Collection Test (Doc ID 732091.1)
R12.0.[3-4] : All RDA Data Collection Test (Doc ID 420427.1)
11i : Applications DBA RDA Data Collection Test (Doc ID 183274.1)
1. How to find versions of files in packages?
select text from dba_source
where name like '%&PKG_NAME%'
and line = 2;
Example:
select text from dba_source
where name = 'GLRX_JOURNAL_PKG'
and line = 2;
2. How to check if a patch is applied?
select * from ad_bugs
where bug_number = &bug_number;
select * from ad_applied_patches
where patch_name = &bug_number;
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 LIKE '&bug_number'
ORDER BY 1 DESC ;
3. How to find the patch set level for an application?
select substr(aa.application_short_name,1,20) "Product",
a.patch_level "Patch Level"
from fnd_product_installations a, fnd_application aa
where a.application_id = aa.application_id
and aa.application_short_name like '%&short_name%';
Example:
select substr(aa.application_short_name,1,20) "Product",
a.patch_level "Patch Level"
from fnd_product_installations a, fnd_application aa
where a.application_id = aa.application_id
and aa.application_short_name like '%AP%';
4. How to find instance name, host name, apps and RDBMS versions of the instance user is logged into?
select i.instance_name, i.host_name, f.release_name release, i.version
from v$instance i, fnd_product_groups f
where upper(substr(i.instance_name,1,4)) = upper(substr(f.applications_system_name,1,4));
5. How to find the latest version of a file on a given instance?
select sub.filename, sub.version
from (
select adf.filename filename,
afv.version version,
rank()over(partition by adf.filename
order by afv.version_segment1 desc,
afv.version_segment2 desc,afv.version_segment3 desc,
afv.version_segment4 desc,afv.version_segment5 desc,
afv.version_segment6 desc,afv.version_segment7 desc,
afv.version_segment8 desc,afv.version_segment9 desc,
afv.version_segment10 desc,
afv.translation_level desc) as rank1
from ad_file_versions afv,
(
select filename, app_short_name, subdir, file_id
from ad_files
where upper(filename) like upper('%&filename%')
) adf
where adf.file_id = afv.file_id
) sub
where rank1 = 1
order by 1
You can enter partial file names and the search is not case sensitive.
For example you can search on "glxjeent" for the form "GLXJEENT.fmb" or "frmsheet1" for java file "FrmSheet1VBA.class".
Note: This script works for the following file types:
- .class, .drvx, .fmb, .htm, .lct, .ldt, .o, .odf, .pkb, .pkh, .pls, .rdf, .rtf, .sql, .xml.
It doens't work for .lpc, .lc files, etc.
6. How to check the installation status and patch set level for a product?
Example 1
select patch_level, status from fnd_product_installations
where patch_level like '%FND%';
Example 2
select patch_level, status from fnd_product_installations
where patch_level like '%XDO%';
7. How to backup a table before users use sql to update the apps tables?
Example 1:
Create table ap_invoices_all_bkp as select * from ap_invoices_all;
Example 2:
Create table gl_interface_bkp as select * from gl_interface;
Note: SQL updates are not allowed unless directed to do so by Oracle Support or Development
8. How to find the table(s) name with the column name?
User knows the column_name but not sure what table(s) the column name is in.
Example:
select * from dba_tab_columns
where column_name like '%SET_OF_BOOKS_ID%';
This will provide the names of all the tables that has column_name SET_OF_BOOKS_ID.
9. How to check for invalid objects in a particular module?
select OWNER, OBJECT_NAME, OBJECT_TYPE
from DBA_OBJECTS
where OBJECT_NAME like 'FND_%'
and STATUS = 'INVALID';
select OWNER, OBJECT_NAME, OBJECT_TYPE
from DBA_OBJECTS
where OBJECT_NAME like 'AP_%'
and STATUS = 'INVALID';
10. How to check for invalid objects in all the modules?
select owner, object_name, object_type from dba_objects
where status = 'INVALID'
order by object_name, object_type;
11. How to find the applications in the system that are either installed shared?
select fat.application_id, FAT.APPLICATION_NAME, fdi.status, fdi.patch_level
FROM FND_APPLICATION_TL FAT, fnd_product_installations FDI
WHERE FDI.APPLICATION_ID = FAT.APPLICATION_ID
and fdi.status in ('I', 'S')
Note: Status 'I' meaning installed and status 'S' meaning shared.
12. How to determine database character set?
select value from nls_database_parameters
where parameter = 'NLS_CHARACTERSET';
The following scripts will provide NLS parameter and value for database, instance and session.
select * from nls_database_parameters;
select * from nls_instance_parameters;
select * from nls_session_parameters;
13. How to check the indexes on a table?
Example:
select index_owner owner, table_name tab, index_name ind, column_name colu, column_position position
from DBA_IND_COLUMNS
where table_name = 'GL_CODE_COMBINATIONS';
14. How to check for custom triggers on seeded tables?
Example:
select trigger_name, owner
from dba_triggers
where table_name = 'GL_BALANCES';
15. How to get the header file versions for an executable in Unix?
Example 1
Log into UNIX.
> cd $AP_TOP/bin
> strings -a APXXTR |grep Header
Example 2
> cd $RG_TOP/bin
> Strings -a RGRARG |grep Header
The above will provide the versions of all the header files in those executables.
Note: the command adident (in unix, windows and other OS) can also be used to provide the file versions.
Subscribe to:
Posts (Atom)