Oracle Cloud Financials

Oracle Fusion Financials offers an integrated financial management suite that is

really designed to automate, streamline, and control an organization’s financial
management processes end-to-end. It includes a broad suite of applications that are
completely integrated. It has your traditional GL, Payables, Receivables, Assets, Expenses,
Collections and Cash Management as well as the common module architecture from EBS
that includes the centralized Subledger Accounting, centralized customer and supplier data
(TCA :Trading Community Architecture), Tax, Payments, and Intercompany.

Implementation
The Functional Setup Manager (FSM)
The Functional Setup Manager (FSM) in Oracle Fusion is a centralised place where configurations are
done for the user. It is also called the Setup and Maintenance work area.
The Oracle Fusion Functional Setup Manager enables rapid and efficient planning, implementation, and
deployment of Oracle Fusion Applications through self service administration.
By using the Functional Setup Manager, the organisation can:
Learn and analyse implementation requirements of Oracle Fusion Applications.
Configure Oracle Fusion Applications to match the organisation’s business needs.
Get complete visibility to setup requirements through guided and sequential task lists.
Enter setup data through user interfaces available directly from the task lists.
Export and import to rapid start functional setup at different instances.
Validate setup by reviewing setup data reports.
The Functional Setup Manager is used to implement all Oracle Fusion Applications through a standard
and consistent process.
In addition, the Functional Setup Manager allows application developers to manage application design
objects, which are the core components of Oracle Fusion Applications, and to add and modify the
functionality of the Oracle Fusion Applications.

Navigating to the Functional Setup Manager

There are two ways to navigate to the Functional Setup Manager:
Through the Navigator menu
a. Click on the Navigator icon in the Global Area on the top of the application
(circled in the screenshot below).
b. Go to Tools ->Setup and Maintenance

Fig, 1 - The Navigator icon in the Global Area is circled

 Fig. 2 - The ‘Setup and Maintenance’ link on the Navigator menu
Through the Settings and Actions menu
a. Click on the name of the user with which you have logged in to the
application.
b. On the Settings and Actions menu, go to Administration ->Setup and
Maintenance.

Fig. 3 - The name of the user logged in

 Fig. 4 - The ‘Setup and Maintenance’ link on the Settings and Actions menu
An important point to note about the Functional Setup Manager is that it is role driven. This means that it
can only be accessed by the users who have administrative privileges. Not every user can configure the
application using the Setup and Maintenance work area.
Specifically, a user with either of the two roles, Application Implementation
Consultant or Application Implementation Manager, can configure the application by
using the Functional Setup Manager.
The Setup and Maintenance Work Area
When you navigate to the Setup and Maintenance work area by either of the two methods shown above,
you will be taken to the Setup and Maintenance home page.

Fig. 5 - The home page of the Setup and Maintenance work area
If you click on the Getting Started link under Implementations from the task list on
the left, a sequence of the implementation process will be shown: Plan, Configure,
Implement, Export and Import, Transact, and Maintain. You can click on the
links below each step of the process to perform the respective tasks.

Fig. 6 - Getting started with Oracle Fusion Applications - Setup and Maintenance
1. Plan
Here, you plan all of the details of the application.
2. Configure
The details of the application are configured. The task is Configure Offerings, where you
configure the settings of the features of the application.
3. Implement
The various projects of the application, called “implementation projects,” are managed
using the Manage Implementation Projects task.
4. Export and Import
Here, the configuration settings can be imported and exported between different instances,
as long as they are of the same version or patch level. The task is Manage configuration
Packages.
5. Transact
The actual transaction takes place. The “transactions” is nothing but the actual operation
of the application to be run.
6. Maintain
Maintenance such as reports, error checking, etc. can be done by using the Perform
Maintenance Tasks task.
Offerings
The first step is to choose the offerings to be implemented. When you scroll down from the
implementation process, you will be able to see a variety of “offerings” available that can be implemented
in the application. Click on each of the offering’s name to view the contents and documents related to that
offering.
 Fig. 7 - Various offerings available to be implemented

Fig. 8 - The contents of the ‘Financials’ offering

Configure Offerings
In order to configure the settings of the offerings that are required, go to the
Configure Offerings task under Implementations from the task list on the left.

Fig. 9 - The ‘Configure Offerings’ task

You will see that the offerings that have been installed will have their Provisioned
field set to Yes. This means that the offering has been provisioned for the user.
In order to use the offerings and the tasks associated with it, the checkbox under
the Enable for Implementation field has to be checked. Note that checking the
parent (Financials) checkbox alone is not enough. You will have to expand the
offering name to view the subdivisions, and then check each box individually in
order to have that component enabled for implementation.

Fig. 10 - The ‘Financials’ offering on the Configure Offerings page

There are three levels to the offerings and their modules. They are the offering itself, its options, and the
features.
To select the choice of features available in the offering, click on the pencil icon
(circled in the screenshot below) under the Select Feature Choices column.

Fig. 11 - The three levels of the offerings

After selecting the checkboxes of the required features, click on the Save and Close button.
 Fig. 12 - Selecting the feature choices
definition of the enterprise structure in Oracle Fusion.
Defining the Enterprise Structure
One of the most critical decisions for any project is the enterprise structure. As discussed before, the
Enterprise is at the top of the structure. There can be only one enterprise for a project in Fusion.
The next step after the creation of an implementation project and implementation users is to configure the
enterprise structure of the project. The following steps detail the method of configuring the enterprise
structure:
1. Go to the required implementation project by clicking on its name from the Manage
Implementation Projects page.
2. Expand the task list and click on the Go To Task icon (circled in the screenshot below)
corresponding to the Manage Enterprise HCM Information task under Define Enterprise for
Financials.
3. The details of the enterprise will be shown. By default, the name of the enterprise will be
“Setup Enterprise.” To change the name or any other detail of the enterprise, click on the
Edit button, followed by the Update or Correct option (circled in the screenshot below). The
fields will then become editable. After making any necessary changes, click on the Submit
button.
The difference between the two options is the maintenance of history. If you choose the
Update option, the detail(s) will be updated in the database along with a version history.
The Correct option simple changes the detail(s) in the same version of the entry, without a
historical record of the previous data, rather than updating it.
4. Click on the Done button after making any changes required.

Fig. 1 - The required implementation project

 Fig. 2 - The ‘Manage Enterprise HCM Information’ task

Fig. 3 - The details of the enterprise

Fig. 4 - The ‘Update’ and ‘Correct’ options to change the details of the enterprise
 Fig. 5 - After clicking on ‘Update’ or ‘Correct,’ all of the fields will become editable
Managing Locations
To create a location for the enterprise follow the steps detailed below:
1. Expand the task list of the implementation project and click on the Go To Task icon (circled
in the screenshot below) corresponding to the Manage Location task under Define
Enterprise for Financials.
2. The Manage Locations page will open. To create a location, click on the Create button,
followed by the Create option (circled in the screenshot below). In case a large number of
locations need to be created, the Create in Spreadsheet option may be used.
3. Enter the basic details and other location information. Make sure that all of the mandatory
fields, marked by an asterisk (*), are filled.
4. After entering the required details, click on the Submit button.
5. A pop-up message will appear asking you to confirm the submission of the details. Click on
the Yes button.
6. A confirmation message will pop up. Click on the OK button.

Fig. 6 - The ‘Manage Locations’ task

 Fig. 7 - Creating a location for the enterprise

Fig. 8 - Entering the basic details and location information

Fig. 9 - Entering the contact details and shipping details of the location
 Fig. 10 - The submission prompt

Fig. 11 - The confirmation message

Managing Legal Jurisdictions
A jurisdiction is a physical territory, such as a group of countries, country, state, county, or parish, where a
particular piece of legislation applies. French Labour Law, Singapore Transactions Tax Law, and U.S.
Income Tax Laws are some examples of particular legislations that apply to legal entities operating in
different countries’ jurisdictions. Judicial authority may be exercised within a jurisdiction.
The following steps detail how to manage legal jurisdictions in an implementation project in Oracle
Fusion:
1. Go to the required implementation project by clicking on its name from the Manage
Implementation Projects page.
2. Expand the task list and click on the Go To Task icon (circled in the screenshot below)
corresponding to the Manage Legal Jurisdictions task under Define Legal Jurisdictions and
Authorities for Financials.
3. In order to search for the territory, click on the arrow of the Territory field dropdown and click
on the Search… option (shown in the screenshot below).
4. Search for the name of the territory (you can use the ‘%’ symbol as a wildcard character).
Select the territory from the search results and click on the OK button (circled in the
screenshot below).
5. Click on the Search button.
6. From the search results, click on the name of the required jurisdiction (circled in the
screenshot below).
7. The details of the legal jurisdiction will be displayed. After making any edits if necessary,
click on the Save and Close button, otherwise click on the Cancel button.

Fig. 12 - The ‘Manage Legal Jurisdictions’ task

 Fig. 13 - Searching for a territory

Fig. 14 - Searching and selecting the territory

Fig. 15 - The search results of the jurisdiction search

 Fig. 16 - Viewing and editing the details of the legal jurisdiction
Managing Legal Addresses
The next step in configuring the enterprise structure of the project is to manage the legal addresses of the
enterprise. The following steps detail the method of managing the legal addresses:
1. Expand the task list and click on the Go To Task icon (circled in the screenshot below)
corresponding to the Manage Legal Addresses task under Define Legal Jurisdictions and
Authorities for Financials.
2. The Manage Legal Addresses page will open. To create a new legal address, click on the
Create icon (circled in the screenshot below).
3. Enter the details of the location and click on the OK button.

Fig. 17 - The ‘Manage Legal Addresses’ task

Fig. 18 - The ‘Manage Legal Addresses’ task page. The ‘Create’ icon is circled
 Fig. 19 - Creating a legal address

This tutorial will deal with Oracle Fusion Financials and how it functions. In this tutorial we look at
the creation of implementation users in Oracle Fusion.
Creating Implementation Users
Implementation users are the ones who view, access, and manage the implementation projects in the
Fusion application. To create implementation users, follow the steps detailed below:
1. Go to the required implementation project by clicking on its name from the Manage
Implementation Projects page.
2. Expand the task list and click on the Go To Task icon (circled in the screenshot below)
corresponding to the Create Implementation Users task under Define Implementation
Users.
3. The Oracle Identity Manager - Self Service window opens up. Click on the Administration
link on the top right of the page (circled in the screenshot below). Note that in order to
access this, the IT Security Manager role has to be assigned to the user.
4. The Oracle Identity Manager - Delegated Administration window will open up. Click on the
Create User under the Users section to create a new implementation user.
5. Enter the details of the implementation user: First Name, Last Name, User Type, User
Login, Password, etc.
6. Click on the magnifying glass icon (circled in the screenshot below) next to the Organisation
field to search and select the organisation of the user.
7. Use the Search field to search for the name of the organisation. From the search results,
select the required organisation’s name and click on the Add button.
8. Once all the required details of the user are entered, click on the Save button on the top
right of the area.

Fig. 1 - The required implementation project

 Fig. 2 - The ‘Create Implementation Users’ task

Fig. 3 - The ‘Oracle Identity Manager - Self Service’ window

Fig. 4 - The ‘Oracle Identity Manager - Delegated Administration’ window

 Fig. 5 - Entering the details of the implementation user to be created

Fig. 6 - Searching and selection the organisation

Assigning Roles to the User
After creating a user, roles have to be assigned to him/her. To do so, follow the steps detailed below:
1. Once the user has been created, a confirmation message will appear, along with tabs
named Attributes, Roles, Resources, Proxies, Direct Reports, and Requests. Click on the
Roles tab (circled in the screenshot below).
2. By default, the ALL USERS role will be assigned to the user. Click on the Assign button
(circled in the screenshot below) to assign further role(s) to the user.
3. As of now, the user will only be a consultant. Hence, they cannot access basic tools like
Scheduled Processes, Setup and Maintenance, Reports and Analytics, etc. Therefore, the
first role to be assigned must be the Employee role.
 Search for the Employee role using the search fields and buttons available. From the
search results, select the name of the role and click on the Add button.
4. The next roles to be added are Application Implementation Administrator, Application
Implementation Consultant, and Application Implementation Manager. Use the Assign
button again to search and select the required roles. You can use the “%” symbol as a
wildcard while searching.

To select more than one role to be assigned at once, hold the Ctrl key on your keyboard
while selecting the roles. Click on the Add button after selecting the roles.
5. Click on the Assign button again and search for “General Accountant%”. You will get a list
of roles as results.
The General Accountant role is simply a job role; this means that the user with this role
can only view the ledger pages but not any data.
In order to enable the user to view the data of the ledger, he/she has to be assigned the
appropriate data role corresponding to that ledger. These data roles are created
automatically upon creation of the ledgers themselves. Select the required ledger data role
and click on the Add button.
6. Once you are done assigning roles to the user, you can go back to the Fusion application.

Fig. 7 - After the successful creation of the user

Fig. 8 - Assigning roles to the user

Fig. 9 - Searching for the ‘Employee’ role
 Fig. 10 - Adding three roles at once
Searching for Users
In order to search for users in the system, follow the steps given below:
1. Go to the Oracle Identity Manager - Delegated Administration window as detailed in the
above mentioned steps.
2. Click on the Advanced Search - Users link under the Users section (circled in the
screenshot below).
3. Search for the required user using the fields available: User Login, First Name, Last Name,
Email, Organisation, etc. Then click on the Search button.
4. A list of users matching your search fields will be displayed in the search results below the
fields. Click on the Display Name of the required user to view their user information.

Fig. 11 - The ‘Advanced Search - Users’ link

Fig. 12 - Searching for a user

This tutorial deals with Oracle Fusion Financials and how it functions. In this tutorial we
will look at the creation and management of implementation projects in Oracle Fusion.
Manage Implementation Projects
The next step to be undertaken after selecting the offerings in Setup and Maintenance is to
manage the projects in which the offerings are being implemented, namely the implementation
projects.
What Is an Implementation Project?
An implementation project is the list of setup tasks that need to be completed to implement
selected offerings and options. First, a project is created by selecting the offerings and options
that the organisation wants to implement together. The project is then managed as a single unit
throughout the implementation lifecycle. These tasks will be assigned to users and their
completion will be tracked using the project management tools.
Therefore, an implementation is nothing but a list of tasks to be performed together that are
grouped as a unit. For example, an organisation may choose to create a single implementation
project for Human Capital Management, Financials, and Supply Chain Management. Or it may
choose to create three separate implementation projects for the three offerings.
Furthermore, there may be multiple implementation projects inside the financials
department itself. All of these implementations are at an instance level.
Creating an Implementation Project
To create an implementation project in the Fusion application, follow the steps below:
1. Go to the Manage Implementation Projects task under Implementations from the
task list on the left.
2. Click on the Create icon (circled in the screenshot below) to create a new
implementation project.
3. Enter the basic information of the implementation project: Name, Code, and Start
Date. Click on the Next button.
4. Select the offerings to be included in the implementation project by checking the
checkbox under the Include column. Once you select a main offering, its list will be
expanded, and you will have to select its options and features individually. Once
you are done selecting, click on the Save and Open Project button.
5. The created implementation project will then be opened and shown on the screen.

Fig. 1 - The ‘Manage Implementation Projects’ task

Fig. 2 - The ‘Manage Implementation Projects’ page. The Create icon is circled

Fig. 3 - Entering the basic information of the implementation project

 Fig. 4 - Selecting the offerings to be included in the implementation project
Once you are done creating an implementation project, you can continue configuring the tasks
under the project. To view the individual tasks in the implementation project, click on its name
from the main list of search results on the Manage Implementation Projects page.

Fig. 5 - The created implementation project shows up in the main list

Click on the arrow next to the name of the offering to view all of the task lists and tasks that
come under it. An asterisk (*) next to a task list name denotes that there is at least one task
under it that needs to be configured mandatorily. Most of the tasks are ordered according to the
generally accepted sequence to be followed when configuring them.

Fig. 6 - Expanding the task list to view the individual tasks

Tasks in an Implementation Project
In order to configure and run tasks after creating an implementation project, first go to the
required implementation project by clicking on its name from the Manage Implementation
Projects page.

Fig. 7 - The required implementation project

The ‘Run User and Roles Synchronization Process’ Task
Oracle Identity Management (OIM) maintains Lightweight Directory Access Protocol (LDAP)
user accounts for users of Oracle Fusion applications. OIM also stores the definitions of
abstract, job, and data roles, and holds information about roles provisioned to users. During
implementation, any existing information about users, roles, and roles provisioned to users must
be copied from the LDAP directory to the Oracle Fusion Applications tables. Once the Oracle
Fusion Applications tables are initialised with this information, it is maintained automatically.
To perform the initiation, this process should be executed.
To run this task, click on the Go to Task icon (circled in the screenshot below) next to the task
name in the task list.

Fig. 8 - The ‘Run User and Roles Synchronisation Process’ task

Click on the Submit button on the page that follows.

Fig. 9 - Submitting the ‘Run User and Roles Synchronisation Process’ task
 Fig. 10 - Confirmation of the task being submitted
To check the status of this process, go to the Scheduled Processes page under Tools in the
Navigator menu.

Fig. 11 - The ‘Scheduled Processes’ link in the Navigator menu

Click on the Refresh button (circled in the screenshot below). The status of the process will
change from Running to Completed, and finally to Succeeded upon successful completion of
the process.

Fig. 12 - The status of the process tells that it is successful

Financial Enterprise Structures and the security feature of Oracle Fusion.

Financial Enterprise Structures
One of the most critical decisions for any project is the financial structure. In Oracle Fusion, the financial
enterprise structure exists as depicted in the below illustration:

Fig. 1 - The financial enterprise structure with legal entities and primary ledgers
Here, the Enterprise is on top, and there can be only one enterprise for a project in Fusion.
Under the enterprise, there exist the Legal Entities. These legal entities will be associated with Primary
Ledgers. Note that there can be multiple legal entities for a single primary ledger. In such a case, each
legal entity has to be associated with a balancing segment. In case of a one-to-one relationship, the
balancing segment is optional.
 Fig. 2 - A financial enterprise structure with business units
Under the primary ledger, there will be Business Units. A business unit is an entity that performs certain
business functions. Each business unit will have Inventory Organisations associated with it.

Fig. 3 - The structure of a primary ledger

As seen in the above chart, each primary ledger has a Chart of Accounts, currency, calendar, and
accounting method associated with it. In case of any difference in those components, either a reporting
currency or a secondary ledger is created.
When creating a secondary ledger with a different currency, it cannot be done directly. First, the
secondary ledger is created with the same currency as the primary ledger. Then, a reporting currency is
created for the secondary ledger.
Business Functions
Business functions are those that are performed by a business unit. Oracle Fusion Financials has a
number of financial-related business functions available to be performed by the users, according to their
roles and duties. The various business functions related to financials that can be performed are:
Payables Invoicing
Billing and Revenue Management
Customer Payments
Service Request Management
Order Fulfillment Orchestration
Collections Management
 Materials Management
Customer Contracts Management
Project Accounting
Procurement
Requisitioning
Receiving
Expense Management
Order Capture
Sales
Marketing
Procurement Contracts Management
Incentive Compensation
Fusion Security - Roles in Fusion Applications
There are different roles available in Fusion applications. As specific roles will be able to perform only
those functions for which they have access to, this type of system enhances its security and prevents
mistakes or any unauthorised access. There are different types of roles applicable to users in Fusion:
 Duty Role (Application Roles)
Any employee of an organisation performs certain tasks (e.g. invoice creation, approval,
enquiry, etc.). These tasks are related to the employee’s duties that are a part of his/her
work. Duty Roles have certain privileges and access to these duty-related tasks.
 Job Role (External Roles)
Job Roles are collections of duty roles, or duties. For example, the person who performs
the tasks of invoice creation, invoice approval, invoice enquiry, etc. is called the Payables
Clerk, which is the employee’s designation.
 Abstract Role
Abstract Roles are roles that are not related to business activities. They can include leave
application, viewing salary, etc. which basically are self service activities for the employees.
 Data Role
Data Roles are created for job roles. These data roles are the ones which provide access
to the actual data associated with the job roles. If the appropriate data role is not assigned
to a user, he/she can only view the page for the job role, but not the data in that page.
 Data Access Set
The Data Access Set is used to control the access of users to a ledger or a specific
balancing segment. A data access set will be created automatically upon the completion of
the ledger configuration along with data roles. Further data access sets can be created to
restrict access to a particular balancing segment value or ledger set level.
Role Based Security
The following illustration depicts how the role based security in Oracle Fusion works in Fusion Financials:
 Fig. 4 - Role based security in Oracle Fusion Financials
Here, the user ‘Fred’ has the following roles associated to him: Accounts Payable Manager - US-West
(here, US-West is a business unit), Employee, and Line Manager. Each of these roles has got certain
functional privileges and data access granted to it, as depicted above.
The role Accounts Payable Manager - US-West grants Fred the following functional privileges: Manage
Payables Invoices, Apply or Unapply Payables, and Prepayments. These privileges grant Fred access to
the following data: Payables Invoices in US-West Business Unit. Similarly, the Employee and Line
Manager roles follow suit with their functional privileges and data access.

Oracle Fusion Receivables Process & Setups Part-1

Introduction
This article will helps to understands basic functionality as available in Oracle Fusion Receivable. Oracle
Fusion Receivables provides integrated functionality to perform most of day-to-day accounts receivable
operations. Receivables functionality is managed via three Overview work areas: Billing, Receivables
Balances, and Revenue Management. All three work areas provide access to general ledger account
activities, including creating accounting, creating manual journal entries, and reviewing journal entries.
Most of the functionalities available in Oracle EBS 11i/R12 are available as is and all the mandatory
setups are also similar to the setups available in 11i/R12.
Let us understand briefly about work areas-
Billing Work Area
Billing work area helps to perform tasks related to customer billing activities. Monitor and review
incomplete transactions, and approve and research pending adjustments. Use AutoInvoice to import
transactions from other systems and generate invoices and credit memos automatically according to your
requirements. You can easily review and correct AutoInvoice import errors and resubmit AutoInvoice.
Create new invoices, debit memos, credit memos, and on-account credit memos. Perform related
activities to manage your transactions: update, duplicate, credit, adjust, dispute, and preview a
transaction. You can also create a new customer record and manage existing customers from the Billing
work area.
Receivables Balances Work Area
Use the Receivables Balances work area to perform tasks related to customer payment activities and the
management of accounts receivable balances. Review actionable items, including open receipts and
receipt batches, unapplied and on-account receipts and credit memos, receipt remittance batches, and
funds transfer errors. Create receipts manually, import receipts via lockbox or spreadsheet, or create
automatic receipts. Perform related activities to manage your receipts: apply, unapply, reverse, delete;
create invoice adjustments or chargebacks during receipt application; and remit, clear, or risk eliminate
factored receipts. You can manage receipt remittances: create, modify, and approve receipt remittance
batches. You can also perform tasks related to managing accounts receivables balances, including
reconciling receivables and managing receivables accounting period statuses.
Revenue Management Work Area
Use the Revenue Management work area to perform tasks related to revenue recognition and revenue
adjustments. Run the Recognize Revenue program to generate revenue distribution records for invoices
and credit memos that use invoicing and revenue scheduling rules. Perform revenue adjustments on one
or more transactions, including scheduling and unscheduling revenue; reviewing, adding, and expiring
revenue contingencies; and transferring sales credits. You can also manage revenue policies, revenue
contingencies, and rules that assign revenue contingencies to transactions automatically.
Customer Information
From either the Billing or Receivables Balances work area, you have access to manage both customer
information and customer account activities, in summary and in detail. You can review customer account
information by a single business unit, bill-to site, or across all business units and bill-to sites. For each
customer account, you can review transactions and receipts, dispute and adjust transactions, and drill
down to current or historical customer account activity.
Oracle Fusion Receivables provides a comprehensive solution for running day-to-day accounts receivable
operations. It includes a host of services for customer billing and payment activities, revenue recognition
and adjustments, accounts receivable balances, and reconciliation to the general ledger. Oracle Fusion
Receivables introduces SmartReceipts, an industry leading automated cash application solution, and role-
based work areas that provide embedded intelligence and focused to-do lists of transactions, receipts,
and other activities requiring immediate attention. You can actively monitor transactions and drill down to
details with its sophisticated reporting tools. Oracle Fusion Receivables comes complete with Excel
integration, tagging, watch lists, collaboration, and context-sensitive embedded help.
Fusion Receivable Mandatory setups are-

1. Receivable System Options

2. Receivable Activities
3. Auto Accounting Rules
4. Receipt Classes and Methods
5. Remit To Addresses
6. Approval Limits
7. Statement Cycles

New Features in Oracle Fusion Account Receivables

1. Auto Lockbox SmartReceipts -Fusion Receivables continues to support auto lockbox but has
enhanced to apply receipts automatically using SmartReceipt.
2. Smartreceipt correctly match receipts to invoices based upon system generated
recommendations that include exception handling
3. Reduce the number of future manual receipt applications by tracking metrics related to why the
system could not automatically apply the receipt
4. SmartReceipts functionality is extended to the receipts that are created manually or uploaded
through excel Fusion Receivable (Customer Receipts)
5. SmartReceipts Manual Receipt Entry Receipt Via Spreadsheet.
6. Smart receipt uses payment information to apply receipts
7. Recommends best potential matches for exceptions
8. Recommended invoices are prioritize and displayed to user based on user defined matching
rules
9. Using calculated score, users can quickly decide which payments to apply and which exception
recommendations to use
10. AutoMatch Rule Set-uses below 4 options-

a. Minimum Weighted Threshold- Auto apply process recommends transaction for

receipt application if score exceeds for one or more transactions
b. Days of Closed Invoices Threshold- All transactions closed on or before the days
provided as threshold value
c. Combined Weighted Threshold- Auto apply process to apply receipt to a transaction
automatically
d. Customer Recommendation Threshold-Auto apply process adds customer information
to the receipt if score exceeds threshold
Excel-based Receipt Entry which helps to quickly create and update customer receipts.
Increase user’s ability to process payments and remittance data by leverage the inherent Excel
functionality, such as copy and paste. This also send spreadsheets to reviewers and approvers
Receivables to General Ledger Reconciliation- Quickly reconcile receivables to the general
ledger to close your books faster
Ensure receivables activity is properly captured and reflected in the financial results
Exceptions are automatically identified
Reports expand account balance information from summarized to detail data for optimal
reconciliations
Quickly investigate differences in balances with drill downs
Increase productivity and efficiency by uploading customer data through the simple and easy-to-
use spreadsheet template. You can quickly enter customer data, including any additional
attributes about the customer, upload the data, monitor the upload status, and perform error
correction from a spreadsheet
Increase operational efficiency and expand country coverage by allowing automatic reversal of
receipts that cannot be processed by the bank due to issues either with the receipt or the
receipt transmission
 Streamline your transaction delivery process by sending your customers their printed
transactions using e-mail
Increase operational efficiency by centrally processing customer payments across business
units when operating in a shared services environment
Oracle Fusion Receivables provides a comprehensive solution to manage the entire lifecycle of
bills receivable: creation, acceptance, remittance, maturity and risk elimination, accounting,
clearing, and history tracking
Gain better visibility into customer creditworthiness by using a public web service to perform
credit checks on demand. The public web service monitors customer creditworthiness
throughout the entire order fulfillment process: preauthorization, authorization, reauthorization,
or cancellation of existing authorizations before an order is fulfilled.

This series of articles aims to be a quick launchpad into Fusion Receivables without spending
hours going through numerous pages of user/implementation guides. We will do three
20minutes recap into Fusion Receivables starting with this first on in series.

Simply put under receivables process Invoice is generated Amount against which payment
is received & revenue recognized. However basic business process remaining the same,
Oracle Fusion Receivables provides considerable business efficiency over earlier releases.
Lets see how?

1. Bill Customer, which includes the creation and processing of invoices and billing
adjustments, as well as template-based bill presentment options
2. Manage Revenue, which includes the processing of revenue and revenue adjustments
with timely, accurate and event-based revenue recognition
3. Process Customer Payments, which includes the processing and application of
customer payments, processing of bank deposits and clearing accounts receivables
transactions, and processing refunds
4. Mange Accounts Receivable, which includes managing customer inquiries, processing
late charges and customer statements, as well as, adjusting customer balances through
automated or manual write-offs of invoices and receipts.
5. Managing Accounts Receivable also provides quick access to generating Subledger
Accounting for all accounting events, reconciling receivables to the general ledger, and
performing period close activities
6. To assist users with their daily and period-end activities, integration with Business
Intelligence Analytics and Transactional Business Intelligence provides easy-to-use
predefined reports, embedded analytics and user-configurable reporting.
• Automated creation of billing in a variety of formats to suit your company needs
• Automation of customer payment processing with new Smart Receipts engine for more
efficient cash application
• Receivables management that includes interactive reporting for quicker reconciliation
and period close cycle
• Contingency based Revenue Management
• Easy access to billing and payment information for managing customer inquiries and
performing account adjustments
Fusion Receivables can be configured to seamlessly integrate with banks and
payment processors for quicker settlement of customer payments. Oracle Business
Intelligence Analytics provides Real-time as well as data warehouse based analytics
embedded within the application.

Business process Vs Set-up in Fusion Receivables

Each detailed business process carries its own setup activities. However, Define Common
Accounts Receivable Configuration and Define Subledger Accounting Rules cross all four of
the Receivables detailed business processes. Fusion setups are accessible via Functional
Setup Manager (FSM) Receivables setups available as part of Financials offering
Various roles that can perform Receivables business activities mentioned above are defined
in oracle fusion are as follows, these roles inherit necessary access to perform necessary
activities

There are seven configuration (+ONE for autoinvoice) tasks necessary to create an
operational Receivables environment, Perform these seven tasks in the order indicated:
Set Receivables System Options: Set Receivables system options to customize your
Receivables environment. During Receivables setup, you specify your accounts, customer
and invoice parameters, and how the AutoInvoice and Automatic Receipts programs
operate.
Define Receivables Activities : Define receivables activities to default accounting
information for the activities you need, such as miscellaneous cash, discounts, late charges,
adjustments, and receipt write-off applications, Bank Error, Credit Card Chargeback/refund,
Earned Discount, Payment Netting
Prepayment, unearned Discount
Define Auto Accounting Rules: Defining Auto Accounting is a required configuration task
for processing customer billing.
Define Auto Accounting to specify how you want Receivables to determine the default
general ledger accounts for transactions. Receivables creates default accounts for revenue,
receivable, freight, tax, unearned revenue, unbilled receivables, late charges, and
AutoInvoice clearing (suspense) accounts using this information.
Define Receipt Classes and Methods Defining receipt classes and receipt methods is a
required configuration task for processing customer payments. Receipt classes determine
the required processing steps for receipts to which you assign receipt methods with this
class. These steps include confirmation, remittance, and clearance. Receipt methods
specify accounting for receipt entries and applications, determine customer remittance bank
account information, and configure automatic receipt processing and fund transfer error
handling.
Define Remit-to Addresses Define remit-to addresses to let your customers know where
to send payment for open receivables. Receivables uses the addresses to provide default
remit-to information when you enter transactions. You must provide a remit-to address to
complete a transaction. If you use AutoInvoice, but have not defined a remit-to address for a
particular customer site, AutoInvoice rejects all transactions for which it could not determine
a remit-to address.
Define Approval Limits Define approval limits to determine whether a Receivables user
can approve adjustments or credit memo requests. You define approval limits by document
type, amount, reason code, and currency.
Define Statement Cycles Define statement cycles to control when you create customer
statements. You assign statement cycles to customer profiles

Setting Up Data for AutoInvoice To ensure that the AutoInvoice process works properly,
you need to prepare Oracle Fusion Receivables for any new data that you want to import. If
your original system uses any setup data which is not yet defined in Receivables, you must
define this data within Receivables before using AutoInvoice. There are these points to
consider when setting up data for AutoInvoice:
1 Data Checklist Ensure that you have set up and updated the appropriate records in
Receivables and related applications.Add or update this setup data:
• Add or import customers, if your original system contains data for customers that are not
yet defined in Receivables.
• Add units of measure, if your original system uses units of measure not yet defined.
• Add or update in Oracle Fusion General Ledger this data:
• Currencies, if your original system uses currencies not yet defined.
• Accounting flexfield segment values, if your original system uses values not yet defined.
• Add or update in Oracle Fusion Tax this tax data:
• Tax rates assigned to tax rate codes that are not yet defined.
• Tax rates associated with products shipped to specific locations.
• Full or partial customer and item tax exemptions.
• Add or update these Receivables lookup codes:
• Free on Board (FOB) lookup codes, if your original system uses FOB point codes not yet
defined.
• Freight carrier lookup codes.
• Add or update this Receivables data:
• AutoAccounting (This is a required setup to use AutoInvoice)
• Payment terms
• Transaction types
• Transaction sources
• Salespersons
• Revenue scheduling rules
2 AutoInvoice Setup
3 Transaction Flexfield
Fusion Receivables with inherent integration with Fusion Subledger Accounting
provides accounting engine that allows organizations to establish their own accounting rules
and procedures as well as supports multiple accounting representations and currency
treatments. This integration enables an organization to support multiple geography and
reporting requirements with little to no additional effort.

Receivables have defined the event classes. An event class is equivalent to a Receivables
document such as Invoice or Credit Memo. For each event class, we have event types. For
all event classes, with the exception of event class Receipt event type Create and Update is
provided. An accounting event for an AR invoice, for example, would be the creation or
adjustment of the invoice. Similarly, for an AR receipt, accounting events would be the
creation, application, or reversal of the receipt. Any time one of these actions is taken on a
receipt transaction, an accounting event will be created. Based on the rule setup, there
may or may not be a resulting journal entry

You can update auto accounting setups under setup & maintenance as below
Quick Process steps after Fusion Receivables setups are done
1 Create Customer
2 Bill Customer/Create Invoice

3 Print Bills using Standard Pre-Defined Templates

Use Pre-defined templates for your bill presentment with minimum personalization
• Update with your company logo
• Verify the default attributes to be included in the printed document
• Set your template as a Default Template in BI Publisher
• List of pre-defined templates
• Default Invoice Template
• Default Credit Memo Template
• Default Debit Memo Template
• Default Chargeback Template
• Default Balance Forward Bill Detail Template
• Default Balance Forward Bill Summary Template
As & when needed Retrieve Printed Invoice in Application

No more following up with IT support on invoicing errors, business users can Correct Auto
invoice errors by downloading error data in excel, correct errors & upload corrected
invoices!
4 Receive & Apply Payments
• Lockbox eliminates manual data entry by automatically processing receipts that are
sent directly to the bank. Specify how this information is transmitted and how Receivables
validates the data and creates receipt batches. Lockbox can also automatically identify the
customer who remitted the receipt and determine how to apply the receipts to the
customer's outstanding debit items.
• Receipts via Spreadsheet integrates with Microsoft Excel to efficiently capture Receipts
data while offline in a field office. The spreadsheet can be later uploaded to the system to
create receipt batches.
• Intuitive and efficient manual standard receipt entry uses sophisticated defaulting to
reduce the amount of data that needs to be entered to create a receipt. It also leverages the
enhancements to the automatic receipt application engine to immediately match the entered
remittance advice information to open receivables transactions and apply the receipts.
• Automatic Receipts integrates with Oracle Fusion Payments to provide convenient
processing and management of Credit Card and Bank Account Transfer payments. It
automatically generates receipts for customers with whom you have predefined agreements
that let you collect payments on time by transferring funds from the customer's bank
account to yours on the receipt maturity date.
Most Frequently used method like lockbox are easier to manage as users can correct errors
using ADFdi integration & even create receipts using spreadsheet.
• multiple lockbox transmission file formats
• error correction via spreadsheet for ease of use
• The SmartReceipts application engine to increase the hit rate based on remittance
advice from your customer, and also factors related to customer payment history when
remittance advice is missing or incorrect

Leverage the new SmartReceipts engine

• Increases the receipt application hit rate based on customer remittance advice
• Generates recommendations based on receipt reference information when receipt
cannot be automatically applied

Receipt Remittance Reference information can be uploaded for an existing receipt in

Receivables via excel upload. The Excel integration leverages the “Apply Receipts using
AutoMatch” process to automatically match and apply receipts to invoices based on the
uploaded remittance advice information, drastically reducing the time required for manual
data entry and receipt application
Automatic Receipts: Errors Needing Manual Correction Pushed for User Review

Key Differences from R12

 Business Process Operational Configuration

Bill Customers Role based Workarea Business Unit

AutoInvoice correction using Fusion Setup Manager (FSM)
ADFdi

Manage Revenue Role based Workarea Business Unit

Mass Revenue Adjustments Fusion Setup Manager (FSM)

Process Customer Role based Workarea AutoMatch Rule Set

Payments SmartReceipts Application Exception Rule Set
Create Receipt Batch using Receivables Specialist
ADFdi Assignment Rules
Receipt Assignment Fusion Setup Manager (FSM)

Manage Accounts Review Customer Account Business Unit

Receivable Balances Details Fusion Setup Manager (FSM)

Simply put, under receivables process Invoice is generated Amount against which payment
is received & revenue recognized. However basic business process remaining the same,
Oracle Fusion Receivables provides considerable business efficiency over earlier releases.
Let’s see how, where& exactly how Fusion Receivables simplifies processes to enable
business focus on more important issues like Making calls to resolve Delinquencies,
Customer Queries.... rather than worrying about records stuck in Autoinvoice.

Continuing from Previous article we discussed about overall Receivables process, Setups
to create an Invoice & apply receipt to it. In this article we will continue with details of setups
and more details of invoicing, receipts, access & setups related to accounting in
Receivables

& Continue discussing late charges, revenue management, creating write-offs & finally
posting Receivables journals to Oracle Fusion General ledger in following article.

Job Roles and Duty Roles for Performing Receivables Activities

The pre-defined job roles have the following duty roles associated to them
Custom Security needs can be met by managing the duty role assignments

To enable a Business Unit to process receivables, enable the following business functions.
•Billing and Revenue Management
•Customer Payments
•Assign your business unit to one primary ledger and a default legal entity This assignment
is mandatory for business units with business functions that produce financial transactions .
Determination of Business Units,Ledger& LE on Receivable transactions is derived
by

In additional to the ability to schedule creating accounting process, you can run accounting on-
line after you complete the invoice and view the generated accounting on-line from the
invoice.You can create accounting an view accounting from Review Transaction page and
Manage Transaction page. Under the Action menu, you will see the following account related
actions:
•Account and Post to Ledger
•Account in Draft
View Accounting

•Receivables generate distributions based on AutoAccounting rules

•Receivables pass distributions to SLA
•SLA generates accounting entries based subledger accounting rule
•General Ledger Imports subledger accounting entries to create journal entries
General Ledger post journal entries to update account balances
Following sources are used by autoaccounting to derive the accounting on transactions. The
available sources are based on the account type. For each segment in your Accounting
Flexfield, enter either the source name that you want Receivables to use to get information or a
constant value.

Here is an example of how AutoAccounting uses the sources

(a)Below is an example of “Invoice” . In Oracle Fusion Receivables , AutoAccounting

generates the distributions which are used as default to generate the final accounting.
Given the predefined accounting rules, this is the accrual accounting for Invoice. The default
accounting in Fusion is at the detail level, showing the final accounting. However, we set
transfer to GL in ‘summary’ mode, resulting in one receivables entry per invoice.
(b)example of “Line Adjustment” prorated over Lines.
Given the Receivables predefined rules, this is the accrual accounting for Adjustment. The
default accounting in Fusion results in one receivables entry for each revenue line. However,
we set transfer to GL in ‘summary’ mode, resulting in one receivables entry per invoice.

Setting up Auto-Accounting as explained above is completed on following screen

Various Receivables transactions can be either created manually or through automated process
& can also be imported from external systems or via excel spreadsheets

The upstream application sends the data to the interface table.

AutoInvoice then selects data from the interface tables and creates transactions in Oracle
Fusion Receivables. Receivables rejects transactions with invalid information to ensure the
integrity of the data.
The invalid data (exceptions) are pushed to users for correction. Users use the Fusion Desktop
Excel Integration , which is an excel interface that is more familiar, to review data and correct
the error using better user interface and faster turn around.
You can expedite Receivables entries by using default values as defined below
Use grouping rule to group imported lines to invoice based on specific business
needs.
Out of box, Receivables provides the DEFAULT grouping rule which contains all of the
mandatory attributes. You can add optional attributes to the DEFAULT grouping rule to
create new grouping rules. You cannot delete any mandatory attributes from a grouping rule
Accounting date for invoices is derived using the following criteria
• Does a GL date exist for this invoice in the interface table?
• Does the invoice use rules?
• What is the setting of the Derive Date option for this Transaction Batch Source (Yes
or No)?
• What is the setting of the accounting date in a Closed Period option for this Transaction
Batch Source (Adjust or Reject)?
If the accounting Date in a Closed Period field for your transaction source is set to 'Reject'
and you pass a general ledger date that is in a Closed or Not Opened period, AutoInvoice
will
reject the line.
If the Accounting Date in a Closed Period field for your transaction source is set to 'Adjust'
and you pass a general ledger date that is in a Closed or Not Opened period, AutoInvoice
will change the date to an open or future enterable period.

Tax Determination for invoice lines is based on following

Tax calculations are done using Oracle Tax Module in context of receivables below are the
tasks that needs to be performed by application to derive correct tax rates for applicable
invoice lines
1. Determine Applicable Tax Regimes and Candidate Taxes
2. Determine Place of Supply and Tax Jurisdiction
3. Determine Tax Applicability
4. Determine Tax Registration
5. Determine Tax Status
6. Determine Tax Rate
7. Determine Taxable Basis
8. Calculate Taxes
Taxes are calculated at the time of saving and competing the transaction.You can update
and view taxes for the entire transaction or for each line.You access the tax details from:
1)Tax Edit icon on the Transaction
2)Edit Tax Action on the Transaction Line table

After you enter all required information, you can complete the invoice. When you complete
an invoice, Receivables creates payment schedules based on the payment terms and
invoice date you specified and includes the invoice in the standard aging and collection
process if the transaction type has Open Receivables set to Yes.
When you complete a standard invoice, receivables will validate the following:
• The invoice must have at least one line.
• The accounting date of the invoice must be in an Open or Future period.
• The invoice sign must agree with the creation sign of the transaction type.
• The sum of distributions for each line must equal the invoice line amount.
•If the Calculate Tax field for the transaction type is set to Yes, tax is required for each line
(except lines of type Charges).
• If freight was entered for this transaction, you must specify a freight account.
• If the system option Require Salesperson is Yes, salespersons must be assigned to each
line.
• If salespeople are assigned to each line, the total revenue sales credit percentage equal
100%.
• All the activity date ranges for the setup values (for example, payment terms) must be
valid for the invoice date.
• If this transaction uses an automatic receipt method, you must enter Customer bank,
branch, and account information.
Receipts of Monies Against invoices created in Oracle Fusion Receivables
Fusion Receivables supports a variety of receipt creation methods to meet the needs of
your organization.
Receipts via Spreadsheet integrates with Microsoft Excel to efficiently capture Receipts
data while offline in a field office. The spreadsheet can be later uploaded to the system to
create receipt batches.

Lockbox eliminates manual data entry by automatically processing receipts that are sent
directly to the bank including how this information is transmitted ,how Receivables validates
the data, creates receipt batches. Lockbox can also automatically identify customer who
remitted the receipt and determine how to apply the receipts to customer's outstanding debit
items.This feature supports:
•multiple lockbox transmission file formats
•error correction via spreadsheet for ease of use

Fusion Receivables expedites user discovery and correction of authorization and funds
capture errors if they are not automatically corrected, by pushing these errors to:

1.On Watch-list
On Receivables Balances Overview page
SmartReceipts application engine increases the hit rate based on remittance advice from
your customer, and also factors related to customer payment history when remittance
advice is missing or incorrect.Allows users to specify threshold scores above which
recommendations are generated and automatically accepted.SmartReceipts also
streamlines exception cases when the Customer has either overpaid or underpaid
Manual standard receipt entry uses sophisticated defaulting to reduce the amount of data
that needs to be entered to create a receipt. It also leverages the enhancements to the
automatic receipt application engine to immediately match the entered remittance advice
information to open receivables transactions and apply the receipts.

Automatic Receipts integrates with Oracle Fusion Payments to provide Credit Card and
Bank Account Transfer payments. It automatically generates receipts for customers with
whom you have predefined agreements that let you collect payments on time by transferring
funds from the customer's bank account to yours on the receipt maturity date.
There are few special considerations to automatic receipts that enables error free & efficient
receipt application that business needs to consider & implement.

Similar to automatic receipts below are few decisions for Automatch rule set to optimize
receipts
Previous articles we discussed about overall Receivables process,Setups to create an
Invoice & apply receipt to it.In this article we will continue with details of setups and more
details around late charges,access& setups related to accounting in Receivables &upto
posting Receivables journals to Oracle Fusion General ledger.
Continuing from last article below is summary of Receipt setups for various receipt
application we discussed,simple table quickly identifies what setup is required is for each type
of receipt creation method.
When creating the receipt classes and methods, there are four primary considerations.
First,determine whether receipts will be created manually, via a lockbox or through
automatic receipt processing.
•When creating receipts manually or via lockbox, the receipt class Creation Method should be
Manual.
•When using automatic receipts, the Creation Method should be Automatic.
Second, determine which bank accounts are used for remitting receipts.
•Payments received in the form of checks or electronic payments, such as, bank account
transfer or credit card payment, need to be remitted to the bank. These payments can be
remitted directly or factored in return for cash.
Cash payments do not need to be remitted to the bank.
•It is possible to enter several remittance bank accounts for each receipt method. However, one
remittance bank account must be designated as the primary bank account for each currency
used.
Third, determine the minimum receipt amount before remitting a receipts to the bank.
Receivables allows the deploying company to control the minimum receipt amount allowed to be
remitted to a bank account by setting a minimum threshold.
Lastly, Payments that are remitted to the bank must be cleared before they are available as
cash. Users can choose to clear receipts either by using Receivables’ automatic clearing
process or by Oracle Fusion Cash Management’s bank statement reconciliation.
AutoMatch and Application Exception Rules
As a simple thumb rule you should Set conservative thresholds and then test.
Start with:High values for Customer Recommendation, Threshold Combined Weighted
Threshold and Days of Closed Invoices Threshold.Low value for Minimum Match Threshold
Review Customer Account Activities task is performed via the Review Customer Account
Details screen which is available on User’s homepage after login

Users can use standard reports to analyze customer account & then take relevant actions
Late Charges Generate late charges for overdue transactions and/or late payments.
Include late payments if you want to consider additional charges when the late payment is
applied.
Use flat, simple, or compound interest rate calculation to generate interest charges for the
transaction depending on the complexity of the interest rate requirements.
Use fixed amounts for late charge calculations if a simplified fixed amount will suffice

Use Interest Tiers and Charge Schedules to enable different interest rate charges
Interest Tiers are used to enable different interest rate charges to the customer based on how
late the invoice is overdue and how late the payment is
Use Fusion Revenue Management to
-Revenue Recognition using invoicing and revenue scheduling rules
-Crediting of invoices with rules
-Cost of Goods Sold and revenue matching
-Mass Revenue adjustments
-Access to Revenue setups directly from the Revenue Management work area.
Use pre-defined invoicing rules to support receivables recognition
In Advance: Recognizes receivable amount immediately
In Arrears: Recognizes the receivable amount at the end of schedule
Close Receivables Accounting PeriodUse following flow to track Month-End processing
which is to ensure all pending transactions are completed & re-conciled before closing
accounting period in Fusion receivables.

Use below three Work Areas below & run following reports to review and manage
actionable items to process before closing your period:
•Billing Work Area
•Receivables Balances Work Area
•Revenue Adjustments
Month-End Reports
1.Receivables to General Ledger Reconciliation Report
2.Extract Reconciliation Data for Receivables to General Ledger
3.Bad Debt Provision Report
4.Customer Balance Revaluation Report
5.Document Number Audit Report
6.Invoices Posted to Suspense report
7.Potential Reconciling Items Report
8.Projected Gains and Losses Report
9.Receivables Aging by General Ledger Account Report
10.Receivables Open Items Revaluation Report
11.Registers
12.Revaluation Reports
13.Exchange gain or loss Reports

Maintain Receivables Period status through common subledger period close

management

Depending on business decision to keep historical data,Purge old extract files based on
number of days set in the Receivables Profile Option: Receivables Reconciliation Data
Purge Frequency

Job Roles & Associated Duty Roles for Month End Processing
To summarize,in these three articles we discussed setups & process to create invoices,
receipts,latecharges,credit memo & other possible transactions in Fusion receivables & then
to recognize revenue & close period to account for transaction described in these three
articles.
For benefit of readers who are new to this functionality below are some key
terms/Definitions
What is Transaction Source?Use transaction types to define the accounting for the debit memos, credit memos,
on-account credits, chargebacks, commitments, and invoices you create in Receivables. Transaction types also determine
whether your transaction entries update your customers' balances and whether Receivables posts these transactions to your
general ledger.
What is Auto Invoice?A) Autoinvoice is a tool used to import and validate transaction data from other financial
systems and create invoices, debit-memos, credit memos, and on account credits in Oracle receivables. Using Custom
Feeder programs transaction data is imported into the autoinvoice interface tables.
Autoinvoice interface program then selects data from interface tables and creates transactions in receivables (Populates
receivable base tables) . Transactions with invalid information are rejected by receivables and are stored in
RA_INTERFACE_ERRORS_ALL interface table.
What is AutoAccounting?A) By defining AutoAccounting we specify how the receivables should determine the
general ledger accounts for transactions manually entered or imported using Autoinvoice. Receivables automatically creates
default accounts(Accounting Flex field values) for revenue, tax, freight, financial charge, unbilled receivable, and unearned
revenue accounts using the AutoAccounting information.
What are Autocashrules?A) Autocash rules are used to determine how to apply the receipts to the customers
outstanding debit items. Autocash Rule Sets are used to determine the sequence of Autocash rules that Post Quickcash
uses to update the customers account balances.
What are Grouping Rules? (Used by Autoinvoice)
A) Grouping rules specify the attributes that must be identical for lines to appear on the same transaction. After the grouping
rules are defined autoinvoice uses them to group revenues and credit transactions into invoices debit memos, and credit
memos.
What are Line Ordering Rules? (Used by Autoinvoice)A) Line ordering rules are used to order transaction
lines when grouping the transactions into invoices, debit memos and credit memos by autoinvoice program. For instance if
transactions are being imported from oracle order management , and an invoice line ordering rule for sales_order _line is
created then the invoice lists the lines in the same order of lines in sales order.
What are Transaction types? Types of Transactions in AR?
A) Transaction types are used to define accounting for different transactions such as Debit Memo, Credit Memo, On-
Account Credits, Charge Backs, Commitments and invoices.
What are the available Key Flex Fields in Oracle Receivables?A) Sales Tax Location Flex field, It’s
used for sales tax calculations.
Territory Flex field is used for capturing address information
What is Autolockbox?
A) Auto lockbox is a service that commercial banks offer corporate customers to enable them to out source their account
receivable payment processing. Auto lockbox can also be used to transfer receivables from previous accounting systems
into current receivables. It eliminates manual data entry by automatically processing receipts that are sent directly to banks.
It involves three steps
1 Import (Formats data from bank file and populates the Interface Table),
2 Validation(Validates the data and then Populates data into Interim Tables),
3 Post Quick Cash(Applies Receipts and updates Balances in BaseTables).
What is Transmission Format?
A) Transmission Format specifies how data in the lockbox bank file should be organized such that it can be successfully
imported into receivables interface tables. Example, Default, Convert, Cross Currency, Zengen are some of the standard
formats provided by oracle.
What are the different statuses for Receipts?
A) Unidentified – Lack of Customer Information
Unapplied – Lack of Transaction/Invoice specific information (Ex- Invoice Number)
Applied – When all the required information is provided.
On-Account, Non-Sufficient Funds, Stop Payment, and Reversed receipt.

GL

Enterprise Structure in Fusion Application – a backbone of Your Financials

Implementation
The Enterprise Structures configuration deals with creating your GL structure & can be
complete manually or using Enterprise Configurator, which is an interview-based tool to
guide through the process of setting up a basic enterprise structure. By answering
questions about enterprise, the tool creates a structure of divisions, legal entities, business
units, and reference data sets that reflects your enterprise structure. Before we start looking
at details of Enterprise structure, below is the Overall process in Fusion GL which will use
the enterprise structure.

Financial enterprise structures are the entities that define the reporting, legal and business
aspects of your enterprise
Enterprise structure now has a definition & an instance to allow users define various
accounting representation.

Chart of accounts structure:

Building block of chart of accounts implementation, geared towards flexibility, minimizing
setup efforts. Defines the number of segments, segment sequence, labels and default value
set for each segment.

Chart of accounts structure instance:Also referred to as chart of accounts,Multiple charts

of accounts can share the same structure, but each may be customized differently to fit your
transactional and reporting requirements: Value set,
Account hierarchy, Dynamic combination creation

**Assuming reader is already familiar of it We will not go in much details of COA, Balancing
segments, Calendars, Accounting method definitions & their setups.
To streamline your chart of accounts implementation, follow the steps below:
Enterprise Structure can also be created using spreadsheet uploads enabling Functional
users to use excel spreadsheet to model, discuss & finalize the structure before the setups
are loaded into Oracle.

(1) Under the Financials offering locate the Define Chart of Accounts task grouping and
navigate to the tasks needed to successfully bring your chart of accounts implementation
into completion
Define Common Applications Configuration for Financials
Define Enterprise Structures for Financials
Define Financial Reporting Structures
Define Chart of Accounts
Manage Charts of Accounts
Manage Chart of Accounts Value Sets
Manage Account Hierarchies
Publish Account Hierarchies
Manage Account Combinations
Manage Segment Value Security Rules
Manage Cross-Validation Rules
Manage Chart of Accounts Mappings (1)

Manage Chart of Accounts Synchronization with DRM

Maintain Segment Value Attributes (2)

(2) Under the Financials offering locate the Define Calendars task grouping and navigate
to the tasks needed to successfully bring your calendars’ implementation into completion
Define Common Applications Configuration for Financials
Define Enterprise Structures for Financials
Define Financial Reporting Structures
Define Calendars
Manage Accounting Calendars
Manage Transaction Calendars
(3) Under the Financials offering locate the Define Currencies task grouping and navigate
to the tasks needed to successfully bring your currencies implementation into completion
Define Common Applications Configuration for Financials
Define Enterprise Structures for Financials
Define Financial Reporting Structures
Define Currencies
Manage Currencies
Manage Conversion Rate Types
Manage Daily Rates
(4) Under the Financials offering locate the task groupings below and navigate to the tasks
needed to successfully bring your legal entity setup into completion
Define Common Applications Configuration for Financials
Define Enterprise Structures for Financials
Define Legal Jurisdictions and Authorities for Financials
Manage Legal Jurisdictions
Manage Legal Authorities
Manage Legal Addresses
Define Legal Entities for Financials
Manage Legal Entities
Manage Legal Entity Registrations
Define Legal Reporting Units for Financials
Manage Legal Reporting Units
Manage Legal Reporting Unit Registrations
(5) Under the Financials offering locate the Define Accounting Configurations iterative
task list and navigate to the tasks needed to successfully bring your accounting
configuration into completion
Define Common Applications Configuration for Financials
Define Accounting Configurations
Manage Primary Ledgers
Assign Legal Entities
Specify Ledger Options
Assign Balancing Segment Values to Legal Entities
Assign Balancing Segment Values to Ledger
Manage Reporting Currencies
Define Secondary Ledgers
Manage Secondary Ledgers
Specify Ledger Options
Complete Primary to Secondary Ledger Mapping
Assign Balancing Segment Values to Legal Entities
Assign Balancing Segment Values to Ledger
Manage Reporting Currencies
Review and Submit Accounting Configuration
(6) Under the Financials offering locate the Define Business Units iterative task list and
the Maintain Common Reference Objects task grouping and navigate to the tasks needed
to successfully bring your accounting configuration into completion
Define Common Applications Configuration for Financials
Define Business Units
Manage Service Provider Relationships
View Service Clients
View Available Asset Books
Specify Customer Contract Management Business Function Properties
Specify Supplier Contract Management Business Function Properties
Manage Business Unit Set Assignment
Assign Business Unit Business Function
Configure Procurement Business Function
Configure Requisitioning Business Function
Maintain Common Reference Objects
Define Reference Data Sharing
Manage Reference Data Sets
Manage Set Assignments for Set Determinant Type
Rapid implementation is a way to configure the Oracle Fusion Financial Enterprise and
Financial Reporting Structures quickly using sheets in a workbook to upload lists of
companies (legal entities), ledgers, business units, chart of account values, and other
similar data. Once the sheets have been uploaded, the application creates your ledger,
business unit, and other components.
Begin by downloading the Rapid Implementation for General Ledger workbook using the
Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet
task on the Setup and Maintenance work area
1. Enter the data into the sheets.
2. Upload the xml files generated from the sheets.
3. Run the deployment process to finalize the chart of accounts configuration.
4. Upload the XML files generated from the sheets for the rest of the configuration
For Example following is a spreasheet example which can be deployed using process
above.

Differences from R12

 Related Concepts
Balance cubes which are Multidimensional structures that store your financial balances
and enable high-speed, interactive financial reporting and analysis
• Balances cubes pre-aggregate your balances at every possible point of summarization,
thus ensuring immediate access to financial data and obviating the need for an external
data warehouse for financial reporting
 A balances cube is uniquely identified by the combination of a chart of accounts and
an accounting calendar. Average balances are tracked in a separate balances cube
 Completing an accounting configuration launches a process to create or update
balances cubes
 If the combination of a ledger’s chart of accounts and calendar is new, the system
creates a new balances cube. If your accounting configuration contains an average
balance enabled ledger, an additional average balances cube is created
 If the combination of a ledger’s chart of accounts and calendar already exists, the
system simply adds the ledger(s) to the corresponding balances cube
 Balances in the cubes are automatically maintained by the following general ledger
processes: posting, open period and translation

Oracle Hyperion Data Relationship Management (DRM) is a data model-agnostic master

data management solution that enables financial and analytical master data management.
It can be used to synchronize charts of accounts values and hierarchies across multiple
EBS and Fusion instances. Oracle provides integration between Hyperion DRM both the
EBS General Ledger and the Fusion Accounting Hub. Integration between Oracle Fusion
Accounting Hub and DRM provides the ability to synchronize charts of accounts values and
hierarchies across multiple EBS and Fusion instances. Customers can maintain charts of
accounts values and hierarchies centrally in a single application, DRM, and then propagate
updates to multiple E-Business Suite (EBS) and/or Fusion instances.

Define Accounting configuration of Enterprise Structure for Procurement in Fusion

Legal entities are discrete business units characterized by the legal environment in which they operate.
The legal environment dictates how the legal entity should perform its financial, legal, and management
reporting. Legal entities generally have the right to own property and the obligation to comply with labor
laws for their country. They also have the responsibility to account for themselves and present financial
statements and reports to company regulators, taxation authorities, and other stakeholders according to
rules specified in the relevant legislation and applicable accounting standards. During setup, legal entities
are assigned to the accounting configuration, which includes all ledgers, primary and secondary.
Setup are listed as follows :
1) Manage Primary Ledgers
2) Specify ledger Options
3) Review and submit accounting Configurations
Navigate to Setup and Maintenance
Designing Account Hierarchies in Oracle Fusion Application- Part 1

Objective:
In this training article we will understand what account hierarchies are and why we require those. In the
subsequent articles we will learn how to design Account hierarchies in Oracle Fusion applications step by
step. We will also discuss the recommendations and best practices followed for designing the same.

What are account hierarchies? :

We need to create account hierarchies in order to reflect managerial, legal or geographical relationships
between the value set values. The financial balances are pre-aggregated at each parent level in the
hierarchy, thus allowing fast and robust account inquiry and drill. An organization operating at multiple
levels always need a track on the account balances at each level for various managerial purposes. Say
for example a company has multiple sales departments selling IPAD, IPHONE, laptop, etc at various
geographic locations. The top level management may not be interested on sales at granular level. They
want to track the overall sales which the company has registered. In that case we need account
hierarchy. Again in the said company a regional manager for a particular region responsible for IPAD and
IPHONE only would be generating report from only two divisions operating in the particular allocated
region using account hierarchies. In a nutshell we use account hierarchies to track the figures country
wise, department wise, regional wise, territory wise, product wise and so on using Account hierarchies.
Why we create Account Hierarchies? :
Account hierarchies can be created for various requirements-
 Creating multiple hierarchies for different purposes e.g. define three different hierarchies to be used
for each chart of accounts segment that has roll ups, each for a particular purpose.
 Hierarchies for financial reporting. It must be published to Essbase cubes. Child values in these
hierarchies cannot roll up to different parents within a hierarchy as this functionality is not support
when publishing such hierarchies to Essbase.
 Hierarchies for allocations. It must be published to Essbase cubes. Used with Allocation Manager
in creating allocation rules.
 Hierarchies for cross-validation rules, revaluation and chart of accounts mapping :
a) Created within the same hierarchy and must be associated with a chart of accounts instance.
b) Only associate one hierarchy with a chart of accounts instance, per segment
c) Such hierarchies can have the same child to roll up to different parents.
d) Do not publish to the Essbase cube since multiple child assignments are not supported in the Essbase
cube.

How many hierarchies should we define? :

Hierarchies are built on top of value set values. We can define as many as we want per value set.
However the best practice is to creating different hierarchies for trees that serve different business
purposes (e.g. management versus geographical hierarchy), and within each hierarchy define date-
effective versions to reflect changes over time.
Account hierarchies:
We can perform the following task-
 Create account hierarchies (trees) to identify managerial, legal or geographical relationships
between the value set values. A segment in the chart of account can have multiple hierarchies and
each hierarchy can have multiple versions.
 Define date effective tree versions to reflect organizational changes within each hierarchy over
time.
 Publish multiple hierarchies to balances cubes to allow for financial reporting and analysis of past,
present or future data.

Profile Options in Fusion Application- Part 2

In part -2 of this training article on Profile Options, we will understand how to Plan Profile Options,
Configure Profile Options and Organize Profile Options in Categories

Profile Option Hierarchies and Levels

Application developers specify at which hierarchy level a profile option is enabled in the system. The
predefined profile option hierarchy levels are site, product, and user. The hierarchy levels specified in the
profile option definition determine the context in which a profile option value may be set. If the profile
option value at a particular level is updatable, an administrator can update the profile option value for that
context.
A profile option may be enabled at any or all hierarchy levels. When enabled at all levels, the predefined
ordering of profile option hierarchy levels gives precedence to the values that are set at the user level
over values set at the product and site levels, and precedence to values set at the product level to values
set at the site level. If there is no value for the current user, then the product value applies. If there is no
value for the user or product, then the site value applies.

Below table shows the predefined profile option hierarchy and ordering.
We can configure updatable values for profile options at one or more levels depending on which levels
are enabled in the profile option definition. When a profile is set at more than one level, higher levels of
specificity override lower levels of specificity.
In the example, if the currency setting for the site is UK pounds sterling, but the Financials division works
in the Netherlands using the Euro, a manager in the US can override that product level setting at the user
level to use US dollars when accessing Financials applications. In another example, if a profile option
called Printer is set only at the site and product levels. When a user logs in, the Printer profile option
assumes the value set at the product level, since it is the highest level setting for the profile.
The profile option values specified at the site-level work as defaults until profile option values are
specified at the other levels.

Key Considerations while Planning Profile Options:

Plan profile options before defining and configuring them. The following aspects will assist in better
planning on how to manage profile options.
• Profile option tasks
• Before creating a profile option
• Profile options data model

Profile Option Tasks

Users may be able to set their own profile options, depending on settings in the profile option definition.
However, not all profile options are visible to end users, and some profile options, while visible, may not
be updated by end users. The following table lists tasks and considerations relevant to planning profile
options.
Before Creating a Profile Option
Profile options are best defined for managing configuration data centrally and influencing the behavior of
applications. If the purpose of a profile option setting is specific to a piece of data (typically setup data), it
is best implemented as an attribute of that data.
Do not use profile options for behavior that is not configurable. Profile options exist independent of role.
Do not use profile options to implement function security. For example, an application should not check
for a profile option value set to yes to provide access to a page. Do not use profile options to implement
data security, such as a profile option value that must be set to a specific value to provide view access to
an entity. Do not use profile options to capture a dynamic system states, such as data stored in a
temporary table. Use Global Variables for temporary states instead. Evaluate if there is a genuine need
before creating a profile option. Do not force users to make a decision about an aspect of their application
use that is of no
Concern. Evaluating need includes looking for duplicate or similar profile options, even in other products,
before creating a new one. For example, you do not need multiple profile options to choose a preferred
currency.

Profile Options Data Model

The profile option data model illustrates the relationships among profile option elements. The figure
shows the data model of profile option entities.
Configuring a Profile Option
A profile option definition includes information about the owning application and module in the application
taxonomy. A start or end date, or both may limit when a profile option is active. The profile option
definition may include an SQL validation statement that determines which values are valid, and the
hierarchy levels at which the profile option is enabled and updatable.
To be visible to users, a profile option must be user enabled. We can also allow user updates of the
profile option, which means users can make changes to the validation and the profile option level
information. Profile option levels specify at which context level profile values may be enabled or updated.
Profile options should only be enabled for context levels that are appropriate for that profile option. For
example, a profile option indicating a global configuration setting should not be enabled at the user level,
if users cannot choose a different value for that setting.

Organizing Profile Options in Categories

As a guideline, group profile options in a single category if the profile options affect the same feature, or if
an administrator would likely want to see the profile options in the results of a single search. Application
developers are responsible for the initial groupings and then administrators can make changes based on
their specific needs. Administrators can categorize profile options and then easily search on profile
options by category.

Adding New Profile Option Categories

We can add new categories or add profiles to an existing category. Also we can create a profile option
category by duplicating an existing category and editing it for a new grouping of profile options. Multiple
profile options can be added to a category. A profile option can exist in multiple categories.

Profile Option Order in a Category

Specify a profile option sequence to determine the order of profile options when queried by profile option
category.

Effect of Changes to Profile Option Values

Any change we make to a user level profile option has an immediate effect on the way applications run for
that session. When we sign in again, changes made to a user level profile options in a previous session
are still in effect. When we change profile option value at the product level and no user level values are
set, we can see the update immediately, but other users may not see the changed value until signing out
and back in. When we change a profile option value and the new value affects other users, the change
takes effect only when users sign in the next time Changes to site level profile options take effect for any
user session that is started after the setting has been changed. Changes to site or user level profile
options do not affect any user sessions that are already in progress when the change is made.

In this article we will discuss high level to-do list & tools available to take the BIG step to move to Oracle
Fusion & all that it has to offer. To minimize risk on the upgrade project Few questions any implementers
needs answering are Do we have? & Automated Migration from EBS
· Migration of data from EBS to a separately-installed instance of Fusion.
· Flexible Migration Architecture
· Well-defined Process and Packaged Migration Tools
· Well defined functional & technical migration approaches
· Pre-migration, migration and post-migration steps
· Data cleansing and validation steps at each stage
· Extensible to support customers own extensions
· Pre-packaged and pre-tested migration lowers risk & uncertainty
· Framework extensibility allows partners & customers to add value
What will be migrated?
o Set-up data will either be migrated or mapped
o Transactional data will be migrated
o Controlled schema customizations will be migrated- Example Descriptive Flex Fields
What will NOT be migrated?

o Non-controlled Schema Customization

o Business logic customization – For instance, Extension using API hooks
o User Interface customization - For instance, OA Personalization Framework customizations in e-
Business Suite will not be migrated.
o Oracle Forms personalization and customizations
o Oracle Workflows customizations
o Analytics/Report customization
 Migration offering is designed to migrate data from an on-premise installation of EBS to an on-
premise instance of Fusion
· Migrate all or nothing from a single database instance
What modules can be migrated?
Upgrade Steps Like Any Other UpgradeWould include Planning , Preparation , Down Time & Post-
Migration however in this case Pre-Migration needs to be plan more carefully to include

First step is to do Pre-Migration reporting & Readiness from Diagnostic Dashboard in EBS to obtain A
high level list of potential impacts to customer’s implementation
Subsequently run Readiness report (Summary & Detail)
• Give a summary picture per product on what will not be migrated to Fusion
• Prepares the customer for potential areas to review and take action before embarking on migration
• Detailed exception report for all products
• Provided more detailed report various entities that will be migrated and will not be migrated.
Use EBS To Fusion Data Migration offering in Fusion Setup Manager (after Completing Source data
cleanup& Validation)

Complete Domain value mapping& System preparation for data migration (Domain value maps (DVM)
are mapping tables to store mapping between source and target values), validate preparation & migration
setup,steps
Complete data migration using ODI interfaces (more details refer ODI Scenarios Orchestration)

Complete Validationusing ODI with BI Publisher reports

• Stage-wise migration provides a mechanism to validate and correct issues as they occur
• Central way of defining & executing tests/validations.
• Integrated with FSM for orchestration of these tests during migration
Complete Pre-Down time & Down Time Activities

Perform Post migration tasks & Validate Transaction , Migration using traditional methods used for
any Upgrade eg Reconcile your transactions using Spreadsheets (OTBI reports),Setup data using FSM
export import functionality etc

Oracle HRMS R12 Setups Step by Step

Open R12 Login Page

http://apps.com:8000/OA-HTML/AppsLogin
User ID: SYSADMIN
Password: SYSADMIN

Press ‘Enter’ or Click on 'Login' Button.

Select the Responsibility ‘System Administrator’.

Create a Responsibility for HRMS Manager:

Navigation :

System Administrator → Security →Responsibility →Define

The following page appears:

Press ‘F11’ and query with ‘Global Super HRMS Manager’ and press ‘Ctrl+F11’.

Create New Responsibility with the same menus and same data group with your name.
Save it and close it.

Create a user with your name

Navigation:

System Administrator → Security → User → Define

Give some name for the user and give a password.

Attach your ‘ Human Resources ’ Responsibility, ‘ Application Developer ’ and ‘ System Administrator ’.

Logout ‘SYSADMIN‘ and login with your username and password.

Press ‘Enter’ or Click on ‘Login’ Button.

As it is the first time of entering with the username system prompts you to change the password.
Give the Old password, new password and confirm the new password.
Now Press ‘Enter’ or click on ‘Submit’ Button.

The following page appears with the Responsibilities you have attached to the user.
Click on your ‘ Human Resources ’ responsibility.
Specify the 6 Key Flexfield Structures that must be defined before you can define a Business Group in
Oracle HRMS.

These are:

Job (Oracle HR)

Position (Oracle HR)
Grade (Oracle HR)
People Group (Oracle Payroll)
Cost Allocation (Oracle Payroll)
Competency Flexfield (Oracle HR)
Specify your requirements for the Key Flexfields specified above. The specification must include the
following details for each Key Flexfield:

The Structure Name and the number of Segments

The Flexfield Segment Names, Order, Validation Options and Qualifiers
The Flexfield Value Sets to be used and any lists of values

The sequence of implementation for each Flexfield is as follows:

Define Key Flexfield Segments

Define Flexfield Segment Values
Define Flexfield Value Sets
Define Key Flexfield Cross-Validation Rules
Define Key Flexfield Aliases
Freeze and Compile Key Flexfield Structure
Populate Flexfield value sets and list of values

Navigation:

System Administrator → Application → FlexField → Key → Segments

Flex field Qualifiers are mandatory for Competence Flex field ( Human Resources) and Cost Allocation
(Pay Roll).
The important point which must do while defining flex fields is to Freeze and compile each and every
Flex Fields after defining segments for it.

Human Resources :

Job Flex field :

Query with ‘Job Flexfield ’ in the ‘ Flexfield Title ’ and click ‘ Ctrl+↓ ’ in the below window displayed with
predefined flex fields to create your own Flex field for ‘Job‘.
Give a name for your Job structure and click on ‘Segments’ button.
Define the Job structure for your Organization and check the required fields based on your requirement.
Save and close the window.

Check the ‘ Freeze Flex field Definition ‘ and ‘Allow Dynamic Inserts ’ check boxes and Click on ‘Compile’
button.
Position Flex field :

Query with ‘ Position Flex field ’ in the ‘ Flex field Title ’ and click ‘ Ctrl+↓ ’ in the below window
displayed with predefined flex fields to create your own Flex field for ‘ Position ‘.

Give a name for your Position structure and click on ‘Segments’ button.
Define the Position structure for your Organization and check the required fields based on your
requirement.

Save and close the window.

Check the ‘ Freeze Flex field Definition ‘ and ‘Allow Dynamic Inserts ’ check boxes and Click on ‘Compile’
button.
Competence Flex field :
Query with ‘ Competence Flex field ’ in the ‘ Flex field Title’ and click ‘ Ctrl+↓ ’ in the below window
displayed with predefined flex fields to create your own Flex field for ‘ Competence ‘.

Give a name for your Competence structure and click on ‘Segments’ button.
Define the Competence structure for your Organization and check the required fields based on your
requirement.
Flex field Qualifiers are mandatory for ‘ Competence Flex field ’.
Click on ‘ Flex field Qualifiers ‘ button and select any one qualifier for the Competence.
Save and close the window. Check the ‘ Freeze Flex field Definition ‘ and ‘Allow Dynamic Inserts ’ check
boxes and Click on ‘Compile’ button.
Grade Flex field :

Query with ‘Grade Flex field’ in the ‘ Flex field Title ’ and click ‘ Ctrl+↓’ in the below window displayed
with predefined flex fields to create your own Flex field for ‘ Grade ‘.
Give a name for your Grade structure and click on ‘Segments’ button.
Define the Grade structure for your Organization and check the required fields based on your
requirement.
Save and close the window.
Check the ‘ Freeze Flex field Definition ‘ and ‘Allow Dynamic Inserts ’ check boxes and Click on ‘Compile’
button.
Cost Allocation Flex field :

Cost Allocation Flex Field is the interaction between Pay Roll and General Ledger . So the Segments
which we are defining in HRMS should match with the Accounting Flex Field which we define in
Financials.

Query with ‘Cost Allocation Flex field ’ in the ‘ Flex field Title ’ and click ‘ Ctrl+↓’ in the below window
displayed with predefined flex fields to create your own Flex field for ‘ Cost Allocation ‘.
Give a name for your Cost Allocation structure and click on ‘Segments’ button.
Define the Cost Allocation structure for your Organization and check the required fields based on your
requirement.
Flex field Qualifiers are mandatory for ‘ Cost Allocation Flex field ’ also.

Click on ‘ Flex field Qualifiers ‘ button and select any one qualifier for the Competence.
Save and close the window.
Check the ‘Freeze Flex field Definition ‘ and ‘Allow Dynamic Inserts’ check boxes and Click on ‘Compile’
button.
People Group Flex field :

Query with ‘People Group Flex field’ in the ‘ Flex field Title’ and click ‘ Ctrl+↓’ in the below window
displayed with predefined flex fields to create your own Flex field for ‘ People Group‘.
Give a name for your People Group structure and click on ‘Segments’ button.Define the People Group
structure for your Organization and check the required fields based on your requirement.
Save and close the window.

Check the ‘Freeze Flex field Definition’ and ‘Allow Dynamic Inserts’ check boxes and Click on ‘Compile’
button.
Business Group Creation

The next Step is to create our Business Group.

The Important thing we must not forgot while creating our business group and all our organizations is
‘Date Tracking’. The date must be checked while creating all the organizations. The dates which we give
for our organizations must be after the date which our business group is created and the dates are those
from which we want the organizations to be existed in our business group.

Note: The Date Tracking Plays a vital role in HRMS.

For that first we have to create a Location

Navigation :

HRMS Super Manager : Work Structures → Location

The next step is to attach all our flex fields which we have defined before to our business group.

Organization Classification is Important in HRMS.

Navigation :

Work Structure → Organization→Description

Click on ‘New’

Create the Business Group.

Enable the Business Group and click on ‘Others’ and give the Business Group Information.
Give a Short name for the Business group.

Select the Employee number , Applicant Number Generation, Contingent Worker Generation Fields as
either as ‘Automatic’ or ‘Manual’ based on your business group requirement.
Select and attach your grade, people group, job, costing,position, competence flexfields to your business
groups here. Select your Legislation Code and currency.
Attach ‘HR Organization’ as well so that we can attach employees in that organization.

Now Switch the Responsibility to ‘System Administrator’

Navigation :

Profile → System
Attach our business group to HR Security Profile.
Under ‘HR Cross Business Group’ Profile Select ‘yes’.
Add ‘HR with Payroll’ for ‘HR User Type’

Switch back to our HRMS Responsibility

The next step is to create organizations in our business group.

It will be better if we Select the Organization type while creating them.
But Attaching HR Organization for every Organization is must.

Create other Locations in your Business group.

Navigation :

Work Structures →Location

Now create all Divisions and Departments in your Business Group.

Navigation :

Work Structure → Organization → Description

The next step is to create a hierarchy for our organization .We must not forget date tracking.
If we want to create a new hierarchy for our organization we will give an end date for our old hierarchy.
The version name will be changed here.

Navigation :

Work Structures → Organization → Hierarchy

Give a name to the Organization Hierarchy and create the hierarchy. Select ‘Primary’ check box if it is
the primary hierarchy of the organization.
Select Version number as ‘1’ and give the starting date for the hierarchy.
Query in the ‘Organization’ window with the Business Group Name and add all the divisions an
departments as per the hierarchy in your organization in the ‘Subordinates’ window.
Job Creation :

Create the Jobs in your Business Group based in the Structure you have defined for the jobs.

Navigation :

Work Structures →Job →Description

Job is a role in our organization. Here we will create jobs which we want in our organization.
The job group will be generated automatically.But if we want a new job group we can create it by our
self. Don’t forget to check the date. After creating the jobs with the job code and job name save them.
Now click on Name field popup will display now add your desired job description on by one.
The next step is to create positions in our organization.

There r many differences between Jobs and Positions.

Jobs Positions

1) Jobs are Flexible roles 1) Positions are rigid roles

2) Jobs are independent of organization 2) Positions are dependent on organization
3) Jobs are independent of positions 3) Positions are dependent on Jobs.

4) A job may have multiple positions 4) A position will have specific job

Navigation for creating a position:

Work Structures → Position → Description

After creating the positions , create Position Hierarchy.

Navigation :

Work Structures → Position → Hierarchy

Give a name to your hierarchy. If the Hierarchy is the primary hierarchy in your organization , check the
‘Primary’ check box .Save it and version number populated for it automatically. If you are creating first
hierarchy give the ‘Date From’ . If we want to create another new hierarchy after some days , give the
‘End Date’ for the previous hierarchy which is running. Save it.
Query with Higher position name and attach the positions in the order as it is in your organization.
The next step is to assign grades to the jobs in our organization. Grades can be assigned to jobs or
positions. But Oracle prefers to assign grades to jobs.

Navigation :

Work Structures → Grade→Description

Here we will define all the grades which are available in our organization. The next step is to assign the
grades to our jobs.

Navigation :

Work Structures→Jobs→Description→ Valid Grades

The next step is to enter the details of Employees

Navigation :

People → Enter and Maintain

Enter all the details of the employee.

Creating Vacancies and Recruitment :

Navigation :

Recruitment → Requisition and Vacancy

We can create Requisitions, vacancies and openings in our organization using ‘Requisition and Vacancy’
window. A requisition can be for one or more vacancies .

Process of raising a requisition for a vacancy :

Enter the requisition and save it before beginning to define the vacancy.

Enter a name and number of openings for the vacancy.

If you advertise vacancies using SSHR, enter the vacancy category. The vacancy is automatically
advertised under this category.

Optionally enter a description and select a status.

You can select one or more assignment components to define the vacancy.

Optionally enter the name of the recruiter.

Optionally enter the budget measurement unit and value for the vacancy. The value you enter is for all
the openings for that vacancy.
Creating Recruitment Activity :

We use ‘Requirement Activity’ window to define either single recruitment activity or more.

Process of creating Recruitment Activity :

Enter the details of the recruitment activity. You can enter the name of a ’parent’ recruitment activity in
the Within Recruitment Activity region, if the activity you are defining is part of a campaign.

Choose the Recruiting For button to select one or more vacancies to associate with the activity.

Navigation :

Recruitment → Recruitment Activity

Entering the Applicant’s details : We use the ‘Applicant Quick Entry’ window to enter basic personal
information and one assignment for an application. If we want to update this information or add further
information , we use ‘People’ window.

Navigation :

Recruitment → Applicant Quick Entry

The process of recording the applicant details quickly :

Enter the applicant’s name and an identifying number recognized by the system.

Select a status for the application. By default a new application has the status Active Application (or an
equivalent user status defined on your system). All other fields are optional.

Enter information in the Further Information field if your Oracle localization team has set it up.

To enter an address, select a national address style. A window opens with the address format for the
country you select. Enter the address lines and choose OK.

The Date Received defaults to your effective date, but you can change it. This is the date the applicant’s
record will begin.

You can enter the name of the applicant’s current employer.

You can select a recruitment activity. If there is only one vacancy for the activity, the vacancy details
appear automatically.

If you select a vacancy, applicant assignment information is displayed from the vacancy record. You can
add to this information or change it. However, if you change it, the vacancy field clears.

If you do not select a vacancy, you can enter assignment information in the Vacancy Applied For region.
If you do not enter an organization, it defaults to the Business Group.
Updating Applicant Assignments by Group:

We can query and update the groups of Applicants assignments using ‘Mass Update of Applicants’
window.
Navigation :

Requisition → Mass Update Of Applicants Process of updating Applicants:

Select find from the Query menu to open the Find Applications window. Enter selection criteria for the
group of applicants you want to update and choose the Find button.

Do one of the following:

If you want to update all or most of these applicant assignments, choose the Select All buttons. Then
unchecked the Mark check box for any assignments that you do not want to update.

If you want to update less than half of this group of assignments, check the Mark check box for each
assignment you want to update.

Choose the Update button.

In the Update window:

If you want to update the status of the selected assignments, select the new status.

If you want to refer these applicants to a new recruiter, select the name of the Recruiter.

Choose OK to affect the update.

Schedule Applicant Interview

Typically, you track applicant progress through a series of interviews and update the status of the
application after each interview. You can schedule these interviews and update the applicant
assignment status using the Applicant Interview window. Before you can schedule interviews, interview
types, such as First Interview, or Selection Test, must be defined as values for the Lookup

After Clicking on ‘ Update ’ button we will get the following window.

Select the status and Recruiter Name
Click on ‘Correction’ button .Then the status of the applicants who were applied will be changed to ‘First
Interview’. Process of Applicant Interview:

Select an interview type, and enter the date of the interview in the Start Date field. You can also select a
location and enter times and an end date.

If you want to associate an applicant assignment status change with the interview, enter it in the New
Status field. This creates a date tracked update to the applicant assignment. You cannot enter a status
when:

There are future changes to the assignment

The interview date is the date when the active application status began

You are updating an existing interview record.

Follow the same process till we give the ‘Offer’ to the applicants to hire them and the applicant may
accept or reject it. If the applicant accepts the offer the next step is to hire the applicant as an employee.
The main point to remember here is that there must be one day difference between the day the
applicant accepts the offer from the company and hiring the applicant as employee.

Posted by MujahidShahaniat 6:54 AM

Develop a form using form developer and register w...

Script/ Auto job to kill inactive sessions for mor...

Create New Report and Registration with Oracle App...

There are no valid navigations for this responsibi...

Oracle HRMS R12 Setups Step by Step

Step by step learn SQL (SQL for Non Technical)