This chapter covers the following topics:
This section discusses the tasks required to create and administer Oracle Applications users.
This section includes the following topics:
Enterprises using Oracle Human Resource Management Systems (HRMS) must create employees with this application. For enterprises not using HRMS as their human resources application, employees must be created using CRM Resource Manager.
Use this procedure to create an employee in Oracle Human Resource Management Systems.
None
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
HRMS Manager or CRM Resource Manager
In a test environment, the Survey Administrator responsibility can be assigned to any Oracle Applications user. In a production environment, however, this user must be an existing HRMS employee. This employee must also be designated as a CRM Resource. Steps to create employees in the enterprise database, import them as CRM resources, define Oracle Applications users, assign them responsibilities, and associate them with employees in the enterprise database are discussed in Creating and Administering Users.
The HRMS employee is typically created in Oracle Human Resource Management Systems (HRMS), if licensed by an enterprise. For enterprises that have not licensed HRMS, the ability to create employees is also a scaled-down function of Oracle CRM Resource Manager.
If HRMS is installed, Oracle Applications enforces the business rule of requiring the user to create a person and designate them as the person type "employee" within HRMS. If you attempt to create an employee using CRM Resource Manager while HRMS is installed, you will experience an error.
Creating an employee in HRMS is accomplished by a user that has been assigned the appropriate HRMS responsibility (in the United States, for example, the US HRMS Manager responsibility).
If HRMS is not installed and licensed by an enterprise, the employee must be created using the CRM Resource Manager responsibility.
After an employee is created, additional information (not required by HRMS) is required in order for CRM applications at the enterprise to appropriately reference this individual. If the employee is created using CRM Resource Manager, this information is part of the definition process.
If the employee is created using HRMS, employee information must subsequently be identified as a CRM resource. (By "resource," the concept of a person in the enterprise is inferred.) To do so, import the HRMS employee into CRM Resource Manager using the CRM Resource Manager responsibility. This process includes creation of a Resource Number and a corresponding Resource ID for this individual which is required by CRM applications.
Regardless of which method is used to create the employee (using HRMS or CRM Resource Manager), this document refers to this employee as an HRMS employee.
The other assumption that is a prerequisite for all Survey implementation steps is that this employee is identified as a CRM resource.
Steps
If using HRMS, from the Navigator, select People > Enter and Maintain and click Open.
The Find Person window appears.
If using CRM Resource Manager, from the Navigator, select Maintain Employee > Employee > Enter Person and click Open.
Click New.
In the People window, enter the following information for the new person.
Last (Name)
Gender
Type (select Employee)
Date of Birth (if using Payroll)
Social Security Number (if using US HRMS)
Employee (Number) - If the Employee field is inactive, then Oracle HRMS is set up to automatically generate the employee number when the record is saved.
Other fields may be required depending on how your enterprise has set up Oracle HRMS or CRM Resource Manager. In addition, when you save the record, you may receive one or more messages that explain the consequences of leaving certain fields blank.
From the File menu, click Save.
In the status line, confirmation appears that a record has been applied and saved.
Use this procedure to set up resource groups in CRM Resource Manager. Resource groups allow the assignment of role types, roles, and usages to one group that may contain one or many members.
An employee in a group with the role of manager automatically becomes the manager of the other employees in that group and of the employees in the groups below in the hierarchy.
Note: You must not assign more than one employee with the role of Manager per group. Doing so will impact reporting accuracy.
Use this procedure to create a resource group.
None
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
CRM Resource Manager
Steps
From the Navigator, select Maintain Resources > Groups and click Open.
The Define Groups page appears.
In the Group Name field, type a name for your resource group.
Click the Roles tab.
From the list in the Role Type field, select the appropriate role type.
For example, select TeleSales if this is a resource group for Oracle TeleSales agents.
From the list in the Role field, select the appropriate role for the selected role type.
For example, select TeleSales Agent for use with Oracle TeleSales.
Click the Usages tab.
From the list in the Usage field, select the appropriate usages for the group.
For example, select Sales and TeleSales if this is a resource group for Oracle TeleSales agents.
Click the Save icon.
Use the following procedure to import a CRM resource.
None
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
CRM Resource Manager
Steps
From the Navigator, select Maintain Resources > Import Resources and click Open.
The Selection Criteria window appears.
In the Resource Category field, select Employee.
Enter any additional selection criteria.
For example, in the Name field, select the name of an employee.
Click Search.
Employees that meet the search criteria are listed in the Search Results area.
Refine your search if necessary. Select the appropriate employee and click OK.
The Selection Criteria window refreshes with the criteria you confirmed.
When satisfied with your selection criteria, click Search.
The Selection Criteria window refreshes. Employees that meet the specified search criteria are listed in the Search Results area. The Select checkbox for the matching employees are automatically selected.
Clear the Select checkbox for each employee for whom you do not want to create a CRM resource.
Click Create Resource.
The Default Values window appears.
Note: Do not make any changes or add roles from this window. You can add or modify this information in the resource details later.
Click Ok to accept the defaults.
The Selected Resources window appears. The Comments field indicates whether the resource is a new record, a duplicate record, or a duplicate record with a new role definition. The Select checkbox is automatically selected.
Clear the Select checkbox for each employee for whom you do not want to save as a resource.
To save the resources, click Save Resource.
A transaction number appears in the Transaction Number field. The transaction number is associated with each resource created during this transaction. More than one resource can have the same transaction number.
Click Details.
The Resource window appears. Verify the name of the resource (Name), the name of the employee (Source Name), and the user name (User Name) and note the resource number (Number).
From the Resource window, click the Roles tab (if it is not already displayed).
In the Role Type field, select the appropriate roles for this imported resource.
For example, if you want this user to access the Administration tab in Oracle Marketing, select Sales from the list of values. If you want this user to access Oracle TeleSales, select Telesales from the list of values.
In the Role field, select the appropriate role for each role type.
For example, if you want this user to access the Administration tab in Oracle Marketing, select Sales Manager from the list of values. If you want this user to access Oracle TeleSales, select Telesales Agent from the list of values.
Click the Save icon.
From the Resource window, click the Groups tab.
In the Name field under Groups, select the group name you created in the topic Creating a Resource Group.
In the Group Member Roles area, click in the Name field.
This field auto-populates with the appropriate role.
Click the Save icon.
Use the following procedure to define Oracle Applications user accounts (user name and password), assign responsibilities to users, and associate an Oracle Applications user with an employee in the enterprise database.
None
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
System Administrator
Steps
From the Navigator, select Security > User > Define and click Open.
The Users window appears.
In the User Name field, type the user name you want to define and press the tab key.
User names should be between 6 and 64 characters in length and should not contain spaces. Avoid using special characters such as %, slash, or backslash. Hyphen and underscore characters are supported.
Optionally, in the Description field, type a description of this user.
In the Password field, type the password for this user and press the tab key.
The first time the user logs in, this password must be changed.
Passwords should be between 5 and 64 characters in length and should not contain spaces. Avoid using special characters such as %, slash, or backslash. Hyphen and underscore characters are supported.
In the Password field, retype the same password for confirmation, and press the tab key.
Optionally, in the Password Expiration area, select criteria for the expiration of this password.
In the Responsibilities tab, click in the first row of the Responsibility column.
Type the appropriate responsibility name and press the Tab key. Optionally, you can search for the appropriate responsibility name by selecting the ellipsis points (...).
You can enter the full responsibility name, or you can enter partial criteria followed by the percent wildcard. Oracle Applications will attempt to automatically validate and autofill based on the criteria you entered. If an exact match results, the remaining columns will be populated.
If an exact match cannot be determined, a Responsibilities window appears on top of the Users window. Your search criteria appears in the Find tab field, with all results that meet your criteria appearing in a list below.
If many choices appear in the list, you may scroll through the list to find the appropriate responsibility. You may also refine your search criteria in the Find field and click Find. Highlight the appropriate choice in the list, and click OK. The Find window closes, and the appropriate criteria for all columns populates in the current row.
Responsibility information appears for the selected responsibility. By default, the Effective Date (From field) is populated with the SYSDATE.
Change the date in the Effective Date From field to a prior date (yesterday's date, the beginning of the current month, or other appropriate choice).
While an effective date starting with the SYSDATE may be effective immediately in some environments, best practices dictate that you ensure that the effective date you designate will take effect immediately in all environments.
Optionally, enter a date beyond which the responsibility will no longer be effective in the To field. This date must be later than the SYSDATE.
Select File > Save and Proceed to save your work.
In a new row in the Responsibility table, repeat steps 8 through 11 for each responsibility that you want to assign to this user.
In the Person field, search for the name of the person (employee in the enterprise database) with whom you want to associate this user account.
Enter full or partial criteria, in syntax Last Name, Title, First Name.
You can use the % wildcard character.
If an exact match is found, the employee name will populate in this field. Otherwise, the Person Names window results.
If required, refine your search in the Person Names window and click OK.
Select File > Save and Proceed to save your work.
There are various methods to debug problems or view informational or error messages when using Oracle Scripting. Each method provides information for functionality or problems with different components.
Problems with Script Author graphical scripts are displayed in the Syntax tab of the Script Author Java applet. Clicking on any specific error displays an error message in the Debug pane, which appears immediately below the graphical Script Author canvas (the visual work area). This is accessed by a user with the Scripting Administration responsibility. No setup is required to view Script Author errors in the Debug pane.
When launching Script Author from the Scripting Administration console, status messages regarding the launching of the Java applet are visible in the Java console. If any errors in communication with the mid-tier occur, these are displayed in the Oracle JInitiator Java console. See Enabling the Oracle JInitiator Java Console. No other setup steps are required.
Client-side message logs for scripts executed using the Scripting Engine component of Oracle Scripting are controlled by the IES : Debug Mode profile. The default setting for this is Debug off, and this is generally the recommended setting. Set this profile to Debug on at the user level only when remediating problems. When debug mode is enabled, these messages are written to the Oracle JInitiator Java console. See Enabling the Oracle JInitiator Java Console and Current IES Profile Options.
Server-side message logs are controlled by FND profiles. FND system profile settings are detailed in Information, Error and Debug Logging Profile Options. These logs are accessed when the user selects the Diagnostics global button or link from an OAF application. The FND: Diagnostics profile must be set to Yes for the logged-in user to display this control. To view message logs, see Viewing Message Server Logs.
This section includes the following topics:
Oracle Scripting has migrated to the Applications Common Logging Infrastructure for those aspects of error and informational message logging supported by that technology stack. Those aspects include:
Status and error information about Scripting Engine mid-tier operations
The Scripting Engine HTML client
PL/SQL information passed between the database and the Scripting Engine
Scripts executed in the Scripting Engine Web interface
Transactions in the Scripting Administration console and the Survey Administration console
To record errors or informational messages, set the FND system profile options. These profile options, the seeded lookup values for each, the recommended level to set each, and a detailed description of each profile is included in Information, Error and Debug Logging Profile Options.
In brief, the following profile options are relevant:
FND: Diagnostics must be set to Yes for an administrator to view message logs. This enables the Diagnostics global link and icon, which appears at the top right side of the HTML user interface for Oracle HTML-based applications using the Oracle Applications Framework. Oracle recommends setting this at the user level to provide access to information in logs only to appropriate trusted individuals.
FND: Debug Log Enabled must be set to Yes in order to capture information.
FND: Debug Log Level determines the amount and type of information captured.
FND: Debug Log Module specifies the module for which messages are logged.
To view message logs, see Viewing Server Message Logs.
For implementations using guest user authentication for scripts executed in the Scripting Engine Web interface, you must explicitly enable message logging if you want to view logs generated for this user.
For example, perform this task if you want to view message logs for users of the Scripting Engine Web interface who execute scripts in a Web browser through targeted surveys and Web scripts that are not hosted in Oracle self-service Web applications.
As a prerequisite, set the profiles as detailed in Information, Error and Debug Logging Profile Options.
At the User level, for the guest user, establish system profile options accordingly. You must ensure that the guest user name and password are registered in the system profile option value for the Guest User Password profile.
For example, for a guest user named GUEST with a password of ORACLE, set the Guest User Password profile to GUEST/ORACLE.
Note: The applications-level guest user is seeded with Oracle Applications. For security purposes, you may want to establish a more secure password for this account.
To view message logs, see Viewing Server Message Logs.
Oracle JInitiator is a Java applet used for Oracle Applications. It serves many purposes, including ensuring that the correct version of Java is executed on the client destktop. This applet launches when an Oracle Applications session is started.
The Oracle JInitiator Java applet includes the ability to view status messages using a Java console. From an Oracle Scripting perspective, you may want to view the Oracle JInitiator Java console for this applet to determine the outcome of certain events or monitor status.
For example, if debug mode is enabled for client-side message logs, the logs are sent to this console.
Also, when launching Script Author, status messages regarding the launching of the Java applet are visible in the Java console. If any errors in communication with the mid-tier occur, these are displayed in the Oracle JInitiator Java console.
Use this procedure to enable the Oracle JInitiator Java console.
Oracle JInitiator must be installed on your client workstation.
None
None
Steps
From the Start menu, select Programs > JInitiator Control Panel.
The Oracle JInitiator Properties window appears.
In the Basic tab, select Show Java Console.
Click Apply.
Close the Oracle Jinitiator Properties window.
To access the Audience tab in the Survey Administration Console, the Oracle Applications user account must generally have a sales group ID or a sales role. Administration of resource groups is accomplished in Oracle CRM Resource Manager.
By setting a profile option, you can bypass this requirement for the Survey Administrator responsibility as described below. This profile can also be set at the application level.
Sales groups, roles and usages are administered in Oracle CRM Resource Manager. These are used by various applications, including Oracle Marketing and Oracle TeleSales.
You must define a sales group and assign the group roles and usages prior to assigning any members to the group. If a sales group already exists, you can add members to the group. Each group member must have a CRM resource ID, which is created upon importing an employee into CRM Resource Manager.
Some applications (such as Oracle Marketing) require steps to be performed in a particular order. The recommended order is as follows:
Creating an employee using Oracle HRMS (if installed) or CRM Resource Manager (if HRMS is not installed).
Creating an Oracle Applications user account with the appropriate responsibilities.
Associating the Oracle Applications user account with the employee.
Creating a resource group and assigning roles and usages to the group.
Importing a CRM resource and assigning roles and usages to the resource.
Adding a defined resource as a member of an existing group.
None
System Administrator
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
Steps
From the Navigator, select Profile > System and click Open.
The Find System Profile Values window appears above the unpopulated System Profile Values window. In the Display area, the Site and Profile with No Values options are selected.
In the Display area, select Responsibility.
The field changes color, and a set of ellipsis points appears.
In the Responsibility field, type the appropriate responsibility for which you want to bypass the requirement of group membership, and press the tab key.
For example, type Survey Administrator and press the tab key.
Leave the Profiles with No Values option selected.
This allows the query to return profiles that meet your search criteria but have no values associated with them yet (blank profiles).
In the Profile field, enter Bypass Group Validation.
Click Find.
The System Profile Values window appears.
In the Bypass Group Validation row, click once in the Responsibility column.
A set of ellipsis points appears.
Click the ellipsis points.
The Bypass Group Validation window appears.
From the list of values, select Yes and click OK.
Save your work and exit.
To perform certain JTF tasks, a user must be assigned a specific JTF role. For example, the JTF_SYSTEM_ADMIN_ROLE role provides certain administrative capabilities to a user. From an Oracle Scripting perspective, survey administrators using targeted deployments must be assigned the JTF_FM_ADMIN role to access the Invitations tab from the Survey Administration console.
Additionally, from an implementation perspective, your Oracle Applications user account must already have certain roles in order to grant those roles to other users.
Use the procedure below to grant JTF roles to Oracle Applications accounts (users).
To perform some Oracle HTML-based applications administration, including this task, your Oracle Applications user must be granted the JTF_SYSTEM_ADMIN_ROLE. If required, you can use the seeded SYSADMIN Oracle Applications user account.
Your Oracle Applications user must be granted a JTF role before you can assign that JTF role to another user. Thus, this user must be granted the JTF_FM_ADMIN role. This role is available to the seeded SYSADMIN Oracle Applications user account.
Log into Oracle applications using the CRM Home Page login, or the Single Sign-On login if implemented.
CRM HTML Administration
Steps
From the CRM Applications Administration console, click the Users tab.
Click the Registration subtab.
The Introduction page appears.
From the side panel, click User Maintenance.
The Users page appears.
In the search criteria field, enter the appropriate search criteria to find the appropriate user name, and click Go.
Note: You must enter at least three characters. In addition to those three characters, you can use the % wildcard search character in your criteria.
The Users page refreshes, displaying a summary list table containing the set of records matching your criteria.
If necessary, refine your search criteria and click Go.
From the resulting list of users, click the appropriate entry in the Username column.
The User Details page appears.
In the User Details area, click Roles.
The User-Role Mapping page appears. Two lists are displayed (Available Roles and Assigned Roles).
From the Available Roles list, select each role you want to assign.
You can select multiple records from the list by pressing and holding the CTRL key (use the Option key for Macintosh computers) as you make each selection.
When all desired available roles are selected, click > Move to move it to the Assigned Roles list.
For example, select JTF_SYSTEM_ADMIN_ROLE and JTF_FM_ADMIN and move them to the Assigned Roles list.
When satisfied, click Update.
The User-Role Mapping page refreshes. Two lists are displayed (Available Roles and Assigned Roles). The roles you just assigned for this user should appear in the Assigned Roles list.
None
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
System Administrator
Steps
From the Navigator, select Profile > System and click Open.
The System Profile Values window appears. Above this, the Find System Profile Values window appears and has focus.
If you want to display and set profile options by site, in the Display area of the Find System Profile Values window, ensure Site is selected. If you do not wish to view or set profiles at the site level, clear the Site option.
You can display and set profile options by Application, Responsibility, or User. For each selection:
Mark the appropriate option.
In the text field next to the selected Application, Responsibility, or User option, type search criteria and click tab.
If you typed full or partial search criteria with one match, the appropriate value populates the field. Otherwise, a window appears where you can narrow your search criteria.
Refine your search if required, select the appropriate option, and click OK.
Note: Site is the highest and broadest level of Oracle Applications profile settings, and affects all Oracle Applications users unless a specific lower level is specified. By changing the search criteria from Site to any of the other values (Application, Responsibility, or User), you can query and set profiles for lower and more granular levels. A lower level profile setting, if populated, always takes precedence and supersedes any value set at a higher level.
Ensure the Profiles with No Values option is selected.
This allows the query to return profiles that meet your search criteria but have no values currently associated with them (blank profiles).
In the Profile field, enter your search criteria. You may include the % wildcard character.
For example, enter IES%. IES is the product code for Oracle Scripting. Profile values associated with the survey component are included in this category.
Click Find.
The System Profile Values window populates, displaying all profile values for the requested search criteria at the requested levels.
Set each profile option as required by your implementation task. You can set these options in any sequence.
Select File > Save and Proceed to save your work.
The status line will indicate that records has been saved.
If you do not need to set additional profile options at this time, then proceed to step 13.
If you want to set additional profile options with different search criteria, then from the View menu, select Find.
The Find System Profile Values window appears.
Repeat steps 2 through 8 above.
When satisfied, select File > Save and Proceed to save your work.
The status line will indicate that records have been saved.
Select File > Close Form to close this window.
Continue your work or log out of Oracle Applications by selecting File > Exit Oracle Applications.
You must know the APPLICATION_ID value for your application and the RESPONSIBILITY_ID value for a specified responsibility before you can set the required Oracle CRM Technology Foundation (JTT) profile options appropriately.
Based on how Oracle Applications was installed in your environment, a responsibility may have different names. For example, in a Vision Database installation, the responsibility to access the Scripting Engine agent interface in standalone mode is Scripting Agent, Vision Enterprises. In a fresh installation, this responsibility is referred to as Scripting User. Nevertheless, both will have a single responsibility identification.
Note: The APPLICATION_ID value for Oracle Scripting is typically 519. The RESPONSIBILITY_ID value for Survey Administrator is typically 21685. The RESPONSIBILITY_ID for Scripting Administrator is typically 23723. However, in some scenarios, the responsibility identification may differ, based on environmental factors.
Use the following procedure to find the APPLICATION_ID value and RESPONSIBILITY_ID value of a known responsibility.
None
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
System Administrator
Steps
From the Navigator, select Security > Responsibility > Define and click Open.
The Responsibilities form appears.
Choose View > Find.
The Responsibilities search window appears.
Search for the appropriate responsibility, highlight it, and click OK in the search window.
The Responsibilities form is populated with the record for the selected responsibility.
With your cursor in any field of the record, select Help > Diagnostics > Examine.
If the Enable Diagnostics window appears, enter the apps level database password and click OK.
The Examine Field and Variable Values window appears.
If you want to determine the Application ID, in the Examine Field and Variable Values window, from the Field list, select APPLICATION_ID and click OK.
The Value field in the Examine Field and Variable Values window is populated with the value of APPLICATION_ID.
If you want to determine the Responsibility ID, in the Examine Field and Variable Values window, from the Field list, select RESPONSIBILITY_ID and click OK.
The Value field in the Examine Field and Variable Values window is populated with the value of RESPONSIBILITY_ID.
If you want to determine the Responsibility Key, check the value of the selected responsibility in the Responsibility Key field.
If a default application is already established for JTT applications, and you see only an application ID number in the JTF_PROFILE_DEFAULT_APPLICATION system profile, you must know which application is assigned, to determine whether to override this value with 519 (for Oracle Scripting).
Use the following procedure to determine (from a known application ID) the name of the application.
You must have the application ID value from the JTF_PROFILE_DEFAULT_APPLICATION system profile.
Log into SQL*Plus or another SQL application as a user with read privileges to the apps schema
None
Steps
Launch SQL*Plus or another SQL application.
Log into the appropriate applications instance.
Perform the following query to determine (from a known application ID) the current default HTML JTF application for this environment.
SELECT A.APPLICATION_ID, B.APPLICATION_NAME FROM FND_APPLICATION A, FND_APPLICATION_TL B WHERE A.APPLICATION_ID = B.APPLICATION_ID AND A.APPLICATION_ID = <KNOWN_APPLICATION_ID>;
Note: Replace <KNOWN_APPLICATION_ID> with the value of the application ID in your SQL statement.
When viewing log messages for Oracle Applications using the OA Framework, a User ID automatically populates in the User ID field, with the value applicable to the current Oracle Applications user account. This value is from the USER_ID column of the FND_USER table in the Oracle Applications schema.
If you want to view log messages for a specific user other than your current user, you must first obtain this user ID.
This section includes the following topics:
Use this procedure to determine the FND_USER_ID value for a defined user from a SQL application such as SQL*Plus.
You must know the Oracle Applications user account.
You must have apps level access to the Oracle Applications database schema using a SQL application such as SQL*Plus.
Log into SQL*Plus or another SQL application as a user with read privileges to the apps schema
None
Steps
Launch SQL*Plus or another SQL application.
Log into the appropriate applications instance.
Perform the following query to determine (with a known Oracle Applications user name, in upper case) the FND USER_ID value for this user.
SELECT USER_ID, USER_NAME FROM FND_USER WHERE USER_NAME = <NAME>;
Note: Replace <NAME> in your SQL statement with the value of the Oracle Applications user name for the appropriate user.
Use this procedure to determine the FND_USER_ID value for a defined Oracle Applications user account from the system administrator Users window.
None
Log into Oracle applications using the Personal Home Page login, or the Single Sign-On login if implemented.
System Administrator
Steps
From the Navigator, select Security > User > Define and click Open.
The Users window appears.
Place your cursor in the User Name field.
Enter query mode by selecting View > Query By Example > Enter or by selecting F11 on your function keys.
For example, to search for the seeded applications guest user, type GUEST.
In the User Name field, type the name of the Oracle Applications user account for which you wish to obtain the FND User ID.
Execute the query by selecting View > Query By Example > Run or by selecting CTRL-F11 on your keyboard.
If the query is successful, the Users window refreshes. If the query is unsuccessful, in the User Name field, type other criteria, and run the query again.
With your cursor in the User Name field, select Help > Diagnostics > Examine.
If the Enable Diagnostics window appears, enter the apps level database password and click OK.
The Examine Field and Variable Values window appears.
To determine the FND user ID value for this user, then in the Examine Field and Variable Values window, from the Field list, select USER_ID and click OK.
The Value field in the Examine Field and Variable Values window is populated with the value of the FND user ID for this user.
When upgrading Oracle Applications, the obsolete Quick Find menu remains associated with product code IES, causing this menu to appear in the Scripting Administration console, where it has no function. This menu will not appear in the Scripting administrative interface for new implementations. For upgrade implementations, you must modify the JTT properties for product IES (Oracle Scripting) to remove the association between this menu and the Scripting product.
Use the procedure below to remove the Quick Find menu from its association with Oracle Scripting (product code IES).
You must log in as a user with JTF_SYSTEM_ADMIN_ROLE. For example, you can use the seeded SYSADMIN Oracle Applications user account.
Log into Oracle applications using the CRM Home Page login, or the Single Sign-On login if implemented.
CRM HTML Administration
Steps
From the CRM Applications Administration console, click the Settings tab.
Click the System subtab.
The Introduction page appears.
From the side panel, select Properties > Advanced.
The Advanced - Properties page appears.
Note: If this page does not appear, your login does not have the JTF_SYSTEM_ADMIN_ROLE role. Log out and log in with an appropriate user.
From the View menu, select IES.
The Advanced - Properties page refreshes. The records displayed show advanced properties for product code IES (Oracle Scripting).
The following keys for IES advanced properties must be modified:
search.factories
service.oracle.apps.ies.survey.search.server.IESSurveySearchFactory.categories
service.oracle.apps.ies.survey.search.server.IESSurveySearchFactory.desc
For each of the keys listed above, append a period and the responsibility ID for the Survey Administrator responsibility, as indicated below:
Note: The responsibility ID for the Survey Administrator is typically 21685, but this may differ in your environment. To determine the appropriate ID for your environment, see Finding Application and Responsibility ID Values.
In the Advanced - Properties table, from the Key column, click on the appropriate property.
The Key Details page appears.
In the Key field, append a period and the responsibility ID.
For example, for the search.factories key, modify the entry to read:
search.factories.21685
Click Update.
The Advanced - Properties page refreshes. The modified key is displayed.
Repeat steps 5.1 through 5.3 for the remaining keys to be modified.
In the Key field, append a period and the responsibility ID.
If the changes do not immediately result in the removal of the Quick Find menu in the Scripting Administration console, stop and restart the Apache Web server to see the changes take effect.
Continue your work or log out of Oracle Applications by selecting Sign Out.