Wednesday, 11 September 2013

sap hr/hcm ess and mss


ESS & MSS

 
What Is ESS and MSS?

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


MSS stands for  Manager Self Service. It is also a web enabled tool used for Managers to take report or update the data from  subordinate.



To implement LEAVE REQUEST &APPROVAKL, both ESS and MSS are not mandatory. But ESS is required.However this functionality is developed to be avaialable 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 requestswith 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) infotype.
12. The system may not be able to post the requests to the infotypes if, for example, they collide with other infotype 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 backend system.
16. If he or she can solve the cause of the problem and save the data record in the infotype, 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 mySAP ERP enables employees to create, display, and change their own HR-related data in the Enterprise Portal. It covers data from various business areas:
- 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. 

We provide sap hr/hcm online and inhouse training

for more deatils
madhupayroll@gmail.com
mobile : 9912223430
             9948932100


 
 















































Thursday, 8 August 2013

Wage type valuation using valuation bases x010,x013



 Wage Type Valuation using Valuation Bases
 You should only use schema XT00, function XMOD, personnel calculation rule X015, if schemas,
Determining Work Center and Basic Pay Data
Subschema XBD0 (Edit Basic Data )  ( INBD for Indian payroll ) is accessed by personnel calculation schema X000  (IN00). Function WPBP is used within the subschema to write an employee’s work center and basic pay data to internal table WPBP (Work Center Basic Pay). Furthermore, wage types in the Basic Pay infotype (0008) are written to the input table (IT) from which they can be retrieved for further processing.
Function WPBP also determines whether a payroll period consists of several partial periods that must be processed separately. Such periods can arise for the following reasons:
  • Because an employee joined the company, left the company, or was absent from the company during the period.
  • Because of substitutions, changes in basic pay, changes in organizational assignment, and changes in the personal work schedule.
  • Because payments are divided for cost accounting into paid and unpaid attendances and absences.
Creating Valuation Bases for Different Payments
Subschema XT00 (Process Time Data in Payroll Accounting) is accessed by personnel calculation schema X000. Function PALP is used within the subschema to run personnel calculation rule X012 (Valuation Bases for Different Payments).
Personnel calculation rule X012 checks whether the employee must be paid differently for part or all of the period for which the payroll is run. The following cases are taken into account:
  • The employee works for part or all of the period at a work center that is not assigned to him or her.
For this reason, the employee must be paid differently for the period of his or her work center substitution. The valuation bases for this period are determined using data for the work center at which the substitution occurs.
  • The collective agreement provisions of a different wage group / wage level apply to the employee for part of the period.
The valuation bases are determined for this partial period using data for the wage group and wage level that apply to the partial period.
Creating Employee-Related Valuation Bases
Personnel calculation rule X010 (Determination of Valuation Bases International) is accessed by personnel calculation schema XT00 (Process Time Data in Payroll Accounting).
All wage types that you can enter as basic pay in the Basic Pay infotype (0008) can be coded in processing class 01. You can use function WPBP to call these wage types from the input table (IT) for further processing.
Calculation rule X010 queries the processing class 01 for the basic pay wage types in the input table. Depending on the specification in processing class 01, the wage type is written to one of the secondary wage types which create the valuation bases.
Calculation rule X010 is called depending on the employee subgroup for calculation rule. In the standard system, the processing steps within personnel calculation rule X010 are the same for all employee subgroup groupings. If you want to set up special processing features for an employee subgroup grouping, you must ensure that you enter your changes for the correct employee subgroup grouping for personnel calculation rules.
Personnel calculation rule X013 (Division of Valuation Bases) is accessed immediately afterwards. Depending on the employee subgroup grouping for calculation rule, calculation rule X013 queries the specification in processing class 01.
  • The system uses specification 5 in processing class 01 to determine valuation bases /001 and /002, as well as valuation bases /003 and /004 for Germany.
  • The system uses the employee subgroup grouping for personnel calculation rule to determine whether the employee is an hourly wage earner, or someone who receives a wage or salary for a payroll period.
  • The valuation bases for all employees who do not receive an hourly wage are divided by the total number of hours for the period. This results in an hourly rate which is written as a valuation basis to the Rate (RTE) field of wage types /001 and/or /002.

Determining Wage Types That are Valuated Using a Valuation Basis
In calculation schema XT00 (Processing Time Data in Payroll Accounting), calculation rule X015 (Valuation of Time Wage Types) checks whether the input table (IT) contains wage types which should be valuated using valuation bases. Calculation rule X015 is called for specific personnel groupings. This means that calculation rule X015 has different subareas for each employee subgroup grouping for calculation rule.
Decision operations AMT?0, NUM?0 and RTE?0 are used to check the contents of the AMT (Amount), NUM (Number) and RTE (Rate) fields.
  • If the Amount (AMT) field contains a value, the wage type will be transferred with the operation ADDWT.
  • If the Amount (AMT) does not contain a value, and the Number (NUM), and Rate (RTE) fields do contain values, then the values in the Number and Rate fields are multiplied. The result is entered in the Total Amount field and the wage type is transferred with the operation ADDWT.
  • If only the Number field (NUM) field contains a value, the operation VALBS queries whether a valuation basis has been entered in the Wage Type Valuation table (T512W) for the wage type. If a valuation basis has been specified, the wage type is valuated using the appropriate valuation basis. If not valuation basis has been specified, the wage type is valuated using the principle of averages, in accordance with the specification in processing class 15.
 This procedure is the same for all subareas of personnel calculation rule X015, in other words, the queries described above are effected for all employee subgroup groupings (hourly wage earners, monthly wage earners, salaried employees, and so on). The actual wage type valuation using a valuation basis is different for hourly wage earners and monthly wage earners/salaried employees, in other words, the valuation depends on the employee subgroup grouping for personnel calculation rules.
Performing the Valuation
The valuation is performed within calculation rule X015 (Valuation of Time Wage Types) and it is dependent on the employee subgroup grouping for personnel calculation rule.
  • For hourly wage earners (employee subgroup grouping for calculation rule with specification 1).
If a valuation basis exists for the wage type, operation VALBS0 is used to valuate the base wage type. Operations VALBS1 and VALBS2 are then used to valuate the first and second derived wage types respectively. Operation ADDNA cumulates the values in the NUM (Number, N) and AMT (Amount, A) fields. The Rate (RTE) field remains unchanged.
 For monthly wage earners and salaried employees (employee subgroup grouping for personnel calculation rule with specifications 2, 3, and 4)
If a valuation basis exists for the wage type, the system accesses personnel calculation rule X115 (Valuation of Time Wage Types).
Operation VAKEY queries the ALZNR indicator. The system uses this indicator to determine whether an alternative payment must be effected for the wage type. This might be necessary, for example, if an employee is assigned for part of his or her working time to a work center that is remunerated differently (such as when substitution occurs).
The alternative payment procedure is determined by processing class 18 (Processing for Work Center-Related Payments):
Specification of processing class 18
Valuation
0, BLANK
Remuneration with higher valuation basis
1
Remuneration with difference (if the specification of the employee subgroup grouping for calculation rule is greater than 1)
 In accordance with processing class 18, operation VALBS0 valuates the base wage type, operation VALBS1 valuates the first derived wage type, and operation VALBS2 valuates the second derived wage type. Operation ADDNA cumulates the values in the NUM (Number, N) and AMT (Amount, A) fields. The Rate (RTE) field remains unchanged.

We provide sap hr/hcm real time  online   training
for more details
madhupayroll@gmail.com
91+9912223430

HOW DO WE KNOW T.CODE


 If we know a program, how do we know a t.code?

Enter t.code "se38" in command field==>press enter==>enter programme

ctrl shift f3
check transaction
press enter --we see transaction code

We provide real time sap hr/hcm online training 
for more details
madhupayroll@gmail.com
91+9912223430

SAP HCM SAUDI ARABIAN PAYROLL WITH REAL TIME SCENARIO

SAP HCM SAUDI ARABIA PAYROLL REAL TIME TRAINING 

BASIC SETTINGS
BASIC PAY CONFIGURATION
RECURRING PAYMENTS AND DEDUCTIONS
ADDITIONAL PAYMENTS
ADDITIONAL PAYMENT S-OFF CYCLE
FORMS
CREATE VARIANT REMUNERATION STATEMENT
PAYROLL DRIVER
MAIN SCHEMA==>SAX0
SUB SCHEMAS   SAD0,SAT0,SAP9,SAL9,SADA,
FUNCTIONS
STANDARD PCR
CUSTOMER SPECIFIC PCR
PROCESSING CLASSESS
CUMULATION CLASS
EVALUATION CLASS
TABLE  V_512W_D, V_T512W_B ,V_T510  V_T510K  V_T511,V_T539J
FEATUERS    ABKRS,LTMST,TARIF,ANSAL,ASAL,PPMOD
INFO TYEPS  0000 0001 0002 0006 0007 0008 0009 0014 0015 2001 2002 2010 2011
SAUDI INFO TYPES--3352  3312
ABSENCES VALUATION WITH SUB SCHEMA  SAT0 AND PCR  SAOD
TIME WAGE TYEP VALUATION WITH PRCL 1 SUB SCHEMA  SAT0 PCR  SAOD,SA10
Leave Passage (Ticket Entitlement) Calculation
 Factoring--WITH SUB SCHEMA  SAL9 PCR  SAPF &SAVL  SAAL
Social Insurance
 Cumulation Wage Types
CUMULATIONS
BENEFITS IN PA
BENEIFTS WITH PAYROLL INTEGRATIONS
End of Service (EOS)
Data Medium Exchange
Forms
Occupational Hazard


      THIS IS REALTIME BASED TRAINING  WHICH CONVERS COMPLETE IMPLEMENTATION AND SUPPORT PROJECT

for more details
mail id   : madhupayroll@gmail.com
whats app no  :  91+9948932100

Tuesday, 30 July 2013

EIC

Employee Interaction Center 

The Employee Interaction Center (EIC) helps streamline the delivery of HR processes and services through a centralized delivery channel, based on a shared services model. Employees can contact the EIC at any time from anywhere to find answers to their most frequently asked questions, to update their HR data, to initiate new processes, or to obtain additional support for more complex HR inquiries. Interaction center agents working for the EIC accept and respond to incoming inquiries through multiple communication channels, therefore expanding the reach, flexibility, and convenience of service offerings to all employees.
The CRM Shared Services Framework (SSF) provides the technical and business platform to support multi-functional shared service organizations in executing their shared services strategy. The EIC provides the necessary enabling technology. From an HR perspective, the EIC incorporates additional Human Capital Management (HCM) integrated functionality, such as the ability to launch and track an HR process, store related HR documents in a Digital Personnel File (DPF), and authenticate the unique identity of callers using a question and answer format.
This business process applies when an employee requires assistance from HR in updating personal data and initiating a new process for a life event change. This data may not be accessible through self-services, or the employee may require additional guidance and support, beyond self-services, to complete the data change and process request. The EIC offers an alternative delivery channel to supplement self-service options and provide an additional layer of HR support. It is especially useful for companies with a geographically distributed workforce, virtual teams, or retirees with limited portal access.
To use this process, you must activate the following business functions:
To use HCM Processes and Forms with the Employee Interaction Center, you must activate the business function HCM, Administrative Services 03 (HCM_ASR_CI_3).

Process

This graphic is explained in the accompanying text.
  1. Identify employee (SAP CRM)
    Agents identify the employee who contacts the EIC to initiate a service request.
    The employee can contact the EIC using multiple communication channels:
    • E-Mail
    • Telephone
    • Fax
    • Chat
    The system can identify the account automatically using computer telephony integration with contact-attached data, or agents can manually search for employees to identify the contact using different search criteria.
  2. Authenticate employee (SAP ERP)
    Employee authentication data is provided, which allows the EIC agent to verify and validate the unique identity of the contact. Employees can maintain authentication questions and corresponding answers using SAP Employee Self-Service. The saved authentication data is stored in the SAP HR back-end system and can be retrieved by the agent from the EIC application, for additional verification and security.
  3. System guides agent (SAP CRM)
    Alerts and interactive scripts guide agents through the interaction. For example, if the customer is a gold customer, the agent can be alerted to be especially courteous. If a script is assigned to a campaign or a call list, the script is started automatically. Otherwise, the agent can start a script manually by choosing the script that is valid for the current situation. This makes customer service more consistent and is especially useful for new, part-time, or temporary agents.
  4. Process service request (SAP CRM)
    To process the service request, the EIC agent logs and records the customer interaction. Typically, specific attributes are assigned to each service request, such as category, description, status, priority, and so on. It is also possible to add a note or an attachment to the service request. Service Level Agreements determine the time frame allotted to respond and complete the processing of a specific service request, based on pre-defined service quality objectives.
  5. Dispatch to further processor (SAP CRM)
    If agents are unable to close the service request, they can forward or reroute it to a further processor or next level of support, such as a subject matter expert. As well as this manual routing procedure, you can set up an automatic routing procedure according to freely definable rules based on service request information. Once a solution is found, the current processor can close the request and send the solution to the employee, or return the request to the agent to provide the solution to the employee.
  6. Initiate data change request by EIC agent (SAP ERP; HCM Processes & Forms)
    The EIC agent can launch a new process (for example, the birth of a child) and data change request directly from the EIC using HCM Processes and Forms Integration. An Adobe interactive form is generated with pre-populated employee data. The agent can enter new data or comments and complete the required fields, then submit the form to initiate the process with pre-defined business and approval workflows. Status tracking and process monitoring are available using the process browser view and process documents (for example, a birth certificate) can be stored in the online Digital Personnel File (DPF).
  7. Update HCM data (SAP ERP)
    To update HCM data, the EIC agent accesses the HR back-end system directly from the CRM EIC. HR master data can be maintained and updated to reflect the requested data change.
  8. Wrap up interaction (SAP CRM)
    When the customer interaction is complete, the agent can wrap up the interaction and save all data.

    We provide excellent sap hr/hcm with all e-modules with real time scenarios
    for more deatils
    you can reach madhupayroll@gmail.com
     
     

Tuesday, 2 July 2013

ASAP METHODOLOGY

What is ASAP methodology ?

A stands for Accelerator. It is a sap tool, provides us a plan how a real time project will be done in real time scenario.

How many phases does it contain ?

It contains five phases:

1.Project preparation

2. Business blue print
3.Realization
4.Final preparation
5.Go live and support

1.Project preparation

Plan your project and lay the foundations for successful implementation. It is at this stage that you make the strategic  decisions are crucial to your project.



    • Define your project goals and objectives
    • Clarify the scope of your implementation
    • Define your project schedule, budget plan, and implementation sequence
    • Establish the project organization and relevant committees and assign resources
    • Prepare Project charter
    • Roles are defined
2.Business blue print
  Approach client side people with your Q & A data base and conduct workshop and gather required business process. Later prepare  As is business process and give presentation and get approval. once we prepare  as is then start preparing of  To be business process. while preparing to be document find gaps. to develop the gaps, write functional specs, later prepare  BBP and get approval from client people


3.Realization phase

Understand  landscape. Start baseline configuration (major scope ) is followed by final configuration (remaining scope). Prepare  customization document and user manual.Involve in unit testing.


4. Final preparation

Involve in  user training, integration testing,cut over activities,uploading master data and authorizations.Involve in open issues. involve in UAT. Upload data to production wit lsmw


5.Go live and support.

We provide sap hr/hcm online and class room training

for more details
madhupayroll@gmail.com
91+9948932100
   

Monday, 1 July 2013

UK Payroll tax tables

UK payroll tax tables

T5G01 Tax Rates
T5G02 Special Tax Code
T5G03 Tax Increase and Limit
T5G05 NIC Limits
T5G06 NIC Percentages
T5G08 NI Control Data Texts
T5G09 NI Categories (GB)
T5G0A Employee Group/Subgroup
T5G10 Pension Fund
T5G15 Court Order Deductions
T5G16 Court Order Indicator
T5G1T Pension Fund Texts
T5G20 SSP System Data (GB)
T5G21 SMP System Data
T5G22 SSP Qualifying Day Pattern
T5G23 Time Models for SSP Qualifying Day Patterns
T5G24 SSP Qualifying Day Pattern Calendars
T5G25 Occupational Sick Pay Schemes
T5G26 OSP-Related Data for SSP Offsetting
T5G27 SSP Rates Payable (GB)
T5G28 SMP Rates Payable
T5G2E SSP/SMP Exclusion Reason Texts
T5G2F SSP/SMP Exclusion Reasons
T5G2T Text for Occupational Sick Pay Schemes
T5G30 Pension Schemes
T5G31 Pension Contribution Calculation Rules
T5G32 Pension Holidays
T5G33 Pension Contribution Calculation Rule Bands
T5G34 Pension Contribution Calculation Rule - Flat Rates
T5G35 Pension Contribution Calculation Rule - Percentages
T5G36 Pension Contribution Calculation Rule - Mix
T5G37 Pension Scheme Types
T5G3T Pension Scheme Names
T5G40 National Insurance Earnings Ranges
T5G41 National Insurance Percentage Rates
T5G4T Text for Court Order Indicator
T5G50 Tax Districts
T5G51 Payroll Area PAYE Reference
T5G52 Tax District and Reference Details
T5G53 Permit Numbers
T5G54 End Of Year Processing Stamp
T5G55 HR-GB: Default Tax Code
T5G5T Tax District Name
T5G61 Business Mileage Bands
T5G62 Payment of Petrol Costs (Based on Engine Size)
T5G63 Payments for Private Fuel (Basis: Car List Price)
T5G64 Unavailability Reasons
T5G6T Unavailability Reasons Text