1

Setup
• Functional Setup Manager provides a central place to access and perform all of the setup steps across products. For many ERP applications, you need
to log in and out of products to perform and maintain setup steps.
• Lists of setup tasks are automatically generated in the correct sequence with dependencies highlighted. For example, the dependency to define a
ledger is to first define a chart of accounts.
• You assign setup tasks to individuals, assign due dates, and track their progress.
• Prepackaged list of tasks for setting up Fusion applications can be easily configured and extended to better fit with the business requirements.

Productivity
• You can package setup configurations as templates and use them to rapidly implement setup data across many instances. For example, if you’re
performing implementations for similar customers in similar industries, you can create a template of a typical setup and use it to get the customers up
and running very quickly. Once the majority of the setup is completed using a template, it will take you much less time to make the adjustments for the
rest of the setups that are different. The same applies to a company's internal systems. Similar setups can be consistently replicated using setup
configuration templates to get internal systems up and running quickly.
• Another powerful feature is the ability to export and import setup tasks between instances . For example, you can migrate setup data between a test
instance to a production instance. Each Business Object has an associated web service to read/write data from one instance to another.

2
Reporting
• Comprehensive reporting helps you audit and validate setup data on any instance. You can review setup reports to find out what setup data is available
at a specific instance.
Monitoring
• Individuals can view all the setup tasks assigned to them and update their completion status.

3
This is just a screen shot of Functional Setup Manager. You’ll be spending the next 4 days in here so you can explore it on
your own.

Here, we have a high level status of all implementation projects.

In the 2nd tab, the Assigned Implementation Tasks tab, you can view those tasks assigned to you.
And then the All Tasks tab shows all the tasks.

4
Apps Sign On
To log onto Fusion Applications, you need the following signons:
1. Fusion Applications
2. Oracle Identity Manager (OIM)
3. Oracle Authorization Policy Manager (APM)

If you do not know the URL's of Oracle Fusion Applications and OIM, contact the person who provisioned the systems at your company. They should
appear on the summary page. They are also recorded in a file whose default name is Provisioning Summary. The person installing the software, however,
has the option to choose a different file name. The file is created in the same location as the provisioning plan.

User IDs
The only user created during Fusion applications provisioning process is the Fusion applications super user, FAADMIN. By default, it will NOT have an
email address attached. You must assign a valid email address in LDAP (Oracle Internet Directory).

You also need the OIM system administrator user ID, XELSYSADM. The passwords are set by the person provisioning the systems.

5
Detailed Step by Step Instructions:
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=311164118762049&id=1387777.1&_afrWindowMode=0&_adf.ctrl-
state=78g5mq0mt_4
1. For the delivered FAADMIN role, you must assign a valid email address in LDAP (Oracle Internet Directory).
To do this you must enter a command from the Oracle home directory where you replace the e-mail address with a fully qualified email.

You must also reconcile LDAP and Oracle Identity Manager:

From OIM, click Advanced link, and run Scheduled Jobs. Run the LDAP User Create and Update Full Reconciliation.
This role has access to 2 job roles:
• Application Implementation Consultant
• IT Security Manager
2. Prepare IT Security Manager Role:
Neither of the job roles assigned to the default FAADMIN provides access to create/manage users. Therefore, you must add the following 2 OIM roles to
the IT Security Manager role:
• Identity User Administrators, which carries user management entitlement
• Role Administrators, which carries role management entitlement
Additionally, you must assign the Xellerate Users organization to the IT Security Manager role.

3. Generate Functional Setup Task List:

NOTE: Steps 3 - 6 will be covered in the hands on exercises. At a high level, this is what is involved:
Step 3: Analyze the offerings for Financials, create an Implementation Project, and select the Financials offering. This will generate a setup task list.
4. Define Implementation Users:
Assign the Application Implementation Consultant and Application Implementation Manager roles to at least one implementation user. This ONLY
needs to be done for the first implementation project before you create your basic enterprise structure in Step 5. After you have your basic
enterprise structure, you can just Define Users and/or employees. This initial implementation user is a user account created in Oracle Identity
Management, specifically for setting up enterprise structures, and is not related to a real person defined in HCM.
5. Set Up Basic Enterprise Structure: This involves defining reference data sharing, loading geographies, and creating your enterprise, such as legal
entities, managing locations, departments, and jobs.
6. Defining Users: This involves creating HCM role provisioning rules and performing the hire employee process in HCM to automatically created user IDs.
6
Creating Implementation Projects
1. Grouping Offerings: 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 include 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.
2. Provisioning: If an offering has NOT been provisioned, you can select it for your implementation project, but ultimately users will 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.

Implementation Users
1. Best practice: For security and audit best practice, implementation users have person records and appropriate role-based security access. So that
appropriate roles can be assigned to implementation users, you must run the process Retrieve Latest LDAP Changes before you create
implementation users.
2. Best practice: The Application Implementation Consultant role has broad access to all enterprise structures. This may be fine for experimentation and
and setting up a pilot environment. This may not be practical in a full implementation. If you want to limit access to enterprise structures for specific
products, then use the Create Data Roles for Implementation Users task to create a data role based on a job role, such as the HCM Application
Administrator job role.

7
There are three functional setup manager related roles that is delivered out of the box:

• There’s the Application implementation Manager that is usually responsible for managing the overall implementation.
During the planning phase, they might configure the offerings (which is really a product family that is implemented as a
unit, such as Financials, Procurement, Sales) that will generate the setup task list. They can then monitor the progress
of the implementation.

• Application implementation consultant, which I assume all of you are, is the super user role for functional setup
manager that has full access to all setup functionality.

• Functional owners. This is a collective term used to identify the users who are typically responsible for setting up and
maintaining setup data after you all leave.

• Before you can begin implementation, at least one user must be created that is granted access to either the
Application Implementation Manager or Application Implementation Consultant.

8
Offering, Options and Features are organized in multi-level hierarchy to help implementers in making decisions progressively during configuration of Offerings. If an implementer decides certain module/application functionality is not applicable to his/her implementation then making decision on other
modules/application functionality that depends on the first one becomes irrelevant. Functional Setup Manager, therefore, presents the Options and Features in the context of their parents.

9
We have something called Scope Value. You’ll see this popup appear for certain tasks, such as legal Entities, Business
Units, Accounting Configurations, Tax Regimes, and Legislative Data Roles. The scope value sets the context for any
subtasks.
For example, when you create an accounting configuration, the scope value is the Primary Ledger because the subtasks,
such as assigning reporting currencies, legal entities, secondary ledgers, and so on are dependent on the primary ledger.
When you have multiple BUs, Legal Entities, and Accounting Setups, and you want to update their setup options, you first
need to specify the context or scope value before you proceed with the subsequent tasks related to that context.

You’ll get lots of hands on practice with this as we do our labs.

10
11
12
Customer refunds from Fusion Receivables and expense reports from Fusion Expenses are imported into Payables as invoices of type "Payment Request.” Oracle Fusion Receivables and Oracle Fusion Expenses can submit requests to Oracle Fusion Payables to disburse funds to a payee who is not
defined as a supplier. Payables records these requests as payment requests.

iSupplier Portal invoices are Invoice Requests in Fusion Payables.

13
Customer refunds from Fusion Receivables and expense reports from Fusion Expenses are imported into Payables as invoices of type "Payment Request.” Oracle Fusion Receivables and Oracle Fusion Expenses can submit requests to Oracle Fusion Payables to disburse funds to a payee who is not
defined as a supplier. Payables records these requests as payment requests.

iSupplier Portal invoices are Invoice Requests in Fusion Payables.

14
Here is the link to our Fusion Applications Technology Library where it shows
• Release Notes
• How to Install
• How to Apply Patches
• How to Configure Security
• How to Customize Fusion Apps
• And so on.

15
You can now rapidly implement your enterprise
structures by creating the following setup objects in
a spreadsheet interface:
•Chart of accounts, including value sets, value set values,
structures, and structure instances
•Account hierarchies including trees and tree versions
•Accounting calendars (monthly type only)
•Legal entities including legal addresses, jurisdictions, and
identifiers
•Primary ledgers with legal entity assignments to primary
balancing segment values 16
Insert speaker notes

17
You can update the business units and remove the
business functions that are not applicable to the
business units

18
Insert speaker notes

19
• You can create natural account values and the
hierarchy of your natural account values
• To enter the hierarchy information, you need to first
decide the number of levels in the hierarchy
• E.g If there are 4 levels of hierarchy, the root parent
(s) have to be entered in Parent4
• Detail value has to be entered in the child value
column

20