Oracle® Fusion Applications Marketing Implementation Guide 11g Release 7 (11.1.7) Part Number E20372-07 |
Home |
Contents |
Book List |
Contact Us |
Previous |
Next |
This chapter contains the following:
Manage Application Implementation
Using the marketing business process area, your enterprise can create consumer awareness of your products or services. You can send marketing messages directly to consumers. Drive prospects towards well qualified leads for your organization's sales force. Define your company's marketing strategy, create marketing plans, define pricing and budgets, identify customer segments, create marketing collateral, and execute campaigns across multiple channels. Integration across marketing, planning, pricing, campaign development and execution, and lead management enables marketing effectiveness, intelligence, and performance analysis. You can effectively close the loop in your marketing campaigns.
Before you begin, use the Getting Started page in the Setup and Maintenance work area to access reports for each offering, including full lists of setup tasks, descriptions of the options and features you can select when you configure the offering, and lists of business objects and enterprise applications associated with the offering.
The first implementation step is to configure the offerings in the Setup and Maintenance work area by selecting the offerings and options that you want to make available to implement. For the Marketing offering, you can select the following options:
E-Mail Server for Marketing
Lead Management
Segmentation Server for Marketing
Marketing Business Intelligence Analytics
Next, create one or more implementation projects for the offerings and options that you want to implement first, which generates task lists for each project. The application implementation manager can customize the task list and assign and track each task.
If you select all of the options, the generated task list for this offering contains the following groups of tasks:
Define Common Applications Configuration
Define Common CRM Configuration
Define Territory Management Configuration
Define Lead Management
Define Common Marketing Configuration
Define Campaign Fulfillment System
Define E-Mail Server
Define Segmentation Manager
Define Transactional Business Intelligence Configuration
Define Extensions for Marketing
Use this task list to manage definitions used across offerings, typically applying to multiple products and product families. These definitions include enterprise structures, workforce profiles, security, and approval rules, amongst others.
You can find other information that supports the common implementation tasks in the Oracle Fusion Applications Concepts Guide.
Use this task list to define and manage the setup for common options within the customer relationship management set of business processes.
Use this task list to define and manage the attributes, attribute values, metrics, policies, and measure information that is related to territory management.
Use this task list to define and manage the setup to support sale leads creation and followup functions.
Use this task list to define and manage the setup for common functions within the marketing business process.
Use this task list to create and manage marketing suppliers, such as call centers and fulfillment companies, that provide campaign distribution services.
Use this task list to install and manage e-mail server configuration changes. The e-mail server provides the e-mail sending daemon that delivers e-mail, the bounce-handling daemon that tracks e-mails that cannot be delivered, and the click-through daemon that tracks e-mail recipient responses.
Use this task list to define and manage Oracle Fusion Segmentation configuration, such as list formats, merge fields, and configuration parameters, for Oracle Fusion Marketing.
Use this task list to configure Oracle Transactional Business Intelligence for ad hoc reporting, including managing the repository, connections, presentation catalog, and currency type display.
Use this task list to define extensions such as custom Oracle Enterprise Scheduler jobs.
You can also customize and extend applications using other tools. For more information, see the Oracle Fusion Applications Extensibility Guide.
The Manage Applications Implementation business process enables rapid and efficient planning, configuration, implementation, deployment, and ongoing maintenance of Oracle Fusion applications through self-service administration.
The Setup and Maintenance work area offers you the following benefits:
Prepackaged Lists of Implementation Tasks
Task lists can be easily configured and extended to better fit with business requirements. Auto-generated, sequential task lists include prerequisites and address dependencies to give full visibility to end-to-end setup requirements of Oracle Fusion applications.
Rapid Start
Specific implementations can become templates to facilitate reuse and rapid-start for comparable Oracle Fusion applications across many instances.
Comprehensive Reporting
A set of built-in reports helps to analyze, validate and audit configurations, implementations, and setup data of Oracle Fusion applications.
With Oracle Fusion Functional Setup Manager you can:
Learn about and analyze implementation requirements.
Configure Oracle Fusion applications to match your business needs.
Achieve complete visibility to setup requirements through guided, sequential task lists downloadable into Excel for project planning.
Enter setup data through easy-to-use user interfaces available directly from the task lists.
Export and import data from one instance to another for rapid setup.
Validate setup by reviewing setup data reports.
Implement all Oracle Fusion applications through a standard and consistent process.
The following documentation resources are available for learning how to configure Oracle Fusion Applications.
Functional Setup Manager Developer's Guide
Common Implementation Guide
Customer Data Management Implementation Guide
Enterprise Contracts Implementation Guide
Marketing Implementation Guide
Sales Implementation Guide
Fusion Accounting Hub Implementation Guide
Financials Implementation Guide
Compensation Management Implementation Guide
Workforce Deployment Implementation Guide
Workforce Development Implementation Guide
Incentive Compensation Implementation Guide
Procurement Implementation Guide
P6 EPPM Administrator's Guide for an Oracle Database
P6 EPPM Administrator's Guide for Microsoft SQL Server Database
Oracle Fusion Applications use the Setup and Maintenance work area, available in the Navigator menu under the Tools heading, as the central work area for planning and executing the setup tasks required to implement and maintain your Oracle Fusion CRM application.
Every phase of application implementation lifecycle is supported by the Setup and Maintenance work area, also referred to as the Functional Setup Manager.
Using the list of tasks on the left side of the Setup and Maintenance work area, you can:
Review the functionality available for implementation using the Getting Started task.
Select what functionality you want to implement using the Configure Offerings task.
Create and manage implementation projects using the Manage Implementation Projects task
You can perform individual setup and maintenance tasks, either from an implementation project or by searching for the task or task group in the All Tasks tab in the work area.
Although you are not required to create an implementation project for setting up your application functionality, implementation projects make it possible to export your setups for use in other environments using the Manage Configuration Packages task. Exporting is useful if you want to move your setups from a test environment to a production environment, for example.
Using the Getting Started task, you can review the functionality available for you to implement.
Oracle Fusion Applications functionality is organized by offerings. Offerings comprise tasks related to business processes that are typically provisioned and implemented as a unit. For Oracle Fusion CRM, there are five relevant offerings:
Offering |
Description |
---|---|
Enterprise Contracts |
Oracle Fusion Enterprise Contracts provides the most complete solution for managing sales, procurement, and other contracts. It is a comprehensive offering for standardizing corporate contract policies, improving internal controls, and complying with all contractual obligations and regulatory requirements. |
Customer Data Management |
Configure everything you need to manage customers, contacts, and resources, and ensure data quality. |
Incentive Compensation |
Configure how you manage incentive compensation, including incentive plans, performance monitoring, credit and rollup rules, earnings calculations, and payment determination. |
Marketing |
Configure everything you need to manage marketing campaigns and leads, including segmentation and e-mail servers. |
Sales |
Configure everything you need to manage sales planning and forecasting, pursue and track opportunities, align territories, and distribute sales quotas. |
Click an offering to obtain details in a series of reports. Available reports include:
Offering Content Guide
List of business processes and activities covered by the offering.
Associated Features
Lists the options and features available for implementation.
Setup Task Lists and Tasks
Complete list of implementation tasks organized in task lists. The tasks, which include all the common and prerequisite tasks, are organized in the order they are to be implemented.
Related Business Objects
Lists business objects along with the applicable Web service used for the export and import process. The report displays the business object, associated product and enterprise application, and the related Web service.
Related Enterprise Applications
List of Java Enterprise Edition applications used for entering, exporting, and importing setup data.
Using the Configure Offerings task, you can select which optional functionality or features will be available for implementation within each offering.
For example, for the Sales offering, you can enable for implementation the following optional functionality:
Competitors
Quotas
References
Sales Catalog
Sales Prediction Engine
Outlook Integration
Territory Management
Lead Management
Sales Business Intelligence Analytics
Partner Management
On the Configure Offerings page, you can also select optional features such as implementing a local help system, or automatic phone dialing with Enhanced Click-to-Dial.
When you are ready to implement, you can use the Manage Implementation Projects task to create the list of setup tasks you will need from one or more offerings. While you can implement your application by searching for each setup task individually, creating an implementation project provides you with many project management features, such as assigning tasks and tracking their completion. Creating an implementation project also makes it possible for you to export your setup after it is complete so you can reuse it in a different environment.
Although there are no restrictions on the number of offerings you can include in a single implementation project, you should create separate projects for each offering:
If you are implementing and deploying offerings at different times
To keep the list of setup tasks manageable within a project
The setup tasks in an offering or in an implementation project are organized in nested task lists in the suggested implementation order:
The most common setup tasks which apply across offerings
Tasks common to an application area such as CRM
Tasks common across multiple modules in an application area
Tasks for specific modules such as Opportunity Management, Territory Management, and Sales Forecasting
Note that:
You do not have to complete all of the setup tasks in a project or an offering. Many setup tasks are optional or have default values already populated for you.
Each offering is self-contained and includes the common tasks. If you are implementing multiple offerings, you do not have to duplicate the common task setup.
You can obtain more information about many setup task lists or individual tasks by clicking the question mark help icon. Compilations of the all the implementation help topics are available in implementation guides.
This topic highlights the differences between using the Functional Setup Manager to implement Oracle Fusion CRM on premise and in the cloud.
While there is no difference in how you use the Functional Setup Manager on premise and in the cloud, there is a difference in the setup tasks you carry out to implement your application. When you implement Oracle Sales and Marketing Cloud Service:
Some required setup tasks, listed in the following table, are already completed for you based on the information you provided on the initial questionnaire.
Some tasks in an offering may not be available. For example, Oracle Sales and Marketing Cloud Service permits you to import customer and other application data from a file, but does not permit you to load data directly into the application using a loader. Some security customizations, such as the creation of additional enterprise roles, must be done for you by service administrators. Details about the availability of specific tasks are provided in related topics.
The following table lists tasks set up for you when you implement in the Oracle Sales and Marketing Cloud Service.
Implementation Task Name |
Description |
---|---|
Manage Enterprise HCM Information |
Oracle enters the company name you provided in the questionnaire as the name of the enterprise in the application. You can search for the name from the Manage Enterprise HCM Information page and edit it. All of the other fields on the Edit Enterprise page are for Oracle Fusion Human Capital Management (HCM), and so are not relevant for CRM. |
Manage Legal Address |
This is the address you provided as the physical address in the questionnaire. As a best practice, use the same legal corporate address used for tax information. |
Manage Legislative Data Group |
The legislative data group is required for creating a legal employer. Legislative data groups are used for partitioning payroll and related data. At least one legislative data group is required for each country where the enterprise operates. CRM-only implementations require only one data group. |
Manage Legal Entity |
The legal entity is required for creating employee users. When you create a user who is an employee, you must select the legal entity, the legal employer. You can set up multiple legal entities if your business requires them, but, for CRM-only implementations, you can assign all employees to just one corporate legal employer. You must complete this task before executing the next step: Manage Legal Entity HCM Information task. |
Manage Legal Entity HCM Information |
In this task, you associate the legislative data group defined in the Manage Legislative Data Group task with the Legal Entity HCM Information. |
Manage Locations |
This is the physical address of your company. Creating a location is required for creating an item organization. An item organization is required if you are adding items into the Sales Catalog. |
Manage Business Unit |
Oracle creates one business unit for creating your employee users based on your company name. Because all CRM transactions occur in one business unit, you can assign all employees to the same corporate business unit. |
Manage Divisions |
Oracle creates a division based on your company name. Divisions are used to support management reporting for financial and subledger business functions. Divisions are not required for CRM-only implementations because CRM implements security and reporting through the territory hierarchy, not through business units and divisions. |
Manage Job |
Oracle creates the Customer Administrator job solely to enable the provisioning of enterprise roles to implementation users. When you assign the Customer Administrator job to a user, the role provisioning rule created in the next step automatically provisions the enterprise roles required by implementors. Jobs are used by Oracle Fusion HCM implementations; they are not required for CRM-only implementations. |
Manage HCM Role Provisioning Rules |
Oracle creates the rules that automatically provision CRM resources and implementors with the enterprise roles they need to perform their work. Oracle creates a separate rule for relevant enterprise roles in the security reference implementation. For a list of the rules that are set up for you, see the Application Security for the Oracle Sales and Marketing Cloud Service: Getting Started topic. |
Select the Manage Users link from the Navigator. |
Oracle creates one initial user for you. Sign in as the initial user to create other users, including other setup users. For step-by-step instructions on creating a setup user and a CRM application user, see the topics Creating Additional Implementation Users for the Oracle Sales and Marketing Cloud Service: Worked Example and Creating Application Users for the Oracle Sales and Marketing Cloud Service: Worked Example. |
Manage Currencies |
By default, the currencies you specified in the questionnaire are enabled. You can enable or disable currencies that appear in the list of values used to enter currencies in the application's user interface. |
Manage Currency Profile Option |
Select the corporate currency used by your organization. The default value is set to U.S. Dollar. This step is required for Territory Management. It is recommended that you not change the selected Corporate Currency Default profile option value for ZCA_COMMON_CORPORATE_CURRENCY after the currency is used in transactions. |
Manage Item Organizations |
Oracle creates the Global Item Organization for you. An item organization is required by the Sales Catalog if you are including items. |
Manage Product Group Profile Option Values |
Oracle sets this profile to the Global Item Organization. This association enables you to create items for use in the Sales Catalog. |
Define Default Proposal Owner |
Oracle assigns the Customer Administrator (the implementation user created for you) as the default owner of automatically generated sales territory proposals. Whenever a user creates a territory proposal, he automatically becomes its owner. The application uses the default proposal owner in cases where a proposal is created automatically by the system, as is the case when territory updates need to be propagated to inheriting territories. |
Manage Accounting Calendars |
Oracle selects the accounting calendar you specified in the questionnaire as the calendar for forecasts and territories. |
Manage Calendar Profile Option |
Oracle specifies the accounting calendar as the common calendar in the Accounting Calendar Default (ZCA_COMMON_CALENDAR) profile option. This step is required for territory management and forecasting. Caution Because many Oracle Fusion CRM applications use this profile option, do not change the value after it is set. Changing the value could result in the loss of data. |
Manage Administrator Profile Values |
Oracle assigns the Customer Administrator as the default owner or an assignee for automatically created customer center tasks, sales lead tasks and marketing campaign tasks. |
Select Forecasting Options |
Oracle sets the forecast period, frequency, due date, and territory freeze date based on the information you provided in the questionnaire. |
Manage Sales and Marketing Organizations |
Oracle creates a sales and marketing organization called Global Organization. You select this resource organization as the parent of the top organization in your resource organization hierarchy. You will be using this same task to create the resource organizations for every manager user. |
Manage Resource Organization Hierarchies |
Oracle identifies the Global Organization as the top of the sales and marketing hierarchy. |
Oracle completes the implementation tasks listed in this topic according to the information you provided when you signed up for the Oracle Sales and Marketing Cloud Service. You can verify or edit the values for each task.
The following table lists the completed tasks in the order they are implemented. Except for the Manage Users task, you can review each setup task and make any necessary changes by searching for the task name in the Setup and Maintenance work area and clicking the Go to Task button.
Links to both the Setup and Maintenance work area and the Manage Users task appear in the Navigator menu at the top of any application page.
Implementation Task Name |
Description |
---|---|
Manage Enterprise HCM Information |
Oracle enters the company name you provided. You can search for the name from the Manage Enterprise HCM Information page and edit it. All of the other fields on the Edit Enterprise page are for Oracle Fusion Human Capital Management (HCM), and so they are not relevant for CRM. |
Manage Legal Address |
This is the address you provided. As a best practice, use the same legal corporate address used for tax information. |
Manage Legislative Data Group |
The legislative data group is required for creating a legal employer. Legislative data groups are used for partitioning payroll and related data. At least one legislative data group is required for each country where the enterprise operates. CRM-only implementations require only one data group. |
Manage Legal Entity |
The legal entity is required for creating employee users. When you create a user who is an employee, you must select the legal entity, the legal employer. You can set up multiple legal entities if your business requires them, but, for CRM-only implementations, you can assign all employees to just one corporate legal employer. You must complete this task before executing the next step: Manage Legal Entity HCM Information task. |
Manage Legal Entity HCM Information |
In this task, you associate the legislative data group defined in the Manage Legislative Data Group task with the Legal Entity HCM Information. |
Manage Business Unit |
Oracle creates one business unit for creating your employee users. The name of the business unit is based on your company name. Because all CRM transactions occur in one business unit, you can assign all employees to the same corporate business unit. |
Select the Manage Users link from the Navigator. |
Oracle creates one initial user for you. Sign in as the initial user to create other users, including other users with the permissions to perform implementation tasks. These users are called setup users. For step-by-step instructions on creating a setup user and a CRM application user, see the topics Creating Setup Users for the Oracle Sales and Marketing Cloud Service: Worked Example. |
An implementation project is the list of setup tasks you need to complete to implement selected offerings and options. You create a project by selecting the offerings and options you want to implement together. You manage the project as a unit throughout the implementation lifecycle. You can assign these tasks to users and track their completion using the included project management tools.
You can also create an implementation project to maintain the setup of specific business processes and activities. In this case, you select specific setup task lists and tasks
Implementation projects are also the foundation for setup export and import. You use them to identify which business objects, and consequently setup data, you will export or import and in which order.
When creating an implementation project you see the list of offerings and options that are configured for implementation. Implementation managers specify which of those offerings and options to include in an implementation project. There are no hard and fast rules for how many offerings you should include in one implementation project. The implementation manager should decide based on how they plan to manage their implementations. For example, if you will implement and deploy different offerings at different times, then having separate implementation projects will make it easier to manage the implementation life cycles. Furthermore, the more offerings you included in an implementation project, the bigger the generated task list will be. This is because the implementation task list includes all setup tasks needed to implement all included offerings. Alternatively, segmenting into multiple implementation projects makes the process easier to manage.
Offerings are application solution sets representing one or more business processes and activities that you typically provision and implement as a unit. They are, therefore, the primary drivers of functional setup of Oracle Fusion applications. Some of the examples of offerings are Financials, Procurement, Sales, Marketing, Order Orchestration, and Workforce Deployment. An offering may have one or more options or feature choices.
The configuration of the offerings will determine how the list of setup tasks is generated during the implementation phase. Only the setup tasks needed to implement the selected offerings, options and features will be included in the task list, giving you a targeted, clutter-free task list necessary to meet your implementation requirements.
Offerings and their options are presented in an expandable and collapsible hierarchy to facilitate progressive decision making when specifying whether or not an enterprise plans to implement them. An offering or its options can either be selected or not be selected for implementation. Implementation managers decide which offerings to enable.
The Provisioned column on the Configure Offerings page shows whether or not an offering is provisioned. While you are not prevented from configuring offerings that have not been provisioned, ultimately the users are not able to perform the tasks needed to enter setup data for those offerings until appropriate enterprise applications (Java EE applications) are provisioned and their location (end point URLs) is registered.
Each offering in general includes a set of standard functionality and a set of optional modules, which are called options. For example, in addition to standard Opportunity Management, the Sales offering includes optional functionality such as Sales Catalog, Sales Forecasting, Sales Prediction Engine, and Outlook Integration. These optional functions may not be relevant to all application implementations. Because these are subprocesses within an offering, you do not always implement options that are not core to the standard transactions of the offering.
Offerings include optional or alternative business rules or processes called feature choices. You make feature selections according to your business requirements to get the best fit with the offering. If the selected offerings and options have dependent features then those features are applicable when you implement the corresponding offering or option. In general, the features are set with a default configuration based on their typical usage in most implementations. However, you should always review the available feature choices for their selected offerings and options and configure them as appropriate for the implementation.
You can configure feature choices in three different ways:
If a feature can either be applicable or not be applicable to an implementation, a single checkbox is presented for selection. Check or uncheck to specify yes or no respectively.
If a feature has multiple choices but only one can be applicable to an implementation, multiple choices are presented as radio buttons. You can turn on only one of those choices.
If the feature has multiple choices but one or more can be applicable to an implementation then all choices are presented with a checkbox. Select all that apply by checking the appropriate choices.