|
Infotype:
A set of data grouped together into areas with similar content, for example, personal data, planned working time, organizational assignment, basic pay. This helps in processing & capturing of record for further use in the system. Therefore, if you see in infotype 0001, you would get many related information such as Employees Pernr, Name, Employee Group, Employees subgroup, Position, Designation & Personal Area, Personal subarea, Cost center where employees cost would be booked etc.. These information are related records required for the further processing. From a technical point of view, the structure of infotypes
reflects a data grouping and can be identified by a four-digit key. Infotypes
are also carriers of system control features, for example, time constraints,
retroactive accounting relevance, and so on.
Why do we use infotypes in HR? Two special reasons - Security and History. Security - Some of the HR data can be seen and changed by the employee - address, tax information, etc. - and some cannot - pay, evaluations, etc. Thus, employee information has to be separated out into various groupings that can have individual security settings applied for who can see what data and who can change that data. History - HR data is time specific. You have a certain pay rate, but as of the first of next month you get a pay raise. Or you move to a new address as of July 1st. The data about your pay must be retained so Payroll knows what to pay you today and then must know what to pay you next month. And that history must be maintained for reporting - What was YuLin's pay rate since hire date? So each infotype, or group of information, has a specific start date and end date during which it is valid. As HR is related to time, we require old data as well as new data. The data we enter into the infotypes are automatically checked for accuracy and against the table entries. In simple, HR data is huge and to access data easily we
require infotype.
What is the difference between internal table and infotype? An infotype is a 'record' or a 'screen' which holds data against an employee or PD object such as a position, org.unit etc. A table stores values about an infotype and the way it will function. Main program generates internal tables for infotypes at runtime. Infotypes have an associated database table and a structure . Example of Infotype in SAP Infotypes 0000 Events 0001 Org assignment 0002 Personal info 0003 Payroll data 0007 Work time 0008 Basic pay 0014 Reoccurring pay 0015 1 X pay 0027 Cost Center 0041 Event Dates 0057 Membership dues 0165 Over ride to limits on deductions 0167 Health 0168 Insurance 0169 Savings 0170 Spending 0194 Garnishment reduction 0195 Garnishment order 0207 Residence Tax 0208 Work Tax 0209 Unemployment Tax 0210 Withholding 0216 Garnishment adjustment 0221 Adjustment 0267 Off cycle 2005 OT 2010 Catts direct to cluster 1000 Infotypes 1000 – 1999 are PD Relationship
infotypes
Self-learn question: Infotypes are accessed directly from Object Maintenance in: a. Simple Maintenance
--- Answer: c |
|
Also See
SAP Human Resouce Books
SAP Human Resource Tips
Main Index
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
|