Hi everybody,

Someone created unallocated receipt transaction in the system and then he noticed that bank account is not correct, He deleted this transaction before finalization. He wants to create new unallocated receipt transaction with same sales invoice in the same batch. But, sales invoice does not appear for this customer. Because, invoice already assign old unallocated receipt transactions in tfacr200. How can I get back the old transaction in tfacp200.How to solve this problem?

Thanks in advance...

U cannot delete an invoice that has assignments. U can delete the invoice only after removing the assignment.Check if the assignment was removed and then the invoice was deleted.

Regards

Sai Krishna

I don't want to delete invoice.I took back assigment transaction from the invoice.I want to reassign this invoice with new unallocated receipt transaction.But ,Invoice has already old assignment in tfacr200.I can not see it neither tfgld102 nor tfgld106.So I can not do new assignment for this invoice.

Hi Gulf01,

You describe a bad situation.

It sounds to me that after making the unallocated receipt transaction this transaction was linked to the specific invoice.

The result of that transaction is a posting in tfgld102 and tfacr200. The sales invoice is not longer open.

It is not possible to delete an unallocated receipt is this receipt is already assigned to an invoice. Before deleting the invoice the assignment transaction should be deleted. If the assignment transaction was deleted the invoice becomes back open.

I think that the following happens. The unallocated receipt is deleted which was not blocked by the system for reason of the existing assignment with an invoice. The software is maybe not up to date and that can be the reason why this happens.

Now the unallocated receipt is removed but the assignment transaction is still available in the table’s tfgld102, tfacr200 and tfgld018.

You can only solve this situation by table maintenance and you can only do this if you have enough experience in this work.

Maybe the solution is to log a case to the baan support centre and a support analyst is able to remove the mess.

With Regards,
Jaap Roos

Hi Jaab,
I think that you are right,We still use old version and can be the reason why this happens.
Thanks for your help.I will open the case to the Baan Support centre.

thanks again.

I have seen this situation happen in BaaN CIV also. However it doesnt happen on a regular basis. Any explanation as to why it happens.


Regards
Sai Krishna

Hi Sai_krishna,

This has everything to do with the session’s tfcmg2105s000 and tfcmg2106s000. In the past years these sessions are maintained several times. After each bug fix a new bug popped up. There are lots of dependencies and at the moment of maintaining one of these sessions you must exactly know what you are doing.

Currently the sessions are more or less stable and therefore it is important that you are working with up to date software.

Regards,
Jaap Roos