Budget edit batch processing
Budget edit processing ensures that transactions requiring budget validation are properly checked before completion.
Budget Edit Batch Processing groups budget edit transactions into a queue, allowing them to be processed more efficiently in batches rather than individually.
When batch processing is enabled for a transaction and a transaction is released:
- A budget edit batch record is created if budget checking is required.
- Each batch record represents a single transaction queued for budget checking.
- The system identifies transactions awaiting processing by checking for a blank Completion Time in the batch record.
- When processing is successfully completed, the system marks the batch record as complete and populates the Completion Time field.
To review existing batch records and its status, see Viewing budget edit batches.
The Enable Budget Edit Batch for All Transactions option controls whether transactions are processed immediately or through the batch queue.
When the option is , transactions are added to the batch queue and processed during the scheduled batch run. When the option is , budget checking is performed immediately when transactions are released.
The table below summarizes the system behavior and expected outcomes for both configurations, including their impact on transaction processing, timing, and system performance.
To enable or disable batch processing for all transactions, see Enabling budget edit batch for all transactions.
| Aspect | Enabled | Disabled |
|---|---|---|
| Transaction Coverage | All transactions requiring budget validation | Selected transactions only |
| Interface transactions (PO, AP, CB, etc.) | Batch records created per document, processed by scheduled job after interface completes | Batch records created per document, processed by a one-time background thread spawned after interface completes |
| Processing trigger | Scheduled background job runs on a configurable interval. The default is 10 seconds. | Immediate — either inline during the transaction or spawned directly by the originating process |
| Auto-prune completed records | Available (configurable) | Not available |
| Recovery from mid-process failure | Scheduled job automatically retries stranded records on next cycle | Manual run of Process Batch Edits is required. |
| Stuck records after blocking condition clears | Picked up automatically by scheduled job | Requires manual Process Batch Edits or a subsequent transaction to trigger processing. |
Budget Edit Batch Records
Depending on value set for the Enable Budget Edit Batch for All Transactions option, transactions can be processed using either Batch Mode or Non-Batch Mode.
When the Enable Budget Edit Batch for All Transactions option is selected:
- A batch record is created for every transaction that requires budget checking upon release.
- All transactions are processed through batch processing.
When the Enable Budget Edit Batch for All Transactions option is not selected:
- Some transactions are processed individually instead of batching. These include:
- Manually created entries
- Other batch programs
- Imports from Infor Spreadsheet Designer
- Only these transactions are processed in batch:
- Interface jobs for Requisition (RQ), Purchase Order (PO) and Accounts Payable (AP) releasing multiple documents
- Documents that are released when the Activate or Process Pending actions are run and the budget editing is suspended.
- Documents with 50 or more budget template amounts to be edited.
To review existing batch records and its status, see Viewing budget edit batches.
To enable or disable batch processing for all transactions, see Enabling budget edit batch for all transactions.