2Maintain Common Reference Objects

This chapter contains the following:

The Maintain Common Reference Objects task list contains tasks that support implementation of common functionality, such as data security, reference data sets, or general preferences.

Use this task list to manage common reference objects that are defined centrally and shared across applications. You can search for and access this task list in the Setup and Maintenance work area.

To make the Maintain Common Reference Objects task list available in your implementation project, go to Setup and Maintenance > Configure Offerings, and for a specific offering, select the Maintain Common Reference Objects feature choice.

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 set general preferences for all users?

Use the Global Admin Preferences page to set general preferences such as language, currency, and time zone that affect all users. In the Setup and Maintenance work area, use the following:

  • Functional Area: Application Extensions

  • Task: Set User General Preferences

Caution: Use this task only if you want to update preferences for all users. To update preferences for a specific user, use the General Preferences page.

If you want to set the preferences for new users whose preferences haven't been set at all, 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.

Define 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

Usage

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.

In the application taxonomy hierarchy, when you create a module, it becomes a child of the currently selected node. Once created, you cannot 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.

Note: Don't change the module key or alternative ID for predefined 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 does not 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 Reference Data Sharing

Reference data sharing facilitates sharing of configuration data such as jobs and payment terms, across organizational divisions or business units. You define reference data sets and determine how common data is shared or partitioned across business entities to avoid duplication and reduce maintenance effort. Depending on the requirement (specific or common), each business unit can maintain its data at a central location, using a set of values either specific to it or shared by other business units.

A common reference data set is available as the default set, which can be assigned to several business units sharing the same reference data. For commonly used data such as currencies, you can use the common reference data set and assign it to multiple business units in various countries that use the same currency. In cases where the default set can't be assigned to an entity, you can create specific sets. The data set visible on the transactional page depends on the sharing method used to share reference data.

For example, XYZ Corporation uses the same grades throughout the entire organization. Instead of different business units setting up and using the same grades, XYZ Corporation decides to create a set called Grades, which contains the grades. All business units in the organization have the Grades set so that the grades can be shared and used.

Note: For specific information about configuring reference data sharing for a particular object or product, refer to the relevant product documentation.

Reference data sets are logical groups of reference data that various transactional entities can use depending on the business context. You can get started using either the common reference data set or the enterprise set depending on your implementation requirement. You can also create and maintain additional reference data sets, while continuing to use the common reference data set.

Consider the following scenario. Your enterprise can decide that only some aspects of corporate policy should affect all business units. The remaining aspects are at the discretion of the business unit manager to implement. This enables your enterprise to balance autonomy and control for each business unit. For example, your enterprise holds business unit managers accountable for their profit and loss, but manages working capital requirements at a corporate level. Then, you can let managers define their own sales methods, but define payment terms centrally. As a result, each business unit has its own reference data set for sales methods and one central reference data set for payment terms assigned to all business units.

Partitioning

Partitioning reference data and creating data sets provide you the flexibility to handle the reference data to fulfill your business requirements. You can share modular information and data processing options among business units with ease. You can create separate sets and subsets for each business unit. Alternatively, you can create common sets or subsets to enable sharing reference data between several business units, without duplicating the reference data.

The following figure illustrates the reference data sharing method. The user can access the data assigned to a specific set in a particular business unit, as well as access the data assigned to the common set.

The figure shows a user having access to the business
data within a specific reference data set for the UK location. The
same user also has access to business data from different locations
- Tokyo, Paris, and Berlin, which are part of a common reference data
set

Oracle Fusion Applications reference data sharing feature is also known as SetID. The reference data sharing functionality supports operations in multiple ledgers, business units, and warehouses. As a result, there is a reduction in the administrative burden and the time to implement new business units. For example, you can share sales methods, or transaction types across business units. You may also share certain other data across asset books, cost organizations, or project units.

The reference data sharing features use reference data sets to which reference data is assigned. The reference data sets group assigned reference data. The sets can be understood as buckets of reference data assigned to multiple business units or other application components.

Reference Data Sets

You begin this part of your implementation by creating and assigning reference data to sets. Make changes carefully as changes to a particular set affect all business units or application components using that set. You can assign a separate set to each business unit for the type of object that is being shared. For example, assign separate sets for payment terms, transaction types, and sales methods to your business units.

Your enterprise can determine that certain aspects of your corporate policy can affect all business units. The remaining aspects are at the discretion of the business unit manager to implement. This allows your enterprise to balance autonomy and control for each business unit. For example, your enterprise holds business unit managers accountable for their profit and loss, but manages working capital requirements at a corporate level. In such a case, you can let managers define their own sales methods, but define payment terms centrally. In this example:

  • Each business unit has its own reference data set for sales methods.

  • One central reference data set for payment terms is assigned to all business units.

The reference data sharing is especially valuable for lowering the cost of setting up new business units. For example, your enterprise operates in the hospitality industry. You are adding a new business unit to track your new spa services. The hospitality divisional reference data set can be assigned to the new business unit to quickly set up data for this entity component. You can establish other business unit reference data in a business unit-specific reference data set as needed.

Reference Data Sharing Methods

Variations exist in the methods used to share data in reference data sets across different types of objects. The following list identifies the methods:

  • Assignment to one set only, no common values allowed. This method is the simplest form of sharing reference data that allows assigning a reference data object instance to one and only one set. For example, Asset Prorate Conventions are defined and assigned to only one reference data set. This set can be shared across multiple asset books, but all the values are contained only in this one set.

  • Assignment to one set only, with common values. This method is the most commonly used method of sharing reference data that allows defining reference data object instance across all sets. For example, Receivables Transaction Types are assigned to a common set that is available to all the business units. You need not explicitly assign the transaction types to each business unit. In addition, you can assign a business unit-specific set of transaction types. At transaction entry, the list of values for transaction types includes the following:

    • Transaction types from the set assigned to the business unit.

    • Transaction types assigned to the common set that is shared across all business units.

  • Assignment to multiple sets, no common values allowed. The method of sharing reference data that allows a reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use this method. It means that each payment term can be assigned to one or more than one set. For example, you assign the payment term Net 30 to several sets, but assign Net 15 to a set specific only to your business unit. At transaction entry, the list of values for payment terms consists of only the set that is assigned to the transaction's business unit.

Note: Oracle Fusion Applications contains a reference data set called Enterprise. Define any reference data that affects your entire enterprise in this set. Also update the data set going forward as you create new reference data items.

You can assign the reference data sets to reference objects using the Manage Reference Data Set Assignments page. For multiple assignments, you can classify different types of reference data sets into groups and assign them to the reference entity objects. The assignment takes into consideration the determinant type, determinant, and reference group, if any.

Determinant Types

The partitioned reference data is shared using a business context setting called the determinant type. A determinant type is the point of reference used in the data assignment process. The following table lists the determinant types used in the reference data assignment.

Determinant Type Description

Asset Book

Information about the acquisition, depreciation, and retirement of an asset that belongs to a ledger or a business unit.

Business Unit

The departments or organizations within an enterprise.

Cost Organization

The organization used for cost accounting and reporting on various inventory and cost centers within an enterprise.

Project Unit

A logical organization within an enterprise that is responsible for enforcing consistent project management practices.

Reference Data Set

References to other shared reference data sets.

Determinant

The determinant (also called determinant value) is a value that corresponds to the selected determinant type. The determinant is one of the criteria for selecting the appropriate reference data set.

Reference Groups

A transactional entity may have multiple reference entities (generally considered to be setup data). However, all reference entities are treated alike because of similarity in implementing business policies and legal rules. Such reference entities in your application are grouped into logical units called reference groups. For example, all tables and views that define Sales Order Type details might be a part of the same reference group. Reference groups are predefined in the reference groups table.

Define ISO Reference Data

When creating or editing currencies, consider these points relevant to entering the currency code, date range, or symbol for the currency.

Currency Codes

You can't change a currency code after you enable the currency, even if you later disable that currency.

Date Ranges

You can enter transactions denominated in the currency only for the dates within the specified range. If you don't enter a start date, then the currency is valid immediately. If you don't enter an end date, then the currency is valid indefinitely.

Symbols

Some applications support displaying currency symbols. You may enter the symbol associated with a currency so that it appears along with the amount.

Use the Derivation Type, Derivation Factor, and Derivation Effective Date fields to define the relationship between the official currency (Euro) of the European Monetary Union (EMU) and the national currencies of EMU member states. For each EMU currency, you define its Euro-to-EMU fixed conversion rate and the effective starting date. If you have to use a different currency for Euro, you can disable the predefined currency and create a new one.

Derivation Type

The Euro currency derivation type is used only for the Euro, and the Euro derived derivation type identifies national currencies of EMU member states. All other currencies don't have derivation types.

Derivation Factor

The derivation factor is the fixed conversion rate by which you multiply one Euro to derive the equivalent EMU currency amount. The Euro currency itself must not have a derivation factor.

Derivation Effective Date

The derivation effective date is the date on which the relationship between the EMU currency and the Euro begins.

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

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.

Note: The National Language Support (NLS) territory codes are territory identifiers used in the application. Don't edit the codes unless you must change the association between ISO and the application territory.

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.

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.

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).

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.

In Setup and Maintenance work area, search for the Manage Currencies task to set these values for a currency.

The statistical unit currency type denotes the Statistical (STAT) currency used to record financial statistics in the financial reports, allocation formulas, and other calculations.

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.

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.

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

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 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, search for the Manage Audit Policies task in the Application Extensions functional area within your offering.

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.

Tip: For business objects based on flexfields, select the Flexfields (Additional Attributes) check box to view and add or remove flexfield attributes, to include or exclude them from the audit.

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 are not audited. To continue to audit the business object with select attributes, deselect those attributes that are not 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.

To set up auditing for Oracle Applications Cloud, use the Manage Audit Policies task from the Application Extensions functional 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

Oracle Fusion Security Products

Using Auditing to Monitor 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.

The following table shows the business objects you can enable for auditing.

Area Parent Objects Child Objects

Advanced Collections

Aging Buckets

  • Aging Method Buckets

  • Aging Method Bucket Details

Advanced Collections

Backup Collectors

  • Backup Collectors

Advanced Collections

Collection Preferences

  • Collection Preferences

Advanced Collections

Collections Scoring and Strategy Assignments

  • Collections Scoring and Strategy Assignments

Advanced Collections

Collections Scoring Formula

  • Collections Scoring Formula

  • Collections Scoring Data Points

  • Collections Scoring Data Point Details

Advanced Collections

Collections Strategies

  • Collections Strategies Group

    • Collections Strategies

  • Collections Strategy Tasks

Advanced Collections

Collectors

  • Collectors

Advanced Collections

Dunning Configurations

  • Dunning Configurations

  • Dunning Configuration Details

Assets

Fixed Asset Bonus Rule

  • Fixed Asset Bonus Rule

    • Bonus Rate

Assets

Fixed Asset Book

  • Fixed Asset Book

  • Tax Authority Name

Assets

Fixed Asset Calendar

  • Fixed Asset Calendar

Assets

Fixed Asset Cash Generating Unit

  • Fixed Asset Cash Generating Unit

Assets

Fixed Asset Category

  • Fixed Asset Category

Assets

Fixed Asset Category Alias

  • Fixed Asset Category Alias

Assets

Fixed Asset Ceiling

  • Ceiling Type

    • Fixed Asset Ceiling

Assets

Fixed Asset Depreciation Method

  • Fixed Asset Depreciation Method

Assets

Fixed Asset Distribution Set

  • Fixed Asset Distribution Set

Assets

Fixed Asset Fiscal Year

  • Fixed Asset Fiscal Year

  • Fiscal Year

Assets

Fixed Asset Key

  • Fixed Asset Key

Assets

Fixed Asset Key Alias

  • Fixed Asset Key Alias

Assets

Fixed Asset Location

  • Fixed Asset Location

Assets

Fixed Asset Location Alias

  • Fixed Asset Location Alias

Assets

Fixed Asset Price Index

  • Fixed Asset Price Index

    • Price Index Value

Assets

Fixed Asset Prorate Convention

  • Convention Type

  • Fixed Asset Prorate Convention

Assets

System Controls

  • System Controls

Bill Management

Bill Management System Options

  • Bill Management System Parameters

  • Bill Management System Option Preferences

Budgetary Control

Budgetary Control and Encumbrance Accounting

  • Enabled Ledger

  • Enabled Business Unit

  • Enabled Business Function

  • Enabled Transaction Source for Project Accounting

  • Enabled Transaction Type

  • Enabled Journal Source

  • Enabled Journal Category

Budgetary Control

Control Budget

  • Control Budget

    • Control Budget Structure

    • Budget Segment Tree

    • Budget Override Rule

    • Budget Override Journal

    • Budget Override Transaction Type

    • Budget Override Rule User Assignment

    • Supplemental Rule

    • Supplemental Rule Filter

    • Supplemental Rule Filter Value Detail

Cash Management

Ad Hoc Payee Information

  • Ad Hoc Payee Information

  • External Payees Audit Setup

    • External Payees

    • Bank Account Usage

Cash Management

Bank Account

  • Bank Account

    • Bank Account Payment Document

      • Bank Account Checkbook

  • Bank Account Use

    • Bank Account General Ledger Account

    • Payment Document Category

  • Bank Account Grant

  • Bank Account Transaction Creation Rule

Cash Management

Bank Statement Parsing Rule Set

  • Bank Statement Parsing Rule Set

  • Bank Statement Parsing Rule

Cash Management

Bank Statement Reconciliation Matching Rule Set

  • Bank Statement Reconciliation Matching Rule Set

    • Bank Statement Reconciliation Rule Set Item

    • Bank Statement Reconciliation Matching Rule

    • Bank Statement Reconciliation Tolerance

Cash Management

Bank Statement Transaction Creation Rule

  • Bank Statement Transaction Creation Rule

Cash Management

Bank Transaction Codes

  • Bank Transaction Codes

Cash Management

Cash Positioning and Forecasting Options

  • Cash Positioning and Forecasting Options

    • Cash Positioning and Forecasting Time Periods

Cash Management

Cash Positioning and Forecasting Transaction Grouping

  • Cash Position Cube Dimensions

    • Cash Position Dimension Sources

Cash Management

Cash Transaction Type Mapping

  • Cash Transaction Type Mapping

Data Security

Data Security Access for Users

  • User Role Data Assignments

Expenses

Manage Conversion Rates and Policies

  • Edit Conversion Rates and Policies

  • Individual Currency Exceptions

Expenses

Manage Expense Report Templates

  • Default Template

Expenses

Manage Expenses System Options

  • System Options

Financials Common Module

Additional Intercompany Balancing and Clearing Options

  • Additional Intercompany Balancing and Clearing Options Setup

Financials Common Module

Business Unit

  • Business Functions

  • Service Provider Relationships

Financials Common Module

Intercompany Balancing Rules

  • Intercompany Rule Setup

Financials for Americas

Collection Remittance Batch Template

  • Bank Transfer Select Control

Financials for Americas

Local Holiday for Brazil

  • Local Holiday Sets

  • Local Holiday Dates

Financials for Americas

Receivables Bank Instruction for Brazil

  • Receivables Bank Instruction for Brazil

General Ledger

Account Combinations

  • Account Combinations Setup

General Ledger

Accounting and Reporting Sequences

  • Sequences Header

    • Sequences Version

  • Sequences Context

    • Sequences Assignment

General Ledger

Accounting Automation Setup

  • Accounting Automation Notifications

    • Accounting Automation Notification Users

General Ledger

Accounting Calendars

  • Accounting Calendar Setup

    • Period Details

  • Period Status

General Ledger

Allocations

  • Allocation Rule Sets

    • Allocation Runtime Prompt

    • Allocation Rules

      • Allocation Runtime Prompt

General Ledger

AutoPost Criteria Sets

  • AutoPost Criteria Set Setup

    • AutoPost Criteria Set Options

General Ledger

Chart of Accounts Mapping

  • Chart of Accounts Mapping Rule

    • Segment Rule

      • Rollup Rule

  • Account Rule

General Ledger

Clearing Accounts Reconciliation Rules

  • Clearing Accounts Reconciliation Rules Setup

General Ledger

Currency Conversion Rate Type and Rates

  • Conversion Rate Type

    • Conversion Rate Rule

  • Daily Rates

General Ledger

Data Access Set

  • Data Access Set

    • Data Access Set Assignment

General Ledger

Encumbrance Carry Forward Rules

  • Encumbrance Carry Forward Rules Setup

    • Encumbrance Carry Forward Accounts

General Ledger

Encumbrance Types

  • Journal Encumbrance Type

General Ledger

Journal Categories

  • Journal Category Setup

General Ledger

Journal Reversal Criteria Sets

  • Journal Reversal Criteria Set Setup

    • Journal Reversal Criteria Set Options

General Ledger

Journal Sources

  • Journal Source Setup

General Ledger

Journals

  • Journal Batch

    • Journal Header

      • Journal Line

General Ledger

Ledger Set

  • Ledger Set

    • Ledger Set Normal Assignment

General Ledger

Ledgers

  • Ledger Configuration

    • Legal Entities

      • Legal Entity Balancing Segment Values

    • Ledgers Setup

      • Ledger Balancing Segment Values

      • Ledger Relationships

        • Journal Conversion Rules

General Ledger

Revaluations

  • Revaluations Setup

    • Revaluation Ranges

General Ledger

Statistical Units of Measure

  • Statistical Units of Measure Setup

General Ledger

Suspense Accounts

  • Suspense Account Setup

Intercompany

Intercompany Customer Supplier Association

  • Customer and Supplier Association Setup

Intercompany

Intercompany Organization

  • Organization Setup

Intercompany

Intercompany Receivables Assignment

  • Receivables Assignment Setup

Intercompany

Intercompany System Option

  • System Option Setup

Intercompany

Intercompany Transaction Type

  • Transaction Type Setup

Legal Entity Configurator

Legal Association

  • Associated Business Entities Setup

Legal Entity Configurator

Legal Contact

  • Legal Contact Role Setup

Legal Entity Configurator

Legal Entity

  • Legal Entity Setup

Legal Entity Configurator

Legal Entity and Legal Reporting Unit Registration

  • Legal Registration Setup

    • Legal Registration Function Setup

Legal Entity Configurator

Legal Jurisdiction

  • Legal Jurisdiction Setup

    • Legal Jurisdiction Function Setup

Legal Entity Configurator

Legal Reporting Unit

  • Legal Reporting Unit Setup

Payables

Aging Periods

  • Aging Periods

    • Aging Period Details

Payables

Bank Charges

  • Bank Charge Details

Payables

Common Options for Payables and Procurement

  • Common Options for Payables and Procurement

Payables

Distribution Sets

  • Distribution Sets

  • Distribution Sets Details

Payables

General Payables Options

  • General Payables Options

Payables

Income Tax Regions

  • Income Tax Regions

Payables

Interest Rates

  • Interest Rates

Payables

Invoice

  • Invoice

    • Invoice Installments

Payables

Invoice Holds and Releases

  • Invoice Holds and Releases

Payables

Invoice Tolerances

  • Invoice Tolerances

Payables

Payables Calendars

  • Payables Calendars

  • Period Information

Payables

Payment Terms

  • Payment Terms

    • Set Assignments

    • Installments

Payables

Reporting Entities

  • Reporting Entities

    • Balancing Segment Values

Payments

Credit Card Brands Audit Setup

  • Acceptable Credit Card Brands

Payments

Disbursement Payment Methods Audit Setup

  • Disbursement Payment Methods

  • Disbursement Payment Methods Usage

Payments

Disbursement System Options Audit Setup

  • Disbursement System Options Enterprise Level

  • Disbursement System Options Business Unit Wise

Payments

External Bank Account Audit Setup

  • External Bank Account

    • External Bank Account Owner

    • Intermediary Bank Account

Payments

External Payees Audit Setup

  • External Payees

  • Bank Account Usage

Payments

External Payers Audit Setup

  • External Payers

  • Intermediary Bank Account

Payments

Formats Audit Setup

  • Format

Payments

Funds Capture Payment Method Audit Setup

  • Funds Capture Payment Method Attribute Applicability

  • Funds Capture Payment Method

Payments

Funds Capture Process Profile Audit Setup

  • Funds Capture Process Profile for Bank Account

  • Funds Capture Process Profile for Credit Card

  • Funds Capture Process Profile for Debit Card

Payments

Internal Payees Audit Setup

  • Routing Rule

  • Funds Capture Payment Method

Payments

Payment Codes Audit Setup

  • Payment Code

Payments

Payment Process Profile Audit Setup

  • Applicable Payment Process Profile

  • Payment Instruction Creation Rule

  • Payment Creation Rule

  • Payment Grouping Rule

  • Remit Advice

  • Payment System Account

  • Payment Process Profile

Payments

Payment System Audit Setup

  • Payment System Transmission Protocols

  • Payment System Formats

  • Payment System

  • Payment Scheme

Payments

System Security Options Audit Setup

  • System Security Options

Payments

Transmission Configurations Audit Setup

  • Transmission Configuration

  • Transmission Value

Payments

Validation Sets

  • Validation Values

  • Validation Assignments

Receivables

Application Rule Sets

  • Application Rule Sets

    • Application Rule

    • Application Rule Set Details

Receivables

Approval Limits

  • Receivables User Approval Limit

Receivables

AutoAccounting Rules

  • AutoAccounting Rules Segment

Receivables

AutoCash Rule Sets

  • AutoCash Rule Details

    • AutoCash Rules

Receivables

AutoInvoice Grouping Rules

  • AutoInvoice Grouping Rule

    • AutoInvoice Grouping Rule Transaction Type

    • AutoInvoice Grouping Rule Group By

Receivables

AutoInvoice Line Ordering Rules

  • AutoInvoice Line Ordering Rule

    • AutoInvoice Line Ordering Rule Order By

Receivables

AutoMatch and Application Exception Rules

  • Application Exception Rules

    • Application Exception Rule Details

  • AutoMatch Rule Set

    • AutoMatch Rule Set Details

Receivables

Balance Forward Billing Cycles

  • Receivables Balance Forward Billing Cycle

Receivables

Credit Scoring Models

  • Credit Scoring Model Details

    • Credit Scoring Model Range

Receivables

Customer Profile

  • Trading Community Customer Billing Account

    • Trading Community Customer Account Relationship

  • Trading Community Customer Account or Site Role

    • Trading Community Customer Account or Site Role Responsibility

  • Trading Community Customer Account Site

    • Trading Community Customer Account Site Use

  • Customer Profile

    • Customer Profile Amount

  • Address

    • Trading Community Address Purpose

    • Location Detail

Receivables

Interest Tiers

  • Interest Tier

    • Interest Tier Levels Information

Receivables

Late Charge Schedules

  • Late Charge Schedule

    • Late Charge Schedule Header

    • Late Charge Schedule Line

Receivables

Payment Terms

  • Payment Terms

    • Payment Terms Line

    • Payment Terms Line Discount

Receivables

Receipt Classes and Methods

  • Receipt Classes

    • Receipt Method

    • Receipt Method Account

Receivables

Receipt Sources

  • Receipt Sources

Receivables

Receivables Activities

  • Receivables Activities

    • Receivables Activities Legal Entity Detail

Receivables

Receivables Customer Profile Classes

  • Receivables Customer Profile Class

    • Receivables Customer Profile Class Amount

Receivables

Reference Accounts

  • Transaction Type Reference Account

Receivables

Remit-to Addresses

  • Remit to Address

  • Receipts from Criteria

Receivables

Revenue Contingencies

  • Revenue Contingencies

Receivables

Revenue Scheduling Rules

  • Revenue Scheduling Rules

Receivables

Standard Memo Lines

  • Standard Memo Lines

    • Transaction Type Reference Account

Receivables

Standard Messages

  • Standard Messages

Receivables

Statement Cycles

  • Statement Cycles

    • Statement Cycle Dates

Receivables

System Options

  • System Options

Receivables

Transaction Sources

  • Transaction Sources

Receivables

Transaction Types

  • Transaction Type Reference Account

Receivables

Transmission Formats for Lockbox

  • Transmission Formats for Lockboxes

    • Transmission Record Formats for Lockboxes

    • Transmission Field Formats for Lockboxes

Regional Localizations

Fiscal Document Business Unit

  • Fiscal System Options

Regional Localizations

Fiscal Document Default and Control

  • Fiscal System Options

Regional Localizations

Fiscal Document Series

  • Fiscal Document Series

Revenue Management

Contract Identification Rules

  • Contract Identification Rules

    • Contract Identification Rule Details

Revenue Management

Implied Performance Obligation Templates

  • Implied Performance Obligation Templates

    • Implied Performance Obligation Template Details

Revenue Management

Item Groups

  • Item Groups

    • Item Group Assignments

Revenue Management

Performance Obligation Identification Rules

  • Performance Obligation Identification Rules

    • Performance Obligation Grouping Rules

    • Performance Obligation Grouping Rule Details

Revenue Management

Performance Obligation Templates

  • Performance Obligation Templates

    • Performance Obligation Template Item Assignments

Revenue Management

Pricing Dimension Assignments

  • Pricing Dimension Assignment Names

    • Pricing Dimension Assignments

Revenue Management

Pricing Dimension Bands

  • Pricing Dimension Band Names

    • Pricing Dimension Bands

Revenue Management

Source Document Types

  • Source Document Types

Revenue Management

Standalone Selling Price Effective Periods

  • Standalone Selling Price Effective Periods

Revenue Management

Standalone Selling Price Profiles

  • Standalone Selling Price Profiles

    • Standalone Selling Price Profile Assignments

    • Standalone Selling Price Profile Price Band Assignments

Revenue Management

System Options for Revenue Management

  • Source Document Type Integration with Revenue Management

  • Currency Conversion for Revenue Management

  • Receivables Transaction Source Integration with Revenue Management

Subledger Accounting

Account Rule Service

  • Account Rule Details Audit

Subledger Accounting

Accounting Method Service

  • Journal Entry Rule Set Assignment Audit

Subledger Accounting

Condition Service

  • Conditions Audit

Subledger Accounting

Description Rule Service

  • Description Rule Details Audit

Subledger Accounting

Journal Line Rule Service

  • Journal Line Rule Attribute Assignment Audit

  • Journal Line Rule Audit

Subledger Accounting

Journal Entry Rule Set Service

  • Account Rule Line Assignment Audit

  • Supporting References Line Assignment Audit

  • Accounting Attributes Assignment Audit

  • Description Rule Assignment Audit

  • Journal Entry Rule Set Audit

Subledger Accounting

Mapping Set Service

  • Mapping Set Entered Source Audit

  • Mapping Set Flavor Audit

  • Mapping Set Value Audit

Subledger Accounting

Subledger Accounting Options Service

  • Subledger Accounting Options Event Class Audit

  • Subledger Accounting System Options Audit

  • Subledger Accounting Options Audit

Subledger Accounting

Supporting Reference Service

  • Supporting Reference Audit

  • Supporting Reference Source Assignments Audit

Subledger Accounting

Transaction Account Type Service

  • Transaction Account Definition Details Audit

  • Transaction Account Definition Audit

Subledger Accounting

User-Defined Formula Service

  • User-Defined Formula Audit

Tax

Application Tax Defaults and Controls

  • Application Tax Defaults and Controls

Tax

Country Tax Defaults and Controls

  • Country Tax Defaults and Controls

Tax

Party Tax Profile

  • Party Tax Profile

Tax

Tax Formula

  • Tax Formula Detail

Tax

Tax Group

  • Withholding Tax Group

Tax

Tax Rate

  • Set Enabled Lookup Type

    • Set Enabled Lookup Values

Tax

Tax Regime

  • Tax Regime

  • Default Tax Accounts

Tax

Tax Reporting Attributes

  • Tax Reporting Type Use

Tax

Tax Rules

  • Tax Rule Account Result

  • Tax Determining Factor Set

  • Tax Rule Condition Set

  • Tax Rule Result

  • Tax Rule Condition Details

  • Tax Rule Result

Tax

Transaction Tax

  • Tax Code

  • Transaction Tax

Users can temporarily designate other users to impersonate their profiles and perform application tasks on their behalf. By default, all impersonations are audited. In the global header, click your user name and from the Settings and Actions menu, select Set Preferences.

At run time, audit setup tracks and stores information about all attributes, whether auditing is enabled for an attribute or not. As a result, impersonation auditing is also active even when auditing is disabled for an application. The audit history captures the impersonator information in addition to the actual user information. Therefore, while viewing audit history, users can retrieve the audited information, filtered by an impersonated user.

To assign or modify impersonations, in the Tasks pane on the Preferences page, click Proxies. You can search for the users who can be impersonated and switch the access to that user.

Note: The associated profile option Audit Impersonation Transaction Enabled is enabled by default. To disable it, set its profile value to No.

Manage 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

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.

Note: When you click Disable Object, the enabled setting of the selected business object is automatically changed to No.

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.

The Update Translations process sends attribute labels and business object names to Oracle Social Network for use in the user interface.

In social network, the attribute 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 enablement option as Manual or Automatic.

Synchronize Business Objects: Explained

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.

Note: If you had modified any business object enabled for social network and not saved your changes, then on clicking Synchronize, a warning message appears. This message informs you that you have not saved your changes, and you can select one of the following options:
  • 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

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.

Note: When you save the enablement of a business object to social network, it sends the translations as well. Hence, you need not click Update Translations after saving the enablement.

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.

Note: When you save the enablement of a business object to social network, it sends the translations as well. Hence, you need not click Update Translations after saving the enablement.

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.

Manage Applications Core Common Reference Objects

Manage Applications Core Messages

Message names that begin with FND_CMN are common messages. Each common message can appear in multiple places in any product family across Oracle Applications Cloud. For example, the FND_CMN_NEW_SRCH message can be used for any search to indicate that no results were found. Common messages of type error or warning are part of the message dictionary.

Creating and Editing Common Messages

You can create common messages for use in multiple places. However, ensure that you follow the predefined naming convention and numbering series associated with the application or module.

Note: Don't use FND_CMN as the prefix for the messages you create because all the predefined common messages begin with it.

Common messages can be used in any application. Therefore, consider the ramifications if you edit any aspect of the message, including incident and logging settings. Changes would be reflected in all instances where the message is used. For example, if you change the message text, ensure that the text is generic and applies to the entire site of Oracle Applications Cloud implementation.

Manage Applications Core Administrator Profile Values

The general preferences such as Language, Territory, or Date Format that you access from the global header have corresponding predefined profile options.

General Preferences

When users define their preferred Date Format, Language, or Currency, they are setting the value of a profile option at the user level.

Profile Options

When users don't specify anything as their preferences, the Site level profile option takes effect.

Setting Up for General Troubleshooting: Points to Consider

To help the help desk troubleshoot issues that users encounter in the application, users can record the issue while they reproduce it. Some advanced users might also need detailed information in the About This Page dialog box. Setting up for troubleshooting involves making sure that users have the right access, and determining how many users can record at the same time.

Access

Check with your security administrator that the appropriate users are assigned roles that inherit the following privileges:

  • Record and View Issue (FND_RECORD_AND_VIEW_ISSUE_PRIV): To create a basic recording

  • Set Issue Recording Advanced Options (FND_SET_ISSUE_RECORDING_ADVANCED_OPTIONS_PRIV): To set advanced options before starting the recording

  • View Version Information (FND_VIEW_VERSION_INFORMATION_PRIV): To see the versions that technical components of the application are on

Number of Users

Recordings are stored on servers, and by default, up to five users can record at the same time on each server. For performance reasons, you can set the Maximum Number of Users Allowed to Record Issues (ORA_FND_RECORD_ISSUE_MAX_USERS) profile option to a number lower than five.

Managing Profile Option Values for CORS Headers: Points to Consider

You can set profile option values for the CORS headers using the Manage Administrator Profile Values task in the Setup and Maintenance work area.

CORS Headers

This table lists the CORS headers that you can set profile option values for.

CORS Header Profile Option Name (Profile Option Code) Profile Option Values

Access-Control-Allow-Origin

Allowed Domains (ORACLE.ADF.VIEW.ALLOWED_ORIGINS)

Valid values for allowed origins:

  • URL of the specific origin, for example, http://www.exampledomain.com

  • Comma-separated list of origins, for example,

    http://www.exampledomain.com, http://us.example.com, http://software.example.com

  • * to allow access to resources from all origins

  • Empty (no value set) to prevent access to resources from any origin

Note: You must set a value for this header to enable CORS.

Access-Control-Max-Age

CORS: Access-Control-Max-Age (CORS_ACCESS_CONTROL_MAX_AGE)

Default value for caching preflight request is 3600 seconds.

Access-Control-Allow-Methods

CORS: Access-Control-Allow-Methods (CORS_ACCESS_CONTROL_ALLOW_METHODS)

Default values for allowed methods are OPTIONS, HEAD, GET, POST, PUT, PATCH, and DELETE.

Access-Control-Allow-Headers

CORS: Access-Control-Allow-Headers (CORS_ACCESS_CONTROL_ALLOW_HEADERS)

Default values for allowed headers are Accept, Accept-Encoding, Authorization, Cache-Control, Content-Encoding, Content-MD5, Content-Type, Effective-Of, If-Match, If-None-Match, Metadata-Context, Origin, Prefer, REST-Framework-Version, REST-Pretty-Print, Upsert-Mode, User-Agent, X-HTTP-Method-Override, and X-Requested-By.

Access-Control-Allow-Credentials

CORS: Access-Control-Allow-Credentials (CORS_ACCESS_CONTROL_ALLOW_CREDENTIALS)

  • True to enable sending credentials with the request

  • False, which is the default value, to disable sending credentials with the request

In the Setup and Maintenance work area, use the following:

  • Functional Area: Application Extensions

  • Task: Manage Applications Core Administrator Profile Values

Search for the Privacy Statement URL profile option. In the profile values section, update the Profile Value text box with the full URL of the web page containing the privacy content.

In the global header, click your user name or image and from the Settings and Actions menu, select About This Application. Click Privacy Statement to view the linked web page.

How can I make message components visible only to specific users?

Use the Manage Administrator Profile Values task to determine the visibility of the message components. For the Message Mode profile option, set the profile value to either User or Administrator. Based on the set value, the administrator or user actions and details appear for the intended audience.

However, the message components are visible to the audience based on their predefined access rights. Anyone having a user level access can't view the Administrator message components. If you set the profile value to the administrators of a specific product, the message components are visible only to that specific audience.

Note: If you don't set any value to the profile option, the visibility of the message component is determined by the default profile option settings.

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.

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.

  1. In the Setup and Maintenance work area, open the panel tab and click Search to search for the Manage Administrator Profile Values task.

  2. Search for the Translation Editor Languages profile option.

  3. 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.
  4. Click Save and Close. The language entries will take effect for the user in the next sign in.

Define Global Search

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.

Enabling Global Search

A predefined set of business objects, for example help files in Applications Help, are available for global search. These objects are grouped into categories. The search gives you results from indexed data, for example the help files with text that matches your search term.

Enabling global search includes setting up the predefined objects and categories, and starting a schedule to refresh the index so that users get the latest results.

  1. Check with your help desk to make sure that objects, categories, and schedules are already set up.

  2. 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.

Note: Enabling global search is the only mandatory setup. You can skip the following setup steps, and just use the default configuration for the global search.

Defining 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 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.

Retaining 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

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.

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:

  1. Click Navigator > Setup and Maintenance.

  2. In the Setup and Maintenance work area, go to the following:

    • Functional Area: Application Extensions

    • Task: Manage Applications Core Global Search Configurations

  3. 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.
  4. For the short name (identifier for your configuration), enter an alphanumeric code with uppercase letters and no spaces.

  5. Enter a user-friendly name and description for the configuration.

  6. 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.

  7. Select a product family if the configuration is for applications or pages within a specific family. Otherwise, select Common.

  8. 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.

  9. Enter a module within the product family you selected. If you selected the Common family, then select the Oracle Middleware Extensions for Applications module.

  10. 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.

  11. Save your work.

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:

  1. In the Setup and Maintenance work area, go to the following:

    • Functional Area: Application Extensions

    • Task: Manage Applications Core Global Search Configurations

  2. 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:

  1. On the page to create or edit global search configuration, click the Autosuggest tab.

  2. In the Synonyms section on the Autosuggest tab, select Enable Synonyms to let users search using synonyms.

  3. 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.

  4. Click Manage Synonyms.

  5. To add search terms and create synonyms for them, on the Manage Synonyms page:

    1. 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.

    2. Click Save and Close.

  6. 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.

  7. 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.

  8. 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.
  9. 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.

Tip: Click Manage Suggestion Groups at any time to edit or create suggestion groups. When you return to the Autosuggest tab, click Refresh to reflect the changes you made to suggestion groups.
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.

Global search configurations determine if saved searches and recent searches are enabled in the global search. Consider the following points when you use 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.

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:

  1. In the Setup and Maintenance work area, go to the following:

    • Functional Area: Application Extensions

    • Task: Manage Applications Core Global Search Configurations

  2. 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:

  1. On the page to create or edit global search configuration, click the Search Results tab.

  2. In the Saved and Recent Searches section, select the check boxes to enable saved searches and recent searches.

  3. In the Filters section, enable personalization of search categories.

  4. 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.

  5. 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:

  1. 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

  2. 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.

  3. 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.

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.

Prerequisites

If you want the global search configuration to apply to specific applications, you need to find the application short name.

  1. Click Navigator > Setup and Maintenance.

  2. In the Setup and Maintenance work area, go to the following:

    • Functional Area: Application Extensions

    • Task: Manage Taxonomy Hierarchy

  3. On the Manage Taxonomy Hierarchy page, expand the Oracle Fusion node.

  4. Select the row (with the Application module type) for your application, and click Edit Module.

  5. In the Application Details section, see the Application Short Name column and note down the value to use as the application short name.

Adding Pages or Applications

Follow these steps:

  1. On the Create or Edit Global Search Configurations page, open the Pages tab.

  2. Click the Create icon.

  3. In the View Type column, indicate if the configuration applies to a specific page or application.

  4. 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 ExamplePage from the URL http://exampleServer/homePage/faces/ExamplePage.

    • Application: Enter the application short name with a wildcard at the end, for example HomePageApp%.

  5. Add more pages or applications as needed.

Manage Suggestion Groups

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

Tip: You can copy predefined suggestion groups and edit them to create your own versions.

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.

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 .png file (16 by 16 pixels) that's used on your company Web site

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.

Duplicating the Predefined Suggestion Group
  1. Click Navigator > Setup and Maintenance.

  2. In the Setup and Maintenance work area, go to the following:

    • Functional Area: Application Extensions

    • Task: Manage Applications Core Suggestion Groups

  3. On the Manage Applications Core Suggestion Groups page, select the Recent Items group and click Duplicate.

  4. In the new row, enter RECENTPAGES as the short name.

  5. Change the display name to Recent Pages.

  6. Change the description to Version of Recent Items with revised heading and icon.

  7. With your new row still selected, click Edit.

  8. In the Heading section, enter Recently Visited Pages in the Text field.

  9. In the Icon field, enter the full URL to your .png file.

  10. Click Save and Close.

Updating Global Search Configurations
  1. Back in the Setup and Maintenance work area, go to the following:

    • Functional area: Application Extensions

    • Task: Manage Applications Core Global Search Configurations

  2. Select the Default configuration and click Duplicate.

  3. Fill out the row for your new configuration, selecting the Default check box.

  4. With the row still selected, click the Edit icon.

  5. In the Autosuggest tab, click the Refresh button in the Suggestion Group section if you don't see your suggestion group.

  6. Move the Recent Pages group into the Selected Groups list, and move the Recent Items group out.

  7. In the Enabled column for the Recent Pages group, select Yes.

  8. In the Appearance section, make sure that headings are set to be displayed.

  9. Click Save and Close.

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

email

e-mail

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

Note: You don't have to account for plurals or case sensitivity. For example, if you have email as a user input word, you don't have to also add Email or emails as an input word.

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.