Skip to Content

You like Solution Manager? You love innovative solutions?

Let’s say you have implemented Solution Documentation 7.2, and you really like it. Now is the time to start documenting your Solution, but building it up from scratch is difficult and time-consuming. Besides you never know how “good” your processes are compared to your industry. You can generate executables and custom objects automatically in your Libraries, but the Reverse Business Process Documentation capability is gone. There is no way to do it in the 7.2 version.

Oh wait, there is. If you are among the customers using S4/HANA, then you can leverage the “Best Practices Packages” feature and import pre-documented processes, including diagrams, fiori apps and configuration units assigned at the right level, in Solution Documentation 7.2. It is really something. But hey, what if you have not migrated to S4 yet?!

Well, have a look at SAP Note 2418929. Not many know about it, but this makes pre-7.2 RDS content available for the new 7.2 version of Solution Manager. For starters, here are the two (2) options that were available to you in the past, but since have been replaced by SAP Best Practices Explorer:

  1. SAP Best Practices RDS Packages: Based on successful software deployments, these solution packages cover the entire SAP portfolio and offer best practices for a wide range of processes and topics. This helps customers to standardize implementation projects (ie. functionality specific to your line of business), and reduce go-live risks and costs.
  2. Business Process Repository: This is an old functionality within Solution Manager 7.1. It provides a central overview of the available Reference Content structured both by organization areas and available solutions respective applications and underneath by business scenarios, business processes and process steps.

Now, back to SAP Note 2418929 (SAP Solution Manager 7.2: Get SAP Best Practices RDS Packages and content from Business Process Repository (BPR)). The note provides you with a list of all RDS packages and BPR content that have been converted to .JSON format so far. This is the only format supported by Solution Manager 7.2 when it comes to content import.

Here, you can see an example of ERP7 ECC 6.0 RDS packages, including regional releases. You also have Best Practices for other products (CRM, SRM..), and even business specific packages (Payroll Processing, SuccessFactors Compensation..).

SAP ERP607 for Baseline Germany (DE) V3
SAP ERP607 for Baseline United States (US) V3
SAP ERP607 for Baseline China (CN) V3
SAP ERP607 for Baseline India (IN) V3
SAP ERP607 for Baseline Brazil (BR) V3
SAP ERP607 for Baseline Canada (CA) V3

Once the content imported to your Solution Manager (follow the steps in the SAP Note), you will have pre-documented SAP standard processes (FI, SD, MM, etc.) for the target product. This includes, for example:

  • Business Processes
  • Process Steps (incl. in the Library)
  • Process diagrams
  • Configuration Units
  • Standard Transactions
  • Best Practices URL documents

Have a look at the “Make-to-Stock Production (Discrete)” process for ERP ECC 6.0:

So, you have these brand-new SAP processes documented in your Solution, what now? I highly recommend you to follow the SAP Activate guidelines. RDS content is an accelerator, not the end result. The next steps could be organizing validation workshops, adapting some processes, building custom ones, etc.

The work begins!

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Sateesh Volimineni1


    Yes, SAP Note 2418929 assists in loading best practices and import pre-documented processes, including diagrams, fiori apps and configuration units assigned at the right level in Solution Documentation 7.2.

    Does it serve the purpose for others who are yet to migrate to S4 HANA ?

    Either we need to start from scratch by creating business process structures and then schedule library generation cockpit or import best practices for ERP and design as per customer standard and release to PRD branch as suggested.



  2. Alexandre SABATIER Post author


    This SAP Note is specifically designed to help you document standard non-S/4 processes. It is a bundle of the RBPD and RDS content from Solution Manager 7.1. You don’t get as many items as with S/4 BP packages (ie. diagrams will not be fully documented), but it is a great starting point.

    You should first (1) decide which packages are to be imported (the more you want to import, the more time it takes to adjust the SLAN system landscape), (2) import the content and verify its integrity, and (3) release it to another branch and start making customer adjustments.

    PS. You can import S/4 HANA Best Practices packages, even though you don’t have any S/4 system connected to your Solution Manager yet.


  3. Dinesh Ghanta

    Hi Alexandre SABATIER,

    Thanks a lot for the blog. This was very useful in importing the RDs packages in our SolMan system. We are facing an issue. All the Document URLs which are created in the RDS folders are pointing to the wrong URL and we are getting a message that the page is not found. Is there a way to fix this issue.

    Thanks and Regards,

    Dinesh Ghanta

  4. Mark Dickhoff

    Thanks for the great post.  When importing BPR content — are we going to have to duplicate all the source logical component groups?  A single file has up to 30-ish groups and the importer does not allow different source groups to be assigned to the same target group.  Just wondering what the best practice would be if we’re importing multiple BPR files with multiple overlapping groups in these files.  And maybe this is a good opportunity to create a one-off solution with all the noise implemented so you can weed out what org units and groups are relevant?  I like having the full BPR at hand but was wondering if you need a hundred or more groups created to get it all in?

  5. Alexandre SABATIER Post author


    You will not end up with duplicates in the case of overlapping LCGs. However, you will end up with a lot of useless LCGs if you choose to import all the BPR contents.

    Besides, you should be careful if you plan to go to S/4 at some point. Some processes (ie. Accounts Payable) exist in different BP packages, but are not exactly the same. I would recommend to start documentation these processes based on S/4 BP content, and attach the ECC executables to the steps manually, until you actually do the upgrade. You would benefit from both.

    Your idea of having a “fake” solution for import is indeed interesting. You could build the documentation there, then export the final content to a new Solution. However, I feel that having 3 branches to handle the import cycle (Development -> Design -> Import) is quite the same.

  6. Mark Dickhoff

    Thanks for your response Alexandre.  I appreciate your suggestions.  The separate solution idea is an attempt at not having to add any noise around import LCGs polluting our “main” solution and our valid LCG’s.  i.e. 30 source LCG’s in an import file need 30 unique destination LCG’s in the solution.  As you suggest we can focus on S/4 content but it would be nice to have this info as a reference still 🙂

    On another note I was about to raise a support note on imports.  I’m getting an import error on my second file.

    Job log overview for job:    SMUD_CONTENT_IMPORT / 10544900

    Job log    Time     Message text uncoded                                                                     Message ID Msg.typ

    07/21/2017 10:54:49 Job started                                                                                  00       516      S
    07/21/2017 10:54:49 Step 001 started (program SMUD_CONTENT_IMPORT, variant &0000000000004, user ID )     00       550      S
    07/21/2017 10:54:53 2gd7shzO7kQlhiZwNuPqSW_CONTENT_OFF_ATTR_WDYAPPCONFIGID_TO_LONG                               00       001      S
    07/21/2017 10:54:53 Content import failed                                                                        00       001      E
    07/21/2017 10:54:53 Job cancelled after system exception ERROR_MESSAGE                                           00       564      A


Leave a Reply