How to syncronize changes in secondary Master data objects with Primary?

Question

Hi Gurus!!
I am working on a requirement in which I have to create a custom repository for EQUIPMENT master and EXCISE master.
There are Material,Vendor,Customer,Equipment,and Excise master repositories in the server.
Excise master deals with determination of excise rates based on Material and chapter Id combination,also its required to have upto date Vendor and Customer details in the Excise master repository.
The Equipment master on the other hand requires updated Material records,which are available in separate Material repository.
It can be done through-
->Multiple Main Tables
->API's fetching records
Please guide me how to go ahead and which is the best way?
Thanks,
Ravi

Answer 1

Hi Ravi,
I just want to know that you have to maintain two custom repositories i.e.  EQUIPMENT master and EXCISE master.
Or is it ok with  one repository.
Why i want to know is  becuase if you create two custom repository then you have to maintain material data two places i.e. in both repositories.
If it possible that only repository can work then you can go with one repository with 5 maintables.
But every  thing has pros n cons .
Pros:
data storage is less
cons:
so if you go with one repository so in this case user load only on one repository becuase if user interested in vendor or customer or material they will log in same repositories and hence there is more chances of  server downtime.
you can go with  multiple repositories  one for each .
pros
With this no more load on one repository.
cons
in this approach you have to do the syndication btw repositories to get upto date data  and storage needs more as some common data maintain in different repositories
So i would suggest that
You can go with multiple maintable IF
   1.1 individaul repositories donot have so many users i.e. vendor ,material and customer repositories  donot have  so many users  then  put all in one repository so that we can maintain data at one place.
Different repositories is also good option if  all three repositories have so much load and you can  get upto date data through syndication .But in this approach if you need all fields from three repositories then it would be  a waste of storage and if you need ony some information from these repositories then this is good also.
Please inform us abt what  is feasible for you so that we can make the solution more simple.
Thanks,
Sudhanshu