Workitem not delivered ??
Priya Sharma
priya.sharma at tcs.com
Thu Jun 28 06:03:33 EDT 2007
Hi All,
Thanks a lot for ur responses .
Ruben / Jim,
As suggested by u , I have checked that FV60 is calling this FM -
PP_WF_CREATED n there is no condition specified which is preventing WF to
get trigger .
In IMG also settings are done . In OWBE- I hv entered only WFvariant n
rest things blank.
still executing FV60 doesn't shows event trace or doesn't start the WF.
I have also applied Business transaction event (BTE) approach for solving
my issue. Following is done in BTE :
I have found BTE - 00002213 through FIBF for parking document . I have
made a z Func Module n copied the interface of the 00002213 in that and
coded for triggering event from FV60 by calling FM - 'SWE_EVENT_CREATE'.
I think through BTE things can be done,but still my issue is not resolved.
Anyone , who have some idea abt BTE, Pls advice whether something is
missing frm my end ??
I have still not gone for user-exit , anyhow i think exit - SAPLF051 will
be used here for my purpose ..
I m puzzled .. Any help will be highly appreciated .
Many thanks ..
Regards
Priya Sharma
Tata Consultancy Services
Mailto: priya.sharma at tcs.com
Website: http://www.tcs.com
Ruben Baldassarri <rbaldassarri at yahoo.com.ar>
Sent by: sap-wug-bounces at mit.edu
06/28/2007 10:46 AM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: Workitem not delivered ??
Hi Priya,
First of all, are you sure the event CREATED from FIPP will be raised from
transaction FV60?
I've implemented succesfully a custom workflow based on WS10000051, but in
my case the same event was triggered by transaction F-63.
Or maybe you are missing some customizing step.
The function module that triggers the event for parked documents is
PP_WF_CREATED, you can set a breakpoint at the beginning of it and check
if trx FV60 is calling the FM. If so, you can check if there is a
condition within it that prevents the event to be raised.
In the IMG, the steps I had to perform were the following:
- Transaction OBWA (Create Workflow Variant for Parking Documents) -> As
described by Jim.
- Transaction OBWJ (Assign Co.Code to a Workflow Variant for Parking
Documents) -> As described by Jim
- Transaction OBWD (Assign Release Approval Path for Parking Documents):
Create entries with WF variants and document types (I think I didn't need
to fill release group or approval path)
- Transaction OBWE (Assign Release Approval Procedure for Parking
Documents): Create entry for WF variant with approval path empty.
Hope this helps...
Regards,
Ruben
At 12:31 p.m. 27/06/2007, you wrote:
Prima,
The problem here seems to be the fact that you are not getting the event
raised from the FV60 transaction. As Jim seems to insinuate, there is
probably some part of configuration that can be set up to ensure that the
event is raised. The other alternative, which he does touch on, is to
raise the event yourself in a user exit. I am not sure what exits exist
for transaction FV60, but I can more or less guarantee there will be at
least one.
It does seem that as soon as you can get the correct event raised,
everything else is in place to allow the workflow to be triggered.
I hope that this helps you find a solution for this.
With Best Wishes
Adrian!
From: sap-wug-bounces at mit.edu [ mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sauceman Jr, James E (Jim)
Sent: 27 June 2007 13:00
To: Priya Sharma
Cc: SAP Workflow Users' Group
Subject: RE: Workitem not delivered ??
Priya,
It is an amount. The F1 Help for this attribute says the following:
Amount from Which a Release Approval Procedure Is To Run
Amount from which a release or completion of the document is required
within document parking. The larger of the debit or credit amounts of the
parked document is the decisive factor.
Use
The sample workflow WS00400004 is delivered as standard for document
completion. For the amount release, sample workflows WS10000051 and
WS00400032 are delivered as standard.
If a document release or completion is required for the parked document,
when you save the document the workflow event CREATED is triggered for
object type FIPP. In the workflow Customizing, you have to link the event
with the workflows specified within the maintenance for event linkage.
Regards,
Jim Sauceman ...................... sauceman at tennessee.edu
The University of Tennessee
From: Priya Sharma [ mailto:priya.sharma at tcs.com]
Sent: Wednesday, June 27, 2007 7:39 AM
To: Sauceman Jr, James E (Jim)
Cc: SAP Workflow Users' Group
Subject: RE: Workitem not delivered ??
Jim,
In OBWA :
Release from should have wat entry ?? I mean in ur case 0.01 represents
wat ?
may b this is to be corrected for my scenario.
Pls advice.
Rgds
Priya Sharma
Tata Consultancy Services
Mailto: priya.sharma at tcs.com
Website: http://www.tcs.com
"Sauceman Jr, James E (Jim)" <sauceman at utk.edu>
06/27/2007 04:53 PM
To
"Priya Sharma" <priya.sharma at tcs.com>, "SAP Workflow Users' Group"
<sap-wug at mit.edu>
cc
Subject
RE: Workitem not delivered ??
Priya,
As some have suggested, you might want to investigate the CMOD approach. I
have some old notes on work I did in that area, but because it did not
seem to fit your situation, I was hesitant to mention it. Based on SAP
Note 85293 - FIPP: Suppress event CREATED I implemented an enhancement
(SAPLF051) in CMOD. For Component EXIT_SAPLF051_002, I have the following
include that lists the Parked Document types for which we want to start
the workflow and raises the NOT_RELEVANT event otherwise.
*----------------------------------------------------------------------*
* INCLUDE ZXF09U05 *
*----------------------------------------------------------------------*
if T_vbkpf-blart <> 'ZC'
and T_vbkpf-blart <> 'ZD'
and T_vbkpf-blart <> 'IL'
and T_vbkpf-blart <> 'KG'
and T_vbkpf-blart <> 'KN'
and T_vbkpf-blart <> 'SA'.
RAISE NOT_RELEVANT.
endif.
Again, it seems that you have a different situation, but maybe this will
help lead you to the solution.
One more thing, in OBWA, in the Preliminary posting release block, I have
the following:
Posting release box checked
Release from 0.01
Subworkflow WSnnnnnnnn (my custom workflow)
I do not remember having to do anything else, but it has been 6 years
since I set this one up.
Hope this helps,
Jim Sauceman ...................... sauceman at tennessee.edu
The University of Tennessee
From: Priya Sharma [ mailto:priya.sharma at tcs.com]
Sent: Wednesday, June 27, 2007 3:23 AM
To: SAP Workflow Users' Group
Cc: Sauceman Jr, James E (Jim); Sauceman Jr, James E (Jim)
Subject: RE: Workitem not delivered ??
Hi Jim,
Many Thanks for the response to query .
I have created a variant 4 my WF using OBWA n assigned Company code using
OBWJ.
still , event trace is not shown in SWEL whenever I execute FV60.
Am I missing something else ?
Pls advice .
Rgds
Priya Sharma
Tata Consultancy Services
Mailto: priya.sharma at tcs.com
Website: http://www.tcs.com
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: Workitem not delivered ??
Priya,
Check the configuration described below:
1. Create a Workflow Variant for Parking Documents using
transaction OBWA. The default is WS1000055 so you must change this by
creating your own variant if you have created a custom workflow.
2. Assign a Company Code to your Workflow Variant for Parking
Documents using transaction OBWJ.
In the IMG, these steps can be found under Financial Accountingà Financial
Accounting Global Settingsà Document à Document Parking
Regards,
Jim Sauceman ...................... sauceman at tennessee.edu
The University of Tennessee
From: sap-wug-bounces at mit.edu [ mailto:sap-wug-bounces at mit.edu] On Behalf
Of Priya Sharma
Sent: Tuesday, June 26, 2007 10:57 AM
To: SAP Workflow Users' Group
Cc: SAP Workflow Users' Group; sap-wug-bounces at mit.edu
Subject: RE: Workitem not delivered ??
Hi Adrian ,
I have checked in SWB_COND , no conditions are specified for my WF.
I am puzzled for one thing :
whenever I have used SWUE for testing event , event trace is shown in SWEL
but executing tcode- FV60 doesn't show any event trace in SWEL.
n as far as my knowledge, event trace should be shown at the execution of
FV60 also.
Am i missing something ??
Please suggest .
Rgds
Priya Sharma
Mailto: priya.sharma at tcs.com
Website: http://www.tcs.com
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: Workitem not delivered ??
Priya,
Just a thought, have you checked transaction SWB_COND to ensure that there
is not a condition that stops your workflow from running?
The event trace, however, should give you the information on whether the
event is linked to a workflow or not. However, if you have used SWUE, this
sounds as if it is.
Another option is that you need to refresh the buffers ? try transaction
SWU_OBUF. Although this happens once a day (midnight server time usually),
this transaction allows you to do this whenever you want. If you have made
all changes in one day, this can sometimes help.
Hope some of this helps?.
Adrian
From: sap-wug-bounces at mit.edu [ mailto:sap-wug-bounces at mit.edu] On Behalf
Of Priya Sharma
Sent: 26 June 2007 14:13
To: SAP Workflow Users' Group
Subject: Workitem not delivered ??
Hiii All,
Pls advice me on the following :
I have created a WF, whose triggering event is "created" n Bus obj is
"FIPP" which should get trigger when an user saves data in tcode-FV60.
My WF is running fine if:
1) I test it through SWDD.
2) I test it through SWUE .
3) Event is traced in SWEL.
4) "Type linkage active " and my WF in "Receiver type "is shown in
SWETYPV.
But still , when an user saves data in FV60, WF is not getting triggered
i.e work item is not delivered in the responsible agent's inbox .
Can someone suggest anything which is missed frm my end n which is still
to be done or checked.
Any help will be highly appreciated.
Rgds
Priya Sharma
mailto: priya.sharma at tcs.com
Website: http://www.tcs.com
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
ForwardSourceID:NT00006AE6
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070628/28a4768a/attachment.htm
More information about the SAP-WUG
mailing list