Overview of the Setup Assistant
The Setup Assistant takes care of many setups in Oracle Sales. After you enter some information, the assistant runs processes that complete many of the initial setups for you.
You can use Setup Assistant for Sales stand-alone implementations and for implementations after you're already implemented other Oracle Fusion Cloud applications.
Before You Run the Setup Assistant
Before you run the Setup Assistant, gather the required information. Descriptions are available in the Setup Assistant wizard itself and in the Excel spreadsheet that you can download.
What the Setup Assistant Completes for You
This table summarizes the information you enter in the Setup Assistant, what it does for you, and what other tasks you must complete in the application itself.
Setup Assistant Sections, Entries, and Actions | Where to Find More Information |
---|---|
Company Information You enter the company name, street address, country, and the corporate currency. The Setup Assistant creates the rudimentary enterprise structure required for Oracle Fusion Cloud applications. |
Enter Company Information and Currency |
Accounting Calendar Based on your entries, the Setup Assistant creates the periods for your sales forecasts, quotas, and reports. |
Overview of the Accounting Calendar in Sales |
Geographies You can import reference geography data for countries where you do business, and you can enable the countries for address mapping. You can import more countries in later runs. You can also set up UI validation for Sales UIs and import more countries. |
Overview of Geographies |
Top of the Sales Resource Hierarchy You enter the name, email address, and resource organization name of the Chief Executive Officer. Even if the CEO never uses your sales application, having them at the top of the hierarchy makes it easier for you to build the rest of the resource hierarchy underneath. Sales creates the resource hierarchy from the resource organization hierarchy, so you must enter a resource organization name for every manager. The resource organization name doesn't have to correspond to any actual organization, so for the CEO you can enter the company name. Both the CEO's name and the resource organization name appear in the sales resource directory, so make sure you enter them the way you'd like them displayed to the sales organization. The application sends email notifications to users when their accounts are created. If you don't want to spam the CEO, enter a dummy email address. You can't update this information in Setup Assistant on later runs. After creating the CEO, you must import the rest of the users or create them manually in the UI. |
|
Sales Catalog Root Product Group The assistant creates the top node of your Sales Catalog. It also creates all the prerequisites for creating products, including UOMs. You can't update this information in Setup Assistant on later runs. You must create the rest of the catalog in Sales, either in the
UI or using import. You might also need to create more UOMs. For
example, the application creates |
|
Resource Roles and Role Mappings Your entries in the assistant can create more resource roles and the accompanying role-provisioning rules. For example, if your sales organization includes sales support agents, you enter the resource role name here and select the job role you want to provision to salespeople with that title. The assistant creates the accompanying role-provisioning rule automatically. You can add more resource roles on later runs. You can also create more resource roles and role-provisioning rules manually. |
|
Opportunities Set the default sales method to guide salespeople through the sales process. Unless you create more sales methods ahead of time, you can only select one of the two predefined sales methods: standard or accelerated. You can edit the names of sales stages for the selected sales method, add new ones, or reorder them. By default, salespeople must enter both win or loss reasons and the primary competitors when they close an opportunity in the UI. When salespeople open opportunities, the application automatically enters a default close date for the opportunity that's 20 days after the opportunity creation date. You can change these defaults. You must complete these steps outside the assistant: opportunity statuses, win/loss reasons, and more sales methods. |
|
Competitors You can create the competitors salespeople can enter when closing lost opportunities. In the assistant, you enter the basics, such as organization size, line of business, and threat level. You can create more competitors on later runs or you can create them in the Sales Competitors work area. Note that you can set a profile option to make entering competitors required when an opportunity gets closed. |
Review the List of Competitors and Create Additional Ones |
Setup Users Create other users to help you with setup. The application automatically notifies setup users by email that their accounts are created and allows them to set their passwords. The user names are set to the email address by default. You can create more setup users on later runs. You can also create more setup users in the UI. |
Create Implementation (Setup) Users |
Adaptive Search Adaptive Search powers all Sales in the Redwood UX search. Select all of the sales objects you want to enable for Adaptive Search. You can't enable more objects in Setup Assistant in later runs. The assistant runs the required indexing process and schedules an hourly index refresh (equal to running a full publish for Adaptive Search). You can make more fields searchable in Adaptive Search. You can also enable more objects for use with REST APIs and other products. |
Video on the Setup Assistant
Review this video for more details about the Setup Assistant: