on 03-16-2019 6:46 AM
Hi Experts,
i am using below code in report to trigger a workflow ( I have hard coded everyhting for testing purpose ). I see the workflow is triggering because I can see entries in table SWW_WI2OBJ. But the problem is the INSTID and TYPE ID fields are not showing correct values. TYPE ID is always CL_SWF_UTL_EVT_IDENTIFIER and CATID is CL. INSTID has some random value other than what I am passing in "instid" paramter.
I have crated a subtype (ZBUS2015) for BUS2015 and delegation done. created a new event called POSTED in ZBUS2015. Am I missing something?
CALL FUNCTION 'SAP_WAPI_CREATE_EVENT_EXTENDED'
EXPORTING
catid = 'BO'
typeid = 'BUS2015'
instid = '0180000423'
EVENT = 'POSTED'
* COMMIT_WORK = 'X'
* EVENT_LANGUAGE = SY-LANGU
* LANGUAGE = SY-LANGU
* USER = SY-UNAME
* IFS_XML_CONTAINER =
* IMPORTING
* RETURN_CODE =
* EVENT_ID =
* TABLES
* INPUT_CONTAINER =
* MESSAGE_LINES =
* MESSAGE_STRUCT =
HI,
I found the solution. open the workflow template from PFTC, go to "triggering events" tab. select the event linkage entry and click on binding. There we have to map "_EVT_OBJECT" to "_Adhoc_Objects" element. This will create entry in SWW_WI2OBJ table.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Sankara,
I am using ZCALSS instead of BO, in this case how the values will update in table SWW_WI2OBJ? Currently I am getting GUID in INSTD and CL_SWF_UTL_EVT_IDENTIFIER in TYPEID
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Are you sure , the entries you showed created for your entries only.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
I would recommend the folowing:
- Make sure these records are really the result of your code (you can do it by turning on Event trace - transaction SWELS )
- Try to look at the workitems mentioned in these records (wi_id field) by means of Workflow Log - the records might make sense when you see them in context
- Try starting yor workflow manually ( transaction SWUS )? It is recommended to first make it work when started directly, and then proceed to more complex way of triggering (through an event)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.