on 11-23-2010 2:50 AM
Hi All,
Currently I am developing customize workflow for LSO...
Below are some of my doubts about this.
Hopefully you all can helps or give me some hints...tq.
1. It is possible to create another workflow for course booking for LSO (but through tcode LSO_PSV1) and input the
new workflow in customizing [Tcode : SPRO Go to: Training and Event Management > SAP
Learning Solution >Training Management > Day-to-Day Activities > Approval workflow > Specify Workflow
Settings] eventhough i am also using standard worklow WS12000003 (BOOK) for course booking via
ESS and while cancellation WS12000004 (CANC)....
2. From what I know, Table LSOWF_RUNNING is updated when an employee book a course through ESS.
At what point in the workflow that table LSOWF_RUNNING get updated? And what is table LSOWF_RUNNING
keep actually.. (pending request for course approval ?)
Thanks & best regards,
Ahmad Azlan
Hi Ahmad,
You can copy the standard workflow's WS12000003 and WS12000004 and you can configure the new customized workflow's in the SPRO instead of standard one. It will not make any issues.
Just you need to activate the event linkage in the basic data of the workflow.
Table LSOWF_RUNNING is updated when the workflow is completed. That means Booking request approved by all approvers and the booking was done.
In the ESS you can find the course status in the My activity's tab under the Carer option.
Thanks,
Viji.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ahmad,
Im not sure about the update process for that table.
Please check the method ParticipationCreate of Business object LSO_PARTIC in transaction SWO1.
After all the approval, workflow will call this method and update the Booking data's.
In this method FM LSO_IF_PARTICIPATION_CREATE_C is used to update the data.
Please check the Function module as well.
Thanks,
Viji.
Hi ,
Actualy I have found the secret of it..
To able the custom workflow to update the LSOWF_RUNNING table , we need to add at the workflow
Basic Data > Version Dependent (Current Workflow Version) >Program exit
with class
CL_LSO_WORKITEM_EXIT_LOG.
CL_LSO_WORKITEM_EXIT_LOG will do the works.
Thanks.
Edited by: ahmad azlan on Aug 24, 2011 3:27 AM
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.