ATG Rup 6 Readme
ATG Rup 6 Readme
ATG Rup 6 Readme
Customers using AutoConfig must apply patch 5658489 (TXK). Customers who are not using AutoConfig must apply patch 5082356 (TXK) and refer to the readme file for patch 5658489(TXK) for more details.
Note: Customers who apply the TXK patches 5658489 or 5082356 must have installed a minimum of Oracle Developer Suite 6ipatchset 17 plus the CPU patches for Oracle Developer Suite 6i patchset 17, as listed in the Oracle Developer Suite Patches section of the Oracle E-Business Suite Critical Patch Update Note, October 2006, OracleMetaLink Note 391564.1. For information about upgrading Oracle Developer Suite 6i, see Information on Previous Versions of Developer 6i Patchsets, OracleMetaLink Note 232313.1.
Attention: Oracle Applications Technology 11i.ATG_PF.H.delta.6 can be applied only to an existing Oracle Applications Release 11i system running Oracle Applications Technology Family Pack 11i.ATG_PF.H , which is included in Oracle Applications Release 11.5.10. If you do not already have a running Release 11.5.10 system, then you must first install the Oracle E-Business Suite 11.5.10 or patch up to Applications Technology Family Pack 11i.ATG_PF.H (3438354). Refer to Installing Oracle Applications, Release 11i or Upgrading Oracle Applications, Release 11i and Oracle Applications Release Notes, Release 11i. To save upgrade time, you may merge Applications Technology Family Pack 11i.ATG_PF.H (3438354) and 11i.ATG_PF.H.delta.6 (RUP6) (5903765) on 11i.8 and above and apply. If you plan to merge and apply, make sure that all required pre-install steps and pre-requisite patches are applied before you apply the merged patch. For 11i.8 and 11i.9 refer to the 'Known Issues'
1. 2. 3. 4. 5. 6. 7. 8.
New and Changed Features New and Changed Components New and Changed Setup Steps Known Issues Instructions for Applying Oracle Applications Technology Update for 11i.ATG_PF.H.delta.6 Implementation and User Documentation Software Updates About Document Change Record
Target Audience:
The Database Administrator: Installs and configures the Oracle database and maintains database access controls. The System Administrator: Administers Oracle Applications systems.
dffBean.setWrapEnabled(true);
Wrapping is disabled by default.
FNDCPASS Utility New Feature: Enhance Security With Non-Reversible Hash Password
A single command line invocation of FNDCPASS USERMIGRATE utility migrates the encrypted passwords for all local Oracle Application Users (i.e. passwords for all users stored in FND_USER) to a non-reversible hash password scheme. For more information, see OracleMetaLink Note 457166.1, FNDCPASS Utility New Feature USERMIGRATE.
Oracle Workflow
Retry Errored Workflow Activities Program
The new Retry Errored Workflow Activities (FNDWFRET) concurrent program lets you retry activities with a status of ERROR for a particular item type. You can retry all errored activities for that item type, or you can choose to retry only activities for a particular work item of that item type, activities for a particular process within the item type, or instances of a particular activity node within the item type. You can also choose to retry only activities that encountered errors during a specific range of dates.
As of delta.5 (RUP5):
Oracle Application Framework
Oracle9i JDeveloper with OA Extension
Customers who intend to work with the Oracle JDeveloper9i OA Extension, and develop extensions to their installed OA Framework based self-service applications, must use the specific build of Oracle9i JDeveloper with OA Extension available. For customers upgrading to Oracle Applications Technology 11i.ATG_PF.H.delta.6 (RUP6), see the section above under delta.6 (RUP6) for the necessary patch number. Complete instructions for installing and configuring JDeveloper are included in the accompanying README file in this ARU and Chapter 1: Getting Started of the Oracle Application Framework Developer's Guide (see the Oracle Application Framework Release 11i Documentation Roadmap, OracleMetaLink Note 275880.1 for information on this document).
Parameter Security
Parameters can be passed to Oracle Web ADI from a form function to control the behavior of an Integrator. These parameters are defined as part of the Integrator by the relevant product. As the processing of undefined parameters is considered a security risk, any undefined parameters will now be discarded. Refer to the documentation for the Integrator or the product-specific documentation to check which parameters are available for use.
Oracle Workflow
Status Monitor Enhancements
You can now designate certain users as administrators only for particular types of workflows by assigning those users specialized workflow monitoring privileges with restricted access to workflow data. You can base the restrictions on a defined set of item types or on criteria specific to a particular functional area. In the administrator version of the Status Monitor, you can now drill down to child workflow information from the Activity History page, the Monitor Responses page, and the Workflow Details page. You can also now drill down to the Notification Detail page for a notification from the Activity History page.
Notification Enhancements
If you grant access to your worklist to another user, you can now choose whether to grant that user access to all your notifications, or only to notifications belonging to selected item types. If a user granted you access only to selected item types, then when you view that user's worklist, the page displays only notifications that belong to those item types. You can optionally give users access to the Notifications administrator Web page from any responsibility you choose by adding the WF_WORKLIST_SEARCH function to the menu for that responsibility. A user must have workflow administrator privileges to access other users' notifications in the Notifications administrator page; otherwise, the user can only search for his or her own notifications. A new internal notification mailer parameter named HTML_DELIMITER lets you specify which characters the notification mailer uses to delimit response values in response templates for HTML-formatted e-mail notifications. You can also define a special #WFM_HTML_DELIMITER message attribute to specify the delimiter for an individual notification message, overriding the notification mailer parameter value. You can now dedicate a notification mailer to process only instances of a particular message from a particular item type by specifying both the item type and the message name within the correlation ID.You can run command-line diagnostic tests for notification mailers through the new oracle.apps.fnd.wf.mailer.Mailer program.
o o o o
Test connectivity to the IMAP mail server. Test connectivity to the SMTP mail server. Test connectivity to the Web tier, which is required for the notification mailer to generate notifications that include Oracle Application Framework content. Check the number of messages in an IMAP folder or the total size of the messages in the folder in bytes, which indicates how much space you can regain by purging messages from the folder.
If the notification mailer cannot deliver an e-mail notification because the recipient's e-mail address is invalid, Oracle Workflow now sends a notification to the SYSADMIN user with the following information: that an e-mail notification could not be sent to one or more recipients; that the notification preference for those recipients has been set to DISABLED; and that those recipients' original notification preferences, which are listed, should be reset after the issues that caused the failures are corrected.
Oracle Alert
Reply To Address for Message Actions
When defining a message action for an alert, you can now specify the address that should receive the reply in the Reply To field in the Action Details window. The Reply To value must be either the reply-to address for the Workflow Notification Mailer, the e-mail address for a human in charge of response processing, or the address for a custom processing agent external to the notification mailer.
New Support
Support for a new profile option FND_OBIEE_URL "Oracle Business Intelligence Suite Enterprise Edition base URL Value" has been added. The profile option is populated by the AutoConfig variable s_fnd_obiee_url. The default value is null. Once OBIEE is installed customers should update this variables value to their equivalent of <protocol>://<machine.domain>:<port>." editable="Yes/> and rerun AutoConfig. The Concurrent Request log and output file can now be stored in each PROD_TOP by setting the context variable %s_applcsf% variable to "" and re-running AutoConfig.
The Windows script adtmplreport.cmd will no longer report AC-00053 file not found errors for adoraias_del.inf and ora806_del.inf.
Oracle Database
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT has now been AutoConfig-enabled to provide more flexibility. It is defined as %s_db_plsql_native_library_subdir_count% and has a default value of 149. The default value of s_db_sga_target is now 1GB. The initialization parameter SGA_TARGET specifies the total size of all SGA components. Up to Oracle9i Database, the value for this variable is calculated as the sum of spaces that are allotted to different components that come under SGA and set accordingly. But from Oracle Database 10g onwards, this is not manipulated; instead this value is set first and then the database decides the memory allocation for different components that come under SGA. For performance reasons, this value needs to be set to 1GB for Oracle Database 10g Release 2. For more information, seeDatabase Initialization Parameters for Oracle Applications 11i, OracleMetaLink Note 216205.1. LD_ASSUME_KERNEL is no longer set on the database node for Oracle Database 10g Release 2. Starting from Java version 1.4, IBM has split rt.jar into component jars for the AIX and zLinux platforms. For the AIX and zLinux platforms, instead of including rt.jar in the CLASSPATH, these component jars are now included in the CLASSPATH.
Cloning
The listener.ora file is now created as part of running adcfgclone.pl and no longer requires AutoConfig to be run again.
DataTemplateGenerator API converts the Oracle Reports data model to an XML Publisher data template. RTFTemplateGenerator API converts the Oracle Reports layout to an XML Publisher RTF template.
As of Rollup 4:
Oracle Alert
Oracle Alert now leverages the Workflow Notification Mailer to send alert e-mail messages and process responses. However, if you implemented response processing in an earlier release, you can continue running the Oracle Alert Response Processor as long as necessary to handle responses to alert messages sent prior to Oracle Applications Technology Family Pack 11i.ATG_PF.H Rollup 4.
When you create or update a custom Look-and-Feel, you cannot directly update an included style that has been added to a style or selector in your Look-and-Feel. Instead you must delete the existing included style and add a new one.
Extensions - Deploying
It is recommended that if you want to deploy your custom extensions, you copy the .jpx definition file(s) to the following staging area before running the jpx import utility to import the substitutions defined in the .jpx definition file to the MDS repository: $APPL_TOP/<CompanyIdentifier>/<AppsProductShortName>/<product-version>/java/
Oracle Workflow
Notification Enhancements
Users who have workflow administrator privileges can now reassign all notifications, regardless of any restrictions set through the #HIDE_REASSIGN attribute. This ability to override restrictions on reassignment lets administrators intervene when necessary in exception cases. If you use a URL attribute to include an image in a notification, you can now optionally add the prefix "LNK:" to the URL attribute value to specify that the image URL attribute should appear in the message body as a link when the notification is viewed from the Notification Details Web page or as an HTML-formatted e-mail. If you add the prefix "IMG:" or if you do not add any prefix, then the attribute appears as an inline image within the message body. You can now define the following special message attributes to control how e-mail notifications are generated.
o o o
#WFM_RESET_NLS - Lets you specify whether the notification mailer should convert the NLS codeset for the message according to the notification recipients preferences before composing the message. #WFM_CC - Lets you specify one or more secondary (CC) recipients for a notification e-mail message. #WFM_BCC - Lets you specify one or more additional non-displayed (BCC) recipients for a notification e-mail message.
The WF_EVENT_GROUPS document type definition (DTD) is enhanced to include the event names for the event group and event group member instead of their global unique identifiers. However, the Workflow XML Loader also still supports uploading event group member definitions that are structured according to the previous version of the DTD. Additionally, the combination of properties that defines a unique subscription definition no longer includes the phase number. Instead, the subscription is defined by the combination of its subscribing system, source type, triggering event, source agent, owner name, and owner tag. This enhancements lets you upload a changed definition for an existing subscription with a different phase number, instead of having to create an entirely new subscription definition with the new phase number.
wfbesdbg.sql - Displays debugging information for an event that you can use to check the status of the event or investigate errors. You can also obtain this information by running the Event Diagnostic Test within the Workflow Tests group in Oracle Diagnostics. wfevrtry.sql - Lets you abort or retry event subscription processing for all locally raised instances of a particular event that are enqueued on the WF_ERROR or WF_JAVA_ERROR queues and that have not yet been processed by an agent listener for these queues. wfntfrsp.sql - Lets you abort or retry event subscription processing for all instances of a particular event for which the SYSADMIN user has an open Local Event Error notification from the Default Event Error process.
Work items that use on-demand item attributes do have access to new item attributes added after the work items have been initiated. You do not need to create the attribute specifically for them through the AddItemAttr or AddItemAttributeArray APIs. However, if you delete an item attribute from the workflow definition in the database after the work item has been initiated, and the work item did not already make a runtime copy of the item attribute on demand, then that work item can no longer access the item attribute. You should plan carefully when deleting any item attributes to ensure that you do not remove attributes that active work items may still require.
As of Rollup 3:
Oracle Application Object Library
New Property Type for Blocks New Builtins Enhanced Ability to Find Objects
Dynamic poplists can now be used. Dynamic poplists display a different set of choices in each row, usually based on another attribute of the given row.
Oracle Workflow
Worklist Flexfields
Worklist flexfields let you display information specific to particular types of notifications in the Personal Worklist. Worklist flexfields are columns in the WF_NOTIFICATIONS table in which you can store information from different message attributes for different notifications. You can then display that information in a Personal Worklist view, enabling users to review important details about several notifications at once, without navigating to the Notification Details page for each notification. Users can also sort their worklists by the displayed message attributes.
New Workflow Engine bulk APIs let you launch multiple work items at once and set values for item type attributes in multiple work items at once. These APIs are supported only on Oracle9i Database or higher.
As of CU2:
Oracle Application Framework
Oracle E-Business Suite Home Page Enhancements
The Oracle E-Business Suite Home Page should now always be used. The Personal Home Page is no longer supported. The Applications region in the Oracle E-Business Suite Home Page has been renamed "Navigator". End users can edit the list of responsibilities in the Navigator.
Personalization Enhancements
The following features within Oracle Application Framework Personalization are new:
The Custom Look-and-Feel (CLAF) HTML editor allows you to create your own look and feel for your application pages. The Personalize Page Hierarchy feature on a page enables toggling between a Simple View, which displays specific page elements only, and a Complete View. Personalization now supports adding new types of content through the Create Item Page, including:
o o o
Region styles flexibleLayout, flexibleContent, and stackLayout. External HTML using the URL Include and Servlet Include beans. Item styles, including an Attachment link, Export button, Message File Upload, Message Download, and Form Value.
Simplest Possible Expression Language (SPEL) personalization on "rendered", "required", and "readOnly" property values. The Document Manager provides the ability to import, export, and delete personalization documents in the Metadata Services (MDS) repository and the file system.
Better error handling during data entry. Defaulting support for descriptive flexfield segments. Enhanced personalization support for flexfields.
Preferences Enhancements
The Preferences Page includes the ability to set a default start page other than the E-Business Suite Home Page, based on responsibility, and the ability to set separate session and default languages.
A history of applied patches. A list of active personalizations for the page and navigation for enabling, disabling, and modifying personalizations. Flexfield details and warnings. Page definition information in a hierarchical format. The ability to view the About Page as a means to recover from personalization errors.
Oracle Workflow
Business Event System "Skip to Next" Error Handling
A new error handling option, called "Skip to Next", is available for subscriptions in the Business Event System. With this type of error handling, the Event Manager rolls back only the subscription for which the error occurred and places the event message on a standard error queue. The Event Manager then continues processing the next subscription for the event according to the subscription phase order, allowing you to continue processing other subscriptions if appropriate.
o o
#WFM_LANGUAGE - Lets you specify the language for the e-mail message, overriding the language preference of the recipient role. #WFM_TERRITORY - Lets you specify the territory-dependent formatting for the e-mail message, overriding the territory preference of the recipient role.
The notification mailer program has also been enhanced to reduce exceptions due to invalid e-mail addresses. The notification mailer will now maintain a list of email addresses that previously caused exceptions and disable e-mail notifications for users with invalid e-mail addresses.
Workflow Purge
The Purge Obsolete Workflow Runtime Data concurrent program no longer lets you specify an Oracle XML Gateway transaction type and subtype to purge. Instead, you use the Purge Obsolete ECX Data concurrent program to purge Oracle XML Gateway transaction data according to transaction-related parameters. The Purge Obsolete Workflow Runtime Data concurrent program still purges Oracle XML Gateway data when appropriate according to workflow-related parameters. A new parameter in the Purge Obsolete Workflow Runtime Data concurrent program lets you specify how often the program commits data during purging, for performance tuning.
Oracle XML Gateway leverages the Oracle Workflow Business Event System to enable the exchange of JMS messages between the Oracle E-Business Suite and trading partners. JMS providers can integrate with XML Gateway for B2B transactions using the pre-defined queues WF_JMS_IN, WF_JMS_OUT, or using their own JMS queues registered with Business Event System. To use this feature, the appropriate protocol type (JMS) and protocol address (a JMS queue) must be set first in the Trading Partner Setup form.
Purge XML Gateway Transactions Using the 'Purge Obsolete ECX Data Concurrent Program'
XML Gateway uses a new 'Purge Obsolete ECX Data Concurrent Program' to specifically purge XML Gateway transaction data based on transaction type, transaction subtype, and date range.
OTA URL Validation Test A time limit of 30 seconds is added to the validation test process to avoid a long delay that could cause the browser to time out.
OTA URL List Extraction Test This new diagnostic test provides as output a list of URLs which are defined in the Protocol Address field in the Trading Partner Setup form for trading partners enabled for the HTTP or HTTPS protocol type. An output URL can be used as input to the OTA URL Validation Test for the URL validation.
As of CU1:
XML Publisher 5.0
Oracle Applications Technology Updates for Release 11i.ATG_PF.H CU1 includes a new version of XML Publisher, version 5.0. For more information on XML Publisher 5.0, see About Oracle XML Publisher 5.0, Note 295036.1. Note: Oracle XML Publisher 5.6.2 was released on May 8, 2006. Please refer to About Oracle XML Publisher Core Rollup Patch 5.6.2, Note 367394.1, for information about this latest version.
New Date Parameter Increment Option Parallel Concurrent Processing (PCP) and Failover Enhancements Enhanced Request NLS Options Print Control for Warned Requests Improved iAS Service Integration Introducing the CP Signature Wizard in OAM Native Client Encoding in Report Viewer
For detailed information, see "Oracle Applications Concurrent Processing (CP) Rollup Patch G", Note 291791.1.
New Object Type of LOV New Menu Entries The ability to "Get" a property in an expression Local Variable Support Form Level Support for Rules New Builtins Tab Pages can be modified even if they do not appear in the Object list Enhanced Debugging
Oracle Workflow
This consolidated update includes a new workflow concurrent program, Resend Failed Workflow Notifications. You can use this program to resend e-mail notifications after correcting conditions that caused the notification to have a status of FAILED.
JTFRS: Synchronize Employee as of date (MM/DD/YYYY) Synchronization for update employees will be based on this profile option. If it is not set (Null), then the program assumes the value as sysdate.
JTFRS: Restrict Group Update (HTML Resource Manager Only) Use this profile option to restrict group update access. The default value is set to "No" at the site level.
JTFRS: Business Group for Synchronizing Employees Use this profile option to determine whether to synchronize employees from all or only in the current business groups. The default value is set to "All" at the site level.
New Programs
Oracle Workflow
The Retry Errored Workflow Activities (FNDWFRET) concurrent program lets you retry activities with a status of ERROR for a particular item type.
Changed Programs
Oracle Workflow
The Resend Failed/Error Workflow Notifications (FNDWF_NTF_RESEND) concurrent program now includes From Date and To Date parameters to let you resend notifications that failed during a particular range of dates. The program also includes a Mail Status parameter to let you specify whether to resend notifications with a status of Failed or Error, as well as a Message Type parameter to let you resend only notifications that belong to a particular item type.
Oracle Workflow
The WF_DIRECTORY.GetRoleDisplayName2 function returns a Workflow role's display name given the role's internal name, whether the role is active or inactive.
As of delta.5 (RUP5):
Changed User Interfaces
Changed HTML Pages
Oracle Workflow
In the administrator version of the Status Monitor, the Activity History page, Monitor Responses page, and Workflow Details page now include a hierarchical grid that displays the process hierarchy formed by the selected workflow and any child workflows associated with it. The activity list in the Activity History page also includes a new Notification column that provides an icon linking to the Notification Detail page for any notification activity. Additionally, in the administrator version of the Status Monitor, the following pages now identify the displayed workflow by its workflow type internal name and item key, as well as by its user key, if it has one.
Child Workflows page Activity History page Status Diagram page Monitor Responses page Workflow Details page Workflow Errors page
In the self-service version of the Status Monitor, the following pages now identify the displayed workflow by its user key if it has one, or by its internal item key if it does not have a user key.
Notification History page Status Diagram page Monitor Responses page Error Summary page
If a user navigates from a link in an e-mail notification to the Notification Details page, and next navigates from the Notification Details page to the Worklist, then to enhance performance, the Worklist page initially shows only the table of notifications, without the Select column, action buttons, or table navigation controls. The user can still navigate through other features such as the subject links to the Notification Details page for his or her notifications. If the user accesses the Worklist for a second time or more in the same session, then the Worklist page displays the full control features for the table of notifications, including the Select column, action buttons, and table navigation controls.
New Programs
Oracle Workflow
The Workflow Directory Services User/Role Validation concurrent program (FNDWFDSURV) validates and corrects the information about user/role associations in the directory service. The oracle.apps.fnd.wf.mailer.Mailer program lets you run command-line diagnostic tests for notification mailers.
Changed Scripts
Oracle Workflow
The wfntfqup.sql script now checks the WF_NOTIFICATION_OUT queue for any alert e-mail messages and, if it finds any, exits without performing any changes. Instead, the script returns an error message that specifies how many alert e-mail messages are pending and indicates that these messages must be processed before the script can run.
As of Rollup 4:
Changed User Interfaces
Changed Forms Oracle Alert
In the Action Details window for actions of type Message, the Reply To field is no longer used. In the Oracle Alert Options window, the Mail Systems tabbed region, the Send Mail Account Description field in the More Options tabbed region, and the default Send Mail Account row in the Mail Server Options tabbed region are no longer used. Additionally, the remaining fields in the Mail Server Options tabbed region and the Response Processing tabbed region are used only if you are still running the Oracle Alert Response Processor to handle responses to alert messages sent prior to Oracle Applications Technology Family Pack 11i.ATG_PF.H Rollup 4.
Workflow System status page: Work Items graph, Agent Activity graph Agent Activity page: agent activity list Notification Mailer Throughput page: throughput graph Workflow Purge page: Completed Work Items list Active Work Items: work item list Deferred Work Items: work item list Suspended Work Items: work item list Errored Work Items: work item list
Oracle Workflow
The WF_RULE.Default_Generate API generates a simple set of event data from the specified event name, event key, and parameter list. You can assign this standard generate function to events for demonstration and testing purposes.
New Programs
Oracle Alert
Alert Action Processor (ALPPWF) - Performs response actions when Oracle Alert receives an e-mail response to an alert message No Response Action Processor (ALPPNR) - Checks for alert messages whose specified response days have passed without receiving a valid response and performs the no response follow-up actions
Oracle Workflow
Workflow Agent Activity Statistics Concurrent Program (FNDWFAASTATCC) - Gathers statistics for the Agent Activity graph in the Workflow System status page and for the agent activity list in the Agent Activity page. Workflow Mailer Statistics Concurrent Program (FNDWFMLRSTATCC) - Gathers statistics for the throughput graph in the Notification Mailer Throughput page. Workflow Work Items Statistics Concurrent Program (FNDWFWITSTATCC) - Gathers statistics for the Work Items graph in the Workflow System status page, for the Completed Work Items list in the Workflow Purge page, and for the work item lists in the Active Work Items, Deferred Work Items, Suspended Work Items, and Errored Work Items pages.
Changed Programs
Oracle Alert
The Response Processor (ALPPIM) concurrent program now only processes responses to alert messages sent prior to Oracle Applications Technology Family Pack 11i.ATG_PF.H Rollup 4.
Oracle Workflow
The Workflow XML Loader (oracle.apps.fnd.wf.WFXLoad) is enhanced as described in the New Features section.
Changed Profiles
Oracle Application Object Library
The Password Case Option profile has two options, 'Insensitive' and 'Sensitive' ('Mixed' is no longer supported).
Setting the Signon Password Case profile to Sensitive (or Insensitive) only affects *new* passwords that are changed after the profile is set. It does not attempt to go back and convert existing passwords. When authenticating users, all passwords will be tested using the case sensitivity policy that was in effect when the password was last changed. In other words, if the profile is currently set to Sensitive but this particular password was last changed when the profile was Insensitive, then password verification will still be Insensitive. If an administrator wants to force all passwords to be immediately case-sensitive, then along with setting the profile they should immediately expire all user passwords, to force everyone to change their password on next login. The new changed passwords will all be stored as case-sensitive.
As of Rollup 3:
New User Interfaces
New HTML Pages Oracle Workflow
Oracle Workflow includes the following new pages to support worklist flexfields:
Worklist Flexfields Rules page Create/Update Worklist Flexfields Rule pages Find Worklist Flexfields Rule Map Conflicts page Worklist Flexfields Rules Simulation page Find Worklist Flexfields Rule Conflicts page
The Oracle Workflow Manager component of Oracle Applications Manager includes the following new pages to support notification mailer configuration:
Create/Edit Workflow Mailer: Basic Configuration page Set Override Address page Verify Override Address page
Oracle Workflow
In the Oracle Workflow Manager component of Oracle Applications Manager, the advanced notification mailer configuration pages now display additional configuration parameters.
CreateProcess - Creates multiple new work items of the specified item type at once. StartProcess - Begins execution of multiple work items of the specified item type at once. FastForward - Creates multiple new work items of the specified item type at once and begins execution of these work items at the specified activity. SetItemAttrText - Sets values for item type attributes of type text, role, form, URL, lookup, or document in multiple work items. SetItemAttrNumber - Sets values for item type attributes of type number in multiple work items. SetItemAttrDate - Sets values for item type attributes of type date in multiple work items.
Oracle Workflow
The WF_NOTIFICATION.Send and WF_NOTIFICATION.SendGroup APIs now store denormalized values for any message attributes mapped by worklist flexfields rules in the designated worklist flexfields columns when sending notifications.
New Programs
Oracle Workflow
The Denormalize Worklist Flexfields concurrent program (FNDWFDCC) stores message attributes mapped by a worklist flexfields rule in the designated worklist flexfields columns for any currently open notifications from the specified item type.
The WF: Mailer Cancellation Email profile option is obsolete, replaced by the Send E-mails For Canceled Notifications mailer parameter.
As of CU2:
Changed User Interfaces
Oracle E-Business Suite Home Page
The Oracle E-Business Suite Home Page now has an customizable Navigator region.
Oracle Application Framework Page Hierarchy Personalization Page and the Create Item Page
These pages allow users to update, delete, or create an entity, primary key, and category maps for an attachment.
New Programs
Oracle Workflow: Move Messages from Exception to Normal Queue of Workflow Agent (FNDWF_MOVE_MSGS_EXCEP2NORMAL) Oracle XML Gateway: Purge Obsolete ECX Data Concurrent Program
XML Gateway uses the 'Purge Obsolete ECX Data Concurrent Program' to purge non-Workflow related XML Gateway transaction data based on transaction type, transaction subtype, and date range.
Event Name
Event Description
Status
If the value is set to 'No' (default), the transaction will be enabled regardless of the association between the user and the trading partner. If the value is set to 'Yes', XML Gateway will validate trading partner user against trading partner user setup data to determine if an inbound transaction can be processed.
Changed Programs
Purge Obsolete Workflow Runtime Data
The Transaction Type and Transaction Subtype parameters have been removed from the Purge Obsolete Workflow Runtime Data concurrent program. This functionality is replaced by the Purge Obsolete ECX Data concurrent program. The Commit Frequency parameter is added to the Purge Obsolete Workflow Runtime Data concurrent program.
As of CU1:
Note: For information on XML Publisher 5.0, see About Oracle XML Publisher 5.0, Note 295036.1.
New Programs
Oracle Workflow Resend Failed Workflow Notifications Page Access Tracking Purge Data
As of delta.5 (RUP5):
Oracle Web Applications Desktop Integrator
Using Oracle Web ADI with Microsoft Internet Explorer 7
Complete the following steps if you want to use Oracle Web ADI with Microsoft Internet Explorer 7. 1. 2. 3. Open Internet Explorer, click the Tools button, select Internet Options, and then click the Security tab. Select the security zone with which your Web site is associated, typically Local Intranet or Trusted Zones. Click the Custom Level button.
4. 5. 6.
Locate the Scripting setting "Allow status bar updates via script". Select the Enable radio button. Save this change by clicking the OK button.
wrapper.bin.parameters=-DAFLOG_ENABLED=true wrapper.bin.parameters=-DAFLOG_LEVEL=<1 for Statement level, 6 for Unexpected level> OTA logs only at either of these 2 levels. wrapper.bin.parameters=-DAFLOG_MODULE=ecx.oxa% wrapper.bin.parameters=-DAFLOG_FILENAME=<filename on midtier> If this parameter is omitted, logging doesn't fnd_log_messages table since anonymous logger without a JDBC connection is used.
As of Rollup 4:
Oracle Alert
The following setup steps are new for Oracle Alert in Oracle Applications Technology Family Pack 11i.ATG_PF.H Rollup 4:
Check that the Workflow Notification Mailer is set up and that its configuration meets your alert requirements. Schedule the No Response Action Processor concurrent program to run at least once a day using the Standard Request Submission windows.
For more information, see the Oracle Alert User's Guide. The following setup steps are changed for Oracle Alert:
You no longer need to use the Oracle Alert Options form to define the name and password of the e-mail account you want to use as the sender of alert messages. Oracle Alert now leverages the e-mail account set up for the Workflow Notification Mailer. If you implemented response processing in an earlier release, you can continue running the Oracle Alert Response Processor as long as necessary to handle responses to alert messages sent prior to Oracle Applications Technology Family Pack 11i.ATG_PF.H Rollup 4. The following setup steps are required only if you are still running the Response Processor: o Create an e-mail account for Oracle Alert
o o o
Define response accounts Create Reviewed and Reviewed_OK mail folders for response accounts Start the Response Processor
Note: If you install Oracle Alert or implement response processing for the first time in Oracle Applications Technology Family Pack 11i.ATG_PF.H Rollup 4 or higher, you do not need to set up the Response Processor.
4. Known Issues
For a list of current issues that exist on top of delta.6 (RUP6), see Note 459353.1, "External Tracking Note For Bugs On Top Of 11i.ATG_PF.H. delta.6 (RUP6) - 5903765".
As of delta.6 (RUP6):
Firefox 3.0 Certification
Apply patch 7651759 to obtain Firefox 3.0 certification fixes, including:
Fix for improper rendering of items under advance table. Fix for browser hanging after a partial page refresh. Fix for failure of submit buttons on the page after a partial page refresh. Fix for MessageRichTextEditor under a subtab that spans to 100% of the browser width and ignoring the width set on its container.
Note: Oracle Application Framework does not support ModalWindows in Firefox. The page button prompts may wrap in a lower resolution screen or a small-sized browser window.
PATCH_TOP/fnd/patch/115/import/US/fndobjt.ldt PATCH_TOP/fem/patch/115/import/US/femobjt.ldt
As of Rollup 4:
"File in patch is not a known Oracle Applications file : JTF MEDIA RUN_ENABLED.GIF"
Customers who have installed recent versions of Oracle Diagnostics may encounter this error. Download and apply patch5449280.
Oracle Payables
Customers with Oracle Payables will need to recompile the form APXXXDER.fmb after applying this patch.
Pre-install Steps
The following pre-install steps must be completed prior to applying Oracle Applications Technology 11i.ATG_PF.H.delta.6 (RUP6). If you already completed a step during a previous 11i patch application, then you do not need to complete the step again, unless otherwise specified.
Attention: The Oracle Applications Technology Updates for ATG_PF.H.delta.6 (RUP6) can be applied only to an existing Oracle Applications Release 11i system running Oracle Applications Technology Family Pack 11i.ATG_PF.H, which is included in Oracle Applications Release 11.5.10. If you do not already have a running Release 11.5.10 system, then you must first install the Oracle EBusiness Suite 11.5.10 or patch up to Applications Technology Family Pack 11i.ATG_PF.H (3438354). Refer to Installing Oracle Applications, Release 11i or Upgrading Oracle Applications, Release 11i and Oracle Applications Release Notes, Release 11i. To save upgrade time, you may merge Applications Technology Family Pack 11i.ATG_PF.H (3438354) and 11i.ATG_PF.H.delta.6 (RUP6) (5903765) on 11i.8 and above and apply. If you plan to merge and apply, make sure that all required pre-install steps and pre-requisite patches are applied before you apply the merged patch. For 11i.8 and 11i.9, refer to the 'Known Issues' section for merging. Step 1 Upgrade the RDBMS to Oracle 9iR2/10g or higher (Required)
Customers on 9iR2 (terminal patchset only, 9.2.0.8) can upgrade to 11i.ATG_PF.H.delta.6 (RUP6) without upgrading the database. See: Interoperability Notes: Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0), OracleMetaLink Note 216550.1. Note that valid support contracts are for Extended Support only. Otherwise, ensure your database is on Oracle 10g or higher before upgrading to 11i.ATG_PF.H.delta.6 (RUP6). See:Interoperability Notes: Oracle Applications Release 11i with 10g Release 2 (10.2.0), OracleMetaLink Note 362203.1.
Note: If your instance is on 11i.AD.I.2 with AD patch 5161680 (Patchset 11i.AD.I.DELTA.5), then there is no need to apply 11i.AD.I.5 (patch 5161676) explicitly. You need to follow only the "Post-Minipack Steps" described in About Oracle Applications DBA Minipack 11i.AD.I (AD.I.6), OracleMetaLink Note 233044.1 (this document is applicable to releases of AD.I prior to AD.I.6 as well).
5989593 - AD: 11i: Remove "REVOKE ALL FROM PUBLIC" from ADGRANTS.SQL 3218526 - BNE: Patch 11i.BNE.D - Refer to About Web Applications Desktop Integrator Mini-pack 11i.BNE.D, OracleMetaLink Note 287080.1, for installation instructions. 4206794 - FRM: Patch 11i.FRM.H - Refer to About Oracle Report Manager Minipack 11i.FRM.H, OracleMetaLink Note 378338.1, for installation instructions.
Apply the following patches if you are on a pre-11i.10 version of Oracle Applications:
3412795 - XDO: ADSPLICE Patch for XML Publisher 3036401 - HZ: Minipack 11i.HZ.L
Apply the following patches if you are on a pre-11i.9 version of Oracle Applications:
2614213 - AME Patch: Delivery of GA and Rule Priority Functionality 3120074 - PER: New: Interoperable Deliveries for Services Procurement Development (This patch is required to resolve the invalid package UMX_REGISTRATION_PVT.)
1.
2. 3. 4.
Establish the needed environment parameters by sourcing the Applications environment file as the owner of the application tier file system. Ensure "APPLRGF" variable is set in environment. If not, set it to the same value as "APPLTMP". From the location where this patch was unzipped, change directory to fnd/patch/115/bin. Run the utility as follows:
Platform
Command Line
./txkprepatchcheck.pl -script=ValidateRollup -outfile=$APPLTMP/txkValidateRollup.ht ml -appspass=<apps database password> %ADPERLPRG% txkprepatchcheck.pl -script=ValidateRollup -outfile=%APPLTMP %\txkValidateRollup.html -appspass=<apps database password>
The utility will produce an HTML report. Review any required actions before proceeding with the Applications Technology Updates. If you have difficulty producing or reviewing an HTML report, you may generate a text version by changing the 'outfile' suffix from .html to .txt and adding 'reporttype', as shown in this command line fragment:
6. -outfile=$APPLTMP/txkValidateRollup.txt -reporttype=text
u5903765.drv
Once you have successfully applied Oracle Applications Technology Updates for 11i.ATG_PF.H.delta.6 (RUP6), you must complete these additional steps. If you completed a task during a previous 11i patch application, then you do not need to complete the step again, unless otherwise instructed.
11i.10 Cumulative Update 2 with iStore 6408117 - iStore Takes to AppsHomePage After implemented and Login with Single SignOn (SSO) enabled
IBE
11i.10 Cumulative Update 2 with 6024690 - Error Thrown when Clicking on the Quotes QOT Quoting Tab implemented 11i.10, 11i.10 Cumulative 4619025 - Invalid Package Update 1, or CS_WF_ACTIVITIES_PKG 11i.10 Cumulative Update 2 11i.10, 11i.10 Cumulative Update 1, or 11i.10 Cumulative Update 2 with Knowledge Management implemented 5368595 - KM Pages Incorrectly Switch to Guest User Responsibility in iSupport Flow CSK This patch is required only if you are using Knowledge Management.
CS
11i.10, 11i.10 Cumulative 5357791 - Not Able to View Solutions Using 'IT:GIT Update 1, or Restricted iSupport' Responsibility 11i.10 Cumulative Update 2 with This patch is required only if you are using iSupport. iSupport implemented
IBU
11i.10 with Oracle HRMS Family 5970422 - ARU for Additional Data Page: LOV does Pack I, or later not Populate Segment Values HRMS Family Packs 11i.10 with Oracle Self-Service HR 5910548 - Patch for Bug 5879690 Failed - Core (product code HRMS PER) fully installed 11i.9 or 11i.10 with Business Intelligence implemented A release prior to 11i.10 A release prior to 11i.10 A release prior to 11i.10 A release prior to 11i.10 11i.9 Cumulative Update 2 with Quoting implemented 11i.9 Cumulative Update 2 11i.9 4429906 - Business Intelligence System Patchset 11i.BIS.L and 5212746 - Business Intelligence System Delta Patchset 11i.BIS.L.delta.4 2823215 - 11I 850 Poor POO Performance on Purchase Orders with 2500 Lines 3734468 - ARU with PO-EDI Integration group package 3950519 - ARU for Invalid IBU_OSS_RPT_DATA_OUT 3055250 - ARU with PO Code Release Package Dependency
BEN
PER
BIS
PO This patch is required to resolve the invalid package ECE_PO_ARCHIVE_PKG. 5977681 - Quoting HTML Page Gives Error QOT
3727065 - HRM_TCA_UTILITY_GET_PERSON_ID PER Required for Define User Form 5985611 - ARU for Adding Requirements to Project Apply if 11i.PJ_PF.M is installed with either of the following two patches: Patch 5105878: Oracle Projects Rollup Patch 3 for Oracle Projects Family Pack M (11i.PJ_PF.M) PJR
or Patch 5121501: Oracle Projects Resource Management Rollup Patch 3 for Oracle Projects Family Pack M (11i.PJ_PF.M) 4072748 - Dependency ARU for EDI SQL Scripts 11i.9 11i.9 11i.9 11i.9 or Service Suite Standalone Family Pack I 11i.9 with CADView-3D implemented This Order Management patch is required only if you are using Order Management EDI transactions. 3752448 - Copyloader May Fail with V904 XML Parser 4862093 - Invalid Package CS_WF_ACTIVITIES_PKG 5412759 - DDD Cumulative Patch 2853893 - One-Off Patch for IBAN Number Change in AP_BANK_ACCOUNTS Data Model 11i.8 This patch is required to resolve the invalid view ECE_PYO_PAYMENT_V. 11i.8 5056696 - Cannot Create Service Request ORA-04068 CSM (invalid CSM_UTIL_PKG ) AP ONT
DDD
11i.8 without Service Suite 4999113 - Invalid Object CS_WF_ACTIVITIES_PKG CS Standalone Family Pack I 11i.7 Any release for NLS customers, or any release using Oracle XML Gateway and applications dependent on it Any release with 4387493 - Missing IMTJSERV_UX.PROPERTIES Causes AutoConfig Errors 5194357 - Rehost XML Parser for PL/SQL v1.0.2+ for Oracle EBS 11i For NLS customers, this patch is required to resolve TXK issues with non-ASCII characters in Oracle Workflow notifications. For Oracle XML Gateway customers, this patch is required to resolve a memory issue with Oracle XML Gateway and its dependent applications. 5230979 - Patch 4334965 Invalidates MView ENI IMT
DBI 7.0 (3358654) or ENI_DBI_CO_OBJIDS_MV on 10g Database 11i.BIS_PF.E (4143498) applied Step 3 Apply SSO 10g Integration Patch. (Conditionally Required)
This step applies only to those E-Business Suite deployments that are integrated with Oracle Application Server 10g (Single Sign-On and Oracle Internet Directory). If the EBusiness Suite deployment is not integrated with Oracle Application Server 10g, you can skip this step. Do not apply this patch if you want to retain your existing Oracle Login Server 3.0.9 and Oracle Portal 3.0.9 integration. This patch includes libraries that are incompatible with Oracle Login Server 3.0.9. For this step, apply the following patch:
This patch delivers an updated Single Sign-On SDK; you will need to de-register and re-register all your SSO partner applications. Please follow Option 3 under "Appendix C: Advanced Configuration - Manual SSO/OID Registration" in the Installation Guide, OracleMetalink Note 233436.1, to de-register the partner applications first and then re-register them again. If you are integrating the E-Business Suite deployment with Oracle Application Server 10g for the first time, refer to OracleMetaLink Note 233436.1 for detailed instructions.
txkrun.pl -script=InstSSLFix
On Windows:
Step 5 : Upgrade Oracle XML Parser for Java v9.0.4 with Oracle Applications 11i. (Required)
Follow the instructions in OracleMetaLink note 271148.1 to configure and apply interoperability patches for Oracle XML Parser for Java v9.0.4.
The default initial size for the APPS_TS_TOOLS tablespace is 500 MB, with auto segment management enabled. If you create the APPS_TS_TOOLS tablespace through SQL*Plus, outside of the OATM utility, you can use the following statement: CREATE TABLESPACE APPS_TS_TOOLS DATAFILE 'datafile_name.dbf' SIZE 500M EXTENT MANAGEMENT LOCAL AUTOALLOCATE; You can override these storage recommendations with storage parameters to suit the expected size required for objects that will be in the Tools tablespace at your site.
Application User ANONYMOUS AUTOINSTALL CONCURRENT MANAGER FEEDER SYSTEM INITIAL SETUP MOBILEADM ASGADM WIZARD ASGUEST IEXADMIN IBE_GUEST IBE_ADMIN IBEGUEST OP_SYSADMIN OP_CUST_CARE_ADMIN IRC_EMP_GUEST IRC_EXT_GUEST FND/AOL
Product/Purpose
AD (Application DBA) FND/AOL AD (Application DBA) AD (Application DBA) Mobile Applications Admin Field Service/Sales Application Admin AD (Application DBA) Sales Application guest user Internet Expenses iSupport Guest user - 1 iSupport Admin user iSupport Guest user - 1 OP (Process Manufacturing) Admin User Customer Care Admin for Oracle Provisioning iRec Employee Guest Login iRecruitment External Guest Login
Condition Your installation requires all the users listed in the preceding table.
Action to Perform Change the passwords for all the required users, using either the User Maintenance page in the Oracle User Management responsibility or the Users form in the System Administrator responsibility. In this case you do not need to run the afdefusrdis.sql script.
Manually edit the afdefusrdis.sql script to comment out the users that are still required. Then log into SQL*Plus as the apps user and run the afdefusrdis.sqlscript. OR
Your installation requires only some of the users listed in the preceding table.
Disable the users that are not required by end dating those users, using either the User Maintenance page in the Oracle User Management responsibility or the Users form in the System Administrator responsibility.
Your installation does not require any of the Log into SQL*Plus as the apps user and run users listed in the the afdefusrdis.sql script. preceding table.
<item_type_name>:%
For example:
WFDEMO:%
Step 11 Run the Workflow Directory Services User/Role Validation concurrent program. (Required)
Run the Workflow Directory Services User/Role Validation concurrent program (FNDWFDSURV) to validate and correct the information about user/role associations. For more information on this concurrent program, see Setting Up Oracle Workflow,Oracle Workflow Administrator's Guide.
Step 12 Migrate Oracle Applications User Passwords to a Non-Reversible Hash Password Scheme. (Recommended)
Run the new FNDCPASS Utility introduced in 11.5.10 RUP 6 to migrate Oracle Applications User passwords to a non-reversible hash password scheme with a single commandline invocation. See OracleMetaLink Note 457166.1, FNDCPASS Utility New Feature USERMIGRATE, for more information. Oracle recommends you implement the non-reversible hash password scheme to enhance the security of your installation.
Step 13 Make the Corresponding Oracle Applications Technology Documentation Available to Your Users. (Recommended)
Oracle strongly recommends the installation of the latest documentation patch. At this time the latest documentation patch is6330890. This patch contains important implementation information for new features, end user documentation for new features, and updates to documentation for previously released features. Applying this documentation patch does not affect any setup or transaction processing. The patch contains only revised text and illustrations that appear when a user reads online help, and does not contain any revised executable files or seed data changes. This patch may be applied while users are on the system.
Best Practices for Securing the E-Business Suite, Knowledge Document 189367.1 Oracle Application Framework Release 11i Documentation Roadmap, Knowledge Document 275880.1 Oracle Application Server with Oracle E-Business Suite Release 11i Documentation Roadmap, Knowledge Document 207159.1 Oracle Applications CRM Technology (JTT) Release Notes and CRM System Administrator's Guide Addendum, Knowledge Document 353149.1 Oracle Workflow Documentation Updates for 11i.ATG_PF.H.delta.5 (RUP 5), Knowledge Document 412709.1 Oracle Workflow Documentation Updates for 11i.ATG_PF.H.delta.6 (RUP 6), Knowledge Document 431219.1 Oracle Application Object Library Documentation Updates for 11i.ATG_PF.H.delta.6 (RUP 6), Knowledge Document 457816.1 Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate, Knowledge Document 975182.1 Using Microsoft Office 2007 and 2010 with Oracle E-Business Suite 11i and R12, Knowledge Document 1077728.1
Additionally, the following documentation updates apply for 11i.ATG_PF.H.delta.6 (RUP6). This section includes updates from previous RUPs.
The following procedure from the Interface Data File chapter of the Oracle e-Commerce Gateway User's Guide has been updated for 11i.ATG_PF.H.delta.6 (RUP6). To change the interface data file: 1. 2. 3. Navigate to the Interface File Definition window. Select the transaction type. Select the transaction data level.
This identifies the level of data within the transaction defined in the e-Commerce Gateway for outbound transactions, and in the application open interface tables for inbound transactions. The levels may differ when compared to the base application tables as data is denormalized. All the records for the data level are displayed. The data format for outbound transactions is displayed by e-Commerce Gateway interface column. The data format for inbound transactions is displayed by application open interface column. You cannot change the data in these two columns. 4. Change the record number.
You can change the record number to another number within the same table level or enter blanks to exclude the record from the interface data file. The record number indicates the relative position of a group on that record in the file. No record can exceed 600 bytes. Note: To activate data elements, you must define the record number, record position number, and the width of the data element. Each level requires at least one data element active. 5. Change the record position number.
You can change the position number to another number within the record or enter blanks to exclude the column from the interface data file. The position number identifies the relative position of a data item in a record. 6. Change the width of the data element.
Most data elements have lengths based on standards. Those lengths are usually longer in Oracle Applications. You may increase the length up to the length in the Oracle application as needed per data element. 7. Change the sequence of external codes.
This identifies which external code (1 - 5) in the code conversion values table is placed on this data element in the transaction interface data file. The default is that external code 1 in the code conversion values table is moved to the external 1 code in the interface table, external code 2 in the code conversion values table is moved to the external 2 code in the interface table, and so on. For example, placing a sequence 5 next to data element external 1 means that the external code from the code conversion values table is moved into the data element external 1 in the transaction interface data file. A conversion sequence of 0 is reserved for the Oracle internal value. Do not change. 8. Change the record layout code.
This identifies the data content of a data element. These codes are predefined for the transaction. Standard record layouts for addresses and flexfields are defined and used across all transactions. Other record layouts are defined for a specific transaction. You may modify the predefined value. See: Record Layout Codes, Oracle e-Commerce Gateway Implementation Manual. These codes have no significant data mapping in business processes. They are used for reference for reviewing the file for research. Only the record layout code and record layout qualifier from the lowest numbered record position is used in the interface data file. 9. Change the record layout qualifier.
This identifies the type of data in the record. For example, a generic record layout code for addresses may have a record layout qualifier that identifies the address as a ship-to, billto, or remit-to address type. You may modify the predefined value. These codes have no significant data mapping in business processes. They are used for reference for reviewing the file for research. Only the record layout code and record layout qualifier from the lowest numbered record position is used in the interface data file. 10. If you want to define process rules, choose Process Rules. If you want to define column rules, choose Column Rules. The number of rules is displayed for reference.
lookandfeel_id.xml lookandfeel_id-metadata.xml
All of the style definition (.xss) files generated in $HTML_TOP/cabo/styles. Note: For every custom LAF you create, one .xss file is generated, named lookandfeel_id.xss.
All .uit files that you placed in the folder $HTML_TOP/cabo/templates/lookandfeel_id. Note: To customize the template renderer of each component, you must create a componentName.uit file and place it in $HTML_TOP/cabo/templates/lookandfeel_id.
All custom image (.gif) files that you placed in the folder $HTML_TOP/cabo/images/lookandfeel_idwhen you created the custom LAF by that ID. Note: To customize icons for a custom LAF, you must place its custom images in the folder$HTML_TOP/cabo/images/lookandfeel_id
3.
To make the newly transferred LAF accessible on the customer's site, you must add lookandfeel_id as a lookup value to the APPLICATIONS LOOK AND FEEL lookup type. You can do this in one of two ways: o Extract the LDT file for the original APPLICATIONS LOOK AND FEEL lookup and the Oracle Applications Look And Feel profile, and apply the LDT to the customer site. This will add the value of the new lookandfeel_idto the customer's APPLICATIONS LOOK AND FEEL lookup type. For more information, refer to the Generic Loader section in the Loaders appendix of the Oracle Applications System Administrator's Guide Configuration, which you can find in the Oracle Applications Documentation Library.
WARNING: Although this is the preferred method, it will overwrite all of the existing lookup and profile values, including any that the customer has modified. To avoid this, use the following method.
o
Manually add the value of the new lookandfeel_id to the customer's APPLICATIONS LOOK AND FEEL lookup type. This method has the benefit of not disturbing any existing look and feel modifications on the customer's system. You need to use the developer form for Application Object Library Lookups. Access the APPLICATIONS LOOK AND FEEL lookup type, and add a new lookup entry with the same value as the name of the new LAF that you are implementing. For more information, refer to the section on Application Utilities Lookups and Application Object Library Lookups in the Additional Developer Forms appendix of the Oracle Applications Developer's Guide, which you can find in the Oracle Applications Documentation Library. The following procedure is added to the Administrative Level Personalization User Interface chapter of the Oracle Application Framework Personalization Guide for 11i.ATG_PF.H.delta.6 (RUP6):
Setting the Record Set Size property for each nodeDefinition item defined under an HGrid An administrator can set the value for the Record Set Size property of each nodeDefinition to control the Record Set Size at each level. To set the Record Set Size value: 1. 2. 3. 4. 5. Navigate to the Personalize Page Hierarchy - Administrator Personalization page for the HGrid page to be personalized. In the Personalization Structure HGrid, locate the HGrid to be personalized in the Name column. For the HGrid, click on the Personalize icon for the nodeDefinition item for which the Record Set Size value needs to be set. In the Personalize Node Definition - Administrator Personalization page set the desired value for the Record Set Size property. Select Apply.
After making this change, the administrator must navigate back to the home page and then return to the application to see the record set size change take effect. The Record Set Size Property value of the HGrid should be set to a value greater than zero for the Record Set Size property value set at the nodeDefinition level to take effect.
Oracle Alert
The following procedure from the Defining Alerts chapter of the Oracle Alert User's Guide has been updated for 11i.ATG_PF.H.delta.5 (RUP5). To define message actions: 1. 2. 3. Choose Message in the Action Type field of the Action Details window if you want the alert to send a message as its action. Specify the electronic mail IDs of the recipients you want to send your message to in the To field. You can also enter the IDs of recipients to whom you want to send "carbon" (Cc) and "blind" (Bcc) copies of your alert message. If you list more than one recipient in any of these recipient fields, separate each recipient by a space, or a comma, or a combination of the two. You can enter as many recipients as you want, up to 240 characters. You can also enter in the List field, a distribution list that you define in the Distribution Lists window. If you enter a distribution list name, Oracle Alert displays all electronic mail IDs on the list in the To field, and does not let you change any values in the To, Cc, Bcc, Print For, or Printer fields. 4. 5. In the Reply To field, you can optionally specify the address that should receive the reply to the alert message. This address must be either the reply-to address for the Workflow Notification Mailer, the e-mail address for a human in charge of response processing, or the address for a custom processing agent external to the notification mailer. If you leave this field blank, the Workflow Notification Mailer uses the value of its own Reply-to Address configuration parameter instead. You can also have Oracle Alert print your message to the printer you specify in the Printer field. Enter in the Print For User field, the names, or alert outputs or response variables that represent the names of the recipients for whom you want to print a copy of the message. Separate the names by commas and do not use blank spaces within a name. Oracle Alert prints the message preceded by a banner page with the name as it appears in the Print For User field. You can enter as many names as you want, up to 240 characters. 6. 7. In the Subject field, enter a brief statement that describes the message's subject matter. You can enter up to 240 characters. You can also enter alert outputs or response variables in any of the alert detail fields. Oracle Alert automatically substitutes the associated output value when checking the alert or the associated response variable value when reading the response. By entering an output or response variable rather than a mail ID in a recipient field, you can make use of dynamic distribution. For example, if you define an alert that reminds users to change expired passwords, you can define an alert output called &USER to hold the user's electronic mail ID. Enter &USER in the To: field to have Oracle Alert send a message to each user whose password has expired. 8. For a detail message action, you can either send the contents of a file as the message, or write the text of your message in Oracle Alert. If you want to write your message in Oracle Alert, choose the Text option and enter the text in the Text field. (You can also click on the Import button and import the contents of a file into the Text field.) You can include any outputs in the message text. If you want to send the contents of a file, choose the File option and enter the file name (including the full path), or the output from the alert Select statement that represents the file name and location, in the File field. You may use any outputs to construct the file name. Note: If this message action has a response set associated with it, you must define the text of the message within Oracle Alert. 9. 10. 11. For detail message actions, Oracle Alert distributes one message for each exception found during an alert check. Place outputs wherever you need to in the message text, to format your message as you like. When Oracle Alert sends the message it substitutes the output variables with the exception values found during the alert check. If this action is a response action, identify your response variables with an ampersand before the name, for example, &VARIABLE_NAME. Oracle Alert reads the value for a response variable from the response message. If the response message does not include the response variable, Oracle Alert uses the default value from your response variable definition. For a no exception message action, Oracle Alert distributes a message when no exceptions are found for an alert check. Do not use outputs to define your no exception message and recipients.
Note: If you decide to change the Action Level of your action after entering message text in the Text field, you must delete the message text yourself. Oracle Alert does not automatically delete the text for you. Important: For detail or no exception message actions, the message text that you specify in Oracle Alert must be less than 2000 characters, while the message file that you specify must be less than 32K. 12. 13. 14. For summary message actions, complete your action details by following the instructions listed in the next section. Save your changes. When you are finished defining actions, close the Actions and Action Details window and choose Action Sets to define the action set(s) for your alert definition.
7. Software Updates
5161676 AD:MINIPACK 11I.AD.I.5 5473858 ATG_PF:11i.ATG_PF.H.RUP5 1674411 FND:FND_MSG_PUB:SUBSTR causes ORA-06502 when handling non 8-bit characters 2920516 OWF:115101: REQINFO:MORE INFO WORKFLOW PARTICIPANT LIST DOES NOT HAVE FROM ROLE 3206418 FND:APP_STANDARD.EVENT('WHEN-VALIDATE-RECORD') MISSING FROM FNDSCAUS & FNDSCRSP 3650294 JTT:M1159SYS: CONNECTION LEAK 4160339 OWF:DO NOT REFERENCE MEMBER VARIABLES IN WEB/APPSCONTEXT SUBCLASSES 4276392 FND:AOLQA : VALUES GREATER THAN MAXSIZE DEFINED IN VALUESETS ARE ACCEPTED. 4483634 OWF:UPGRADE WFDIRCHK.SQL SCRIPT 4532756 FND:UNABLE TO REVERT THE LOOKUP TYPE TO THE GLOBAL SECURITY DEFINITION 4631123 FND:ICM DOES NOT UTILIZE SECONDARY NODE IN IT'S OWN MIGRATION 4653165 OAM:PERF: OAM - PERFORMANCE ISSUES IN CP MANAGER MONITORING 4705060 UMX:USER CREATION IN SECURITY: INVALID EMAIL VALIDATION FAILURE 4899697 TXK:REHOSTING ORACLE JDBC THIN DRIVERS V9.2.0.8+ FOR USE WITH APPS 11I 5042954 OWF:INCONSISTENCY BETWEEN JMS QH ENQUEUE AND DEQUEUE 5096839 OWF:PRINTSTACKTRACE SHOULD BE REMOVED FROM GSC AND MAILER JAVA CODE 5329609 XDO:NLS:COMMON REGION: PLEASE REMOVE "DEFAULT" TEMPLATE LOCALE 5354477 FND:USER LEVEL PROFILE VALUE IS INTERMITTENTLY RETURNED 5367396 OAM:TEST STATUS SHOULD BE 'SEVERE ERROR' IF TEST ENDS WITH EXCEPTION 5389430 OWF:SOME GARBAGE ARABIC CHARACTERS ON WORKFLOW MAIL BODY 5444378 OWF:P2R: PAC REL: 'REQUEST FOR MORE INFO ' FUNC IS NOT WORKING WITH WF ROUTING RULE 5450788 FND:Unexpected request cancel behavior due to inadequate record locking 5467610 FND:FND_USER_RESP_GROUP VIEWS AND FND_USER_RESP_GROUPS_API UPDATE 5475482 FND:XML PUBLISHER REPORTS FAIL TO RUNS WITHIN REQUEST SETS 5475896 FND:IMPLEMENT USAGE OF TABLE HANDLER FND_PROFILE_OPTION_VALUES_PKG 5572911 FND:TRACKING BUG FOR FND_GLOBAL & FND_PROFILE SECURITY CTX MISMATCH (REF: 4864506) 5574945 FND:AUDITTRAIL: QUERY NAVIGATOR FIND DOES NOT PROPERLY RESTRICT RESULTS 5633265 FND:HELP-ABOUT ORACLE APPS NEEDS TO SHOW VALUE OF PROFILE "JAVA COLOR SCHEME" 5653545 FND:FNDPMNET:FRAME TEXT NEEDS CHANGING 5670542 OWF:AFTER PATCH 5609865 XML PARSER IMPORTS INCOMPLETE 2ND AND SUBSEQUENT LINES 5672924 FND:ID TOKEN SHOULD BE USED INSTEAD OF VALUE TOKEN. 5673692 FND:INCONSISTENT TIMEOUT ERROR ON FRAMEWORK PORTLET 5677222 FND:MESSAGE TOKEN SUBSTITUTION NEEDS TO BE IMPROVED 5680579 JTT:POTENTIAL CROSS-SITE SCRIPTING VUNERABILITY IN JTFTMPLH.JSP PAGE 5710743 FND:<RESPONSIBILITY NAME>,STANDARD IS NOT A VALID RESPONSIBILITY FOR THE 5711134 EC:TP_CODE_INTERNAL CODE CONVERSION DOES NOT HAPPEN FOR ADVO 5716857 FND:Correct truncation errors in fnd_audit_update_pkg
5730762 FND:USER WITH MULTIPLE ROLES GET UNAUTHORIZED FUNCTIONS AVAILABLE 5739375 JTA:11.5.10.2 JTA NEW USER NOTIFICATION EMAIL NOT RECIEVED 5741542 OWF:NOTIFICATION SUBJECT LOV DOES NOT MATCH THE FIELD WIDTH 5742181 OWF:STANDARD WORKFLOW ACTIVITY WAIT FOR CONCURRENT PROGRAM ACTIVITY DOES NOT WORK 5743320 FWK:11i.ATG_PF.H.RUP3 OA GLOBAL fixes V4 5744967 ALR:Comma is not recognized as valid starting character in an email address. 5759858 UMX:SORT ON STATUS COLUMN DOES NOT WORK 5767753 ALR:Added the colon to the email parser to recognize it as valid email character. 5767802 FND:RESPONSIBILITY GETTING UPLOADED BUT END DATE NOT REFLECTING IN THE RESPONSIBILITY 5842543 FND:ANY CODE COMBO FIELD, PRESSING F9 BRINGS UP SEG. LIST + FIRST SEGMENT LOV 5849329 OWF:WORKFLOW NOTIFICATION MAILER ALLOWS ADDING 1 CUSTOM TAG ONLY 5853433 FND:FNDSCAUS:ORA-01422 RESETTING A USER'S PASSWORD ORA-6512 FND_OAM_USER_INFO 5856570 FND:JAPANESE MESSAGE IS CUT OFF IN A POP UP WINDOW 5857297 FWK:11i.ATG_PF.H.RUP3 OACORE fixes V4.12 5873313 FRM:CPUApr2007 : 5873313 : 11.5.8 - 11i.ATG_PF.H RUP4 5879608 JTA:ATG11510RUP5D4FUNC:SOME ENROLMENT KEYS ARE DUPLICATE IN SEED DATA 5882694 FND:ORA-06502: PL/SQL: NUMERIC OR VALUE ERROR OCCURRED WHEN UPLOADING MENU LDT FILE 5883106 FWK:11i.ATG_PF.H.RUP3 OACORE fixes V4.8 5884253 OWF:NTFCOMMENTSVO?.XML VIEW OBJECT NEEDS TO ORDER BY SEQUENCE DESC ALSO 5886272 XDO:INDEX FILE IS NOT ENCODED WITH UTF-8 PROPERLY. 5886745 FND:PATCH 4676589 FILE FND/PATCH/115/SQL/AFICXSMB.PLS HAS HARDCODED APPLSYS 5890215 FRM:ON PUBLISHING PARAMETERS THE DEFAULT TEMPLATE IS POPULATED WITH STRANGE CHARS 5892957 OWF:11i.ATG_PF.H:RUP4::Enhanced logging in WF Status Monitor for java.lang.NullPoint 5893391 FND:CPUApr07 5893391 for 11.5.7 to 11i.ATG_PF.H RUP4 5893412 OWF:CPUAPR07: ORACLE E-BUSINESS SUITE ARBITRARY NODE DELETION VULNERABILITY 5896599 OAM:OAM ROLLUP PATCH FOR 11.5.10.6RUP 5902759 FWK:11i.ATG_PF.H.RUP3 OA GLOBAL fixes V4.1 5903106 OWF:CONCURRENT PROGRAM TO RETRY ALL ERRORED ACTIVITIES GIVEN AN ITEMTYPE 5905811 FND:Audit Trail cumulative fixes for February 2007. 5907520 FWK:Fix for cache invalidation issue in Inquiry pages 5913033 OWF:JAVA.LANG.NULLPOINTEREXCEPTION AFTER APPLYING ATG RUP 4 5914893 OAM:OD 2.5 RUP A 5915960 FND:UPDATED FND_TIMEZONES_B SEED DATA 5919689 FND:WHEN-NEW-ITEM-INSTANCE EVENT NOT TRIGGERED AGAINST THE E-MAIL FIELD IN USER FORM 5924067 FND:ATG11510RUP5D3FUNC:RUP4D3B:NON-ASCII ERROR MSG GARBLED CREATED BY FNDERROR.JSP 5924455 FND:ADD A VALIDATION METHOD FOR PROFILE OPTION ICX_SESSION_TIMEOUT 5926371 XDO:A LONG INNER TABLE CAN CAUSE OUT OF MEMORY ERROR 5927951 FND:APPS_SSO Profile Only Site level value used 5930091 OWF:PERFORMANCE ISSUE WITH WF DIR SVCS USER/ROLE VALIDATION 5931820 JTA:CRM ADMIN CANNOT ASSIGN AN ACCOUNT WHEN APPROVING USERS 5932115 OWF:WORKFLOW ADMINISTRATOR IS NOT SHOWING ALL NOTIFICATION IN A SEARCH 5936286 FWK:OAF Flexfield Version 4.06 5936694 OAM:APPLYDATABASE.JAVA DOES NOT ACCOUNT FOR 10G RAC LISTENER.ORA 5939442 OWF:JAVA.LANG.NULLPOINTEREXCEPTION AFTER APPLYING ATG RUP 4 5946713 EC:ECECDMO NOT POPULATING FIELDS(TOTAL_AMOUNT_DUE,AMOUNT_TAX_DUE) IN HEADE 5947217 OWF:WF JAVA DEFERRED AGENT LISTENER NOT STARTING 5948734 UMX:5022830 BACKPORT: SQL:REPOS:WF_EVENTS (GUID)-> FULL-TABLE SCAN
5948876 FND:11i Backport of 5307052:AFLOBBLD.SQL:PLS-00201: IDENTIFIER 'MY_COUNT' 5949825 FRM:REPOSITORY_MAINTENANCE ERRORS WITH ORA-01403: NO DATA FOUND DELETING TIMEFRAME 5953789 OAM:APPS SUPER USER ROLE MUST BE RE-DEFINED AFTER OD 2.5 RUP A INSTALLATION 5954008 FND:SUPPORT NEGATIVE CURRENCY PROFILE VALUE '(XXX)' 5954184 FND:5699245 BACKPORT: CANCEL STATUS IS SHOWN WARNING IN SELF SERVICE PAGES 5955122 FND:EXIT COMMENTED OUT IN FND_WEB_SEC (AFSCJAVB.PLS) 5956363 FWK:11i.ATG_PF.H.RUP3 OABC4J fixes V4.4 5958686 XDO:INDEX FILE IS NOT ENCODED WITH UTF-8 PROPERLY. 5960561 FND:JDBC CONNECTION LEAK IN SSOCOMMON.ISDEFAULTUSER 5964322 FND:5704428 BACKPORT: R12: UNABLE TO SUBMIT CONCURRENT PROGRAM FROM HTML CP UI 5968876 XDO:EBS-BURSTING INTEGRATION PATCH. 5971238 OWF:ctx_itemtype and ctx_itemkey is set when context was not set in current session. 5973343 OAM:ADDOS2UNIX.PL FAILS WITH COMMAND NOT FOUND ON LINUX MIGRATION 5973431 OWF:MAILER WITH NON-NULL CORRELATION ID DOES NOT PROCESS MESSAGES 5974895 OWF:SHARED WORKLIST USER NOT ABLE TO VIEW REQUISITION FROM APPROVE REQ NOTIFICATION 5977927 FND:FND_CURRENCIES:MISSING RSD (SERBIAN DINARS) CURRENCY_CODE 5980699 JTA:ADDRESS3 IS OVERWRITING ADDRESS4 FIELD DURING USER ACCOUNT CREATION 5981078 FND:MODIFY APPCORE TO TEST ORA_NLS10 SETTINGS FOR DATES. 5985964 FND:FND_LOGINS TABLE NOT CAPTURING LOGINS WHEN PASSWORD IS BEING RESET 5985992 TXK:TXK AUTOCONFIG ROLLUP PATCH Q (JUL/AUG 2007) 5988983 FND:ONDEMAND:GETTING ERROR ON COPY FROM ITEM IN INVIDITM 6001837 OWF:OAC: ACCESSIBILITY ISSUE ON WORKLISTPRTLETRG REGION 6004264 OAM:DIAGNOSTICS SCHEDULING : APPLICATION IS NOT REGISTERED 6004524 ALR:Added the colon to the email parser to recognize it as valid email character. 6005745 OWF:END DATED USERS ARE NOT BEING DISPLAYED IN MONITOR PARTICIPANT RESPONSES PAGE 6009589 FND:NLS_NUMERIC_CHARACTERS KEEP CHANGING DYNAMICALLY FROM SESSION TO SESSION 6011240 OWF:FND_WF_STANDARD.WAITFORCONCPROGRAM.L_MINUTE IS CALCULATED AS A SECOND 6014006 FND:GSISAN: AFFURGOL.SQL TOOK 00:23:49 (HH:MM:SS) 6022448 OWF:WF_DIRECTORY.GETROLEDISPLAYNAME RETURNS DISPLAY NAME OF ONLY ACTIVE USERS 6024480 FND:CREATE USER FAILS IF SIGNON PROFILE HAS NON-NUMERIC VALUE 6025162 OWF:WORKFLOW MAILER IS NOT CHANGING '<','>' SYMBOLS PROPERLY 6032295 FND:CRM NOT RECOGNIZING NON DEFAULT ACTIVE REQUEST LIMIT on startup after rup4 6032403 FND:Session Mgmt: End dating Guest Login when converting Guest Session. Gather Sessi 6036695 XDO:NOAVAILABLEAREAEXCEPTION ERROR OCCUR IF 3000+ LINES WITHIN A TAG IN XML FILE 6045931 FND:CPUJul2007 : 6045931 : 11.5.8 - 11i.ATG_PF.H RUP5 6050795 FND:PATCH 5578650 LEAVES COUNTRY 'CS' (SERBIA & MONTENEGRO) UNFLAGGED AS OBSOLETE 6051971 FND:11.5 FLEXFIELDS 11.5 PATCH K.2 (MAY/07) 6054413 JTA:UPDATE TEMPLATE PAGE MAXLENGTH FOR 'PAGE NAME' NEEDS TO BE INCREASED 6059507 XDO:NOAVAILABLEAREAEXCEPTION GOT WHEN GENERATING PDF REPORT 6060885 OWF:DATE PARAMETERS ARE REQUIRED FOR RESEND FAILED WORKFLOW NOTIFICATIONS 6067900 FND:ENHANCE PROFILES PROVIDED FOR CP PRINTER DRIVER ARGUMENT 6074641 OWF:JAVA ERROR PAGE ON SETTING VACATION RULES FOR A RESPONSIBILITY 6086949 FND:EXISTING VALUE SETS ARE NOT COMPILING 6112028 OWF:WFEVQCLN.SQL DOSEN'T CLEAN EVENT DATA FROM WF_JAVA_DEFERRED 6113725 FND:HARDCODED STRINGS IN APPCORE.PLD 6113770 OWF:WFAQBACK.SQL AND WFAQRENQ.SQL MODIFIED TO WORK WITH
SYS.AQ$_JMS_TEXT_MESSAGE 6114290 FND:PROFILE_OPTION_HIERARCHIES HAS ORGANISATIONS FOR US INSTEAD OF ORGANIZATIONS 6115106 FND:AFVLTPCY.SQL:FDMGORIGSYS ORA-28100 DUE TO HARDCODED APPS, APPLSYS SCHEMA 6118574 OWF:SWITCH RESPONSIBILITY PULLDOWN DISAPPEARS AFTER CLICKING SWITCH USER BUTTON 6131701 FND:NEED MODIFICATION OF APPCORE.PLD FOR FORM EXPORT ISSUE 6132312 FND:PRINTERS ARE NOT SORTED IN THE PRINTER LIST LOV FWK 6132333 OWF:NON-ASCII CHARACTERS IN OVERRIDE ADDRESS VERIFICATION EMAIL 6135295 FND:LOGGING INTO SSO - 'YOU HAVE INSUFFICIENT PRIVILEGES FOR THE CURRENT OPERATION' 6140696 XDO:FORWARDPORT REQUEST OF 5584501 - FILTER SUPPORT 6141149 FND:FORMS: HELP->ABOUT ORACLE APPLICATIONS NEEDS TO SHOW LIBRARY VERSIONS 6157467 OWF:ADD LOGGING BEFORE AND AFTER WORKFLOW FUNCTION CALLOUTS 6159407 FND:HASH PROJECT 6162044 OWF:ENHANCE WFVER.SQL TO PULL CONTENTS ALL QUEUES BEING USED 6162428 OWF:WF_MAILER_PARAMETER.GETVALUEFORCORR (2 PARAMS) RETURNS INCORRECT VALUE 6167881 FND:SSO MESSAGES FOR RUP6 6168003 OWF:ADD LOGGING BEFORE AND AFTER WORKFLOW FUNCTION CALLOUTS 6193583 FND:AOLJ Diagnostics jsps
December 11, Added Oracle e-Commerce Gateway procedure update in Section 6. 2007 February 21, 2008 April 17, 2009 Updated pre-install step regarding AD minipack 11i.AD.I with a note regarding 11i.AD.I.2. Added Firefox 3.0 Certification information to Section 4, and updated the instructions for "How do I package a new LAF configuration for delivery to a customer?" in Section 6.
July 17, 2009 Added patch 6408117 to post-install step 2 in Section 5.. February 18, 2010 Updated the reference to AF_JRE_TOP in post-install step 9, Section 5.
April 6, 2010
Added information about integration with Oracle Access Manager in Sections 1, 2, 3, and 6. Added information about the requirement for patch 5194357 for NLS customers in post-install step 2 in section 5. Added information for Oracle Web Applications Desktop Integrator and link to document 1077728.1 in section 6.
June 24, 2010 Updated information about integration with Oracle Access Manager in Section 1. January 14, 2011 April 20, 2011
Oracle Corporation Copyright Notice Copyright 1994-2011, Oracle. All rights reserved. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Related Products Oracle E-Business Suite > Applications Technology > Lifecycle Management > Oracle Application Install
Back to top