Showing posts with label sap profiles. Show all posts
Showing posts with label sap profiles. Show all posts

November 11, 2012

Start and Stop Sap System



Start and Stop Sap System :-


Start the SAP instances  by entering the command startsap. Start the central  instance first and then the dialog instances.

a) Start the SAP instances by entering the command startsap.

startsap 

syntax: startsap name=<sid> nr=<Instanz-Nr.>SAPDIAHOST=<Servername>
Start the central instance first and then the dialog instances.

Stopping the SAP System

It may be necessary to stop an SAP system for a variety of reasons, for example,
restarting after permanently changing profile parameters, before installing kernel
patches, or allowing hardware upgrades to be carried out.

Before you stop the system, you should check the status of the system.

 This involves, among other things:

. Active Users:
  Check which users are logged on using the User List (SM04).

. Background Processing :
  Check which jobs are active using the Job Overview (SM37). If jobs are
  terminated by the system stop, these jobs must be rescheduled. Jobs that are
  scheduled for the time when the system is stopped run automatically once
  the system restarts.

. Batch Input:
The transaction Batch Input: Session Overview (SM35) displays running
batch input jobs.

. Update:
Use the Update Overview (SM13) to check whether update processes are
terminated by the system stop. These update records are rolled back during
the stop, and these are set to the status .init.. These records are then updated
again during the restart.

Before you stop your system, you should inform users using a system message
(SM02).

Enter the command stopsap to stop an instance.

stopsap 

syntax:  stopsap name=<sid> nr=<Instanz-Nr.>SAPDIAHOST=<Servername>





November 7, 2012

How to trace user's activity



How to trace user's activity :-



Creating a User Audit Profile :-


1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM19.

3. From the top-most menu bar on the Security Audit: Administer Audit Profile screen, click Profile
   -> Create.

4. On the Create new profile popup, type in a new Profile name and click the green √ picture-icon.

5. On the Filter 1 tab of the Security Audit: Administer Audit Profile screen, click the icon to the left of Filter active to place a √ in the box. In the Selection criteria section, select the Clients and User names to be traced. In the Audit classes section, click “on” all the auditing functions you need for this profile. In the Events section, click the radio button to the left of the level of auditing you need. Once you have entered all your trace information, click the Save picture-icon. You will receive an Audit profile saved in the status bar at the bottom of the screen.

6. Please note that while the user trace profile has been saved, it is not yet active. To activate the user trace, see the next section Activating a User Audit Profile.

7. You may now leave the SM19 transaction.


Activating a User Audit Profile :-

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM19.

3. On the Security Audit: Administer Audit Profile screen, select the audit profile to be activated from the Profile drop down. Click the lit match picture-icon to activate it. You will receive an Audit profile
activated for next system start in the status bar at the bottom of the screen. The audit will not begin
until after the SAP instance has been recycled.

4. You may now leave the SM19 transaction.


Viewing the Audit Analysis Report :-

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM20.

3. In the Selection, Audit classes, and Events to select sections of the Security Audit Log: Local Analysis screen, provide your information to filter the audit information. If you need to trace the activities of a specific user, be sure to include that user’s ID. Click the Re-read audit log button.

4. The resulting list is displayed. This list can be printed using the usual methods.

5. You may now leave the SM20 transaction.




November 3, 2012

Difference Between SAP_ALL and SAP_NEW




Difference Between SAP_ALL and SAP_NEW :-




Most of the times you might have question in your mind that why you give sap_all and sap_new everytime we create admin user (Altough some people used to give sap_all to every one ).So here the difference between these



SAP_NEW:-
SAP_NEW is a SAP standard Profile which is usually assigned to system users temporarily during an upgrade to ensure that the activities and operations of SAP users is not hindered, during the Upgrade. It contains all the necessary objects and transactions for the users to continue their work during the upgrade. It should be withdrawn once all upgrade activities is completed, and replaced with the now modified Roles as it has extensive authorizations than required.



SAP_ALL:-
SAP_ALL is a SAP standard profile, which is used on need basis, to resolve particular issues which may arise during the usage of SAP. It is used by Administrators/Developers only and is applied on a need to use basis, then withdrawn. It contains all SAP system objects and Transactions. SAP_ALL is very critical and only SAP* contains SAP_ALL attached to it in the production system. No other dialog users have SAP_ALL attached to them.



SAP_NEW is used in the Production environment during a version upgrade whereas SAP_ALL shouldn't be or not allowed be used in Production except where necessary, in a controlled manner with all proper approvals from the customer.






Generate Solution Manager Key




Generate Solution Manager Key :-




To Generate Solution Manager Key Execute T-code SMSY in Solution Manager system, you need to do the following steps:

 

1)Create a system by right clicking on System entry and select Create new system. 

2)Enter the System Name i.e., SID (3 chars)


3)Product = SAP ECC (select from the list)


4)Product Version= ECC 5.0 (select from the list)


5)Save the entries.


6)Select Menu Item "System--->Other Configuration" and enter the SID which you have created earlier.


7)Enter the Server Name(hostname)


8)Finally click on Generate "Installation/Upgrade Key Button "



The system generates a Key ,copy that Key and paste it in the SAPINST screen when it prompts for Sol man Key.