<br><font size=2 face="sans-serif">Hi Florin,</font>
<br>
<br><font size=2 face="sans-serif">Alright, thanks! I just wanted to know
how others deal with that kind of daily requirements...</font>
<br>
<br><font size=2 face="sans-serif">br chris</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Florin Wach"
<florin.wach@gmx.net></b> </font>
<br><font size=1 face="sans-serif">Gesendet von: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">08.10.2007 14:55</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Bitte antworten an<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">An</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Kopie</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Thema</font></div>
<td><font size=1 face="sans-serif">Re: Antwort: Workflow for Creating G/L
account via FSP0</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hello Christian,<br>
<br>
I would vote for the second solution to approve a form separatly, and after
the final approval has been given, you could use a background batch-input
to actually post the approved data into the transaction.<br>
This way I had implemented a WF to approve vendor-master-data and it worked
fine.<br>
<br>
Best regards,<br>
Florin<br>
<br>
<br>
-------- Original-Nachricht --------<br>
> Datum: Mon, 8 Oct 2007 14:49:57 +0200<br>
> Von: "Christian Wallner" <C.Wallner@ats.net><br>
> An: "SAP Workflow Users\' Group" <sap-wug@mit.edu><br>
> Betreff: Antwort: Workflow for Creating G/L account via FSP0<br>
<br>
> Hi!<br>
> <br>
> No one any ideas?<br>
> <br>
> br<br>
> chris<br>
> <br>
> <br>
> <br>
> <br>
> "Christian Wallner" <C.Wallner@ats.net> <br>
> Gesendet von: sap-wug-bounces@mit.edu<br>
> 02.10.2007 09:31<br>
> Bitte antworten an<br>
> "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> <br>
> <br>
> An<br>
> sap-wug@mit.edu<br>
> Kopie<br>
> <br>
> Thema<br>
> Workflow for Creating G/L account via FSP0<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Greetings! <br>
> <br>
> I am looking for any ideas on how to implement the following workflow
(not<br>
> having found anything in standard...): <br>
> <br>
> Version 1: (IMHO unlikely to be implement because not possible/too
much <br>
> effort) <br>
> User wants to create a new GL account in chart of accounts ZZ. Therefor
he<br>
> starts transaction FSP0, presses create and fills out all necessary
data. <br>
> When he presses "save" the account actually isn't saved
but goes to a HoD <br>
> for approvement. when he approves->create account, if not ->
back to <br>
> creator. <br>
> I think its not possible (without bigger modifications which I want
to <br>
> avoid!!) to not save the account but to "park" it until
its approved. <br>
> <br>
> Version 2: <br>
> I create a workflow via start form, the user fills out all necessary
<br>
> fields, the data go to HoD for approvement etc...just like any other
<br>
> simple approvement wf. <br>
> <br>
> Any ideas on how to implement this consistently? <br>
> <br>
> br from austria, <br>
> chris_______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> <br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
</font></tt>
<br>