Developing and Deploying Siebel Business Applications > Installing Software, Adding Users, and Creating the Company Structure >

Process of Creating the Company Structure


This process is a step in Roadmap for Developing a Siebel Application.

To create the company structure, perform the following tasks:

  1. Creating an Organization
  2. Creating Positions and Position Skills
  3. Creating a Partner Organization

Overview of Creating the Company Structure

Because NREC does not use Access Groups or Catalogs, this chapter does not describe how to create them. For more information, see Siebel Applications Administration Guide and Siebel Security Guide.

Creating the organizational structure for your company includes creating the following items:

  • Organizations and organization skills. An organization represents broad divisions of internal or external groups of users. For example, internal divisions or partners. An organization controls access to data.
  • Divisions. A division belongs to an organization but does not affect visibility. A division groups positions and record addresses, and maintains default currencies.
  • Positions and position skills. A position represents a specific job type. It determines the records a user can access.
  • Responsibilities. A responsibility controls the screens and views a user can access. For more information, see Creating Responsibilities.

The company structure affects the records and views that Siebel CRM displays to a user. A many-to-many relationship exists between a person and the positions you associate with that person. For example, you can associate a person with the sales representative position for the X territory and the sales manager position for the XYZ region. You can also associate more than one person to a single position. For example, when two people share a single job.

If you associate a user with one responsibility and multiple positions, then that user can access the same set of views regardless of the position the user logs in with. If the user changes position, then the user can access different data. For example, a user who logs in as a sales representative can only access data that pertains to the sales representative position. The user can still access the My Team's Accounts view, but because no other positions report to the sales representative position, Siebel CRM only displays data that pertains to the sales representative position. In this situation, it does not display data that pertains to the sales manager position. If the user changes to the sales manager position, and if the user is the primary on the account, then the My Team's Accounts view displays user information for the positions that report to that user.

NOTE:  Changing your company structure can cause routers to reevaluate visibility for every object that is related to the objects that you change. This reevaluation can affect performance. For more information, see Siebel Remote and Replication Manager Administration Guide.

For more information, see Siebel Applications Administration Guide and Siebel Security Guide.

Developing and Deploying Siebel Business Applications Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.