Oracle Fusion Customer Relationship Management 11g Sales Essentials
Question No: 41
A company has to assign sales representatives to leads opportunities based on the size and location of the customer and the skills of the sales representative. Which three dimensions must be enabled while configuring territories?
Answer: A,D,E Explanation: D:
Note: you might want to assign a resource such as a sales representative to a business object like opportunity based on the product skill of the sales representative. In this case, when you create the opportunity work object and the sales representative candidate object, you will select the attributes of opportunity and sales representative that correspond with product skill. Selecting these attributes makes them available for mappings and for conditions on your rules, so ensure that you select the attributes that reflect the criteria that you want to use for matching business objects to work objects.
E: Location of the customer.
Note: Assignment mappings drives territory-based assignment. These mappings identify the dimensions, attributes, and territory filtering used in territory-based assignment processing. A default set of mappings are seeded. This seeding assumes that opportunities, leads, and sales accounts use the same territory hierarchy
Reference: Oracle Fusion Applications Sales Implementation Guide, Define and Maintain Opportunities
Question No: 42
Identify the three true statements about the Cube in territory Management.
It is a product of enabled dimensions.
It is a product of dimension members defined for territories.
It never enables the metrics information for territories.
It enables the metrics information for territories.
It is not a product of dimension members defined for territories.
Answer: A,B,D Explanation:
When you do not use data warehouse, dimension and transaction data are populated directly from Fusion Applications into territory dimension members and the Oracle Essbase cube. Thestructure of the cube reflects the enabled dimensions in Territory Management
(A) and their members (B, not E). The cube provides metrics information for defined territories.
Territory Management generates the cube based on the enabled dimensions and their members (A, B, not E). Territory Management loads the cube with dimension members and metrics directly from the data warehouse, in the case of the data warehouse option, or from Fusion Applications, in the case of the non-data warehouse option. The cube provides metrics information for defined territories. (D, not C)
Reference: Oracle Fusion Applications Sales Implementation Guide, Define Territory Management Configuration, Cube
Question No: 43
Identify the lookup type used for reference data sharing.
Explanation: The available kinds of lookups are as follows.
Lists the available codes and translated meanings
Additionally associates a reference data set with the lookup codes
Common Legacy lookups
Reference; Oracle Fusion Applications Compensation Management, Incentive Compensation Guide Standard, Common, and Set-Enabled Lookups
Question No: 44
You are the administrator in charge of Oracle Fusion CRM configuration for your company. While configuring products, you identify a gap where Fusion doesn#39;t provide a default method of capturing company#39;s custom account code.
Select the two possible methods used to customize the application and capture the data.
Run a SQL command to alter the database and add a column for the account code.
Use a Descriptive flexfield.
Use an Extensible flexfield.
Use a Key flexfield.
Use Oracle Pane Composer to modify the product page.
Answer: B,C Explanation:
Note: A flexfield is a set of placeholder fields (segments) that are associated with a business
object. There are three types of flexfields – descriptive, extensible, and key.
Descriptive and extensible flexfields enable you to configure your applications to capture additional attributes without having to perform custom development. For example, you can modify an application to capture additional company-specific product information, such as voltage for electronic equipment, or size and color for clothing.
Reference; Oracle Fusion Applications, Extensibility Guide, About Using Flexfields
Question No: 45
A company has introduced a new product that requires a new object in the Oracle Fusion
Sales application. What is the process to extend this new object in Oracle Fusion Sales?
The administrator uses Oracle Composer to customize a new object and content
The sales manager uses Oracle Composer to customize a new object and content
The administrator uses CRM Application Composer to customize a new object and content.
The sales manager uses Oracle Composer to customize a new object and content.
The sales manager uses Oracle Object Composer to customize a new object and content.
Explanation: Access the Application Composer from a CRM application at runtime by using the Navigator menu. The first view of the Application Composer is the main Overview page, which is the entry point into all your customization options. On the main Overview page, the regional pane at left displays the object tree, which lets you browse an application#39;s existing object configuration in a tree format. The object tree reflects the latest configuration of the application: both standard objects as well as custom objects.
To use the object tree:
Select Application Composer from the Navigator menu, under the Tools category.
On the main Overview page, select an application from the Application choice list.
For each object node, whether standard or custom, expand it further to view and edit object details, such as an object#39;s fields and Enterprise pages where the object is exposed.
For both standard and custom objects, you can view and edit the following details:
Add new fields to an object.
Modify the pages on which an object appears.
Write application logic that controls the behavior of an object#39;s records.
Buttons and links
Add buttons or links to Enterprise pages.
Define saved searches for an object.
Reference; Oracle Fusion Applications CRM Extensibility Guide, CRM Application
Composer#39;s Object Tree
Question No: 46
You are implementing Oracle Fusion CRM for your company. Currently you are configuring the Assignment Manager. Your company wants to assign territories to a sales load where the Territory Program ID is the same as the Sales Lead Program ID.
Select the mapping that you will configure to meet this requirement.
Explanation: Creating an Attribute Mapping
You want to assign territories to a sales lead when the territory program ID is the same as the sales lead program ID. Create a mapping where the work object is sales lead and the candidate object is sales lead territory. Select the territory when the attribute territory program ID is equal to the sales lead attribute program ID.
Reference: Oracle Fusion Applications Sales Implementation Guide, Creating an Attribute Mapping
Question No: 47
Which module maintains the industry hierarchy for territory definition?
Oracle Fusion Trading Community
Oracle Fusion Territory Management
Oracle Fusion Sales Quota Management
Oracle Fusion Customer Center application
Oracle Fusion Partner Management
Explanation: Manage Territory Management Synchronization Dimension Parameters: Explained
Use parameters to refine the definition of each dimension so it best fits business requirements.
Three dimensions use parameters: Industry
Use the parameter to set the number of levels in the industry hierarchy that display in the dimension member selection screen.
Set the start of the time period used in calculating metrics using the Calendar Start parameter. Set the number of years prior to today#39;s date when the calendar starts for metrics.
Use the parameter to set the number of levels in the product hierarchy that display in the dimension member selection screen.
Note: The industry hierarchy is from the customer classification module.
The profile option Industry Classification Category must be set to the classification category that you want to use before you can enable the dimension. The available selections include only classification categories belonging to the Industrial Categories grouping.
Question No: 48
A customer has Implemented Oracle Fusion sales and the sales team in the company wants to convert the qualified lead into a sales opportunity.
Identify the correct prerequisite to convert a lead into an opportunity.
lead with sales account and primary product
lead with sales account and assessment data
lead with sales account and revenue lines
lead with assessment data and primary product
lead with sales account and sales methodology
Explanation: Normally, you convert leads to opportunities that have previously been qualified.
If you determine that a lead has some potential for becoming an opportunity, you can qualify the lead. Normally, you select a rating for the lead according to a scale set up by your administrator.
You must complete a Step (link an account and contact to the lead) before you convert the lead to an opportunity.
Note: To qualify a lead 1.Select the lead.
For instructions on selecting leads, see Finding Records.
On the Lead Detail page, make sure that the lead record#39;s First Name, Last Name, Rating, Lead Owner, and Sales Person fields are filled.
NOTE: This information helps to ensure that leads are not lost after they are qualified, and that valuable sales resources are used to full advantage to follow up leads that will evolve into a sales opportunity. In particular, if the Rating and Sales Person fields are not filled, you will not be able to set the status of the lead to Qualified.
Click Mark as Qualified.
The system verifies that the critical fields contain data. If the criteria are met, the lead Status field value changes to Qualified.
Reference; Administering Oracle CRM On Demand, Converting Leads to Accounts, Contacts, or Opportunities
Question No: 49
Your company has been working with Fusion in development for some time and has decided to move to production. After configuring part of the production setup data, your supervisor decides to import the setup data from development. Because two separate teams were working on development and production, not all of the configurations match.
Industry is configured in development but not in production.
Tax Regime is configured in production but not in development
Territories are configured in both development and production, but they were configured differently.
Based on this scenario, identify the three things that will happen when the development setup imported to production.
Industry in production will remain unchanged.
Industry In production will be updated with values from development.
Tax in production will remain unchanged.
Tax In production will be deleted.
Territory will be synchronized between development and production.
Territory in production will be updated with the values from development.
Territory in production will remain unchanged.
Answer: B,C,E Explanation: Import
In the target application instance, the setup import process will insert all new data from the source configuration package that does not already exist and update any existing data with changes from the source. Setup data that exists in the target instance but not in source will remain unchanged.
Note: Almost all Oracle Fusion application implementations require moving functional setup data from one instance into another at various points in the lifecycle of the applications. For example, one of the typical cases in any enterprise application implementation is to first implement in a development or test application instance and then deploy to a production application instance after thorough testing.
Reference: Oracle Fusion Applications Sales Implementation Guide, Exporting and Importing Setup Data: Explained
Question No: 50
Oracle Fusion Territory management is used in an organization to assign sales accounts, leaders, and opportunities. It is also used to generate Business Intelligence reports. Identify three territorymanagement-related setup tasks that have to be performed by the territory administrator while configuring territories.
Identify visible members.
Enable dimensions and metrics.
Answer: A,B,C Explanation: Cube
Territory Management generates the cube based on the enabled dimensions and their members. Territory Management loads the cube with dimension members and metrics directly from the data warehouse, in the case of the data warehouse option, or from Fusion Applications, in the case of the non-data warehouse option. The cube provides metrics information for defined territories.
There are several aspects to enabling and populating dimension members, including setting profile options for certain dimensions.
Following is the sequence for populating dimensions for use in defining territories:
Change profile options for industry classification category or the classification category for auxiliary dimensions 1, 2, or 3.
If you are using data warehouse, then run ETL to populate the data warehouse with the dimension members and transactional data.
In Territory Management, identify the dimension members to be made visible in selection lists for defining territories. (A) Refresh the members before making visibility selections.
If you are using data warehouse, then run ETL to populate the data warehouse with visibility settings.
Use the stage environment in Territory Management to enable dimensions. Execute the Stage action which synchronizes the Territory Management stage environment with the data source.You can start defining territories using newly enabled and populated dimensions after you promote the stage environment to production.
Reference: Oracle Fusion Applications Sales Implementation Guide, Define Territory Management Configuration
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|