on 2012 Jan 07 11:31 AM
Hi Experts,
Actually we extended one material code with wrong valuation type, now we want to block that valuation type not the material code, I am using MM06 but I am not able to block only valuation type. We want that we can use the correct valuation type not the wrong valuation type. But when I am blocking material code using MM06, some time material is blocked at plant level or storage location level, but we want only valution type block not storage location or plant block. How achive this.
Regards
Ishu
Hi, workaround you can do is open the material in MM02 giving proper valuation type which you want to block and maintain the field "Plant-sp.matl status" in Purchasing view for blocking the material for further activity.
In this way your material with specific valuation type will only get blocked, you can use the same material code having different valuation type as you want,
Similarly for blocking for other activities also maintain status in fields,"P-S matl status" in Work scheduling view if view maintained & "X-distr.chain status" in Sales: sales org. 1 view also,
You can make a new status in T-code OMS4, where you can make new entries & maintain the fiels with values 'B' every where, maintain this 'Material Status' in all the above mentioned field in Material master for the particular valuation type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If its wrong valuation type then you used that valuation type anywhere other than this material?
If not used anywhere,then try this you can deactivate this valuation type in configuration OMWC t-code for your plant.
Regards
Kailas ugale
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
but this does not make the wrong created material master view going away.
And it may create problems when you later really want archive. as many archive programs are checking the correctnes of the data against the customizing. Never delete anything from customizing what isanywhere used, rename it to "do not use".
I am currently migrating SAP to SAP systems, and I often have errors because of deleted customizing in source system but master data still has the values.
unfortunatly there is no option to block the usage of a wrong created valuation type.
Setting the deletion indicator does not stop a user from using this valuation type.
You have to archive this valuation type org level using SARA object MM_MATNR
you have to test if your system is able to archive certain org levels of a material or if it only allows to archive the entire material.
If you cannot archive the valuation type only, then you have to implement an OSS note to make it possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
8 | |
8 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.