Monthly Archives: September 2017

Oracle Fusion Cash Management – Bank Setup

This tutorial deals with Banking configuration and contains the following:

  1. Bank, Branch, and Account Component
  2. Creating Banks
  3. Creating Branches
  4. Creating Accounts
Bank, Branch, and Account Components

In oracle fusion Banks, branches, and accounts work together to support the real world bank account model. Organization will leverage the model to define and keep track of all bank accounts in one place. In addition, oracle fusion enables the organization to grant bank account access to:

  • multiple business unit
  • multiple business functions
  • multiple users

The above model and functionalities would be leverage by the organization to eliminate the redundant duplicate bank accounts assigned to different business units, when different business units are sharing the same bank accounts.

Creating Banks

Once the organization enterprise structure is ready, the banks and respective accounts can be created. You will define the internal bank account details for your organization and depends on the business functions enabled, these bank accounts are debited when payments are made to the third parties and credited when payments are received from the third parties, on behalf of the organization.

To create banks, navigate to Setup and Maintenance in the FSM and search for Manage Banks


Click on Manage Banks setup task to open the Bank page


Click on Actions drop-down and click on Create Bank to create a new bank for your organization


Enter the Bank details for your bank with Country and bank name is the required field.  Enter the other fields as per your requirements.

Addresses and Contacts are optional. will create as per the organization requirements.


Click on Save and Close to complete the Bank creation process.


Create Bank Branch

Once the bank setup is complete in above step, click on Create Branch button to create the respective bank branches. Alternatively, navigate to Setup and Maintenance in the FSM and search for Manage Bank Branches.

Now, highlight the bank row for which you need to create branches and click on Create Branch button to open the bank branch creation setup page.


The Bank branch setup page will open with Bank and Country defaulted from the Bank.

Enter the Bank Branch detail with Branch name and Routing number is the required field and enter other information as per organization requirements. And, define branch addresses and contacts as needed.


Click on Save and Close to complete the Bank branch creation. You will add more branches by repeating the same steps again.

Create Bank Account

Once the bank branch setup is complete in above step, click on Create Account button to create the respective bank accounts. Alternatively, navigate to Setup and Maintenance in the FSM and search for Manage Bank Accounts.

Now, highlight the bank branch row for which you need to create accounts and click on Create Account button to open the Bank Account creation setup page.


The Bank account setup page will open with Bank and Bank Branch defaulted from the Bank branch setup.

Enter the Bank Account details and,

  • associate it with Legal Entity
  • mention the account type
  • Mention the Account use by checking the required business functions

In General Tab, enters the Cash account assign to this specific bank account, that is used in all the financial transactions.


Click on Business Unit Access tab to assign Bank account to one or many business units that are authorized to use this bank account or cash account for financial transaction purpose.

Click on Actions > Create to assign business unit/s to the bank account.


Assign the business unit intended to use this bank account. The cash account will default from the General tab.

In bottom of page, under Payment document categories by payment method section you will add or assign the Payment method and payment document category used by this bank account when making payments to creditors.

Click on OK to complete the bank account business unit access setup


Click on Save and Close to complete the bank account setup.

The above activity will complete your bank setup and organization will use particular bank and bank account in their transactions.

Oracle Fusion Pricing

In this piece of work, we will learn to create Price list in Fusion Cloud.

Pricing is a part of an Oracle Fusion Order management and is used to price items on Order lines. Oracle Fusion Pricing setup comprise below set of tasks:

  1. Customer Pricing Profile
  2. Pricing Segment
  3. Pricing Strategy
  4. Price List
  5. Pricing Strategy Assignment

Customer Pricing Profile

Customer Pricing Profile is a set of pricing-related attributes that describes a customer’s buying behavior. It is date-effective because the profile of a customer can change over time.

Pricing Segment

Pricing Segment is a grouping of customers who exhibit a common set of characteristics and similar buying behaviors. Pricing segment is used to identifies targeted groups of customers in order to apply specific pricing strategies and leverages extensibility of matrix.

Pricing Strategy

Pricing strategy is the container for the pricing rules – price lists, discount lists, shipping charge lists, cost lists, currency conversion lists, and more. Configurable process to derive the pricing strategy by using:
–Customer pricing profile
–Pricing segment
–Pricing strategy assignment

Pricing strategy defines the approach for achieving a specific goal around selling and pricing products. It contains the group of pricing rules such as price lists, cost lists, discount lists, shipping charge lists, and currency conversion list. Allow to create multiple rules determined by precedence and set business objectives and the default currency.

Price List

Price list is a defined collection of prices for items or services targeted for a set of customers for a specific period of time. Price lists are a means of capturing base list prices and other types of adjustments to arrive at the list price. It support pricing charges (price type, charge type, charge subtype), one-time charges and recurring charges.
Oracle Fusion support multiple types of price lists and identifies the item price by assigning price lists to pricing strategy. Oracle Fusion also support price list import and export capabilities

Pricing Strategy Assignment

Pricing Strategy Assignment is the assignment of pricing segment to pricing strategy. The assignment provides a mechanism to employ different pricing strategies for the same pricing segment in different selling scenarios, using extensibility of the matrix

Pricing an Order

You are the pricing administrator at Vision Corporation and responsible for implementing the pricing for your organization.

Navigate to the Pricing Administration Overview Page, by clicking the Pricing Administration work area link in the navigator.

Create Customer Pricing Profile

  • Click the Tasks panel tab
  • Click the Manage Customer Pricing Profiles link.
  • From the Actions drop-down list, select: Create


  • In the Customer Name field, enter the Customer
  • Complete a customer pricing profile by selecting values for the attributes and dates. Although these are the default values for the attributes, you can define the valid set for your implementation in the pricing lookups. This can be done through the Functional Setup Manager, through the task Manage Pricing Lookups.
  • Click Save and Close


Create Pricing Segment

  • Click the Tasks panel tab
  • Click the Manage Pricing Segment link.
  • From the Actions drop-down list, select: Create


  • Complete the pricing segment by selecting values for the attributes as defined in the customer pricing profile
  • Select Unique Pricing segment value to associate with conditions defined, along with the precedence and date defined. You can define the valid set of pricing segment values for your implementation in the pricing lookups

Create Price List

  • Click the Tasks panel tab, and select: Manage Price Lists
  • From the Actions drop-down list, select: Create


  • Enter the below field values as per requirement:
    • Name
    • Business Unit
    • Start Date
    • Price Type
    • Currency
    • Pricing Charge definition
    • Line Type
    • Calculation method
  • Click on Save and Edit, so that you can add the item and respective price


  • In Price List Lines section, click Actions drop-down list and select: Create


  • Select Item, UOM and Line type
  • Click on Create Charge to add price for item and respective UOM


  • Click on Save to save the price list


  • Once the price list is saved, you have to change the status of Price list from In Progress to Approve by clicking on the Approve button


Your Price list is ready to be used in pricing strategy for pricing an order.

Create Pricing Strategy

  • Click the Tasks panel tab
  • Click the Manage Pricing Strategy link.
  • From the Actions drop-down list, select: Create


  • Select name, business unit, currency and date to create strategy
  • Click on Save and Edit to assign price list to pricing strategy
  • In the Pricing Rules – Segment Price list section, click on select and add from the Actions drop down


  • Search the price list that you already created
  • Highlight the price list you want to add, and click on Apply and then OK


  • Once the pricing strategy is saved, you have to change the status of Pricing strategy from In Progress to Approve by clicking on the Approve button


Manage Pricing Strategy Assignment

Now, you have created all the components for the pricing to work. Only task you need to perform is to bring together all the components together by mapping Pricing segment to Pricing Strategy


Once Pricing Segment is assigned to Pricing Strategy, you pricing is ready to be used to price an order.

Supply Chain Orchestration Overview in Fusion Cloud

Supply chain orchestration provides the ability to receive supply requests from several sources operating on Oracle Cloud, to launch and manage complex business processes and perform automated change management to match supply & demand.

Below figure provide a complete view of the Supply Chain Orchestration process.

1Supply Chain Orchestration is designed to execute and manage complex, cross-product business processes such as Internal Material Transfer (IMT), back-to-back, and contract manufacturing. Supply Chain Orchestration provides the ability to:

  • Receive supply requests from several Oracle Cloud systems, such as Planning Central, Inventory Min/Max planning, and Global Order Promising (GOP)
    • For demand-specific supply requests, such as back-to-back, SCO combines the demand from Order Management and the supply suggestion from Global Order Promising to create supply documents.
  • Launch and manage complex business processes to create supply in the warehouse that would fill the anticipated demands
  • Perform automated change management to match supply to demand to ensure that quantity and fulfillment dates are automatically balanced
    • In demand-specific supply creation, Enterprises aim not to create excess supply or fall short on orders. Balancing supply with demand on order-by-order basis is important for customer satisfaction and for profitability. The automated exception management capability of Supply Chain Orchestration supports these goals.
  • Provide a 360 degree view of the supply-creation process and the relationship between the various documents of a flow

Detailed Flow of Supply Chain Orchestration Process


Supply Chain Orchestration Functional Overview

The functional components of Supply Chain Orchestration are:

  • Decomposition: Receives supply requests from other systems and invokes a predefined orchestration process to create the supply
  • Orchestration: Executes the predefined process that creates supply.
    For example, the process may call a manufacturing system to create or modify a manufacturing work order, or a purchasing system to create or change the quantity on a purchase order.
  • Business Services: Are invoked to send and receive messages from an execution system.


The overall Supply Chain Orchestration process consists of four major steps:

  1. Receive request to create supply.
  2. Determine which orchestration process to use and launch the process.
  3. Execute the steps of the orchestration process.
  4. Interact with the execution system.
Supply Chain Orchestration Process Overview


Supply Chain Orchestration (SCO) process starts on receiving a supply request. Supply request received via:

  • Planning Central – Standard Orders and Contract Manufacturing
  • Global Order Promising (GOP) and Order Management (OM) – Back-to-Back Supply process and Contract manufacturing
  • Min-Max Planning in Inventory
  • Spreadsheet upload of Internal Material Transfer (IMT) requests


Supply Chain Orchestration receives request to create supply When a supply-requesting system sends a request to Supply Chain Orchestration , the SCO process starts to process the order. The requesting systems include the following:

  • Planning Central: Releases a request for a planned order batch to Supply Chain Orchestration . A batch may include standard make, buy, or transfer orders. It may also include make orders for inventory organizations designated as contract manufacturing organizations.
  • GOP and OM: Demand data for back-to-back orders scheduled by OM are sent to Supply Chain Orchestration .
    • When an order is confirmed, GOP sends the supply data to Supply Chain Orchestration .
    • When a back-to-back order is scheduled by OM, it sends the demand data to Supply Chain Orchestration .
    • SCO matches the data received from GOP and OM, and treats them as one set of data to launch back-to-back processes. These processes could be back-to-back make, buy, or transfer processes.
  • Inventory: Inventory Min/Max planning can result in a make, buy, or transfer request to Supply Chain Orchestration .
  • Manual spreadsheet upload: You can upload transfer order data to send transfer requests to Supply Chain Orchestration .


Supply Chain Orchestration (SCO) process prepares the incoming payload to create supply.

  • Transformation of Supply request for use in execution system
  • Evaluation of execution rules
  • Apply enrichment rules
  • Assign and Launch appropriate supply creation process


After receiving a supply request, Supply Chain Orchestration next step is to prepare the incoming payload to create supply. The following steps are involved:

  1. Attribute mapping: Attributes specific to requesting system are mapped and transformed to execution system attributes. For example, the supplier ID from Planning Central is transformed to Procurement systems supplier ID.
  2. Evaluation of execution rules: Transfer requests are evaluated using the execution rules to determine if they are to be processed as a transfer order or a purchase order. If the decision is to execute it as a standard transfer, then the decision is made whether or not to route it via Order Management.
  3. Supply created: Predefined supply creation process is selected and launched.


Supply Chain Orchestration (SCO) process executes the steps of the launched supply creation process. The process includes:

  • Scheduling of the overall process to determine start and end dates of each process step
  • Identifying and responding to changes in supply or demand
  • Overall progress tracking


After a predefined supply-creation or orchestration process is selected and launched, the process steps are executed. For example, the back-to-back process includes the following steps:

  1. Application calls the procurement system to create a purchase order.
  2. Application calls the inventory system to reserve a purchase order (PO) against the demand.
  3. Supply is received in warehouse.

The orchestration process execution also includes:

  • Process Planning: At launch, the overall process schedule is calculated based on the duration of each constituent task. The start and end dates of each process step are determined.
  • Change Management: In case of changes in supply or demand, the change management system responds and makes adjustments to keep supply and demand in balance.
  • Tracking: The status and state of all execution documents are tracked.


Supply Chain Orchestration (SCO) system interacts with execution systems:

  • Invoke target execution systems
  • Build target specific payload and send to execution systems
  • Receive and process responses from the execution systems


The predefined supply creation or orchestration process interacts with execution systems to create and manage supply:

  • A payload specific to the target execution system is built and sent to the execution system.
  • Updates from the execution system, such as purchase order status change or quantity decrease, are received and passed to the orchestration system for change management.

Overview of Security in Fusion R12

Oracle Financial Cloud Security Methodology

Cloud security methodology can be summarized with the simple statement: “WHO can do WHAT on WHICH set of data.”

  • Who: The user who performs functions in your company, such as an General Accountant.
  • What: Individual actions a user can perform, such as the ability to enter and post journals.
  • Which: The set of data that the user can perform the action on, such as general ledger journals with in your assigned ledger.


Security Reference Implementation

Oracle Financials Cloud comes with a predefined security reference implementation which consists of a baseline set of predefined security definitions and a set of security components which are delivered with the offering or service & used to meet the business needs of most enterprises.

The security reference implementation covers all functions and actions that need to be
secured. The security definitions were based on industry standards. Unless you have
customized existing functions or added new functions, you shouldn’t have to create any new job or duty roles. The implementation includes:
> Complete set of job roles.
> Duty roles and role hierarchy for each job role.
> Privileges granted to job and duty roles.
> Data security policies for each job role.
> Policies that protect personally identifiable information.
> Policies enforced across tools and access methods.
> Segregation of duties policies respected in the design of duties for the job role.
> Segregation of duties conflicts.

The First User

Define at least one implementation user using the Create Implementation Users task at the beginning of the project. The first implementation user is for creating only the initial enterprise structure and is not a real person in HCM. After the initial enterprise structure is complete, you can create additional users in HCM using the Manage Users or Import Worker Users tasks. Your users require that a business unit, legal entity, and other setup be added after the initial implementation. Planning is essential to:
> Analyze the access requirements specific to your organization, understanding who
needs access to what.
> Compare the requirements with the predefined roles in the security reference
implementation, and decide which predefined roles meet your requirements and can be
used as-shipped, and which will require customizations to meet your requirements.
> Certain product areas, such as Accounts Payable and General Ledger, include multiple
roles in the reference implementation. To compare accesses granted to each role, you
can use the Compare Role feature in the Security Console.

Function And Data Security

Oracle Financials Cloud uses role-based access control (RBAC). Your application is secure as delivered and you will provide function and data access through roles that you assign to users. Function security allows you to access:
> A page or a specific object.
> Functionality within a page, including services, screens, and task flows.
Data security consists of privileges conditionally granted as:
> Data security policies carried by roles.
> Human Capital Management (HCM) security profiles.

For example, a job role can enable users to work with journals. A data role in an upgraded
implementation that inherits the job role can provide access to the journal data within a ledger.
The data role General Accounting Manager – US inherits functionality from the General
Accounting Manager job role and it enables users to perform general ledger duties in the US ledger.

Types of Roles

Three role types can be assigned to users. These enterprise roles, also called external roles, are:
• Abstract roles: Represent people in the organization independent of the jobs they perform, such as employee or line manager.

Abstract role• Job roles: Represent jobs that users perform in an organization, such as Accounts Payable manager.

job Roles• Duty role: Logical collection of privileges that grant access to tasks that someone performs as part of a job, such as processing payables invoices or posting journals.

duty roles

• Data roles: Data roles is Combination of worker’s job and the Data/Security Profiles. You define the data scope of a Data role in one or more HCM security profiles. You define all HCM data roles locally and assign them directly to users.

Data role

Assign these roles directly to users:
• Job roles: You can also create custom job roles.
• Abstract roles: All users are likely to have at least one abstract role that provides access
to a set of standard functions, such as expense reporting or procurement. You can also
create custom abstract roles. In addition, the Employee role is important to assign to a
user as it allows users to submit ESS jobs, among other general functions that an
employee would have.
Assign these roles to Job and Abstract roles, not directly to users:
• Duty roles: You can also create custom duty roles.

Job Roles, Duty Roles and Privileges


Role Inheritance

Role inheritance is a key concept in the security model. The figure illustrates the hierarchy of job and duty role inheritance which are used as the building blocks in Oracle Cloud Security.


Almost every role is a hierarchy or collection of other roles.Job and abstract roles inherit duty roles and Duty roles can inherit other duty roles. You can also assign privileges directly to job, abstract, and duty roles. The diagram now shows Data Role added to secure User to the UK Set of Data in the UK Ledger for General Accountant Job role.


New Data Security in R12

Does not use data role templates
> Assigns users directly to the job roles and to the appropriate data sets.
> Uses the new Manage Data Access for Users page.

Security Console Replacing APM and OIM


The Security Console is an easy-to-use administrative interface that you access by selecting Tools -Security Console on the home page or from the Navigator. You use the Security Console for most role-management tasks. For example, use the Security Console to:

  • Review predefined job, abstract, and duty roles.
  • Create and manage custom job, abstract, and duty roles.
  • Typically, you copy a predefined role and use it as the basis for a custom role.
  • Review the roles assigned to users.
  • Compare roles.
  • Simulate the Navigator for a user or role.

Simplified experience for the IT Security Manager. Use Security Console for all tasks:

  • User Account Management
  • Role Management
  • Edit, Copy, Compare, Simulate
  • Functional and Data Security Policies
  • Role Hierarchy Management
  • User Name / Password policies
  • User Lifecycle Management
  • Certificate Management

To access the Manage Data Access for Users page, navigate to Setup and Maintenance > Manage Data Access for Users task. You use the Manage Data Access for Users task to assign users to data scopes, like Business Units, Ledgers, and Asset Books. You can access this task from the Setup and Maintenance work area.
You assign data scopes to users by role, and you can only assign data scopes to roles a user
has been provisioned.
You can also import assignments from a spreadsheet. By clicking on the Authorize Data
Access button in the Manage Data Access page, you can download a spreadsheet which you
can use to import the data assignments. You can prepare the data from another source, such as your legacy system, and populate the spreadsheet, then import.