In this article we will undertake a simple example for AME customization in iRecruitment. This example pertains to Vacancy creation process in iRecruitment.
In the last three AME articles we learnt
1. Basics of AME
2. How SSHR is attached to HRSSA Workflow and AME
3. How to create FND User for AME with necessary RBAC
This example has been purposely kept very simple to show you the end to end process involved in setting up Custom Logic for AME in eBusiness Suite. At the end of this example, you will find a link to see the video demo explaining how these steps are implemented in real-time. Do not miss out the video link at the end of this article if this is first time you are trying to customize AME.
What is Vacancy creation process in iRecruitment
Using iRecruitment, the vacancy creation process can be de-centralized. This reduces the operations costs for central HR/Recruitment team. For example, “Oracle Development Manager” can have access to responsibility “iRecruitment Manager” and also the “Payroll Manager” can have access to the same responsibility. By decentralization of these responsibilitiies, an “Oracle Development Manager” can post a job advert for a developer by themselves. Likewise the “Payroll Manager” might want to hire a Payroll clerk, therefore they might want to create a vacancy for Payroll Clerk. Alternately the same functions can be performed via responsibility “iRecruitment Recruiter” too. The idea here is that the vacancy gets drafted and advertised by the very person that originates the requirement or by their secretary.
What is the business requirement for this customization, as per the example in this article?
The business requirement in this example is very simple.
Part 1. Whenever a new Vacancy is created, it should first go for approval to the Supervisor of the vacancy creator.
Part 2. After the vacancy has been approved by supervisor, it should then be approved by “Recruitment Administrator” in central Recruiting team.
The “Part 1” of this requirement is already present in standard Oracle functionality.
Customization is required for implementing the Part 2.
Example data used in this customization
USER BERICKSO creates the vacancy
His Supervisor “Brown, Casey” gets notified for approval
Recruitment Administrator “Stockman, Pat” gets notified after “Brown, Casey” approves the notification
How to implement the “Part 2” of this requirement?
a. Create a static AME Approval Group, and add the name of the Recruitment Administrator to this approval group. Approval group is something that returns a list of Approvers, either from a pre-defined list of approvers or dynamically from SQL statement.
b. Include this new Approval group into the AME Rule that is used by Vacancy Creation process.
How did Oracle design its vanilla/standard approval process for vacancies?
In other words, why does standard Oracle process works the way it does?
The “AME Trsnsaction Type” for iRecruitment Vacancies is “iRecruitment Vacancy Approval”. This AME Trx Type uses an AME rule named “iRecruitment Create Vacancy”. If you open this rule, in “Approvals Management Business Analyst” responsibity, you will notice that it uses action type “Supervisory level”.
Therefore each time you create a vacancy in iRecruitment, the supervisor of the vacancy creator receives a notification to approve/reject the vacancy.
To recap- the customization steps of video link
Create a static “Approver Group” in AME that will have “Stockman, Pat” who is Recruitment Administrator
Include this “Approval Group” in the desired “Approval Rule” which gets executed during vacancy creation.
Testing the results
The result of our AME customization can be tested by the steps as shown in video tutorial below
You will notice that now there are two approvers that will be required to Approve any vacancy.
First approver will be the supervisor/manager and the next approver will be the Recruitment Administrator.