Page 1 of 1

AUTOINVOICE IMPORT PROGRAM COMPLETED WITH ERROR

Posted: Thu Mar 06, 2008 10:39 am
by anandsoni
Dear all,

I m using AP/AR Netting and able to import open interface invoices in AP . But when i try to import invoices by
using Autoinvoice Import Program in Receivables it completed with error.

I checked the log file but didn't find any consolidated error . I just found :

arcdsu() error level: 3 array size: 900000 insert array size: 900000

Error calling raaild()
Error calling raapic()


Plz help me .

Regards,

Anand

Posted: Thu Mar 06, 2008 12:24 pm
by antojoen
Hey Anand,

From this error, i can tell you there are some buffer size problem with your database.

Can u Just send ur log file to my gmail id anto.natesh@gmail.com.

So that i can help you in this.

Regards,
AntoJoeN

Posted: Fri Mar 07, 2008 1:49 pm
by thinktank
Hi,
clear off your autoinvoice interface table and try to run interface again.

Posted: Sat Mar 08, 2008 3:38 am
by anandsoni
Hi,
clear off your autoinvoice interface table and try to run interface again.



<i><div align="right">Originally posted by thinktank - Mar 07 2008 : 08:49:27 AM</div id="right"></i>
Hi,
Do u mean that i should clear the RA_INTERFACE_LINES_all . Please suggest if there is more table to be cleared .

Regards,

Anand

Posted: Sat Mar 08, 2008 10:33 pm
by thinktank
1. Backup the ra_interfaces* table.
2. No harm in clearing the interface error table altogether

3. Then you can do either of the following

a. Autoinvoice a new transaction (or)
b. Insert from backup table the relevant contra transaction only

4. Run Autoinvoice

Sometime back we hit a problem where autoinvoice failed with no error message too. We did this and it worked.

You may just try and let us know if this works for you too.

Posted: Mon Mar 10, 2008 2:21 am
by anandsoni
Hi Sam ,

Thank you so much . Yeah ! it worked for me also . I have done the same as suggested by you and now Autoinvoice Import Program is working file .

Best regards,

Anand

Posted: Mon Mar 10, 2008 7:32 pm
by thinktank
Great.

This is one problem with not enough documentation on metalink or user guide. And unless the dba analyses not much would turn out too.

Good to know you are on track.