Workitem not delivered - Solved
Priya Sharma
priya.sharma at tcs.com
Fri Jun 29 02:57:08 EDT 2007
Thanks All , for the extended help provided .
My issue got resolved .
Long live WUG !!
Rgds
Priya
Ruben Baldassarri <rbaldassarri at yahoo.com.ar>
Sent by: sap-wug-bounces at mit.edu
06/28/2007 08:09 PM
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 ??
Priya,
Please, try this:
- Add entries in Trx OBWD with:
Workflow Variant: The one you created with OBWA
Type: The type of accounting document (one entry for
each type)
Release group: Leave this field empty
Approval path: 0001
Then, in Trx OBW create an entry with:
Workflow Variant: The one you created with OBWA
Approval path: 0001
Amount to: The highest value you can (e.g.
99,999,999,999.99)
Release level: Number of approvals needed for
release (e.g. 2)
Amount Release Subworkflow: The subworkflow used for
releasing parked documents.
Regards,
Ruben
--- Priya Sharma <priya.sharma at tcs.com> escribió:
> 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
>
=== message truncated ===>
_______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
__________________________________________________
Preguntá. Respondé. Descubrí.
Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).
¡Probalo ya!
http://www.yahoo.com.ar/respuestas
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
ForwardSourceID:NT00006BB2
=====-----=====-----=====
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/20070629/eefdffc1/attachment.htm
More information about the SAP-WUG
mailing list