1 Reply Latest reply on Dec 14, 2015 6:27 PM by Hari Babu Krishnan

    Best Practice to manage contracts that will not be renewed, but are in force until expiration date?

    mit01 Apprentice

      We have set up business areas to get expiration notifications for contracts reaching the expiration date.  If we receive communication from the business area that the agreement should not be renewed, but will remain in force until the expiration date, what is the best practice to manage this action within Ariba?

      We want to turn off further email notifications, since the decision has already been communicated; however, we don't want to officially 'Close' the contract until the expiration date.  We also don't want to lose track of the action to close the agreement on the expiration date.

      Ideally, we'd want a status that would turn off notifications and then prompt for action on the actual expiration date (or automatically close). Any thoughts on how this can be managed this?

        • Re: Best Practice to manage contracts that will not be renewed, but are in force until expiration date?
          Hari Babu Krishnan Master

          Hi

          We recommend that you do a termination amendment and make changes to the notification and expiration emails so that the only person to get notified when the contract actually expires is the Project Owner or, if you choose, you can update to Project Owner to an administrator. 

          Then, when the contract expires, the Project Owner closes the project.  All expired contracts should be closed.  Optionally, you might also set up a notify task (or even include it in the template) according to the retention policies of your corporation.  When this task sends its notice, an administrator should delete the project.

          Hari and Sharon

          1 of 1 people found this helpful