When organizations implement new software, they are often most focused on getting the functionality up and running and achieving business results as quickly as possible. This goal sometimes comes at the expense of important procedures — such as properly documenting their solutions. When consultants are around to answer questions, a lack of documentation is no problem, but as soon as they leave, customers are left to their own devices. If the solution is not properly documented, the organization could be in trouble.
This holds true for SAP solutions for governance, risk, and compliance (GRC). If your solution, such as SAP Access Control or SAP Process Control, isn’t properly documented, you run the risk of not getting the most out of your investment due to not being confident in updating your solution, not applying patches, being reluctant to upgrade, or even having to reimplement. You can use SAP Solution Manager to document your solution, regain any lost knowledge, and keep your users informed, even after the project team has left.
Use Solution Documentation to Prevent Project Knowledge Loss
Say, for example, that you upgrade SAP Access Control from version 5.3 to version 10.1 and you want to create or update documentation. You would start by creating the blueprint for your system in the Projects application in SAP Solution Manager. You then use accelerator data from the repository for SAP Access Control, which supplies basic business processes to populate a blueprint structure for user provisioning and role management. From this structure, you can add any customized workflows, interfaces, and organizational data.
If your solution isn’t properly documented, you run the risk of not getting the most out of your investment.
In tabs within the Projects application, you can store project data such as decision-making explanations, which can serve as a guide for future decisions. There is also a graphical tool for organizing processes across multiple systems, such as connections to LDAP and identity management systems, as well as identifying and documenting target systems. Furthermore, you can print the blueprint document, which can be useful to compliance teams, as it is a record of the system design at a point in time.
When you move to configuration mode, new tabs appear in SAP Solution Manager from which you can perform configuration directly in your GRC development system. You can store the entries made in the target system’s IMG next to each step and group steps module by module into a Business Configuration (BC) Set for check-out or portability later. A printout of the completed configuration serves as a delivery document for sign-off and comparison with the blueprint document.
There are a number of other standard tools that you can use during various project steps. For example, when testing GRC apps you can use the testing suite to manage the whole testing cycle, including using workflow for testers, test script management, and issue management. You can also use the learning suite to automatically distribute content, as well as collect Shareable Content Object Reference Model (SCORM)-compliant data and return it to HR training records. The Change Analyzer tool allows you to collect data about the changes that have been made to SAP solutions for GRC. It then tells you what testing is required and which learning modules to check.
Reporting is also available throughout all of SAP Solution Manager, with preconfigured reports for each section.
Island Consulting specializes in SAP Solution Manager and SAP solutions for GRC, with experience running them on both SAP HANA and standard ABAP implementations. Island Consulting also offers reverse engineering of your solutions as well as preconfigured solutions that can be delivered to give your organization a rapid standard deployment of SAP solutions for GRC 10.1. For more information and brochure downloads, go to www.islandconsulting.ie.