Setting up AME for iRecruitment:

This Document is divided in to two parts.

1. Configuring AME Responsibilities for the User
2. Configuring AME for iRecruitment

1.Configuring AME Responsibilities for the User.

To use AME we need to have AME responsibilities assigned to our user. AME uses Role
Based Acccess (RBA) model.
AME has 5 seeded roles
1.
2.
3.
4.
5.

Approvals Management Administrator

Approvals Management BusinessAnalyst
Approvals Management System Viewer
Approvals Management System Administrator
Approvals Management Process Owner

AME can be accessed if sufficient functional grants are available. Each of the above 5
roles has specific set of functional grants. By assigning the roles to user, the functional
grants will be available to user and hence he can access those functions/pages. To
configure AME we need only the Approval Management Business Analyst role.
Assigning Roles to user:
Login as sysadmin user
Select the responsibility "User Management"
Select "Users" screen
Search for the user to whom you wish to grant AME roles.
In the results table, click on update icon.
In this page user details can be seen along with a list of roles available to user
Click on "Assign Roles" Button
Select the Approvals Management BusinessAnalyst role.
Now the functional access to user has been successfully setup and the Approval
Management Business Analyst Responsibility Is added to the user. Fucntion Business
Analyst Dashboard can be used to setup AME.

AME restricts access to "AME Transaction Types" using Data Security. To access AME
and use it, user needs to select a transaction type.

Access to AME transaction types to a user can be setup as follows:

Login as a user having Functional Administrator responsibility attached.
Select Functional Administrator responsibility
Select Grants Tab
Click on Create Grant
Select "Specific User" as grantee type
Select the User as grantee key
Select "AME Transaction Types" as object
In the next page there will be 3 options for instance type.
Select the All Rows Option.
In the next page, select "AME Calling Applications" as the permission set
Review and Finish.

-----------------------------------------------------------------------------------------------------------2. Configuring AME for iRecruitment:

Responsibility -> Approval Management Business Analyst
Function -> Business Analyst DashBoard
Select the transaction Type as iRecruitment Vacancy Approval

iRecruitment Provides seeded Approval Style, which is Supervisor Based and is for one
level (Goes for Approval to the immediate Supervisor). We can modify the seeded
Approval style if we want an Approval style other than Supervisor Approval or we need
more levels of approval.
We have almost all the Required Attributes and Conditions Predefined for iRecruitment.
Creation of attributes and Conditions are allowed if the business needs it (This is not in
the scope of this Document).
Steps for modifying the seeded Approval Style:
1. Create Approver Group
2. Select the Required action types
3. Use the action in the Rule
1. Define Approver Group:
Create an approver group whenever there is a need to create approver(s) who is not part
of the supervisor hierachy. (For example we may require the Approval to go for HR
Manager after the Supervisor approval)

Click on the Approver Group from the Dashboard and then click on create button.
1.Give a Name and Description for the Approver Group
2. Give the order Number.If you have Multiple Approver Groups the, Order of Approval
will be decided based on the order Number.
3. Select the Voting Method as Serial.
4. Select the usage type as static or dynamic.
If the type is static, we need to add the Approver in the Group Member Region
(Present in the Bottom of the page)
If the Type is Dynamic, then we can select the approver with the help of an SQL
Query.
Here is a sample Dynamic Query.
Select PER:||person_id from per_all_people_f
Where person_id =132

(Refer Note: 336901.1 - AME implementaion Guide for More Details on

Dynamic Approval)

2. Define Action Type:

An action type is a collection of actions having similar functionality. Every action

belongs to an action type. Action types are enabled or disabled for a particular
transaction type.
There are several Predefined Action types Available in AME. Supervisory Level is
available by default. If we need to use other action types for the transaction, we need add
the action here by clicking on the Use Existing Action Types Button. For example if we
need to add the HR Manager as a Final Approver then we need to add the action type
approval-group chain of authority. After adding when we select the Approval-group
chain of authority the actions Region will list all the Approver Groups that are created.
Selecting the supervisory level will list the Levels of approval needed.
Note: Check the AME Implementation Guide for more details on various Action types.

3. Define Rules:
Click on Rules tab or we can select Rules from the DashBoard.

A Rule contins two parts.

1. Condition - Specifies the condtion on which the Rule will be fired.
2. Action - Specifies the action to be performed when the rule is fired.
iRecruitment has a set of Predfined Rules Delivered with Pre-defined conditions and
Rules. We can modify the conditions and rules to suit our Business Requirements or we
can create a new Rule.
The seeded rule for Creating or updating vacancy is iRecruitment Create Vacancy.
The Rule has VACANCY_INSERT_OR_UPDATE in (INSERT) condition added by
Default.
The action attached to this rule by default is supervisory level action type with Action
Require approvals up to the first superior, at most.
We can remove the existing actions or create new actions. For example if we want to add
the HR Manager as the Final Approver we need to add an action by clicking on the Add
action button. Select the action type as Approval-group chain of authority and select
the action (Select Approver Group that we have created in Previous step for selecting the
HR Manager).

Note 1: Setup is very similar for Offer Approval also. The Transaction type for offer
Approval is iRecruitment Offer Approval.
Note 2:
There are 3 temporary tables that hold data for entries made in iRecruitment until the
approval cycle is complete.(This is from IRC.e.RUP1 onwards. Earlier the table used is
HR_WIP_TRANSACTION).
1) HR_API_TRANSACTIONS - Each iRecruitment transaction is represented by
one row.
2) HR_API_TRANSACTIONS_STEPS - Each row in hr_api_transactions is
mapped to one or more rows in hr_api_transaction_steps table with following
relation.
hr_api_transactions.transaction_id = hr_api_transaction_steps.transaction_id
3) HR_API_TRANSACTIONS_VALUES Each row in hr_api_transaction_steps is
mapped to one or many rows in hr_api_transaction_values table with following
relation.
hr_api_transaction_steps.transaction_step_id =
hr_api_transaction_values.transaction_step_id
Data from this table is used while making the API call. This table stores each
parameter name, data type of the parameter and value.

References:
1.434567.1 - Approvals Management Responsibilities and Setups in AME.B
2. 336901.1 - AME implementaion Guide
3. 453507.1 - Extract Vacancy Details From Table HR_WIP_TRANSACTIONS /
HR_API_TRANSACTIONS