
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2022 03:21 AM
We know that application services is related to service offerings (technical & business)
For report purpose I'd like to have a list of Service offerings grouped by Application services.
But unfortunately, i can not found the table which support this relationships.
Have you any idea?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2022 03:36 AM
The relationship table should contain these information. (cmdb_rel_ci)
The parent should be the service offering. The child should be the application service. Over dot-walk in the filter you would need to filter based on the class of the parent and the child.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2022 03:56 AM
thank you for your answer very clear and detailed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2022 03:37 AM
Hi
The main reason to use a cmdb relationship between service and service offering was to be able to show it on the dependency map, though this is not really needed, as you can just use "map related items".
First, a little background
Services have probably been part of the CMDB structure from day 1 of ServiceNow. They end up being referenced in many ways and by many things. One data element of a service is the “Service Classification” field. Historically this field included some odd values like “infrastructure,” “billable” and others. Notably, one of those odd values was “Service Offering.” My understanding is that originally there was no Offering table, so that “Service Offering” value was needed.
Services vs. Offerings
But eventually a Service Offering table was added to the CMDB, inheriting from Service. This layering gave a more useful structure. A service is defined with respect to how it enables and is used by the business, that is, what outcomes, capabilities, or process does it support? Then, child offerings can be defined that are particular variants of that service. You may see offerings like Gold, Silver and Bronze in the demo data as examples of service variants. We think of services really as “containers” of offerings and we recommend every service have at least one offering as good practice.
Also, refer to this PDF to get a pictorial understanding:
https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/success/quick-answer/services-service-offerings.pdf
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2022 03:52 AM
Thanks for your detailed and prompt answer. It's very helpful for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2022 06:59 AM
Hello,
I know this has already been marked as answered but there is another table (svc_ci_assoc) that we use to understand all related items, manual and discovered, to a service. You can run queries on this table much like the relationship table but typically doesn't contain as many relationships as the cmdb_rel_ci because the cmdb_rel_ci table contains all horizontal relationships, which could impact the performance of your report.
Thanks,
Jeff

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2022 07:10 AM
Hey,
Related to performance this doesn't need to be correct, because the svc_ci_assoc contains also the relationship between dynamic ci groups and CIs. And these could be much more data depending, how many dynamic CI groups your are using. So I would say it really depends on your CMDB and the data, which are stored in it.
Kind regards
Sebastian