Dear Gaurish
from EHS point of view there is no reason to exchange the specs. You could go on in using REAL_SUB without any problem. I am sorry to say:
we have only these "dumb" methods to execute such kind of mass changes:
a.) trying to do mass ehs export (change spec) and import it(never tried it this way !!)
b.) may be using ALE (from external source) (never tried it this way)
c.) may be using OCC (which is moreor less only dedicate to"legal" updates; so I am not sure if it will work and we do not use this tool in this context)
Statement: 1.) your amountof changes is quite low; 2.) only one value assignment type is effected (Hazardous ingredients) => there do it by "hand" (one by one)
But I have some "similar" doubts as may be Tarun. In most cases the story is like this:
You have a "REAL_SUB"; you maintain a composition (e.g. in one of the "Exact compoistions); then you use rule sets to populate Hazardous ingredients
Therefore. what is your data modell???
Second (I agree fully to Taruns explanation): before you can exchange the "spec" number you need to make sure that on LIST_SUB level you will find the same data; further on you might get trouble with "change marks" in reports if you do it like this (reasons are to complex to be enumerated here)
Conslusion: the solution depends on "future data model". If you need to exchange the specs only "once" and there is no demand for future, then you should generate a "one and only" report; in most cases this is not true; this type of "demand" is coming up more than one time during the life cycle ofa SAP ERP EHS enabled systems; therefore it is better to look for future options than to prepare a "one and only" report
C.B.