FIPP method POST
John Haworth
jhaworth at csc.com
Mon Mar 18 10:43:33 EDT 2013
Hi
Thanks for that.
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?
Kind Regards
John Haworth
SAP PDM
CSC
Euxton House, Euxton Lane, Chorley, PR7 6FE.
|Office: +44(0)1257 23 6474|Mobile: +44(0)7921069650| email:
jhaworth at csc.com|www.csc.com
=============================================
Advanced Holiday Notice:
3rd June - 28th June
=============================================
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
From: "Florin Wach" <florin.wach at gmx.net>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date: 18/03/2013 14:05
Subject: Re: FIPP method POST
Sent by: sap-wug-bounces at mit.edu
Hi John,
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.
The user itself will not notify this kinde of
dialog-method-that-is-no-dialog, unless it runs into an error ;-)
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.
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.
Florin
-------- Original-Nachricht --------
> Datum: Mon, 18 Mar 2013 14:50:46 +0100
> Von: John Haworth <jhaworth at csc.com>
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> Betreff: Re: FIPP method POST
> Hi
>
> Thanks for that.
>
> Could you please just clarify, if this has been defined as a dialog
> method, when creating the workflow task that's calls it, would the task
> not require a user name as the the receiving agent, (as its a dialog
> method, i cant run it as a background task), so its going to try and
send
> the task to the receiving agent.?
>
> Kind Regards
>
> John Haworth
> SAP PDM
> CSC
>
> Euxton House, Euxton Lane, Chorley, PR7 6FE.
> |Office: +44(0)1257 23 6474|Mobile: +44(0)7921069650| email:
> jhaworth at csc.com|www.csc.com
>
> =============================================
> Advanced Holiday Notice:
>
> 3rd June - 28th June
>
> =============================================
>
> 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
>
>
>
>
> From: "Florin Wach" <florin.wach at gmx.net>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date: 18/03/2013 11:46
> Subject: Re: FIPP method POST
> Sent by: sap-wug-bounces at mit.edu
>
>
>
> Hello John,
>
> I've create a new method PostDialog within a subtype of FIPP and checked
> the box "Dialog".
> Within the method implementation I've basically called the Post method
and
> passed throught the same exceptions. You may vary here the
implementation
> as you like, depending on the processing flow of the workflow pattern,
and
> how you'd like to handle the exception situation, such as "Object is
> currently locked by user &2"
>
> begin_method postdialog changing container
> swc_call_method self 'Post' container.
> CASE sy-subrc.
> WHEN 0. "Everything was okay with the call, so nothing to do
> WHEN 1001. "Serious posting problem
> exit_return 1001 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
> WHEN 1002. "Locked
> exit_return 1001 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
> WHEN OTHERS. "Unknown exception
> exit_return 9001 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
> ENDCASE.
> end_method.
>
>
> Florin Wach
> Systems-Integration
>
>
> -------- Original-Nachricht --------
> > Datum: Mon, 18 Mar 2013 12:24:44 +0100
> > Von: John Haworth <jhaworth at csc.com>
> > An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> > Betreff: FIPP method POST
>
> > Hi
> >
> > Thanks to all who responded to previous help requests.
> >
> > I now have a FI Journal approval workflow that seems to be meeting
> > requirements. I have one further question though. The workflow uses
the
> > POST method of FIPP to post the fi document after it has been
released.
> > But as the post method is a background method, the users see that
> Approved
> > documents show Posted By WF-BATCH in the header. Is there any way of
> > changing this to show the name of the person who released it instead?
> >
> > Kind Regards
> >
> > John Haworth
> > SAP PDM
> > CSC
> >
> > Euxton House, Euxton Lane, Chorley, PR7 6FE.
> > |Office: +44(0)1257 23 6474|Mobile: +44(0)7921069650| email:
> > jhaworth at csc.com|www.csc.com
> >
> > =============================================
> > Advanced Holiday Notice:
> >
> > 3rd June - 28th June
> >
> > =============================================
> >
> > 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
> >
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130318/fd3b6f51/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 18237 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20130318/fd3b6f51/attachment-0001.gif
More information about the SAP-WUG
mailing list