That's not quite how it works.
You'd actually put the Business Service in the Configuration Item field.
Once selected, you should then see a Dependency View icon appear, clicking that should show you a Dependency Map, which allows you to see all Incidents open on the related CIs to that Business Service.
There is also an Active Tasks icon there (explanation point), that will bring up a list of open tasks impacting that Dependency tree as well.
The purpose of both of these activities, is to allow the Service Management person to quickly diagnose if the requestor is being impacted by an existing Incident / Task on a related CI.
You wouldn't normally select a Business service, and then want to create a list of EVERY downstream CI that is impacting that service. Just because someone is opening a ticket on "SAP Enterprise Services" doesn't mean that every CI downstream is being impacted, quite the opposite. There is probably only a single CI that is causing the interruption of the primary Business Service. In that case, it would be revealed via the Dependency Map, or currently active tasks. You can also right-click on a CI on the map and see "View Affected CIs" to get a list.
The Impacted CIs is for the reverse of your use case. You open a Change (or an Incident) on a specific CI, then you want to see the dependencies present UPSTREAM from that CI that are impacted. In that case, the specific CI in question was automatically placed in "Affected CI" and then you can refresh the Impacted CIs to populate those.
Here, I enter SAP Web01 as the CI for the Incident, and it's automatically placed in Affected CI (you can add more manually or from the Dependency Map).
Once all of the Affected CIs are in your related list, then you "Refresh Impacted Services" and that populates the list:
Hope that helps.
The answer to your question is that any of the "Depends on", "Runs on", "Used by", "Exchanges data with", dependencies will work for this. You can see those on the Relations area of the specific CI in question (in this case SAP Web01):
Hope this helped.
-Rob
That's not quite how it works.
You'd actually put the Business Service in the Configuration Item field.
Once selected, you should then see a Dependency View icon appear, clicking that should show you a Dependency Map, which allows you to see all Incidents open on the related CIs to that Business Service.
There is also an Active Tasks icon there (explanation point), that will bring up a list of open tasks impacting that Dependency tree as well.
The purpose of both of these activities, is to allow the Service Management person to quickly diagnose if the requestor is being impacted by an existing Incident / Task on a related CI.
You wouldn't normally select a Business service, and then want to create a list of EVERY downstream CI that is impacting that service. Just because someone is opening a ticket on "SAP Enterprise Services" doesn't mean that every CI downstream is being impacted, quite the opposite. There is probably only a single CI that is causing the interruption of the primary Business Service. In that case, it would be revealed via the Dependency Map, or currently active tasks. You can also right-click on a CI on the map and see "View Affected CIs" to get a list.
The Impacted CIs is for the reverse of your use case. You open a Change (or an Incident) on a specific CI, then you want to see the dependencies present UPSTREAM from that CI that are impacted. In that case, the specific CI in question was automatically placed in "Affected CI" and then you can refresh the Impacted CIs to populate those.
Here, I enter SAP Web01 as the CI for the Incident, and it's automatically placed in Affected CI (you can add more manually or from the Dependency Map).
Once all of the Affected CIs are in your related list, then you "Refresh Impacted Services" and that populates the list:
Hope that helps.
The answer to your question is that any of the "Depends on", "Runs on", "Used by", "Exchanges data with", dependencies will work for this. You can see those on the Relations area of the specific CI in question (in this case SAP Web01):
Hope this helped.
-Rob
