Siebel Enterprise Integration Manager Administration Guide > Importing Data > Importing Legacy Data >

Recommended Import Order for Importing Legacy Data

The order in which legacy data is imported is critical to make sure that relationships between dependent data elements are established correctly. Siebel EIM tables do not map one-to-one with Siebel target database tables. To make sure that the necessary data is present to establish relationships between data entities, use the following sequence to import data:

  1. Administrative

    NOTE:  An example of administrative data would be a List of Values for Currency or Zip Code.

  2. Business Unit
  3. Positions
  4. Accounts
  5. Contacts
  6. Employees
  7. Products
  8. Opportunities
  9. Personal Accounts
  11. Documents
  12. Forecasts
  13. Fulfillment
  14. Marketing Campaigns
  15. CPG Promotion Management
  16. CPG Product Movement
  17. Service Requests
  18. Product Defects
  19. Activities and Appointments
  20. Notes
  21. File Attachments

This import order reflects most import processes. In some cases, the import order for your import process may vary slightly depending on your requirements.

NOTE:  Your Siebel application provides a sample configuration file named default.ifb. You can also use the import sequence in this sample file in your configuration file.

While the import order is most critical when performing the initial import of legacy data, this recommended order should be followed for all subsequent data imports as well.

NOTE:  Some tables cannot be used to import all data necessary for the imported data to be visible in the GUI. For example, the interface table EIM_FCSTOPTYPRD can be used to export forecast data but it cannot be used for importing. The import runs successfully, but the imported data cannot be seen in the GUI because EIM does not populate the table that would make the data visible.

 Siebel Enterprise Integration Manager Administration Guide 
 Published: 05 January 2004