Business Units in Fusion Apps

Download as pdf or txt
Download as pdf or txt
You are on page 1of 25

What is a Business Unit (BU)?

A business unit is a unit of an enterprise that performs one or many business functions
that can be rolled up in a management hierarchy. A business unit can process
transactions on behalf of many legal entities. Normally, it will have a manager, strategic
objectives, a level of autonomy, and responsibility for its profit and loss. Roll business
units up into divisions if you structure your chart of accounts with this type of hierarchy.
In Oracle Fusion Applications, you assign your business units to one primary ledger. For
example, if a business unit is processing payables invoices they will need to post to a
particular ledger. This assignment is mandatory for your business units with business
functions that produce financial transactions.

Can a BU Process Transactions for Multiple Legal Entities (LE)?

Yes, If you want multiple LEs using the same BUs then all LEs must be assigned to the
same ledger and the BU needs to have the same ledger assigned as it's primary ledger.

Can I Create a Financial Transaction Between BUs?

No, In V1 of Fusion Cross BU Financial Process is not Available.

Do I Have to Assign a Primary Ledger my BU?

When assigning functions to your chosen BU if these functions result in producing a


financial transaction
then it is mandatory to assign a primary ledger to the BU.

When Looking at the Fusion Tables How can I Tell which BU has Processed That Specific Row?

This will depend on which table you are looking at. It will be one of the following fields:

BU_ID
or
BUSINESS_UNIT_ID
or
ORG_ID
5/14/2018 Document 1380204.1

Copyright (c) 2018, Oracle. All rights reserved.

Fusion: How to Specify Default Business Unit For a User in Fusion Payables (Doc ID 1380204.1)

In this Document

Goal
Solution
References

APPLIES TO:

Oracle Fusion Payables Cloud Service - Version N/A and later


Oracle Fusion Payables - Version 11.1.1.5.1 and later
Information in this document applies to any platform.

GOAL

This document outlines the steps to define Default Business Unit for a User in Fusion Payables.

Profiles are permanent user preferences and system configuration options. They allow for the centralized management of
configuration data but with sophisticated, customized user, security, and session-context access to the values.

SOLUTION

1. Log in to the Fusion application and from the global navigator go to the Setup And Maintenance under
Tools

2. From the Functional Setup Manager, look up for the "Manage Profile Options" task click to open the task.
The Profile Option Code for Default Business Unit is "DEFAULT_ORG_ID"

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_625&id=1380204.1 1/3
5/14/2018 Document 1380204.1

When defining profile definitions you also define profile levels, which are part of a hierarchy. At this time, only the following
hierarchy is available:
Site (lowest level: All users at an installation site)
Product
User (highest level:An individual user, identified by their UserID (UserGUID) for the current session.)

As most profiles are user preferences and can potentially be set at these three levels, this is the default hierarchy. Profiles can
be set at one or more levels.

3.To set the profile option value for Business Unit, go to the Manage Administrator Profile Option Values page to search for the
required profile option.

4. Specify the Profile Values as shown below:


https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_625&id=1380204.1 2/3
5/14/2018 Document 1380204.1

4. Specify the Profile Values as shown below:


In this example, the Profile Value for BU:Vision Operations is 204.

5. Now log into the Payable Application as FIN_USER50 user, notice the Vision Operations,
or BU_ID =204 defaults as the BU.

REFERENCES

NOTE:2032943.1 - Unable To Setup Default BU At Site Level


Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_625&id=1380204.1 3/3
5/14/2018 Document 1357431.1

Copyright (c) 2018, Oracle. All rights reserved.

Unable To Access The Business Unit Screen With A New User (Doc ID 1357431.1)

In this Document
Goal
Solution
References

APPLIES TO:

Oracle Fusion Financials Common Module - Version: 11.1.1.5.1 and later [Release: 1.0 and later ]
Information in this document applies to any platform.

GOAL

A new user tries to access the Define Business Unit implementation task as follows and the page does not display.
Log in as the user
Path : Navigator -> Tools -> Setup and Maintenance
Select an implementation project
Click on Define Business Unit.
Click on the Go to Task Link
The system does not open the BU window.

What may be the problem with this user?

SOLUTION

Ensure either the Financial Application Administrator Application Implementation Consultant


or roles are assigned to the user
to access to the Business Unit UI.
Roles are assigned to users via Oracle Identity Manager (OIM). See note 1354214.1 for an example on how to assign roles to
users.

REFERENCES

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_772&id=1357431.1 1/1
5/14/2018 Document 1344883.1

Copyright (c) 2018, Oracle. All rights reserved.

How To Assign A Primary Ledger and A Default Legal Entity To A Business Unit (Doc ID
1344883.1)

In this Document

Goal
Fix
Why do you need to assign a Primary Ledger and a Default Legal Entity ?
Important Points:
The Following Functional Setup Manager (FSM) steps are required to assign a Primary Ledger and Default LE:
References

APPLIES TO:

Oracle Fusion Financials Common Module - Version 1.0-Beta and later


Oracle Fusion Financials Common Module Cloud Service - Version N/A and later
Information in this document applies to any platform.

GOAL

How To Assign A Primary Ledger and A Default Legal Entity To A Business Unit

FIX

Why do you need to assign a Primary Ledger and a Default Legal Entity ?

If you pick an Business Function that will create a Financial Transaction it is mandatory to assign
a Primary Ledger and a Default Legal Entity (LE) to the Business Unit (BU) you have chosen to perform that Business Function.

Important Points:

A BU can only have one Primary Ledger.

Prior to assigning a Default LE to the BU it is mandatory that you first assign the LE to the Ledger which is to be used as the
Primary Ledger. See Note1344517.1 How To Assign A Legal Entity To A Ledger.

Business Functions that do not create a financial transactions will not require a Primary Ledger or Default LE assignment.

The Following Functional Setup Manager (FSM) steps are required to assign a Primary Ledger and Default LE:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_870&id=1344883.1 1/3
5/14/2018 Document 1344883.1

After creating a project in FSM pick the task list "Define Business Units". Ensure before you go into the individual tasks that the
correct BU you are working on is shown. In the above example it shows BU "NC LEBU2" as the BU to be worked on.

Next step will be to click on the "Go To Task" for the "Assign Business Unit Business Function" task.

Once clicked on the "Go To Task" for the "Assign Business Unit Business Function" task. This
will take you into the "Assign Business Functions" page as shown above.

Note after you have picked the desired Primary Ledger when you pick the Default LE only the LEs
that have previously been assigned to this desired ledger will be available to be assigned to the BU.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_870&id=1344883.1 2/3
5/14/2018 Document 1344883.1

In the above example only LEs that have been already assigned to the "Vision Operations (USA)"
Ledger show as available as Default LE.

When enabling a Business Function that creates financial transactions if no Primary Ledger
and Default LE has been picked then a warning will appear. You will then not be able to save until
a Primary Ledger and Default LE have been picked.

REFERENCES

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_870&id=1344883.1 3/3
5/14/2018 Document 1344878.1

Copyright (c) 2018, Oracle. All rights reserved.

Business Units in Fusion Receivables (Doc ID 1344878.1)

In this Document

Purpose
Scope
Details

APPLIES TO:

Oracle Fusion Receivables - Version 11.1.1.5.1 and later


Oracle Fusion Receivables Cloud Service
Information in this document applies to any platform.

PURPOSE

Defining the use of Business Unit in Fusion Receivables

SCOPE

Business Unit

Definition
Unit of an enterprise that performs one or more business functions. Normally, it will have a named manager, strategic
objectives, a level of autonomy and responsibility for profit and loss.
Business units may
Outsource business functions to other business units
Be the service provider of a business function to other business units.
Business unit legal entity
Business unit legal entity defaulted onto transactions
Some, but not all, subledgers allow override at a lower level (supplier invoices and payments; customer invoices and
payments; inventory organizations etc.)

DETAILS

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_919&id=1344878.1 1/3
5/14/2018 Document 1344878.1

The Business unit in fusion has a multiple function when compared to release 12 of applications. The functionality itself is a
Peoplesoft process used in Fusion.
Release 12 the terminology would be an operating unit in applications and this would be confined to being a receiving unit or
a purchasing unit.
Fusion in the above example highlights the business unit to be multifunctional.

Business Units, enable the following important features;

Share reference data between departments that perform the same function
Support consolidated processing of downstream transactions from many upstream departments in a business flow
View and process transactions from upstream departments in a business flow without having to change the department in
which you are currently transacting

Business Units use in Fusion can provide the following capabilities:

Flexible Performance Reporting and Analysis, showing activities and results


Adherence to complex Legislative Compliance that differs from region to region
Increased Governance opportunities and reduced Risk due to the separation of specific capabilities and activities
Adherence to complex Taxation Regimes, again varying across regions
Logical division of the organization across Geographical boundaries

Physical Data Model Usage


The following describes how the new entities in the logical data model are implemented using the existing HR Organization
tables as described in the physical data model.

BusinessFunctions
Business Function metadata is implemented using a combination of business function definition contained in the application
taxonomy (FND_APPLICATION_TAXONOMY) with additional Business Function specific attributes held in a sibling table
FUN_BUSINESS_FUNCTIONS.
The view FUN_BUSINESS_FUNCTIONS_V joins these two tables to provide a single representation of Business Function
metadata.

Business Units have the following integration Points:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_919&id=1344878.1 2/3
5/14/2018 Document 1344878.1

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_919&id=1344878.1 3/3
5/14/2018 Document 1432441.1

Copyright (c) 2018, Oracle. All rights reserved.

How To Create Data Roles for Business Units (Doc ID 1432441.1)

In this Document

Goal
When assigning Business Functions to a Business Unit data roles should automatically be created.
Solution
Worked Example
Create Basic Business Unit (BU)
Check if BU Data Roles have been created
Create Data Roles
Synchronize Oracle Identity Manager (OIM) with Authorization Policy Manager (APM)
Assign Data Roles to Login User
Check Access to BU

APPLIES TO:

Oracle Fusion Financials Common Module - Version 1.0-Beta and later


Oracle Fusion Financials Common Module Cloud Service - Version 11.1.4.0.0 and later
Information in this document applies to any platform.

GOAL

When assigning Business Functions to a Business Unit data roles should automatically be created.

On occasions, for various reasons, this does not happen. When data roles have not been created and correctly assigned this
will prevent a user from configuring or using a Business Unit.

The solution is to manually create these data roles and assign them.

SOLUTION

If you are a Software-as-a-Service (SaaS) customer, there are multiple sections in this document that need not be
performed by you. Please log a Service Request in My Oracle Support for Oracle to do this for you.

Worked Example

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 1/14
5/14/2018 Document 1432441.1

This example will show a case where a user creates a Business Unit but no data roles are created so they have to create and
assign them manually. The various stages will be broken down into the following
headings:

Create Basic Business Unit (BU)

Check if BU Data Roles have been created

Create Data Roles

Synchronize Oracle Identity Manager (OIM) with Authorization Policy Manager (APM)

Assign Data Roles to Login User

Check Access to BU

Create Basic Business Unit (BU)

After picking the 'Define Business Units' task list create Business Unit. Then save and close. Note This user has created a new
default set called 'NC_BU110S'. It will hold any new set_id data used by the BU 'NC BU110'.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 2/14
5/14/2018 Document 1432441.1

Once the initial BU has been created Business Functions need to be assigned. Assigning functions to a BU should automatically
create the related data role. In the above example the user is assigning Receivable functionality to a BU named 'NC BU110'.

Check if BU Data Roles have been created

Check if the BU is available to pick when configuring the relevant module. In this worked example the user has chosen the
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 3/14
5/14/2018 Document 1432441.1

receivable functionality. If they cannot pick 'NC BU110' when configuring the receivables system options then it's likely the
relevant data role has either not been created or not assigned.

To check if the data role exists log into the Authorization Policy Manager (APM) module. Under the 'Authorization Management'
tab click on the Search External Roles.

For the basic BU setup there should be two data roles created under the 'Financial Application Administrator' role. One will be
for the basic BU access and the other for the BU set_id access. In the above case neither role has been created 'NC BU100'
BU.

For each functionality there will be additional roles required. An example will be shown in the latter steps of this document.

Create Data Roles

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 4/14
5/14/2018 Document 1432441.1

To create a data role the user first needs to search and pick the relevant data role template.

There are two templates used for the minimum BU usage these are:

FinancialsFunBusinessUnit = used for basic BU setup


FinancialsFunSetIdFinancialsFunSetId = BU SetId usage

In this example as we have assign receivable functionality there should be 2 additional templates which are:

BillingRevMgtandCustPayment = Basic AR setup


FinancialsArSetIdFinancialsArSetId = AR SetId

Once the correct template is shown the user needs to highlight the required template then click on open.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 5/14
5/14/2018 Document 1432441.1

Once the template has been opened the user can view existing data roles. If they want to create new roles then they need to
click on 'Generate Roles' as shown above.

Once the 'Generate Roles' has completed the user can click on 'refresh role' under 'valid roles', In the above example it shows
a data role for basic BU usage has been successfully created - 'FUN_FINANCIAL_APPLICATION_ADMINISTRATOR_JOB_NC
BU110'.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 6/14
5/14/2018 Document 1432441.1

When the FinancialsFunSetIdFinancialsFunSetId template is used it will create set_id data role called
'FUN_FINANCIAL_APPLICATION_ADMINISTRATOR_JOB_NC BU110S'.

As this example is using receivables functionality when the template FinancialsArSetIdFinancialsArSetId is used to generate
data roles then all AR roles will have a set_id role created for them. As as shown above.

Note. There have been occassions when there have been blank spaces in the BU name. This is not correct. These roles will
need to be regenerated to ensure there are no blank spaces in the BU name.

Synchronize Oracle Identity Manager (OIM) with Authorization Policy Manager (APM)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 7/14
5/14/2018 Document 1432441.1

Once the data roles have been successfully created in APM they then need to be copied over to OIM. To do this you can either
run 'LDAP Role Create and Update Full Reconciliation' or 'LDAP Role Create and Update Reconciliation' program. To run either
program you will need to go into OIM and click on the 'Advance' icon as shown above.

Once in OIM's Advance Administration section pick the 'System Management' tab then select either of the LDAP reconciliation
scheduled jobs. Now double click on the chosen job to open up it's parameters.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 8/14
5/14/2018 Document 1432441.1

After opening the parameters section of the job click on 'Run Now'. This will then copy all the successfully created data roles
from APM into OIM. The next step will to assign these data roles to a login user.

Assign Data Roles to Login User

When in OIM under the 'Administration' tab click on the users 'Advance Search -Users' section.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 9/14
5/14/2018 Document 1432441.1

In this example the user would like the login user 'fin_superuser' to be able to use the BU 'NC_BU110'. Therefore they will
need to assign these roles to this login user. Once the user has found 'fin_superuser' they will need to pick this user in the
research results field then click on open.

Once the user is in the required login user. Here it is showing the 'FIN_SUPERUSER' tab. Then click on the assign icon to pick
which roles you want assigned.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 10/14
5/14/2018 Document 1432441.1

The above example shows the user assigning basic BU access data role for BU 'NC BU110' to the login user 'FIN_SUPERUSER'.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 11/14
5/14/2018 Document 1432441.1

As the user has assigned Receivable functionality to this BU they also need to assign the AR roles ,such as the
'AR_BILLING_MANAGER', to this login user.

Check Access to BU

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 12/14
5/14/2018 Document 1432441.1

To show the user now has access to the newly created 'NC BU110' BU they can go to any AR configuration step to see if this
BU is available in the LOV. Here the user has chosen the 'Receivable Activities' task.

The data roles have correctly been created and assign as they are now able to pick BU 'NC BU110'.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 13/14
5/14/2018 Document 1432441.1

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=15mpvrv20i_1017&id=1432441.1 14/14

You might also like