transaction journal error - job codes not coming through in import.

Hi Mike_James

Attached is information requested.

I have attached batch we are trying to import plus the error files once imported with errors.

Please help to resolve this issue.

Thanks 

MIA17

Hi MIA2017 , I'd like to see the whole of the log entry for the journal that received a 576 warning, the one dated 18/08 with $4585 in the first line. That may tell us which job number has been ignored.

PS, the account number being rejected must be 4-8000, because it appears as such in the log. Is that account a header, or does it not exist?

lt does not make a difference if we have the 4-8000 number in fromt of the job code or not. The 4-800 represents income account and not all job codes get allocated straight to income. Some are allocated to 2-6's numbers for deferred income.

Its the second portion that is of importance eg. F2F23201. OW23216 etc. I have tried both ways of importing with the 4 or 2' s in front and just the code itself.

All job codes exist in MYOB.

Thanks and Kind Regards

Hi MIA2017 

Can you provide a screenshot showing job OW23219 and OW23222 exist and that they are not Header jobs. One of these (or both) is causing a problem.

As Mike_James suggested with the bottom of the 3rd entry cut off, we cannot tell which job is being rejected. 5 of the jobs were ok.

Also MYOB seems to think account 4-8000 does not exist as a detail account. As pointed out by Mike_James this is what caused the first 2 errors. This is unrelated to the jobs issue, but must also be resolved. A screenshot might be helpful.

OW23216 if the correct way to refer and MYOB did find this job. As indicated MYOB could not use either OW23219 or OW23222.

Regards

Gavin

Hi Gavin,

Firstly see attached file for showing that job codes OW23219 and OW23222 do exist. MIA job code listing is extensive. File been sent is a portion of it. 

Secondly, all jobs are been rejected. Non of them are coming through.

Finally, you are correct, 4-800 does not exist. I have correct the external system to reflect correct account number.

Please let me know of your progress.

Thanks and Kind Regards

MIA Admin

Hi MIA2017 , thanks for the extra information. 

I notice that your import file is designed for version 19 of MYOB, which is indicated by the lack of {} symbols in the first line. 

So I'm wondering whether you have recently upgraded to the current version of AccountRight Live, from version 19? Were previous imports done into v19?

A  solution to your issue could be to change the output from the 3rd party program to suit the current version. If this is not a selectable configuration option in that program, ask the vendor whether it is possible. 

The import fields for transaction journals are different for v19 as compared with the current version. See these links for details:

v19: https://help.myob.com.au/prem19/win/impexptables.htm?_ga=2.228739036.1589077814.1694322418-161310380.1561343059

Current: https://help.myob.com/wiki/display/ar/Import+and+export+fields#expand-Transactionjournals

To see an example of the current file format, you can export the same data from the sample file (Clearwater). I've attached that file (transaction journals for sales transactions).

Hi Mike,

Yes i have upgraded MYOB to the latest AccountRight version.

I will speak to the 3rd party organisation and see if this could be one of the issues.

Will let you know when i receive a response.

Thanks and Kind Regards

MIA Admin