Reprogramming Transactions Workflow Status/action: Rejected Vs Unable To Reserve (Doc ID 3031626.1)

Last updated on JULY 24, 2024

Applies to:

Symptoms

Reprogramming Transactions WorkFlow status/action: Rejected vs Unable to Reserve

We are encountering the following action related to Reprogramming transactions and the Approval Workflow functionality.
1) When a Reprogramming transaction fails funds, the transaction status is set to ‘Not Reserved’ (fv_be_rpr_transactions.transaction_status = 'NR') and is able to be updated in the Re-programming Transactions form (FVXBERPR). This seems to work well.

2) When a Reprogramming transaction is rejected by the approver, the transaction status is still set to ‘Processed’ (fv_be_rpr_transactions.transaction_status = 'PR') and is not able to be updated in the Re-programming Transactions form (FVXBERPR). The only way that transactions can be updated is for users to update the individual -RPF/-RPT transactions and then resubmit them for approval. This is a little problematic since users have to update the two -RPF/-RPT transactions (instead of the single RPR record) and there could be a potential for user error in not updating both transactions the same way. In addition, there are additional SLA configuration complexities that are necessary to allow for these transactions to properly account.

Is this the intended functionality/design? Or could this be a bug w/the Reject functionality for the FV BE Reprogramming transactions?
It seems that RPR transactions rejected by the approver should be updatable in the Reprogramming Transactions form like those BE RPR transactions that fail funds. Should the rejected reprogramming transaction status be updating to ‘Not Reserved’ (instead of ‘Processed’) as part of the reject action, to enable further update?
I’ve recorded two quick videos which I’m uploading to demonstrate these different actions.
1) FV BE RPR Transaction - Fails Funds.webm
2) FV BE RPR Transaction - Rejected.webm


The issue can be reproduced at will with the following steps:
1. GO to Federal Administrator
2. Create a Budget Reprogramming transaction.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.