Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9052

Variant configuration Error- Requirement Planning Run

$
0
0

Hi,

 

My client wants to sell a material with a service(NLAG).  There is one material that can be sold with
different service levels.  I suggested using
variant configuration so the material can be sold with a chosen service level.

 

Material: Computer

 

Service – Std., Adv., Premium

 

I have done the configuration and successfully tested order OTC scenario.  However, I am encountering an error(SAP error Message 61259, Material requires configuration) while running the requirement for a material marked for variant configuration. We are using Make to order scenario.

 

 

Material requires configuration

 

Message no. 61259

 

Diagnosis

 

Orders and requirements for a configurable material must
have characteristic values.

 

Usually, you should create a variation for configurable
materials managed in inventory management which has the default variant
configuration.

 

System Response

 

 

MRP: Requirements without characteristic values for a
material cannot be planned in MRP.

 

Procedure

 

Check requirements or orders.

 

Create a configuration evaluation for the material in the
material master record if necessary.

 

There is a BOM(raw materials) used for Production(BOM usage:production) and another BOM is created in SD(BOM usage: SD) for variant
configuration.

 

 

I would like to know if there is way to avoid the error while running the requirements planning.

 

 

I don’t want any impact on requirement planning run if the material is marked for variant configuration. Please note I have not done any maintenance for MRP view 3 related variant config.  and the configuration profile is only selected
for SD.

 

var2.jpgVAr1.jpg

 

Your guidance will be greatly appreciated.

 

 

Thanks,

 

 

Abdul


Viewing all articles
Browse latest Browse all 9052

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>