From SAP: “All live Meet the Expert Sessions are recorded and will be then available via SAP ES Academy ‘Replay Library’ www.service.sap.com/replay-library”
The usual disclaimer applies that things in the future are subject to change. Also a couple caveats:
1. I have not used this feature productively
2. I missed parts of this webcast in the middle so my notes are not complete
Figure 1: Source: SAP
Figure 1 shows that SAP plans to make Solution Manager more business oriented.
SAP also wants to make SolMan ready for HANA deployments
Figure 2: Source: SAP
SOLAR transactions that support documentation and implementation processes
SAP said this approach that had drawbacks
Figure 3: Source: SAP
Figure 3 shows the current pain points, including a “Rigid 3 level hierarchy”
SAP wants to use the new UI – HTML5
Basic Concept for SAP Solution Manager 7.2
Solutions can act as a an umbrella
Figure 4: Source: SAP
Solution (in Figure 4) covers system landscape where you need to know runtime environment, execution environment
New solution documentation UI works with LMDB content, logical component, new logical component group
It covers the processes that the customer execute
Figure 5: Source: SAP
Figure 5 shows the Solution landscape and documentation UI
Sub landscapes relates to a maintenance cycle related to ERP
Sites are processes deployed to multiple plant running different ERP systems – for global rollout use cases
Document types reflect what documentation to be available
Figure 6: Source: SAP
Figure 6 shows the planned solution documentation approach is to be both top down and bottoms up.
Figure 7: Source: SAP
Figure 7 shows where attach documentation related to executables
Business processes can be reused
Define configuration block; define dependencies of the block
Figure 8: Source: SAP
Library of executables, config units, interfaces – IT
Enable processes – assemble end to end processes out of artifacts
Figure 9: Source: SAP
Introduce a change and include change documentation
Ensure properly documented in maintenance branch and transported
Documentation needs to be released
Figure 10: Source: SAP
Logical components have changed; solution documentation is bound to logical component group
When upgrade, you need to restructure logical components
Figure 11: Source: SAP
Figure 11 shows projects/solutions to move to 7.2 content structure; this includes BPMN modeling capability
Question and Answer:
Q: What is clear definition for branch?
A: Branch is a versioning context for documentation
Q: Is this Solution Manager running on HANA DB?
A: Can run on HANA or other databases
Q: Will integration with ARIS be possible?
A: Clearly plan to have open interface to integrate with third party modeling tools
Not available in first version but it is on the agenda
Q: Is there is a limit on the number of nodes you can have on your project
A: not known to him
Q: Will there be integration with PowerDesigner?
A: plan to have open interface to integrate with third party modeling tools
Q: What is the effort to migrate?
A: If you move content from SOLAR to new documentation – content is moved to process area – the respective library structures are created