on 2010 Jan 28 7:48 AM
Dear All
i have a requirment.
Can we do Mass Hiring action.
For Eg: Generally we use PA40 to hire an employee, but this is restricted to only single employee at a time.
For suppose i want to hire some 40 employees at a single go for around 15 infotypes for each employee and there should not be an duplication of data.
one thing, Number range is internal
Please let me know how to do it.
Regards
Vishveshwar rao
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
*Question 1.OM PA Integration :
Case(1): I have implemented PA now i want to implement OM:
Do I create OM objects ( 0,S,J,K) first and after that what should I do?
How do I assign Position Code to the Employees -- Doubt Do i use rhintee programs here
Case (2): I want to implement only PA and not OM...
Then what is the position code i shoule use
**Question 2
What should be implemented First OM or PA ?
Hello,
Use Ecatt and hire one employee and then you can hire as many as employee by passing the variants.
PS : ECATT : Extended Computer Aided Testing Tool.
REgards, Manasa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vishwanath,
Ecatt is an automation tool of SAP. The way there is Test Partner and QTP , Ecatt is tool that is developed by SAP. This is available to the customer who buy sap product. In this tool we can record any transaction transcation Eg: PA40. And using this tool we have hire n- number of people. To know more about Ecatt, goto help.sap.com-> Ecatt. You can get all the information about the tool and the recording.
I hope this will help you.
Best Regards,
Manasa
Use transaction SHDB to create your new recording session of PA40 for 1 employee. Then generate a custom BDC program from the recorded session to read the input file for all 40 employees.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can create a report using FM HR_MAINTAIN_MASTERDATA and upload the data via EXCEL for example. This FM will replicate PA40, so you will have the assurance that all validations are done exactly like they would be done using PA40 and also it will go through all infotypes for the measure you use in the parameters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear All
Below are the list of infotypes which we cannot maintain them while uploading the date and will have an impact on the Payroll.
1) Basic Pay (Infotype 0008) -- we cannot maintain this infotype as it varies with salary structure.
2) Bank Detail (IT0009) -- we cannot maintain the bank details thru Mass Hiring,as first month salary is paid thru
cheque,
3) Other Statutory Deductions (IT0588)-- These infotype is depended on basic pay Infotype, so we cannot maintain
this.
In this statutory deduction (IT0588) -- we have three sub types -- 1) ESI 2) Labour welfare Fund 3) Professional tax.
4) HR letters (IT9002) -- we cannot maintain this infotype thru mass hiring, it should be updated manually.
5) Nominations (IT0591) -- This infotype has many subtypes and all subtypes will not maintained for an employee, so we cannot maintain this infotype thru mass upload.
6) CTC (IT9003) -- The salary structure varies with respect to the position, we have 5 CTC structures with different pay elements.
7) Objects on loan (IT0040) -- This has many sub types and all of them are not maintained for an employee.it avries with employee.
😎 Absence Quota IT(2001) -- We have written a dynamic action to automatically generate the absence quota for an employee. The quota would not be generated while mass upload.
9) HRA (IT0581) -- This infotype is based on Basic Pay Infotype, since basic pay cannot be maintained thru mass upload,so we cannot maintain this infotype also.
10) Conveyance (IT0583) -- This infotype is based on Basic Pay Infotype, since basic pay cannot be maintained thru mass upload,so we cannot maintain this infotype also.
11) Previous Employer Tax Details -- These Details varies with respect to the employee.
12) Monitoring of Task (IT0019) -- We have written a dynamic action to automatically generate the Retirement Date. Date will not be generated as code will not work thru mass hiring.
13) Date Specification (IT0041) -- We have written a dynamic action to automatically generate the Probation end Date and to intimate the Probation end date to his reporting boss abut his probation.
14) Spouse Details -- We have wriiten a dynamic action code to call the Spouse Details Screen when if an employee is married.Screen will not be called while mass hiring.
15) Child Details -- We have wriiten a dynamic action code to call the Child Details Screen when if an employee is has childrens.Screen will not be called while mass hiring
16) Previous Employer Details (IT0023) -- This infotype also varies with employee, if an employee is fresher.we need not maintain this infotype.
17) need to add one more critical issue to the Mass Hiring.
Some more fields like Job Text, Cost center value, Orgainizational Key etc will be automatically defaulted based on the Position because we have integrated OM sub module and PA sub module.
This Functionality will not work while Uploading Data and it will have impact on Payroll and when posting the Payroll Results to FI.
Regards
Vish
you have to go with LSMW or BDC are you looking at some other way
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
104 | |
10 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.