Workflow for Master Agreement (Publish to ERP)

[Former Member]

What is the best practice for approval workflow before publishing a master agreement from eSource to ECC?

In the interest in keeping the source-of-truth within a single application we do not want to keep approval workflow of Outline Agreements in ECC as it is currently when moving the creation of the master agreement functionality to eSource. There is no inherent workflow functionality for master agreements in eSource. Are there customizations and/or best practices for having workflow of master agreements such that the Publish to ERP would not be possible until approval has been done within the eSource application?

[Former Member]

Hi,

As you rightly said, Work flow support is not available in MA and more specifically before sending it to ERP

Here are some options you may want to consider:

- Try to use ACL/Security rights to control who can publish to ERP. For instance only the "document owner" can publish and the document owners are responsible. You can put a message or ask the publisher to enter some values on extension fields on who all approved this document.

- Try using approval functionality in ERP if that works. that may be the simplest..

The following options require heavy customization & scripting:

Leverage workflow support from other docs

- Tie an User defined business document (UDO that supports workflow) with MA. Provide a custom action, which will create a UDO biz doc instance and trigger a workflow behind the scenes. MA will have a reference to UDO and vice versa. Users will approve the UDO. In your Pre Publish to ERP script check for the approval conditions of UDO and work with that.

- if MA is created from Projects try using project workflow for the business process..

Good luck!

Thanks, Baski