Bookshelf Home | Contents | Index | PDF |
Siebel Enterprise Integration Manager Administration Guide > Importing Data > Special Considerations for Imports > Importing Positions and EmployeesThe 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
To import employees and positions with S_CONTACT.PR_HELD_POSTN_ID and S_POSTN.PR_EMP_ID as primary columns
Activating Position HierarchyAfter importing or merging positions using EIM, or after merging positions through the user interface, it is necessary to generate reporting relationships to populate or rebuild S_POSTN_RPT_REL (for versions prior to 6.x) or S_PARTY_PER (for version 7.x or later). This happens automatically when you insert positions using the user interface. NOTE: For customers using the Siebel Financial Services application, the relationship of party entities is stored in S_PARTY_RPT_REL. The Generate Reporting Relationships button is not exposed by default. To expose this button, follow the instructions in Exposing the Generate Reporting Relationships Button for Versions Prior to 6.x or Exposing the Generate Reporting Relationships Button for Versions 7.x and Later, depending on the version number of the application you are using. Exposing the Generate Reporting Relationships Button for Versions Prior to 6.xIn Siebel Tools, there are two places where you can expose the Generate Reporting Relationships button: To expose the Generate Reporting Relationships button
After exposing the Generate Reporting Relationships button, you can test it by generating reporting relationships. See Generating Reporting Relationships. Exposing the Generate Reporting Relationships Button for Versions 7.x and LaterThe Generate Reporting Relationships process needs to be executed after upgrading to version 7.0. For more information, see the section on post-upgrade tasks for the production environment in the Siebel Database Upgrade Guide. You also need to execute this process whenever the denormalized hierarchy structure (S_PARTY_RPT_REL) becomes unsynchronized with the data in the normalized tables (S_PARTY). The following situations can cause these tables to become unsynchronized:
Generating Reporting RelationshipsIf you want to modify your organization structure by importing or updating positions using EIM, you must generate reporting relationships after running EIM to maintain organization relationships. Before generating reporting relationships, you must first activate position hierarchy by completing the procedure in Activating Position Hierarchy. For best performance, complete all organization changes before generating reporting relationships, because this operation generates a high number of transactions for mobile users. This operation generates reporting relationships for all organizations and divisions regardless of the organization or division you have selected in the GUI. For more information on organization administration, see Siebel Security Guide. NOTE: If you have mobile users, stop the Transaction Processor before clicking Generate Reporting Relationships. This is necessary because generating the reporting relationships can cause a large number of Siebel Remote transactions to also be generated. |
Siebel Enterprise Integration Manager Administration Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |