Removal of button from std. transaction FV60 in WF ?

[Hilsbos, Margaret A]

Hi Trygve,

I'm not familiar with the specific transaction, but I was wondering if this might be a good use of a "transaction variant". It's been a while since I played with that but it sounds promising. The idea being that you create a transaction variant which allows you to hide, or otherwise change the behavior of, certain fields and buttons in the transaction.  In the workflow you call the variant instead of the standard. I believe you can even create a new transaction code based on the variant. The benefit of using a transaction variant is that you would be only adjusting the user interface, not the underlying functionality (although obviously unwise adjustments to the ui could make the functionality inaccessible to the user).

This is highly conceptual on my part, but I thought I'd throw it out there as a suggestion. 

Another possibility is GuiXT, but I haven't done much with that, and in that case it may be dependent on the user instead of the call from the workflow. 

Transaction variants can be configured in the IMG under General settings > Field Display Characteristics > Configure application transaction fields.

Maybe some other folks here have more experience with transaction variants or GuiXT and can give a better assessment of whether either of those might be appropriate to solve this problem.

Good luck,

Margaret



-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Trygve Leivestad
Sent: Thursday, February 16, 2006 9:09 AM
To: sap-wug at mit.edu
Subject: Re: Removal of button from std. transaction FV60 in WF ?



Seems like it's because if the invoice isn't balanced 0,00  the users can't 
continue the WF, and the people in the central 'invoice handling department' 
get several phone calls because of this, often by the same people over and 
over.

The user's got a manual saying NOT to press the 'Save as complete' button, 
but some of them seems to have a problem remembering it.

I don't know excactly how it was built once upon a time, and being maybe the 
only WF responsible in the world not knowing ABAP, I'll need some help if 
I'm going to try finding it out.

On the other hand, the invoice dept. say that they can live with it as it is 
if it's too complicated fixing it.


Regards
Trygve

>From: "Mike Pokraka" <wug.replies at workflowconnections.com>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: Re: Removal of button from std. transaction FV60 in WF ?
>Date: Thu, 16 Feb 2006 12:35:49 -0000 (GMT)
>
>Hi Trygve,
>That's one of the more bizarre requests I've heard of. Dare I ask why?
>
>The 'Post' button is configurable from FI, but not 'Save as complete'. All
>it does is perform a few extra checks and set a flag if it's technically
>correct and 'postable' (still not guaranteed to post). On that basis I
>would think that nobody at SAP was bored enough to add a feature to let us
>disable it from WF.
>
>Cheers
>Mike
>
>Trygve Leivestad wrote:
> > Hi !
> >
> > We've got a 'home made' WF for invoice handling. (Not made by me)
> > During the WF transaction FV60 is called for parking the invoice.
> >
> > I've got a request to check if it's possible to remove the 'Save as
> > completed' button.
> >
> > I've checked with my FI expert and she will not start tampering with the
> > standard SAP functionality on the reason given for the removal of the
> > button.
> >
> > Is it some way we can handle this directly in the WF ?
> >
> >
> > Regards
> > Trygve
> >
> >
> > _______________________________________________
> > 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


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug