Material master deletion flag and blocking activities
Flagging Material Master Records for Deletion
For a material master record to be deleted by the
archive and delete program, it must be flagged for deletion. Please read
flagged for archiving when seeing marked or flagged for deletion in SAP.
You can set deletion flags at different organizational levels, for example, at plant level or/and at sales organization level.
The material master record is then marked fordeletion at this level and at all lower levels.
How to do it technically?
You set a deletion flag at client level. Since it is the highest hierarchy level, the material master record is deleted at this level and at all lower levels.
(pictures showing the screen before and after execution)
Means, this material master record is globally marked for deletion (e.g. for the existing organisation levels Hamburg and London, but as Italy would as well get a message when trying to extend this material for their organization.
You set a deletion flag at plant level. Since it is below client level, the material master record is marked for deletion at plant level and at all lower levels (for example, at storage location level), but not at client level.
Means, this material master record is only for Hamburg plant marked for deletion, London is still active and Italy can extend this material master to their organization without any trouble.
Even the other Hamburg organization levels like Sales Org and Warehouse are still active in the example. This situation can occur when moving the production to another site. Hamburg sales organization can still sell material (shipped from another plant) , but the Hamburg plant cannot produce or store it.
You set a deletion flag at storage location level. Since it is below plant level, the material master record is marked for deletion at storage location level but not at client level or plant level.
Means, in this material master record only a certain storage location is marked for deletion, all other storage locations are still active.
Setting a flag for deletion will usually just trigger a warning message whenever the material is used. E.g. in material master maintenance or when doing goods movements.
This warning message will not stop you from doing what you want to do. It is supposed to make the user think if he is using the correct material or not.
If you want block a user from using this material master in any transaction, then assign a material status to the material master.
The material status is a customized status, that can restrict certain activities and allow others ( e.g. restrict procurement but allow material movements like goods issues, or block any transaction for this material)
A material status can be set at general level, and affects all plants that share this material master, or you set the status only for a specific plant at plant level
in material master.
Example for general level, status is set at basic data 1 view. You can add a date from which on the status becomes active. This date field is right of the status field
Example for material status at plant level only :
If a user uses a material that has a status which restricts the activity he performs, then he will receive an error message: