HELP NEEDED: Use a new record for a customized table as a workflow trigger

Question

Hi SAP Workflow Gurus,
Good day!
One of our requirements is to have the creation of a new record in a custom database table trigger a workflow. I read and followed the steps as indicated in this link
http://www.****************/Tutorials/Workflow/Table/events.htm
As a summary, here is what I did:
1. Created a subroutine for the custom table ZPA2003 for the create event
2. Defined this event as a trigger for the custom workflow WS90000019
3. Maintained and activated the event linkage via SWETYPV
Basically I tried following the instructions indicated on the link
Note that the entries for the custom table are created via a function module.
Now during testing of the workflow, the system was able to complete the notification message. However, when I triggered the event via creation of the entry in the custom db table nothing happened
1. Is there a way to debug/find out whether the link between the subroutine in the table and event itself are connected?
2. I also tried running the event trace to check the activities executed but found nothing.
Can you guys help me check on what I may have missed out?
Regards,

Answer 1

Hi All,
Basically these are the requirements for the work schedule substitution:
1. Employee enters the request via ESS (custom portal transaction)
2. Upon saving of the entry (request) in a custom  table, this should trigger the workflow at the backend
3. The Manager should then receive a work item in his Universal Worklist at the MSS side of the portal
4. Upon clicking on the work item, a new screen will pop up showing the work schedule substitution details as well as an interface which will allow him to enter his/her usage decision
5. Depending on the decision, the workflow must execute the necessary notifications as well as changes in the custom and PA2003 tables
Now, we have accomplished step 1 and I am currently in the process for step 2. Now I have some queries:
1. For the Manager to view and approve the substitution details, I used two methods for each process (view and approve) since our ABAPer mentioned that this cannot be done in 1 function module. Is there a way to simplify this step or is it really valid that they need to be executed in 2 different methods?
2. As per our ABAPer, function Modules only import and export variables; they do not have the facility of say having tags on the details being displayed. Hence, if the details are 10001 (Employee Number), 10/20/2011 (Start Date), 10/25/2011 (End Date) the output would be 10001, 10/20/2011, 10/25/2011. Is there a way within the function module (or dynpro interface) to show it like this: Employee Number: 10001
                           Start Date: 10/20/2011
                           End Date: 10/25/2011
3.  Speaking of dynpro applications, do I need to still develop one to allow the Manager to view and approve/reject the request via the MSS portal upon accessing the work item via the UWL? How would the work item go about calling the dynpro application? or is this even possible?
It would have been easier if the facility would not pass through workflows since it will be just direct web dynpro/ABAP calls. Having to include it as a work item in the UWL puts a certain twist to it
Your inputs are well-appreciated.
Regards,