ESS Workflow 10000015 Approve request for changing address thru Portal ESS

Question

Hi Experts,
We want to implement ESS workflow 01000015 u201Cchange (infotype 0006) Address will be blocking until approved/rejected by Administratoru201D. The workflow is trigger OK from R3, user creates a new address and IT0006 is blocking till administrator approve or reject.
What we want now is to trigger this workflow from Portal, but here is the problem:
1.-  I do not see any option (button) for creating a new address from Portal iView, what else is missing??? I believe creating new address from Portal could trigger this workflow, but I am not sureu2026
2.- If the first option does not work I would like to trigger this workflow by the event u201CChangeu201D, so I need to edit the address. From R3 is blocking IT0006 OK, but from portal is not blocking the address at allu2026 What else is missing??? I do not know if this could be an issue from R3 or Portalu2026.
We already check u201CNote 495971 - Workflow 01000015 is not triggered when changing addressu201D and workflow is working ok only from R3.
Regardsu2026..
David Cortes

Answer 1

Hi Swamy,
I am a little confused of you requirement. The scenario here is that Person A (Any person using ESS) must not change any of his/her own personal data until Person B Approve/Reject the new Data. For example: if a user A want to change his/her address, personal data etc. must be approve or reject for another person B. This is a validation that most of the companies want to have in order to validate this information. Employees may change their personal data, but how HR area validates if this new information is real or not...  One way to verify this new information is a validation for a Person B who will be to approve or reject this information. Now if you do not have this scenario I believe you will not have to do this implementation class because ESS do not have this scenario. The standard ESS functionality is available for change any data without validation and this should be working right now on your Enterprise Portal.
If you want to have a validation for a third User, Person B, you may check these points:
1. Edit 2. New Permanent address
Edit - Will change the record irrespective of dates. This will modify the current record which is valid as of today.
New Permanent address - This will create a new record effective today and previous record will be delimited.
If I use lock functionality in Edit scenario, then in the portal it will dispaly previous record which is not the correct data.
For 2nd case, this will insert the new record, so Lock may work in this case. I will check this.
I believe you will work most of the time with "Edit" button. If Person A edit address, the new register will be created and locked in PA30 Infotype  6 until person B Approve/Reject. How Person B knows if someone has edit his/her address?? You may achieve this using Universal Work List and notification. You may have to create a task for person B with email notification, so person B will be enter into Portal and check his/her new task from the UWL. This task will be ITS UI front end and from here person B decide if approve or reject. If Person B approve, the new register will be unlocked and replace the last one (Also in Portal). If person B reject, the register blocked will be gone and the last one remains.
This should work for any infotype . Check only the type of event generated for any of them in order to trigger the workflow.
Do you have any idea how to achieve this for Personal details where the Lock/Unlock functionality is not available.
Standard ESS works without any lock/unlock functionality. remove the current workflow if you have used any.
Regards
David Corté