Hello John,<br/>
<br/>
there're two possibilities, why you can loose the consecutive dialog procssing:<br/>
<br/>
A) there's one background step in between the release step and the post step, which is why you loose the dialog processing, because the Workflow runtime can create the next dialog step only after having switched the user to WF-BATCH<br/>
<br/>
B) In the workflow pattern definition you have unchecked the box "Immediate dialog forwarding" (or kinda like that)<br/>
<br/>
To solve A) you'd need to check if you could replace another background step by a synchronous dialog one. In this case you could think of integrate the previous synchronous one into the PostDialog method. I think that I can remember some SAP Standard step to set the "Released" flag on the preliminary document, before it can be posted. This is using the method ReleaseSet and its a synchronous background step which can be transformed how I have described.<br/>
<br/>
To solve B) just check the missing box and try again.<br/>
<br/>
With the very best wishes,<br/>
Florin<br>
<br>
<div name="quote" style='margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;'>
<div style="margin:0 0 10px 0;">
<b>Gesendet:</b> Donnerstag, 21. März 2013 um 16:10 Uhr<br/>
<b>Von:</b> "John Haworth" <jhaworth@csc.com><br/>
<b>An:</b> "SAP Workflow Users' Group" <sap-wug@mit.edu><br/>
<b>Betreff:</b> Re: FIPP method POST
</div>
<div name="quoted-content">
<font face="sans-serif" size="2">Hi</font>
<br/>
<br/><font face="sans-serif" size="2">I added the step as you suggest, but
the task doesnt automatically complete, the workflow returns a task in
my inbox asking me to Post. Any ideas? </font>
<br/>
<br/><font face="sans-serif" size="2">Kind Regards<br/>
<br/>
John Haworth<br/>
SAP PDM<br/>
CSC<br/>
<br/>
Euxton House, Euxton Lane, Chorley, PR7 6FE.<br/>
|Office: +44(0)1257 23 6474|Mobile: +44(0)7921069650| email: jhaworth@csc.com|<a href="http://www.csc.com" target="_blank">www.csc.com</a><br/>
<br/>
=============================================<br/>
Advanced Holiday Notice:<br/>
<br/>
3rd June - 28th June<br/>
<br/>
=============================================<br/>
<br/>
CSC • This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the mistake
in delivery. NOTE: Regardless of content, this e-mail shall not operate
to bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose • CSC Computer Sciences Limited • Registered
Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire, GU11 1PZ,
UK • Registered in England No: 0963578<br/>
</font>
<br/>
<br/>
<br/>
<br/><font color="#5f5f5f" face="sans-serif" size="1">From:
</font><font face="sans-serif" size="1">Florin Wach <florin.wach@gmx.net></font>
<br/><font color="#5f5f5f" face="sans-serif" size="1">To:
</font><font face="sans-serif" size="1">"SAP Workflow
Users' Group" <sap-wug@mit.edu></font>
<br/><font color="#5f5f5f" face="sans-serif" size="1">Cc:
</font><font face="sans-serif" size="1">"SAP Workflow
Users' Group" <sap-wug@mit.edu></font>
<br/><font color="#5f5f5f" face="sans-serif" size="1">Date:
</font><font face="sans-serif" size="1">18/03/2013 20:41</font>
<br/><font color="#5f5f5f" face="sans-serif" size="1">Subject:
</font><font face="sans-serif" size="1">Re: FIPP method
POST</font>
<br/><font color="#5f5f5f" face="sans-serif" size="1">Sent by:
</font><font face="sans-serif" size="1">sap-wug-bounces@mit.edu</font>
<br/>
<hr noshade=""/>
<br/>
<br/>
<br/><font size="3">They'd be exactly the same, as the Containers are just
passed completly!</font>
<br/>
<br/><font size="3">addendum:</font>
<br/>
<br/><font size="3">The containers are passed completly, by using the</font>
<br/><font size="3">swc_call_method self 'Post' ===> container <===.</font>
<br/>
<br/><font size="3">So the same receiving container for the method call to
PostDialog is used as-is for the call to the Post method. Therefore you
need to declare all importing/exporting elements exactly the same way as
the called method does.</font>
<br/>
<br/>
<br/><font size="3">Best wishes,</font>
<br/><font size="3"> Florin</font>
<br/><font size="3"><br/>
Am 18.03.2013 um 15:43 schrieb John Haworth <</font><a href="jhaworth@csc.com" target="_parent"><font color="blue" size="3"><u>jhaworth@csc.com</u></font></a><font size="3">>:<br/>
</font>
<br/><font face="sans-serif" size="2">Hi</font><font size="3"> <br/>
</font><font face="sans-serif" size="2"><br/>
Thanks for that.</font><font size="3"> <br/>
</font><font face="sans-serif" size="2"><br/>
One last question, looking at the binding of the method POST, i.e. would
you use the same binding to the POSTDIALOG method, but how then would you
bind these in / out to the POST method called in the method POSTDIALOG?</font><font size="3">
<br/>
<br/>
<mime-attachment.gif> </font><font face="sans-serif" size="2"><br/>
Kind Regards<br/>
<br/>
John Haworth<br/>
SAP PDM<br/>
CSC<br/>
<br/>
Euxton House, Euxton Lane, Chorley, PR7 6FE.<br/>
|Office: +44(0)1257 23 6474|Mobile: +44(0)7921069650| email: </font><a href="jhaworth@csc.com" target="_parent"><font color="blue" face="sans-serif" size="2"><u>jhaworth@csc.com</u></font></a><font face="sans-serif" size="2">|</font><a href="http://www.csc.com/" target="_blank"><font color="blue" face="sans-serif" size="2"><u>www.csc.com</u></font></a><font face="sans-serif" size="2"><br/>
<br/>
=============================================<br/>
Advanced Holiday Notice:<br/>
<br/>
3rd June - 28th June<br/>
<br/>
=============================================<br/>
<br/>
CSC • This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the mistake
in delivery. NOTE: Regardless of content, this e-mail shall not operate
to bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose • CSC Computer Sciences Limited • Registered
Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire, GU11 1PZ,
UK • Registered in England No: 0963578</font><font size="3"><br/>
<br/>
<br/>
<br/>
</font><font color="#5f5f5f" face="sans-serif" size="1"><br/>
From: </font><font face="sans-serif" size="1">"Florin
Wach" <</font><a href="florin.wach@gmx.net" target="_parent"><font color="blue" face="sans-serif" size="1"><u>florin.wach@gmx.net</u></font></a><font face="sans-serif" size="1">></font><font size="3">
</font><font color="#5f5f5f" face="sans-serif" size="1"><br/>
To: </font><font face="sans-serif" size="1">"SAP
Workflow Users' Group" <</font><a href="sap-wug@mit.edu" target="_parent"><font color="blue" face="sans-serif" size="1"><u>sap-wug@mit.edu</u></font></a><font face="sans-serif" size="1">></font><font size="3">
</font><font color="#5f5f5f" face="sans-serif" size="1"><br/>
Date: </font><font face="sans-serif" size="1">18/03/2013
14:05</font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br/>
Subject: </font><font face="sans-serif" size="1">Re:
FIPP method POST</font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br/>
Sent by: </font><a href="sap-wug-bounces@mit.edu" target="_parent"><font color="blue" face="sans-serif" size="1"><u>sap-wug-bounces@mit.edu</u></font></a><font size="3">
<br/>
</font>
<hr noshade=""/><font size="3"><br/>
<br/>
</font><tt><font size="2"><br/>
Hi John,<br/>
<br/>
yeah, that's how I've designed it: It's a foreground/dialog step, that
is executed right after the final approval was done, still being in the
context of the current user.<br/>
<br/>
The user itself will not notify this kinde of dialog-method-that-is-no-dialog,
unless it runs into an error ;-)<br/>
<br/>
This way you can avoid to hack the change-document table afterwards, as
the underlying called function modules do not allow to pass on a different
user agent name, which would be overwritten here.<br/>
I've also watched for available (implicit) Enhancement options, where a
different user name could be picked up, but there wasn't any that I've
found.<br/>
<br/>
Florin<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
-------- Original-Nachricht --------<br/>
> Datum: Mon, 18 Mar 2013 14:50:46 +0100<br/>
> Von: John Haworth <</font></tt><a href="jhaworth@csc.com" target="_parent"><tt><font color="blue" size="2"><u>jhaworth@csc.com</u></font></tt></a><tt><font size="2">><br/>
> An: "SAP Workflow Users\' Group" <</font></tt><a href="sap-wug@mit.edu" target="_parent"><tt><font color="blue" size="2"><u>sap-wug@mit.edu</u></font></tt></a><tt><font size="2">><br/>
> Betreff: Re: FIPP method POST<br/>
<br/>
> Hi<br/>
> <br/>
> Thanks for that. <br/>
> <br/>
> Could you please just clarify, if this has been defined as a dialog
<br/>
> method, when creating the workflow task that's calls it, would the
task <br/>
> not require a user name as the the receiving agent, (as its a dialog
<br/>
> method, i cant run it as a background task), so its going to try and
send <br/>
> the task to the receiving agent.?<br/>
> <br/>
> Kind Regards<br/>
> <br/>
> John Haworth<br/>
> SAP PDM<br/>
> CSC<br/>
> <br/>
> Euxton House, Euxton Lane, Chorley, PR7 6FE.<br/>
> |Office: +44(0)1257 23 6474|Mobile: +44(0)7921069650| email: <br/>
> </font></tt><a href="jhaworth@csc.com" target="_parent"><tt><font color="blue" size="2"><u>jhaworth@csc.com</u></font></tt></a><tt><font size="2">|</font></tt><a href="http://www.csc.com/" target="_blank"><tt><font color="blue" size="2"><u>www.csc.com</u></font></tt></a><tt><font size="2"><br/>
> <br/>
> =============================================<br/>
> Advanced Holiday Notice:<br/>
> <br/>
> 3rd June - 28th June<br/>
> <br/>
> =============================================<br/>
> <br/>
> CSC • This is a PRIVATE message. If you are not the intended recipient,
<br/>
> please delete without copying and kindly advise us by e-mail of the
<br/>
> mistake in delivery. NOTE: Regardless of content, this e-mail
shall not <br/>
> operate to bind CSC to any order or other contract unless pursuant
to <br/>
> explicit written agreement or government initiative expressly permitting
<br/>
> the use of e-mail for such purpose • CSC Computer Sciences Limited
• <br/>
> Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire,
<br/>
> GU11 1PZ, UK • Registered in England No: 0963578<br/>
> <br/>
> <br/>
> <br/>
> <br/>
> From: "Florin Wach" <</font></tt><a href="florin.wach@gmx.net" target="_parent"><tt><font color="blue" size="2"><u>florin.wach@gmx.net</u></font></tt></a><tt><font size="2">><br/>
> To: "SAP Workflow Users' Group" <</font></tt><a href="sap-wug@mit.edu" target="_parent"><tt><font color="blue" size="2"><u>sap-wug@mit.edu</u></font></tt></a><tt><font size="2">><br/>
> Date: 18/03/2013 11:46<br/>
> Subject: Re: FIPP method POST<br/>
> Sent by: </font></tt><a href="sap-wug-bounces@mit.edu" target="_parent"><tt><font color="blue" size="2"><u>sap-wug-bounces@mit.edu</u></font></tt></a><tt><font size="2"><br/>
> <br/>
> <br/>
> <br/>
> Hello John,<br/>
> <br/>
> I've create a new method PostDialog within a subtype of FIPP and checked
<br/>
> the box "Dialog".<br/>
> Within the method implementation I've basically called the Post method
and<br/>
> passed throught the same exceptions. You may vary here the implementation
<br/>
> as you like, depending on the processing flow of the workflow pattern,
and<br/>
> how you'd like to handle the exception situation, such as "Object
is <br/>
> currently locked by user &2"<br/>
> <br/>
> begin_method postdialog changing container<br/>
> swc_call_method self 'Post' container.<br/>
> CASE sy-subrc.<br/>
> WHEN 0. "Everything was okay
with the call, so nothing to do<br/>
> WHEN 1001. "Serious posting problem<br/>
> exit_return
1001 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.<br/>
> WHEN 1002. "Locked<br/>
> exit_return
1001 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.<br/>
> WHEN OTHERS. "Unknown exception<br/>
> exit_return
9001 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.<br/>
> ENDCASE.<br/>
> end_method.<br/>
> <br/>
> <br/>
> Florin Wach<br/>
> Systems-Integration<br/>
> <br/>
> <br/>
> -------- Original-Nachricht --------<br/>
> > Datum: Mon, 18 Mar 2013 12:24:44 +0100<br/>
> > Von: John Haworth <</font></tt><a href="jhaworth@csc.com" target="_parent"><tt><font color="blue" size="2"><u>jhaworth@csc.com</u></font></tt></a><tt><font size="2">><br/>
> > An: "SAP Workflow Users\' Group" <</font></tt><a href="sap-wug@mit.edu" target="_parent"><tt><font color="blue" size="2"><u>sap-wug@mit.edu</u></font></tt></a><tt><font size="2">><br/>
> > Betreff: FIPP method POST<br/>
> <br/>
> > Hi<br/>
> > <br/>
> > Thanks to all who responded to previous help requests.<br/>
> > <br/>
> > I now have a FI Journal approval workflow that seems to be meeting
<br/>
> > requirements. I have one further question though. The workflow
uses the <br/>
> > POST method of FIPP to post the fi document after it has been
released. <br/>
> > But as the post method is a background method, the users see
that <br/>
> Approved<br/>
> > documents show Posted By WF-BATCH in the header. Is there any
way of <br/>
> > changing this to show the name of the person who released it
instead?<br/>
> > <br/>
> > Kind Regards<br/>
> > <br/>
> > John Haworth<br/>
> > SAP PDM<br/>
> > CSC<br/>
> > <br/>
> > Euxton House, Euxton Lane, Chorley, PR7 6FE.<br/>
> > |Office: +44(0)1257 23 6474|Mobile: +44(0)7921069650| email:
<br/>
> > </font></tt><a href="jhaworth@csc.com" target="_parent"><tt><font color="blue" size="2"><u>jhaworth@csc.com</u></font></tt></a><tt><font size="2">|</font></tt><a href="http://www.csc.com/" target="_blank"><tt><font color="blue" size="2"><u>www.csc.com</u></font></tt></a><tt><font size="2"><br/>
> > <br/>
> > =============================================<br/>
> > Advanced Holiday Notice:<br/>
> > <br/>
> > 3rd June - 28th June<br/>
> > <br/>
> > =============================================<br/>
> > <br/>
> > CSC • This is a PRIVATE message. If you are not the intended<br/>
> recipient, <br/>
> > please delete without copying and kindly advise us by e-mail
of the <br/>
> > mistake in delivery. NOTE: Regardless of content, this
e-mail shall not<br/>
> <br/>
> > operate to bind CSC to any order or other contract unless pursuant
to <br/>
> > explicit written agreement or government initiative expressly
permitting<br/>
> <br/>
> > the use of e-mail for such purpose • CSC Computer Sciences Limited
•<br/>
> > Registered Office: Royal Pavilion, Wellesley Road, Aldershot,
Hampshire,<br/>
> <br/>
> > GU11 1PZ, UK • Registered in England No: 0963578<br/>
> > <br/>
> _______________________________________________<br/>
> SAP-WUG mailing list<br/>
> </font></tt><a href="SAP-WUG@mit.edu" target="_parent"><tt><font color="blue" size="2"><u>SAP-WUG@mit.edu</u></font></tt></a><tt><font size="2"><br/>
> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank"><tt><font color="blue" size="2"><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></tt></a><tt><font size="2"><br/>
> <br/>
> <br/>
_______________________________________________<br/>
SAP-WUG mailing list</font></tt><tt><font color="blue" size="2"><u><br/>
</u></font></tt><a href="SAP-WUG@mit.edu" target="_parent"><tt><font color="blue" size="2"><u>SAP-WUG@mit.edu</u></font></tt></a><font color="blue" size="3"><u><br/>
</u></font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank"><tt><font color="blue" size="2"><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></tt></a><font size="3"><br/>
</font>
<br/><font size="3">_______________________________________________<br/>
SAP-WUG mailing list</font><font color="blue" size="3"><u><br/>
</u></font><a href="SAP-WUG@mit.edu" target="_parent"><font color="blue" size="3"><u>SAP-WUG@mit.edu</u></font></a><font color="blue" size="3"><u><br/>
</u></font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank"><font color="blue" size="3"><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a><tt><font size="2">_______________________________________________<br/>
SAP-WUG mailing list<br/>
SAP-WUG@mit.edu<br/>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank"><tt><font size="2">http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size="2"><br/>
</font></tt>
<br/>
</div>
</div>
<br/>