Sage 100

Second issue same customer GL Exchange - Sage 100 STD v4.4.0.5 Customer is using the Alternate format to import GL transactions. They supply a 7 character journal number. Sage on the import (GL Exchange) takes: first 4 characters precedes those 4 characters with zeroes (I think two) Am not realizing why I rarely use GL Exchange Customer wants to know why the system doesn't take the full 6 and truncate just the last character Example: Wants to import journal 8010413 (7 characters) Expects it to pull in: 801041 (truncate 3) Sage Exchange pulls in: 008010 I suspect this is: a. WAD b. GL Exchange fluke

What format is the source file for the import?

I believe it's the alt - the one used when you have a 9 character GL

Sorry should be more clear - its is an Excel or text file?

csv

I opened it in notepad and it looked fine

I've had success using Excel files. Here's a template I use:

Thanks @MoiraGoggin that's a nice template.

I'm not sold that it's a template issue since the mapping for the journal number for an ALT format shows 4 characters. The exchange import takes the first four (which I'd expect) and it's prepending it with two zeroes (which I didn't expect).

I don't disagree with you @WayneSchulz - true alt format use 4 characters for the journal and left pads to 6. What I've done in the past, using this template, is to add a task button for the user to open the GL Source Journal maintenance so they look up the next new entry, number for the source journal (in this case JE) and then plug it into the template. I just provided the template in case you wanted to use it.

Thanks Moira - the other issue we are encountering is that the next source journal number is not automatically incrementing (within source journal maintenance -> Next Number). It almost appears based on a KB entry that the source journal number only increments when the ""next"" button is used on an AJE.

Oh my gosh, I'd never noticed that. I just ran a test manually enter journal # 20, even though 19 is the ""next"" one. The only good news is that it does show the last journal number in the grid.

The problem here is when the customer uses a mix o manually entering the source journal number (which doesn't advance the ""next journal"" and uses the "" # "" button to get a next journal number (which does advance it). What I believe also occurs is if you use GL Exchange to pull in an entry the source # is not automatically rolled forward (i don't think there is a way to trigger GL Exchange to take the next source # as there is with VI). Or if there is a way my customer hasn't found it.