Dear Forum Members,
In SAP Active Global Support, we are underway with a project to simplify the component selection process for our customers. From our analysis of customer feedback and usability studies, we have found that customers have difficulty in navigating through the component hierarchy tree, and as such, often end up choosing incorrect components. We will therefore be reducing the number of NW Java components visible to customers.
Based on an analysis of incoming message volume, 112 components have been selected for hiding because of a lack of usage, or because they could be easily absorbed by other areas or parent components. see the list below which shows the components which will be hidden.
The reduction of components will assist us in Support as less component granularity leads to swifter and easier dispatching. Secondly, the reduction will pay dividends on the SMP Message Wizard as fewer components being proposed to the customer in the SMP means easier component selection and increased satisfaction.
We plan to introduce component hiding from Thursday, the 26th of January 2012.
The affected components which will be removed from the SMP Message Wizard list are listed in [this Wiki page|http://wiki.sdn.sap.com/wiki/x/-Ia1Dw].
Furthermore, we will use this thread and the mentioned [Wiki page|http://wiki.sdn.sap.com/wiki/x/-Ia1Dw] to inform you, our customers, of any updates to the NW Java component hierarchy as and when we have such details.
Please feel free to post any comments or queries related to this topic and we will respond at our earliest convenience.
SAP NW Java Moderators
Thanks for the positive feedback for the initiative. Regarding the Notes, they won't be affected, since the components still exist and can be used internally.
In the vast majority of cases, the hidden components are replaced by their parent components. This does mean that when carrying out a Note search, it's a good idea to search on a component and all its children, using the '' wildcard character, e.g. to search on EP-PIN-APF rather than on EP-PIN-APF (Service Marketplace data tells us that customers actually tend to use more generic searches like EP-PIN* or EP*).