Sunday, 28 October 2012

PY Q n As Set 1

Q. What are the mandatory modules for HR to implement SAP Payroll ?
A. PA / OM / Time Management (basic) 

Q. What is the personnel subarea grouping for primary wage types used for?
A. You can use these groupings to specify which wage types may be entered for which personnel subareas.

Q.  What is the employee subgroup grouping for primary wage types used for?

A. You can use these groupings to specify which wage types may be entered for which employee subgroups.

Q. Permissible check for wage type is performed for each
A. EE subgroup grouping and PSA grouping

Q. Which criteria determine payroll accounting areas?
A. The payroll accounting area  is determined according to the HR country grouping, the employee group and the employee subgroup.

Q. Is there a way to define default values for the pay scale area and pay scale type?
A. Via TARIF feature. The return value must have the form xx/yy, when xx is the pay scale type, and yy the pay scale area. 

Q. Is there a way to define default values for the pay scale group and pay scale level ?
A. Pay scale group and levels can only be defaulted through ABAP development. There is no standard feature to default payscale group and level.

Q. In which tables Payroll constant will be stored & through which T-Code you are able to view the records?
A. Payroll constants are stored under tables T511K which can be accessed via SM30.

Q. Through which T-Code you are able to create a remuneration statement?
A. PC00_Mxx_CEDT (xx - denotes the molga for a country)

Q. What is the employee subgroup grouping for collective agreement provisions used for?
A. The collective agreement provisions grouping is required for indirect valuation of wage types in the Basic Pay infotype (0008).

Q. Can all wage types be entered into all Infotypes?
A. No. All wage types are not permissible for all infotypes (refer wage type groups concept). Wage types are permitted to be stored in payroll infotypes only if these are added to the wage type groups.  Eg Basic Pay IT0008 has wage type group 0008.

Q. What does the input permissibility of a wage type depend upon?
A. Input permissibility of a wage type depends on  the wage type grouping and wage type characteristics. The wage type characteristics are attributes of the wage type that determine as to what is permissible and not permissible, what are the maximum and minimum value limits , what are the units permissible, whether they are to be valuated directly (values entered) or indirectly (values as a reference to other wage type values).

Q. How can you define default wage types for the Basic Pay Infotype?
A. The system can suggest a default wage type for basic pay (IT0008), to do this appropriate wage type must be included in a wage type model. Here you define the default wage types and the sequence how they should appear in the infotype Basic Pay and whether you can overwrite the defaulted wage type or not. 

Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Revise Default Wage Types

After setting wage type model, LGMST feature needs to be defined. Feature LGMST has two return values: firstly, the maximum number of wage types that can be entered in the Basic Pay infotype (IT0008), and secondly, the wage type model the system is to use, which was defined above.

To access feature LGMST use following SPRO path or transaction PE03.
SPRO: Personnel Management -> Personnel Administration -> Payroll data -> Basic Pay -> Wage Type -> Enterprise Structure for Wage Type Model

Q. In which feature, default wage type is defined for Basic Pay Infotype?

Q. How does the system know when to trigger retroactive accounting for a particular employee?
A.Retroactive accounting recognition consists of four steps:
  • If you edit an infotype that is relevant to retroactive accounting, the system enters the start date of the changed infotype record in the following fields of infotype 0003 Payroll Status:
    • Earliest MD change (earliest master data change since last payroll run)
    • MD chng.bonus (earliest payroll-relevant master data change (bonus)). This field is only displayed for specific country groupings, it is not displayed for all personnel numbers.
  • During the next regular payroll run or correction run (off-cycle payroll type B), the system determines whether the date in the Earliest MD change and (if applicable) MD chng.bonus fields comes before the date in the Accounted to field.
  • If this is the case, the system performs retroactive accounting. It starts with the payroll period in which the date entered in the Earliest MD change and MD chng.bonus fields occurs. The system recalculates all payroll periods that lie between the date in the Earliest MD change and MD chng.bonus fields and the date in the Accounted to field.
  • The system deletes the date in the Earliest MD change and MD chng.bonus fields 
Q. How is the earliest retroactive accounting date determined for an employee?
A. The system uses the following values to determine the retroactive accounting limit:
  • For each payroll area, the system uses the earliest possible retroactive accounting period that is stored in the corresponding payroll control record
  • For each employee, the system uses the earliest personal retroactive accounting date that is stored in the Payroll Status infotype (0003)
  • For each employee, the system uses the hiring date of the employee The system uses these values to select the most recent date.
Q. What activities are possible when the payroll control record is set to “Released for Payroll”?
A. If you choose the function Release Payroll from the menu, you are prevented from changing infotype data records if such changes affect the past or present. This lock applies to the personnel numbers included in the payroll area concerned. Changes that affect the future are still permitted. You must execute this function in the menu before starting the payroll. If the status of the payroll control record was previously Exit Payroll, the Release Payroll function also has the effect of increasing the period in the payroll control record by 1.

Q. Can a posting run be deleted?
A. Yes It can be reversed before the Bank transfer.Once the transfer is done the payments need to be adjusted in the next payments.

Q. Where are payroll results stored?
A. Payroll results are stored in PCL2 cluster, which can be accessed using the transaction pc_payresult.

Q. Account assignment type characteristic used in SAP HR
A. The account assignment type of the symbolic account determines:
-The type of posting (for example, posting to expense accounts, debit posting, credit posting) and the process that the system uses in table T030 (Standard Account Table) to search for the assigned account in Accounting
-Which information the system should transfer to Accounting and from which table in the payroll result this information should be taken

Example: The wage types Basic pay and Overtime both represent personnel costs and should therefore be posted to expense accounts. You also want to assign these wage type amounts to Cost Accounting objects. Both wage types are dealt with in the same way as far as posting is concerned and can therefore be posted to the same symbolic account. You must specify the account assignment type C, since, in Accounting, there should be a posting to expense accounts and Cost Accounting should be provided with information.

Q. Where do you specify whether an employee is paid in cash or whether the money is transferred to a bank account?
A. IT 0009 (Bank Details )

Q. Is it possible to branch directly from the payroll log to master data and time data maintenance?
A. Yes. To some extent.

Q. Difference between PCR and CAP?
A. Difference between PCR and CAP is mentioned below:

PCR - The Personnel Calculation rule allows how one wage type is to be processed in different ways in payroll accounting

CAP - CAP is Collective Agreement Provision based on which the different groups of Employees are eligible for different kinds of pay scale structures and benefits and so on. CAP is based on the following components :
1) Pay scale type
2) Pay scale area
3) Employee subgroup grouping for CAP
4) Pay Scale Group and Pay Scale Level

An employee subgroup grouping for collective agreement provisions combines subgroups which are governed by the same valid collective agreement provisions. A provision is a specific labor law regulation within the collective agreement.

Q. PCRs and Employee Subgroup Grouping
A. A personnel calculation rule can consist of several subareas, each of which is characterized by an employee subgroup grouping for personnel calculation rules, a wage type, and a time type. An index function provides an overview, and enables you to switch from one section to another as well as delete individual subareas.

To facilitate differential processing, each employee subgroup must be assigned to a grouping for a personnel calculation rule. Each grouping is defined by SAP and, in this case, can have its own area depending on the personnel calculation rule.

Q. What are the Characteristics of a wage type?
A. These characteristics describe entering of wage types and not how they behave in payroll.

  • · You want to define a maximum wage type amount of $1000 and a minimum of $10.
  • · The maximum wage type number may be 100, the minimum 1.
  • · The wage type amount should not be included in the totals line of basic pay.
  • · You must enter a wage type amount.
  • · You should only be able to enter the number for a wage type.
  • · You want to set certain units of time and measurement for the number.
  • · You want to set certain units of time and measurement for the number.
  • · Wage types should be valuated indirectly.
Q. What is the remuneration Infotype used for?
A. The Employee Remuneration Information infotype (2010) describes the possible entries for different wage types. You can enter a variety of information for wage types in this infotype which is then processed accordingly during payroll.

In this infotype you can enter the following in combination with a wage type:
  • · a valuation basis entered simultaneously with the wage type
  • · extra pay for the valuation basis of the wage type still to be determined in payroll
  • · a premium indicator
  • · an overtime compensation type. 
Q. Naming convention for wage types
A. The following naming conventions are used for wage types:
  • /0** – valuation bases
  • /1** – cumulation of gross amount
  • /2** – averages 
  • /3** – country-specific, usually for social insurance 
  • /4** – country-specific, usually for tax 
  • /5** – legal net 
  • /7** – wage/salary plus ER shares
  • /8** –  factoring 
  • /84* – cost accounting
  • /A** – outgoing wage types in retroactive accounting period
  • /Z** – incoming wage types from the previous period 

Q. Briefly explain the two different ways to perform pay increase? In dynamic pay increase what are variants A, G, D, E, T , C and R?
A. The two ways are:
1.Simple pay scale increase using report RPU51000 which increases the wage types in customizing
2. Standard pay scale increase where the wage types entered in IT0008 can be automatically increased and the history of the wage types in IT0008 are also updated.

Only one variant can be defined for a wage type. You need to maintain table V_T510D in the customizing and run the program RPITRF00 to carry out the standard pay scale increase.

Make sure that you test your configuration and the execution of the report RPITRF00 only in the test system, run payroll test cases and take user acceptance before transporting these changes to the Production. It is highly recommended that you always do this in the supervision of a senior consultant with good sap payroll experience.

Variant AIncreases a wage type in IT0008 to an absolute amount
Variant GIncrease total pay in IT0008 to an absolute amount
Variant DIncrease by a difference by value or percentage.
Variant EValuate according to another pay scale group
Variant TAdd a new wage type to IT0008
Variant CDelimit an existing wage type in IT0008
Variant RReplace one wage type by another in IT0008

Saturday, 27 October 2012

Q n As - Set 1

A. IMG stands for implementation guide. It is a project support tool containing documentation on each and every activity that can be carried out using SPRO. The developers will customize the SAP HR system as per the customer requirements in the IMG. IMG further allows to create project IMG’s which limit the customizing nodes to the requirement of the projects and for each project IMG multiple views like MM, SD, HR etc can be created to get more specific.
IMG is accessed via transaction SPRO.

Q. What are the customizing step specific attributes?
A.  Below are the customizing step specific attributes
  • Mandatory activities. : These are activities for which SAP cannot deliver default settings (for example Organizational Structure). Customer-specific requirements should be stored for activities that are classified as mandatory.
  • Optional activities: SAP delivers default settings for these activities. These settings can be used if they meet the requirements.
  • Non-required activities: SAP delivers complete default settings for such activities and only in rare cases, do we need to adapt these settings (for example, if you need country specific settings)
  • Critical activities: One has to proceed with great care when carrying out these activities as any errors made here can have severe consequences.
  • Non-critical activities: One must also proceed with care when carrying out these activities, but the consequences of any errors will have less far-reaching than the critical activities.
Q. Describe the points of integration with other SAP Components.
A. Below are some of the points of integration
  • Personnel Development:  Plan and carry out training and job-related activities, which provide individual professional development for your employees.
  • Training and Event Management: organize and schedule training events and conventions.
  • Workflow: automates business processes, tasks are given to the right person at the right time.
  • Compensation Management: necessary for the administration of compensation (carrying out payroll, for example).
  • Personnel Cost Planning: used to project personnel costs on the basis of existing and planned organizational units.
  • Shift Planning: used to schedule the optimum number of appropriately qualified personnel on the basis of job requirements.
  • Capacity Planning: Logistics component used to schedule persons on the basis of their availability and qualifications to complete work for specific work centres.
  • HIS: perform simplified reporting for employee data in the organizational plan.
  • Manager’s Desktop: supports managers in their administrative as well as strategic daily tasks.

Q. What elements determine the enterprise structure for personnel administration?
A. Client, Company Code, Personnel area (PA) and Personnel sub-area (PSA)

Q. What elements make up the personnel structure?
A. Employee group, employee sub-group and payroll area.

Q. What elements make up the organizational structure?
A. Position, Job Key, Organizational Unit and Organizational key

Q. eCATT (extended Computer Aided Test Tool)
A. eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3.

Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.

eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.

Q. Why eCATT?
A. CATT is no longer supported by SAP for the creation of new developments. Hence all the test scripts developed in CATT now need to migrate/update to eCATT. Comparative to manual testing, the following are advantages of using eCATT:
  • Due to automation, testing time is reduced to a large extent.
  • Due to automation, less manpower is required for testing. This helps financially.
  • Due to automation, manual errors are reduced to large extent. Hence results in error free testing. This helps, as no further problems will occur while the usage of R/3 system by end users and hence increases the efficiency.
  • Proved to be extremely useful in implementation projects.

In regression testing, automated test scripts are an ideal method of quickly detecting errors. Automatic test logs make it easy to reproduce test results, enabling fast analysis and planning of further activities, leading to cost savings for the customer.
Q. Features of eCATT:
A. Following functions can be performed using eCATT:
  • · Test transactions, reports and scenarios.
  • · Call BAPIs and function modules.
  • · Test remote systems.
  • · Check authorizations (user profiles).
  • · Test updates (database, applications, GUI).
  • · Set up customizing tables.
  • · Test the effect of changes to customizing settings.
  • · Perform load testing.
  • · Check system messages.
  • · Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
  • · Supports CATT migration to eCATT.
  • · All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
  • · eCATT Objects can easily download & upload in XML with XSD format.
  • · There can be several versions of Test Scripts, which allows different implementations with different releases.
  • · The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.

Q. Difference between SE16 and SE16N.  
A. SE16 is a normal transaction.
  • SE16 allows you to view data stored in different fields in tables, structures etc.
  • SE16 is a data browser and it is used to view the contents of the table; we cannot change or append new fields to the existing structure of the table as we cannot view the structure level display using the SE16.
SE16N is an Enjoy Transaction.
  • With SE16N you can check number of entries in background – good for production environments where the table is very large and timeouts occur.
  • You can see technical names and descriptions for fields.
  • You are not limited to table width.
  • The results are displayed in ALV grid format.
Q. Finding list of roles assigned to different users
  1. Tcode SUIM; Roles -> By user assignment
  2. Tcode SE16; Table Name: AGR_USERS 

Q. Audit Report (RPUAUD00)
A. Audit report is used to determine changes made in made in Master Data. It can be accesses via SA38/SE38 

Q. What are long-term documents in audit report ?
A. Long-term documents are used for revision purposes. Changes made to the infotype are stored in the database or can be archived. Long texts are stored until they are deleted. The archiving object is called PA_LDOC.

Q. What are short-term documents in audit report ?
A. Short-terms documents are stored in the database. Short-term documents are evaluated differently to long-term documents. Short-term documents are evaluated according to date and time.

Q.What is the infotype to store personal data for an employee?
A. Infotype 0002 – Personal Data is used to store personal information of an employee. In some countries you could use infotype 0077- Additional Personal Data.

Q. How do you set up integration between Personnel Administration and Organizational Management?
A. Activating PLOGI ORGA Switch in table T77S0.

T-Codes for OM

PPOM - Change org Unit
PO03 - Maintain Jobs
P013 - Maintain Position
PO10d - Display Organizational Unit
P013d - Display Position
PO10 - Maintain Organizational Unit
PP01 - Maintain Plan Data (menu-guided)
PP02 - Maintain Plan Data (Open)
PP03 - Maintain Plan Data (Event-guided)
PP05 - Number Ranges
PP06 - Number Ranges Maintenance HR Data
PP07 - Tasks/Descriptions
PP69 - Choose Text for Organizational Unit
PP90 - Setup Organization
PP01 - Change Cost Center Assignment
PP02 - Display Cost Center Assignment
PP03 - Change Reporting Structure
PP04 - Display Reporting Structure
PP05 - Change Object indicators (O/S)
PP06 - Change Object indicators OS
PPOA - Display Menu Interface (with dyn.)
PPOC - Create Organizational Unit
PPOM - Maintain Organizational Plan
PPOS - Display Organizational Plan
PQ01 - Events for Work Center
PQ02 - Events for Training Program
PQ03 - Events for Job
PQ04 - Events for Business Event Type
PQ06 - Local Events
PQ07 - Resource Events
PQ08 - Events for External Person
PQ09 - Events for Business Event Group
PQ10 - Events for Organizational Unit
PQ11 - Events for Qualification
PQ12 - Resource Type Events
PQ13 - Events for Position
PQ14 - Events for Task
PQ15 - Events for Company
PSO5 - PD : Administration Tool
PSOA - Work Center Reporting
PSOC - Job Reporting
PSOG - Org Mgmt General Reporting
PSO1 - Tools Integration PA-PD
PSOO - Organizational Unit Reporting
PSOS - Position Reporting
PSOT - Task Reporting

T-Codes for Benefits

PA85 - Benefits - Call RPLBEN11
PA86 - Benefits - Call RPLBEN07
PA87 - Benefits - Call RPLBEN09
PA89 - COBRA Administration
PA90 - Benefits Enrollment
PA91 - Benefits - Forms
PA92 - Benefits Tables - Maintain
PA93 - Benefits Tables - Display
PA94 - Benefits - Access Reporting Tree
PA95 - Benefits IMG - Jump to Views
PA96 - Benefits reporting
PA97 - Salary Administration - Matrix
PA98 - Salary Administration
PA99 - Compensation Admin - rel. Changes
PACP - HR-CH : Pension fund, interface

T-Codes for Payroll

PC00 - Run Payroll
PC10 - Payroll menu USA
PE00 - Starts Transaction 
PE01 - Schemas
PE02 - Calculation Rules
PE03 - Features
PE04 - Create functions and Operations
PE51 - HR form editor
PRCA - Payroll Calendar
PRCT - Current Settings
PRCU - Printing checks USA
PRD1 - Create DME
PU01 - Delete current payroll result

PC00_MXX_CALC - Executing Payroll
PC00_MXX_CALC_SIMU - Executing payroll in test/simulation mode
PC00_M99_ABKRS Specify a payroll area
PC_PAYRESULT - Checking payroll results
PC00_M99_CWTR - Wage type reporter
PC00_MXX_CDTA - Run Preliminary DME Program
PC00_MXX_FFOT- Create the DME file

PC00_M99_DLGA20 - Use of wage types in payroll
PC00_M99_CIPE   - Creating posting runs
PCP0 - Display posting runs


PC00_MXX_CEDT - Remuneration Statements
PDF7 -  Delete Form in Customer Client
PDF8 - Copy Form from SAP Client to Customer Client
PDF9 - Copy Form within Customer Client
PC00_MXX_CLGA00 - Wage Type Statement
PC00_MXX_CLGV00 - Wage Type Distribution
PC00_MXX_CKTO - Payroll Accounts
PDF0 -Conversion Report for Remuneration Statement Forms
PDFA - Conversion of Payroll Journal Forms

(XX = Molga)