Check Logical Components Solution Manager 7.2
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 “” 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. 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:.: 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.: 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 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) V3SAP ERP607 for Baseline United States (US) V3SAP ERP607 for Baseline China (CN) V3SAP ERP607 for Baseline India (IN) V3SAP ERP607 for Baseline Brazil (BR) V3SAP ERP607 for Baseline Canada (CA) V3Once 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 documentsHave 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. 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!. Hi,Yes, 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.ThanksSateesh. Hello,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.
I believe I have the final answer:“ Because of the sum of SAP Best Practices RDS Packages and SAP Solution Manager 7.1 Business Process Repository content the focus of the project was on the technical enablement for SAP Solution Manager 7.2 use. It was not possible to check all documentation assignments if they still work right. As a consequence there might be several documentation assignments (e.g. On Process level) which will not be possible to be executed any longer. We are not able to correct this.”. Hi, my pleasure!I think you did not perform all the required steps. Did you import the.A4H files in the transport repository?
May 19, 2012 To create a new Logical component, proceed as follows: In the Solution Manager, call transaction SMSY. In the transaction SMSY, click on ‘Solution Groups and Logical Components’. Expand the ‘Logical Components’ tree. Released in 2016, SAP Solution Manager 7.2 introduced a new process management architecture providing one simplified process landscape for the business and IT, along with enhanced functionality such as a new SAPUI5-based user experience, cloud & hybrid solution support, transparent requirements to deploy project management, and SAP Solution Manager 7.2 can run on SAP HANA.
You need to transport these files to get the KW documents.Besides that, no all URLs are working since they are inherited from 7.1 content. See this sentence from SAP: “ Because of the sum of SAP Best Practices RDS Packages and SAP Solution Manager 7.1 Business Process Repository content the focus of the project was on the technical enablement for SAP Solution Manager 7.2 use. It was not possible to check all documentation assignments if they still work right.
As a consequence there might be several documentation assignments (e.g. On Process level) which will not be possible to be executed any longer. We are not able to correct this.“. 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?
Hello,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.
Check Logical Components Solution Manager 7.2 Help
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.
Hi,Great post- thank you for writing on this! If I want to add a step in process path – I can do in SOLMAN, view process, add process step. This I have seen possible in SOLMAN, however two questions request inuts.Two question –. If I have to extend the best practice package – eg. Creation of Z-Document-type (ZOR), The Configuration – how e capture this in SOLMAN?2) If I have to change Best Practice Package or extend it – E.g. Instead of sales document type OR, I want to use ZOR, how and where SOLMAN CHARM should be used to reflect this change in SOLUTION Configuration?