Developing and Deploying Siebel eBusiness Applications > Required Application Administration Tasks > Defining Company Structure >

Setting Up Positions and Position Skills

An employee has to have a position in order to log on to the Siebel application. Positions determine which records users with a particular position can access. Positions represent a job slot in your organization. As you enter your company's positions, refer to your company's organization chart to determine reporting relationships (positions and parent positions). There is always one position that does not have a parent position. For instance, the CEO position probably does not report to a higher level. Define positions in each level of your company's division hierarchy.

Because you choose parent positions as you create new positions, you should start at the top of the organization chart and work your way down.

To create positions

  1. From the application-level menu, choose View > Site Map > Group Administration > Positions.

    2. The Positions view appears.

  2. In the Positions list, add a new record for each of the positions you want to define.

    3. Some fields are described in the following table.

    Most fields in the Position list are filled in automatically from the Employee record of the active employee. If you have not set up employees, you can associate them with positions later.

    Field
    Comments
    Billing Product
    Used for Professional Services. For more information, see Applications Administration Guide.
    Compensable
    Used for incentive compensation. For more information, see the Siebel Incentive Compensation Guide.
    End Date
    Last day for the currently associated employee to be associated with this position. After this date, the employee will no longer have visibility to the records associated with this position.
    Organization
    Select an organization for the position. A position can only have one organization. If you want a user to have visibility to some organizations, but not all organizations, then you must create a position for each organization and assign the employee to each position.
    The employee can then see one organization's data at a time, by choosing View > User Preferences > Change Position.
    Position
    The name of the position. Required.
    Territory
    Allows a position to be associated to a territory for use by the Assignment Manager module. For more information, see Siebel Assignment Manager Administration Guide.
    Position Type
    Informational field that indicates the type of position. It has no impact on visibility.

    The following table lists sample positions for the NREC example. Later, as described in the section Setting Up an Employee in Your Siebel Application, you will add the employees listed in the last column.

    Position
    Parent Position
    Employee
    CEO
    N/A
    Ben Warren
    Sales Manager
    CEO
    Joe Smith
    Information Technology Manager
    CEO
    Kelly Brown
    Administrator
    Information Technology Manager
    Lisa Bolivar
    Real Estate Agent 1
    Sales Manager
    Leslie Castro
    Real Estate Agent 2
    Sales Manager
    Michael Stevens
    Marketing Associate
    Sales Manager
    Pablo Williams
    Partner Manager
    Sales Manager
    Pam Frederick

    Most fields in the Position applet get filled in automatically from the Employee record of the active employee. For example, the Start Date field shows the start date of the employee marked Active for the position.

To set up position skills

  1. From the application-level menu, choose View > Site Map > Group Administration > Positions.

    2. The Positions view appears.

  2. In the Positions list, select the position to which you want to add skills.
  3. Click the Position Skills tab.
  4. In the Position Skills list, add a new record.
  5. Select a skill in the Item field.

    6. Skills must exist before you can add them. Skills are added using Siebel Tools.

  6. Add comments, if desired.
  7. In the Position Skill Item list, add a new record.

 Developing and Deploying Siebel eBusiness Applications 
 Published: 18 April 2003