Does anyone have any suggestions for amending existing workspaces? We have a lot of 1 page renewal agreements to amend contracts. The renewals require legal review. When we first built out our process we did not have a renewal phase built in, same with the legacy loaded agreements.
I have since modified the template to trigger an amendment phase whenever renewal is selected as an amendment type, however as this only impacts new workspaces it won't come into play for some time.
Is there a way to push out a phase to existing workspaces, or even grab a phase that has been built out and stored somewhere (sourcing library maybe?). Sourcing leads manage their own workspaces, however as the admin I have been manually building the amendment phase out to workspaces on a one by one (as needed) basis. Thanks.
Thank you Rich. This could work for our bulk load legacy agreements, I think. That still leaves manual work for agreements created in ariba (with assembled documents), but it is a start. I have put in a service request to enable this option and will test out the functionality.
We built in task steps for renewal, amendment and termination. No steps for administrative. We've got 2 templates - one for new contracts and one for legacy contracts. Both have the amendment options and tasks built in. The trick is to think through your current types of amendment procedures and map them to the 4 options in the system.
But there is one MAJOR restriction in Ariba. if you build in the various amendment tasks to trigger when you select those amendment types they only come up once to be completed - what this means is if you have a multi year contract with numerous amendments, after the first set of amendment tasks are completed, then the contract owner has to manually create the tasks for any subsequent amendments. Ariba really need to look at the whole amendment process because it doesn't match real world situations of how buyers have to work with contracts. Happy to show you a demo of what we set up. In exchange, I'd be interested to know if you are using the DFS enablement and negotation function with main agreement and clauses. We couldnt' get it to work so we've dropped it and just pass word documents back and forth.
not sure - Ariba consultant was helping us. when you say refire, it fires a NEW task, or it just refires the old completed task? She was saying we would have to work out how many times we would need a renewal or amendment and we'd have to set up all those tasks over and over again in the template. It became to onerous to consider in the end. If your solution is different, I'd be interested to learn more.
The trick to getting NEW tasks with each Amendment is to place the task on the workspace itself (which is actually a document). You need to do this from the template overview View. after adding the tasks, you'll need to go to the Tasks tab and place them in the order and folder that you want. Now, every time you amend the workspace, the tasks will reset. One word of caution is for approval tasks. If you have an approval task on the whole workspace, all documents in the workspace will be sent in the email, which may 1) clog your servers and 2) may clog your approver's focus. So, as a compromise, when we work with our customers, we place all of our amendment tasks except the approval task (which needs to be resubmitted anyway) at the template level and have those tasks repeat with each version of the workspace.
Would you be able to provide more detail steps on how you create the tasks and NEW tasks with each amendment that is created in the existing workspace?
This is something our orginization is really looking into doing, but do not know much about it. I create a condition tied to the Amendment field and document but that works only once, so I am open to any information you can provide on creating these amendments within the existing workspace.
I reached out to Sharon Horton for guidance regarding your questions. Noted below is the feedback she provided:
"This is a very complex topic and it can't be easily answered within the confines of an Exchange post. However, we would recommend that you go to this web site which contains a large number of free webinars that have been conducted by our experts in the Best Practice Center. The Webinar that you should look for is Amendment Processing and Advanced Approvals."
Hopefully, this will get you started.
Ariba Exchange Community Manager
Ariba is looking into a "fix" for the Template Upgrade to Ignore Assembled Doc's. That being said it is important that we all put in Enhancement Requests into Connect. This will only enforce that it is a necessary enhancement/addition. The more visibility customers give that its wanted, the faster it should get implemented.
This is the case for many items discussed. As a community we need to get unified Requests into Connect for these types of issues that need fixing or enhancing.
Everyone, please go to Ariba Connect and log an Enhancement Request.
The template upgrade feature is enabled as a parameter in Ariba but it's also a feature in the template Advanced tab. There are 3 levels for the parameter: No upgrade, Ask When Upgrade, and Upgrade Automatically. If you don't have any assembled documents, then you can use the upgrade automatically setting. Otherwise, you will need to use the "ask" setting. This is important when you have a mixed template environment, some with assembled documents and some not.
When the "ask" feature is enabled and the user selects Amend, they are presented with a radio button yes/no defaulted to no. They will need to select Yes to get the upgrade. Obviously, sometimes this will be missed.
If you have an assembled document and either use Upgrade Automatically or if you select Yes to the ask question, and your template is set to upgrade, you will get an error.