Hope all are doing good,
I'm just trying to make a scenario here,
Scenario : I don't want use to SVT relevant flag, I was removed ZRCS_SVT_REL flag from Environmental Parameters and i'm not using any classification in material level.
I'm just using Specify Selection Criteria for Volume Tracking and given a filter criteria as ESTRH-SUBCHAR and given a value into it. like example Substance nature PRE_REACT in composition level then only the substance will be tracked.
I would like to know the Pros and cons of it.
It will give the same out as the material relevant flag ? Does it work ?
Thanks in adv.
the filter options are useful; but you need to pay attention in use of them. These are considered in the "filling" and the "tracking".
It is better to make the "filling" and the "tracking" work and then to think about: can the result be improved (e.g. less tracking etc.)
Regarding your sentence:
"I'm just using Specify Selection Criteria for Volume Tracking and given a filter criteria as ESTRH-SUBCHAR and given a value into it. like example Substance nature PRE_REACT in composition level then only the substance will be tracked."
I am not sure if I have understood it 100 %; technically: the tracking is done on level:
Using the amounts as aggregated by "line" you can check if a threshold limit is exceeded etc.
In doing so: e.g. SAP is doing the filling (get data in CCRCT_EHS_COMP) and then use it;
As we have now "two specs" in the game (refer above) you need to define first: what is you demand?
As we have "REAL_SUB" (which can have a substance nature) and "Tracked Substance" which can have a substance nature
Here now a "major" issue need to be listed: the spec id is mandatory; the authorization group as well
but you can generate specs with or without a substance nature.
So you should pay attention with your criterias
Only if you use BADis or Exits (in CG02) you can make sure (potentially) that e.g. LIST_SUB must have a "nature".
But in practical cases (which i know): the substance nature is discussed more on "REAL_SUB" than "LIST_SUB" level. Idea is in most cases: If REAL_Sub is a "physical mixture": than at least for production you need not to consider this.
Anyhow: we need to assume that you use the "standard function modules"; if you use customer specific one: you can do what you would like to do (in combination with the filter); this increases the complexitiy of the overall logic.
So my hint is: pay attention with filter criterias ... First make SVT run; and then improve the data situation
The process is that the system first tries to determine the relevant materials. You can define relevant materials via the material classification or via filters on table MARA.
After the relevant materials are determined, the system will look for assigned specifications . During this step, the filter you mentioned will come into play. Any specifications that do not match the selection criteria you mentioned will not be considered for the further processes.
As I see, the Pro of your approach is that the selection will be at the specification level and not the material level.
The Con, I guess, would be that the performance would be affected if you dont filter materials at all.