Showing results for 
Search instead for 
Did you mean: 

SAP EHS SVT Quantity limit checking including existing stock

0 Kudos

Dear Expert,

My company is new to both EHS and SVT and we need to implement this module to track the substance volume for K-REACH. We managed to set up to enable checking and blocking the PO when the substance in the PO Qty exceeded the threshold set.

However, we can't seem to trigger the block/warning although the substance qty + existing GR-ed PO qty, exceeded the threshold.

Do you have any idea what may be missing or suggest something that we can look into?

Thank you.


For example,

Material has 96% of substance 46, so when i GR for 600KG of material, which consist of 576KG of substance 46, there was no problem.

What i was expecting is, when i create new PO for 800KG, which consist of 768 KG of substance 46, adding up the existing 576KG of substance 46 from the previous GR, it would have exceed the threshold of 1MT = 1000KG of substance 46, thus creating error in PO. But it wasn't working.

When i created new PO for 1100KG, it triggered error successfully, since it exceed the substance 46 threshold of 1MT.

Active Contributor
0 Kudos

Dear Bang Doosung

I have reread the online help. You will find there this important sentence/paragraph:

In volume determination , the system determines the quantities of the substances that must be tracked. It adds the quantities of each substance to the previously determined total quantities on a daily basis and saves the current totals in the tables in substance volume tracking. To enable this, run report RREGCH_VT once as an initial run and then schedule it so that it updates the total quantity daily.

In the online checks, the system uses the last saved total quantity from volume determination and the quantity entered in the current document. This means that any quantities in other documents entered on the current day are not taken into account. This means that there is a slight discrepancy in the quantities for a short time, but system performance is greatly improved. The discrepancy is corrected in the next daily update of the total quantity because all documents for a day are taken into account.

Therefore that was the reason why i asked on which day which action is happening. If you read carefully the sentence/paragraph it just explain it as: a.) if you enter a SVT relevant PO at day X: this PO (and the content) will be compared with the "just tracked" quantities (via the job) b.) if you enter more POs (with the same data constellation) during the check only a comparisison is done with "last day" results. So within 24 h no "accumulation" is done On the next day: any PO (which is SVT relevant) is analyzed and the values are added to those exsiting yet in database On top the same is true for the "goods movement" story; you need to wait 24 h until the "online" check can do the work Conclusion: the design of SVT is such that the "online check" is only a general "hint" that something can go wrong (form limit prespective) and it does not fully support the 24 h. This is one of the "gaps" in the SVT and in the online approach


Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos


The quantity that is used for comparison is the quantity that was last tracked with the RREGCH_VT report. This means that if you have already used 900 Kg of the limit you would not be able to create another order which raises the quantity by 101 Kg. But you can create multiple orders of quantites upto 99 Kg. Because the system always checks against the last tracked quantity i.e. 900 Kg.

One solution could be to run the RREGCH_VT report multiple times a day (if the number of orders per day is not huge and the runtime is a few minutes)


Neeraj Agrawal

Active Contributor
0 Kudos


we are not using your scenario. But the best is to "debug" the process and using breackpoint at the correct place.

But you will find some rare examples here of similar set up (please check the existing SVT blog as well)

E.g. like:



Check as well online help and OSS (there is a special consulting OSS note for SVT) (e.g. SAP note 1111196)

In the "online help" and in SAP marketplace you will find hints (and OSS notes) referring to "limits" in the SVT process (processes which are not supported)

In theory story you be like:

During the "save" of the PO the process should check: what has been tracked yet; and what is added by the "PO"; this is the so called "planned" part

During the goods movement in theory (if i remember correct) the next check is done (normally this is not so of interest as in the "planning" part you should get enough hints regarding "problems" from threshold limit point of view

But the goods movement would be the "confirmed" part

Regarding your findings:

"What i was expecting is, when i create new PO for 800KG, which consist of 768 KG of substance 46, adding up the existing 576KG of substance 46 from the previous GR, it would have exceed the threshold of 1MT = 1000KG of substance 46, thus creating error in PO. But it wasn't working."

As we are not using the online part i can only "judge" a little bit (and this is as well some reason why we are not using the process if i remember correct).

I am not 100% if in "realtime" the goods movement done on date "x" and the new PO create on the same date "X" really "adds" the volumes as you expect

You just check the called function modules and analyse the logic or simply may be start a OSS dialog


PS: is your property / VAT "Quantity" a customer specific one? Normally the threshold limits are set up different (please check the SVT consulting OSS note)

0 Kudos

Hi Christoph,

Thank you for your comment. I have gone through the links you provided, unfortunately it doesn't seems to be what i am looking for.

Regarding your question, the goods movement not necessarily done on the same day PO is created.

And the Quantity is not a customer specific, we just need to track the substances in all materials in our SAP.

We are hoping that when we create new PO, it will also check the existing stock/GR in the same year.