Monday, 8 April 2013

What is Employee Self Service & Manager Self Service


ESS - Employee Self Service & MSS- Manager Self Service

Employee Self Service is a web enabled tool used to update their own data by the employee itself.

MSS- Manager Self Service
Manager Self Service is a web enabled tool used for Managers to take report or update the data of subordinate.

This will give you a comprehensive idea:
To implement LEAVE REQUEST & APPROVAL, both ESS and MSS are not mandatory. But ESS is required. However this functionality is developed to be available in MSS also if a client wants have both ESS and MSS.  Without MSS, the business flow of Leave request would be in ESS is like this:
1. An employee wants to take two weeks of leave. He or she accesses the Leave Request Web application. He or she sees in the Team Calendar that other team members also have leave at the same time. Nonetheless, he or she requests leave for the planned period.

2. The leave requires approval. The system automatically determines the approver responsible and lists the name in the Web application. If required, the employee can overwrite the name of the approver.
  1. The employee's request is stored in the database of leave requests with the status Sent.
  2. Once a day, the RPTARQEMAIL report (Leave Requests: Send E-Mails) is run in the background. The system sends an e-mail to the appropriate approver for the requests with status Sent that require approval. The e-mail notifies the approver of the steps required.

3. The approver accesses the Approve Leave Requests Web application from the Universal Work list.. The application provides the approver with a list of all the leave requests that require his or her approval.

4. The approver selects the employee's leave request. After checking the Team Calendar, the approver realizes that the employee's leave request cannot be approved since it would mean there would not be enough team members at work for the period in question.

5. The approver writes a note in which he or she states why the request has been rejected. He or she then rejects the request.

6. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her that the request was rejected. The employee accesses the Leave Request Web application. He or she selects the request in the Absence Overview. He or she sees in the note the reason why the request was rejected.

7. The employee looks at the Team Calendar and finds a period in which no other team members are on vacation. He or she changes the period of the request. The employee
Specifies the change in period in the note.

8. The RPTARQEMAIL notifies the approver of the request by e-mail.  This time the approver can approve the request.

9. The request receives the status Approved in the database. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her that the request was approved.

10. The system processes the requests further according to their status:

11. The RPTARQPOST report (Leave Requests: Post) writes all requests in the database that have the status Approved to the Absences (2001) or Attendances (2002) info type.

12. The system may not be able to post the requests to the info types if, for example, they collide with other info type records. These requests are given the status With Errors.

13. The RPTARQEMAIL report sends an e-mail to the relevant time administrator to notify him or her that the requests were unable to be posted.

14. The time administrator accesses the RPTARQERR report (Leave Request: Process Posting Errors). It lists the requests with errors.

15. The time administrator analyzes the error situation in the back end system.

16. If he or she can solve the cause of the problem and save the data record in the info type, he or she uses the RPTARQERR report to set the request to Posted.

17. If the problem cannot be solved, because the employee has other commitments at the time, for example, the time administrator rejects the request.

18. The RPTARQEMAIL report sends an e-mail to the employee notifying him or her of the change in status of the request (in ESS)


MSS:  it is a web based application designed for the people who carry out management tasks.  Here is the brief description.

This Manager Self Service is designed for all employees who perform management tasks at an operational level, for Example:
i.   Line managers
ii. Team leaders with project management tasks
iii. Department heads
In particular, the business package supports managers

Perform the following:
1    Tasks related to the personnel responsibility for their team
- Controlling tasks within their budgeting responsibilities
- Planning tasks
- Project management tasks
* Budget* -- Supports managers in fulfilling their cost and budget responsibilities, including annual budget planning, budget monitoring, cost analysis, and correction of postings. Managers can check critical variances, monitor travel expenses, and track budget consumption on projects.

*Staffing* -- Supports managers in their HR-related administrative and planning tasks. The application supports
HR processes relevant to a manager's particular tasks -- from recruitment to the annual employee review and compensation planning. It allows a manager to display attendance information, as well as to change data for employees who have no access to PCs. SAP Manager Self-Service supports flexible reporting on data from different data sources, and a quota planning function enables managers to plan future staffing quotas. In the latest release there some additional functionalities (iViews) are added.

ESS:  Allows employees to create, display, and change their own data in the company's intranet. In Personnel Administration, for example, employees can use the Personal Data service to create and edit their own personal data. In this way, employees can keep their own data up-to-date, while simultaneously reducing the number of time-consuming and expensive activities performed by the Human Resources Department.
Employee Self-Service of my SAP ERP enables employees to create, display, and change their own HR-related data in the Enterprise Portal. It covers data from various business areas:

THE CONFIGURATION AREAS IN ESS IS BELOW WISE AS A FUNCTIONAL CONSULTANT.
- Working Time
- Career and Job
- Employee Search
- Personal Data
- Benefits and Payment
- Travel Management
- Corporate Information
- Life and Work Events
- Training related details
- Qualifications 
- Appraisals
- Participation in the Appraisal process* etc.  

Tuesday, 26 March 2013

How to do a SAP System Copy?

How to do a SAP System Copy

Step by step for SAP System Copy.
1. Take offline backup of both the server (source and target servers)

2. Verify the backup is successfully done.

3. Run the following command on source system.
o    Login as adm
o    svrmgrl
o    connect internal
o    alter database backup control file to trace;
o    exit;
o    Above command will generate a .trc file in /oracle/P01/saptrance/usertrace directory.
o    Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file.
o    Copy the controlfile.sql to target system..
o    Edit the file and replace the entire source SID to target SID.
o    Edit the reuse database command with the set database command

4. Copy the generated during the backup file from the source system to target system.   
     (/oracle//sapbackup)
o    Change all the source to target .
o    Only don’t change the backup volume name it must be target system.
o    Copy the above aft file name line from the source back.log to target.log file.

5. Shutdown the target server instance.

6. From this onwards all the command on the target system only.
o    Login as Orasid
o    run the brtools
o    select Restore/Recovery
o    select Full restore and recovery
o    select backup type
o    Select the offline backup which you want to restore.
o    It will take some time to restore.
o    Once the database is restored login as Orasid and run the
o    svrmgrl
o    connect internal;
o    startup nomount (if the database is already mounted shutdown it using the shutdown command)
o    run the following command
o    @controlfile.sql (file name of the control file contains the CREATE CONTROLFILE statement)
o    After the run the above command it should give the “Statement Processed)
o    alter database open resetlogs
o    shutdown
o    Start the database and SAP services using startup.

7. After this you have to reconfigure the STMS.

8. All the jobs also you have to reconfigure and reschedule.

9. Reconfigure all the printers.

10. If you want to change the Client number then use the local copy tool and remove the
      original client after successful import to new client.

Monday, 18 March 2013

SAP Daily System Monitoring



Daily System Monitoring:
               SM51 SAP Servers:
1.       Check Availability of All Servers
2.        Check Process Lists for All Servers for Unusual Processes or Activities (e.g. Extra-long execution times, too many errored processes, too many sequential reports)
               SM66 Global Process Monitor:
1.       Check for over-all system process utilization
2.       Are Batch id's taking up too many DIA processes
3.      Is one user running too many BGD jobs for the same report
4.      Is one server being used heavily compared to others
              SM21 System Logs:
1.       Is there any repetitive errors in the system log
2.       Any unusual repetitive failed login attempts
            ST22 Short Dumps:
1.       Except 'Time-Out' errors, are there any short dumps?
           SMLG Logon Groups:
1.       Check load distribution (Menu: Go to-->Load Distribution)
2.       Are server response times acceptable? (< 2 sec)
3.      Is user distribution even among active servers
          ST03N Workload Analysis:
1.       Check is daily, weekly and monthly totals are being calculated for each server
2.       Check for Avg. Dialog Response Times. Is it below 2 sec
         SM12 Lock Overview:
1.       Check for outdated lock records
2.        Verify that these lock records are not actively being used and delete these lock records if they are obsolete
         SM13 Update Records:
1.       Check if the 'Update System' is active.
2.       If not active, investigate what happened
3.      Activate 'Update System' after fixing the problem
4.      Review update records of past two days and delete if errored or obsolete
        SM37 Background Job log:
1.       Check if they are any critical jobs that were canceled
2.       Identify/Fix the problem
3.      Contact canceled job user for details
4.      Reschedule if needed
       SP01 Spool Request overview:
1.       Check if there unusual number of errors in spool (>100)
2.       Check if there are spool request with more than 200 pages
3.      Should not be a need to delete any as the daily job should handle, unless too many spools are old.
       ST04 Database Activity Monitor:
1.       Check 'Data Buffer' and 'Shared Pool Cache' quality
2.       Investigate and make suggestions to the team to improve quality of these buffers
      DB02 Database Performance:
1.       Check 'Current Sizes' to see if any tablespace is above %90
2.       Add new data file to the tablespace if needed
3.      Check if there is space-critical objects
4.      Check if there are any missing objects in DB or R/3 Data Dictionary
      DB16 Database Check, Overview of message:
1.       Check if there are any messages
2.       Take immediate action to fix the problem
3.      Notify the team if there is any parameter changes or assistance needed for Production Systems
        DB24 Database Operations Logs:
1.       Check if all DB Operations are executed
2.       Check if any of the operations generated any errors
3.      Fix the problem. Notify team if needed
        DB12 Database confirms backup success:
1.       Check to see that the previous backup was successful
2.       If a backup is currently running check its status
3.      If the last backup failed, check the reason correct and resubmit.
        ST06 OS Monitor:
1.       Click on 'Detailed Analysis menu'
2.       Click on 'CPU' in 'Previous Hours' Group
3.      Check if at any past hours is > %80
4.      Notify Team if there is any such case


Basis T-Codes


Administration
AL11      Display SAP Directories
OSS1    Logon to Online Service System
SARA  Archive Management
SCC3  Copy Analysis Log
SCC4 Client Administration
SCC5 Client Delete
SCC7 Client Import Post-Processing
SCC8 Client Export
SCC9 Remote client copy
SCCL Local Client Copy
SICK    Installation Check
SM01 Lock Transactions
SM02 System Messages
SM04 User Overview
SM12 Display and Delete Locks
SM13 Display Update Records
SM14 Update Program Administration
SM21 System Log
SM35 Batch Input Monitoring
SM50 Work Process Overview
SM51 List of SAP Servers
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM66 System Wide Work Process Overview
SAINT SAP Add-on Installation Tool
SPAM SAP Patch Manager (SPAM)
SPAU Display modified DE objects
SPDD Display modified DDIC objects
ST11   Display Developer Traces
ST22  ABAP/4 Runtime Error Analysis
SU56 Analyze User Buffer

ALERT MONITORING
AL01 SAP Alert Monitor
AL02 Database alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL16 Local Alert Monitor for Operat.Syst.
AL18 Local File System Monitor
RZ20 CCMS Monitoring

CONFIGURATION
 FILE    Cross-Client File Names/Paths
RZ04  Maintain Operation Modes and Instances
RZ10   Maintenance of Profile Parameters
RZ11    Profile parameter maintenance
SE93   Maintain Transaction Codes
SM63 Display/Maintain Operating Mode Sets
SPRO  Customizing: Initial Screen

DATABASE ADMINISTRATION
 DB01 Analyze exclusive lock waits
DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar
DB15 Data Archiving: Database Tables

JOBS
SM36 Define Background Job
SM37 Background Job Overview
SM39 Job Analysis
SM49 Execute External OS commands
SM62 Maintain Events
SM64 Release of an Event
SM65 Background Processing Analysis Tool
SM69 Maintain External OS Commands

MONITORING
AL08 Current Active Users
OS01 LAN check with ping
RZ01 Job Scheduling Monitor
RZ03 Presentation, Control SAP Instances
ST01 System Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace
ST06 Operating System Monitor
ST10 Table call statistics
ST03 Performance, SAP Statistics, Workload
ST07 Application monitor
STAT Local transaction statistics
STUN Performance Monitoring (not available in R/3 4.6x)

SPOOL
SP01 Output Controller
SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration

TRANSPORTS
SCC1 Client Copy – Special Selections
SE01 Transport Organizer
SE06 Set Up Workbench Organizer
SE07 CTS Status Display
SE09 Workbench Organizer
SE10 Customizing Organizer
SE11  ABAP/4 Dictionary Maintenance
SE16 Data Browser
SE80 Repository Browser
SM30 Call View Maintenance
SM31 Table Maintenance
STMS Transport Management System

USER ADMINISTRATION
PFCG Profile Generator (Activity Group Maintenance)
PFUD User Master Data Reconciliation
SU01 User Maintenance
SU01D User Display
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 User Mass Maintenance
SMLG Maintain Logon Group
SUPC Profiles for activity groups
SUIM Infosystem Authorizations