Hi all

While finalizing Batches, Some times i am getting a message "Background process Not Yet Completed". This message comes in two places.

1. At the time of selecting a batch.
2. At the time of Finalizing a batch.

The problem is, for some batches, even after running the session "invoke background process", still it is showing the message. I checked in the GTM [tfgld102] for the batch. The Background process indicator for all the documents against the batch is "Processed" This problem majorly coming for Integration Batches.

Can i get the reason of this with a solution.

if the error is mainly for integration batches, then check the reporting and tax periods by printing non finalised transactions. Also check the display error log (tfgld1506m000) for those batches.

Hi Balaji -

What is the update mode of your integration transaction types? (session tfgld0111m000).

When we first went live, we had ours set to End of Session. We ran into tremendous problems with the background process, even after running the Invoke session. Many times we had to let them set overnight in order for the status to change.

We changed our update mode to Finalization, and the problem went away. (please note that this change must be done when there are no existing transactions for the transaction type - everything must be posted.)

Another thing that can cause the slow process is if you have many different types of integrations using the same transaction type. This can cause you to get the "in use" error.

We had also experienced the problem with missing tax/reporting periods as mentioned by venkat500. We are on version IVc2. The problem was caused by creating batches in the Maintain Transactions session instead of the Maintain Batch Status session. Once we began using the Maintain Batch Status session, the problem was resolved.

Hope this info helps.

Regards,
Linda


Regards,
Linda

We experienced the same that only if you don't use finalization as update mode for a transaction type, you got problems with background processes.

Bye, Juli

--------------------------------------------------------------------------------
We changed our update mode to Finalization, and the problem went away. (please note that this change must be done when there are no existing transactions for the transaction type - everything must be posted.)
--------------------------------------------------------------------------------

Hello,
I also want to change the mode to finalization, but we have go live, history transactions have existed, in this scenario, how to do? Posted or Finalization all transactions?

Carol,

I think only if you finalized all the open transactions, you can change the finalization mode. No matter if historical data existed.

BR,
Anthony

Hello Carol -

Anthony is correct - the change can be made as long as all transaction are finalized. That is what I meant when I said no existing transactions - I should have clarified and said no unposted transactions.

Sorry for the confusion, and good luck. I hope this helps you.

Regards,
Linda

Ideally all system-generated transaction’s update mode should be ‘Finalization’
i.e. All Integrations transactions, all recurring transaction, automatic balancing of P&L transaction, final close year transaction, FAS transaction and ANP/ANR transaction from CMG.

Background process is a Unix feature; never keep update mode other then finalization in NT for any transaction type.