How to connect Service offerings subscriptions with Service catalog

[JohannesGP]

We are starting to use Service Portfolio Management to mange our customer subscriptions.

Now we would like to connect it to our Request catalog. Making items to display depending on Service offering Subscriptions.

ServiceNow is talking about this in the Request Catalog. I can't figure out the last sentence is supported "Each catalog item is linked to one service offering"?

Any help on how to get us working with this would be much appreciated. Thanks

Posts already read:
Can you link Service Portfolio / Service Offerings to Catalogue Request Items?

[Sameep Kodia · Accepted solution]

The name of the table is sc_cat_item_subscribe_mtom. Associate offerings to catalog items in this table. Make sure consumers of the offerings are added to SPM subscription tables.

P.S. - Please mark the answer helpful if it did!! 

[JohannesGP]

Thanks Sameep,

Thank you very much for point this out. Now I understand how Service offerings and Catalog items are connected. Thanks!

Testing this. Can't figure out how it's connected to the Service portal, so users only are showed Catalog items, which is related to a Service offering that the user is subscribing to.
User still sees all Catalog items.

We are using the standard SP Service portal.

[Eivind Sandnes]

We have the same issue for a customer;

When relating a Catalog Item to a Service Offering, the Catalog Item is not visible to the end-user.

Our difference is that when we add a user to the Subscribe-list, it is still not visible in the portal. Only when we add a "Available for"-criteria it is visible in the Service Portal.

[JohannesGP]

Thanks for your comment Eivind,

How does your User criteria look like?

We are still trying to find a general solution for whenever a User/Company Subscribes an Offering, that Offerings related items is shown to the user.
We tried doing a User criteria, but was only able to succeed creating a User criteria per item. Which I don't like.
We are now trying to limit access based on Business rule - which is not optimal, but might be functional.