The Year 2008 brings the advent of changes to SAP Solution Manager with introduction of Solution Manager 7.0 from May 1st, 2008.
SAP Netweaver 7.0 which was previously known as 2004s is the current main release of SAP Netweaver technology. Solution Manager which is also built on Netweaver technology has been renamed from version 4.0 to 7.0 so as to be in sync with the current Netweaver technology release.
SAP Solution Manager 7.0 is a Name Change Only from SAP Solution Manager 4.0; it will not affect SAP Solution Manager Functionality, release schedule, installations, or other technical aspects of SAP Solution Manager.
Support Package Stacks information for SAP Solution Manager 7.0:
- For SAP Solution Manager 7.0, Support Package Stack 15 is installed.
- For Solution Documentation Assistant, SP 16 is required in 7.0
- The Kernel Version is 700 for both SOLMAN 4.0 and SOLMAN 7.0.
- SP17 was only a minor shipment with corrections in SOLMAN 7.0
For SAP Solution Manager 4.0 the Support Pack Stack level is up to 14.When the next level support packages are deployed i.e., from support pack 15 onwards it will be renamed to 7.0 Enterprise Version.
The following are the additional features provided in the Enterprise Edition:
1. Test Management: Additional Test workbench Functions are as follows
1.1. Release Status Schema
This function helps to control and monitor the execution of tests more
effectively to the tester.
Features:
The release status values settings are set in Customizing and can influence
therelease of test plans and packages in the following ways:
- Presetting of release status values:
The status numbers specifies the release status values series in the release status schema. With this schema the system determines the settable release status values in the test plan attributes and shows these in the input help.
The structure of the test plan and the attributes, including its test packages, cannot be changed. If the change lock is activated for the settable release status value in the test plan attributes.
The tester cannot execute the tests which are assigned to him means the tester cannot change the test status, if lock is executed on the settable release status value in the test plan attributes,
Fulfillment of signature strategy plays a Vitol role in controlling the testing plan for a Project. A signature strategy is assigned to the release status value set in the test plan attributes then the people must sign first to fulfill the signature strategy.If the signature strategy is fulfilled then the system sets the end status value automatically. If the signature strategy is cancelled then the system sets the cancel status value automatically.
1.2. Test Sequence and Test Assignment at Test Case Level
With the test sequence the Test Organizer specify that a test case is only available for testing when the predecessor test case is finished. This is significant function for unit testing and Integration testing.
Features:
There are the following tab pages available.
The test packages assigned to the test plan. The system displays the assigned test cases for each test package in a simple list. In this list the test Organizer can assign Testers at Test Case Level and Organize Test Cases in Test Sequences.
Here displays all test packages of the test plans, the consolidated test status of test cases, as well as the consolidated end-status of a test package. The status for selected test packages could be updated.
This shows the testers assigned to the test plan. When Test Organizer use the workflow, the system displays the procedure number and Workflow history for each tester for whom a business process has been created. Using the procedure number, Test Organizer could display a procedure document in the procedure processing.
- User Check on a Test Plan
The test organizer execute a user check before release of a test plan, Once the check is successful then only the test plan is released. This ensures when using workflow that a correct tester and test organizer is stored in the form of a business partner in the procedure document.
With workflow the test organizer could use actions that trigger the system at pre- defined times in a test organization and during the execution of a test. The system then automatically informs the Tester about released and locked test packages and test cases. If test sequences and a tester assignment at test-case level are used, the system informs the assigned tester of the successor test case as soon as the predecessor test case is finished.
2. Process Structure Management:
Additional Functions for editing the Project Structure
- Locking a Structure node:
A node which is there in the project structure can be locked for which the processing is completed. This is a fine controlling feature in Enterprise Edition. The other project participants are prohibited later making changes to parts of the project structure.
- Locking and Unlocking Tab Pages:
As locking structure nodes the Tab pages in the Project can be locked after finishing the editing the data of a tab page in your project so that other project participants cannot make any changes. According to each structure node, one can lock and unlock entries on the following tab pages:
- General Documentation, Project Documentation, Administration, Transactions, End User Roles, Configuration, Test Cases, Development, Learning Materials.
Locking a tab page only keeps locked entries from being edited. But we can still continue to edit other tab pages or the project structure.
Assigning and Locking Attributes:
Stores information on structure nodes of the project structure or assign
information to specific objects.
Depending on the object the following tab pages are available for assigning
Attributes:
- General : General information about the object and assigning
Keywords
- Links : Assigning documents
- Further Attributes : Customer-specific attributes and their assignments
- History : Editing history
3. Document Management:
Displaying and printing digitally signed documents:
This is one more excellent feature available with Enterprise Edition .To ensure data security and the integrity of data, could sign documents digitally. Using the digital signature, could also trace which user executed a particular processing step.On display or print digitally-signed documents, the system displays information relating to the digital signature associated with the document, such as name of the signee, date, and time.
4. Change Request Management
Assigning Structure Elements to Change Procedures:
In Change Requests, could assign urgent corrections and structure elements from projects or solutions. With this could able to find the objects in a change procedure that are affected by changes quickly again which is very important. Could navigate from the structure elements assigned in the change procedure to the assigned projects and solutions. Could assign structure elements to the newly-created change procedures once it has been saved. In the change procedure, could only check in and Check out objects for solutions.
5. Retrofitting Transport Requests:
In system landscapes where multiple releases are used at the same time, could make changes in different development systems: this means that changes can be developed in development systems and at the same time errors can be corrected in a maintenance system for the productive system landscape, or corrections can be triggered. The important thing here is that the system release levels are regularly adjusted. Because work was executed in parallel, it is not possible to transport changes to another system simply by using requests as there is the risk that current software release levels can be overwritten and inconsistencies may occur. To avoid this, we can execute a monitored import into the target system. This procedure is called retrofitting.
