Request to review the custom workflow logic in E recruting

Question

<b>Requirement:</b>
The purpose of this workflow is to change the status of the candidate to “Rejected” if they are not selected in the selection process and also to change the status of the requisition to “Closed” when a candidate is selected. The workflow is triggered when the system is updated to reflect that the candidate has accepted the offer.
<b>processing details:</b>
• When a candidate has accepted an offer, an activity “Offer Accepted” is created in the Status Change infotype (IT5139). This will trigger the workflow.
• The workflow will check the Candidacy infotype (5133) for all other candidates who have applied for the same position and reject the candidate by creating a “Rejected” activity.
• Simultaneously the workflow should change the status of the Requisition Info type to closed, so that the requisition status is closed
<b>
Logic</b>
<b>Step 1</b>: Candidate accepts the offer (Trigger)
When the Candidate accepts the offer, i.e. if in the table HRP 5139 (Status change infotype which stores the activities which result in status change of candidate) for the keyed in value of object type ‘NE’ (Candidacy) plan version Current, with the keyed in start date and the end date the value of the field ‘ACT_CAT’ (activity category) is ‘5100-Offer Accepted’, the workflow should trigger
<b>Step 2</b>: Change Status of Non-Selected Candidates to rejected
A) Check infotype, table HRP 5139(Status change infotype which stores the activities which result in status change of candidate) for keyed in value of object type ‘NE’ (Candidacy) plan version Current (field name PLVAR), with the keyed in start date (field name - BEGDA) and end date (field name-ENDDA) the value of the field ‘ACT_CAT’ (activity category) is ‘5100-Offer Accepted’ or not
If it exists then no action,
If not then,
B) Trigger (create) the activity “5010-Rejection” (field name “ACT_TYPE”,) in the table HRP 5139 (Status change infotype which stores the activities which result in status change of candidate) for the object type ‘NE’(Candidacy) plan version ‘Current’ with the keyed in start date (field name- BEGDA) and end date (field name-ENDDA) and save ,
<b>Step 3</b>: Close Job Requisition
A) Derive the value of object id for object type ‘NB’ {Requisition (related object type)} in table HRP 1001, subtype A654 (Relationship between Candidacy and Requisition) for the keyed in value of the object type NE (Candidacy) plan version ‘Current’ with the keyed in start date (field name- BEGDA) and end date (field name-ENDDA) .
B) For the above derived value of Object type ‘NB’ (Requisition), change the status of the table HRP 5125 (‘Requisition information’ infotype that stores the status of the ‘Requisition’), to closed field name “STATUS” ‘value 2-closed’ plan version ‘Current’ with the keyed in start date (field name- BEGDA) and end date (field name-ENDDA).
Request to Check the workflow logicand provide your valuable comments.
Thanks and best regards
Rajeev

Answer 1

Hallo Rajeev,
better forget the idea of the standard sap workflows - they are just examples and my opinion is: they are bad ones.
I understand the topic, although so far I did not encounter any customer / hr department which was giving the system so much power through automatization. You also will never be able to hire more than 1 person on 1 requisition. But this is all requirement analysis not solution (although the sencond one is not possible w/o the first one - "pigs will fly before I implement a workflow just the way the hr department described and requested it" ;o).
Your description is quite rough from my point of view. The workflow landscape is missing to tell you if this steps are enough to get your things done correctly and of course without your processes no serious workflow programmer will give his ok to a workflow soluition.
What I see as a problem you defined everything based on tables. E-recruiting is an object oriented solution. You never go down to table level for workflows you not even use the hr function modules. You always have to use the service funtions contained in classes like the cl_hrrcf_*_bl ones.
If you change to service functions you are at least not completely wrong based on what you described as your approach. But for a real complete analysis everyone would have to dig into the processes what is usually impossible as they are company secrets.
Best Regards
Roman Weise