After selecting a batch for finalisation through session tfgld1110m000 i am getting this error (attached).
This error is very frequent in our company and the solution suggested every time is to make a counter entry in table tfgld102 though GTM to match debit / Credit.

I dont think this is the correct way.
First of all i want to understand where to look if a debit/credit entry is comming "0' for a line. Are the chart of acocunt set properly for sales invoice.

Request to all Finance guru..to look in the matter and give me advice in detail. As i am not finance consultant , i make require the procedure in brief to understand. Please dont mind.. as we have no finance consultant in our company at the moment.

Thanks
Manish

Urgently need some advice on this..

Regards,

Manish

in case of stuck up of any finalization process you can re run it from Restart Finalization Run (Interim Table) (tfgld1118s000), or Restart Finalization Run(tfgld1119s000). first try these sesions before the manual counter entry.

I have tried to RUn that session. But it gives me a message..'This batch is not a Stuck batch".

This session can be run only if the batch is stauck in between by power failure or something like that.

Please advice me...

Thanks

Hi,

Is the batch an integration batch.??!!!

Regards,
Sushil Kumar Mudaliar

Yes...and the status is 'Error'

Regards

Yes. It is . The status is "Error"

Regards,

Manish

Manish,
First thing is if its an integration transaction (as per your last post), how come you are finalizing it by session Select Batches for Finalization instead of Post Integration Transactions to Finance Transactions?

Secondly, again since you said its an integration transaction, did you try looking into Display Integration Transactions Log {tfgld4532m000} and subsequently Display Integration Transactions by Project/Order {tfgld4510m000}?

sk

Hi,

Sukesh >> i assume the finance parameters "start of finalization process" after posting must be "NO" .

Manish >> as said above by sukesh - kindly check the session logs -> and post screen dump of tfgld4510m000 (all tabs) for the problem.

and Is their any script updating sales orders directly (i.e sales made from any other anciliary apps).


Regards,
Sushil Kumar Mudaliar

Hi Sushil
Checked the log. Also posted screen dump of tfgld4510m000 all 7 tabs. Info on one form is 2 big hence breaked up in 2.
Dont get confused with old sales order. Look only for Year2008.

Yes we are importing sales order from exchange scheme.

Regards,

Manish

Hi Manish,

1.I suppose their might be some issue with "Exchange" -> may be some other members can throw some light on the same.


Yes we are importing sales order from exchange scheme.

Else you could log a call with Infor for "Exchange" issues.

2.Is the problem entry is for a specify Item / item group -> please check with your previous counter entry.

Regards,
Sushil Kumar Mudaliar.

Sushil,
I dont think there should be any issue with Exchange scheme. Because this is a routine procedure and we are doing it quiet often. And sales ordere has gone through other steps like GEnerate OUtbound, Maintain Deliveries etc upto Deleting lines....
Regards,

Manish

Manish,

Please Monitor weather the Problem you reported exists in

1.Manually created SO ?
Or
2.Exchange Generated SO ?

Note :
Years ago i had similar issue due to SO created using AFS .i had debugged and resolved.
hence i suggest you on similar lines.

The AFS only used to create SO .
steps like Generate , release outbound are done manually with out issues -> then after posting i had problems .

Regards,
Sushil Kumar Mudaliar

Manish,
I noticed that your Sales Issue transaction on 26/07/2008 is unposted. Why? Does the integration log tell you what did not work (example-Could not create account...)? Do the Inventory and WIP Transaction Accounts properly handle all the elements you are feeding it? I noticed that the warehouse is different for those lines? If the integration mapping was set-up very specifically and the process has changed it is possible that the transactions are not being handled correctly.