cancel
Showing results for 
Search instead for 
Did you mean: 

Configurable Stage at Sub Assembly Level MTO scenario

shailesh_mishra5
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Experts,

Need your help and support on below Issue.

Customer is a rubber based Belt and Sheets manufacturers. They are on SAP already but facing some extreme challenges as business is not mapped as per their exact requirement. They are not using Variant configuration as of now

The core problem of client is that it has 8 alternate BOMs at SFG level and whenever a characteristic change in dimension happens, a new Assembly material is created with new version of BOM. Unnecessary BOMS and assembly Materials goes on increasing due to slight characteristic dimensional change.

They have 11 operation to produce the final product. But during the 6 stage known as Calendering, where the assembly being produced, have 8 alternate BOMS.  This is technically a Configurable material.( They are not using VC)

Right now they are facing huge Material Stock variances as Materials.

Can you please help how they can overcome this problem? Right sets of BOM explosion is not happening in production order due to which there is huge material variance in their plant.

They want a solution for this!!!

Best regards

Shailesh Mishra

Accepted Solutions (0)

Answers (2)

Answers (2)

Ritz
Active Contributor
0 Kudos

As its not VC , by moving it to PP forum you will get more favorable replies.

.

Thanks

Ritesh

kiran_kumar179
Active Contributor
0 Kudos

Shailesh,

They have 11 operation to produce the final product. But during the 6 stage known as Ccalendaring where the assembly being produced, have 8 alternate BOMS.  This is technically a Configurable material.( They are not using VC)

So after 6th operation they are cutting down production to receive SFG right? have not they mapped Routing with 6 operations for SFG and at 6th stage auto GR?

for remaining 5 operations they can have in FG Routing.

For alternative BOM issue I suggest they should implement VC so that mass maintenance of master data can be reduced and also frequent changes in BOMs also rectified.

BR
KK