Are you implementing your eRecruiting system outside of your HCM system? This is a good practice, since eRecruiting has external services which most likely would need to be visible to non-authenticated users on the internet. A good example of this is your Company’s external website with a Job Search function. You might not want potential candidates to have to create a candidate user ID if they are just searching for jobs you currently have open, or can’t find a suitable job at this time.
ALE allows disparate HCM and eRecruiting systems to utilize the same Organization Structure, as well as bringing your existing Employee and user information into eRecruiting.
This set-up will automatically create the organization structure in eRecruiting, but will also keep it updated. Additionally your employees will automatically be created in eRecruiting so they can apply for internal postings.
Step 1 In the eRecruiting Development box, go into the IMG and maintain the settings for separate HCM and Recruiting.
Step 2 Go to transaction SALE.
Step 3 Navigate to Define/Assign Logical Systems:
- a. Select Define Logical System first. Create a logical system for the HCM and eRecruiting systems in both HCM and eRecruiting.
- b. Select Assign Logical System to Client (only to the client you are in- not to both clients- see below)
Assign the Logical System (created in A. above) to the appropriate Client. You will assign the HCM LS to the HCM client in the HCM system. Do the same in the eRecruiting system, assigning the eREc LS to the eRec client in the eRec system.
Step 4 Navigate to Create RFC Connections (transaction SM59):
In HCM System create eRec ABAP connection:
In eRecruiting system create HCM ABAP connection via SM59:
Be sure these connections have a valid communications user <ALEUSER> with a password you know.
Step 5 Determine RFC Destinations for Method Calls:
In HCM: Select the eRec Logical System. Click Create Standard Bapi Destination:
This ties your Logical System to the ABAP Connection.
Repeat this step in the eRecruiting System, tying the HCM Logical System to the HCM ABAP connection.
Step 6 in HCM, navigate to Maintain Distribution Model and Distribute Views (transaction BD64):
Click Create model view. Create a model that makes sense for the connection. Recommend a name that does not mention ‘Dev’ or ‘Prod’, as you can transport your Distribution model, then change the logical systems. Click Save
Now highlight your newly created model and select Add message type:
Select the Sender. Since you are maintaining this in HCM the Sender will be the HCM Logical System.
Select the Receiver, which would then be the eRecruiting system.
The Message Type will be the latest message type both HCM and eRec systems have. To determine this, go to transaction WE60, entering HRMD* in the drop-down. The HRMD_ABA iDocs will be in both HCM and eRecruiting. In this ABAP system the latest version is HRMD_ABA05:
In the eRecruiting system verify this idoc also exists there.
Enter the Message Type HRMD_ABA. Save your Distribution model.
Step 7 Create Filter of what you want to send to eRecruiting. Open the Model until you see No filter set:
The following dialog box will appear:
Select Create Filter Group button. Open the Data Filtering area until you see Object Type, etc. Douple-click on Object Type. A second pop-up will appear:
Do the same for the other areas. Save your Filter Group.
You can add as many as you need.
To select Employee Master Data, select Object Type P and the Infotypes you want (0000, 0001, 0002, etc.)
For Org Data: Obj Type: C, O, S Infotype 1001 Subtype A002, A003, A007, A008, A012, B002, B003, B007, B008, B012
Obj Type: C, O, S Infotype 1000
Obj Type P Infotype 0000, 0001, 0002, 0006, 0105, 1000, 1001
Step 8 Generate Partner Profiles. Highlight your model, then select Environment- Generate Partner Profiles
<Leave Partner system blank>
Step 9 Distribute the Distribution model. Select your model then Edit- Model view- Distribute
This places the Distribution model in the receiving system.
Step 10 In eRecruiting system, go to Maintain Distribution Model (transaction BD64) and go to your Distribution model. Generate the Partner Profiles there as well by highlighting your model, then select Environment- Generate Partner Profiles:
Step 11: Activate Change Pointers in HCM. Navigate to Activate Change Pointers for Message Types:
Enter your iDoc – HRMD_ABA. Then Activate Change Pointers- Generally.
This turns on the change pointers so changes will begin to create idocs in the sending system.
Step 12 Test your set-up by modifying some Master Data in the HCM for an infotype included in the iDoc. Save the infotype.
Go to Program RBDMIDOC and execute it with Message Type HRMD_ABA.
Go into eRecruiting system. Execute transaction WE05 to view any received iDocs.
Getting any Data from HCM to eRec (for example, if eRec goes live after HCM) see transaction PFAL
Step 1 Execute PFAL (RHALEINI)for Obj Type O, Infotype 1000 and Transfer mode as Update mode
Step 2 Execute PFAL (RHALEINI)for Obj Type S, Infotype 1000 and Transfer mode as Update mode
Step 3 Execute PFAL (RHALEINI)for Obj Type O and Transfer mode as Insert
Step 4: Execute PFAL (RHALEINI)for Obj Type S and Transfer mode as Insert
Step 5: Execute PFAL (RHALEINI)for Obj Type P and Transfer mode as Insert