CSDM Walk - Run

[MirnaliR]

Can multiple service offerings be mapped to a single service instance? eg: there are many support groups managing various services related to SAP Successfactors.

[M Iftikhar]

Hi @MirnaliR, 

Yes, multiple service offerings can be mapped to a single service and it is a recommended practice within CSDM.

Here is a brief explanation:

• Service: Represents the overall business capability, the "what." In your example, the service is "SAP SuccessFactors." It's a single, logical entity.

• Service Offerings: These represent the specific, committable versions of that service, the "how." Each offering can have different support groups, commitments (SLAs), pricing, and availability. For your example, you could have offerings like:

  • SAP SuccessFactors - Payroll Support (Managed by the Finance Tech team)

  • SAP SuccessFactors - Performance Management Support (Managed by the HR Tech team)

  • SAP SuccessFactors - Employee Central Support (Managed by another specialized team)

This structure allows you to clearly define who supports what for a single, shared business service, while tracking commitments and performance separately for each area.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

[MirnaliR]

Thanks, multiple service offerings can be added to a single service. But can they be added to a single Application service/Service instance like SAP Successfactors Prod?

[Mathew Hillyard]

Hi @MirnaliR 

I think I confirmed this in my post above:

SAP Payroll Support Service Instance, connected to

• SAP Success Factors - Payroll Support Service Offering
• SAP Success Factors - Performance Management Support Service Offering
• etc..

I hope this helps!

Mat

[Mathew Hillyard]

Hi @MirnaliR 

I think you are asking about multiple service offerings connected to one service instance. There is no issue with this - it's commonly used where there are flavours of an app that do not have separate stacks themselves and where it doesn't make sense to create separate business applications.

However, as @M Iftikhar has mentioned, when looking at platforms or larger apps, this is more challenging because you can lose visibility of which apps are providing which services. SAP as a platform has many different application suites, each of which have their own individual apps. It is not recommended to nest Business Applications in a parent-child hierarchy, so you shouldn't create a parent SAP business app, then a child SAP Success Factors business app and finally a grandchild SAP Success Factors - Payroll Support business app.

It depends on how granular an organisation wants to go but you could model this two ways;

1) Granular (1:1 between Service Offering and Service Instance)

SAP - Platform Host Business Application

• SAP Success Factors - Payroll Support (Platform App Business Application running on SAP) - connected to
  • SAP Success Factors - Payroll Support PROD Service Instance, which connects to
    • SAP Payroll Support Service Offering
• SAP Success Factors - Performance Management Support (Platform App Business Application running on SAO) - connected to
  • SAP Success Factors - Performance Management Support PROD Service Instance, which connects to
    • SAP Success Factors - Performance Management Support Service Offering
• etc...

2) Generic (m:1 between Service Offering and Service Instance)

SAP - Platform Host

• SAP Success Factors - Platform App Business Application running on SAP
  • SAP Success Factors PROD Service Instance, connected to

SAP - Platform Host

• SAP Success Factors - Payroll Support (Platform App running on SAP) - connected to
• SAP Success Factors - Payroll Support PROD Service Instance, which connects to
• SAP Payroll Support Service Instance, connected to
  • SAP Success Factors - Payroll Support Service Offering
  • SAP Success Factors - Performance Management Support Service Offering
  • etc...

My preference would be for option 1 but I've seen organisations use option 2 - typically when at a lower level of CSDM maturity.

I hope this helps!
Mat