Below is the list of tables for UK country.Here G is meant for Great Britain.
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
Dynamic Actions are performed automatically by the system, depending on certain conditions. If maintaining one infotype has an effect on another infotype, the system automatically displays the second infotype for processing. Dynamic actions can run in the background i.e. the user does not see the run on the screen. A change in one field of an infotype might require, that certain other infotype be updated at the same time. The details can be specified as a dynamic event. It is automatically triggered by the system.
Ex:1)The Personal Data(0002) infotype is newly created, and the Number of children field is filled. Once the record is saved, the system automatically displays the Family/Related Person (0021) infotype and the Child subtype (2) for processing to enter the details about the spouse and the children.
Ex:2)An employee is hired, and the probationary period is entered in infotype Contract Elements(0016). Once this information is saved, the system automatically displays a record from the Monitoring of Dates (0019) infotype and the subtype Expiry of probation (1) for processing.
IGM Path for configuring the Dynamic Action:IMG - Personnel management - Personnel administration - Customize procedures - Dynamic actions.
Table: T588Z.
Q)Which characteristics does a day with day type 1 have?
A)Its OFF and Paid
Q)Can a posting run be deleted?
A)Yes It can be reversed before the Bank transfer.Once the transfer is done the pay menets need to be adjusted in the next payments.
Q)What activities are possible when the payroll control record is set to " Released for Payroll "?
A)When you set the status to Released for pay roll "\\\' you cant make any changed to master data. Its actully released for pay roll
Q)How does the system know when to trigger retrocative accounting for a particular employee?
A)You have to mention the retro active accounting date in IT 0003 in the relevant feild. other wise it will take the earliesr hiring date.
Q)Is it possible to branch directly from the payroll log to maser data and time data maintenance?
A)Yes you can go in a seperate sessions.
Q)How to create payroll area, pay scale types and levels for different employee group and subgroup?
A)To create Payroll Area you need to go to PM-PA-Organisation Assignment - Create Payroll Area-Check Default Payroll Area
To create Payscale Type and Payscale Area u need to follow : PM-PA-Payroll Data-Check Payscale type/ Check Payscale Area
Payscale Levels and groups are created while doing the step Revise Payscale groups and levels and Define Salary ranges.
Q)Do you know in OM -> copy plan version?
A)To copy plan version the Tcode: RE_RHCOPL00.
This report is only for copying objects from one planversion to another planversion to keep updated structures.Always only one plan version would be active which is current.This report does not help to copy any masterdata.
Q)How do I design the Indian Remuneration statement for the first time as the IN01 which is copied and renamed is showing blank.
A)After copying he IN01 form go into the form and click on the windows where you find so many entries to be made.
Q)What actually happens in real time Recruitment?
A)Real Time in the sence of SAP or IT or Domain. You should have asked him the question, Ok it should be SAP for interview For SAP Consultant. Any company wants a sophisticated Work to be done and with more useful and accurate result even after spending more and more on EPR, So SAP Recruitment helps to Rect people of the client to get the exact people for not only their experiance , with also Educatonal , Exp, Skills, Past experiance and all reqd areas with out enering all the data of the requirement.
As in normal people has to sit on the requirement of he position and then shorlist all the applications, it also helps to know the internal employees to call for intvs and the best way of shorlisting is going for Profile Match Ups, and reruitment is useful for integration with all other modules for PD, PY also for relevant reports and up gradations.
Even rect modules will be able to send the recruiter a POP up saying the Position is vacant and it should be filled with requirement.
Q)I got struck in PB10 initial entry screen. While assigning personnel officer by default its showing the standard one like APPL's admin group only. Its now accepting what I have created under PA define admin group and I assigned under define admn group also (PINCH).
A)Once you assign your administrator group under PINCH, please check whether you activated or not and also check your groupings.
Q)I am facing problem in PA40. While entering the inputs in Personal data in hiring action, I am having the field which is called " CUIL/ CUIT" ( Which it shows key field) . I do not know about this field and how to enter the data in this field. I would like to remove this field from personnel data. IIIly i am having one more field in Bank details in hiring action, I am having the field " Bank Key " I would like to know how to delete/ remove this field from the action, or else how to input the data in this field.
I can suggest you can hide this field by using the following path. Not only this you can hide any field in your screens. Here is the IMG Path :SPRO-->personnel management-- >personnel administration- ->change screen modifications;
HERE
Mod.pool--- MP000200 ,Screen --- 2000,Feature--- P0002,Variable key--- 29,Alt.screen---2029,Next screen--- 0
Then execute details, in 011 -- Q0002-CCUIL -- Worker identification code -- activate Hide checkbox.
You can use screen modifications and hide the field. after you hide it and save the settings, CCUIL will not be seen on the screen. Same procedure can be used for bank key too. In the same screen you can also choose the options to set a specific field to be Optional,and Mandatory.
Q)Which time we have to consider as a login time?
Is it 1) swiping machine recorded time or 2) System login time.
A)If an company is going for both the systems, first the company want to decided to go for swapping card system or system log in time, if you required the both, then you discuss with the time administrator to design for both, as per the company requirement the time administrator will decided.
Integration is nothing but linking the different sub-modules of SAP HR which will help us to have the consistent data throughout the system.The Table is T77S0.
PLOGI : PLOGI for integrating paln version
PLOGI : ORGA for integrating OM & PA
PLOGI : PAPLI for integrating Recruitment & PA
Integration with Other Modules i.e (HR : FI)
T Code: T.CODE PC00_M99_CIPE
Path: Wage Type->symbolic- >GL Code Assignment in the back end in both HR and FI system
This feature is only used if you have implemented the SAP Concurrent Employment model (for Global Employment).The system then allows you to send an employee on an assignment to a an affiliate company in the host country, and temporarily exit him in the home country. At the end of the assignment you repatriate him. Hence this feature informs the system which actions are related to Global Employment activities.Otherwise it has no effect on your system.
Basically ACTCE feature recognizes the action if you are trying to perform any action on the person who already exist in your system and have valid actions.
In general, concurrent employment is defined as an employment situation in which an employee has several personnel assignments with one organization. The organization may be a group of employers or an enterprise. The personnel assignments may occur simultaneously, and the tasks required may vary from job to job. The concurrent employment solution provided by mySAP ERP includes key functional areas, such as personnel administration, benefits, time management, payroll, and reporting. These key functional areas together with the technological framework provide the necessary infrastructure to support concurrent employment.
Technological FrameWork
The variety of concurrent employment situations and the myriad administrative burdens that often accompany assignmentscan make HR professionals wonder how they can transform their organization from a traditional "one person, oneassignment" model to a "one person, multiple assignment" culture. The answer is a technological framework that enables you to manage concurrent employment situations. This technological framework consists of the concurrent employment model delivered with mySAP ERP.
Concurrent Employment Model
The concurrent employment model in mySAP ERP describes the relationship between the employee and the organization.The most important concepts are as follows:
* Each employee can have multiple personnel assignments. A permanent record of personal information, including the person's name and address, is kept independent of the individual assignments.
Each personnel assignment is linked to the person.
A personnel assignment describes the work that the person needs to do, when the work is to be done, and how that work is to be paid, among other characteristics. In mySAP ERP, each personnel assignment is given a unique personnel number for this purpose. For example, Donna has two personnel assignments: one at the pediatric clinic as a pediatric nurse and the other at Memorial Hospital as a cardiology nurse. Both assignments are under the umbrella of the same healthcare institution and are active simultaneously. Because each personnel assignment has a unique number, you can easily identify the characteristics of each assignment within mySAP ERP.
The concurrent employment model in mySAP ERP is flexible enough to be used for different kinds of concurrent employment situations. For example, the solution does not limit the number of personnel assignments that a person can have. Each personnel assignment refers to a person who might hold one or several positions at the same time; the solution can track which assignments are active or inactive. This concurrent employment model serves as the framework for the concurrent employment solution in mySAP ERP. The key functional areas have also been enhanced based on this model.
The time management capabilities of mySAP ERP, which are delivered in mySAP ERP HCM, support HR professionals in the planning, recording, and tracking of an employee's work history, the days worked, and the days missed due to illness, vacation,and so on. It is an efficient and effective time managementsystem that you can adapt to meet your specific needs.
Time management is subject to fundamental regulations that are rather complex in the case of employees in concurrentemployment situations. This is why SAP enhanced the time management capabilities of mySAP ERP to manage employees' working time across simultaneously active personnel assignments.
Work Schedules:The work schedule is an essential element of successful time management in concurrent employment scenarios. For example, Donna has two work schedules: one for the pediatric clinic for her early shift and break times and another at Memorial Hospital for her late shift and its break times. From her organization's perspective, it is important to verify that Donna works the hours she has been assigned in both jobs. With mySAP ERP, the time administrator at the healthcare institution can view Donna's work schedules in one simple report. Additionally, HR personnel at both the pediatric clinic and Memorial Hospital can monitor her work independently. Furthermore, mySAP ERP allows you to combine work schedules under different views. This allows time management administrators to catch any scheduling conflicts and prevent overstaffing. And this information empowers administrators to make the right staffing decisions on a case-by-case basis.
Time Evaluation:
The time evaluation capabilities of mySAP ERP valuate the time an employee has worked, along with time missed due to sickness, vacation, and so on. You can calculate overtime, manage time accounts, update time quotas, and check working times. In a concurrent employment environment, time evaluation is a critical tool for valuating the time an employee has worked and the days missed for different personnel assignments that are simultaneously active. Additionally, the time evaluation and payroll capabilities of mySAP ERP are completely integrated, which considerably simplifies the process of paying employees with multiple personnel assignments.
Payroll:
Because of the scope and complexity of tasks, payroll software requires a high degree of accuracy and flexibility. After all, employees expect to be paid the correct wage in a timely manner. A payroll system must also be flexible enough to support numerous legal and organization-specific regulations. Concurrent employment situations add even more complexity to the process.
Payroll Process Architecture:
In a concurrent employment environment, it is often necessary to run payroll simultaneously for each personnel assignment. This is now possible, thanks to a new payroll architecture. The parts of the payroll process that have to do with a personnel assignment are processed sequentially. The parts of the payroll process that are grouping-related are processed together in a synchronization point. For example, in the chart, the tax, net calculation, retroactive accounting calculation, and payment calculations are performed simultaneously at synchronization points. The payroll log displays payroll results both from the perspective of the person and from the perspective of that individual's personnel assignments.
Payroll Payment and Posting to Accounting:
A very important aspect of the payroll is the payment - informing the person about the payment and performing the actual payment by means of a check or a bank transfer. At the same time, it is important for the employer to record these payments accurately.
Payroll Payment:
Once the payroll has been run, it is necessary to pay wages and salaries to the person, taking into consideration bank requirements and payments to third parties. In concurrent employment, the person usually likes to have the payment and bank transfer combine the net amounts from the different personnel assignments. The mySAP ERP solution for concurrent employment makes this possible by defining a payment group.
Country Versions for Concurrent Employment Solution:
One of the greatest challenges for international enterprises is compliance with the laws and regulations of the country in which they operate. For example, the regulations for calculating taxes or garnishments may differ materially. Currently, mySAP ERP provides payroll capabilities for concurrent employment based on a country-specific solution for the United States and Canada only. The enhanced payroll architecture and other solution elements described in this document only pertain to the U.S. and Canadian country versions with others to follow.
Read more!
Positive Time Management:
Positive Time Management is when an employee has to "Clock-in and Clock-out" each day. There must be a time entry or absence entry for every scheduled work day.
Negative Time Management is when an employee only has to record absences or "variations" to the work schedule - works overtime, works other than regular scheduled hours, vacation, jury duty, funeral leave, etc.
Hourly employees - those paid for each hour worked usually use positive time recording, Salaried employees, paid regular amounts regardless of time worked usually use negative time recording.
The details are as follows : There are 2 Mechanisms of time recording are available
1.Positive time recording :- Actual times are recorded
This method completely records all actual times, that is, all transactions such as actual working times, absences, and so on.
2.Negative time recording :- Deviations from a work schedule are recorded.
Recording Only Deviations to Work Schedules
This method records only employee time data that represents exceptions or deviations to the work schedule assigned to employees. Here you can include the most current data, such as employee illnesses, schedule and record substitutions, and enter annual leave for employees.
SAP provides various Info types for time recording purposes.
All above explanations are correct, however to simplify :
In Positive time, where you need to maintain all in time out time either through Time Recorder or some time it is uploaded after maintaining manually.
Example:
When you record in time as 8.30 am and out time as 19.30 pm. against your DWS 8.30 am to 16.30 pm. applicable on that day, the additional 3 hrs automatically gets into Overtime...whereas if you don't record your in time or out time any day against your X planned working hours in DWS, it means its your absent that day.
Whereas in negative time: You maintain these additional 3 hrs in Overtime Infotype. and absence in 2001 infotype for that PERNR.
Below is the list of transaction Codes that we use regularly in Payroll.
PC00_M99_CLSTR Display Payroll Results
PC00_M99_CALC Payroll Driver (International)
PC00_M99_ABKRS Specify a payroll area
PC00_M99_CLSTPC Display PC Cluster: Personal Calendar
PC00_M99_TLEA Leave Overview
PC00_M99_TLEA30 Batch-Input: Annual Leave
PC00_M99_CPRC Access Payroll Calendar
PC00_M99_MOLGA Specify a personnel country grouping
PC00_M99_CLJN Payroll Journal - International
PC00_M99_DLGA20 Use of Wage Types in Payroll
PC00_M99_UDIR Restore the Payroll Results Directory
PU00 Delete Personnel Data
PU01 Delete Current Payroll Result
PU03 Change Payroll Status
PU2 Archive Data
PU0 Wage Type Copier
PU95 Edit Wage Type Groups and Logical Views
PU96 Edit Wage Type Groups
PU97 Edit Logical Views
PU98 Assign Wage Types to Wage Type Groups
PUOC_xx (xx = Country Code) Off-Cycle Workbench
PEST Maintenance of Process Model
PUST HR Process Workbench
Pay scales:
PC00_M99_U510 Simple Std Pay Increase for Indirectly Valuated WTs
PC00_M99_IRTF Enhanced Std Pay Increase (Indirect and Direct WTs) with Batch Input
PC00_M99_ITUM Pay Scale Reclassification acc.to Age or Pay Scale Membership Period
Third party
PC00_M99_URMA Acknowledgement Report for Third Party Remittance
PC00_M99_URMU Update of Remittance Tables from TemSe-Object
Forms
PC00_M99_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_M99_CLGA00 Wage Type Statement
PC00_M99_CLGV00 Wage Type Distribution
PC00_M99_CKTO Payroll Accounts
PDF0 Conversion Report for Remuneration Statement Forms
PDFA Conversion of Payroll Journal Forms
Transfer Activities
PC00_M99_CIPE Posting to Accounting: Create Posting Run
PC00_M99_DKON Posting to Accounting: Wage Type Assignment - Display G/L Accounts
PC00_M99_CIPC Posting to Accounting: Search for Payroll Results not Posted
PC00_M99_URMR Reconciliation of Transfers
PC00_M99_URMW Maintain Wage Types According to Assignment to HR Creditors
PC00_M99_URMD Undo Third-Party Remittance Runs
PC00_M99_URMP Create Third-Party Remittance Posting Run
PC00_M99_CMLI0 Cash Breakdown List (International)
PC00_M99_CDTA Preliminary Program- Data Medium Exchange for Several Payment Runs
Tools
PE04 Editor for Calling Functions and Operations
PE03 Editor for Calling Features
PE02 Editor for Calling Personnel Calculation Rules
PE01 Editor for Calling Personnel Calculation Schemas
PE51 Call the Form Editor
PU12 Interface Toolbox
PDSY HR-Documentation Maintenance.
Infotypes:
Infotypes are units of information in the Human Resource Management System.
Infotypes are used to record employee data for administrative, time recording, and payroll purposes is of primary importance for master data administration in HR.In the SAP System, the information units used to enter master data are called infotypes.
They are also used to group related data fields together. They provide information with a structure, facilitate data entry, and enable you to store data for specific periods.
For your quick reference look into the below infotype range for each sub-module of SAP HR
Number Range Description
0000-0999 Personnel Admin
1000-1999 Personnel Planning/Org Mgt
2000-2999 Time Data
4000-4999 Applicant Data (recruitment)
The infotypes for Personnel Administration would fall between 0000-0999,for Personnel Planning/Org Mgt would fall between 1000-1999 and 2000-2999,4000-4999 for Time Management and Recruitment respectively.
Apart from the above SAP Defined Infotypes we can creat our own custom Infotypes as per our needs.The range for the Custom Infotypes should start with 9 and should be between 9000-9999.
Infotypes are characterized by the following 3 main things
1.Infotype Structure:
To the user, infotypes appear as data entry screens. They contain whole series of information (for example, last name, first name, date of birth) that you enter in data fields. Data fields concerning the same or similar subject matter are combined into data groups or information units.
In database terms, infotypes represent a data structure or set of related data records. When you update an infotype, old data is not lost but is instead stored in the system for historical evaluation purposes.
2.Data Entry:
You perform data entry as follows:
Your entries are automatically checked for accuracy and against table entries.
Predefined default values help you to enter and maintain data.
Checks and default values depend on the employee’s organizational assignment. The organizational assignment determines the relevant information used from time recording, wage type and pay scale structure.
3:Time-Dependent Storage of Infotype Data:
When you update an infotype, the old data may not be lost. Instead, it must be retained so that past data can be evaluated. When you update an employee’s personal data, the old data is automatically time-delimited. The system creates a validity period for each infotype record. As a result, each employee infotype has several data records that differ from each other by their validity periods.
Hope you referred the previous post and are ware of what's Infotype,its use and the structure.
So Apart from the standard SAP defined Infotypes,we can create custom infotypes to meet our requirements.
Here is a step by step procedure of Creating the Infotype and Configuring the Subtypes for the newly created Infotype.
Go to Transaction PM01.
Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
Select the 'Employee Infotype' radio button.
Select the 'PS Structure Infotype'.
Click on Create, a separate table maintenance window appears…
Create a PS structure with all the fields you want on the Infotype
Save and Activate the PS structure
Go back to the initial screen of PM01.
Click on 'All' push button.
Click on 'Change'(pencil) button
Select your Infotype and click on 'Detail' (magnifying glass) button
Give 'T591A' as subtype table
Give 'T591S' as subtype txt tab
Give your subtype field as subtype field
Save and come back to PM01 initial screen
Click on 'Infotype Characteristics', Infotype list screen appears
Click on 'Change' (pencil) button
Click on 'New Entries'
Enter your Infotype number and short text
Here you have to set different Infotype Characteristics as per the requirement.
Save your entries.
Now the Infotype is created and ready to use.
If you want to change the layout of the Infotype as per your requirement…
In the PM01 initial screen…Select 'Screen' radio button and give 2000 as the screen name, then click on edit.
In the next screen, select 'Layout Editor' and click 'Change'.
Screen default layout appears, here you can design/modify the screen; change the attributes of the fields, etc.
Save and activate. (Don't forget to 'Activate at every level).
I have come across a good number of questions during the interviews on Wage Types.So here are the basic steps in creating a wage type.All the below steps are not mandatory, depending on the kind of wage type you wish to create.
1.Look at Existing Wage Types
2. Copy an Existing Wage Type
3. Maintain HR Payees and Creditors
4. Select the Symbolic Account for Your Wage Type
5. Test Your New Wage Type
In SAP-HR the tables has the very important role to pick your data and to faster enough your configuration insted of going through the menu paths.Here is an useful information about the SAP-HR tables.
All personnel administration tables start with PA and the infotype number behind it.
All personnel development/OM tables start with HRP and infotype (e.g. 1000) behind it.
All recruitment tables start with PB and infotype number behind it.
Transaction SE16 (data browser) is also useful. As mentioned above, the PA infotype tables all begin with PA and are followed by the infotype number e.g. PA0001 for the Org Man infotype.
PA* - PA infotype tables
PCL* - HR clusters
PB* - recruitment tables
PCERT - payroll posting runs
Another useful table is CATSDB for CATS, and PTEX2000 for the CATS transfer table for infotype 2001/2002.
The rest of the HR Tables are as follows:
DD01L Domains
DD02L SAP tables
DD03L:Table Fields
DD03T DD: Texts for fields (language dependent)
DD04L :Data elements
DD04T R/3 DD: Data element texts
DD05S :Foreign key fields
DD06L :Pool/cluster structures
DD20L :Matchcode Ids
DD24S :Fields of a matchcode ID
T000 :Clients
T001 :Company Codes
T001E :Company code-dependent address data
T001P :Personnel Areas/Subareas
T012 :House banks
T012K :House bank accounts
T012T :House bank account names
T500L: Personnel Country Grouping
T500P: Personnel Areas
T500T :Personnel Country Groupings
T501 :Employee Group
T501T :Employee Group Names
T502T : Status Designators
T503 :Employee Groups / Subgroups
T503K :Employee subgroup
T503T :Employee Subgroup Names
T504A :Benefits - Default Values (NA)
T504B :Benefit Option Texts (North America)
T504C :Benefit Type (NA)
T504D :Benefit Credit Group Amount
T504E :Benefit Amount
T504F :Benefit Costs
T508A :Work Schedule Rules
T508T :Texts for Employee Subgroup Groupings for Work Schedules
T510 :Pay Scale Groups
T510A :Pay Scale Types
T510F :Assign Pay Scale > Time Unit, Currency
T510G :Pay Scale Areas
T510H :Payroll Constants with Regard to Time Unit
T510I :Standard Working Hours
T510J :Constant Valuations
T510L :Levels
T510M :Valuation of pay scale groups acc. to hiring date
T510N :Pay Scales for Annual Salaries (NA)
T510S :Time Wage Type Selection Rule
T510U :Pay Scale Groups
T510Y :Special Rules for Wage Type Generation
T511 :Wage Types
T512R :Cumulation Wage Types in Forms
T512S :Texts for Cumulation Wage Types in Forms
T512T :Wage Type Texts
T512W :Wage Type Valuation
T512Z :Permissibility of Wage Types per Infotype
T513 : Jobs
T514S :Table Name Texts
T514T :Field Name Texts
T51D2 :Wage Type Classes
T51D3 :Reduction Rules
T51D4 :Cumulation Rules
T527X :Organizational Units
T528B :Positions - Work Centers
T528C :Wage Type Catalog
T528T :Position Texts
T529A :Personnel Event
T529F :Fast Data Entry for Events
T529T :Personnel Event Texts
T52BT :Texts For HR Objects
T52C0 :Payroll Schemas
T52C1 :Payroll Schemas
T52C2 :Texts for Personnel Calculation Schemas
T52C3 :Texts for Personnel Calculation Schemas
T52C5 :Personnel Calculation Rules
T52CC :Schema Directory
T52CD :Schema Directory
T52CE :Directory of Personnel Calculation Rules
T52CT :Text Elements
T52CX :Cross References via Generated Schemas
T52D1 :Valid Processing Classes
T52D2 :Valid Values for Processing Classes
T52D3 :Valid Evaluation Classes
T52D4 :Permitted Values for Evaluation Classes
T52D5 :Wage Type Groups
T52D6 :Wage Type Group Texts
T52D7 :Assign Wage Types to Wage Type Groups
T52D8 :Valid Processing Classes - Texts
T52D9 :Valid Values for Processing Classes - Texts
T530 :Reasons for Events
T530E :Reasons for Changes
T530F :Reasons for Changes
T530L :Wage Types for Special Payments
T530T :Event Reason Texts
T531 :Deadline Types
T531S :Deadline Type Texts
T533 :Leave Types
T533T: Leave Type Texts
T539A :Default Wage Types for Basic Pay
T539J :Base Wage Type Valuation
T539R :Events for Standard Wage Maintenance
T539S :Wage Types for Standard Wage Maintenance
T548 :Date Types
T548S :Date Conversion
T548T :Date Types
T548Y: Date Types
T549A :Payroll Areas
T549B :Company Features
T549C :Decision Trees for Features (Customers)
T549D :Feature Directory
T549L :Date modifiers
T549M :Monthly Assignment: Payroll Period
T549N :Period Modifiers
T549O : for date modifier
T549P :Valid Time Units for Payroll Accounting
T549Q :Payroll Periods
T549R :Period Parameters
T549S :Payroll date types
T549T :Payroll Areas
T549M :Monthly Assignment: Payroll Period
T549N :Period Modifiers
T549O :Text for date modifier
T549P :Valid Time Units for Payroll Accounting
T549Q :Payroll Periods
T549R :Period Parameters
T549S :Payroll date types
T549T Payroll Areas
T554S :Absence and Attendance Types
T554T :Absence and Attendance Texts
T554V :Defaults for Absence Types
T554Y :Time Constraints in HR TIME
T555A: Time Types
T555B :Time Type Designations
T559A: Working Weeks
T559B :Name of Working Week
T572F :Event Texts
T572G :Allowed Values for Events
T572H :Event Value Texts
T582A: Infotypes
T582B :Infotypes Which Are Created Automatically
T582S :Infotype Texts
T582V :Assignment of Infotypes to Views
T582W :Assigns Infotype View to Primary Infotype
T582Z :Control Table for PA Time Management
T584A :Checking Procedures - Infotype Assignment
T588A :Transaction Codes
T588B :Infotype Menus
T588C :Infotype Menus/Info Groups
T588D :Infogroups for Events
T588J :Screen Header Definition
T588M :Infotype Screen Control
T588N :Screen Modification for Account Assignment Block
T588O :Screen Modification for Assignment Data
T588Q :Screen types for fast entry
T588R :Selection Reports for Fast Data Entry
T588S :Screen Types for Fast Entry
T588T :Menu and Infogroup Designations
T588V :Business object type
T588W :Event types for infotype operations
T588X :Cust. composite definition of event types for IT operations
T588Z :Dynamic Events
T591A :Subtype Characteristics
T591B :Time Constraints for Wage Types
T591S :Subtype Texts
T596F :HR Subroutines
T596G :Cumulation wage types
T596H :_Cumulation wage type texts
T596I :Calculation rule for cumulation wage types
T596U :Conversion Table
T599B :Report Classes
T599C :Report Classes
T599D :Report Categories
T599F :Report Classes - Select Options
T777A :Building Addresses
T777T :Infotypes
T777Z :Infotype Time Constraints
T778T :Infotypes
T778U :Subtypes
Error Messages tables:
T100 :Messages
T100A :Message IDs for T100
T100C :Control of messages by the user
T100O :Assignment of message to object
T100S :Configurable system messages
T100T :Table T100A text
T100V :Assignment of messages to tables/views
T100W :Assign Messages to Workflow
T100X :Error Messages: Supplements
You can leave your comments on any other important information on Tables,so that I can add up to the above list.
VDSK1 is the feature to represent the Organizational Key which is important to run diverse authorization checks by organizational assignment in SAP HR.The Organizational Key enables you to define the organizational assignment more exactly.It Consists of elements from Enterprise Structure and Personnel Structure.Its content is derived from either the Organizational Assignment IT-0001 or from the manually written entries.
The planned remuneration specification feature (LGMST) determines default wage types depending on various values (for example, country, employee group and subgroup) for the basic pay Infotype 0008.The second part of the issued return value forms the name for the wage type model.You can follw the table:V_T539A
IMG -> Payroll: India -> Reimbursements, Allowance and Perks -> Assign wage type model for Pay scale grouping for Allowances
Explanation:
1. Press the button ‘Feature (LGMST)’.
2. Choose sub object: Decision Tree
3. Press ‘Change’ button.
4. Create an entry for Molga country grouping ( Ex: 40 for India)
5. Create entry for different employee group
6. For each employee group, create entry for different employee subgroup
7. For each employee subgroup, create the return value as per your requirement.
8. Finally,Check the feature and if there is no error,then save the feature.
If you are assigning a Planned working time to an employee for the first time, you can use this feature SCHKZ to generate a default work schedule according to the employee's organizational assignment.
The feature is used in assigning the work schedule rule (general) defined for particular personnel sub area. When ever any action is run, the IT 0007 is updated with the default work schedule assigned in the feature.
IMG Path: IMG >Time management>Work schedule>Planned working time.
Explanation:
1.Click on the sub node “ Set default value for the work schedule"
2. Maintain the feature SCHKZ
3. Putting the cursor on the feature and then select the options "Create" . Then select the option field for decision operation and select WERKS (personnel area)
4. Then select all the personnel area relevant to the Sree’s Group. To each of the PA select its corresponding PSA. (BTRTL)
5. Then maintain the respective work schedule rule against all the selected PSA
6. After creating all the work schedule rule against the PSA click on the check button before you activate it
7 .Save your settings .
Q:Payroll Results
How do you post the payroll results to FICO? I created one symbolic account and assigned the
same to Salaries GL Account and then completed the other configuration steps needed to complete
the procedure. However, when I tried to run the simulation for posting to FICO, I got the message
“Document is not generated”.
A: If you have selected “Output Log” at the beginning of your configuration procedure, it will tell you at the bottom part what went wrong.
Q:Components
What is the basis of valuation of certain wage components such as Provident Fund? Where does
one configure it? A corollary question is what if another component – i.e., Special Allowance is
made as basis of calculation at another time? How is this configured?
A: Go to view V_T511 wage type char and read the F1 help for field Indirect Evaluation module. Module PRZNT will be applicable in this case. Also read help for V_T539J. Both these nodes can be found under Payroll Date>Basic Pay.
Q: Deduction Wage Type
We have a deduction wage type displayed in the window of our pay slip that shows a negative value.
This causes problems and we have tried several measures to correct this including conversion rule 16 for our wage type in the same window but so far, without any success. How can we correct or delete the negative sign?
A: You can review OSS Note 406977.
This is a collective note of issues with RPCEDTx0 with examples of problems and solutions.
Q: Payroll Simulation
How do I correct the payroll simulation entry and check the correctness of our master data? What if one
hundred employees get rejected due to error 167-process health plans. What does the following error
mean?
“No entry for plan DENT/cost variant.
FMDN/key////x00000000000000”
A: You should check for the cost element associated and the validity of cost rule for this plan. To do this,
check your configuration under Benefits>Plans>Health Plans>Define cost variant and define cost rules.
Q:Leave Quota
How do I make sure that if an employee goes over the limit of a leave quota , the future leave accrual will be
reflected accurately?
A:Configure the negative deduction and check these through the rules.
Q:IT0015
I need to capture a reason in additional payment IT0015. The reason code is “save” in this infotype.
I tried to capture for reason A Example to ADDWT 9999 if Reason ADDWT9998. How can I check the
reason in IT0015 for accuracy?
A: You can try using this to start with: ‘TABLEP0015> VARGBPREAS’
Then, use the variable key to define the different reasons.
Q:Payroll Simulation
Why is the system not picking up the values changed this month by default during payroll simulation? However, when I tried last month’s retro date, it picks up correctly. How can this issue be corrected?
A: You can check the “Earliest MD change” date on infotype 0003. If you have done that already and
payroll simulation still doesn’t function by default, then there is a problem with your infotype and/or wage type
retro settings. Check table T582A.
Q:Single Payroll
Is it possible to configure a single payroll to pay an individual in multiple currencies?
A: No. The system can be configured to pay in multiple currencies but not to pay an individual in multiple
currencies.
Labels
- Benefits (1)
- CATS (1)
- Concurrent Employment (1)
- Custom Infotype (1)
- Dynamic Action (1)
- FAQs (2)
- Features (4)
- HR (1)
- Infotypes (2)
- Integration of SAP HR (1)
- OM (2)
- Organizational Management (1)
- PA (2)
- PY (3)
- SAP HR Interview Questions (1)
- Structural Authorizations (1)
- T-Codes (8)
- Tables (2)
- Time Management (1)
- TM (3)
- Travel Management (1)
- UK Specific Tables (1)
- Wage Types (1)
Browse by Categories
Archives
-
▼
2009
(16)
-
►
March
(13)
- Integration
- ACTCE
- Concurrent Employment
- Positive & Negative Time Management
- T-Codes for Payroll
- Infotypes
- Creating Infotype and configuring Subtypes for tha...
- Creating Wage Types
- SAP HR Tables
- VDSK1-Organisational Key
- LGMST-Planned Remuneration
- SCHKZ-Default Work Schedule
- SAP HR Interview Questions and Answers-OM,PA,TM,PY...
-
►
March
(13)
