Overview

This article covers how to how to finalize a resource commitment record through the Approve and Push Commitment action on Task 7.3 Enter Resource Commitment Details, which is the fourth step of processing a record in the Resource Commitment Allocation Module (RCAM). The following steps are for users of the EPBCS Web Application.  

Essential Information

• How to Finalize a Resource Commitment Record in RCAM (Smart View) is a separate article. 
• You will not be able to finalize/push a record through the Approve and Push Commitment action until all required fields have been completed.  
• The Approve and Push Commitment action does not initiate any workflow or notification for the individual designated in the Resource Commitment Approved By field - there is no approval workflow built into RCAM.
• The Approve and Push Commitment action formally liens the Destination side of the resource commitment in RCAM.
• Pushing a Base Commitment record generates the Transfer In Commitment record, which is viewable by the Destination if they have the appropriate access to RCAM and is viewable by the Source if the Destination falls within their security rights.

Next Steps

Finalizing through the Approve and Push Commitment Action

1. If not already on Task 7.3 Enter Resource Commitment Details, navigate to it via Task 7.2A Enter Basic Resource Commitment Data – Simplified. For detailed instructions on how to navigate to locate the record on Task 7.2A, refer to KBXXXXXXX: How to Locate a Resource Commitment Record in RCAM (EPBCS Web App). 
   NOTE: While you may also navigate to Task 7.3 directly from the task list or by clicking Next on Task 7.2, this is not recommended for the following reasons:
   - You will be limited to only the 3Yr time horizon.
   - You may be forced to manually select each individual dimension in the POV (e.g., Financial Unit, Project, Fund, Function, Budget Type, Scenario) to generate details for the specific record you need – this is an onerous process, and incorrect selections could lead to unwanted data.  
2. Once all required fields are completed and you have reviewed the calculation, right-click on any cell in the left-most column containing field labels to produce the Action Menu. 
3. Select Approve and Push Commitment from the Action Menu. 
   
    
   
   
4. A window will appear indicating that the action has run successfully – click OK to clear this message.

 
NOTE: If you instead receive an error message, verify that your Destination Project belongs to the selected Destination Financial Unit. Invalid Financial Unit/Project combinations are the most common reason for encountering an error when running this action.

Verify Successful Push on Base Commitment Record

The resource commitment record should now show several indicators that the record was successfully pushed:

1. The Resource Commitment Pushed Flag field will display Yes within the No Year/Assumptions (or No Year/BegBalance) column, the current fiscal year FYXX/Assumptions (or FYXX/BegBalance) column, monthly period column(s) with amounts in the current fiscal year, and in the Year Total column for the current fiscal year.
   
    
   
   
2. Resource Commitment Pushed By is populated with the name of the user who ran the Approve and Push Commitment action. This value is populated in the No Year/Assumptions (or No Year/BegBalance) column, the current fiscal year FYXX/Assumptions (or FYXX/BegBalance) column, and monthly period column(s) with amounts in the current fiscal year. These values will be overwritten each time the record is pushed within a fiscal year, but the last value recorded in a prior fiscal year will not be overwritten. This allows for multiple names to be recorded over the years. 
   
    
   
   
3. Resource Commitment Pushed Date is populated with the most recent date the Approve and Push Commitment action was run. This value is populated in the No Year/Assumptions (or No Year/BegBalance) column and the current fiscal year FYXX/Assumptions (or FYXX/BegBalance) column. These values will be overwritten each time the record is pushed within a fiscal year, but the last value recorded in a prior fiscal year will not be overwritten. This allows for reporting on most recent Pushed Dates at the fiscal year level.
   
    
   
   
4. If not completed in a prior step, the Resource Commitment Approved Budget Amount in the current fiscal year is now populated with the same value as the Resource Commitment Amount within the current fiscal year. 
   
    
   NOTE: If your security rights allow you to view the Destination side of the resource commitment, you can further verify the record was pushed by looking for the Transfer In Commitment record under the same CTID on Task 7.2A Enter Basic Resource Commitment Data – Simplified. When searching for the record, make sure you have an appropriate Financial Unit member tied to the Destination Financial Unit selected in the POV.