Now I apologize, because the title of this post might suggest that you can actually accomplish this feat. Unfortunately, to the best of my knowledge, you cannot dynamically change plant based on the configuration. In my experience, this was always a no-no. Now if anyone has actually gone down the user-exit approach and made it work, I’d be curious to hear it. In the meantime, here are some approaches to potentially help you… or at least give you some ideas of your own to change plant for a configurable item based on the configuration.
The biggest problem is that you get to choose one plant for each sales organization to be the default. And even using configuration, it doesn’t matter if something within the configuration can only be done in Plant 0002, but Plant 0001 can do everything else (and should). That being the case, here’s some approaches/techniques that may help.
1. Multiple KMAT’s. This is probably the most common/standard approach to change plant for a configurable item. You can have one KMAT for each different plant. You can reuse all of the dependencies, and create new configuration profiles etc. Now the drawback to this approach is that you have to know in advance which product you want to manufacture.
2. Use special procurement keys on a sub-KMAT. Here’s the idea. Set up your main KMAT A. In the BOM add 2 SUB-KMATS, X & Y. X will be the standard produce here in house (whatever plant is listed on the sales order). Y will be a KMAT with a special procurement key pointing to the other plant. Then using object dependencies select either X or Y. I admit, I’m pulling this one out of my ass, so if anyone knows if this does or doesn’t work, let me know. It sounds promising, but I have my doubts it would actually work =).
3. Material Determination – this is a handy trick that could be used to make #1 easier for the sales order entry folks. What you could do is create something “meaningful” to the entry people, that they could type in and it pull up the second KMAT in another plant. For example it could X – Express, would pull up the KMAT with the least number of options that would be shipped the fastest.
4. User Exit – you could always go down the path of adding new entry into VCSD_UPDATE for werks and using User-exits, drive the plant change this way. Like any good SAP consultant, this is always the last resort, but for my current project, this may be the way we have to go. Based on a little online research, it appears you’d want to use the following: VCSD_UPDATE and transfer the changed values from the configuration to the sales order: EXIT_SAPLCEI0_001 (include fields in structure VCSD_UPDATE) EXIT_SAPFV45S_002 (process changed field values)”
Now, all that being said… option 2 would be the coolest way to “possibly” do it with standard SAP, but I have a feeling that #4 is only way to accomplish a change plant based on configuration.
Thanks for reading,As always, thanks for reading and don't forget to check out our SAP Service Management Products at my other company JaveLLin Solutions,