01-24-2013 9:38 PM
Hi,
We have an SAP ECC6 system with EHP5 which has been in use for several years and was recently upgraded from 4.6C.
This system has been in use for several years and now business drivers require activation of BFS DIMP.
I have searched OSS, these forums and internet at large for a discrete list of what is changed upon activation.
Anything that can get us started in the right direction in terms of the analysis.
Perhaps a discrete list of affected processes, programs, transactions, tables etc ...
We fully realize thet the exact impact will be specific to our system but we are looking for a starting point.
Any help would be greatly appreciated.
Ricky
01-29-2013 3:47 PM
You could check at SAP Help: Discrete Industries and Mill Products
In short, the industry extension provides:
Actually it is possible, and quite common to "add" Mill Products functionality to ERP. This does not require a new client or installation.
In customizing you activate the Business Function "DIMP_SDUD". See SAP Help.
Points to consider
01-16-2014 12:37 AM
Hi Stefan,
Can you please add some information to your previous comment?
We use the core ECC BF and would like to use BOS without activating the entire IS_DIMP; i.e. only the component DIMP_SDUD.
However when I try to do so, I get few errors pointing that I also have to activate:
PSCD; PSCD_Settings; ISHERCM_MAIN and ISHERCM_Settings.
However, there is no indications as a prerequisite in the DIMP_SDUD or in any of the other listed components.
1. Is this a necessity, or there is other way to activate DIMP_SDUD?
2. If I still have to activate the other components, are they as well do not require a specific licences?
3. Should I expect any restrictions?
Kind regards
Hadas C.
08-12-2014 4:31 PM
Hi Ricky,
we are now in the same situation like you more than one year ago:
We have an SAP ECC6 system with EHP6 which has been in use for many years and now we want to activate DIMP_SDUD. I have also searched the internet to find a list of effects, but nothing is there. Now I found your question in here and I am keen to know, if you activated the function in the meantime. What is your experience on it?
Have you created a list of affected processes, programs, transactions, tables etc ... ?
I am looking forward to hearing from you 🙂
Lisa
08-12-2014 9:17 PM
Hi Lisa,
In that client's case, we were succesful in activating DIMP_SDUD as well as several other business functions.
It is imperative that you execute your activation in Client 000 and harvest and analyze the logs to confirm what happened. Any intersections with customer changes to SAP code will cause the activation to stop since the program cannot be modified because of a changed origin. This is quite similar to a Support Pack condition. However, we found several areas where configuration was impacted and this guided our testing which was similar in nature to what you would do following a support pack.
Please note that most of the new configuration used to drive the new processes will be in Client 000 only and will need to be copied over to your development client. Total run time for activation in development for activation was just over two hours. In QA and PRD it was much quicker because we used a transport to migrate the activation through the the development path.
The cross system compare tool and Excel will become your best friends 🙂
In our case we did 3 full runs in the sandbox before we developed and understood our recipe.
Hope this helps encourage you to proceed. Do not hesitate if you have more specific questions.
Ricky
08-22-2014 2:50 PM
Hi Ricky,
thank you very much for your immediate answer!
We will discuss internally if, how and when we will proceed with the DIMP_SDUD activation. Your answer will help us to start this discussion. I might come back with some more questions, when we start the project.
Thanks and best regards
Lisa