How to stop a workflow to trigger for allPARKEDDOCUMENTS(FIPP)?

[Mike Pokraka]

Sorry if I'm being daft here, but I still don't understand the problem:
You want to know how to determine the transaction, you say VBKPF-TCODE
works but want to know another way around this problem... ??

To the second point, I didn't mean the TCODE field isn't reliable, I meant
that the idea of looking at a transaction is unreliable. Why transaction?
So you create a condition for FB50, what's to stop a user from entering
the same document using FV60, FB60, FBV1... or a BAPI, IDOC.... ? Find
another way around whatever it is you're trying to achieve.

Cheers
Mike

Yogesh Chopra wrote:
> Sorry for creating a misunderstanding. I mean to say is. I have already
> created an attribute in ZFIPP with VBKPF-TCODE and checked that
> attribute for transaction FV60 in stared condition. According to my
> understanding it is working fine.
>
> What is another way round for this problem to tackle if we don't have
> TCODE facility?
>
> As you said that you don't find very reliable to depend upon TCODE, is
> there any way around for this?
>
> Thanks and Best Regards
>    Yogesh Chopra
> Yogesh.Chopra at axonglobal.com
>
>
> -----Original Message-----
> From: Mike Pokraka [mailto:wug.replies at workflowconnections.com]
> Sent: Friday, December 09, 2005 3:15 PM
> To: SAP Workflow Users' Group
> Subject: RE: How to stop a workflow to trigger for all PARKED
> DOCUMENTS(FIPP)?
>
> Proof that I'm being discriminated against by Mailman: I received the
> reply before seeing my own post make it to the list!
>
> I don't understand the problem... if you have done that then what
> exactly
> is not working? Completely aside, I don't find looking at a transaction
> very reliable for anything and would avoid it, what's to stop a user
> from
> using a different TCode?
>
> Cheers
> Mike
>
> Yogesh Chopra wrote:
>> Mike: Thanks for your comments. I have already done that. Is there any
>> other way around for this? Suppose if we don't have the facility of
>> TCODE then??
>>
>> Thanks and Best Regards
>>    Yogesh Chopra
>> Yogesh.Chopra at axonglobal.com
>>
>>
>> -----Original Message-----
>> From: Mike Pokraka [mailto:wug.replies at workflowconnections.com]
>> Sent: Friday, December 09, 2005 2:47 PM
>> To: SAP Workflow Users' Group
>> Subject: Re: How to stop a workflow to trigger for all PARKED
> DOCUMENTS
>> (FIPP)?
>>
>> Hi Yogesh,
>> Create a start condition on VBSEG-TCODE (custom DB attribute in a
>> delegated subtype)
>> Cheers
>> Mike
>>
>> Yogesh Chopra wrote:
>>> Hi! Workflow Gurus
>>>
>>> I have created a workflow for PARKED DOCUMENTS with events created,
>>> changed, completed Active. It is working fine. But this workflow
>> should
>>> trigger for ONLY ONE transaction i.e. FV60. It is also getting
>> triggered
>>> for transaction FB50. I have done a customize setting in SPRO to
>> trigger
>>> a workflow by creating a variant and assigning that variant to
> company
>>> code. I know, it will trigger for ALL PARKED documents but how I can
>>> stop this workflow to be triggered from other transaction except
> FV60?
>>> Is there any other way except controlling through DOCUMENT TYPE?
>>>
>>> I will be very thankful for your valuable suggestions.
>>>
>>>
>>> Thanks and Best Regards
>>>    Yogesh Chopra
>>> Yogesh.Chopra at axonglobal.com
>>>
>>>
>>>
>>>
>>>
>>> The content of this email is confidential and for the
>>> addressee only. If you are not the addressee of this
>>> email (or responsible for the delivery of this message
>>> to such person) you may not copy, forward, disclose
>>> or otherwise use it or any part of it in any form
>>> whatsoever. If you have received this email in error
>>> please email the sender by replying to this message
>>> and delete this message thereafter.
>>>
>>> Opinions, conclusions and other information in this
>>> message that do not relate to the official business
>>> of our Company shall be understood as neither
>>> given nor endorsed by it.
>>>
>>> _______________________________________________
>>> SAP-WUG mailing list
>>> SAP-WUG at mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>>
>> The content of this email is confidential and for the
>> addressee only. If you are not the addressee of this
>> email (or responsible for the delivery of this message
>> to such person) you may not copy, forward, disclose
>> or otherwise use it or any part of it in any form
>> whatsoever. If you have received this email in error
>> please email the sender by replying to this message
>> and delete this message thereafter.
>>
>> Opinions, conclusions and other information in this
>> message that do not relate to the official business
>> of our Company shall be understood as neither
>> given nor endorsed by it.
>>
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> The content of this email is confidential and for the
> addressee only. If you are not the addressee of this
> email (or responsible for the delivery of this message
> to such person) you may not copy, forward, disclose
> or otherwise use it or any part of it in any form
> whatsoever. If you have received this email in error
> please email the sender by replying to this message
> and delete this message thereafter.
>
> Opinions, conclusions and other information in this
> message that do not relate to the official business
> of our Company shall be understood as neither
> given nor endorsed by it.
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>