SAP ABAP IMG Activity RCF_WF_STATUS_CHANGE (Workflow After Status Changes to E-Recruiting Objects)
Hierarchy
☛ ERECRUIT (Software Component) E-Recruiting
   ⤷ PA-ER (Application Component) E-Recruiting
     ⤷ PAOC_RCF_BL (Package) Recruitment Factory: Business Logic
IMG Activity
ID RCF_WF_STATUS_CHANGE Workflow After Status Changes to E-Recruiting Objects  
Transaction Code S_PE1_57000007   (empty) 
Created on 20030130    
Customizing Attributes RCF_WF_STATUS_CHANGE   Workflow After Status Changes to E-Recruiting Objects 
Customizing Activity RCF_WF_STATUS_CHANGE   Workflow After Status Changes to E-Recruiting Objects 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RCF_WF_STATUS_CHANGE    

Use

Additional steps are triggered by the Status Change workflow (ERCStatusChg) when status changes are made to the E-Recruiting objects Candidate (ERC_CAND), Candidacy (ERC_CDCY), Application (ERC_APPL), Requisition (ERC_REQUI), or Job Posting (ERC_POST).

For example, if the status of an application is changed to Withdrawn, additional changes must be made to all open candidacies of this candidate. This prevents these candidacies from being processed further, although the candidate is no longer available for this.

Requirements

Standard settings

The Status Change workflow (ERCStatusChg) is triggered when the status of an E-Recruiting object is changed (event StatusChanged). The following workflow scenario is delivered by SAP in the standard system and runs automatically in the background for the Candidacy and Application objects.

Candidate

The workflow checks whether the candidate is an employee.

  • If the candidate is an employee, the workflow is completed.
  • If the candidate is not an employee, the workflow checks whether the candidate profile is released or locked.

Depending on the status of the candidate profile, the following steps are performed:

Candidate profile status Released:

  • The index for the candidate object is set with the following attributes:
    • Application Area: Candidates
    • Index Group: MNWENA

      The system uses indices when creating worklists in the dashboard.

Candidate profile status Locked:

The index for the candidate object is deleted with the aforementioned attributes.

Candidacy

The status was changed to In Process.

  • Following activity is created: 0010 Check Suitability (Planned)

The status was changed to Withdrawn.

  • The data retention period as required by law is set.
  • The workflow determines the names of the candidate and support team members assigned to the associated requisition.
  • A member of the support team who has been assigned the role of recruiter, is informed of the status change via e-mail.

The status was changed to Rejected.

  • The type of requisition is determined.
  • If the requisition is a job-specific requisition, the data retention period as required by law is set.

Application

The status was changed to In Process.

  • The index for the application object is set with the following attributes:
    • Application Area: Applications
    • Index Group: MNEWND

      The system uses indices when creating worklists in the dashboard.

  • A copy of the resume is added to the Audit Trail.
  • The following activities are created:
    • 0200 Check Documents for Completeness (Planned)
    • 0070 Find Suitable Requisitions (Planned)
  • The workflow then checks how the application was submitted. Different activities are created depending on the application source.

    Application of an Unregistered Candidate

    • Following activity is created: 1030 Acknowledge Unregistered Candidate (Planned)
    • The acknowledgement is then sent by e-mail and the status of the activity is set to Completed.

      Application of a Registered Candidate

    • Following activity is created: 1020 Acknowledge Registered Application (Planned)
    • The acknowledgement is then sent by e-mail and the status of the activity is set to Completed.

      Application Submitted Using the Application Wizard

    • Following activity is created: 1035 Application Confirmation (Manual) (Planned)
    • If an e-mail address is stored, the confirmation is sent by e-mail and the status of the activity is set to Completed. If no e-mail address is stored, the status of the activity remains Planned.

The status was changed to Withdrawn.

  • The index for the application object is deleted with the following attributes:
    • Application Area: Applications
    • Index Group: MNEWND

      The system uses indices when creating worklists in the dashboard.

  • A copy of the resume is added to the Audit Trail.
  • The workflow determines all of the candidacies that are based on the application.
  • The system sets the status of these candidacies to Withdrawn.

The status was changed to To Be Hired.

  • A copy of the resume is added to the Audit Trail.
  • The workflow determines all of the candidacies that are based on the application and assigns the corresponding status reason to the status change.
  • The system sets the status of all open candidacies to Rejected.

The status was changed to Rejected.

  • A copy of the resume is added to the Audit Trail.

The workflow determines all candidacies that are based on the application and sets the status of all open candidacies to Rejected.

The workflow then checks the reason for the status change.

If it is due to an error in the application entry process, then the workflow is ended. This is the case if the assigned reference code is changed during the manual application entry process. For more information about this, see Workflow After Data Entry Error.

If this is not the case, the activity 1060 Correspondence Rejection (Planned) is created for the application. If an e-mail address is stored in the candidate profile, the acknowledgement is sent by e-mail and the status of the activity is set to Completed. If no e-mail address is stored, the status of the activity remains Planned.

Activities

Example

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG RCF_WF_STATUS_CHANGE 0 ALN0000024 O KER0000011  
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
OOCU T - Individual transaction object HRRCF_STATUS_CHANGE  
History
Last changed by/on SAP  20030130 
SAP Release Created in 10A