Applicant ranking - E recruiting

Dear experts,
I am working on EREC 6.0 implementation.
I would like to know the following
Questionnaires are attached to process templates in order to facilitate ranking.
how does it exactly happen, how to attach test scores into it.
Regards,
Bharat

Bharat,
check this link
http://help.sap.com/saphelp_erp60_sp/helpdata/en/72/c9b54015c4752ae10000000a155106/frameset.htm
in the detailed level navigation check ranking of candidates by responses to a questionnaire
Thanks
Bala Duvvuri

Similar Messages

  • Applicant correspondence in Recruitment issue

    Dear Friends,
    Greetings !!
    In Applicant Correspondence,
    I have set the feature WPROC to RTF (rich text format) and trying to create standard texts for applicant correspondence, I am getting the error as -
    "Internal error in SAP OLE document container control.
    Message no.SOFFICEINTEGRATION019"
    What is the main problem? what should I need to do to overcome this error?
    Can anyone please suggest me the procedure, how to create the standard texts for applicant correspondence in Recruitment module in ECC 6.0 ........
    I will be grateful to you.
    Thanks,
    Sai Narayana

    gr8...on applying the notes...im able to create the word documents
    ....now how am i supposed to map the fields in the word document
    <<zstructure-field1>> is it like this??  its very urgent help me..
    thanks
    g3

  • Talent Relationship Management and applicant ranking.

    Hi Gurus,
    I am new to this technology. Please provide me some tutorial on "TRM and applicant ranking (how is it done?)".
    Thanks in advance,
    Posun

    Hello
    Please note the description from the Overview for this SCN Space:
    Official SAP Help Portal Community. Find comments on SAP product documentation (such as SAP Application Help, also known as SAP Library), and read best practices shared by the community.
    Based do the above, I believe you posted your query into the incorrect SCN Space. Please use the Forum Finder for the New SCN document to find your product and post into that SCN Space.
    With best regards,
    - Ludek
    SCN Moderator

  • Link Employees to Applicant in HCM Recruitment

    Hello All,
    We wanted to find out the applicant for a particular Employee. Which is the tables where i can check the link between PERNR and the APPLICANT?
    We us transaction PBA7 to hire the applicant and transfer data from PB* tables to PA* tables.
    Regards,
    Rishav Surana

    Hi Rishav,
    In case of the internal applicant check for the table PB4005 where employee number would be mapped against the applicant number.
    Also for activation between P.A and Recruitment maintain the feature accordingly -  PRELI return value must be *.
    Regards,
    Mithun K

  • How to add letters  to applicant activities  in recruitment module

    Hi Experts,
    We have created letters in recruitment module through tcode So10
    Here im in confusion where shall we add these lettes in the module.
    We have to add for Acknoeledgement,invitation for interview,offer letter and  rejection letter.
    kindly advice.
    Vsai.

    Hi Vicky,
    You assign letters to activities by implementing feature PACTV.
    Please assign the standard text name to IDTXT field.
    Regards,
    Dilek

  • Recruitment - Applicant attachments to be transferred to PA

    Dear Experts,
    Im able to transfer Applicant data from recruitment to PA and EMployee ID is generated along with Infotypes updation.
    Now my query is Is there any option to transfer Applicants attachments also along with Applicants data transfer to PA in recruirment module??
    If so where to do settings.
    Thanks
    Ravi

    Hi,
    In SAP each module is a stand alone module.
    PBA7  and PBA8 are used for transferring of data from RC to PA.
    If you want to transfer any data from one module to other module is possible by using data carrier instruments with technical people help.
    Thanks,
    Venu

  • E-Recruiting: Batch Creation of Applicants

    Hi Experts,
    I have the following questions and would really appreciate if anyone could help:
    1) My job portal is an external system and I need to import in the applicants into E-Recruiting.  I know E-Recruiting does not have a BDC concept.  So how should I do it?  Is there a standard function module/program which I can call to create the application and necessary relationship tables like HRP5102?
    2) In infotype HRP5102, for the Status field, there are two possible values for 'released' mode (1 and 2).  What is the difference?
    3) In infotype HRP5102, for the ISTAT field, what does the different status value means?
    Will appreciate if there are any documentation on it as online help did not elaborate much.
    Many thanks.
    william
    Edited by: William Toh on Mar 16, 2008 9:34 AM

    Hello William,
    for question 1:
    E-recruiting is does not support an complete interface for data maintenance like the BAPIs of the Business Partner. It has carious service classes to support customer developments but replacing the whole candidate frontend by a non sap solution will generate very huge expenses.
    I am not sure why you do not want to use the frontend delivered with e-recruiting. It can be integrated into company web appearance which would be much easier and probably cheaper,too.
    Perhaps you can highlight some reasons / restrictions which lead to the conclusion that you can't use the sap delivery here.
    for question 2:
    The reason for the 3 domain keys for only 2 values is a historical one. When the development of e-recruiting started the status management for candidates had 3 different value based on the assumption that candidates will be in the pool for a lon period of time:
    - "not searching" - a candidate which has been in contact with the company but for any reason does not currently look for a new position, e.g. he just changed jobs. of course he stays in the system for identifying former contacts and perhaps in a year or 2 he is interested in a job again.
    - "passive searching" - a candidate which is more or less satisfied with his current employment but won't complain about an new offer for a new challaging task or enough cash
    - "active searching" - a candidate who is really unsatified with his current job and will take any acceptable offer
    Anywhen SAP came to the conclusion that these 3 candidate states are very difficult to handle. In the end most candidates will take a new job if you put enough money on the table. So SAP changed the candidate status to "I only want to be checked on the positions I choose" (= profile locked) and "If you think you have a job I might fit just feel free" (= profile released). It seems that SAP was not really sure where they used 1 or 2 so they just gave both keys the same description. Within coding profile status is usually checked against key 0 with EQ or NE.
    for question 3:
    The standard HR components use a status concept for some of the objects e.g. an organizational unit can have different states (planed, requested, activ, ...) and the relation to other objects derive this concept. As all HR components use the same database structures e-recruiting infotypes have this field in their key structures, too. But e-recruiting does not use this concept so this field always should be 1 in all datasets.
    Best Regards
    Roman Weise

  • Query on Applicant Actions

    We are implementing both Recruitment & PA modules for the customer. In the Recruitment module, the customer wishes to enter the applicant data into the system only after the initial shortlisting. What are the typical infotypes that are included in the infogroup for Applicant action? As far as I see, Persoal Data, Addresses, Qualification, Previous Employment are the important ones. Are there any more?
    Also, when the applicant is converted to an employee (thru Hiring action), these infotypes should not appear in PA40. How is this integration acheived? Through which integration switch?
    -Shambvi

    May be, I did not explain my query properly. The customer wishes to enter some basic information about the applicant in the Recruitment module. The information typically available at the stage of recruitment are Personal Data (name, address, DOB), Previous Employment Details (like earlier companies, where he worked, along with the duration & designation etc.). Also, when the customer wishes to "Offer" the job to the applicant (if he is selected), they can enter the organizational Assignment data like, position, personnel area/subarea & employee group/subgroup. My first query is, how is  this data entered into the system? Which transaction code? Also, how do we set up the Action (infogroup etc.)? Is it through Applicant Actions?
    Now, if the "Offered" applicant joins the company, then the available applicant info should be transferred to the PA module, so that he becomes "Hired" now. During this process, the applicant, who becomes an employee now, should be assigned a personnel number (internally or externally, depending on the configuration). Also, the user provides the Joining Date. How is this transfer done?
    Once "Applicant to Employee"  transfer is done, should I use PA30 to update the remaining infotypes configured in the Hiring Action?
    Hope I am more clear with my query now.
    -Shambvi

  • Custom configrations in Recruitment

    Experts,
         Could you please let me know the major configrations in Recruitment by a Functional consultant.
    Regards
    SD.SK
    Edited by: SD.SK on Jan 22, 2009 8:57 AM

    Once you run PBA7, run report RPAPRT04. You can use this report to set applicant activities to completed, after you have transferred data for the applicants to Personnel Administration. The advantage of this report is that you receive a list of applicants for whom data has already been transferred to Personnel Administration, without having to enter selection criteria.
    From now on, the applicants are handled as employees in Personnel Administration. The applicant data for these new employees does not require any further processing in the Recruitment component. You run this report to close the administration of the applicant data in Recruitment.
    Apart from this i dont think there is any other major configurations..

  • Applicant Create (BAPI_APPLICANT_CREATE)

    Hi ,
    I know its lenghty  but am sure an ABAP programmer can understand my problem.
    My requirement is to create an applicant in SAP system by reading the file from the applicantion server .I have written  an interface  program  to create the Applicants in SAP recruitment model. Basically  the data comes from the external  system( website) is  a CSV format.
    WELL!!! I  cannot use BDC to create applicants because they could be created in different countries (7)   . As I say  the screen would be different for each country . I dont know anything about dynamic recording of screens so this is out of the way.
    I have tried the bapi function module BAPI_APPLICANT CREATE but this is giving an error " No batch input data for screen SAPLRHP6 6000 " (Qualifications)
    When I tried to debug the  FM in all screen mode  org assignment , education, actions and personnel data infotypes are created correctly. But  even thought  have passed the qualifications  import paranmeter nothing is being passed into it. QUalifications is the mandatory screen for the  applicant master data .
    Below  the data I am passing into the qualifications table in BAPI.Okay I  will be  creating the proficiencies only in languages.
    QUALIF   P PROF
    50000000 1 0001
    Please can you help me the best way forward  . IThis is vey urgent , I have tried all m y ways and hands up now
    Thanks and Regards,
    Aarti

    Hi Aarati Ramaraju ,
                                  I think you are not passing some important input parameter to the BAPI call.
    Check the Business object APPLICANT for  method "Create" There is a sample code inside this method:
    BEGIN_METHOD CREATEFROMDATA CHANGING CONTAINER.
    DATA:
          APPLICANTGROUP LIKE BAPIAPLORG-AP_GROUP,
          APPLICANTSUBGROUP LIKE BAPIAPLORG-AP_SUBGRP,
          PERSONELAREA LIKE BAPIAPLORG-PERS_AREA,
          PERSONALSUBAREA LIKE BAPIAPLORG-P_SUBAREA,
          PERSONNEL LIKE BAPIAPLORG-PERSONNEL,
          FIRSTOFADRESSKEY LIKE BAPIAPLPER-FOA_KEY,
          FIRSTNAME LIKE BAPIAPLPER-F_NAME,
          LASTNAME LIKE BAPIAPLPER-L_NAME,
          MAIDENNAME LIKE BAPIAPLPER-BIRTHNAME,
          SECONDLASTNAME LIKE BAPIAPLPER-LAST_NAME2,
          KNOWNAS LIKE BAPIAPLPER-KNOWN_AS,
          SSN LIKE BAPIAPLPER-SSN,
          DATEOFBIRTH LIKE BAPIAPLPER-B_DATE,
          TITLE LIKE BAPIAPLPER-TITLE,
          TITLE2 LIKE BAPIAPLPER-2ND_TITLE,
          ARISTOCRATICTITLE LIKE BAPIAPLPER-ARI_TITLE,
          AFFIX LIKE BAPIAPLPER-AFFIX,
          PREFIX2 LIKE BAPIAPLPER-PREFIX_2,
          GENDER LIKE BAPIAPLPER-GENDER,
          PLACEOFBIRTH LIKE BAPIAPLPER-BIRTHPLACE,
          MARITALSTATUS LIKE BAPIAPLPER-MAR_STAT,
          INITIALS LIKE BAPIAPLPER-INITIALS,
          NATION LIKE BAPIAPLPER-NATION,
          LETTERLANGUAGE LIKE BAPIAPLPER-LANGU,
          CO LIKE BAPIAPLADR-C_O,
          STREET LIKE BAPIAPLADR-STREET,
          ADDRESS2NDLINE LIKE BAPIAPLADR-2ND_ADD_LN,
          CITY LIKE BAPIAPLADR-CITY,
          REGION LIKE BAPIAPLADR-REGION,
          DISTRICT LIKE BAPIAPLADR-DISTRICT,
          ZIPCODE LIKE BAPIAPLADR-PCD_CITY,
          COUNTRY LIKE BAPIAPLADR-CNTRY,
          TELEPHONNO LIKE BAPIAPLADR-TEL_NO,
          ADVERTISEMENT LIKE BAPIAPPLIC-ADVERT,
          UNSOLICITEDAPPLGROUP LIKE BAPIAPPLIC-UNSAPPGP,
          MEDIUM LIKE BAPIAPPLIC-MEDIUM,
          RETURN LIKE BAPIRETURN,
          EDUCATION LIKE BAPIEDUC OCCURS 0,
          PREVIOUSEMPLOYMENT LIKE BAPIEMPLOY OCCURS 0,
          QUALIFICATION LIKE BAPIQUALI OCCURS 0,
          VACANCYASSIGNMENT LIKE BAPIVACASS OCCURS 0,
          EMPLOYEENUMBER LIKE BAPIP0001-PERNR,                   "WBIK005689
          COMMUNICATIONTYPE LIKE BAPIP0105B-USERTYPE,            "WBIK005689
          EMAIL LIKE BAPIHR0105-E_MAIL.                          "WBIK005689
      SWC_GET_ELEMENT CONTAINER 'ApplicantGroup' APPLICANTGROUP.
      SWC_GET_ELEMENT CONTAINER 'ApplicantSubGroup' APPLICANTSUBGROUP.
      SWC_GET_ELEMENT CONTAINER 'PersonelArea' PERSONELAREA.
      SWC_GET_ELEMENT CONTAINER 'PersonalSubArea' PERSONALSUBAREA.
      SWC_GET_ELEMENT CONTAINER 'Personnel' PERSONNEL.
      SWC_GET_ELEMENT CONTAINER 'FirstOfAdressKey' FIRSTOFADRESSKEY.
      SWC_GET_ELEMENT CONTAINER 'FirstName' FIRSTNAME.
      SWC_GET_ELEMENT CONTAINER 'LastName' LASTNAME.
      SWC_GET_ELEMENT CONTAINER 'MaidenName' MAIDENNAME.
      SWC_GET_ELEMENT CONTAINER 'SecondLastName' SECONDLASTNAME.
      SWC_GET_ELEMENT CONTAINER 'KnownAs' KNOWNAS.
      SWC_GET_ELEMENT CONTAINER 'SSN' SSN.
      SWC_GET_ELEMENT CONTAINER 'DateOfBirth' DATEOFBIRTH.
      SWC_GET_ELEMENT CONTAINER 'Title' TITLE.
      SWC_GET_ELEMENT CONTAINER 'Title2' TITLE2.
      SWC_GET_ELEMENT CONTAINER 'AristocraticTitle' ARISTOCRATICTITLE.
      SWC_GET_ELEMENT CONTAINER 'Affix' AFFIX.
      SWC_GET_ELEMENT CONTAINER 'Prefix2' PREFIX2.
      SWC_GET_ELEMENT CONTAINER 'Gender' GENDER.
      SWC_GET_ELEMENT CONTAINER 'PlaceOfBirth' PLACEOFBIRTH.
      SWC_GET_ELEMENT CONTAINER 'MaritalStatus' MARITALSTATUS.
      SWC_GET_ELEMENT CONTAINER 'Initials' INITIALS.
      SWC_GET_ELEMENT CONTAINER 'Nation' NATION.
      SWC_GET_ELEMENT CONTAINER 'LetterLanguage' LETTERLANGUAGE.
      SWC_GET_ELEMENT CONTAINER 'CO' CO.
      SWC_GET_ELEMENT CONTAINER 'Street' STREET.
      SWC_GET_ELEMENT CONTAINER 'Address2ndLine' ADDRESS2NDLINE.
      SWC_GET_ELEMENT CONTAINER 'City' CITY.
      SWC_GET_ELEMENT CONTAINER 'Region' REGION.
      SWC_GET_ELEMENT CONTAINER 'District' DISTRICT.
      SWC_GET_ELEMENT CONTAINER 'ZipCode' ZIPCODE.
      SWC_GET_ELEMENT CONTAINER 'Country' COUNTRY.
      SWC_GET_ELEMENT CONTAINER 'TelephonNo' TELEPHONNO.
      SWC_GET_ELEMENT CONTAINER 'Advertisement' ADVERTISEMENT.
      SWC_GET_ELEMENT CONTAINER 'UnsolicitedApplGroup' UNSOLICITEDAPPLGROUP.
      SWC_GET_ELEMENT CONTAINER 'Medium' MEDIUM.
      SWC_GET_ELEMENT CONTAINER 'EmployeeNumber' EMPLOYEENUMBER. "WBIK005689
      SWC_GET_ELEMENT CONTAINER 'CommunicationType' COMMUNICATIONTYPE. "WBIK
      SWC_GET_ELEMENT CONTAINER 'EMail' EMAIL.                   "WBIK005689
      SWC_GET_TABLE CONTAINER 'Education' EDUCATION.
      SWC_GET_TABLE CONTAINER 'PreviousEmployment' PREVIOUSEMPLOYMENT.
      SWC_GET_TABLE CONTAINER 'Qualification' QUALIFICATION.
      SWC_GET_TABLE CONTAINER 'VacancyAssignment' VACANCYASSIGNMENT.
      CALL FUNCTION 'BAPI_APPLICANT_CREATE'
        EXPORTING
          2ND_ADD_LN = ADDRESS2NDLINE
          STREET = STREET
          C_O = CO
          LANGU = LETTERLANGUAGE
          NATION = NATION
          INITIALS = INITIALS
          MAR_STAT = MARITALSTATUS
          BIRTHPLACE = PLACEOFBIRTH
          CITY = CITY
          MEDIUM = MEDIUM
          UNSAPPGP = UNSOLICITEDAPPLGROUP
          ADVERT = ADVERTISEMENT
          TEL_NO = TELEPHONNO
          CNTRY = COUNTRY
          PCD_CITY = ZIPCODE
          DISTRICT = DISTRICT
          REGION = REGION
          GENDER = GENDER
          L_NAME = LASTNAME
          F_NAME = FIRSTNAME
          FOA_KEY = FIRSTOFADRESSKEY
          PERSONNEL = PERSONNEL
          P_SUBAREA = PERSONALSUBAREA
          PERS_AREA = PERSONELAREA
          AP_SUBGRP = APPLICANTSUBGROUP
          AP_GROUP = APPLICANTGROUP
          BIRTHNAME = MAIDENNAME
          SECONDNAME = SECONDLASTNAME
          PREFIX_2 = PREFIX2
          AFFIX = AFFIX
          ARI_TITLE = ARISTOCRATICTITLE
          2ND_TITLE = TITLE2
          KNOWN_AS = KNOWNAS
          SSN = SSN
          B_DATE = DATEOFBIRTH
          TITLE = TITLE
          EMPLOYEENUMBER = EMPLOYEENUMBER                        "WBIK005689
          COMMUNICATION_TYPE = COMMUNICATIONTYPE                 "WBIK005689
          E_MAIL = EMAIL                                         "WBIK005689
        IMPORTING
          RETURN = RETURN
          APPLICANTNUMBER = OBJECT-KEY-APPLICANTNUMBER
        TABLES
          VACANCY_ASSIGNMENT = VACANCYASSIGNMENT
          QUALIFICATION = QUALIFICATION
          PREVIOUS_EMPLOYMENT = PREVIOUSEMPLOYMENT
          EDUCATION = EDUCATION
        EXCEPTIONS
          OTHERS = 01.
      CASE SY-SUBRC.
        WHEN 0.            " OK
        WHEN OTHERS.       " to be implemented
      ENDCASE.
      SWC_SET_ELEMENT CONTAINER 'Return' RETURN.
      SWC_SET_TABLE CONTAINER 'Education' EDUCATION.
      SWC_SET_TABLE CONTAINER 'PreviousEmployment' PREVIOUSEMPLOYMENT.
      SWC_SET_TABLE CONTAINER 'Qualification' QUALIFICATION.
      SWC_SET_TABLE CONTAINER 'VacancyAssignment' VACANCYASSIGNMENT.
    END_METHOD.
    Also check the include "MPW12F01" for another sample code that SAP uses to create the applicant:
    *&      Form  UPDATE_APPLICANT
    FORM update_applicant.
      DATA: initdate LIKE p0022-begda.
      DATA: initquali LIKE p0024-quali.
      DATA: additional_suppress TYPE c VALUE 'X'.               "XDVN618851
      DATA: BEGIN OF tab OCCURS 5,
              subty LIKE t591a-subty,
            END OF tab.
      DATA: ind LIKE syst-index.
      DATA: BEGIN OF infty_0001 OCCURS 1.
              INCLUDE STRUCTURE p0001.
      DATA: END OF infty_0001.
      DATA: BEGIN OF infty_4001 OCCURS 1.
              INCLUDE STRUCTURE p4001.
      DATA: END OF infty_4001.
      DATA: BEGIN OF old_adr,
                  stras    LIKE bapiapladr-street,
                  name2    LIKE bapiapladr-c_o,
                  locat    LIKE bapiapladr-2nd_add_ln,
                  ort01    LIKE bapiapladr-city,
                  ort02    LIKE bapiapladr-district,
            END   OF old_adr.
      DATA: BEGIN OF old_per,
                  nachn    LIKE bapiaplper-l_name,
                  vorna    LIKE bapiaplper-f_name,
                  name2    LIKE bapiaplper-birthname,
                  rufnm    LIKE bapiaplper-known_as,
                  gbort    LIKE bapiaplper-birthplace,
            END   OF old_per.
      REFRESH education.    "LCP46C Note 204481
      LOOP AT tab0022.
        CHECK tab0022-begda NE initdate.
        CLEAR education.
        MOVE  tab0022-begda TO education-from_date.
        MOVE  tab0022-endda TO education-to_date.
        MOVE  tab0022-insti TO education-institute.
        MOVE  tab0022-slabs TO education-certific.
        MOVE  tab0022-slart TO education-educ_est.
        MOVE  tab0022-sland TO education-cntry.
        MOVE  tab0022-sltp1 TO education-br_study_1.
        MOVE  tab0022-sltp2 TO education-br_study_2.
        MOVE  tab0022-emark TO education-mark.                  "4.6C
        APPEND education.
      ENDLOOP.
      IF sy-subrc NE 0.                                         "4.6C
        REFRESH education. CLEAR education.                     "4.6C
      ENDIF.                                                    "4.6C
      REFRESH employer.    "LCP46C Note 204481
      LOOP AT tab0023.
        CHECK tab0023-begda NE initdate.
        CLEAR employer.
        MOVE tab0023-begda TO  employer-from_date.
        MOVE tab0023-endda TO  employer-to_date.
        MOVE tab0023-arbgb TO  employer-employer.
        MOVE tab0023-land1 TO  employer-cntry.
        MOVE tab0023-ort01 TO  employer-city.
        MOVE tab0023-taete TO  employer-job.
        MOVE tab0023-ansvx TO  employer-employment_contract.    "4.6C
        APPEND employer.
      ENDLOOP.
      IF sy-subrc NE 0.                                         "4.6C
        REFRESH employer. CLEAR employer.                       "4.6C
      ENDIF.                                                    "4.6C
      REFRESH qualification.    "LCP46C Note 204481
      LOOP AT tab0024.
        CHECK tab0024-quali NE initquali.
        CLEAR qualification.
        MOVE tab0024-quali TO qualification-qualif.
      MOVE TAB0024-AUSPR TO QUALIFICATION-PROFIC.             "XCZK034654
        MOVE tab0024-auspr TO qualification-profic_4.           "XCZK034654
        APPEND qualification.
      ENDLOOP.
      IF sy-subrc NE 0.                                         "4.6C
        REFRESH qualification. CLEAR qualification.             "4.6C
      ENDIF.                                                    "4.6C
      REFRESH tab.
      CLEAR tab.
    Lesen der Infosubtypeigenschaften für den IT4002.
      SELECT * FROM t591a WHERE infty EQ '4002'.
        tab-subty = t591a-subty.
        APPEND tab.
        CLEAR tab.
      ENDSELECT.
      ind = 0.
      REFRESH vacancy_assignment.                "WBIK
      CLEAR vacancy_assignment.                  "WBIK
    LOOP AT S_VACANCIES.                      "WBIK059034
      LOOP AT s_vacancies WHERE indic = 'X'.                    "WBIK059034
        ADD 1 TO ind.
        READ TABLE tab INDEX ind.
        IF sy-subrc NE 0.
          EXIT.
        ENDIF.
        CLEAR vacancy_assignment.
        vacancy_assignment-priority = tab-subty.
        vacancy_assignment-va_status = '1'.
        vacancy_assignment-vacancy = s_vacancies-objid.
        APPEND vacancy_assignment.
      ENDLOOP.
    Default-Werte aus den Merkmalen INTDF und INTDY.
      infty_0001-werks = int_defaults-werks.
      infty_0001-btrtl = int_defaults-btrtl.
      infty_0001-persg = int_defaults-persg.
      infty_0001-persk = int_defaults-persk.
      infty_0001-sachp = int_defaults-sachp.
      infty_4001-spapl = int_defaults-spapl.
      infty_4001-media = int_defaults-media.
      p0002-sprsl = sy-langu.
      CLEAR: text_1000_2, text_1000_1.
      MOVE-CORRESPONDING p0002 TO old_per.
      MOVE-CORRESPONDING p0006 TO old_adr.
    Flag additional_suppress is set in case of internet application;
    for internet application an additional suppress dialog is necessary
    when automatically generating an activity.
    flag is imported in PBO-Module INIT_D1000 of program SAPMPAP3.
      EXPORT additional_suppress TO MEMORY ID 'ADD_SUPP'.      "XDVN618851
    Mit dieser Methode kann ein Bewerber angelegt werden. Es finden alle
    Konsistenzprüfungen statt, die auch bei einer Bewerberdatenerfassung
    innerhalb der R/3-Transaktionen durchgeführt werden. Es wird nur dann
    ein Bewerber angelegt, wenn alle Konsistenzprüfungen erfolgreich
    abgeschlossen werden konnten. Die vom System vergebene Bewerbernummer
    sowie ein Returncode werden zurückgegeben.
    Technisch wird die Tabelle PROPOSED-VALUES gefüllt, wobei diese Daten
    mit dem Dialogbaustein RP_TRANSFER_APPLICANT weggeschrieben werden.
    Der BAPI-Returnparameter wird gesetzt und die Texte der System-
    variablen werden im Nachrichtentext eingefügt.
      CALL FUNCTION 'BAPI_APPLICANT_CREATE'
        EXPORTING
          ap_group            = int_defaults-persg
          ap_subgrp           = int_defaults-persk
          pers_area           = int_defaults-werks
          p_subarea           = int_defaults-btrtl
          personnel           = int_defaults-sachp
          foa_key             = p0002-anred
          f_name              = old_per-vorna
          l_name              = old_per-nachn
          birthname           = old_per-name2
          known_as            = old_per-rufnm
          ssn                 = p0002-perid
          b_date              = p0002-gbdat
          title               = p0002-titel
          2nd_title           = p0002-titl2
          ari_title           = p0002-namzu
          affix               = p0002-vorsw
          prefix_2            = p0002-vors2
          gender              = p0002-gesch
          birthplace          = old_per-gbort
          mar_stat            = p0002-famst
          initials            = p0002-inits
          nation              = p0002-natio
          langu               = sy-langu
          c_o                 = old_adr-name2
          street              = old_adr-stras
          2nd_add_ln          = old_adr-locat
          city                = old_adr-ort01
          region              = p0006-state
          district            = old_adr-ort02
          pcd_city            = p0006-pstlz
          cntry               = p0006-land1
          tel_no              = p0006-telnr
          advert              = advert                    "XCZ
          unsappgp            = int_defaults-spapl
          medium              = int_defaults-media
          employeenumber      = pernr                           "WBIK031606
          communication_type  = '0010'                          "WBIK031606
          e_mail              = p0105-usrid_long                "WBIK031606
        IMPORTING
          applicantnumber     = rpapp-aplno
          return              = bapi_rcode
        TABLES
          education           = education
          previous_employment = employer
          qualification       = qualification
          vacancy_assignment  = vacancy_assignment
        EXCEPTIONS
          OTHERS              = 0.
      IF bapi_rcode IS INITIAL.                                 "WBIK059033
        PERFORM save_orig_data USING rpapp-aplno.               "WBIK059033
        already_applicant = yes.                                "XDVN427098
    new / J. Naeckel
    Let me know if you have any questions.
    Thanks,
    Greetson

  • Recruitment data transfer to PA

    Hi All,
    When I transfer applicant data from Recruitment module to PA (PBA7 or Hire Applicant action), not all the expected infotypes are copied.
    For instance, we use several subtypes of Address , but only 1 subtype  is transferred.
    Same case with Education. Not all Education subytpes are getting copied.Only 2 records got copied when I maintained 3 records.
    In Infogroup I maintained all subytpes when transferring master data. Please let me know how to solve this issue.
    Thanks in advance,
    Ravi

    During the action, is the Addrs and Edu infotypes come more than one time?
    Because, whatever infotypes that updates in  PA30 can be visible at the time of transfer, and you can make any changes if required. If you maintain different records in an infotype (i.e subtypes), it should show more than one time. Otherwise, I think it will update only the primary subtype (the subtype that shows).
    Let us wait for experts opinion.

  • E-Recruitment and Hiring Action

    Can someone tell me that once you have selected your applicant through e-Recruitment, how do you then hire the employee into ERP HR?
    What is the process?
    What data can be transfered?
    Thanks
    WB

    Hi,
    as said by the community before the standard technical ways to transfer data from e-recruiting to PA for hiring are RCF transfer into table T752F where they are used for PA48 or the XI technology. The HCM Forms might be an option but the Adobe licence (if not already there) might cost more than the complete e-recruiting rollout.
    That's the theory. As far as I encountered in different rollouts XI is usually not available for the HR in most cases. So most projects tend to use the RFC transfer. But in the end you have to admit that the system only supplies ~15 values from personal data and address which are not exactly matching the PA infotypes (e.g. in e-recruiting street and house number are one field, in PA there are two). All data is entered by the applicant so everything has to be checked and it's only a low percentage of a complete hiring action with >20 screens. So it is not very uncommon that in the end the real process stays on paper. The hr admins send out a form, the applicant fills it and sends it back. Then the hiring action is done and the paper version gets into the the files.
    So often the lived process does not match the technical options available.
    Rgds.
    Roman Weise

  • Conditional activity in Recruiter role

    Dear All,
    I am implementing e-recruitment. The client's requirement is to allow creating a specific activity only if certain condition is met.
    The condition is the response (YES /NO) of a question that candidate filled during the application.
    For Example the question is: Have you ever worked in ABC Company? 
    If candidate says YES or NO during the application wizard its stored in questionnaire table.
    Now on the candidate assignment list during the applicant tracking when recruiter selects this candidate and wants to create a certain activity say "XYZ", system should stop it if candidate response was NO and allow it in case of YES.
    your consideration would be highly appreciated as I really need a solution very urgently.
    Chohan

    Hello Chohan,
    currently there is no option to restrict the creation of an activity in the described way. In fact there is no way at all to have a logical restriction on activity maintenance. There is only an authorization object which allows to restrict the activity maintenance on activity type level.
    SAP is currently working on a concept for allowing dependencies between activities but I am not sure if it will be flexible enough to cover your specific requirement.
    To at least improve the process I can imagine to create the activity automatically in planned status via workflow if it is obligatory. So the recruiter only has to continue the work and not create new ones. You could also use the enhancement concept of the candidate selection list to add a column with the information. Both solutions will not prevent a recruiter from intentionally creating the activity for a candidate for whom he should not create it but the additional service or information can reduce errornous activities.
    Kind Regards
    Roman   

  • Email sending in Activity Management for E-recruiting

    Hi Everyone
    I am using E-rec on EP4. And I am trying to use the Email sending functionality in Applicant management in recruiting. It's the part where a recruiter acknowledges the receipt of an application/resume and the recruiter needs to send notification using the email function of the Invite to Apply activity where you use a letter template and you press the Send Email function. When I click that Send Email function. I get and error that says ' 1 document could not be created or processed'.
    Does anyone have that same error? What am I missing and what should I do to set that up.
    thanks
    Vince

    Hi
    For this same message, we have done all the mentioned config and created a new Z Custom Smart form but while creating the activity, we are getting this error - 1 Document cannot be created.
    SLG1 Log says -
    The incorrect HR object has the key 01NE00100504
    The error occurred in program CL_HRRCF_CANDIDACY============CM00B line 77
    Please let me know what I am missing.
    Thanks

  • Activites in Recruitment Module

    Hi,
    Plz let me know what are all the activities required to configure Recruitment module in R3
    Thanks in advance

    Hi,
    The recruitment Module activities are as follows:
    1.     VACANCY MANAGEMENT
    2.     APPLICANTS
    3.     RECRUITMENT MEDIUM  & INSTRUMENT
    4.     APPLICANT ADMINISTRATION
    5.     SELECTION OF APPLICANTS
    6.     ADMINISTRATION OF APPLICATION GROUPS
    7.     TRANSFER OF APPLICANT DATA TO P.A.
    8.     APPLICANT DATA  & REPORTING.
    The recruitment module in integration with PA, OM and PD are done for the following purposes.
    u2022     Personnel Administration u2013 for internal sourcing
    u2022     Organizational Management u2013 for creation and maintenance of vacancies
    u2022     Personnel Development u2013 for profile match up and creating skills and    proficiencies for each position.
    Regards
    Raviiiiiiiiii

Maybe you are looking for