Catalog Item to Service Offering m:m

Robert80 · ‎11-10-2022

Howdy

Is there a reason why the data model only allows mapping a catalogue item to one service offering?

For context, I have a catalog item which is used to request access to an application service. Users can request access to either production or training environments on the same form. I have an offering for production and an offering for non-production because they have different availability KPIs.

It would be helpful to map multiple offerings to one catalog item and I'm not sure why it's not available OOTB.

Barry Kant · ‎11-11-2022

I understand the concept, but in my opinion the catalog item is a construct to facilitate a Service Offering.
When it is 1:n (as is now) it blocks the option to standardize the catalog as such. With 1000 applications you might have a high repeating number of catalog items because it can be linked to 1 offering.
It has a huge maintenance effect and a huge performance impact.
And a usability impact. Users will not find the catalog item needed.

Catalog Items can be flexible/dynamic and still serve the same purpose. It doesn't need to tie to a single service offering. (not necessarily)

View solution in original post

Nils Pokorny · ‎04-24-2025

It seems like this issue is finally resolved with Yokohama.
The business rule "Validate new Offering Catalog relation" on table "sc_cat_item_subscribe_mtom" no longer exists in Yokohama.

Robert80 · ‎04-27-2025

Thanks NIls, this is good to know.