Block empty D.Chain spec. material status (SalesOrg1) in Sales doc

[Former Member]

Hello, At our company we added some new status to the Distribution-chain-specific material status. While doing this, we also changed the ' ' (empty) status which is also customisable I changed all the settings to 'B' (block) to prevent Materials with this status to Sales orders. This should block materials which are not 100% correct implemented in our organisation, as masterdata is not complete. Unfortunately after implementing the change in our test system it doesn't work. The system doesn't recognise this empty status and as a result, the material is still accepted in the order. Why is the empty status changeable in customising if this isn't recognized by the system? Or am I forgetting something? someone with experience with this? If any information, thanks in advance!

[VeselinaPeykova · Accepted solution]

Check the logic in FM RV_MATERIAL_STATUS_CHECK - it is called during sales order creation.

There is an additional check for FMSTA not to be ' ' and the validity date:

If you try to set this ' ' block with validity in MM02, you will receive M3 134 error, which means would not be able to save it with validity date. In this case the block is not considered as set at all your customizing will be bypassed.

Why didn't you just create a block e.g. Z1 and use MASS to update the relevant materials?

[Former Member · Accepted solution]

Thank you Vesilina. Why we didn't create an new status and convert anything? Because a lot of these materials aren't completely finished yet. For instance no Sales views created because they aren't sold. So we cannot fill another value. I was hoping by blocking the ' ' (empty) status, these materials would also be blocked.

[VeselinaPeykova · Accepted solution]

One approach could be to use listing functionality on a high level - eg. sales organization for the materials that are considered as OK (as you cannot use exclusion on sales area level for materials that are not extended yet) . Unfortunately this would mean more maintenance effort (in addition it may not work well in some scenarios), so it is not a really good idea.

Another possibility is to block whatever you can from the list (materials extended with sales views) and implement some sort of approval process (could be done with workflow or with transaction variants for example) to control the quality of master data maintained in the system and available for the sales team.

Without the corresponding sales views the products cannot be used for sales orders anyway - so if you use mobile devices or an external system for order entry, you can control what is distributed based on these block values.