Showing results for 
Search instead for 
Did you mean: 

How to disallow direct scrapping from a Storage Type

0 Kudos

Hello Gurus,

I have a Storage Type where I have marked 'no GI' indicator in the Storage Type definition:

My expectation was that now, system should not allow me to post a direct goods issue (for example Scrap) from this Storage Type using the transaction /SCWM/ADGI.

However, this is not the case. I can still use /SCWM/ADGI for a bin in this Storage Type, select the option 'scrapping' and post the Scrap.

This transaction when posted, still creates a Goods Issue WT and removes the quantity from the bin.

How can I technically stop users from doing this.

The target process is that they should always first move the scrap material to a dedicated Storage Type, and then do the /SCWM/ADGI from there.

Thanks in advance for your comments.

Accepted Solutions (0)

Answers (2)

Answers (2)

Active Contributor
0 Kudos

Hi rahulsharma.iitr

Unfortunately this is standard behaviour.

Please see details: An unplanned goods issue can be performed even if you have selected the No GI checkbox in the storage type settings, because the unplanned goods issue is not an outbound delivery process. For more information, see Customizing for Extended Warehouse Management under Master Data Define Storage Type.


Solution: you can implement checks during unplanned goods issue by using the Business Add-In BAdI: Stock Checks for Goods Movements. For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Cross-Process Settings Goods Movement Postings BAdI: Stock Checks for Goods Movements.

Other option-: Screen variant (honestly never tried in EWM).

Kind Regards,


Active Participant
0 Kudos

To disallow direct scraping from a storage type, you can implement authentication and access control mechanisms that require users or applications to provide valid credentials before accessing the data. Here are some steps you can take to achieve this:

  1. Use Access Control: Implement access control lists (ACLs) to restrict access to specific users or applications. This can be done at both the storage level and the API level.

  2. Use Authentication: Require authentication before granting access to the data. This can be done through the use of API keys, OAuth tokens, or other authentication mechanisms.

  3. Implement rate limiting: Set limits on the amount of data that can be accessed within a specific time period. This can help prevent abusive behavior and ensure fair usage of the storage system.

  4. Implement Encryption: Encrypt the data stored on the storage system to prevent unauthorized access to sensitive information.

  5. Use Captchas: You can also implement Captchas on your site to prevent automated scraping by bots. Captchas can help prevent bots from scraping your data and also help protect your site from other types of attacks.