2Maintain Common Reference Objects
This chapter contains the following:
-
How can I determine which languages appear in the Translation Editor?
-
How do I define whether the user image, name, or initials display in the global header?
Overview of Common Reference Objects
The Maintain Common Reference Objects tasks support implementation of common functionality, such as data security, reference data sets, or general preferences.
Use these tasks to manage common reference objects that are defined centrally and shared across applications. You can search for and access the tasks in the Setup and Maintenance work area.
To make the Maintain Common Reference Objects tasks available in your implementation project, go to the Offerings work area and enable the Maintain Common Reference Objects feature.
Set General Preferences for All Users
Use the Global Admin Preferences page to set general preferences, such as language, currency, and time zone for all users. Use this task only if you want to update preferences for all users. Your users can still set preferences for themselves using the General Preferences page. Once you set the general preferences for all users, if specific users don't change their preferences, then the preferences that you have set for all users will apply to them.
To set general preferences:
-
In the Setup and Maintenance work area, go to the Set User General Preferences task.
-
Set the required general preferences for your users.
-
If you only want to set the preferences for new users whose preferences haven't been set by them yet, select the Reset preferences for new users only check box. Selecting this option excludes all users whose preferences were set at some point in time.
-
Click Save.
Why can't I edit setup data?
The configuration of your setup data may be protected. Application developers mark some configurations as protected, indicating that you can't edit them.
Some examples of configurations that may be protected are:
-
Descriptive flexfields
-
Extensible flexfield contexts
-
Extensible flexfield pages
-
Value sets
-
Tree structures
How can I determine which languages appear in the Translation Editor?
Use the Translation Editor Languages profile option to specify the languages as the profile values, so that they are available as options for the user on the Translated Editor dialog box.
-
In the Setup and Maintenance work area, go to the Manage Administrator Profile Values task.
-
Search for the Translation Editor Languages profile option.
-
In the Profile Values section, specify the required languages as its profile values, separated by comma. You can either list the complete names of the languages or just the language codes specified on the Manage Languages page, for example, F for French, KO for Korean.
Note: You can specify only those languages that are available in the supported language pack. If you don't specify any value, all available language packs are supported. -
Click Save and Close. The language entries will take effect for the user in the next sign in.
How do I define whether the user image, name, or initials display in the global header?
Set the User Image Display Enabled (FND_USER_PHOTO_ENABLED) profile option. If you select:
-
Yes, then the user image is displayed in the global header only if the user uploaded a photo. Otherwise, the user's initials are displayed. By default, this profile option is set to Yes.
-
No, then only the user name is displayed in the global header.
Define Application Taxonomy
Overview of Application Taxonomy
Oracle application components and functions are organized in a hierarchy, ranging from product lines to logical business areas. The hierarchy represents a breakdown of products into units based on how applications are installed and supported.
In the Application Extensions functional area within your offering, search for the Manage Taxonomy Hierarchy task and view the hierarchy on the Manage Taxonomy Hierarchy page.
A detailed introduction to application taxonomy is provided in the Oracle Fusion Applications Developer's Guide.
Hierarchy
-
The application taxonomy hierarchy contains various levels and types of nodes, or modules.
Usage
-
Use application taxonomy to understand relationships among applications and between an application and its files. This information is helpful in managing various phases of the product life cycle.
Modules in Application Taxonomy
The highest level of the hierarchy is product line, followed by the product family, application, and logical business area. There can be multiple levels of logical business areas, with one or more nested within a parent logical business area. A module is a node at any of these levels. Each level is briefly described here.
-
Product Line: A collection of products associated with a single brand name, for example, Oracle Fusion.
-
Product Family: A collection of products associated with a functional area that may or may not be licensed together as a single unit, for example Oracle Fusion Financials.
-
Application: A single product within a product family, containing closely related features for a specific business solution, for example General Ledger.
-
Logical Business Area: A collection of business object definitions organized into a logical grouping. It contains the model objects, services, and UI components for those business objects. Logical business areas have their own hierarchy levels and in some cases can be up to two or three levels deep.
Guidelines for Managing Modules in Application Taxonomy
In the application taxonomy hierarchy, when you create a module, it becomes a child of the currently selected node. Once created, you can't delete the module or move it elsewhere in the hierarchy.
From the Manage Taxonomy Hierarchy page, navigate to the Create Child Module or Edit Module page to manage the modules. As you create or edit modules, consider the following points regarding specific fields.
Identifiers
Module ID is the unique primary key for nodes in the taxonomy table. When you create a module, a unique read-only ID is automatically generated. The module contains two other identifiers: Module key and alternative ID. The module key is a string identifier, for example AP for the Oracle Fusion Payables application. The alternative ID is a numeric identifier, for example 1 for the Oracle Fusion product line. These additional identifiers are provided for the product line, product family, and application modules. However, you can optionally add them for logical business areas and new modules.
The product code is relevant only to application and logical business area modules. You can leave the field blank for other module types. The product code for applications is the short name that can be displayed in lists of application values. For example, FND for Oracle Fusion Middleware Extensions for Oracle Application.
Names
Module name is the logical name for the module. The name must be unique among nodes within the hierarchy level with the same parent, but Oracle recommends keeping it unique in the entire hierarchy. The user name and description can appear to users in other parts of Oracle Applications Cloud.
Usage Types
Though you can update the usage type to reflect the current state of the module, just doing so doesn't affect the actual state. For example, setting a module as installed doesn't mean the module is actually installed if the installation itself didn't take place. Installation refers to operations related to laying down all the components required to create an Oracle Applications Cloud environment. Deployment is the process that starts the managed servers and clusters and facilitates the actual use of product offerings. A licensed module is available for installation and deployment, and a deployed module is considered actively used when actually used by users.
Seed Data
If seed data is allowed, then data residing in flexfields and lookups can be extracted for the module using seed data loaders. By default, extract is allowed for all predefined modules of type application and logical business area.
Associations
You can associate a logical domain to modules of the type Product Family, as well as one or more enterprise applications to modules of type Application. This association represents the relationship between the taxonomy modules and the corresponding domain and enterprise applications stored in the Oracle Applications Cloud Functional Core (ASK) tables.
Define ISO Reference Data
Considerations for Natural Languages
Natural languages are all the languages that humans use, written and spoken. If a language is enabled, then users can associate it with entities, for example as languages spoken by sales representatives. When managing natural languages, consider tasks to perform and best practices for entering particular values.
Tasks
Once you add a language, it can't be deleted, but just disabled. You can optionally associate natural languages with International Organization for Standardization (ISO) languages and territories, just for reference.
Values
When you create a natural language, use the alpha-2 ISO code as the language code, or, if not available, then alpha-3. If the language is not an ISO language, then use x- as a prefix for the code, for example x-ja for a Japanese dialect. Use the sgn code of ISO-639-2 for sign languages, followed by territory code, for example sgn-US for American Sign Language. You can also use Internet Assigned Numbers Authority (IANA) language tags.
The natural language description must be the language name with territory name in parenthesis where needed, for example English (Australia) and English (Canada).
FAQs for Define ISO Reference Data
When do I create or edit territories?
The predefined territories are countries from the International Organization for Standardization (ISO) 3166 standard. Edit territory descriptions to determine how they are displayed in lists of country values in an application. You don't have to edit territory names or codes unless there is a specific requirement. Create territories if new countries emerge and the application isn't yet patched with the latest ISO country values.
When do I create or edit industries?
To meet a specific business need, you may edit industry names or descriptions of industries except for those belonging to the North American Industry Classification System (NAICS). Edit the industry descriptions also to determine how they appear in an application.
You may also create industries with specifications not included in the NAICS standards.
When do I associate industries with territories?
To meet specific business needs, you can associate industries with territories. For example, administrators can configure a page in different ways for different sets of users of the same industry, but residing in different countries.
When do I create or enable currencies?
Create or enable any currency for displaying monetary amounts, assigning currency to ledgers, entering transactions, recording balances, or for any reporting purpose. All currencies listed in the International Organization for Standardization (ISO) 4217 standard are supported.
The default currency is set to United States Dollar (USD).
What's the difference between precision, extended precision, and minimum accountable unit for a currency?
Precision refers to the number of digits placed after the decimal point used in regular currency transactions. For example, USD would have 2 as the precision value for transactional amounts, such as $1.00.
Extended precision is the number of digits placed after the decimal point and must be greater than or equal to the precision value. For calculations requiring greater precision, you can enter an extended precision value such as 3 or 4. That would result in the currency appearing as $1.279 or $1.2793.
Minimum accountable unit is the smallest denomination for the currency. For example, for USD that would be .01 for a cent.
You can set these values for a currency using the Manage Currencies task in the Application Extensions functional area in the Setup and Maintenance work area.
What's a statistical unit currency type?
The statistical unit currency type denotes the Statistical (STAT) currency used to record financial statistics in the financial reports, allocation formulas, and other calculations.
When do I create or edit ISO languages?
Edit the names and descriptions of International Organization for Standardization (ISO) languages to determine how they appear in the application. The ISO languages are a part of the ISO 639 standard. If any change to the ISO standard doesn't reflect in the application, you can update the ISO alpha-2 code or add languages to provide up-to-date information.
When do I edit languages?
Installed languages automatically appear on the Manage Languages page. This page also displays all languages that are available for installation and translation. Each dialect is treated as a separate language.
Generally, you don't need to edit any of the detailed fields unless absolutely necessary.
Can I add or edit time zones?
You usually don't add or edit time zones because all standard time zones are provided. However, you may create time zones if new zones become standard and the application isn't yet updated with the latest values. You can rename existing time zones and enable them. Only the enabled time zones are available for all users to select while setting their regional general preferences.
To add or edit time zones, use the following in the Setup Maintenance work area:
-
Functional Area: Application Extensions
-
Task: Manage Time Zones
Manage Audit Policies
Audit Policies
Auditing is used to monitor user activity and all configuration, security, and data changes that have been made to an application. Auditing involves recording and retrieving information pertaining to the creation, modification, and removal of business objects. All actions performed on the business objects and the modified values are also recorded. The audit information is stored without any intervention of the user or any explicit user action.
Use audit policies to select specific business objects and attributes to be audited. The decision to create policies usually depends on the type of information to be audited and to the level of detail required for reporting.
Enabling Audit Functionality
For Oracle Applications Cloud, you must configure the business objects and select the attributes before enabling audit. If you enable audit without configuring the business objects, auditing remains inactive. By default, auditing is disabled for all applications. To enable and manage audit, ensure that you have a role with the assigned privilege Manage Audit Policies (FND_MANAGE_AUDIT_POLICIES_PRIV). For appropriate assignment of roles and privileges, check with your security administrator.
To enable auditing for Oracle Fusion Middleware products, select one of the levels at which auditing is required for that product. The audit levels are predefined and contain the metadata and events to be audited. For more information, see Audit Events for Oracle Applications Cloud Middleware (Doc ID 2114143.1) on My Oracle Support at https://support.oracle.com.
If you don't want an application to be audited, you can stop the audit process by setting the Audit Level option to None.
Audit Configuration for Business Object Attributes
Audit enables tracking the change history of particular attributes of a business object. However, those objects and their attributes must be selected for audit and auditing must be enabled for that application. Your configuration settings determine which attributes to audit for a given object, and when the audit starts and ends. Auditing takes into account all the operations performed on an object and its attributes, such as create, update, and delete. To configure audit business object attributes, use the Manage Audit Policies task in the Setup and Maintenance work area.
Selecting an Application
To set up auditing, you must select a web application that contains the required business objects that can be audited. From the list of business objects, select those business objects that you want to audit. Selecting a business object also displays its attributes that are enabled for auditing.
Selecting Attributes
For each selected business object to be audited, select the corresponding attributes to include in the audit. All attributes that belong to that object are by default selected for audit and appear on the user interface. However, you can add or remove attributes from the list. When you remove an attribute from the list, you stop auditing it even when the parent object is selected for audit. So, if you want an attribute to be audited, you must add it to the list. If the object selected in an audit hierarchy is also a part of several other audit hierarchies, the attribute configuration for that object is applicable to all the hierarchies in that application.
Starting and Stopping Audit
The business object is ready for audit after you select its attributes and save the configuration changes. However, to start auditing, the audit level for Oracle Applications Cloud must be set to Auditing on the Manage Audit Policies page.
To stop auditing an object, you can deselect the entire object and save the configuration. As a result, all its selected attributes are automatically deselected and aren't audited. To continue to audit the business object with select attributes, deselect those attributes that aren't to be audited. When users view the audit history for an application, they can specify the period for which they want the results. Therefore, make a note of when you start and stop auditing an application.
For example, users intend to view the audit history of an object for the previous week, but auditing for that object was stopped last month. They wouldn't get any audit results for that week, because during the entire month that object wasn't audited. Even if you enable audit for that object today, users can't get the wanted results because audit data until today isn't available.
Overview of Audit Configuration
To set up auditing for Oracle Applications Cloud, select the Manage Audit Policies task from the Setup and Maintenance work area within your offering. To set up auditing for Oracle Fusion Middleware products, select the level of auditing mapped to a predefined set of metadata and the events that have to be audited. Information about configuring audit for Oracle Fusion Middleware products is provided in Oracle Fusion Middleware guides.
You can also create a configuration file and deploy it to audit a specific Oracle Fusion Middleware product. The configuration details for Oracle Fusion Middleware products are available as audit-specific assets that you can use to create the config.xml configuration file. To get a list of audit-specific assets, see Audit Events for Oracle Applications Cloud Middleware (Doc ID 2114143.1) on My Oracle Support at https://support.oracle.com.
Oracle Fusion Middleware Products
-
Configure business objects to enable auditing in Oracle Fusion Middleware products. Refer to the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.
Oracle Fusion Security Products
-
Configure business objects to enable auditing in Oracle Fusion security products. Refer to Oracle Fusion Middleware Application Security Guide.
Use Auditing to Monitor Financials Application Changes
You use auditing to monitor user activity and all configuration, security, and data changes that have been made to an application. You can enable business objects to allow auditing, recording, and retrieving information about when the objects were created, modified, and removed.
Here's a list of business objects that you can enable for auditing:
| Area | Parent Objects | Child Objects |
|---|---|---|
|
Advanced Collections |
Aging Buckets |
|
|
Advanced Collections |
Backup Collectors |
|
|
Advanced Collections |
Collection Preferences |
|
|
Advanced Collections |
Collections Scoring and Strategy Assignments |
|
|
Advanced Collections |
Collections Scoring Formula |
|
|
Advanced Collections |
Collections Strategies |
|
|
Advanced Collections |
Collectors |
|
|
Advanced Collections |
Dunning Configurations |
|
|
Assets |
Fixed Asset Bonus Rule |
|
|
Assets |
Fixed Asset Book |
|
|
Assets |
Fixed Asset Calendar |
|
|
Assets |
Fixed Asset Cash Generating Unit |
|
|
Assets |
Fixed Asset Category |
|
|
Assets |
Fixed Asset Category Alias |
|
|
Assets |
Fixed Asset Ceiling |
|
|
Assets |
Fixed Asset Depreciation Method |
|
|
Assets |
Fixed Asset Distribution Set |
|
|
Assets |
Fixed Asset Fiscal Year |
|
|
Assets |
Fixed Asset Key |
|
|
Assets |
Fixed Asset Key Alias |
|
|
Assets |
Fixed Asset Location |
|
|
Assets |
Fixed Asset Location Alias |
|
|
Assets |
Fixed Asset Price Index |
|
|
Assets |
Fixed Asset Prorate Convention |
|
|
Assets |
System Controls |
|
|
Bill Management |
Bill Management System Options |
|
|
Budgetary Control |
Budgetary Control and Encumbrance Accounting |
|
|
Budgetary Control |
Control Budget |
|
|
Cash Management |
Ad Hoc Payee Information |
|
|
Cash Management |
Bank Account |
|
|
Cash Management |
Bank Statement Parsing Rule Set |
|
|
Cash Management |
Bank Statement Reconciliation Matching Rule Set |
|
|
Cash Management |
Bank Statement Transaction Creation Rule |
|
|
Cash Management |
Bank Transaction Codes |
|
|
Cash Management |
Cash Positioning and Forecasting Options |
|
|
Cash Management |
Cash Positioning and Forecasting Transaction Grouping |
|
|
Cash Management |
Cash Transaction Type Mapping |
|
|
Data Security |
Data Security Access for Users |
|
|
Expenses |
Manage Conversion Rates and Policies |
|
|
Expenses |
Manage Expense Report Templates |
|
|
Expenses |
Manage Expenses System Options |
|
|
Financials Common Module |
Additional Intercompany Balancing and Clearing Options |
|
|
Financials Common Module |
Business Unit |
|
|
Financials Common Module |
Intercompany Balancing Rules |
|
|
Financials for Americas |
Collection Remittance Batch Template |
|
|
Financials for Americas |
Local Holiday for Brazil |
|
|
Financials for Americas |
Receivables Bank Instruction for Brazil |
|
|
General Ledger |
Account Combinations |
|
|
General Ledger |
Accounting and Reporting Sequences |
|
|
General Ledger |
Accounting Automation Setup |
|
|
General Ledger |
Accounting Calendars |
|
|
General Ledger |
Allocations |
|
|
General Ledger |
AutoPost Criteria Sets |
|
|
General Ledger |
Chart of Accounts Mapping |
|
|
General Ledger |
Clearing Accounts Reconciliation Rules |
|
|
General Ledger |
Currency Conversion Rate Type and Rates |
|
|
General Ledger |
Data Access Set |
|
|
General Ledger |
Encumbrance Carry Forward Rules |
|
|
General Ledger |
Encumbrance Types |
|
|
General Ledger |
Journal Categories |
|
|
General Ledger |
Journal Reversal Criteria Sets |
|
|
General Ledger |
Journal Sources |
|
|
General Ledger |
Journals |
Note: You can only audit updates for journal batches, headers,
and lines.
|
|
General Ledger |
Ledger Set |
|
|
General Ledger |
Ledgers |
|
|
General Ledger |
Revaluations |
|
|
General Ledger |
Statistical Units of Measure |
|
|
General Ledger |
Suspense Accounts |
|
|
Intercompany |
Intercompany Customer Supplier Association |
|
|
Intercompany |
Intercompany Organization |
|
|
Intercompany |
Intercompany Receivables Assignment |
|
|
Intercompany |
Intercompany System Option |
|
|
Intercompany |
Intercompany Transaction Type |
|
|
Legal Entity Configurator |
Legal Association |
|
|
Legal Entity Configurator |
Legal Contact |
|
|
Legal Entity Configurator |
Legal Entity |
|
|
Legal Entity Configurator |
Legal Entity and Legal Reporting Unit Registration |
|
|
Legal Entity Configurator |
Legal Jurisdiction |
|
|
Legal Entity Configurator |
Legal Reporting Unit |
|
|
Payables |
Aging Periods |
|
|
Payables |
Bank Charges |
|
|
Payables |
Common Options for Payables and Procurement |
|
|
Payables |
Distribution Sets |
|
|
Payables |
General Payables Options |
|
|
Payables |
Income Tax Regions |
|
|
Payables |
Interest Rates |
|
|
Payables |
Invoice |
|
|
Payables |
Invoice Holds and Releases |
|
|
Payables |
Invoice Tolerances |
|
|
Payables |
Payables Calendars |
|
|
Payables |
Payment Terms |
|
|
Payables |
Reporting Entities |
|
|
Payments |
Credit Card Brands Audit Setup |
|
|
Payments |
Disbursement Payment Methods Audit Setup |
|
|
Payments |
Disbursement System Options Audit Setup |
|
|
Payments |
External Bank Account Audit Setup |
|
|
Payments |
External Payees Audit Setup |
|
|
Payments |
External Payers Audit Setup |
|
|
Payments |
Formats Audit Setup |
|
|
Payments |
Funds Capture Payment Method Audit Setup |
|
|
Payments |
Funds Capture Process Profile Audit Setup |
|
|
Payments |
Internal Payees Audit Setup |
|
|
Payments |
Payment Codes Audit Setup |
|
|
Payments |
Payment Process Profile Audit Setup |
|
|
Payments |
Payment System Audit Setup |
|
|
Payments |
System Security Options Audit Setup |
|
|
Payments |
Transmission Configurations Audit Setup |
|
|
Payments |
Validation Sets |
|
|
Receivables |
Application Rule Sets |
|
|
Receivables |
Approval Limits |
|
|
Receivables |
AutoAccounting Rules |
|
|
Receivables |
AutoCash Rule Sets |
|
|
Receivables |
AutoInvoice Grouping Rules |
|
|
Receivables |
AutoInvoice Line Ordering Rules |
|
|
Receivables |
AutoMatch and Application Exception Rules |
|
|
Receivables |
Balance Forward Billing Cycles |
|
|
Receivables |
Credit Scoring Models |
|
|
Receivables |
Customer Profile |
|
|
Receivables |
Interest Tiers |
|
|
Receivables |
Late Charge Schedules |
|
|
Receivables |
Payment Terms |
|
|
Receivables |
Receipt Classes and Methods |
|
|
Receivables |
Receipt Sources |
|
|
Receivables |
Receivables Activities |
|
|
Receivables |
Receivables Customer Profile Classes |
|
|
Receivables |
Reference Accounts |
|
|
Receivables |
Remit-to Addresses |
|
|
Receivables |
Revenue Contingencies |
|
|
Receivables |
Revenue Scheduling Rules |
|
|
Receivables |
Standard Memo Lines |
|
|
Receivables |
Standard Messages |
|
|
Receivables |
Statement Cycles |
|
|
Receivables |
System Options |
|
|
Receivables |
Transaction Sources |
|
|
Receivables |
Transaction Types |
|
|
Receivables |
Transmission Formats for Lockbox |
|
|
Regional Localizations |
Fiscal Document Business Unit |
|
|
Regional Localizations |
Fiscal Document Default and Control |
|
|
Regional Localizations |
Fiscal Document Series |
|
|
Revenue Management |
Contract Identification Rules |
|
|
Revenue Management |
Implied Performance Obligation Templates |
|
|
Revenue Management |
Item Groups |
|
|
Revenue Management |
Performance Obligation Identification Rules |
|
|
Revenue Management |
Performance Obligation Templates |
|
|
Revenue Management |
Pricing Dimension Assignments |
|
|
Revenue Management |
Pricing Dimension Bands |
|
|
Revenue Management |
Source Document Types |
|
|
Revenue Management |
Standalone Selling Price Effective Periods |
|
|
Revenue Management |
Standalone Selling Price Profiles |
|
|
Revenue Management |
System Options for Revenue Management |
|
|
Subledger Accounting |
Account Rule Service |
|
|
Subledger Accounting |
Accounting Method Service |
|
|
Subledger Accounting |
Condition Service |
|
|
Subledger Accounting |
Description Rule Service |
|
|
Subledger Accounting |
Journal Line Rule Service |
|
|
Subledger Accounting |
Journal Entry Rule Set Service |
|
|
Subledger Accounting |
Mapping Set Service |
|
|
Subledger Accounting |
Subledger Accounting Options Service |
|
|
Subledger Accounting |
Supporting Reference Service |
|
|
Subledger Accounting |
Transaction Account Type Service |
|
|
Subledger Accounting |
User-Defined Formula Service |
|
|
Tax |
Application Tax Defaults and Controls |
|
|
Tax |
Country Tax Defaults and Controls |
|
|
Tax |
Party Tax Profile |
|
|
Tax |
Tax Formula |
|
|
Tax |
Tax Group |
|
|
Tax |
Tax Rate |
|
|
Tax |
Tax Regime |
|
|
Tax |
Tax Reporting Attributes |
|
|
Tax |
Tax Rules |
|
|
Tax |
Transaction Tax |
|
Impersonation Audit
Users can temporarily designate other users to impersonate their profiles and perform application tasks on their behalf. Impersonation auditing is active even when auditing is disabled for an application. At run time, the audit setup tracks and stores information about attributes, even when auditing isn't enabled for the attributes. Impersonation auditing is enabled by default so that all actions performed by the impersonator are audited. Therefore, while viewing audit history, users can retrieve the audited information, filtered by an impersonated user.
However, impersonation auditing is limited in scope and applies only to the business objects in the Manage Audit Policies task. While impersonation auditing is enabled, updates are permitted only to the business objects in the Manage Audit Policies task. The impersonator can't update business objects in other tasks. If updates to business objects in other tasks are required, the impersonation auditing must be disabled.
Impersonation auditing is controlled through the Audit Impersonation Transaction Enabled profile option. By default it's enabled. To disable it, set the profile value to No.
Manage Oracle Social Network Objects
Management of Oracle Social Network Objects
Use the Manage Oracle Social Network Objects task for managing the Oracle Social Network Objects. The integration of Oracle Social Network with applications and business processes brings key attributes from the applications to share, socialize, and update information. This helps in making better business decisions based on additional information that you obtain and analyze within your social network environment.
Use the Manage Oracle Social Network Objects page to set up and define:
-
The business objects and attributes to enable
-
The enablement method for social network integration with Oracle Applications Cloud
To open the Manage Oracle Social Network Objects page, use the following in the Set and Maintenance work area:
-
Functional Area: Application Extensions
-
Task: Manage Oracle Social Network Objects
Use Oracle Social Network to:
-
Discuss projects and plans in public forums
-
Maintain:
-
Membership groups
-
Activity feeds of the people you select
-
-
Facilitate:
-
One-on-one Conversations
-
Reviews
-
Document sharing
-
An important aspect of managing Oracle Social Network objects is enabling business objects for integration.
Enabling Business Objects for Integration
A business object can't be shared within social network until a functional administrator or implementor:
-
Accesses the Manage Oracle Social Network Objects page in Oracle Applications Cloud
-
Enables the business object for social network integration
Considerations for Enabling Social Networking on Objects
You can determine whether information about a business object, such as benefit plans or sales accounts, displays in Oracle Social Network. If you enable an object for sharing, you allow users to collaborate on the object through social networking. You can choose whether all instances of an object are shared, or only at the user's discretion. You can also choose which attributes are shared, such as names, details, and who made the last update.
In addition to a wide range of predefined objects, you can share:
-
Objects and attributes that you created in Application Composer
-
Fields that you created in descriptive flexfields
In the Setup and Maintenance work area, use the following:
-
Functional Area: Application Extensions
-
Task: Manage Oracle Social Network Objects
After you click Enable Object, select one of the following enablement options:
-
Manual
-
Automatic
-
No
Manual
If you select this option, which is recommended, you let users decide whether to share each instance of the object with the social network. Once shared, all updates to the enabled attributes of the instance appear on the social network. If the instance is deleted, that information is also shared.
Click Enable All to enable all objects for all applications. Enable All automatically applies the Manual option, which means that the user can choose whether to share an object instance.
Automatic
With this option, news about all instances of the object appears on the social network, including:
-
Every newly created instance
-
All subsequent updates to the enabled attributes
-
Deletion of any instances
No
With this option, which is the default value, no news about the object appears on the social network.
After you enable a business object, you must enable one or more attributes of the object. Only the enabled attributes are shared. The Status column in the Business Objects table indicates which enabled business objects don't yet have an enabled attribute. For these objects, only the following information appear on the social network:
-
Internal bookkeeping information, when creating or updating an instance of the object.
-
News that an instance is deleted.
Update Translations
The Update Translations process sends attribute labels and business object names to Oracle Social Network for use in the user interface.
In social network, attributes or business object labels appear in the language of your locale. If you change the locale in social network, then the attribute or business object labels appear in the updated language. However, the data appears in the language in which it was originally sent to social network. If you have previously sent an instance of the business object to social network, then the instance data isn't updated. Clicking Update Translations on the Manage Oracle Social Network Objects page sends translations for business objects with the option to enable as Manual or Automatic.
Synchronization of Business Objects
Use Synchronize on the Manage Oracle Social Network Objects page to synchronize business objects. This resends the definitions of business objects having the enablement option as Manual or Automatic to Oracle Social Network.
Use the Synchronize button at the:
-
Business Objects table level: To resend the definitions of a selected business object to social network. This button is enabled only when you select a row for a business object with the enablement option as Manual or Automatic.
-
Manage Oracle Social Network Objects page level: To resend the definitions of all business objects with the enablement option as Manual or Automatic to social network.
-
Save and Synchronize: To save the modified business objects, and synchronize the unmodified business objects.
-
Synchronize: To ignore any unsaved business objects, and only synchronize the unmodified business objects.
-
Cancel: To cancel the synchronization task.
FAQs for Manage Oracle Social Network Objects
What happens if I update translations?
When you update translations, you send translations for business objects with the enablement option as Manual or Automatic to Oracle Social Network.
On updating translations, you also:
-
Synchronize the newly translated text from Oracle Applications Cloud so that it can be used within social network. This means you can:
-
Install and enable a new language.
-
Take a language patch at any time.
-
-
Send attribute labels and business object names to social network for use in its user interface.
How can I update translations?
Use Update Translations on the Manage Oracle Social Network Objects page for subsequent updates to labels and attributes.
Use the Update Translations button at the:
-
Business Objects table level: To send translations for a selected business object to Oracle Social Network. This button is enabled only when you select a row for a business object with the enablement option as Manual or Automatic.
-
Manage Oracle Social Network Objects page level: To send translations for all business objects with the enablement option as Manual or Automatic to social network.
When do I update translations?
Run the Update Translations process only after you install a new language pack of Oracle Applications Cloud.
Updating translations synchronizes the newly translated text to Oracle Social Network for integration with Oracle Applications Cloud.
What happens if I synchronize business objects?
When you synchronize business objects, you resend the definitions of business objects having the enablement option as Manual or Automatic to Oracle Social Network.
When do I synchronize business objects?
Run the Synchronize process after you use configuration sets to import the setup from the Manage Oracle Social Network Objects page in another environment.
You can also run the process whenever you want to synchronize the settings of business objects with social network without making changes in the Manage Oracle Social Network Objects page.
Search Extension Framework
Overview of Search
Users can search for product-specific business objects, such as documents, records, and purchase orders. They can use highly responsive, index-based, and full-text search capabilities. The search platform has these components:
-
The search engine, which provides primary search capabilities, such as indexing and querying, as well as supports search functions such as keyword and attribute search.
-
The search extension framework, which serves as an integration layer between search engine and Oracle Applications Cloud.
Search Extension Framework
You can use the search extension framework to define product-specific searchable business objects and provide real time, index-based, and full-text search capabilities using REST and Java APIs.
This metadata-based framework supports search features, such as functional and data security and Natural Language Support. You can manage and configure the indexes after they are created, such as manage bulk uploads or provide production-to-test support.
Here are some of the things you can view in the search results using this framework.
-
List of attributes and their associated set of available values. The attribute search results are based on the attributes of the business objects. After selecting a value for each attribute in the search result, you get more filtered results.
-
Action links associated with the searchable objects. From the search results, you can either go straight to the related page or open a specific task.
-
Recent searches for all the business objects enabled in the search.
-
Basic search results based on the keywords used.
-
Configured attachments related to transactional objects and record in your application.
Enable Search Extension Framework
Enable the search extension framework to create indexes, ingest predefined indexes, and manage search capabilities.
-
Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes. This profile option is set to No by default.
-
Make sure that you have the Manage Scheduled Job Definition (FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV) privilege to run scheduled processes.
-
Submit the ESS job to create index definition and perform initial ingest to OSCS process for creating indexes and ingesting predefined indexes.
FAQs for Search Extension Framework
What do I do if the process for creating indexes keeps failing?
It might be because of one or more of these reasons:
-
You entered incorrect index names while submitting the process. Make sure that your ESS job parameters have the correct index names. If the problem persists, contact your help desk.
-
You might not have enabled the search extension framework. Make sure you enable it.
-
Your search cloud service isn't reachable. To check its availability, submit the ESS process to check Search Cloud Service availability process.
What do I do if I get errors about enabling the search extension framework?
Follow these steps:
-
Set the Enable/Disable Search Ext Framework (ORA_FND_SEARCH_EXT_ENABLED) profile option to Yes.
-
Create indexes and ingest predefined indexes. To do so, submit the ESS job to create index definition and perform initial ingest to OSCS process.
What do I do if I get errors stating that the OSCS isn't reachable?
Follow these steps:
-
Check the availability of search cloud service. To do so, submit the ESS process to check Search Cloud Service availability process.
-
Create indexes and ingest predefined indexes. To do so, submit the ESS job to create index definition and perform initial ingest to OSCS process.
Define Global Search
Overview of Global Search Setup
You have many options for setting up the global search, from enabling or disabling it completely to controlling what appears in the autosuggest. For most of the steps, use setup tasks in the Setup and Maintenance work area.
Enable Global Search
A predefined set of business objects, for example files related to purchase order, are available for global search. These objects are grouped into categories. The search gives you results from indexed data that matches your search term.
-
Check with your help desk to make sure that objects and categories are already set up.
-
Set the Global Search Enabled (FUSION_APPS_SEARCH_ENABLED) profile option to Yes at the Site level.
-
Otherwise, the Search field isn't available in the global header for any user.
-
After you set the profile option, users must sign out and sign back in to see the global search.
-
Define Global Search
Use the following tasks in the Application Extensions functional area to control how the global search works:
-
Manage Applications Core Global Search Configurations: Define configurations that capture a collection of settings, and determine which configurations are enabled or used as default. Each configuration applies to the global search on all or specific applications or pages.
-
Manage Applications Core Global Search Suggestion Groups: Define suggestion groups, which represent categories of suggestions in the autosuggest.
-
Manage Applications Core Alternate Words: Define alternates for search terms that users enter, so that the search can also find matches based on the alternate terms.
Retain Recent Items
You can set the Recent Items Retention (FND_PURGE_RECENT_ITEMS) profile option to determine how long to retain recent items for the global search autosuggest. A page that the user opened can appear in the user's autosuggest until the specified number of days passes. Aside from the autosuggest, this profile option also applies to the recent items tracked in Favorites and Recent Items in the global header. The Favorites and Recent Items icon is available in the global header only if your default home page layout is panel or banner.
Manage Global Search Configurations
Examples of Global Search Configurations Set as Enabled or Default
Each global search configuration contains settings for the global search, and a configuration can apply to specific pages or applications. Use the Manage Global Search Configurations page to enable or disable configurations, and select the one to use as the default. The following scenarios explain which configurations actually apply to the global search, depending on the configurations that you enable or set as default.
Predefined Default
The predefined Default configuration is always enabled and set as a default. This configuration is the working default unless a custom global search configuration is also set as a default. In this scenario, you don't enable any other configuration, so this Default configuration applies to the global search on all pages, in all applications.
Custom Default
You create a global search configuration that applies to page A and application B. Later, you set your configuration as the default. Only this configuration and the predefined Default configuration are enabled. Both are set as default.
The result is that:
-
Your configuration overrides the predefined Default one and becomes the working default.
-
Even though you defined your configuration to apply to page A and application B, it now actually applies to all pages and all applications. This is because your configuration is the working default, and no other configuration is enabled.
Specific Pages or Applications
You're using either the predefined Default configuration or a custom configuration as the default. You also enable:
-
Configuration 1: Applies to application A
-
Configuration 2: Applies to application B and a few pages in application A
The result is that:
-
Configuration 1 applies to all pages in application A, except the few pages that use configuration 2.
-
Configuration 2 applies to all pages in application B, plus the few pages in application A.
-
The default configuration applies to all other applications and pages.
Create Global Search Configurations
Predefined global search configurations control how the global search behaves and looks. You can't edit these configurations, but you can duplicate them and edit the copies, or create your own from scratch.
Creating a Configuration
Follow these steps:
-
Click Navigator > Setup and Maintenance.
-
In the Setup and Maintenance work area, go to the following:
-
Functional Area: Application Extensions
-
Task: Manage Applications Core Global Search Configurations
-
-
On the Manage Applications Core Global Search Configurations page, click the Create icon, or select a row and click the Duplicate icon.
Note: You can't delete a configuration after you create it, but you can disable it. -
For the short name (identifier for your configuration), enter an alphanumeric code with uppercase letters and no spaces.
-
Enter a user-friendly name and description for the configuration.
-
Select the Default check box to use your configuration as the default instead of the predefined Default configuration. If another custom configuration was already set as the default, then your configuration becomes the new custom default.
-
Select a product family if the configuration is for applications or pages within a specific family. Otherwise, select Common.
-
If you're creating a duplicate, click Save and Close. To go on to the next steps and define more settings, select your configuration and click Edit.
-
Enter a module within the product family you selected. If you selected the Common family, then select the Oracle Middleware Extensions for Applications module.
-
Use the tabs to define your configuration:
-
Autosuggest: Determine what's available to users in the global search autosuggest, as well as how the autosuggest looks and behaves.
-
Search Field: Control the Search field in the global header and in the search results dialog box.
-
Search Results: Enable or disable saved and recent searches, select the search categories available to users, and define settings for filters.
-
Pages: Indicate the applications or pages that this global search configuration applies to.
-
-
Save your work.
Configure Attachment Search
You can enable or disable the file and content search for specific content types of attachments. You can also set the maximum file size and content size so that your users can't search the file or content if the sizes exceed the specified limits. If enabled, the searched attachments are available for download.
Before you start, ensure that the Enable Search Attachment (ORA_FND_SEARCH_ATTACH_ENABLED) profile option is enabled.
Here's how you can configure the attachment search.
-
Click Navigator > Setup and Maintenance.
-
In the Setup and Maintenance work area, go to the Manage Applications Core Global Search Configurations task in the Application Extensions functional area.
-
On the Manage Applications Core Global Search Configurations page, click Configure Attachment Search.
-
On the Configure Attachment Search page, click the Create icon, and then specify the values in these fields.
Tip: Alternatively, click Create from Sample to get the sample values, such as index names, content type, and maximum file size. Also, to view values for specific index names, you can select the index name from the Index Name list, and click Create from Sample.Field What You Do Index Name
Select the index name specific to your product.
Content Type
Enter the content type.
You specify the content type with a specific hierarchical structure, and based on that structure, you get the match of the attachments. Let's look at some examples.
-
If you specify the content type as application/vnd.ms-excel (for example, type/subtype), you get the exact match of the attachments.
Note: The subtype in this example doesn't have a fixed structure. That means you can use either a dot or a hyphen to get the exact match of attachments for specified content type. -
If you specify application/vnd.ms-*, you get the match of attachments, which are of different types, such as Microsoft Word or Microsoft Excel.
-
If you specify application/vnd.*, you get the match of the attachments, which are applicable to all suppliers.
-
If you specify */*, you get all the possible matches.
Enable File Search
Determine whether users can search the attachment.
Enable Content Search
Determine whether users can search the content in the attachment. For example, suppose you set this value as Yes for a specific type of attachment. Then, if a user searches for a keyword that's available in an enabled attachment, that attachment will appear in the search results.
Maximum File Size
Specify the maximum file size of the attachments that users can search content for. If the file size of an attachment is greater than the specified size, the content of the file won't appear in the search results at all. Only the metadata, such as file name, will be searchable.
Maximum Content Size
Specify the maximum content size of the attachments that users can search content for. Suppose you set this value as 200KB, users get the content in the attachments pertaining to this size in the search results. Make sure that this size is less than or equal to the maximum file size.
-
-
Click Save and Close.
Set Up Autosuggest for Global Search
Use global search configurations to determine what's available to users in the autosuggest. You select the suggestion groups to include in configurations. The configurations also determine how the autosuggest looks and behaves.
Prerequisite
Create a global search configuration or edit an existing one. Follow these steps:
-
In the Setup and Maintenance work area, go to the following:
-
Functional Area: Application Extensions
-
Task: Manage Applications Core Global Search Configurations
-
-
On the Manage Applications Core Global Search Configurations page, click the Create icon to create a global search configuration, or select an existing row and click the Edit icon to change it.
Defining the Content
To define synonyms, select suggestion groups and determine how they're displayed in the autosuggest:
-
On the page to create or edit global search configuration, click the Autosuggest tab.
-
In the Synonyms section on the Autosuggest tab, select Enable Synonyms to let users search using synonyms.
-
Optionally, enter the following:
-
Synonym Context Code: A logical grouping such as a product family, navigation group, or work area that determines the subset of synonyms to search on. For example, if you enter Academics, every time the user enters a term and clicks the Search icon, the search runs on all terms related to Academics and their synonyms.
-
Synonym Object Type: A business object name that would determine the subset of synonyms to search on. For example, if you enter Curriculum, every time the user enters a term and clicks the Search icon, the search runs on all terms related to Curriculum and their synonyms.
-
-
Click Manage Synonyms.
-
To add search terms and create synonyms for them, on the Manage Synonyms page:
-
Click the New icon and do the following:
-
Enter a short name in uppercase, with no spaces. This name is required as an identifier.
-
Select a module name, which is required to map the data with a specific product or area. There are no restrictions on where the synonyms can be used.
-
Optionally, enter a context code and object type. This information can be used to ensure that certain synonyms are only used when a global search configuration having the same values is in effect.
-
Enter the primary synonym, which is the main term or business object to which other synonyms are to be matched.
-
Enter at least one synonym that matches the primary synonym.
-
-
Click Save and Close.
-
-
Select the Enable personalization of search groups check box to allow users to override your configuration. Users can hide, show, and reorder suggestion groups for their autosuggest.
-
In the Suggestion Group section on the Autosuggest tab, move the groups you want to include into the Selected Groups pane. Use the Move, Move All, Remove, and Remove All icons to move the groups.
The Enabled column in the Available Groups pane indicates if the group is defined (on the Manage Suggestion Groups page) to be displayed by default or not in the autosuggest.
-
In the Enabled column in the Selected Groups pane, select one of the following values:
-
Inherit: In the autosuggest, the group is displayed or hidden by default depending on what's defined for the group.
-
Yes: The group is displayed by default, no matter what's defined for the group.
-
No: The group is hidden by default, no matter what's defined for the group.
Note: The Displayed by Default column shows the resulting behavior in the autosuggest, based on what you select in the Enabled column. -
-
Using the Move to Top, Move Up, Move Down, and Move to Bottom icons, order the selected groups as you want them to appear in the autosuggest.
Defining the Appearance
Optionally define settings in the Appearance section on the Autosuggest tab:
-
Show Suggestion Group Headings: Select this option to display suggestion group headings (text and icon) in the autosuggest. Even if you do so, if a group is defined on the Manage Suggestion Groups page to not show headings, then its heading won't be displayed.
-
Show Icons: Select this option to display icons next to suggestions in the autosuggest.
-
No Suggestions Message: Enter the message that appears when no suggestions match the user's search term. If you leave this field blank, then no autosuggest or anything at all appears when there are no matches.
Defining the Behavior
Optionally define settings in the Behavior section on the Autosuggest tab:
-
Show Top Suggestions: Enable this option to display suggestions in the autosuggest as soon as the user clicks in the search field, even without entering a search term. For example, the last few pages the user opened would appear as suggestions in the Recent Items group.
-
Minimum Characters for Autosuggest: Enter the number of characters that users must enter in the search field before matching suggestions appear in the autosuggest.
-
Maximum Number of Suggestions: Enter the maximum number of suggestions to be displayed across all suggestion groups. This total is distributed as equally as possible among the groups.
Considerations for Disabling Saved Searches and Recent Searches for the Global Search
Global search configurations determine if saved searches and recent searches are enabled in the global search. Consider the following points when you disable either. In the Create or Edit Global Search Configuration page, open the Search Results tab and use the Saved and Recent Searches section.
Disabling Saved Searches
If you disable saved searches:
-
You disable the Save button in the search results dialog box, so users can't create or edit saved searches for global search.
-
You're not disabling the Saved Searches suggestion group. Users can still see any applicable saved searches in the global search autosuggest.
Disabling Recent Searches
If you disable recent searches:
-
The application isn't saving recent searches.
-
You're not disabling the Recent Searches suggestion group. Users can still see in the autosuggest any applicable searches that they recently ran before you disabled recent searches.
Set Up Filters for Global Search
To determine how users can filter their search results, define the appropriate settings when you create or edit global search configurations. You can set up search categories so that users can limit the scope of their search to begin with, or refine their search results.
Prerequisite
Create a global search configuration or edit an existing one. Follow these steps:
-
In the Setup and Maintenance work area, go to the following:
-
Functional Area: Application Extensions
-
Task: Manage Applications Core Global Search Configurations
-
-
Click the Create icon to create a global search configuration, or select an existing one and click the Edit icon to change it.
Setting Up Categories to Narrow Search Scope
To let users select the categories to search on before running the search:
-
On the page to create or edit global search configuration, click the Search Results tab.
-
In the Saved and Recent Searches section, select the check boxes to enable saved searches and recent searches.
-
In the Filters section, enable personalization of search categories.
-
In the Search Categories section, select the categories that users can search on. If you don't select any, then every category is available to users.
-
For each of your selected categories, select Yes or No in the Enabled column to have it enabled or disabled by default.
Setting Up Categories as Search Result Filters
To let users filter search results based on category:
-
In the Filters section, select a filter display style so that the list of all available category names are displayed:
-
Inline: In the Filters pane in the search results
-
LOV: In a Categories dialog box that users can open from the Filters pane
-
-
Select the check boxes to show subcategories, facets, or both. Categories are always displayed. Subcategories are an additional level of filters that appear after categories, and facets are a level after categories.
-
In the Search Categories section, select the categories to use as filters. This is the same set of categories to be used for personalization. If you don't select any, then every category is available to users.
Setting Other Options for Filters
You can also use the Filters section to:
-
Show hit counts: Show the number of search results that match each filter value
-
Enable clear all filters: Allow users to clear all filters with one click of a button
-
Show applied filters: Show all the filters that have been applied
In the Last Updated Date Filters section, select the criteria to use as filters, based on the last update date. If you don't select any, then every date filter is available to users.
In the Appearance section, set the Show Icons option Off if you don't want to display the icons.
Specify the Pages or Applications That a Global Search Configuration Applies To
As part of defining your global search configuration, you can specify the pages or applications (or both) that your configuration applies to. If you want your configuration to apply to all pages in all applications, then skip these steps.
Before You Start
If you want the global search configuration to apply to specific applications, you need to find the application short name.
-
Click Navigator > Setup and Maintenance.
-
In the Setup and Maintenance work area, go to the following:
-
Functional Area: Application Extensions
-
Task: Manage Taxonomy Hierarchy
-
-
On the Manage Taxonomy Hierarchy page, expand the Oracle Fusion node.
-
Select the row (with the Application module type) for your application, and click Edit Module.
-
In the Application Details section, see the Application Short Name column and note down the value to use as the application short name.
Add Pages or Applications
Follow these steps:
-
On the Create or Edit Global Search Configurations page, open the Pages tab.
-
Click the Create icon.
-
In the View Type column, indicate if the configuration applies to a specific page or application.
-
Enter a view ID to identify the page or application:
Tip: You can use % as a wildcard for the page or application value, such as Example% for all pages that start with Example.-
Page: Enter the last part of the URL you get when you open that page. For example, enter
ExamplePagefrom the URLhttp://exampleServer/homePage/faces/ExamplePage. -
Application: Enter the application short name with a wildcard at the end, for example
HomePageApp%.
-
-
Add more pages or applications as needed.
Manage Suggestion Groups
Suggestion Groups for Global Search
A suggestion group is a category of suggestions that users see in the autosuggest for the global search. For example, if the user enters Report in the Search field, then the Navigator suggestion group in the autosuggest shows any Navigator menu names with Report.
Managing Suggestion Groups
Each suggestion group can have a heading, for example Recent Items, as well as an icon that appears before the heading text. The icon helps users identify what the group is all about.
You can manage suggestion groups to:
-
Show or hide the group by default in the autosuggest
-
Enter the heading text
-
Define if the heading text appears in the autosuggest or not
-
Identify the image file to use as the icon
To manage suggestion groups, open the Setup and Maintenance work area and use either the:
-
Manage Suggestion Groups task
-
Autosuggest tab when you create or edit global search configurations using the Manage Global Search Configurations task
Using in Global Search Configurations
Just because a suggestion group is defined to be displayed by default doesn't necessarily mean that it in fact appears in the autosuggest. Global search configurations determine which groups are included for the autosuggest, whether icons appear for the headings, and so on.
You can use a suggestion group in many or all global search configurations. And ultimately, if personalizing suggestion groups is enabled, then users can show, hide, and reorder the suggestion groups included in the global search configuration.
Change Heading Text and Icons for Suggestion Groups
This example shows how to change the icon and text for a suggestion group heading in the global searchautosuggest. In this example, you start out with the predefined Default global search configuration enabled, and no custom configurations.
The following table summarizes key decisions for this scenario.
| Decisions to Consider | In This Example |
|---|---|
|
Which predefined suggestion group do you want to change? |
Recent Items |
|
What do you want the new heading text to be? |
Recently Visited Pages |
|
Which image do you want to use as the icon? |
A |
|
Do you want the new suggestion group to appear in the autosuggest by default? |
Yes |
|
Which pages should the changes apply to? |
All pages |
To use a new icon and heading text for the suggestion group:
-
Make a copy of the predefined Recent Items suggestion group.
-
Update global search configurations to use your suggestion group.
Duplicate the Predefined Suggestion Group
-
Click Navigator > Setup and Maintenance.
-
In the Setup and Maintenance work area, go to the following:
-
Functional Area: Application Extensions
-
Task: Manage Applications Core Global Search Suggestion Groups
-
-
On the Manage Applications Core Global Search Suggestion Groups page, select the Recent Items group and click Duplicate.
-
In the new row, enter RECENTPAGES as the short name.
-
Change the display name to Recent Pages.
-
Change the description to Version of Recent Items with revised heading and icon.
-
With your new row still selected, click Edit.
-
In the Heading section, enter Recently Visited Pages in the Text field.
-
In the Icon field, enter the full URL to your .png file.
-
Click Save and Close.
Update Global Search Configurations
-
Back in the Setup and Maintenance work area, go to the following:
-
Functional area: Application Extensions
-
Task: Manage Applications Core Global Search Configurations
-
-
Select the Default configuration and click Duplicate.
-
Fill out the row for your new configuration, selecting the Default check box.
-
With the row still selected, click the Edit icon.
-
In the Autosuggest tab, click the Refresh button in the Suggestion Group section if you don't see your suggestion group.
-
Move the Recent Pages group into the Selected Groups list, and move the Recent Items group out.
-
In the Enabled column for the Recent Pages group, select Yes.
-
In the Appearance section, make sure that headings are set to be displayed.
-
Click Save and Close.
Considerations for Managing Alternate Words for Global Search
Use the Manage Applications Core Alternate Words task in the Setup and Maintenance work area to maintain a list of search terms that users might use for the global search. For each user keyword, define a possible alternate to also search on. Consider various reasons for defining these word pairs, and also decide whether to automatically search on both terms or not.
Reasons for Word Pairs
This table provides some reasons and examples for managing alternate words.
| Purpose | What You Enter | User Input Keyword Example | Alternate Keyword Example |
|---|---|---|---|
|
Correct user typos |
A possible typo as the user input keyword, and the correctly spelled term as the alternate keyword |
Oracel |
Oracle |
|
Account for abbreviations and acronyms |
An abbreviation or acronym and what it stands for |
BI |
business intelligence |
|
Account for common variations in spelling |
Two different ways to spell the same term |
|
|
|
Enable matches on synonyms |
A pair of terms that are functionally similar |
hyperlink |
link |
|
Help new users who are not familiar with what things are called in the application |
The term that your users might search on as the user input keyword, and the equivalent in the application as the alternate keyword |
concurrent program |
scheduled process |
Automatically Search Both Terms
For each pair of terms, use the Automatically Search Both check box to determine what happens when the user enters the input word and starts the search:
-
Yes: The search runs and displays results based on both terms.
Before you select this check box, carefully consider possible impact. For example, would users get a lot of unnecessary search results, making it harder to find what they want?
-
No: The user sees a message and can decide to continue searching on just the input term, or to search on just the alternate term instead.