Running process batch edits manually

Budget edits are processed automatically under normal conditions:

• For Batch Mode Enabled For All Transactions, a scheduled background process selects and processes pending records.
• For Batch Mode Disabled For All Transactions, budget edits are processed inline as part of the originating transactions.

Budget edit batch records are normally processed automatically. Use Process Batch Edits only to troubleshoot and recover stalled or interrupted queues when pending records are not processed automatically.

You need to run it manually during these scenarios:

• A processing failure left the batch records with a Start Time but no Completion Time. It often has an Error Message indicating what blocked them.
• A selective budget group was not initialized. After initializing it, rerun to retry held transactions.
• A blocking condition such as scenario loading data has completed. When the condition clears, stuck records need to be processed manually particularly when batch mode is disabled, since there is no scheduled job to retry them.
• Batch mode is disabled and no scheduled job exists to pick up accumulated records.

To maintain system accuracy and prevent processing issues:

• Do not modify the delivered asynchronous queue mapping for the Budget Edit queue.
• Do not reassign these actions to a different queue.

Before running Process Batch Edits, ensure that these actions have been done:

• The budget edit queue has been resumed if it was previously suspended
• No budget templates are stuck in Processing status. If a template is stuck, use Recover After Processing Error before reprocessing batches. See Handling failed budget template processing: Requeue and Recovery.
• Any known processing errors have been corrected.