Fiscal year change raises completed event multiple times

[former_member348787]

This is an issue we have been dealing with for several years.  We have a 2 week window at the end of the fiscal year where users can create documents for either the new or the old year.  Invariably, a document is created for the "wrong" year and the user discovers this after it has been saved as complete.  When they go back into the document and change the posting date to the other fiscal year, SAP interprets this as a new document and triggers the completed event multiple times resulting in multiple workflows for the same document.  Users can simply approve the workitems and the additional workflows will error when trying to post and I delete the extras but apparently this has become an unacceptable solution.

The events are triggered simultaneously and I can't figure out a way to get rid of the extra workflow instances.  Any help is greatly appreciated.

[former_member186746 · Accepted solution]

Hi,

If you can find out when a year is entered wrong, you could use conditions (swb_cond) or check function modules in SWE2 to prevent the instantiation of workflows.

I think this is the best way to tackle this issue, the standard logic of triggering the event is sound and should be left alone. You should focus on preventing workitems, or maybe better create a warning in the screen of the users when they want to save. Check for badis to fulful that requirement.

Kind regards, Rob Dielemans

[former_member348787]

I already had a couple of start conditions so I couldnt use the check function module.  I added a new attribute to the BO to check for existing workflow and use that as an addition start condition.

Thanks for the replies.

[Pyc]

G'day Tommy,

It's been a long time since I looked at this issue, but have you reviewed note Note 87700  (FIPP: Documt nos change, workflows not transferred) and it's related notes?

Once you've run the associated report and a flag is set within the system, rather than triggering new WFs when changing the fiscal year of a parked the system rather cleverly updates the existing WF instances with the new object key thus avoiding the duplicate issue you mention.

Hope it's as simple as this for you.

Have fun,

Mark