Non-Configurable Status Processing

By providing a configurable status framework, Oracle enables you to add additional statuses to meet your organization’s need. The system also allows you to change the delivered statuses, but use extreme caution if you do so. The system has non-configurable references to many of the delivered status codes, so be sure to thoroughly test any changes you make.

WARNING:

Oracle recommends that you do not change the delivered status codes because the system contains many non-configurable references to specific codes.

For example, in the Recruitment Summary area, the Reject Applicant action always applies status code 110. Therefore, using that code to represent anything other than a rejected status will invalidate the Reject Application action. You can change the description if you prefer a different word rather than Reject, but the code itself should always be used to represent a rejected disposition.

The following sections provide examples of non-configurable status code processing for different status areas.

Recruitment Summary Statuses

The following table lists examples of when the system invokes specific status codes for the recruitment summary (disposition) area.

Code and Delivered Description	Examples of Non-Configurabe Processing
015 - Linked	The Link Application to Job action uses has a non-configurable default disposition of 015, but users can override the default.
019 - Linked Questionnaire	The Link Applicant to Job Opening action displays a warning if you assign a disposition other than 019 when linking an applicant to a job opening that has a questionnaire, or if you assign disposition 019 to a job opening that does not have questionnaire.
071 - Offer Accepted	The Prepare for Hire action is available if the disposition is 071. (This action is also available if the disposition is 080 -Ready for Hire, 090 - Hired, or 120 - Withdrawn.)
080 - Ready for Hire	The Prepare for Hire action always applies disposition 080. The Withdraw from Hire action is available only if the applicant's current disposition is 080.
090 - Hired	The post-hire message from the Human Resources system sets the disposition to 090. The Copy Applicant to Employee action is available only if the disposition is 090.
120 - Withdrawn	Performing the Withdraw from Hire action always applies status 120.
110 - Reject	The Reject Applicant action always applies disposition 110. The In Process Applicants pivot grid disregards applicants in disposition 110.
112 - Failed Prescreening	The Rejected/Reviewed chart for job openings does not include applicants in disposition 112 in either the applications received or applications rejected data.
130 - Withdrawn Application	The Withdraw Application action always applies disposition 130. The availability of the Withdraw Application action depends on whether disposition 130 is a successor for the application’s current disposition. The option to select the Applicant Withdrawal check box for a disposition (giving an applicant the ability to withdraw an application in Candidate Gateway) depends on whether disposition 130 is a successor for the disposition being configured. Note: The delivered reason codes for the 130 - Withdrawn Application disposition also have non-configurable processing. When an applicant withdraws the application using Candidate Gateway, the system assigns code 010, Candidate Withdrawn. When a recruiting user uses the Withdraw Application action, code 020, Recruiter Withdrawn is the default reason, but the user can change this.

Job Opening Statuses

The following table lists examples of when the system invokes specific status codes for the job opening status area.

Code and Delivered Description	Examples of Non-Configurabe Processing
110 - Filled/Closed	The post-hire message from PeopleSoft HCM sets this status if the available openings is zero.
100 - Hold 110 - Filled/Closed 120 - Canceled	The Hold, Close, and Cancel actions on the Search Job Openings page use these status codes when updated the job opening status. If any of these status codes do not exist, the corresponding action does not appear in the Group Action menu.

Offer Statuses

The following table lists examples of when the system invokes specific status codes for the offer status area.

Code and Delivered Description	Examples of Non-Configurabe Processing
020 - Accept	Applied to offers when applicants accept an online job offer in Candidate Gateway or when recruiting users perform the Accept Offer action.
110 - Reject	Applied to offers when applicants reject an online job offer in Candidate Gateway and when recruiting users perform the Reject Offer action.