Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Ramesh Radhakrishnan
    R13-19A - ALLOW APPROVERS TO UPDATE BUDGETARY-CONTROLLED...Answered
    Topic posted May 13, 2019 by Ramesh RadhakrishnanGold Crown: 30,000+ Points, tagged Approvals/Notification, Public Sector 
    56 Views, 5 Comments
    Title:
    R13-19A - ALLOW APPROVERS TO UPDATE BUDGETARY-CONTROLLED REQUISITIONS
    Content:

    I would like to understand more on the "Allow Approvers to  Update Budgetary-Controlled Requisitions"  as part of  19A update.

    Is there a detailed document for this functionality? I turned on this functionality and tested. Based on my testings I have the following questions.

    1. Do we need to add privilege - POR_CREATE_REQUISITION_ALLOW_APPROVER_MODIFICATION_PRIV for the approvers to edit the requisition?
    2. Where do we see the changes made by approvers to the original requisition? Business wants to see the history of which approver made what changes to the requisition and compare to original requisition submitted by the requester
    3. When any of the approver makes changes and approves, the requisition is withdrawn and send to requester again for resubmitting. Is this is how it works? For example there are 3 approvers and if approver 2 and approver 3 make changes and submits the requisition it is again going to requester for resubmitting the document to the approval chain again. Need more clarification on how this works?

    Thanks

    Ramesh

     

     

    Version:
    R13-19A

    Best Comment

    Ashok

    To your questions 2 and 3:

    Question 2: The basic privilege requirements (including the privilege you have mentioned) remain. It is up to the organization to determine which approver/s needs to be given the privilege to edit a requisition. This is existing functionality as you are aware

    Question 3: That too is existing functionality and is based on how the configuration of the Requisitioning BU:

    In the Configure Requisitioning Business Function, there is an attribute entitled: Reapproval required for changes made during an active approval process. This is the attribute that controls the behavior you have asked about.

    Comment

     

    • Ashok

      Hi Ramesh

      On documentation, when i doubt, you should always visit docs.oracle.com (Not sure if you have on this topic). Here is an extract from the document and here is a link to the documentation: https://docs.oracle.com/en/cloud/saas/procurement/19b/oaprc/manage-requisitions.html#OAPRC2435316

      Approver Edit of Budgetary-Controlled Requisitions

      As an approver, you can edit a budgetary-controlled requisition submitted by a preparer, if the Allow Approvers to Update Budgetary-Controlled Requisitions feature is enabled for your application. You can edit the chart of accounts, project details, quantity ordered and so on. When you submit the edited budgetary-controlled requisition, the application runs budget checks and handles the funds reservation on either submit or approval, depending on the budgetary controls configuration.

      If the budget check fails, you are notified with an appropriate error message. If you reject the requisition, funds will not be reserved if they have not been already, and the requisition will not be submitted.

      If you have the Request Budgetary Control Override security privilege, you can request override.

      The Budgetary Control Analysis Account Activities is an Oracle Business Intelligence Publisher report that helps you see which activities are consuming your budget. Approver edit of a Budgetary Control and Encumbrance Accounting-enabled requisition during the approval process results in the creation of the following entries in the report:

      Action by Approver Transaction Action

      Approver clicks Edit button

      Requisition withdraw

      Approver clicks Funds Check button

      Requisition check

      Approver clicks Submit button

      Requisition submit

    • Ashok

      To your questions 2 and 3:

      Question 2: The basic privilege requirements (including the privilege you have mentioned) remain. It is up to the organization to determine which approver/s needs to be given the privilege to edit a requisition. This is existing functionality as you are aware

      Question 3: That too is existing functionality and is based on how the configuration of the Requisitioning BU:

      In the Configure Requisitioning Business Function, there is an attribute entitled: Reapproval required for changes made during an active approval process. This is the attribute that controls the behavior you have asked about.

      • Ramesh Radhakrishnan

        Hi Ashok,

        Thanks for the inputs. This is very helpful. I will test on this further and see. Also can you please have the below point checked with Product team? Will this be an new enhancement?

        1. Where do we see the changes made by approvers to the original requisition? Business wants to see the history of which approver made what changes to the requisition and compare to original requisition submitted by the requester

        Thanks

        Ramesh

         

    • Judy Hamner

      Ramesh, 

      We have found that even if we have "Reapproval required for changes made during an active approval process" not checked/required, the approver that edits the requisition is still receiving an email notification after re-submission.  For instance:

      User 1 is the requester

      Approver 1 withdraws, edits and resubmits.  This action approves the requisition and it is moved on to the next approver.

      Approver 2 withdraws, edits and resubmits.  This action approves the requisition.

      The one issue we have identified in our testing is that after Approver 1 resubmits the requisition, even though the requisition is approved by that action, Approver 1 is receiving a second approval required email notification.  To the Approver, it appears that they have an action to take still, but when you look at the BPM worklist, the approval has already occurred.  

      I opened an SR about this and was told it was working as designed.  However, I think it is very confusing for the approver.  

      Otherwise, we have found that this functionality is working well.

      Judy

      • Ramesh Radhakrishnan

        Hi Judy,

        Yes I agree with you. This is very confusing for approvers and they will not know which notification to take action on as both the notification shows active.

        Once the changes are made and submitted the previous notification should move out of queue. May be we can log this as an enhancement.

        Thanks

        Ramesh