Start Condition
Nat 4 Govender
ngovender4 at toyota.co.za
Wed Aug 3 03:53:40 EDT 2005
Hi Mark,
Thanks for your quick and helpful response.
Regards
Nat Govender
Toyota South Africa
IT - SAP - SAP Workflow
Internal Ext. : 32645
Direct Line : +27 31 910 2645
Fax : +27 31 902 9633
E-mail : ngovender4 at toyota.co.za
=========================================================
Remember not to forget that which you do not need to know
=========================================================
Mark Pyc
<mark.pyc at gmail.c
om> To
Sent by: "SAP Workflow Users' Group"
sap-wug-bounces at m <sap-wug at mit.edu>
it.edu cc
Subject
2005/08/03 09:30 Re: Start Condition
AM
Please respond to
"SAP Workflow
Users' Group"
<sap-wug at mit.edu>
G'day Nat,
Unfortunately you can't see the reason for the check FM failure. I've
seen responses from the SAP developers explaining that it's just not
possible from their point of view. You can debug the CFM by raising
the event using SWUE and choosing the flag 'Start receiver syncron',
but this may not be of use to you if you can't reliably make the CFM
raise the exception.
As for why it would fail one day and not the next..?
Does it fail the first time and then work subsequently? This could
indicate timing issues with DB updates.
Does it fail when triggered by one user and not another - auths of course.
Is this a one off issue or is happening with any regularity?
Sorry to be more helpful.
Have fun,
Mark
On 8/3/05, Nat 4 Govender <ngovender4 at toyota.co.za> wrote:
>
>
> Hi All,
>
> Below are details regarding the Business Object the Start Condition and
the
> Trace Event Details.
> I have 2 problems
> 1. What transaction can I see the details of "Check FM ends with
> exception"
> 2. How can the start condition work one date and not the other
day
> for the same business object.
>
> Any help will be appreciated.
>
> Details of Object
> BUS2013 5500018915
> Attributes
> GOODSMOVEMENT 0 Entries
> MATERIALOBJECT 00701-YZE30-1
> OBJECTTYPE BUS2013
> PURCHASINGDOCUMENT 5500018915
> PURCHASINGGROUP 017
> PURCHORGANIZATION TSAP
> RELEASEGROUP
> RELEASEINDICATOR
> RELEASESTATUS
> RELEASESTRATEGY
> SA_CREATION_DATE 29.02.2004
> SA_DATE_EXIST Y
> SUBJECTTORELEASE
> VENDORBILLINGDOC 0 Entries
> VENDOR_MASTER 0000201402
>
> Details of Start Condition
> Start Condition
> For Both Change And Create Events
> If Pur Schd Agreement.SA_Date_Exist = 'Y' Start workflow: Pur.
Schd.
> Agreement Notification W/F
>
> Trace Event Details on 01/08/2005
> Event Data
> Event instance ID 25761277
> Object type BUS2013
> Key 5500018915
> Event CHANGED
> User BANG
> Main program SAPLSWUS
> Date 01.08.2005
> Time 13:59:47
> UTC 20,050,801,115,948
>
> Receiver Data
> Receiver type WS90100118
> Receiver ID 000034933226
> Receiver FM SWW_WI_CREATE_VIA_EVENT
> Receiver type FM
> Check function SWB_CHECK_FB_START_COND_EVAL
> Status Receiver started correctly
> RFC status
>
>
>
> Trace Event Details on 03/08/2005
> Event Data
> Event instance ID 25761545
> Object type BUS2013
> Key 5500018915
> Event CHANGED
> User BANG
> Main program SAPLSWUS
> Date 03.08.2005
> Time 07:23:30
> UTC 20,050,803,052,330
>
> Receiver Data
> Receiver type WS90100118
> Receiver ID
> Receiver FM SWW_WI_CREATE_VIA_EVENT
> Receiver type FM
> Check function SWB_CHECK_FB_START_COND_EVAL
> Status Check FM ends with exception
> RFC status
>
>
> Regards
>
> Nat Govender
> Toyota South Africa
> IT - SAP - SAP Workflow
> Internal Ext. : 32645
> Direct Line : +27 31 910 2645
> Fax : +27 31 902 9633
> E-mail : ngovender4 at toyota.co.za
> =========================================================
> Remember not to forget that which you do not need to know
> =========================================================
>
> This message is a privileged and private communication and may be read,
> copied and used only by
> the intended recipient(s). If you are not an intended recipient, please
let
> us know by return email.
> Please then delete the message and do not disclose its contents to any
> person. Neither the sender nor
> Toyota South Africa Motors accepts any liability whatsoever as a result
of
> the further dissemination
> of this message. Whilst all reasonable steps are taken to avoid
corruption
> of data or information,
> we do not accept any liability should such corruption occur.
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
This message is a privileged and private communication and may be read, copied and used only by
the intended recipient(s). If you are not an intended recipient, please let us know by return email.
Please then delete the message and do not disclose its contents to any person. Neither the sender nor
Toyota South Africa Motors accepts any liability whatsoever as a result of the further dissemination
of this message. Whilst all reasonable steps are taken to avoid corruption of data or information,
we do not accept any liability should such corruption occur.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050803/85462be1/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050803/85462be1/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic06868.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050803/85462be1/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050803/85462be1/attachment-0002.gif
More information about the SAP-WUG
mailing list