MultiOrg setting for Concurrent Request in R12

While you were upgrading to R12, if you will not implement MOAC, you should make relevant changes for Multi Org concept. In order your custom reports to be run properly, make them "Single" org to continue using without implementing MOAC.

• Login into application with 'System Administration' responsibility
• Click on 'Programs' under 'Concurrent' menu.
• Query for short name of the concurrent program (i.e. XXSIPRNT_CA ).
• Click on Update pencil icon of your program under result region
• Under 'Update Concurrent Program' region, select Request tab
• Under 'Request Setting' region, select 'Single' from the drop down of 'Operating Unit Mode' field
• Save changes by clicking on 'Apply' button.

Or

update FND_CONCURRENT_PROGRAMS
set multi_org_category='S'
where concurrent_program_id=45718;

Enabling OAF Personalization

To enable Personalization:

• FND: Diagnostics should be set to “Yes”. This will allow the “About this Page” link to be displayed on the OA pages.
• Personalize Self-Service Defn should be set to “Yes”. This will allow the “Personalize Page” link to be displayed on the OA pages.
• FND: Personalization Region Link Enabled should be set to “Yes”. This will allow the Personalize Region links to be displayed at the region level.
• FND: Developer Mode = YES (Optional for debugging)

Use Functional Administrator -> Core Services -> Profiles to change this.

R12 and JRE 1.5.10

In order to run R12, use JRE 1.5.10 which is located under the http:///OA_HTML/oaj2se.exe

After installing this, Internet Explorer and Firefox can run the R12 forms screens properly.

You may need to make adjustments on the Java Runtime settings in order your browser can use the proper version of Java. Check the following settings;

Settings -> Control Panel Java -> Java -> Java Application Runtime Settings

The "Show Log" feature in R12

The "Show Log" feature is available only to the System Administrator responsibility by default. Access is controlled using Function Security. Users can be granted access by including one or more of the following submenus or functions on a user's responsibility:

• Log Search: OAM_BF_SYSLOG_READ_ONLY_MENU (Log Search: Read Only) Menu
• Log Delete: OAM_BF_SYSLOG_DELETE (Log Delete) function
• Log Setup: OAM_BF_SYSLOG_CONFIG (Log Setup) function
• Full access (Search/Configure/Delete): OAM_BF_SYSLOG_ALL_MENU (Log Search: All Functions) Menu.

NOTE: After making these changes please ensure that you bounce Apache.

OAF JDeveloper Version

How to find the correct version of JDeveloper to use with E-Business Suite 11i or Release 12 - Use Metalink Note:416708.1

In order to find the information regarding your installation use the link of your EBusiness Installation;
http://host:port/OA_HTML/OAInfo.jsp

NOTE : Starting from 12.0.4 the page http://host:port/OA_HTML/OAInfo.jsp is not supported anymore, instead we need to login to Applications and select “About this Page” link. It will show us the OAF level and much more information.

Java class header Info

Sometimes, we may need to find the version of the class file for OAF pages. The following shell commend will help to find out relevant information about class file;

strings -a ArCusOvrCO.class | grep '$Header'

and, the output will look like;

Timezone in APPS

For time zone support to be activated, the system administrator must ensure that each of the following is true:

• Oracle E-Business Suite version 11i10 or higher
• Oracle RDBMS 9i or higher
• The database must be configured to use the time zone file 'timezlrg.dat' rather than the 'timezone.dat' file
• The database must be started in the standard corporate time zone
• Profile 'Server Timezone' (SERVER_TIMEZONE_ID) must be set at the Site level, and must be set to the same standard corporate time zone as the database
• Profile 'Client Timezone' (CLIENT_TIMEZONE_ID) must be set at the user level
• Profile 'Enable Timezone Conversions' (ENABLE_TIMEZONE_CONVERSIONS) must be set to 'Yes' ('Y') at the Site level.
• Profile 'Concurrent: Multiple Time Zones' (CONC_MULTI_TZ) should be set to 'No' (N) at the Site level

HRMS - fnd_session tip

Almost all the HRMS views have a join to fnd_sessions table. When user changes their date-track value, it gets reflected in fnd_sessions table. Use the SQL below to create a default record for your SQL*Plus session;

INSERT INTO fnd_sessions
(session_id
,effective_date)
(SELECT userenv('sessionid')
,SYSDATE
FROM dual
WHERE NOT EXISTS (SELECT 'c'
FROM fnd_sessions s1
WHERE userenv('sessionid') = s1.session_id));

Getting the Dependencies

This is a very easy task, in fact: Oracle maintains the relationships automatically and exposes them through three views. As such, we do not need to rely on reverse engineering DDL scripts.

• USER_DEPENDENCIES returns the dependencies of the objects owned by the current user.
• ALL_DEPENDENCIES returns the dependencies of the objects visible to the current user (so it's a superset of the former)
• DBA_DEPENDENCIES returns the dependencies of the all database objects. It requires SYSDBA privileges.

The most useful fields are returned by the following query:

select name, type, referenced_owner, referenced_name, referenced_type
from user_dependencies

whose results can be read as "The object name of type type depends on the object referenced_name of type referenced_type owned by referenced_owner (as implied by the use of user_dependencies, the owner of the name object is the current user). The referenced_owner column is useful to filter out various Oracle objects such as DUAL.

APPEND into tables

By using the APPEND hint, you ensure that Oracle always grabs "fresh" data blocks by raising the high-water-mark for the table. If you are doing parallel insert DML, the Append mode is the default and you don't need to specify an APPEND hint. Also, putting the table into NOLOGGING mode will allow Oracle to avoid almost all redo logging.

insert /*+ append */ into customer select (. . .) from customer_xx;

Selecting sample data from table

Sometimes you may need to select a percentage of data from the table to create test data. The following statement will select approximately 0.2 percent of the data in the table;

select * from RA_CUSTOMER_TRX_ALL sample(0.2);

Commit, commit_form and forms_ddl

commit
this is db command (only), not FORMS and if:

• form has upPOSTed statements they may be ignored
• form not fire PRE, POST, ON - commit triggers

commit execute as client side statement


forms_ddl(commit)

this is dynamic sql - commit and commit execute as server side. And form doesn't know about commit. it commits the all the DML transactions if any executed and pendig for commit .

commit_form

• It fires commit for all the database blocks on the form
• it commits the all the DML transactions if any executed and pendig for commit .