<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">They'd be exactly the same, as the Containers are just passed completly!</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">addendum:</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">The containers are passed completly, by using the</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">swc_call_method self 'Post' ===> container <===.</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">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.</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Best wishes,</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"> Florin</span></div><div style="-webkit-text-size-adjust: auto; "><br>Am 18.03.2013 um 15:43 schrieb John Haworth <<a href="mailto:jhaworth@csc.com">jhaworth@csc.com</a>>:<br><br></div><blockquote type="cite" style="-webkit-text-size-adjust: auto; "><div><font size="2" face="sans-serif">Hi</font>
<br>
<br><font size="2" face="sans-serif">Thanks for that.</font>
<br>
<br><font size="2" face="sans-serif">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>
<br>
<br><mime-attachment.gif>
<br><font size="2" face="sans-serif">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: <a href="mailto:jhaworth@csc.com">jhaworth@csc.com</a>|<a href="http://www.csc.com">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 size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif">"Florin Wach"
<<a href="mailto:florin.wach@gmx.net">florin.wach@gmx.net</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif">"SAP Workflow
Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Date:
</font><font size="1" face="sans-serif">18/03/2013 14:05</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Re: FIPP method
POST</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Sent by:
</font><font size="1" face="sans-serif"><a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a></font>
<br>
<hr noshade="">
<br>
<br>
<br><tt><font size="2">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 <<a href="mailto:jhaworth@csc.com">jhaworth@csc.com</a>><br>
> An: "SAP Workflow Users\' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><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>
> <a href="mailto:jhaworth@csc.com">jhaworth@csc.com</a>|<a href="http://www.csc.com">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,
<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" <<a href="mailto:florin.wach@gmx.net">florin.wach@gmx.net</a>><br>
> To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
> Date: 18/03/2013 11:46<br>
> Subject: Re: FIPP method POST<br>
> Sent by: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><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 <<a href="mailto:jhaworth@csc.com">jhaworth@csc.com</a>><br>
> > An: "SAP Workflow Users\' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><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>
> > <a href="mailto:jhaworth@csc.com">jhaworth@csc.com</a>|<a href="http://www.csc.com">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<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>
> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size="2">http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size="2"><br>
> <br>
> <br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size="2">http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size="2"><br>
</font></tt>
<br>
</div></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto; "><div><span>_______________________________________________</span><br><span>SAP-WUG mailing list</span><br><span><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a></span><br><span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></span><br></div></blockquote></body></html>