Postponement of background process

After non-finalized transactions have been created, the automatic start of the background process can now be postponed.

The background process is used to update the non-finalized totals by ledger account and ledger account/dimension, and to generate tax transactions or intercompany/intersegment transactions. When finalizing the transactions, the background process is automatically rerun before the transactions are finalized.

If sessions are closed in which non-finalized transactions are created and, shortly after that, the bshell is closed, the background process can still be running. Consequently, the status of documents is set to In use by the background process. The background process must be restarted to resolve this blocking situation.

This situation often occurs in case of integration transactions where many transactions are generated. Usually, after these transactions have been generated, they are immediately finalized (which reruns the background process). If the background process can be postponed for these type of transactions, the background process need not be restarted and time is saved because the background process is run only once for the transactions.

To support this functionality, the Activate Background Process field has been added to the Transaction Types (tfgld0511m000) session. The field can be set to these values:

• Always (default value): when non-finalized transactions are created for the transaction type, the background process is always started.
• Postpone: when non-finalized transactions are created for the transaction type, the background process is never started. Only during finalization, the background process is started.
• Postpone when in Job Mode: When non-finalized transactions are created for the transaction type by a job, the background process is never started. Only during finalization, the background process is started. When non-finalized transactions are manually created for the transaction type, the background process is started.