SAP HR Recrutiment. The data held within the Recruitment module is held in a separate database, as is the data contained within PA and OM. The master data for Recruitment is held in tables (PBxxxx) where xxxx is the infotype number. You can can get the infotype number by using the menu path: System. Status. You will see the program number which contains the infotype number in the notation. The Recruitment module within SAP is probably its weakest HR module. Our advice is to only introduce bespoke developments when it is either essential for your business or going to involve very little risk to other parts of SAP. Development items such as bespoke infotypes are fine. Just be wary of modifying SAP standard objects. You may well find that this affects another part of SAP - at some point in the future. Probably one of the strongest pieces of advice SDS can offer, is to recommend that you get your business processes clearly defined for Recruitment. This should take place as a matter of course during your implementation. PDF File: Sap E Recruiting Configuration Guide - SERCG-18-TAOM6-PDF 2/4 Sap E Recruiting Configuration Guide INTRODUCTION This particular Sap E Recruiting. Jeremy Masters, Christos Kotsakis, and Venki Krishnamoorthy E-Recruiting with SAP PDF File: Sap E Recruiting Configuration Guide - SERCG-18-WWRG6-PDF 2/4 Sap E Recruiting Configuration Guide INTRODUCTION This particular Sap E Recruiting. Sap E Recruiting Configuration Guide. 14-09-2016 2/2 Sap E Recruiting Configuration Guide. Other Files Available to Download Download as DOC, PDF, TXT or read online from Scribd. Flag for inappropriate content. More information Show less. How to create DSN in SQLServer. These processes which will include both SAP and non- SAP activities should be available to all on an Intranet. It is great to have them on a file server somewhere, but does everyone know where they are stored and does everyone have access to this drive? The fast entry screen within Recruitment is very inflexible. You can't use screen modifications on it, as you can with other Recruitment and PA screens. One thing you can do is make use of Transaction and Screen Variants. The transaction code to activate this is SHD0. It is a very useful piece of functionality within SAP. With it you can hide fields, provide defaults, make fields mandatory etc. There is some very useful information on it, just click on the . You have to have the . SAP has some serious limitations in this regard. The first problem is that everything is geared around the advert. Most of the reports have advert as a selection criteria, but most do not have vacancy or position included as a selection criteria. You can insert vacancy or position as a selection field in the relevant reports. This will involve some additional ABAP development work. SAP does not provide a typical object type for advert, as it does for org unit, job, position etc. PDF File: Sap E Recruiting Configuration Guide - SERCG-18-STRG6-PDF 2/4 Sap E Recruiting Configuration Guide INTRODUCTION This particular Sap E Recruiting.This becomes a problem if you need to bespoke anything within the Recruitment module in SAP. The module does tend to just hang together in a manner which is different to the rest of HR. If you publish your advert in more than one advertising recruitment instrument, then you have to create a separate advert for each one. This is because the time constraint on advert will only allow one recruitment medium per advert. The fact that advert is not an object in SAP means that to change the time constraint, you would effectively have to modify the relevant programs - which is going down the high- risk road. You can also not use advert altogether. Make use of the Unsolicited Application Groups on PB1. The downside to this is that you will have to write your own cost per applicant reports. You can use the transaction code OOPS to default the personnel area and sub- area for recruitment. This would also affect PA as well. Remember that when you go into the main configuration screen for Actions in Recruitment called . You need to scroll along to the right to see the other columns. One of the most important columns holds the value for the Info Group. This is often missed by users and consultants when configuring the Recruitment module. When entering the initial data for an applicant, the system does a check on first name and surname only. Once you hit the return button it does the check even if you haven't clicked on the . It looks for unique matches. If for example the previous applicant's name is Sarah Jones: Sarah Jones - Will find the match. Sara Jones - Will find the match. S J - Will find the match. Sar Jons - Won't find the match. The check is only done once you have changed the input fields for both first name and last name and then clicked the return button. These pieces of configuration are used essentially to group the different types of applicants in the system. They can be used very effectively in decisions for features and for report selection and output. Many customers are not able to come up with meaningful entries for both fields. It is worth spending a fair amount of time in deciding the values for these fields. They are integral to the Recruitment module and its successful implementation. Remember that there are a number of SAP standard dynamic actions which are there to assist you. Remember to add to them if you add in, for example, additional action types for Recruitment. These are very useful in the Recruitment solution for making changes to the screen fields where you either can't use . Remember that the feature for each infotype will generally allow you to select on either Applicants(B) or Employees(A). The transaction code OOPS allows you to set various fields. Try it out, it is quite useful. Remember that setting Personnel Area and Sub- area will set it for your user settings on that client. Remember that these can also be set in your user parameters. See the document we have in the Knowledge Base on User Parameters. For information, the common fields and parameter settings are: Personnel Area = PBRPersonnel Sub- area = PBSApplicant Group = APGApplicant Range = APRCountry = LNDIf you would like to transfer additional infotypes for internal applicants (PA to Rec) then you can do so by enhancing the user exit ZPAP4. CUS. You also need to modify the feature IGMOA. See OSS note 3. 14. Mail – Changes to Infotypes. The feature M0. 00. Refer to the documentation under Personnel Administration which provides more details on how to configure this. Mail sent after update to Applicant Activity. The feature MAILS can be used to send out an email to various recipients based on changes to different Applicant Activities in Recruitment. The following table shows a list of infotypes which are available as standard in the Recruitment module. This table contains infotypes which can be used in Recruitment. Infotype. Infotype name. Organizational Assignment. Personal Data. 00. Addresses. 00. 07. Planned Working Time. Basic Pay. 00. 09. Bank Details. 00. Recur. Payments/Deds. Additional Payments. Contract Elements. Education. 00. 23. Other/Previous Employers. Skills. 00. 28. Internal Medical Service. Date Specifications. Fiscal Data A0. 07. Additional Personal Data. Communication. 01. Working Time. 01. Personal Data B0. Contract Elements. Personal IDs. 01. Construction Pay: Previous ER0. GB View for Contractual Elements. Suppl. The following items should be considered: If your company uses a particular font set, does it exist within SAP Script - if not it will have to be added. Would you need to use the . You may wish to include IF, THEN, ELSE statements etc, in your letter. SAP Script provides many whilst standard Word provides a bit less. Are all the mail merge fields available in Word? If you would like to hold more expansive details about interview venues you can do so in Word or SAP Script using a few programming commands. SAP allows you to store 6 characters for both the room and building which is great if you are all familiar with them and where they are etc. If you need to store an address for them, then that becomes a lot more difficult. You can use IF statements in both Word and SAP Script to retrieve much more expansive and descriptive texts. The following fields are available to be inserted into letters of correspondence. This table contains fields which can be used in letters of correspondence. Field. Field Description. ADRS- ANREDTitle. ADRS- NAME1. Name 1 of an address. ADRS- NAME2. Name 2 of an address. ADRS- NAME3. Name 3 of an address. ADRS- NAME4. Name 4 of an address. ADRS- STRASHouse number and street. ADRS- PFACHPO box. ADRS- PSTL2. PO Box postal code. ADRS- PFORTPO Box city. ADRS- LAND1. Country key. ADRS- PSTLZPostal code. ADRS- ORT0. 1City. ADRS- ORT0. 2City. ADRS- REGIORegion (State, Province, County)ADRS- SPRASLanguage Key. ADRS- INLNDCountry key. ADRS- ANZZLNumber of lines in the address. ADRS- PRIORAddress lines priority. ADRS- WARENDelivery address IDADRS- LINE0. Address line. ADRS- LINE1. Address line. ADRS- LINE2. Address line. ADRS- LINE3. Address line. ADRS- LINE4. Address line. ADRS- LINE5. Address line. ADRS- LINE6. Address line. ADRS- LINE7. Address line. ADRS- LINE8. Address line. ADRS- LINE9. Address line. ADRS- LINEKAddress line. ADRS- LINEDAddress line. ADRS- LINED0. Address line. CONTR- CTARTText for contract type (Contract Elements infotype)CONTR- PERSGName of employee group. CONTR- PERSKName of employee subgroup. CONTR- RETEXTText for Work Schedule Rule (Planned Working Time Infotype)CONTR- SZTXTText for time recording status (IT Planned Working Time)CONTR- WWTXTName of Working Week (Planned Working Time Infotype)CONTR- PREASText on reason for change (Basic Pay infotype)CONTR- TARTXName of pay scale type (Basic Pay infotype)CONTR- TGBTXName of pay scale area (Basic Pay infotype)CONTR- CTRBEContract start date (Infotype Contract Elements)CONTR- CTRENContract temporary until (Infotpye Contract Elements)CONTR- WRKPLWork location (Contract Elements infotype)CONTR- LFZFRNumber of continued pay periods (IT Contract Elements)CONTR- LFZZHContinued pay period unit (IT Contract Elements)CONTR- KRZFRNo. Dear)PTXT1- TEL0. Pers. officer's tel. Mr/Mrs/Ms)PTXT1- NACHNLast name. PTXT1- VORNAFirst name. PTXT1- ENAMEFormatted name (e. Dr Jones)PTXT1- BEGDADate of receipt of application. PTXT1- PERNRApplicant number. PTXT1- PLSTXName of position. PTXT1- DATUMDate and time, current (application server) date. PTXT1- WWBEGDADate of receipt of application. PTXT1- TODAYSystem: Current date. PTXT1- ASHTXShort text for applicant activity type. PTXT1- ACTTXLong text for applicant activity type. RFACT- INDICIndicator: Completed/planned. RFACT- ACTIDIdentification number for applicant activity. RFACT- APACTApplicant activity type. RFACT- DATUMLast changed on. RFACT- UZEITTime. RFACT- UNAMEUser name.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |