How does one enable trace for all actions that occur for a user?

The instructions for enabling the event trace follow:
a. First enable trace for a specific user:
- Bring up the Core application - System Administrator responsibility
- Move to Profile/System
- Check off the USER box - and enter your username that you are using when getting the error
- Search on the following profile option - 'Initialization SQL Statement - Custom'

Please set this at the user level with the following string:
BEGIN FND_CTL.FND_SESS_CTL('','', '', 'TRUE','','ALTER SESSION SET
TRACEFILE_IDENTIFIER='||''''|| '4269824.999' || '''' || ' EVENTS =' || '''' || ' 10046 TRACE NAME
CONTEXT FOREVER, LEVEL 12 '|| ''''); END;

(Cut and paste the above sql statement into the User Level profile option: "Initialization SQL - Custom")
This must be one complete line of text - so may be best to copy the string into notepad prior to putting it into the profile.

b. Once the profile is set, please change responsibilities and directly go and reproduce the problem.
To locate the trace file, use the following sql in sqlplus:
SQL> select name, value from v$parameter where name like 'user_dump_dest';

c. Note that a similar technique can be used for enabling trace with binds for a user in SQL*Plus. The commands would look like the following:
SQL> ALTER SESSION SET TRACEFILE_IDENTIFIER='577' EVENTS ='10046 TRACE NAME CONTEXT FOREVER,LEVEL 12';
SQL> select 'x' from dual; -- or any SQL that you want to trace
SQL> alter session set sql_trace = false;

Embed Oracle Applications Framework regions in a notification message

If you are using Oracle Applications and you have Oracle Applications Framework set up in Oracle JDeveloper for custom development, you can embed Oracle Applications Framework regions in a notification message. To embed a region, define a message attribute whose value is a Java Server Page (JSP) call that references the region.


The message attribute representing the region must be of type document and must have a source of Send. You can assign the attribute any appropriate internal name, display name, and description.

Specify the value for the attribute in the following format:
"JSP:/OA_HTML/OA.jsp?OAFunc="

Click here to know further

Useful list of scripts for OA Framework

This document helps the developer to get the scripts for the Apps Customization development. This will have all the OAFramework related components download from the server and upload the components from the laptop.

Click here to know more

OAF Page Deploy Commands

To load a page from file into MDS from unix platform.

adjava -ms128m -mx256m -nojit oracle.jrad.tools.xml.importer.XMLImporter XxnchZhsNotifExpLinesRN.xml -username apps -password appspassword -dbconnection "(description = (address_list = (address = (community = tcp.world)(protocol = tcp)(host = hostname)(port =1529)))(connect_data = (sid = dev4)))" -rootdir /u01/dev4/comn/java/oracle/apps/ap/oie/workflow/apexp/webui -rootPackage /oracle/apps/ap/oie/workflow/apexp/webui

To load a page from file into MDS from windows platform.

c:\9ijdeveloper\11i_generic\jdevbin\jdev\bin\import.bat c:\9ijdeveloper\11i_generic\jdevhome\jdev\myprojects\oracle\apps\xxtpc\cbt\webui\page1.xml -rootdir c:\9ijdeveloper\11i_generic\jdevhome\jdev\myprojects -userId 1 --username un -password pwd -dbconnection "(description = (address_list = (address = (community=tcp.world)(protocol = tcp)(host =hostname)(port = 1531)))(connect_data = (sid = sidname)))"

Oracle Workflow in Multiple Languages

WF_LANGUAGES View
Oracle Workflow uses a view called WF_LANGUAGES that identifies the languages defined in your Oracle installation. Oracle Workflow uses the WF_LANGUAGES view to create, in its translatable tables, a row for each language that maps to a row found in the corresponding non-translated base table. Installed_Flag column is the Flag to indicate if the language is installed and available for use. Ref Oracle Database Globalization Support Guide

Display Oracle Workflow Web Pages in Other Languages
For Oracle Workflow embedded in Oracle Applications, you select and install additional languages as part of the Oracle Applications installation. Users can set their language preference to an installed language through the Personal Homepage in order to view Oracle Applications screens in that language. See: Selecting NLS Settings, Installing Oracle Applications and Set Preferences, Oracle Applications User's Guide.


For the standalone version of Oracle Workflow, the server installation and upgrade are available only in English. To support access to Oracle Workflow web pages in another language, you must load that language after the installation using the Oracle Workflow Configuration Assistant. See the installation documentation for your release and platform.

The Oracle Workflow Configuration Assistant performs the following tasks to set up a language:


1. Runs the script wfnlena.sql to enable the language.
2. Runs the script WFNLADD.sql to create rows for the enabled language in each workflow object translation table.
3. Loads translated resource files for the user interface using the Workflow Resource Generator, translated versions of the standard and demonstration workflow definitions using the Workflow Definitions Loader, and translated Business Event System object definitions using the Workflow XML Loader.
Note: To display Oracle Workflow web pages properly, the character sets on the database tier and middle tier must match.

To Create and View Workflow Definitions in Other Languages using Oracle Workflow Builder


1. Set the NLS_LANG environment variable for the new language, territory, and encoded character set that you want to use for the workflow definition. For example, for Windows NT, run the regedit32 command and locate the NLS_LANG setting under the HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE hierarchy. Double click on NLS_LANG. Then set the variable to the new value and save your work. Specify the value for NLS_LANG in the following format:

LANGUAGE_TERRITORY.CHARSET

For more information about setting NLS_LANG, see: Globalization Support, Oracle Database Installation Guide.

2. Start Oracle Workflow Builder. Create a translated version of your workflow definition and save it as a flat file (.wft), or open and view a workflow definition that is already translated.

Note: Although you can enter and view property values for your workflow definitions in other languages, the Oracle Workflow Builder user interface is still displayed in English.

To Load Workflow Definitions in Other Languages to a Database


1. Ensure that the WF_LANGUAGES view has been created in your workflow server. This view is automatically created during installation.

2. Ensure that the language you want is set up in the database.

For Oracle Workflow embedded in Oracle Applications, you select and install additional languages as part of the Oracle Applications installation. See: Selecting NLS Settings, Installing Oracle Applications.

For standalone Oracle Workflow, the server installation automatically adds all available languages to your workflow database. See the installation documentation for your release and platform.

For standalone Oracle Workflow, the server installation and upgrade are available only in English. To support access to workflow definitions in another language, you must load that language after the installation using the Oracle Workflow Configuration Assistant. See the installation documentation for your release and platform.

3. Load the translated workflow definition to your workflow database using either the Workflow Definitions Loader or the Workflow Builder.

Before running the Workflow Definitions Loader program, you must set the NLS_LANG environment variable to the appropriate territory and character set for the workflow definition you want to load. The character set must match the character set encoding used to create the workflow definition file, which is determined by the NLS_LANG value that was set on the client PC before the .wft file was created in the Workflow Builder. For example, if the .wft file was created in the Japanese native character set encoding JA16SJIS, then you must specify JA16SJIS in the character set portion of NLS_LANG before loading the file, and you cannot specify a different character set such as UTF8.

To set NLS_LANG before running the Workflow Definitions Loader, use the following format:

_TERRITORY.CHARSET

Note that it is important to include the underscore (_) before the territory name and the period (.) between the territory name and the character set name in the NLS_LANG value. For example, if the .wft file was created in the Japanese native character set encoding JA16SJIS, set NLS_LANG to the following value:

_JAPAN.JA16SJIS.

You do not need to include the language in this NLS_LANG value because the Workflow Definitions Loader uses the language specified within the .wft file to determine the language to load.

Note: If you create all your translated workflow definition files in Unicode encoding, you can simply set NLS_LANG to .UTF8 before loading these files. In this case you will not need to reset NLS_LANG for translated files in different languages, because the .UTF8 character set applies to all the files in Unicode encoding.


Before using the Workflow Builder to save a translated workflow definition to the database, you must set the NLS_LANG environment variable to the appropriate language, territory, and character set. If you are saving several workflow definitions in different languages, you must reset NLS_LANG for each language. See: Opening and Saving Item Types, Oracle Workflow Developer's Guide.

Note: The translated versions of Oracle Workflow's standard and demonstration workflow definitions are provided in native character set encoding, not in UTF8.

To Send E-mail Notifications in Other Languages


1. Determine whether Oracle has translated the e-mail notification templates to the language you wish to set by checking for the file containing the templates in the appropriate language subdirectory, $ORACLE_HOME/wf/res/ for the standalone version of Oracle Workflow or $FND_TOP/import/ for the version of Oracle Workflow embedded in Oracle Applications. The standard templates are delivered in a file called wfmail.wft. See: Modifying Your Message Templates.

2. If the e-mail templates are available for the desired language, Oracle Workflow uses the language preference for the notification recipient to determine the language for an e-mail notification.

Oracle Applications users can set their language preference in the Preferences page. This preference is also stored in the ICX: Language profile option. See: Set Preferences, Oracle Applications User's Guide.

Note: In Oracle Applications, users can select a session-level language in the login window, which overrides their user-level language preference for that session. However, Oracle Workflow still uses the user-level language preference to determine the language in which e-mail notifications are sent.

For standalone Oracle Workflow, as the workflow administrator, you can specify the default language setting in the Global Preferences page. Individual users can override the default language setting by specifying their own preferred language in the User Preferences page. See: Setting Global User Preferences and Setting User Preferences, Oracle Workflow User's Guide.


Further reference Clcik here

XML Publisher Configuration File

•Customize the behavior of XML Publisher by setting properties in a configuration file.
•The configuration file is optional.
• No default configuration file is provided.
•The file is primarily used for: Setting properties for PDF, RTF, and HTML o/pSetting PDF security propertiesSetting font locations and substitutions Setting translation properties

Filename: xdo.cfg.
Location: /jre/lib

XML Publisher Tags

1. Sort Tag :> "sort:VOUCHER_NUM;'ascending';data-type='number'"

2. Row Column Highlighting :> "if@row:position() mod 2=0"

3. Creation of page total Elements : "add-page-total:TotalFieldName;'element'"

4. Displaying Page Total: "show-page-total:TotalFieldName;'Oracle-number-format'"

5. Re grouping: "for-each-group:BASE Group;Grouping Element" , "for-each:current-group(); GROUPING-ELEMENT"

6. Last Page Only : "start@last-page:body" "end body"

7. Variable Declaration : :variable name="lpp" select="number(5)"

8. Assigning Value to Variable : "xdoxslt:set_variable($_XDOCTX, 'variable name', value)"

9. Get Value from Variable : "xdoxslt:get_variable($_XDOCTX, 'variable name')"

10. MICR font can be linked by moving it to a UNIX directory and referencing the location in the Template

11. Extended SQL and XSL Functions : xdofx:expression

12. Dynamic Data Column header : split-column-header:group element name

13 Dynamic Data Column Data : split-column-data:group element name

For reference go through link

http://blogs.oracle.com/xmlpublisher/

http://www.scribd.com/doc/210892/XML-Publisher-17th-July-07