I’m posting a small hint which helps to recognize in which SAP system you are connected via SAP GUI. Sometimes when you are working with several sessions in different systems and you switching between windows very often it is problem to do not get confused.
Log in to some SAP system in which you want to change the color via SAP GUI -> select Customizing local layout (ALT+F12) -> Set color to system (select color) -> Save.
To setup production client in a BW system in order to use BW func. (e.g. RSA1) take the following steps.
1. create new client via SCC4
2. copy client from 000
3. adapt Instance or Default profile parameter login/system_client so the the system opens with prod. client
4. Edit the cust. in table RSADMINA and change the value of field BWMANDT to your new client.
5. Test with running RSA1.
References: OSS Note 122679 and 116432
As project team member, you want to:
● check business scenarios and/or processes which have already been used productively, out of the Solution Directory, to adjust or change them in a maintenance project.
● check business processes which have been changed or adjusted for production processing in a maintenance project (transaction SOLAR01), back into the Solution Directory.
As project leader or administrator, you want to:
● confirm business scenarios or processes to be checked out of the Solution Directory, and assign them to project team members for processing.
● confirm changed or adjusted business scenarios or processes from the maintenance project (transaction SOLAR01) which are to be checked in, for production processing.
You have assigned a maintenance project with project team members, to your solution, and selected the check-out function in the solution settings.
Once the business scenarios or processes are checked out, they can no longer be changed in the Solution Directory.
...
1. Check-out of the Solution Directory into the maintenance project (transaction SOLAR01)
You are in the Solution Landscape Maintenance (Solution Directory):
a. as project team member:
i. Select the business scenario or process, in the Structure tab.
ii. Click on the button Request.
The system changes the status of the change request to Check-Out Requested.
You can reset the request with the pushbutton Cancel Request.
iii.
b. as project leader or administrator:
i. Choose Check Out to check the processes in the project out.
If you have assigned the roles for the project leader, the project team member selection appears.
ii. Assign project team members by selecting them.
iii. Confirm.
The system changes the status of the change request to Checked-Out.
The checked out business scenario or process appears in the maintenance project under the hierarchy node for your solution.
2. Check-in from the maintenance project (transaction SOLAR01) into the Solution Directory
a. as project team member:
You are in the Business Blueprint (transaction SOLAR01). The system displays the status Checked Out.
i. Select the business scenario or process, in the Structure tab.
ii. Click on the button Ready.
The system changes the status to Check-In Requested.
To be able to release the processes, you must set the status of all associated documents, such as documentation, test cases, etc. to Released.
b. as project leader or administrator:
You are in the Solution Directory for your solution. The system shows the change request status as Check-In Requested.
i. Choose Check-In.
ii. Save.
You can trace changes to your business processes, in the change history.
You transport a BI 7.0 Web Template but after the import the changes is not visible in the report.Do get around this problem, clear the ICM cache in your BI backend system via transaction SMICM.See the screenshot below:
A lot of new features have been introduced with NetWeaver 2004s and its ABAP SAP Application Server 7.0. Finally password is case sensitive and may have from 8 to 40 characters in length. Huge bunch of new system profile parameter have been acquaint as well:
login/min_password_lowercase
login/min_password_uppercase
login/password_max_idle_productive
login/password_max_idle_initial
login/password_history_size
login/password_change_waittime
login/password_downwards_compatibility
login/password_compliance_to_current_policy
For details see following SAP notes:
862989 1023437 992855 968558 943505
You can change and adjust production business scenarios and processes, using the 4 eyes principle.
You have:
● Defined solutions.
● Defined business scenarios and processes
● assigned Roles for the Solution Directory:
○ Project team member: SAP_SOLMAN_DIRECTORY_EDIT
○ Project leader or administrator: SAP_SOLMAN_DIRECTORY_ADMIN
● assigned roles for Project administration
...
1. The project team member responsible for modelling the business scenarios and processes wants to change one or more production business scenario or process. The processes must be checked out of the Solution Directory into a maintenance project for processing. Project leader or administrator:
a. assigns an existing maintenance project to the solution in the solution settings or defines and assigns a new maintenance project with Create and Assign New Project in the Project Administration (transaction SOLAR_PROJECT_ADMIN).
b. activates the history and check out/in functions in the solution settings.
c. assigns project team members to make changes in the maintenance project later.
2. The business scenarios or processes of the solution are selected for check-out into the maintenance project, by the project team member responsible.
3. The administrator or project leader releases check-out of the business processes into the maintenance project for specified project team members.
4. The project team members edit the business scenarios or processes assigned to them, in the maintenance project.
5. When the project team members have edited the business scenarios, they check the business scenarios or processes back into the processes.
6. The administrator or project leader confirms the procedure so that the changed business scenarios and processes are productive.
Before users can start working with Change Request Management, the system administrator (or equivalent user) has to create user roles that contain the relevant authorizations, and then assign these roles to the corresponding users. The roles have to be created (by using transaction SU01) for users in the following systems:
· SAP Solution Manager system (Change Request Management runs in this system)
· Satellite systems that are managed by Change Request Management
The following roles are provided by SAP and have to be assigned to the corresponding users in the SAP Solution Manager system:
· SAP_CM_CHANGE_MANAGER
This role enables the user to approve and reject change requests.
· SAP_CM_DEVELOPER_COMP
This composite role enables the user to make corrections in the development and maintenance systems, and to release the necessary transport requests. It comprises the following single roles:
¡ SAP_SOCM_DEVELOPER
¡ SAP_CM_SMAN_DEVELOPER
· SAP_CM_TESTER_COMP
This composite role enables the user to test and validate corrections in the test system. It comprises the following single roles:
¡ SAP_SOCM_TESTER
¡ SAP_CM_SMAN_TESTER
· SAP_CM_OPERATOR_COMP
This composite role enables the user to import corrections into systems, and to perform operational tasks in task lists. It comprises the following single roles:
¡ SAP_SOCM_IT_OPERATOR
¡ SAP_CM_SMAN_OPERATOR
· SAP_CM_PRODUCTIONMANAGER_COMP
This composite role enables the user to approve and perform the import of corrections into the production system. In certain critical situations (such as during a payroll run), the production manager can decide not to import corrections into the production system; otherwise, the system could be rendered inconsistent. It comprises the following single roles:
¡ SAP_SOCM_PRODUCTION_MANAGER
¡ SAP_CM_SMAN_PRODUCTIONMANAGER
· SAP_CM_REQUESTER
This role enables the user to create change requests.
· SAP_CM_ADMINISTRATOR_COMP
This composite role enables the user to customize and check all Change Request Management functions in the Solution Manager system, as well as perform administrative and technical tasks for task lists and cProjects. It comprises the following single roles:
¡ SAP_SOCM_ADMINISTRATOR
¡ SAP_CM_SMAN_ADMINISTRATOR
¡ SAP_CPR_PROJECT_ADMINISTRATOR
¡ SAP_CPR_USER
From a transport point of view, the remote architecture of Change Request Management consists of one central SAP Solution Manager system, which is where Change Request Management runs and where all transports are controlled, and satellite systems where transport requests are created, released, and imported. In all these satellite systems, the local users need to have special authorizations within the Change and Transport System (CTS) according to their particular tasks.
· Real Users
For users in the satellite systems that have the system role types Development, Test or even Production, assign the following roles:
¡ SAP_CHANGEMAN_DEVELOPER
Contains the authorization profile S_TMW_DEVELO. This profile contains CTS authorizations for developers: No authorization to create transport requests, and no authorization to release transport requests but to create and release tasks.
¡ SAP_CHANGEMAN_OPERATOR
Contains the authorization profile S_TMW_OPERA. This profile contains CTS authorizations for operators: All transport authorizations; no configuration authorizations
¡ SAP_CHANGEMAN_ADMIN
Contains the authorization profile S_TMW_ADMIN. This profile contains CTS authorizations for administrators: All authorizations in the CTS (including configuration)
Note that the roles SAP_CHANGEMAN_PROJECTASSISTANT and SAP_CHANGEMAN_PROJECTLEAD are obsolete; do not assign them to users.
For SAP systems based on SAP Web Application Server 6.10 and lower, the profiles listed above are available, but not the roles. Therefore, you have to explicitly assign the authorization profiles to the relevant users.
· Trusted System Users
For all client system actions in Change Request Management, users are required to log on by using trusted systems. For this purpose, you must also assign trusted system authorizations to the relevant users. In particular, you have to assign the authorization object S_RFCACL. For more information, see SAP Solution Manager: Configuration Guide ® Technical Requirements ® Automatic Generation of Trusted System RFC Destinations.
· Background User
This user is required for communication between the SAP Solution Manager system landscape (transaction SMSY) and all systems that have the role type source system. For more information, see 
Generate/Change RFC Connections. In these logical systems, a communication (background) user is generated for executing tasks in the background (user SOLTMW
¡ S_TMW_CREATE for creating and releasing transport requests in development systems as well as for setting the project status switch for creating transport requests
¡ S_TMW_IMPORT for importing transport requests into test systems (empty)
The most important task of the background user is to create and release transport requests and tasks remotely from Change Request Management. Requests that are created in this way are known to Change Request Management, which means that Change Request Management can control the distribution of these requests within the landscape.
Requests that are created, released, or imported locally cannot be identified by Change Request Management in conjunction with a change request and are therefore not part of the Change Request Management transport control and distribution process. For this reason, we recommend that no users (apart from administrators) have authorization to create transport requests or tasks in Change Request Management-controlled clients.
· Import Authorization Checks
Change Request Management uses the import functions of the Transport Management System (TMS). The TMS remote infrastructure is based on RFC connections that point solely to the 000 client of a target system. For this reason, you must make sure that Operators and Administrators have users both in the client into which changes are imported, and in the 000 client of these systems.
· Automatic Imports
In test systems, it is sometimes necessary that imports are performed automatically. If you want developers within the Change Request Management scenario to start imports into a test system automatically, you must add the profile S_TMW_IMPORT to the user TMSADM in client 000 of the test system. Since S_TMW_IMPORT is delivered empty, you have to assign it the authorizations S_CTS_IMPALL and S_CTS_IMPSGL, which are also contained in the authorization object S_CTS_ADMI.
It is now possible to start an import into this system from every satellite system within your domain by using the CPIC user TMSADM; therefore, do not use this method in production systems or in any other security-critical systems.
The system where you want to start the import automatically must share the same transport directory as its preceding system. If the transport directories were different, the user who starts the import would need “addtobuffer” authorizations for the buffer adjustment, which would present a security risk not only for the system concerned, but also for the whole landscape (including the production system).
The following figures show which authorizations are contained in the Change Request Management roles.
· Roles in SAP Solution Manager system
The following table shows which task list authorizations are assigned to the roles in SAP Solution Manager system:
| Developer | Tester | Prod. Manager | Operator | Administrator |
Display | X | X | X | X | X |
Create | X | --- | --- | --- | X |
Change | --- | --- | --- | --- | X |
Delete | --- | --- | --- | --- | X |
Run | X | X | X | X | X |
Change status | X | X | X | X | X |
· Roles in the satellite systems
The following table shows which transport request/task authorizations are assigned to the satellite system roles:
* See Roles in the Satellite Systems (Automatic Imports section)
Technical name: SAP_MAINT_OPT_ADMIN
Technical name: SAP_MAINT_OPT_DISP
The individual roles allow users to either administer or display product maintenance procedures in the Maintenance Optimizer.
This individual role allows users to create and change product maintenance procedures in the Maintenance Optimizer
This individual role allows users to display product maintenance procedures in the Maintenance Optimizer
The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.
You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system.
The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.
The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.
The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.
You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, „BPM“ of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.
The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:
● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and „Other CCMS“ and interface data, in the local CCMS of the satellite systems.
● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.
The SAP Solution Manager system copies the data from the local CCMS.
The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.
The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.
You've probably heard about all the new functionality that comes BI 7.o , especially around web reporting. You can actually upgrade to BI 7.0 "as is" without having to do all the BI-JAVA stuff but then you won't be able to use the new web reporting functionalities that come with BI 7.0 like :
3. Analysis of aggregates
4. Recommendations for BI
5. BI Statistics
1. BI Runtime Statistics
2. Analysis of Query Definition
3. Analysis of OLAP Cache
4. Frontend Servers
1. Upload Statistics
2. Process Chains - Runtime Overview
3. Source System Settings
1. InfoCube 1
2. InfoCube N
1. Report 1
2. Report N
1. Important SAP Notes for data upload
1. Chain: 1
2. Chain: N
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
