Multiple Business Units and Data Access for Sales Objects

The way that you implement multiple business unit functionality in your enterprise can affect your users' access to object transactional data.

A business unit (BU) is a part of an enterprise that performs one or more business functions, such as sales or marketing. BUs let you both separate and share setup data. BUs also can control transactional data access. When you first implement the applications, your enterprise structure has a single BU, and all of your users belong to that one BU. You can create more BUs if you need to.

Resource organizations are mapped to one or more BUs, and users get associated with BUs through their resource organization membership. When you create a sales user and assign the user to a resource organization, the user gains access to each BU that's mapped to the resource organization. For example, users can access relevant transactional data associated with their primary BU, but might also have access to relevant transactional data in other BUs through their resource organization.

Note: When you create a user in the sales application, you specify a BU for the user. But only the BUs associated with the user's resource organization are relevant in determining the BUs a user can access. If a BU isn't specified for a resource organization, the default BU is used.

Within Sales, these business objects support the use of multiple BUs:

• Contracts
• Leads
• Opportunities
• Resource Organizations
• Territories

When you create an object that supports multiple BUs, such as an opportunity, you specify the BU to associate with the object.

Object Access in a Single BU Environment (Default)

In this type of implementation, all users can access master data, such as product or account information, by default. Users also have access to transactional data for objects such as opportunities, contracts or leads:

• Sales administrators can access transactional data for all objects.
• Sales users gain access to transactional data for an object through one of these methods:
  • They have been granted full access to the object
  • Through territory or team membership
  • Through the resource management hierarchy

  Full access to an object is provided through data security policies that include a condition of All Values. This table provides information about other methods of object access:

  More Ways to Gain Access to Objects

  Type of Object Access	Description
  Territory membership	You gain access to an object if: You're the owner or member of the territory that's assigned to the object. You're the owner or member of an ancestor territory of the territory assigned to the object. Your direct or indirect report in the resource hierarchy is the owner or a member of the territory assigned to the object. Your direct or indirect report in the resource hierarchy is the owner or member of an ancestor territory of the territory assigned to the object.
  Team membership	You gain access to an object if: You're a member of the sales team assigned to the object. Your direct or indirect report in the resource hierarchy is a member of the sales team assigned to the object . You're a member of the partner team assigned to the object.

Object Access in a Multiple BU Environment

In a multiple BU environment, access to objects and data is influenced by the BU the user belongs to. In this type of implementation, access to transactional data for objects, such as opportunities or leads, is determined in these ways:

• Sales administrators can access transactional data for all objects that are associated with the BU or units to which the administrators are assigned.

• Sales users access to transactional data for an object is the same in multiple BU environments and single BU environments. So sales users can access object data across BU boundaries provided that they have valid access to the object by means of territory or team membership, through the resource hierarchy, or by being granted full access to the object.

  But BU assignment can indirectly affect a user's access to object transactional data. In a multiple BU environment, BUs are available as territory dimensions and can be included as part of the territory coverage definition for the assignment of transactions. A sales user gains access to object data through territory membership. If BU is specified as a territory dimension, then the user's access to data is limited to objects which, when they were created, were assigned to the same BU that's assigned to the user's territory team.

For additional information about using multiple BUs, see the Oracle Fusion Cloud Sales Automation: Implementation Reference guide.