FM SWW_WI_CREATE_VIA_EVENT

in this FM,
what is the parameter RECTYPE,OBJTYPE,OBJKEY
i have a business object BUS2038, for a workflow WS90000092, what is the object key here? Workitem?
RECTYPE is defined as two character code concatenated with the 8 digit number, so WS90000080 wud be the RECTYPE, so would OBJKEY be?

Hello,
OBJTYPE will be your business object type (BUS2038 in this case) and the OBJKEY will be the key field defined for the Business Object Type BUS2038. Hope this clarifies.
Regards,
Venkata Phani Prasad K

Similar Messages

ZBUS2032 not shown in workflow and status in SWEL- no receiver entered

I am trying to change an existing workflow(This one has the standard BO- BUS2032 linked). Now I am trying to link the same workflow to a custom BO(ZBUS2032) copied from BUS2032. This custom BO is generated, released, delegated. I have maintained the default values as
Method = DISPLAY and
Attribute = SALESDOCUMENT
Created an entry in SWE2 for ZWBUS2032 with
Object type = ZWBUS2032
EVENT = CREATED
RECEIVER = WS90000014
Receiver call = FM
Receiver FM = SWW_WI_CREATE_VIA_EVENT
checked the linkage activated checkbox and left the rest AS-IS
In the workflow side,
In the task screen- I added the task number that has (ZBUS2032 and the new method), specified the triggering events and binded, event is green. When I click on Define binding autom. it shows
WIOBJECT_ID = &ZBUS203&
In the actual event
I added the Object type to ZBUS2032 and the event as CREATED, clicked on start condition and specified the SALES document type condition but it doesn't go green.
When I click on the binding, on the right hand side of the new window where the workflow parameters are there, it still shows BUS2032 instead of ZBUS2032
No errors, I activated. When I hit the test, it still shows BUS2032.
When I do the process through front end and check SWEL, it says No receiver entered.
I am new to Workflow. Kindly please advice.
Regards,
Kiran

Hi,
What are you trying to do with the ZBUS2032?
IIf you create a new task that should call a new method (in ZBUS2032), if you enter BUS2032 as object type and then select the method, are you able to see the new method in the selection list? If yes, that would mean that you have delegated the ZBUS2032 properly. (=You have kind of extended the usage of the standard BUS2032 with the new Z-version).
You could also add some new attributes to your ZBUS2032. If you are able to see them in workflow builder or in the workflow log, this would also mean that the delegation has been done properly. (I just hope that you did the subtype in a way that Rick tried to describe).
In general I hope that you have tested your new functionality (method or attribute) directly in SWO1. If it works there, it should then work in the workflow too. I would be interested to know how you came into conclusion that ZBUS2032 is not working as it should? Do you see an error or what?
Regards,
Karri

Workflow error in fork step, process control, wait event

I am using fork step in workflow which has 2 parallel branches. In 1st branch i have a user decision step followed by a task for posting PO document in case of approval. In the 2nd branch of fork step I have a wait step to wait for an event followed by the same task for posting document with a process control step after that in the end to cancel the workitem(workitem generated by user decision step in the 1st branch of fork). I created the event by using a custom BOR object.
After the fork step is triggered, i have both a wait event running and workitem generated. When i raise the wait event from SWUE by entering the event, object key etc it works fine i.e., the workitem in the other branch is set of logically deleted and workflow ends.
But if the wait event is triggered from the program i.e., using FM SWW_WI_CREATE_VIA_EVENT, both get an error message in workflow log(SWIA). The message is: Error when executing the binding between work item 000000XXXXXX and flow item 000000XXXXXX where workitem number is the workitem id of the posting document task and flow item id is the workflow parent id

hi,
message is self explanatory.
Activate the event trace SWELS, then do the event with SWUE and within your program (als please use SAP_WAPI function modules).
Now compare the 2 events in SWEL to see what the differences are .
Kind regards, Rob Dielemans

Runtime Error - Order Status

Hi friends,
Pls check below the runtime error description ,which I'm getting when releasing the Order - PM.
Pls advise, What happ'd and how to fix it.
Regards
Sankar.
Runtime Errors MESSAGE_TYPE_X
Date and Time 31.03.2008 13:16:08
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_250
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_250"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
"IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "SILDEV"
Network address...... "192.168.255.70"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x IA64 Level 3"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "SILDEV"
Database type..... "MSSQL"
Database name..... "DEV"
Database user ID.. "dev"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 3 2008 03:55:37"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 150
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 16384
MM Used. 4889280
MM Free. 3487552
User and Transaction
Client.............. 250
User................ "PM5CHARL"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059"
Program............. "CL_SWF_RUN_WIM_LOCAL==========CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "DEV"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........."C0A8FF46013847F096C00004"
Outbound Queue Name.." "
Client.............. 250
User................ "PM5CHARL"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_SHIP"
Call Destination.... "NONE"
Source Server....... "SILDEV_DEV_00"
Source IP Address... "192.168.255.70"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "CL_SWF_RUN_WIM_LOCAL==========CP" -
in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 10
of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
Source Code Extract
Line SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2 DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4 TRY.
5 IF me->m_int_state-system_user IS INITIAL.
6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7 ENDIF.
8 re_user = me->m_int_state-system_user.
9 CATCH cx_swf_run_wim INTO l_excp.
>>>>> MESSAGE ID l_excp->t100_msg-msgid
11 TYPE 'X'
12 NUMBER l_excp->t100_msg-msgno
13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15 ENDTRY.
16
17 ENDMETHOD. "
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 2
SY-TABIX 1
SY-DBCNT 0
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE CPIC and RFC Control
SY-MSGTY X
SY-MSGID SWF_RUN
SY-MSGNO 617
SY-MSGV1 WORKFLOW_LOCAL_250
SY-MSGV2 RFC_READ_DESTINATION_TYPE
SY-MSGV3 DESTINATION_NOT_EXIST
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080331
SY-UZEIT 131608
SY-XPROG SAPMSSY1
SY-XFORM XAB_READ
Active Calls/Events
No. Ty. Program Include Line
Name
26 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM088 10
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
25 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM00J 5
CL_SWF_UTL_MAIL=>GET_OWNER
24 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM002 37
CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
23 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0IE 38
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
22 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM021 7
CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
21 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM01V 12
CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
20 METHOD CL_SWF_RUN_WIM_STATE_FLOW=====CP CL_SWF_RUN_WIM_STATE_FLOW=====CM004 2
CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION
19 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM09A 72
CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL
18 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0H3 16
CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS
17 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM04P 7
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS
16 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM011 12
CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR
15 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A 81
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT
14 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R 93
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT
13 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM008 144
CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION
12 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM016 42
CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM
11 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM002 33
CL_SWF_RUN_WORKFLOW_START=>EXECUTE
10 FUNCTION SAPLSWW_SRV LSWW_SRVU13 135
SWW_WI_CREATE_VIA_EVENT_INTERN
9 FUNCTION SAPLSWW_SRV LSWW_SRVU11 64
SWW_WI_CREATE_VIA_EVENT
8 FORM SAPLSWW_SRV LSWW_SRVU11 1
SWW_WI_CREATE_VIA_EVENT
7 FORM SAPMSSY1 SAPMSSY1 271
XAB_RUN_DRIVER
6 FUNCTION SAPLSXAB LSXABU01 9
RFC_RUN_XAB_DRIVER
5 FUNCTION SAPLERFC LERFCU01 115
ARFC_EXECUTE
4 FUNCTION SAPLERFC LERFCU02 386
ARFC_DEST_SHIP
3 FORM SAPLERFC LERFCU02 1
ARFC_DEST_SHIP
2 FORM SAPMSSY1 SAPMSSY1 85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 26 Ty. METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
RE_USER
222222222222
000000000000
000000000000
000000000000
L_EXCP
B0004000
90006000
SY-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
L_EXCP->T100_MSG-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
SWFCO_WIM_WI_FORWARD
SWW_WI_FORWARD
555554544554542222222222222222
377F79F6F271240000000000000000
000000000000000000000000000000
000000000000000000000000000000
SY-MSGNO
617
333
617
000
000
L_EXCP->T100_MSG+40(6)
617
333
617
000
000
SY-MSGV1
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+48(100)
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+148(100)
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+248(100)
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+348(100)
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No. 25 Ty. METHOD
Name CL_SWF_UTL_MAIL=>GET_OWNER
RE_OWNER
%_DUMMY$$
2222
0000
0000
0000
ME->M_OWNER
%_VIASELSCR
0
4
ME
A0005000
E0001000
L_WORKITEM
60009000
3000C000
SY-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 24 Ty. METHOD
Name CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
EX_SENT_TO_ALL
2
0
0
0
EX_MAIL_OBJECT
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME
A0005000
E0001000
OBJECT_HD_CHANGE-ACNAM
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222222222222222222222222222
377F79F4930C19F6F2FD19C0000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
OBJPARB
Table IT_7581x570
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB
Table reference: 224
TABH+ 0(20) = E06D6DEFF9060000000000000000000000000000
TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF
TABH+ 40(16) = 042A0200600B000010000000C1248401
store = 0xE06D6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 224 (0xE0000000)
label = 758 (0xF6020000)
fill = 1 (0x01000000)
leng = 570 (0x3A020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000046
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x80095FEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 540 (0x1C020000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
OBJECT_HD_CHANGE-OBJDES
Workflow 405090 set to status ERROR
56766667233333327672762776777245545222222222222222
7F2B6CF70405090035404F03414530522F2000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_FSREG_001
OBJCONT
Table IT_7609x510
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT
Table reference: 225
TABH+ 0(20) = 106F6DEFF9060000000000000000000000000000
TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF
TABH+ 40(16) = 042A0200300B000010000000C1248401
store = 0x106F6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 225 (0xE1000000)
label = 760 (0xF8020000)
fill = 9 (0x09000000)
leng = 510 (0xFE010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000045
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x402D5FEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 541 (0x1D020000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
OWNER
222222222222
000000000000
000000000000
000000000000
SENDER
222222222222
000000000000
000000000000
000000000000
SY-SUBRC
0
0000
0000
SWFCO_MAIL_ERROR_NOTIFY
0002
3333
0002
0000
0000
OBJECT_HD_CHANGE
E ERRORMESSAGEWorkflow 405090 set to status ERROR 00000000000000 F F S
4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OBJECT_TYPE
RAW
545
217
000
000
SWFCO_OBJTYPE_BOR
BO
44
2F
00
00
No. 23 Ty. METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
LT_AGENTS
Table IT_7521x28
\CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
Table reference: 207
TABH+ 0(20) = 806B6DEFF9060000000000000000000000000000
TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF
TABH+ 40(16) = 04180100E006000010000000C1248401
store = 0x806B6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 207 (0xCF000000)
label = 752 (0xF0020000)
fill = 1 (0x01000000)
leng = 28 (0x1C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000022
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xA0696DEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 537 (0x19020000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SYST-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28)
WS20000014
55333333332222
73200000140000
00000000000000
00000000000000
SY-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
FUNCNAME
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222
377F79F4930C19F6F2FD19C0000000
000000000000000000000000000000
000000000000000000000000000000
SWFCO_WI_REMOTE
R
5
2
0
0
PARAMETER-NAME
WI_ID
54544
79F94
00000
00000
SWFCO_CALLBACK_AGENTS
CALLBACKAGENTS
54444444454444552222222222222222
F31CC213BF175E430000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
PARAMETER-VALUE
000000405090
333333333333
000000405090
000000000000
000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID
000000405090
333333333333
000000405090
000000000000
000000000000
PARAMETER
807020C0
7080A050
00000000
00100010
LS_MAILOBJ
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Hi Sankar,
Clearly RFC destination WORKFLOW_LOCAL_250 doesnot exist. But please don't create it directly using Sm59.
Log into client 250 and go to transaction SWU3. Here you will get option for creating RFC destination making use of user WF-BATCH. In case there is workflow expert in your project take his help.
Once this is done this dump should not come.
Regards.
Ruchit.

Problem of trigger event for Customer master.

Hi all,
I created one object type in KNA1. because i want to use task instead of the workflow.
after i executed the customer master creation , i got this error during the execution."Dereferencing of the NULL reference".
if anybody want information, please let me know.
Regards,
Luke

Hi
"At the beginning, i am using the Receiver Function module is SWW_WI_CREATE_VIA_EVENT.
after i change to "SAP_WAPI_CREATE_EVENT" but got error too."
Can you tell us where are you calling this FM (is it via Enhancement option or badi or exit) to trigger the event?
Just leave the Receiver FM as same as in SWE2 and make sure Linkage Actiavted check box is checked
"i can't do the buiding between &EVT_OBJECT& and &WI_OBJECT_ID&. because it is not same business object.
for our workflow object, it references to class is developed by me.
As suggested by Rick, you could make use of FM or as per blog, you could use class to trigger your custom class's event. Then you need to have binding at task level (PFTC)
&EVT_OBJECT& --> &WI_OBJECT_ID&.
Vinoth

RUNTIME Error - User Status for Order release

HI Friends,
Pls go thru the run-time error description,which i'm getting on Order release.Pls reply,.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          31.03.2008 13:16:08
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_250
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_250"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
"IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "SILDEV"
Network address...... "192.168.255.70"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x IA64 Level 3"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "SILDEV"
Database type..... "MSSQL"
Database name..... "DEV"
Database user ID.. "dev"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 3 2008 03:55:37"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 150
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 16384
MM Used. 4889280
MM Free. 3487552
User and Transaction
Client.............. 250
User................ "PM5CHARL"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059"
Program............. "CL_SWF_RUN_WIM_LOCAL==========CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "DEV"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........."C0A8FF46013847F096C00004"
Outbound Queue Name.." "
Client.............. 250
User................ "PM5CHARL"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_SHIP"
Call Destination.... "NONE"
Source Server....... "SILDEV_DEV_00"
Source IP Address... "192.168.255.70"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "CL_SWF_RUN_WIM_LOCAL==========CP" -
in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 10
of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
Source Code Extract
Line
SourceCde
1
METHOD if_swf_run_wim_utl_internal~get_system_user .
2
DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4
TRY.
5
IF me->m_int_state-system_user IS INITIAL.
6
me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7
ENDIF.
8
re_user = me->m_int_state-system_user.
9
CATCH cx_swf_run_wim INTO l_excp.
>>>>>
MESSAGE ID     l_excp->t100_msg-msgid
11
TYPE   'X'
12
NUMBER l_excp->t100_msg-msgno
13
WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14
l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15
ENDTRY.
16
17
ENDMETHOD.                    "
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
X
SY-MSGID
SWF_RUN
SY-MSGNO
617
SY-MSGV1
WORKFLOW_LOCAL_250
SY-MSGV2
RFC_READ_DESTINATION_TYPE
SY-MSGV3
DESTINATION_NOT_EXIST
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080331
SY-UZEIT
131608
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
26 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM088    10
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
25 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM00J     5
CL_SWF_UTL_MAIL=>GET_OWNER
24 METHOD       CL_SWF_UTL_MAIL===============CP    CL_SWF_UTL_MAIL===============CM002    37
CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
23 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0IE    38
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
22 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM021     7
CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
21 METHOD       CL_SWF_RUN_WIM_STATE==========CP    CL_SWF_RUN_WIM_STATE==========CM01V    12
CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
20 METHOD       CL_SWF_RUN_WIM_STATE_FLOW=====CP    CL_SWF_RUN_WIM_STATE_FLOW=====CM004     2
CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION
19 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM09A    72
CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL
18 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM0H3    16
CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS
17 METHOD       CL_SWF_RUN_WIM_LOCAL==========CP    CL_SWF_RUN_WIM_LOCAL==========CM04P     7
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS
16 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM011    12
CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR
15 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A    81
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT
14 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R    93
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT
13 METHOD       CL_SWF_RUN_WIM_EXECUTION_MGR==CP    CL_SWF_RUN_WIM_EXECUTION_MGR==CM008   144
CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION
12 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM016    42
CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM
11 METHOD       CL_SWF_RUN_WORKFLOW_START=====CP    CL_SWF_RUN_WORKFLOW_START=====CM002    33
CL_SWF_RUN_WORKFLOW_START=>EXECUTE
10 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU13                           135
SWW_WI_CREATE_VIA_EVENT_INTERN
9 FUNCTION     SAPLSWW_SRV                         LSWW_SRVU11                            64
SWW_WI_CREATE_VIA_EVENT
8 FORM         SAPLSWW_SRV                         LSWW_SRVU11                             1
SWW_WI_CREATE_VIA_EVENT
7 FORM         SAPMSSY1                            SAPMSSY1                              271
XAB_RUN_DRIVER
6 FUNCTION     SAPLSXAB                            LSXABU01                                9
RFC_RUN_XAB_DRIVER
5 FUNCTION     SAPLERFC                            LERFCU01                              115
ARFC_EXECUTE
4 FUNCTION     SAPLERFC                            LERFCU02                              386
ARFC_DEST_SHIP
3 FORM         SAPLERFC                            LERFCU02                                1
ARFC_DEST_SHIP
2 FORM         SAPMSSY1                            SAPMSSY1                               85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.      26 Ty.          METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
RE_USER
222222222222
000000000000
000000000000
000000000000
L_EXCP
B0004000
90006000
SY-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
L_EXCP->T100_MSG-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
SWFCO_WIM_WI_FORWARD
SWW_WI_FORWARD
555554544554542222222222222222
377F79F6F271240000000000000000
000000000000000000000000000000
000000000000000000000000000000
SY-MSGNO
617
333
617
000
000
L_EXCP->T100_MSG+40(6)
617
333
617
000
000
SY-MSGV1
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+48(100)
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+148(100)
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+248(100)
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+348(100)
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No.      25 Ty.          METHOD
Name CL_SWF_UTL_MAIL=>GET_OWNER
RE_OWNER
%_DUMMY$$
2222
0000
0000
0000
ME->M_OWNER
%_VIASELSCR
0
4
ME
A0005000
E0001000
L_WORKITEM
60009000
3000C000
SY-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No.      24 Ty.          METHOD
Name CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
EX_SENT_TO_ALL
2
0
0
0
EX_MAIL_OBJECT
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME
A0005000
E0001000
OBJECT_HD_CHANGE-ACNAM
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222222222222222222222222222
377F79F4930C19F6F2FD19C0000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
OBJPARB
Table IT_758[1x570]
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB
Table reference: 224
TABH+ 0(20) = E06D6DEFF9060000000000000000000000000000
TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF
TABH+ 40(16) = 042A0200600B000010000000C1248401
store        = 0xE06D6DEFF9060000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 224   (0xE0000000)
label        = 758   (0xF6020000)
fill         = 1     (0x01000000)
leng         = 570   (0x3A020000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000046
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x80095FEFF9060000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 540   (0x1C020000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
OBJECT_HD_CHANGE-OBJDES
Workflow 405090 set to status ERROR
56766667233333327672762776777245545222222222222222
7F2B6CF70405090035404F03414530522F2000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_FSREG_001
OBJCONT
Table IT_760[9x510]
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT
Table reference: 225
TABH+ 0(20) = 106F6DEFF9060000000000000000000000000000
TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF
TABH+ 40(16) = 042A0200300B000010000000C1248401
store        = 0x106F6DEFF9060000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 225   (0xE1000000)
label        = 760   (0xF8020000)
fill         = 9     (0x09000000)
leng         = 510   (0xFE010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000045
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x402D5FEFF9060000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 541   (0x1D020000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
OWNER
222222222222
000000000000
000000000000
000000000000
SENDER
222222222222
000000000000
000000000000
000000000000
SY-SUBRC
0
0000
0000
SWFCO_MAIL_ERROR_NOTIFY
0002
3333
0002
0000
0000
OBJECT_HD_CHANGE
E          ERRORMESSAGEWorkflow 405090 set to status ERROR                00000000000000 F F S
4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OBJECT_TYPE
RAW
545
217
000
000
SWFCO_OBJTYPE_BOR
BO
44
2F
00
00
No.      23 Ty.          METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
LT_AGENTS
Table IT_752[1x28]
\CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
Table reference: 207
TABH+ 0(20) = 806B6DEFF9060000000000000000000000000000
TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF
TABH+ 40(16) = 04180100E006000010000000C1248401
store        = 0x806B6DEFF9060000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 207   (0xCF000000)
label        = 752   (0xF0020000)
fill         = 1     (0x01000000)
leng         = 28    (0x1C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000022
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xA0696DEFF9060000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 537   (0x19020000)
refCount     = 1     (0x01000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 2     (0x02000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
SYST-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28)
WS20000014
55333333332222
73200000140000
00000000000000
00000000000000
SY-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
FUNCNAME
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222
377F79F4930C19F6F2FD19C0000000
000000000000000000000000000000
000000000000000000000000000000
SWFCO_WI_REMOTE
R
5
2
0
0
PARAMETER-NAME
WI_ID
54544
79F94
00000
00000
SWFCO_CALLBACK_AGENTS
CALLBACKAGENTS
54444444454444552222222222222222
F31CC213BF175E430000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
PARAMETER-VALUE
000000405090
333333333333
000000405090
000000000000
000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID
000000405090
333333333333
000000405090
000000000000
000000000000
PARAMETER
807020C0
7080A050
00000000
00100010
LS_MAILOBJ
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
60009000
3000C000
SWFCO_WORKITEM_OBJECT
_WORKITEM
55454454422222222222222222222222
F7F2B945D00000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
No.      22 Ty.          METHOD
Name CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
SWFCO_WORKITEM_OBJECT
_WORKITEM
55454454422222222222222222222222
F7F2B945D00000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No.      21 Ty.          METHOD
Name CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
IM_STATE_ACTIONS
Table IT_279[30x152]
\CLASS=CL_SWF_RUN_WIM_STATE_FLOW\DATA=M_STATE_ACTIONS
Table reference: 112
TABH+ 0(20) = 90CE53EFF9060000B04D6BEFF906000000000000
TABH+ 20(20) = 70000000170100001E0000009800000090010000
TABH+ 40(16) = 049A01007004000010000000C9248001
store        = 0x90CE53EFF9060000
ext1         = 0xB04D6BEFF9060000
shmId        = 0     (0x00000000)
id           = 112   (0x70000000)
label        = 279   (0x17010000)
fill         = 30    (0x1E000000)
leng         = 152   (0x98000000)
loop         = 400   (0x90010000)
xtyp         = TYPE#000009
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 1     (ItIndexLinear)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xF0C453EFF9060000
pgHook       = 0xF0CE53EFF9060000
idxPtr       = 0x50E253EFF9060000
shmTabhSet   = 0x0000000000000000
id           = 207   (0xCF000000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 48    (0x30000000)
lineAlloc    = 48    (0x30000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x204C6BEFF9060000
collHook     = 0x0000000000000000
ext2         = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
SWFCO_WI_NO_DEADLINE
0000
3333
0000
0000
0000
L_OBJ
A0005000
D0002000
ME
A0005000
D0002000
ME->IF_SWF_RUN_WIM_STATE~NEW_STATUS
ERROR
455452222222
522F20000000
000000000000
000000000000
<%_L003>
ERROR
455452222222
522F20000000
000000000000
000000000000
SY-REPID
CL_SWF_RUN_WIM_STATE==========CP
4455545554554455545433333333334522222222
3CF376F25EF79DF34145DDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
<%_L004>
F
4
6
0
0
<STATE_ACTION>
FERROR       01DYN_SEND_ERROR_REPAIR_MAIL
4455452222222334545544454554555454455444422222222222222222222222222222222222
6522F200000000149EF35E4F522F2F250192FD19C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
<%_L002>
<%_L002>-WI_STAT
SYST-REPID
CL_SWF_RUN_WIM_STATE==========CP
4455545554554455545433333333334522222222
3CF376F25EF79DF34145DDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SWFCO_WI_STATUS_WILD_CARD
222222222222
A00000000000
000000000000
000000000000
<%_L002>-WI_TYPE
<STATE_ACTION>-METHOD
DYN_SEND_ERROR_REPAIR_MAIL
4545544454554555454455444422222222222222222222222222222222222
49EF35E4F522F2F250192FD19C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
0
0
LV_EXCP
F0000000
F0000000
No.      20 Ty.          METHOD
Name CL_SWF_RUN_WIM_STATE_FLOW=>

Hello,
Get help from your abaper on this.
Vinay

Vendor payments release workflow!!!

Hi all
Can somebody explain to me how we setup standard workflow so that all vendor invoices greater than 100.000 can be blocked for payment automatically & released by some other user?
I tried to give the document type "KR" to the workflow variant & tried to do invoicing for the vendor. But I do not how I could release that blocked invoice...Is there any specific tcode or I have to go to the proposal & change the blocked reason from P to 'space'.
Thanks for all your time....

Hello Morgan,
Payment Release Process
Purpose
For each workflow variant, you can specify the amount from which a payment release should be triggered.
You can differentiate between one, two, and three-level release. This enables between one and three people to be involved in the release procedure, thus supporting both dual and triple control.
Prerequisites
You have made the following settings in Customizing:
Release approval procedure
(document type and amount for each workflow variant)
Assign persons with release authorization
In order to do this, you must first create release approval groups that can be entered in the customer and vendor master records.
Depending on these criteria and the release level, you can assign release authorizations in the form of organizational objects (job, position, organizational unit) in Customizing. If you do not define any criteria (such as release approval groups), the system takes the initial value of these criteria when the payment program is run. For example, if the system was unable to determine the release approval group, the release approval procedure and the employees with release authorization are determined on the basis of release approval group zero.
Process Flow
Minimum requirements:
The payment release function must be activated.
The relevant document type must be defined.
An item containing the following specifications must be created for employees with release authorization:
Workflow variant
Initial release approval path
Initial level
Maximum amount
Employees with release authorization can also be determined and assigned by user exits at each stage of the release approval procedure.
Result
If, when the payment run is made, the system could not determine an employee with release authorization, then it sends a message to the inbox of every person who has been assigned the task "payment release". Only after all these people have released the payment will the payment block be removed.
If a line item is refused for release, it is forwarded to the clerk who entered it for correction. After the document has been changed, the payment release procedure begins again. If changing the line items necessitates further actions, these must be defined within the Workflow component. The event CHANGED has been preconfigured for this purpose in the standard workflow model. If you run this event, the system assumes that the line item was rejected for payment. However, the item is NOT forwarded for correction to the clerk who entered it.
If an item is cleared before it is released, the payment release procedure is terminated (event CLEARED).
===========================================================
Workflow settings: The standard system contains several workflow models for payment release: One workflow framework (WS00400012) and three sub-workflows. In Customizing for Financial Accounting, you can specify which sub-workflow should be used when the workflow framework is run. You can also enter your own sub-workflows. They must however send and receive the same data from the workflow framework as the workflow models do.
You can use the standard sub-workflows (WS00400011, WS00400021, and WS00400022) to carry out a one, two, or three-level payment release procedure. If you require more than three release levels, you can copy the workflow models, enhance them and then enter the enhanced workflow definition in Customizing for Financial Accounting.
Event Linkage for the Event CREATED
If an amount requires a payment release, the event CREATED is triggered when a document is posted.
In this case, you must go into the workflow framework in the Workflow Workbench and enter the event linkage for this event, as described below:
Data for Event Linkage
Object type
BSEG
Event
CREATED
Receiver type
WS00400012
Receiver module
SWW_WI_CREATE_VIA_EVENT
Check Function
Receiver type
FM (function module)
Global
X
Enabled
X
Standard Tasks for the Event CREATED
The standard system contains two standard tasks that are triggered from the workflow mailbox and used in the workflow models.
Payment release (line item)
Change (line item)
Creating and Assigning Organizational Objects for Payment Release
You must assign organizational objects (organizational units, jobs, positions) to the standard tasks. These organizational objects can be created either in Personnel Planning and Development, via the Workflow Workbench, or in Customizing for Financial Accounting (assignment of release authorization to employees).
When you create organizational units, you must assign them to jobs or positions. You can then assign users to the positions.
Examples for assignments:
Organizational unit X < Position Y < User
Organizational unit X < Job Y < Position Z < User
In Customizing for Financial Accounting, you can assign organizational objects to the workflow variant, the release approval path, the release approval level, and the amount. These objects then release the amount depending on these criteria.
The organizational objects for payment release defined in Customizing for Financial Accounting are automatically assigned in the background to the standard payment release task (TS00407862).
The organizational objects for changing line items after they have been rejected for payment must be assigned to the standard task "Change line item" (TS00407864), either in Personnel Planning and Development, or via the Workflow Workbench. Alternatively, you can define the task as a general task (Additional data -> Classification).
Changing Line Items
The workflow models described above all contain a pre-configured event (CHANGED), which triggers other events in the same fashion as a rejection does. This event can be triggered by change documents. You must define it via the Workflow Workbench.
Hope I had been able to help you. Please assign points.
Rgds
Manish

Urgent!! 'Screen output without connection to user'

Hi,
Our requirement is to send an e-mail in the outlook when a workflow is triggered.
On trigerring, the WF is started but in TRXn SWEL the RFC status says <i><b>'Screen output without connection to user'</b></i>. In transaction SM58, i get the status 'Screen output without connection to user' against the function module 'SWW_WI_CREATE_VIA_EVENT' . I have seen in the previous threads that pop-up could be one of the reasons. But i havnt used any pop-ups. The WF consist of only one step 'Send mail' in which we give the users email ID. Can any one help me on this issue?
P.S: I was sucessful in sending mail to outlook previously, but suddenly show this type of error. Is it because of the change in configuration which our basis team do?
Thanks in Advance
S.P.K

did u solve this problem if yes how did u resolve this...i am getting the same error...

Workflow not getting triggered from MM01

Hi,
I understand there is a similar post but the solution is not so clear there.
I wish to trigger a workflow whenever a material is created using tcode MM01.
For which i am using BUS1001. (In the header data > start events tab > BO/BUS1001/CREATED binding exists and activated)
whenever i am creating a material using MM01, and check the trace in SWEL i am getting the following info:
BUS1001006     VIEWCREATED     25.03.2011     13:00:12          @AI@     No receiver entered
BUS1001006     CREATED     25.03.2011     13:00:12     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
Can someone please help where to enter the receiver.
regards
abhishek

Hi sanju,
I have created the event as per your suggestions but the workflow is not yet triggered from mm01.
the event stack trace is as follows :-
BUS1001     CREATED     28.03.2011     08:28:42     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT
BUS1001006     VIEWCREATED     28.03.2011     08:33:03     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
BUS1001006     CREATED     28.03.2011     08:33:03     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT
BUS1001     CREATED     28.03.2011     08:33:03     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT
Linkage is activated in SWE2 and the receiver FM is SWW_WI_CREATE_VIA_EVENT.
still unable to get the workflow triggered.
Secondly as per SAP suggestion the BO BUS1001006 should be used for std material master. But while i enter BUS1001006 no such methods are available in F4. (refer atttachment)
I have checked in the BOR and i see that BUS1001006 is released and active.

Problem in triggering of workflow

Hi All,
We have custom events assigned to bus2104.In Event linkage transaction SWW_WI_CREATE_VIA_EVENT is passed to Receiver Function Module and "Linkage Activated" = 'X'.
In quality server after approval request (t.code IMA1N) is created and status of approval is changed to "Request for POP inclusion" the workflow is triggered. But in testing workflow is not triggering.
In test system if i am manully executing the workflow using SWUE t.code & selecting "trigger receive FM synchronus" then only the workflow is triggered.
If i execute workflow manully through SWUE & unselecting " trigger receive FM synchronus" the workflow is not triggered.
Could you plz let me know why the worklfow is not triggered in qualtiy system automaticly.
*Please do not use words like "Urgent" in the forum.Hence i edit the message as per the forum guidelines. Edited by: Saujanya GN on May 12, 2008 5:41 AM

Hi
Thanks for your response.
The settings in SWEL are identical in Quality & test system.But if i am manually running the workflow fro SWUE with "tigger receiver function module synchronouly" = X
in workflow graph its shown that the workflow is triggered through event but in SWEL data is not available.
Regards
Deepthi

FICO-Invoice Parking and approval; Unable to complete some Config steps

FICO-Invoice Parking and approval; Unable to complete some Config steps
I am using standard WF: WS10000051 (SAP template) in Accounts payable to get triggered for Invoice Parking-Approval and Posting.
One of the steps mentioned at help.sap.com is below;
1. Data for Event Linkage
Object type     FIPP
Event     CREATED
Receiver type     WS10000051
Receiver module     SWW_WI_CREATE_VIA_EVENT
2. Check Function
Receiver type (function module)
Global     X
Enabled     X
I could get to 1. Data for Event Linkage which is T Code SWETYPV but could not find 2. Check Function.
Where do I set the parameters for : 2. Check Function in SAP
The help file link is
http://help.sap.com/saphelp_erp2005/helpdata/en/01/a9ceb5455711d182b40000e829fbfe/content.htm
Regards
Nilabh

You dont need to assign the Check function module.
Check function module is used to prevent the workflow from triggering if the checks written in the function fail.
For eg. check if the invoice amount is GT 500. If yes trigger workflow else dont.
-Kiran

PO workflosw giving error .

In case of PO workflow .
the workflow get triggered according to the release strategy .
but in my its getting only for one agent .
for others we are not getting the release code for the SWE_EVENT_CREATE at the time the workflow is triggered for the second code in ME21n.
can anyone suggest why this might be happening .
Everything else is fine no problem with release strategy .
Thanks in advance .
Naval Bhatt

can you check in SWEL are there any entries like this ?
BUS2012 RELEASESTEPCREATED WS20000075   SWW_WI_CREATE_VIA_EVENT
BUS2012 RELEASESTEPCREATED WS20000075   SWW_WI_CREATE_VIA_EVENT
                           Feedback after error
                           Deactivated
Regards,
PR.

Queries regarding the workflow

Hi guys
I have created a workflow definition in SWDD and creted a object in SWO1 with an event. this event i linked to the workflow in tepe linkage table also. I tried to trigger the event from the abap report program .I have used standard FM SWE_EVENT_CREATE. I have added the FM SWW_WI_CREATE_VIA_EVENT as the receiver FM in the event.
But still when i run the report i can not see this event in event trace. When i debugged the program i have found that the Event id is generated by the FM SWE_EVENT_CREATE.
Do i have to add anything to the program or anything to be added to the event. PLease let me know
thanks
sankar

hi
i am giving my code here:
REPORT ZEMPWORKFLOW.
PARAMETERS : empid type ZEMPID obligatory,
             empname type ZEMPNAME obligatory,
             empDOB type ZEMPDOB obligatory,
             empcont type ZEMPCOUNTRY obligatory.
INCLUDE <cntn01>.
DATA: objtype LIKE swetypecou-objtype,
      event   LIKE swetypecou-event,
      objkey LIKE sweinstcou-objkey,
      eventid LIKE swedumevid-evtid,
      creator LIKE swhactor.
objtype = 'ZEMPLOYEE'.
event = 'UPDATE'.
clear objkey.
objkey(10) = empid.
swc_container z_container.
swc_create_container z_container.
swc_set_element z_container 'empid' empid.
swc_set_element z_container 'empname' empname.
swc_set_element z_container 'empdob' empDOB.
             CALL FUNCTION 'SWE_EVENT_CREATE'
               EXPORTING
                 OBJTYPE                       = objtype
                 OBJKEY                        = objkey
                 EVENT                         = event
             IMPORTING
                EVENT_ID                      = eventid
             TABLES
                EVENT_CONTAINER               = z_container
             EXCEPTIONS
                OBJTYPE_NOT_FOUND             = 1
               OTHERS                        = 2.
IF sy-subrc = 0.
COMMIT WORK.
WRITE:/ 'Your event was created.'.
ELSE.
WRITE:/ 'There was an error creating the event.'.
ENDIF.
please tell me if you need any more info.
thanks
sankar

No reciever entered for MM po rel workflow

Dear all,
I am trying to create MM po release workflow.
I have customised settings in SPRO
I switched on trace swels.
It shows following log.
QCYBUS2012 CREATED                           03.06.2009 12:24:31    No receiver entered
BUS2011           QUOTATIONCREATED     03.06.2009 12:24:31       No receiver entered
BUS2012           RELEASESTEPCREATED     03.06.2009 12:24:31    WS20000075      Event put in queue
FREBUS2012 CREATED                     03.06.2009 12:24:31      No receiver entered
Please help to Resolve.
with best of Regards,
Gaurav sood

After changes in SWE2
i got mail in SBWP
as following:
Error processing following event linkage:
BUS2012 RELEASESTEPCREATED TS20000166
Following error occurred:
WL 610
BUS2012
RELEASESTEPCREATED
TS20000166
Message text:
Event BUS2012 RELEASESTEPCREATED for task TS20000166 not defined as start/end event
Event container appended as attachment.
Event linkage with errors deactivated.
Also Event trace Shows ythis messsage
CREATED                              03.06.2009   14:44:11   No receiver entered
QUOTATIONCREATED       03.06.2009   14:44:11   No receiver entered
RELEASESTEPCREATED 03.06.2009   14:44:11 TS20000166     SWW_WI_CREATE_VIA_EVENT
RELEASESTEPCREATED 03.06.2009    14:44:16 TS20000166     Feedback after error
RELEASESTEPCREATED 03.06.2009    14:44:16 TS20000166     Deactivated
CREATED                             03.06.2009    14:44:11                       No receiver entered
Please help to resolve this
Regards,
Gaurav sood

Passing container vlaues using program

hi all,
i am triggering workflow using events. in the program i am using the following code as
DATA : V_OBJKEY LIKE SWEINSTCOU-OBJKEY,
T_CONTAINER LIKE SWCONT OCCURS 0 WITH HEADER LINE,
wa_cont like line of t_container,
V_ID TYPE SWELOG-RECID,
I0008 TYPE P0008,
IT_0008 TYPE TABLE OF ZPA0008,
WA_0008 LIKE LINE OF IT_0008,
WA_PA0008 TYPE PA0008.
wa_cont-element = 'EMPNAME'.
wa_cont-type = 'PERSNO'.
wa_cont-ELEMLENGTH = '8'.
wa_cont-value = '12345'.
append wa_cont to t_container.
CALL FUNCTION 'SWW_WI_CREATE_VIA_EVENT'
EXPORTING
EVENT = 'CHANGED'
RECTYPE = 'WS90000014'
OBJTYPE = 'BASICPAY'
OBJKEY = V_OBJKEY
IMPORTING
REC_ID = V_ID
TABLES
EVENT_CONTAINER = T_CONTAINER
EXCEPTIONS
READ_FAILED = 1
CREATE_FAILED = 2
OTHERS = 3.
here i am able to trigger the work flow but not able to pass the container values to the workflow.
kindly help me.
thanks,
sirisha

Hi
INCLUDE <CNTN01>. " <----- Include this
DATA : V_OBJKEY LIKE SWEINSTCOU-OBJKEY,
T_CONTAINER LIKE SWCONT OCCURS 0 WITH HEADER LINE,
wa_cont like line of t_container,
V_ID TYPE SWELOG-RECID,
I0008 TYPE P0008,
IT_0008 TYPE TABLE OF ZPA0008,
WA_0008 LIKE LINE OF IT_0008,
WA_PA0008 TYPE PA0008.
SWC_CREATE_CONTAINER t_container " <---- Include this statement.
SWC_SET_ELEMENT t_container 'EMPNAME' '12345'.
wa_cont-element = 'EMPNAME'. " <-- Replace the below 4 lines of code with the above line
wa_cont-type = 'PERSNO'.
wa_cont-ELEMLENGTH = '8'.
wa_cont-value = '12345'.
append wa_cont to t_container.
CALL FUNCTION 'SWW_WI_CREATE_VIA_EVENT' " <----- Repalce this with SWE_EVENT_CREATE
EXPORTING
EVENT = 'CHANGED'
RECTYPE = 'WS90000014'
OBJTYPE = 'BASICPAY'
OBJKEY = V_OBJKEY
IMPORTING
REC_ID = V_ID
TABLES
EVENT_CONTAINER = T_CONTAINER
EXCEPTIONS
READ_FAILED = 1
CREATE_FAILED = 2
OTHERS = 3.
COMMIT WORK <---- INclude this statement too after callin SWE_EVENT_CONTAINER
But make sure that you already have the container element EMPNAME in the workflow container before raising the event..
Edited by: Pavan Bhamidipati on Aug 30, 2010 3:51 PM

FM SWW_WI_CREATE_VIA_EVENT

Similar Messages

Maybe you are looking for