2 Replies Latest reply: Oct 8, 2012 5:44 PM by Ahsan Shah RSS

    Looking for best approach to implement all ERP and CRM Analytics

    user10116791
      There is a scope to implement all the ERP Analytics (HR, Finance, SCM, Procurement & Spend, Project) and CRM Analytics (Sales, service, Marketing, Contact Center, Price, Loyalty ). Just want to know the best approach for impelmentation of both ERP and CRM analytics

      1- Work with two separate containers with separate execution plan for ERP and CRM
      2- Work with one container with one execution plan for both ERP and CRM
      3- Work with one container with separate execution plans for both ERP and CRM

      Also, Please let me know if there any standard document to achieve both the implementations simultaneously.
      Thanks!
        • 1. Re: Looking for best approach to implement all ERP and CRM Analytics
          Srini VEERAVALLI
          I would suggest to go/read this doc or 'Multi-Source Execution Plan Extract and Load Scenarios'
          http://docs.oracle.com/cd/E28271_01/fusionapps.1111/e14849/dacexecutionplans.htm

          This will take case common dimensions, assuming your target database is same for both.
          Option would be 'Work with two separate containers with one execution plan for ERP and CRM'
          You haven't mentioned ;)

          Pls mark if helps
          • 2. Re: Looking for best approach to implement all ERP and CRM Analytics
            Ahsan Shah
            Answer, as always, is "it depends". Here is a list of things to consider w the 3 approaches you mentioned:

            1- Work with two separate containers with separate execution plan for ERP and CRM

            This is a good approach if you plan on a different frequency of ETL loads for each container or different timings. As long as the targets are the same and you run INCREMENTAL loads from both containers, then the refresh dates will be updated. This is usually a good idea if your ERP and CRM users have different timing and load requirements and do not want to "interfere" w each other. You will also have DATASOURCE NUM ID uniquely defined for each system so the data will be segregated. By default, each source system will have its own container

            2- Work with one container with one execution plan for both ERP and CRM

            This is good if you are ok w the same exact load time for both. Its a simple approach and all tables will be loaded at the same time to avoid any confusion.

            3- Work with one container with separate execution plans for both ERP and CRM

            Not sure what the advantage of this option versus keeping them in separate containers (like Option 1).

            I would also review the secion in the DAC guide for "MultiSource Execution Plans"

            if helpful, pls mark correct