I Recruitment

Few important points before we start I Recruitment:

o Migration of Legacy data to I Recruitment is possible

o Even without having full HRMS functionality you can have I Recruitment available to
your organization.
o Approval work flow is supervisory based. But you can create a new Transaction type
and can attach the same to existing workflow. This can be done with the help of
AME (Oracle Approval Management).

Implementation:

Profile Options:
Abbreviation used: Site – S, Application – Ap, Responsibility – R, User – U.
Configurable
Profile Option Description Default Value
Level
Application Proxy S Define the Proxy exclusion list. Syntax to be used is *.domain1.com;
Bypass Domain *.domain2.com etc.
Application Proxy S Port for Proxy server – if required.
Port
Application server S Proxy server address – if required.
side proxy host and
Domain
Application SSO S,Ap,R,U Determines if you use Oracle Portal for SSWA.
Type Logging in. Oracle Portal login is not
appropriate for external candidate
responsibility hence if u have SSWA as
profile option at site level change it at
responsibility.
IRC: Accent S,Ap,R,U Identifies the Background colour for action If you do not set this profile option
Background Colour button and table background. Set 6 digit than system uses the default
hexadecimal value for corresponding colour. colour set in the xss style sheet.
IRC: Anti Virus S This is for scanning the document which are
Server uploaded by Candidate and Manager.
Provide name of server on which Anti Virus
engine is running.
IRC: Background S Required for Background check function.
Checking Vendor
URL
IRC: Background S,U Company Account name for Background
Check Sender check.
Credential
IRC: Core S,Ap,U & R Set core colour for page component for
Background Colour page components like Tab bar, Header &
Footer. Set six digit hexadecimal no,
IRC: Default S,AP,U & R Define default country when – (i) Parsing
Country resumes: when application can not find a
country than uses default country’s address
style. (ii) When candidate enter the
address information it get defaulted but
can be changed by candidate. & (iii) for
eLocation – this is limited for few countries
only.
IRC: Document S,R Max no of the documents a candidate can 20 at Site Level
Upload Count Limit upload in system. If we keep this blank
candidate can upload as many documents
required but it can not exceed total max
monthly count.
IRC: Extract Skill S Indicates whether skills should be Yes
extracted when candidate parse a resume.
If no than candidate have to select skills
manually.
IRC: Geocode Host S URL for Geocode information.
IRC: Internal S,R This defines no of days for which a vacancy
Posting Days should be available for Internal site before
they can appear on the external recruitment
site. If this profile is set than you can not
alter the Start Date of the Vacancy on the
External site as system automatically
decides the same upon the start date of
vacancy and the no. of days defined here.
IRC: Installed S Indicates that IRec is licensed. No.
IRC: Job S, R This profile option identifies the function IRC_APL_VAC_DIS_PLAY –
Notification used to show advt. user when they click on Candidate Responsibility &
Function the notification. IRC_VIS_VAC_DIS_PLAY for all
other responsibility.
IRC: Monthly S,R Max no of the document candidate can 10 at the site level.
Document Upload upload. If not specified unlimited subject to
Count Limit no specified in total document count.
IRC: Notification S,Ap,R This will decide which workflow IRC_WF
List Types notifications are displayed on the home
pages of the managers and candidates. If
you wish to see notification for more than
one workflow than just separate them by
comma (,) sign.
IRC: Proxy S Password for Proxy server.
Authorization
Password
IRC: Proxy S User name of Proxy Server.
Authorization User
Name
IRC: Registration S,R When candidate registers than person Note: to use this profile option at
Business Group record is created in the specified business Responsibility level Use I Rec.
group. External Site visitor responsibility
that can be associated with guest
user.
IRC: Registration R Responsibility that a user is given after I-Recruitment External Candidate
Responsibility registration. or I-Recruitment Emp. Candidate
IRC: Resume Parsing S,U Password for Resume Parsing Vendor for
Sender Credential resume parsing.
IRC: Resume Parsing S,U User ID for above.
Sender ID
IRC: Resume Parsing S URL for Resume Parsing Vendor. Set this
Vendor URL profile option if you are registered with
Resume parsing provider. If you don’t setup
this profile option then the resume parsing
functionality and the Upload resume region
is hidden from your user and replaced with
std. document upload functionality and text.
IRC: Search Criteria S, R Determines the segments that are matched
Segment matching when your managers performs candidate
matching for a vacancy, or when you run the
process I Recruitment e-mail job seekers.
Enter the segment numbers to whom you
want to match, separate with symbol |
(pipe). If nothing is mentioned than
application matches all the active segments.
IRC: Suitable S This profile option identifies the function IRC_CM_CAND_DETAILS
Seekers Function used to show candidates to managers when
they click on a link in a notification.
IRC: Text S,Ap,R,U Identifies the Background color of the
Background Color content. 6 digit hexadecimal code.
IRC: Text S,Ap,R,U Identifies the color of the text.
Foreground Color
IRC: Vacancy S When person receives the vacancy to IRCVACAAPPROVAL
Approval Function approve the notification contains the link to
page that displays the vacancy that has
been asked to approve. This profile defines
function for that page.
IRC: Workflow Item S,R Defines which workflow item is used in I IRC_WF.
Type Recruitment. The seeded workflow item
type is delivered with I Rec. is IRC_WF.
This item type governs the workflow in the
vacancy process i.e. vacancy creation,
approval and notifications.

I Recruitment & AME:

With AME you use components to define your approval process which are in turn associated
with Transaction Type of the Application.

o Attribute: This is a business Variable, Salary Amount, User ID or a Vacancy Type.

o Condition: it compares the attribute value with set of allowed attribute values. For
e.g. if a salary amount is a specific amount than approval list is created.
o Approval Type & Approval Specification: These components define the type of
approver list that is being generated. For e.g. to generate the Supervisory – based
approver list with 5 levels, you use the “Supervisory Level” approver type with the
“required approval up to the first 5 approver’s ” approval specification.
o Rules: It links the other components together by associating one or more conditions
with the approval type and approval rule.

Default use of AME configuration in I Recruitment

It’s a supervisory based hierarchy. Here you can either create a custom transaction type or
you can use Vacancy Approval Transaction Type.

AME – will be covered at the last stage.

Important Step  The ircdtd.zip should be extracted to html directory. If you don’t do
this than you may encounter problems when parsing resumes or initiating background checks.

I Recruitment Index Synchronization – this ensures the Job Posting and document index
are kept upto date should
1. Online Index Rebuild – At the end of every 5min
2. Full Index Rebuild – At every night.

IRC_VARIABLE_COMP_ELEMENT lookup type for compensation element lookup to be

advertised against your vacancies.
Schedule following Concurrent Request.

1. iRecruitment Email Job Seekers Details to Vacancy Owner  this request sends the
notification to Manager of open vacancies to inform them about suitable match.
2. iRecruitment Email Vacancies to Job Seekers.  This sends notification to suitable
candidate. You can schedule this at night.

Business Group Level Information:

Go to your business group definition. Go to Others Tab and select Recruitment.

Enter Following Information:

1. Vacancy Code Allocation: (i) Manual: Vacancy name field will be available and you
need to enter the vacancy details manually. (ii) Automatic: the application assign a
unique vacancy name automatically. The vacancy field will not be displayed.
2. Default no of vacancies. You can override the same at vacancy level.
3. Specify Organization Defaulting Method; (i) Creator: Default Organization is the
organization of the Creator of the vacancy i.e. organization to which the person
belongs. (ii) Manager: Organization of the Manager of the Vacancy. (Both the
method uses the primary assignment i.e. organization at primary assignment level)
4. Specify Location Defaulting Method: (i) Manager: Location of Manager to Vacancy.
(ii) Position: Location of Position of Vacancy.
5. Default Budget measurement Type: like full time equivalent or headcount etc. (this
depends upon the budgeting setup done at Organization level.)
6. Default status for candidate withdrawing application: If you do not specify anything
here than candidate receives Terminate Status.
7. Default Person type: in HRMS we can have user defined person type as a default for
candidate who register in iRecruitement. If you don’t specify anything than default
status is Candidate. (The user person type that you define here is associated with
the External system person type. Internal code for External System person type is
OTHER.)
8. Save your work.

Defining Assignment status:

Go to Assignment Status window

Defining Primary User Status: (i) Renaming User Status – Delete the name and just provide
your desired name. (ii) Inserting New Record: Insert record provide the username – for
iRecruitement you can use external status which will be shown to the third party for e.g. in
case of Interview you may have 1st Interview , 2nd Interview etc but for applicant you can
have External Status as Interview for both of them and the candidate can see status as
Interview only irrespective of 1st interview or 2nd interview. (iii) If you are defining
Assignment Status for Employee you have to select Payroll system Status if you do not
select Payroll here than payroll will not process this assignment status while processing
payroll.

Defining Secondary User Status: As seen user status associated with the system status is
known as Primary Status because this will determine how system will process this
assignment. You can define secondary status for your reference like analysis purpose but
this status will not be used by System for any kind of Processing. (i) Insert New Record in
Assignment (ii) Type User Status and do not select System Status, Type field will show
secondary.

Setting up Searchable Flexfield:

Define Additional Search Criteria details (descriptive Flexfield  Human Resource).

Import point: lets assume that you have Experience Years as one of the Segments
now when the concurrent manager runs to notify your manager of suitable candidate
or notify candidates of suitable jobs than it will match exact details like if for Job
Requirement is 5 years than it will search only for 5 years candidate and not those
having any extra or less experience. To control which segment to be used in this
search criteria depends upon profile option IRC: Search Criteria Segment Matching
(but this profile option does not have any impact on other search on any other page
of iRecruitement).

1. Define Segments in “Define Additional Search Criteria Details” try and make it non-
criteria sensitive.
2. Personalize Create vacancy page and candidate’s work preference pages to display
DFF.
3. Personalize pages (i) Vacancy Search, (ii) Candidate Search, (iii) Candidate for
Vacancy Advance Search, (iv) Visitor Job Search and (v)Candidates Job Advance
Search.
4. Set the profile option - IRC: Search Criteria Segment Matching – as discussed this
profile option determines the segment matching to be done for notifying managers
about correct candidate and job seekers about the Job. If you wish to match say
Segment 2,5,6 than you need to provide 2|3|5.

Setting up Virus Scan:

Skipped. (please read from page 73 & 74 of Oracle iRecruitment Implementation Guide
Chapter page no. 2.37 & 2.38)
Security

Vacancy Security: iRecruitment controls users access to created vacancies and to create
vacancies. By applying proper security profiles you can restrict manager from Creating
vacancies for a particular organization.

o Registered User & Site Visitor: As they should be allowed to have access to all the
vacancies there is no need to setup security profile for them.
o Managers & Recruiters: Security Profile as defined in HRMS.
o User Access to Personal Information: this is defined by the candidate himself while
registering himself i.e. while creating profile in iRecruitment he has option of making
his details published. If he selects this option than his information are available to
all else only those managers or recruiters who has access to his vacancy can see his
information. All candidates will have access to information only relating to them.

iRecruitment Responsibilities & User Menus:

Predefined Responsibilities are: (i) iRecruitment Manager, (ii) iRecruitment Employee

Candidate, (iii) iRecruitment External Candidate, (iv) iRecruitment Employee Site Visitor,
(v) iRecruitment External Site Visitor & (vi) iRecruitment HRMS Manager.

Predefined Menus are: (i) IRC Advance Manager Menu, (ii) IRC Employee Candidate Menu,
(iii) IRC Employee Site Visitor Menu, (iv) IRC External Candidate Visitor Menu, (v) IRC
External Site Visitor Menu, & (vi) IRC Manager Menu.

Self Service Menus and User Access:

iRecruitment uses 5 types of Menus (i) top-level menu  e.g. iRecruitment Manager, (ii)
homepage menu  these are application menus for users for e.g. IRC <user> Application
Menu comes to IRC Employee Candidate Application Menu, (iii) sub-menus, (iv) hidden sub-
menus  just remove the name of Promt form the menu screen. & (v) Global Menus.
iRecruitment Functions: