Skip to Content
Technical Articles
Author's profile photo Chih-Hao Huang

How to upload scope item per LoB to SAP Cloud ALM with DDA

When implementing S/4HANA Cloud (public edition) projects, SAP Cloud ALM (CALM) is the recommended tool to manage projects. In terms of managing project scope, there is a scoping exercise where you have to select the relevant business processes. While it is flexible to define scopes (e.g. based on country, functionalities, sites with own tenants, etc.), there could be a scenario where the project manager wants scopes to be managed per LoB. This blog is to give you a hint how to achieve this with your DDA (Digital Discovery Assessment) output.


Users are able to create scopes by manual selection or file upload. As the project scope has been already discussed with customers during the DDA process in pre-sales phase, it is best practice to bring those results into the Cloud ALM tool for implementation.


Nevertheless, scope items downloaded from DDA tool does not include any LoB(Line of Business) information and during import in CALM, it is created as a single scope. For project managers wanting to define scope per LoB (i.e. sales, finance, supply chain), there should be a workaround.


In the following I am going to show you how to upload scope items per LoB (Line of Business) to SAP Cloud ALM (CALM) with your DDA output.


Given current system restrictions, we have to manually prepare scope item files per LoB and upload them to the Cloud ALM tool. Although additional manual effort is inevitable, it is still far more efficient than manual selection.


Now we assume the scoping process in DDA is done.


step 1: download scope item file from DDA

step 2: open the file and add one additional column “LoB”

step 3: Download scope item list from Best Practice Explorer. We need to use this file to help us divide scope items into LoB.

step 4: Open the scope item file and copy these 2 columns to the DDA file.

step 5: In the DDA file: copy the scope item ID and LoB into an additional sheet.

step 6: Use excel function “VLOOKUP” to find the LoB against the scope item ID.


Now we have the scope item with LoB designated.


step 7: Filter the LoB to get the scope items and copy that into a new file.

Note: In the new file it is important to keep the 1st and 2nd rows like the screenshot shows.

Below is the file for finance and sales respectively.

Repeat the same step to copy scope items into a new file per LoB, e.g. service, supply chain, etc..

step 8: Go to SAP Cloud ALM and create scope from file.

step 9: Type scope name and upload the new DDA file we just prepared. Press review and create.

step 10: Press process scoping


step 11: The system shows all the available scope items. Choose end scoping.


Now the 45 finance scope items are selected based on our file.


step 12: Repeat the same steps for sales.

44 sales scope items are created.

Now we have successfully divided scope items per LoB with the file from DDA.


Thank you for your reading. Please feel free to leave your comment and feedback! 🙂


Useful blogs and links to CALM

End to End Story for Implementation in SAP Cloud ALM


Next steps

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Jim Mueller
      Jim Mueller

      Whats the benefit of adding LOB to the Scope in ALM?  For filtering or anther process reason?

      Author's profile photo Chih-Hao Huang
      Chih-Hao Huang
      Blog Post Author

      Thanks for raising this question. Let me explain the reason there. Since some partners have stream leads (finance, sales, procurement…) in their projects, it might make sense for them to divide scopes into LoB in the scoping process. So each of the team can conduct F2S and following activities based on their own scopes.

      CALM has the upload functionality and it could make sense to divide scope items into separate LoB files in advance and then upload to create scopes. You can compare of having a big scope with N scope items from different areas vs. LoB scopes with respective SIs. Below I have an example of having upload SIs by LoB.

      Also, for each scope CALM will create F2S related activities. Without dividing the scopes, you will have only 1 set of F2S activities for all SIs. Based on my above scopes, I have the following activities automatically generated.

      CALM is flexible with scoping, it is more for a project team to see which makes more sense to manage projects. Hope this answers your questions. Any further feedback is welcome.

      Author's profile photo Marko Tödtling
      Marko Tödtling


      Thanks for your effort and sharing this information with the community!

      Here are my two cents..

      After moving Best Practice Explorer site to, the file Availability_Dependencies_EN_XX.xlsx (in this blog found under Availability and dependencies of scope items on the SAP Best Practice Explorer site) can be downloaded within a bundle.


      SAP for Me

      After the extraction of the files you can find the file in the following location SAP_Best_Practices_for_SAP_S_4HANA_Cloud/ S4C / Library / General.

      Now you can proceed with the step 4 stated in the blog.