Applicant creation

Hi,
I have created a rfc for creation of an applicant using BAPI_APPLICANT_CREATE function module. I am capturing the created applicant number into V_APPLNO.
IMPORTING
          APPLICANTNUMBER           = V_APPLNO
The thing is now i am passing this variable into a internal table for output
OT_ZHRMSGMPR-V_APPL = V_APPLno and the number is created in debugging mode and then it is being moved to OT_ZHRMSGMPR but in the output screen the moved value is not being displayed.
CALL FUNCTION 'BAPI_APPLICANT_CREATE'
          EXPORTING
          AP_GROUP                  = 'B'
          AP_SUBGRP                 = IT-I_AP_SUBGRP
          PERS_AREA                 = IT-I_PERS_AREA
          P_SUBAREA                 = IT-I_P_SUBAREA
          PERSONNEL                 = IT-I_PERSONNEL
          FOA_KEY                   = IT-I_FOA_KEY
          F_NAME                    = IT-I_F_NAME
          L_NAME                    = IT-I_L_NAME
BIRTHNAME                 =
SECONDNAME                =
KNOWN_AS                  =
SSN                       =
          B_DATE                    = IT-I_B_DATE
          TITLE                     = IT-I_TITLE
2ND_TITLE                 =
ARI_TITLE                 =
AFFIX                     =
PREFIX_2                  =
GENDER                    =
BIRTHPLACE                =
MAR_STAT                  =
INITIALS                  =
          NATION                    = 'IN'
          LANGU                     = SY-LANGU
C_O                       =
          STREET                    = ''
2ND_ADD_LN                =
          CITY                      = ''
REGION                    =
DISTRICT                  =
          PCD_CITY                  = '500008'
          CNTRY                     = 'IN'
TEL_NO                    =
          ADVERT                    = '00000000'
          UNSAPPGP                  = IT-I_UNSAPPGP
          MEDIUM                    = '00'
          EMPLOYEENUMBER            = '00000000'
COMMUNICATION_TYPE        =
E_MAIL                    =
    IMPORTING
          APPLICANTNUMBER           = V_APPLNO
RETURN                    =
TABLES
EDUCATION                 =
PREVIOUS_EMPLOYMENT       =
QUALIFICATION             =
VACANCY_ASSIGNMENT        = VACANCY_ASSIGNMENT
      IF SY-SUBRC EQ 0.
        OT_ZHRMSGMPR-V_APPL = V_APPLno.
      ENDIF.

594647 wrote:
we created an applicant on 01-May-2012 with applicant status as ACCEPTED. Yesterday 22-May-2012 the same applicant was hired in the system with the hire date set as 22-May-2012 this was based on the management approval.
But today another changes have come in so now the hire date must be 16-May-2012...
how can i get this done???
Thank you!what happens when you go the employee record-->benefits..and change the date first hired to 16th may??
Mahendra

Similar Messages

IDOC setting for tcode PB40 and applicant creation

In tcode PB40 (a tcode of HR Module), when for example, Applicant Creation is done, an IDOC is triggered.
We are encountering an error in the IDOC which is trigered when Applicant Creation is done because that IDOC is picking up a partner profile which is not correct.
Please tell me where is the setting maintained which dictates the triggering of IDOC in tcodes like PB40 (so that i can debug why is it picking up a wrong partner profile)

Hi,
This output determination is done using NACE..
For your scenario in We20 check the message type you are using and associated partner profile...there you need to configure the message control for generation of the idoc check whether this has been configured in different partner profile than required..
Also check any distribution model associated for this data (Tcode :BD64)
HTH
Rajesh

HCM Dynamic Applicant Creation

Applicant Data Will me Maintained in EXCEL .CSV File. I tried to update the excel data thro BAPI To create a New Applicant IN PB30 Dynamically. But went in vain.Kindly Suggest me an Idea or is there any option to create an applicant dynamically other than BAPI..

Ya i solved by creating Z Module

Applicant number creation

Hello, I created action called 'ZO' for applicant in 'SPRO' transaction which generates applicant number.
After applicant creation I got IT 4000 but didn't get IT 4003, without it I can not hire an employee.
So I am not able to find configuration to set up it.

Hi revathi,
i guess that,which you have created the applicant number 1.. it is internal number range right...after that some other person might be processed applicant number...(or already processed).some other person might be created 2,3,4..later once you did your applicant number that has taken 5.. nothing to worry..
hope it gives you clear idea.
//jcak//

Bapi for creation of employee(pernr)?

Hi,
Is there any Bapi with which we can create an employee(Pernr)?
I need to call this BAPI from .net connecctor.
We have BAPI_APPLICANT_CREATE for applicant creation. Like this, do we have any thing for employee creation?
Thanks in advance,
RSS.

You could have a look at the function modules starting with HR_INFOTYPE* especially HR_INFOTYPE_OPERATION. However, I've only used this to create things such as absences and absence quotas for an existing employee and it may not be possible to use it to create an employee from scratch.

Applicant Conversion - Which is better of the 2 options and why?

Hi -
I needed your technical expertise to identify the easiest and most efficient method I should take for converting the applicants -
First option is to Convert the candidate into an applicant by applying to an existing vacancy (This is similar approach we do in the front end ).
Potential API Internal Name: CONVERT_TO_APPLICANT
Interface:HR_APPLICANT_API.
Second method is a two step process, convert the candidate into an applicant, then creating applicant assignment for all the jobs the candidate has applied for.
Potential API Internal Name: ACTIVATE_EMP_ASG, CREATE_SECONDARY_APL_ASG
Interface:HR_ASSIGNMENT_API
Which approach do you experts think would be the best option and why?
Early response is much appreciated.
Many Thanks,
Dinesh Babuji

If you are looking applicant creation without Assignment , Ist option is good
If you are looking applicant creation with Assignment , IInd option is good
Thanks

MC94 Disaggregation in Level by Level Planning

Dear All,
I have created a self defined info-structure
Characteristics
Key Figures
Sales Organization
Sales
Distribution Channel
Production
Division
sold-to party
Product Group/material
Plant
I have done all the required configurations:
Assigning the planning parameters to the info structure. – MC7F with planning method I (Level by Level Planning) as with Product groups only level by level planning is applicable
Creation of Planning Hierarchy – MC61
Creation planning type - MC8A
After that in MC94 (Change Plan in Level by Level Planning), I am able to perform disaggregation only till Sold- to party. After sold to party, I am not able to dis-aggregate it further down to product group. I have maintained the product group below sold-to party in hierarchy as well. Please suggest.
Regards
Ashish

hi Ashish,
@ as mentioned by Mariano, please check the total % of the proportional factors.
either you want it to be 100% or more or less...depends on project requirement....
regards,
Sandeep

Automatic creation of applicant activities

Dear Experts,
I have created application status and applicant activity type and also configured for automatic creation of applicant activity. But after performing applicant action automatic applicant activity is not reflecting.
Did I miss any step.
Help me to solve this issue.
Regards,
Goldy

have u maintained the feature PACTV???

Creation of Applicant with Refrence Emplyee

Dear Experts,
I am new to HR module, there is a requiremnt where in I have written a report to create applicants using the standard BAPI
BAPI_APPLICANT_CREATE by giving the required parameters.But for creation of Applicats with existing employee refrence I was not able to find a parameter where in we can pass the reference employee details to the BAPI. If the BAPi which I have used is not the one by which I will be able to create Applicats with refrence employee details kindly suggest another BAPI or a Function module.
Thanks & Regards,
Murthy.

u can also use HR_MAINTAIN_MASTERDATA Tclass u can maintain as B.

Block creation of PO if the release strategies is not applicable

HI SAP,
Can we block creation of PO if the release strategies is no applicable ?
My release strategies is on the PO header. It's only work if the PO have one Plant only. If the user put more then one plant
my release strategies will not work. how to solve this problem ?

Hi,
Check on it:-
http://www.sapfans.com/forums/viewtopic.php?f=6&t=205684&start=0&st=0&sk=t&sd=a
Re: Release Strategies in Purchase Order - possible values of caracteristics
PO Release strategy question
pherasath

Applicant letter creation reruitment

Hi All,
Applicant letters ( Offer letter, Invitation letter, etc) in standard format that i need to change as per client requirement, could you all please to share the procedure how to change standard text and put client format on the same..
Please put you all your inputs...
Appreciate your inputs..
Regards,
KAmlesh Manker

Hi,
E-Recruiting or the 'old' recruitment?
Regards
Nicole

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

Error in creation of PurOrd IDoc

Hi All,
I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG but when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
What could be the possible problem?
Highly appreciate any kind of help.
Thanks in advance,
Shweta
PS: <b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

Hi
Check the Partner Profile in WE20 correctly
also see the steps for it as per the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

Goods receipt Capacity check in PO creation- EHP2

Hi
I have activated business function LOG_MM_CI_1 in our ECC 6.0 system . I have also activated Goods receipt capacity check and subsequent settings in customization . I am able to view the GR capacity check icon in Purchase order creation (ME21N). When I click this icon by selecting the line item , system does not perform any function . I have read in SAP documentation that Vendor can be assigned to door . I am not able to find this assignment in the system . Not sure whether this function is only applicable to retail system and not to SAP R/3 . If some one worked on this functionality , kindly request you to throw some light on this functionality .
with regards,
Joseph Anand B

Same thing is happening to me right now .. did you found out what the error was,, or what was missing ?
Please reply soon as I have a demo on the same in two days..
Regards
Digant.

Automatic po creation third party order

Hello Gurus,
In case of automatic po creation from third party order we have attach purchase organization and vendor to sales organization. This restrict only one vendor against sales organization.
Is any BADI available which we can use which to change vedor dynamically ?
Best Regards,
Vasant

Dear Vasant,
For automatic PO at the time of GR following are the prerequisites:
1) In Customizing
a) Auto PO generation must be activated in Mov. Type 101 & 161
b) the plant for which GR is entered must be assigned to standard Pur. Org.
c) Default Document type for PO must be specified in GR ( MB 01)
2) Application - Front end side
a) material must be valuated material
b) Purchasing Info record must exist for vendor , material & standard Pur Org.
c) Conditions in Info Records must be valid.
d) Applicable for stock items & not consumable items
e) you cannot enter any movement in GR block stock
f) Material Master & vendor master records must.
If you ensure all above settings then it is possible to have auto PO during GR.
Please try,
Vivek

Applicant creation

Similar Messages

Maybe you are looking for