Sourcing

Get Involved. Join the Conversation.

Topic

    John Lay
    19D Create Supplier Contract from Negotiation
    Topic posted November 5, 2019 by John LayBronze Medal: 1,250+ Points, tagged How-To, Negotiation Award, Procurement Contracts 
    117 Views, 18 Comments
    Title:
    19D Create Supplier Contract from Negotiation
    Summary:
    New feature instructions incomplete to accomplish goal of creating contract
    Content:

    Unable to determine steps required to create contract from Negotiation. When looking at Negotiation in Closed status unable to determine steps to access Edit Negotiation form during Award process where the Create Contract button is available to user. Need more complete set of steps that identify Negotiation status and navigation steps required to enable user to Create Supplier Contract from Negotiation.

    Comment

     

    • Ramesh JC

      Did you go through the published TOI which has a recorded demo?

      https://download.oracle.com/ocomdocs/global/apps_19D/prc/Create_Supplier_Contracts/index.html

       

    • John Lay

      Discovered that the LOV will only present a value when the setup task 'Manage Contract Type' definition includes Line Type=Item. This is not acceptable for clients that do not use Items.

    • Ramesh JC

      We will treat this as a bug and fix this. Ideally it should allow 'contract types' with no line types defined as well.

    • John Lay

      Ramesh,
      Moving on to the actual Create Contract process I have some additional questions. When completing the Negotiation Award there are references to the Contract created for each awarded supplier which is good. Also noted that the Base Contract is a separate record from the Awarded Contract so here is my question:

      What happens to the Base Contract record?
      What purpose does it serve if not used for Award and what should be done with it? Would imply the process creates a contract record with no continuing purpose that clutters the Contract repository.

      From within the Contract created by Sourcing, is there any reference back to the Negotiation record that created it? Seems logical that the document history or Overview page would contain a reference and link to the source Negotiation.

      • Ramesh JC

        Party-less base contract holds the contract terms for the negotiation. Yes we need some enhancements on the contracts side to flag this as a different contract or they need to enhance their contract template to support contract terms. You should post these ideas in their idea labs.

        Coming to referencing back to negotiation record, its already built & coming in 20A. You will see source document references in the contract with link to the negotiation.

         

    • Sara Craven

      Hi Ramesh

      I had to award/create the contract before the award was submitted for approval which does not seem logical, am I missing a step as i would expect to create the final contract after the award has been approved?

      Also agree with John, why do we end up with two contracts? The base contract just stays in draft form as a duplicate, again am i missing some steps? 

      It is also a shame that this functionality is restricted to the contract class - enterprise contracts only and not those that use the class - agreement. 

      I've been looking forward to this functionality for a long time and it could be very good if it covered all contract types. 

      Thanks

      Sara

      • Ramesh JC

        Hi Sara,

                  We have customer use cases where they want to create a contract before award and we have cases where they want to create after award, now this feature will support both. In 20A we are going to support new approval attributes to control this.

        We are building this feature in incremental builds based on the customer feedback, you can go ahead and log an idea in idea labs for class - agreement or other contract types.

         

        -Ramesh

         

        • Sara Craven

          Hi Ramesh

          I totally understand the use case for creating contract before award, and after award and support both. However what i mean is when you award the lines at the end of the new process you have to do it before the award is submitted for approval, whereas i would expect it to be after approval.

          For example, you author the RFQ and create the base contract, you then publish, score, evaluate, etc, select award and then select the line/supplier to create the contract from the base contract. But then you have to submit the award for approval, what if the approver spots a mistake or disagrees and you have to select a different outcome for award, then you have to start again. Where as i would expect the bit in bold to be after the award decision has been approved then you can create the contract for the approved award decision. 

          I have created an idea for other contract types.

          Thanks

          Sara

           

           

    • Ramesh JC

      So this company which ever chooses not-to-create contracts before award is approved should enforce that rule manually. In 20A with these new approval attributes we are supporting, you can create approval rules around whether a bid has already contracts or not.

      Also I hope you are aware that 'create contract' (which just creates a contract with terms but NO lines) and 'Add awarded lines to contract' are 2 different actions. And 'Add awarded lines to contract' is visible only after award is approved & completed.

      • Sara Craven

        Ok that is good to know, I assume I don't get that action due to the bug as i am not using the item line type. I had run through this multiple times looking for that option but all i found was the second create contract button. I will wait until the bug has been fixed and will test again. 

        Thanks for your help. 

        Sara