Parking Documents for transaction FV50 FV60 Fv70

[Yogesh Chopra]

Hello! Richard..
 
Thanks a lot for your suggestion. It is working ok now. 
 
Thanks and Best Regards
   Yogesh Chopra
Yogesh.Chopra at axonglobal.com
 
-----Original Message-----
From: Richard Marut [mailto:rvmarut at earthlink.net] 
Sent: Tuesday, January 17, 2006 10:39 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Parking Documents for transaction FV50 FV60 Fv70
 
Yogesh,
 
Business transaction event 00002213, Document Parking: Check for Release
should solve your issue. Read the documentation to see what you need to
do to prevent FV50 and FV70 from requiring a release.
 
Richrad...
 
  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Yogesh Chopra
Sent: Tuesday, January 17, 2006 6:34 AM
To: sap-wug at mit.edu
Subject: Parking Documents for transaction FV50 FV60 Fv70
 
Hello! Every body
 
I have successfully triggered a workflow for parking documents but now
the requirement is, this workflow should not triggered for FV50 & FV70.
I have done some customizing in SPRO. I have created a workflow variant
for parking documents and assigned that variant to company code. Now
when ever user enters a document in FV50 & FV60 post button gets
disappeared.User can not post the document because of spro setting. This
SPRO setting is perfectly ok for FV60. 
 
 My question is :- Is there any way I can restrict post button to
DISAPPEAR only for FV60? 
 
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.
 



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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060118/ec515ce0/attachment.htm