Register incoming MM/FI invoices in workflow as a step

Dart, Jocelyn jocelyn.dart at sap.com
Wed Mar 19 17:47:20 EDT 2014


Hi Robert
The vast majority of database updates from such transactions occurs in the LUW triggered from but separate to the transaction itself. Which means if you use synch methods you risk the database updates being incomplete or failing at the time the workflow moves onto the next step. Typically adding any user activity into the same method will add sufficient delay to avoid problems other than actual failure. However suggest you think around a couple of worst case scenarios in your design
Rgds
Jocelyn

Sent from my iPhone with many apologies for the spelling, grammar and any other deficiencies

On 19 Mar 2014, at 7:39 pm, "Robert van den Berg" <wug at bergtop-ict.nl<mailto:wug at bergtop-ict.nl>> wrote:

Actually, it is not to approve, but to change the document.
First person registers the document and fill's in the header. (FV60 / MIRO)
Then it is send to a second person who complements the data. (FV60 / MIR4)
Then it is send to a third person who approves the invoice. (FV60 / MIR4)
When it is approved, the invoice is booked.

For both FI and MM invoices.....

Idea now is to create a subtype of the BOR objects and just call MIRO and FV60 in a sync method.
Anyone knows why the methods are async?

Regards,
Robert

Op 18 maart 2014, schreef Andy Curtis <abcurtis at gmail.com<mailto:abcurtis at gmail.com>>:

At risk of repeating Mike here, we use a solution for this built by OpenText (VIM Vendor Invoice Management) it is very good actually.  They basically have code in teh LIV Invoice SAVE BADI, and probably the equivalent in FI Invoices, I don't do much with them so now too sure.

OpenTexts Save Badi basically popups up a screen to allow a 'Parking Reason' to be chosen (ohh this is on Parking an Invoice, it will get Posted when it's ready later in the Resolution process).  The Parking Reason is the basis for the next step in the the life of the Invoice and is used along with other Agent determination config to send the invoice to the person (approver) that needs it.

QQ, wouldn't you have already approved the PO and GRN/SES? So a 3 way match could be posted?

Andy


---------- Forwarded message ----------
From: "Robert van den Berg" <wug at bergtop-ict.nl<mailto:wug at bergtop-ict.nl>>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu<mailto:sap-wug at mit.edu>>
Cc:
Date: Tue, 18 Mar 2014 14:46:57 GMT
Subject: Register incoming MM/FI invoices in workflow as a step
All,

I have a requirement where we want to register an incoming invoice in a workflow step, then choose the approvers and send the invoice to the approver.

Normally (as I read from SAP documentation), a user goes to transaction MIRO of FV60, enters data and when they save, then the workflow starts. But then, the user can't choose the approvers. So I need the workflow to have the registration included..
But to be able to call MIRO or FV60, I can only use async methods.

BUS2081-CREATE I can use, because this triggers the event BUS2081-CREATED. So MIRO seems to be checked.
But for FV60, I need to use BKPF-CREATE but this triggers event CREATED from object FIPP. So I can't use this as a ending event...

Does anyone have any experience with the registration of incoming invoices (MM/FI) from a workflow?

Kind regards,
Robert


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto: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/20140319/6fc3a249/attachment.htm


More information about the SAP-WUG mailing list