Service hierarchy for SRM-MDM catalogi scenario

Question

Hello,
We tried setting up the 'new' SRM-MDM service hierarchy catalogi. I've looked over some sdn threads already and read the SAP help http://help.sap.com/saphelp_srm70/helpdata/en/6b/7fb967f6cd4df0a5a9d5dec7e4aa72/frameset.htm. Both told me the service hierarchy should work in the SRM 'bidding/RFx' scenario. Since service hierarchy should work for RFx we continued trying setting it up but ran into the following problem:
Up on opening our service hierarchy catalogi it returns the following message 'Table is empty' and does not show us any items(mss hierarchy is enabled in the SRM-MDM UI configuration for this catalogi). If we change thé UI setting to 'products' the items do show-up in a 'flat' manner (without hierarchy).
- We've set up grouping in the SRM-MDM catalogi for these items
- We've set up an entry in the MSS hierarchy lookup table and assigned this entry some of the catalogi items
- We've not setup any MSS Hierarchy price
- We've setup the item types, the outline item is of type 'MSS header' the subtypes are of type 'Free Text' and the MSS hierarchy entry is of type 'MSS header' aswell.
- we've setup the hierarchy manually with testdata via the important manager (no pi/ix).
Could anybody confirm service hierarchy works in the RFx scenario (mss hierarchy enabled)? Is there something we've missed or are forgetting? Any other pointters are greatly appreciated.
Kind regards,
Tim

Answer 1

Hello Masa,
We have not loaded our service hierarchy catalogi items from ECC nor SRM. We've manually set-up test-date via the import manager and data manager tools. This, as long as you set it up correctly, should still work in my oppinion?
For the UI configuration the service (mss) is enabled causing the 'empty table' line to show up. If we would change it to 'product' the items would show but in a flat manner.
Do you have any other pointers . F.e. what the item types should be (subitems: free-text and header: mss-header) and what the role of the mss-hierachy and mss-pricing table are and what we should do with those?  We've configured grouping (main item, component item, substitute item ..) to enable hierarchy is this correct?
Ps. What does 'MSS' stand for, what does it mean?
Kind regards,
Tim