Screen for Workflow starting transaction

[Dart, Jocelyn]

Hi Ram,
Using SWUG gets rid of all the effort of creating the
transaction and keeps it nice and standard so that
it can be included in more general lists like transaction SWUI
and general object services.
 
It contains an include .....E1000 where you can add your
own custom code.  You can use the subroutine EXIT_PBO_END_1000
to change the INVISIBLE flag of the relevant table control
on.  That way the table should disappear from view.
If you're not sure what a table control is I suggest you
look up the online ABAP help on the CONTROLS ... TYPE TABLEVIEW  statement.
Similarly you can
use this subroutine to set the invisible flags of the buttons and boxes that
you no longer need.
 
If you really want to create a simple screen you could always
create your own program then call the workflow using the
WAPI i.e. SAP_WAPI_START_SIMPLE or better still
raise an event using SAP_WAPI_CREATE_EVENT.
But don't underestimate the effort involved in creating your
own transaction.
 
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
 jocelyn.dart at sap.com
 +61 412 390 267
 +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Ramkumar, Govindasamy [mailto:ramkumarg at m1.com.sg]
Sent: Friday, 2 August 2002 12:20 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Screen for Workflow starting transaction
Importance: High
 
 
Hi Workflowers,
 
While creating starting transaction for a workflow using transaction SWUG,
the default screen generates fields for "Adhoc Objects and Attached Objects
in the table format".
 
Is it possible to hide these fields?  If so,  how to do it?
 
Should the starting transaction screen be generated using SWUG or can I
create a simple screen using screen painter and attach it to the Workflow
transaction? What is the transaction to attach the screen created using
Screen Painter?
 
Thanks in advance for your help.
 
Best Regards
Ram