Kontakt

Ansicht
Dokumentation

ERC_WF_STATUS_CHANGE - Workflow After Status Changes to E-Recruiting Objects

ERC_WF_STATUS_CHANGE - Workflow After Status Changes to E-Recruiting Objects

Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

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

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.

The Status Change workflow (ERCStatusChg_2) 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.

Candidacy

The status was changed to In Process.

  • Following activity is created: 0010 Check Suitability (Planned)
  • The workflow assigns the candidacy to the process that is relevant based on the origin of the candidacy.
Note
Also see the Customizing activities Assign Origins of Candidacies to Processes and BAdI: Determine Origin of Candidacy.

The status was changed to Withdrawn.

  • The data retention period as required by law is set.
  • The workflow determines the name of the associated candidate.
  • The recruiter assigned to the requisition is then determined. This is either the responsible recruiter or the first recruiter of the support team. The recruiter is informed of the status change by 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.

  • 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 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.

The status was changed to Withdrawn.

  • 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.






Addresses (Business Address Services)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 7147 Date: 20240523 Time: 211104     sap01-206 ( 61 ms )