Skip to Content
author's profile photo Former Member
Former Member

LSO Workflow : Workflow Trigger Based on course type & Table LSOWF_RUNNING

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 23, 2010 at 03:05 AM

    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.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      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 will do the works.


      Edited by: ahmad azlan on Aug 24, 2011 3:27 AM

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.