Skip to Content
0

Impact if we dis enable the costing view at material type config level for existing material type?

Jan 24 at 08:53 AM

27

avatar image
Former Member

Dear all

Need your support clarifying below aspect.

We have a service material meant for external operation purpose. By material type configuration wise it is enabled with costing view. However, in practice, do not have the costing view opened during material master creation. We have thousands of materials in this material type and many of them are with existing purchase requisition (about to convert to PO) and many of them are with existing purchase order (about to have GR).

During recent month end costing run, by mistake. all these materials were automatically added with costing view but with no cost. This caused the error in all those materials while undergoing subsequent transaction like...PR to existing PO conversion and during GR to PO stage.

Per my understanding, it is not possible to dis-enable the costing view at material master level. correct me if I am wrong.

Question here is .....at this time, is it possible to dis enable the costing view at material type configuration level? and if we do so then will it resolve our current issue? ( like error during PR to existing PO conversion and error during GR to existing PO). and would there be any other impact?

Regards

Venkatesh Kannan.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Dibyendu Patra Jan 24 at 09:45 AM
0

If material has the costing view, then it should not stop any transaction like PR, PO or GR. You should investigate the issue further.

Diisabling the costing view from material type does not remove costing data from material. During creation, these all materials are already updated to the costing data. Disabling from material type is just to not to see the costing view during creation or change or display.

Share
10 |10000 characters needed characters left characters exceeded
Jürgen L
Jan 24 at 09:48 AM
0

You should have posted the error message (along with message number) which you actually receive in the follow-on functions.

Removing the costing view from the material type will not remove any data that was already created, it just creates an inconsistency since you have data and can't access it.

This OSS note explains how you can stop the automatic creation of costing views: 545585 - Preventing automatic creation of the costing view

Share
10 |10000 characters needed characters left characters exceeded