Dear Guarish
Gopi highlighted the main ideas of the SAP standard model (Best practise). Now coming back to your demand. PLease answer these questions:
1.) do you use a data provider?
2.) how may REAL_SUBs are part of a composition or specification listing and therefore would need to be exchanged
3.) What about your data model for DG_CL_SUB etc. (Dangerous goods data model)? Are there as well adaptions needed?
Coming back to your questions/doubts etc:
.
2. Buying LIST_SUB Database from content provider => the data providing ist not "mandatory" be linked to LISTZ_SUB; you can do data upload from the provided as well onj REAL_SIUNB level; to do it on LIST_SUB is the recommended data model
1. Creation of Specifications of PURE_SUB Type to inherit data from the LIST_SUB and make business specific additions.=> the use of PUR_Sub is the "standard data model"; but you can maintain the same data on REAL_SUB or LIST_SUB level as well
2. Data cleansing activity for replacing the old components with new components. => this would be needed if you would switch your data model
The "main" idea of the data model is:
a.) make clear to the user (maintenance) user whcih data he/she can expect on LIST:SUB level => answer is: (in the standard model) only data which is coming form Data provider
b.) The use of the PURE_SUB is to "enhance" data. Therefore PURE_SUB does have some reference to LIST_SUB but you add aditional data (based on informaiotn form your own company or using other sources)
c.) now you generate the composition based on PURE_SUB etc.
The main idea of thsi data model is therefore to generate "subobjects" which can be maintained independent but can be used in composiitons etc. to inherit data to REAL_SUB (e.g.via WWI report MSDS/SDS)
But you need to understand that e.g. REAL_GRP is as well an important part of standard data model; This type of object is used to "group" data which can be used very often. E.g. you could do it on "lowest" level. You could prepare a REAL_GPR with only the data "Color = green". Now any REAL_SUB having this "attribute" could get simply a reference to REAL_GRP; by "clever" use of this data model the data maintenace actions are reduced. But pay attention: this data model should only be used if you are not using "Rulesets" (which are as well available form data provider in most cases)
Conclusion: there is no "direct" benefit to switch the data model; there is no "clear" business driver; it is more the decision about how to go on with the data molde used. E.g. you need not to swicth the data model in one bug project; you could do it as wel step by setp (or e.g. only for new REAL_SUBs etc.)
C.B.