Importing Positions and Employees

The Administration - Group views automatically maintain the internal organization hierarchy incrementally as you change your organization’s position hierarchy, minimizing transaction volume and therefore improving the performance of Siebel Remote. For more information on using the Administration - Group views for working with positions, see Siebel Security Guide.

When using EIM to import or update positions, you must generate reporting relationships after running EIM to maintain organization relationships. If you do not generate reporting relationships, then incomplete or inaccurate data will be displayed in views involving employees or positions. For example, the My Team View will fail to display all positions on the team.

Note: When importing or updating positions, you must check for duplicate reporting relationships. Make sure that no positions report directly to themselves (PAR_POSTN_ID=ROW_ID). Before importing, search for this condition and correct it. If you import a record with this condition, you will get an error when you click Generate Reporting Relationships after the import.

To activate position hierarchy, see Activating Position Hierarchy. To generate reporting relationships, see Generating Reporting Relationships.

Note: EIM does not support importing Multiple Organization Visibility organizations. You cannot import this type of organization using the EIM_ORG_INT interface table or S_ORG_INT base table. EIM does support importing divisions that are not Multiple Organization Visibility Organizations.

To import employees and positions

1. Before importing employees and positions, make sure that the Position and Department columns in the Employee table contain the correct data, as follows:

   • Data from the Hire Date column in the Employee table matches the data from the Emp_Start_Date column in the Position table.

   • Data from the Position Start Date column in the Employee table matches the data from the Position Start Date column in the Position table.

   • Position table contains the logons of all employees.

   • Data from the Employee Hire Date column in the Position table matches the data from the Hire Date column in the Employee table.

2. Import the Employee table.

   You should import the Employee table first, because EIM searches for the foreign key of the Position table during its import and update of the Employee table.

   Note: If you are importing employees and positions with S_CONTACT.PR_HELD_POSTN_ID and S_POSTN.PR_EMP_ID set as primary columns, import the Position table first. See the following procedure.

3. Import the Position table.

4. If you want to import employees and positions using EIM and you also want to set the following primary columns, then you will have to run the import twice for the EIM_POSITIONS table:

   • S_CONTACT.PR_HELD_POSTN_ID

   • S_POSTN.PR_EMP_ID

   For example, to import employees and positions with S_CONTACT.PR_HELD_POSTN_ID and S_POSTN.PR_EMP_ID as primary columns:

   1. Import the Position table using the EIM_POSITION interface table.

   2. Import the Employee table, associate positions, and set the primary held position (S_CONTACT.PR_HELD_POSTN_ID) with the use of the MISC SQL parameter.

   3. Set the primary employee of Position (S_POSTN.PR_EMP_ID) by using the EIM_POSITION table and the MISC SQL parameter.