Technical and Installation Discussions

[tmmorgan33]

I'm trying to import into the GL Journal Entry. The source file contains only the account number and the amounts. We had setup the import to runtime assign the batch number, source journal and posting date since this changes for the customer each time they import. Unfortunately, the fact that there is no header record in the source file is causing the error message seen above. There is a reported issue similar to this on Sage's knowledge base but it only deals with how to handle the error when a header record is present. It doesn't tell you how to handle where there is no header record available.

I am able to work around the issue by changing the batch number, source journal and posting date to replace and setting a default. However, I really need the runtime feature to work. Any input on this would be greatly appreciated.

[JimPetrie]

Are you actually attempting to import, or just testing the import?  I think you have to actually import rather than just test for it to work.

[LeslieMarrero]

I am also having the same problem, importing into the same file with the same type of source data.  Even with removing the runtime function, I can't get the import to work.  I tried importing it in WITHOUT a TEST and no luck.  Anyone else have any suggestions?  What has changed in 4.40 with the VI that it is now doing this?

[BigLouie]

---

LeslieMarrero wrote:

  Anyone else have any suggestions?  What has changed in 4.40 with the VI that it is now doing this?

---

As a Partner you should be talking with Scott Brady at Sage who is the "guru" for all things VI.

[DFeller]

I am having trouble with this too.

Dawn

[viperbri]

We ran into this problem on a SO import after an 4.4 upgrade and talked to Sage on it.  They had us remove all the instances in the record tab in the job and that solved our issue.  We were only important line item types of 1 so we were told we didn't have to have any criteria in there (even though I had always done that in the past). 

[BigLouie]

---

DFeller wrote:

I am having trouble with this too.

Dawn

---

When Dawn's having trouble with something, then it's serious.

[LeslieMarrero]

Big Louie, I have never spoken to Scott Brady and I wouldn't know how to reach him.  I did call Sage support on this issue and got a resolution.  My source file did not have a header,  I added a column with the source Journal.  In the import there has to be at least one REPLACE function for the header and I used the column I created for that.   All other fields like the posting date and comment I set them to RUN TIME.  According to Sage, I also had to look at the source file at the amount column.  Any amounts that were the same and right next to each other, I separated them by a few rows.  They said that when the two amounts are together, the import fails. Then finally it worked perfectly. 

I was told that its a problem and it was going to be submitted to Engineering.

[rmikolainis]

I have the same issue with the run time command.