Solution documentation in solution manager 7.2

[Former Member]

All,

We are upgrading solman 7.1 to 7.2 next month and we do not have solution documentation yet on 7.1 but once we upgrade to 7.2 we want to use fresh solution documentation in 7.2.

Blueprint Generation Report do not exists on 7.2 so I assume we need to setup business process structure manually under process management.

Do we have other options where we can get business process strucuture automatically in 7.2 ?

Thanks

Sateesh.

[prakhar_saxena · Accepted solution]

Hi Sateesh,

Yes we don't have RBPD anymore in Solman 7.2 but you can use library generation cockpit as of now.

https://help.sap.com/saphelp_sm72_sp03/helpdata/en/14/90f55473b5f51ee10000000a441470/frameset.htm

https://uacp2.hana.ondemand.com/doc/60943adf3ff44893b62c568bb8a87d17/7.2.04/en-US/1490f55473b5f51ee1...

hope this helps

Thanks

[Former Member · Accepted solution]

Hi,

Library Generation Cockpit is only for executables and development elements but not for automatic generation of business process structure

So I assume we need to setup business process structure ( Process step library ) manually and then schedule library generation accordingly.

Thanks

[prakhar_saxena · Accepted solution]

Yes, this is what I meant..please read the documentation in detail.

Thanks

[Former Member]

Hi,

Please see Note 2418929 - SAP Solution Manager 7.2: Get SAP Best Practices RDS Packages and content from Business Pr....

The above note contains Rapid deployment packages that can be imported to your Solution in Solman 7.2.

See also - rapid.sap.com. here you'll find deployment packages for various scenarios which could be imported into the Solution.

The packages contain (for the respective scenarios) all the relevant libraries, Processes and Process steps and the related diagrams.

Hope this helps.

Thanx

Deepak

[sabatale]

Hello,

You are right. However you can generate the steps manually in a single shot: select all executables, right-click,and click Create Process steps.

I would not recommend this approach, though. RPBD is gone because you end up with too much information. Besides, it is not adapted to your business context.

You should generate the Exec/Dev. libraries, then focus on your most critical processes and start building them by generating only the relevant steps. When you generate the steps out of the executables, those are assigned to the step directly.

'luck

[Former Member]

Hi,

Do you think either note 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.

What if we have n't migrated to S4 HANA yet ? Is it valid for non S4 HANA systems ?

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

Please suggest

Thanks

Sateesh

[sabatale]

This SAP note should be used to cover non-S4 content (ie. ECC, CRM, etc.). However you won't have as much pre-documented content as with the S4 Best Practices (ie. it does not deliver fully-completed business diagrams, nor BP URLs, etc.). It is bascally just the structure with executables attached. This is a good starting point if you have never documented your solution, though.

You should select which BP packages are in scope, import them (careful, the system landscape adaptation takes some time if you select too many packages), then have validation/fit-gap workshops. It is up to the business to decide whether the standard processes will help.

[Former Member]

Thank you

[Former Member]

Hi,

Below note suggests that Library Generation Cockpit does not create any new process steps or business process structure

2450667 - How to Generate a Process Step Library from an Executable Library

Thanks

Sateesh.