on ‎2012 Jan 03 7:55 AM
Hi out there and happy new year to forum,
i want to update to implement a recruitment measure (Transaction PB40). I did it already with batch input, but i guess it's much more comfortable to do with funtion module, bapi or calsses.
After choosing the measure, the infogroup will be processed. So i guess, i just have to use the corresponding function modules to update the infotypes in a given sequence. is this suggestion right?
What are these function modules? How to update f.e. IT4000? Does anyone has a coding snippet?
Is it HR_INFOTYPE_OPERATION?
In our Infogroup there are also customer specific infotypes f.e. 9***. Can I use the sap standard function modules for "own implemented" infotypes?
I also appreciate an abap oo pattern or any similar....
Best regards,
T
Request clarification before answering.
yes you can update it via HR_INFOTYPE_OPERATION I think but why would you use the old recruiting database? This is hardly used anymore.
you can also use the FM for your 9000 infotypes (if they are PA infotypes, for OM you use RH_INSERT_INFTY
There is no OO (yet?) for HR PA.
But I don't think that it's possible to hire an application completly with function modules (there is no PERNR in the beginning so I would keep the BIM).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But I don't think that it's possible to hire an application completly with function modules (there is no PERNR in the beginning so I would keep the BIM).
The applicants already exists in system, i just want to implement a measure with exact one click!
Otherwise there is a BAPI for applicant_create.
I'm not very expierienced focussing the implementation in pa-recruiting. I'm really looking for a good documentation or anything like that f.e. sap press.
... but why would you use the old recruiting database? This is hardly used anymore.
.
What are the alternatives to it. (I'm not looking forward to upgrade releases or using wd4a or webgui). we are on ecc 6.0 There is already a lot of z-coding in recruitment. We are also using an self implemented e-recruiting approach
Edited by: Timo Ehl on Jan 3, 2012 2:30 PM
depending on the size of your company I would advise e-recruiting if it is big enough.
Anyway, maybe you can replace a lot of that Z coding in the old recruiting with standard features of e-recruiting.
but if you already have the applications, than you can try to use the HR_INFOTYPE_OPERATION fm.
You need to lock the employee first and unlock it afterwards (BAPI_APPLICANT_ENQUEUE and dequeue)
| User | Count |
|---|---|
| 7 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.