Position Administration

Positions can be set up in a multilevel hierarchy, which allows for manager access control. The parent position gains visibility to all the sets of data visible to the individual child positions. (Usually, the data is displayed only where the child position is the primary on the team or record.)

You cannot make a position obsolete by setting the End Date. This field records only the end date for the current employee associated with the position. It does not make the position obsolete after that date has passed.

Caution: Do not delete or merge positions because doing so renders the primary position invalid.

If you rename a position, check these areas in your Siebel application to make sure the name change is reflected correctly:

  • Assignment rules, if you have used these positions in assignment rules. For more information, see Siebel Assignment Manager Administration Guide.

  • Workflow processes, if you have used these positions in workflow processes. For more information, see Siebel Business Process Framework: Workflow Guide.

  • Enterprise Integration Manager (EIM), if you are referring to these positions in EIM import SQL scripts. For more information, see Siebel Enterprise Integration Manager Administration Guide.

  • The Position field of the Employees view.

    Note: If you change a mobile user’s position, that user’s visibility rules change. In this case, it is recommended that the user reextract his or her local database. However, if you change only the position name (for example, from Sales Representative to Sales Associate), then reextraction is not required because in the database table where position names are stored, this column has enterprise-wide visibility. In other words, changes to this column are distributed to all users.

Related Topics

Planning for Access Control

About Planning for Divisions

About Planning for Organizations

About Planning for Responsibilities