FIPP method POST

[Florin Wach]

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
>