cancel
Showing results for 
Search instead for 
Did you mean: 

DTW 2007A Journal Entry Import failing

Former Member
0 Kudos

Hi,

I am trying to import our payroll data in our G/L using DTW but get the following error:

Invalid AccountCode Application-defined or object-defined error oJournalEntries

I have checked the account codes specified and they are present in my Chart of Accounts.

I am using SBO 2007A SP00 PL41. I have checked the DTW template file oJournalEntries and the field names and mandatory requirements are correct.

Here are my header and detail files:

RecordKey AutoVAT DueDate ReferenceDate StampTax StornoDate TaxDate UseAutoStorno VatDate

RecordKey AutoVAT DueDate ReferenceDate StampTax StornoDate TaxDate UseAutoStorno VatDate

1 tNO 20080912 20080912 tNO 20080912 20080912 tNO 20080912

RecordKey LineNum AccountCode BaseSum ShortName Credit Debit VatLine

RecordKey LineNum AccountCode BaseSum ShortName Credit Debit VatLine

1 0 11201000000000 16194.24 11201000000000 16194.24 0 tNO

1 1 23101000000000 16194.24 23101000000000 0 16194.24 tNO

I have tried variations based on searching this forum but I cannot get past this error.

Any Idea's?

Regards,

Gary.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Add-on certified with 2005 may not work for 2007. You need to get the new update from add-on supporter.

There are quite a few database structure changes between two version, you have to use updated add-on if any.

Thanks,

Gordon

Former Member
0 Kudos

Hi Gordon,

HR3PAY is not an add-on but an external application that produces G/L import files in CSV for DTW import.

HR3 have tested with B1 2004 and B1 2005 and hence the 'certified' statement.

My understanding is that by using DTW the background database version changes in B1 would be more transparent and therefore these (B1 2005) CSV files should work in B1 2007.

Can anyone confirm that this AccountCode/formatCode change is actually part of the 2007 changes?

Given that the G/L codes are derived from various parts of the payroll setup (Company, Department, Location, etc) as a segmentation structure, I can't see how HR3 will handle _SYSxxx account codes and thus renders this feature unavailable.

According to the DI API (which I understand DTW uses), the Account Code properties are:

Sets or returns the control account code, or G/L account code as defined in Chart of Accounts.

Field name: Account.

Length: 15 characters.

Is there anyway to do an import using the G/L codes (formatcodes) ?

Regards,

Gary.

former_member583013
Active Contributor
0 Kudos

Gary,

By using a Transform table you could achieve this ..

Suda

Former Member
0 Kudos

Hi Suda,

Many thanks, I have used Transforms where G/L codes were used and this has now loaded ok.

Regards,

Gary.

Answers (1)

Answers (1)

former_member583013
Active Contributor
0 Kudos

Gary,

You need to use the internal Account Code and not the actual G/L account number.

Please use the SQL below to find the Account Codes.

SELECT AcctCode FROM OACT WHERE FormatCode = '11201000000000'

You need to use the values in the AcctCode field of the OACT table

LineNum column is only required for Update and can be left blank

Former Member
0 Kudos

Hi Suda,

There was a slight mistake in my account codes but the error is the same.

I ran your exact query "SELECT AcctCode FROM OACT WHERE FormatCode = '11201000000210'" and got the following:

_SYS00000000094

I presume this is the internal account code.

This now gives me more concern.

The import files are provided by an external application HR3PAY by HR3 and their software is certified to run with SAP B1 2005A, so I don't have the option of supplying internal Account code numbers only our G/L numbers and segmentation structure.

I know I am using 2007A but I am assured there is little difference in DTW between the 2 versions.

Has the requirement for internal Account Code changed since 2005A ?

Can the internal codes be changed to match the G/L codes ?

Thanks in anticipation,

Gary.

Edited by: Gary Bromley on Sep 15, 2008 6:53 PM