<br><font size=2 face="sans-serif">Srini,</font><br><br><font size=2 face="sans-serif">I haven't seen any responses, so I'll
take a stab at it...</font><br><br><font size=2 face="sans-serif">Regarding your first issue, I would
think that depends on how the transaction is being called. Are you
using one of the standard methods from BUS2028? Have you created
a custom method with a bAPI or BDC call transaction? Is this a decision
dialog that branches to a post method? It isn't clear from your description
of the problem.</font><br><br><font size=2 face="sans-serif">Regarding issue 2, we had a similar
workflow with a similar requirement (except involving invoices instead
of inventory documents) and I used 2 tricks to fufill the requirement.</font><br><font size=2 face="sans-serif">1. In the workflow I made a loop that
checked a container variable (BUS2081-STATUS) after the posting transaction
was called. This status variable holds the actual status of the invoice
(parked, saved, posted, etc....). based on this check, if the invoice
doesn't have a status posted, I loop back and recreat the work item. Otherwise
I fall through and exit the loop. I don't know what attributes or
key fields BUS2028 has, you may need to create a custom background method
that checks the status of the document and sets the flag.</font><br><font size=2 face="sans-serif">2. As parallel branches to the main
workflow, I have created wait steps that wait for events to be generated
from outside the workflow. In my case I wait for the BUS2081.DELETED
and POSTED events. If these wait steps are triggered, the workflow
is bypassed and ended. This way if a user posts a document from outside
the workflow, another user will not have a work item in their inbox telling
them to post this document.</font><br><br><font size=2 face="sans-serif">I hope at least the answers are relevant
to your questions ;-) </font><br><br><font size=2 face="sans-serif">Have a good day!!!!<br></font><font size=4 color=#808000><b> </b></font><p><font size=4 color=#808000><b>Michael McLey</b></font><font size=3 color=#808000><b></b><br>MBUSI - IT Parts & Administration </font><font size=2 color=#808000><br>Mercedes-Benz US International, Inc.</font><font size=3 color=#808000></font><font size=2 color=#808000><br>1 Mercedes Drive</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>Vance, AL 35490</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>PHONE: (205) 462 - 5239</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>EMAIL: michael.mcley@daimler.com</font><font size=3 color=#808000>
</font><br><br><br><table width=100%><tr valign=top><td width=40%><font size=1 face="sans-serif"><b>ootasrinivasreddy@gmail.com</b></font><br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font><p><font size=1 face="sans-serif">05/24/2012 06:35 AM</font><table border><tr valign=top><td bgcolor=white><div align=center><font size=1 face="sans-serif">Please respond to<br>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">To</font></div><td><font size=1 face="sans-serif">sap-wug@mit.edu</font><tr valign=top><td><div align=right><font size=1 face="sans-serif">cc</font></div><td><tr valign=top><td><div align=right><font size=1 face="sans-serif">Subject</font></div><td><font size=1 face="sans-serif">Problem while calling a standard SAP
transaction inside workflow</font></table><br><table><tr valign=top><td><td></table><br></table><br><br><br><font size=2 face="Arial">Hello Experts,</font><p><font size=2 face="Arial"> </font><p><font size=2 face="Arial">I am facing a strange issue in my workflow
development. The workflow will be started after clicking on POST button
in the standard transaction MI04. I have used the standard event
created from the business object BUS2028 for starting the workflow. After
starting the workflow I am calling the standard transaction MI07 in the
very first step which will be sent to the approver. Once the approver clicks
on POST an email will be sent and the document will be posted.</font><p><font size=2 face="Arial"> </font><p><font size=2 face="Arial">Issue 1) When the user manually goes into
the SAP transaction MI07 , opens a document and clicks on back, cancel
or exit buttons. The transaction is working as desired but the same thing
when the same user does from executing the work item the transaction
is not working as desired. A pop-up screen with YES, NO and CANCEL buttons
and also a message whether to SAVE before exit is displayed. Even
though if the user clicks on NO button the document is getting posted.
No idea what is going wrong with the method calling the transaction MI07.</font><p><font size=2 face="Arial">Issue 2) Once the users does this process.
The work item is getting completed. But the requirement is, work item should
be available as the POSTING is not completed. Here how can I put the work
item in ready status after completeion. Once the users executes the work
item the work item is getting disappeared.</font><p><font size=2 face="Arial"> </font><p><font size=2 face="Arial">Where am I doing wrong?</font><font size=3><br><br>-- <br>Thanks and Regards<br>Srini..<br>SAP Technical Consultant<br>+919963307464<br></font><tt><font size=2>_______________________________________________<br>SAP-WUG mailing list<br>SAP-WUG@mit.edu<br>http://mailman.mit.edu/mailman/listinfo/sap-wug<br></font></tt><p><font face="sans-serif"><font face="sans-serif, Arial, Helvetica" size="-1" color="#808080"><br>If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.
<br></br>
</font></font>