Sales Transaction Distribution Entry Integration

[lpapa]

I wonder is someone can help me with an integration problem.

I am trying to automate the Sales/Receivables Entry using Excel2003 VBscript/sanscript (using MoveToField and SetDataValue commands). Everything works out well before I get to the Sales Transaction Distribution Entry form.

I cannot find the appropriate field name for the Distribution GL account in the scroll window. Is there a special way to handle this type of entry programatically?

Question:
1) Is using Excel and sanscript the best way to interface with Great Plains ver 6.00g52 Sales/Receivable Module? Is there a better way?

2) How do I enter multiple GL accounts in the Sales Transaction Distribution Entry form? I cannot seem to find the right field name for this.

Thanks,
Lpapa

 

[jazgeek]

integration manager accomplishes that

-----------
and they wonder why they call it Great Pains!

jaz

 

[lpapa]

Thanks Jaz,
As you can tell I am quite new to GP and integration. I will invest some time with Integration Manager. I see some samples I can probably use (RM Cash Receipts).

Do you know if Integration Manager always posts, or if we have the option to save only and allow a person to actually validate before posting?

Thanks,
Lpapa

 

[jazgeek]

I haven't worked with IM for a while, but I seem to remember that it only saves the document for you to review and post as a batch later (if that's the way your integration was set up)

Luvsql knows quite a bit about IM, so I'm sure she can answer your question better than I can.

-----------
and they wonder why they call it Great Pains!

jaz

 

[stef315]

The only type of transactions that integration manager posts automatically are ones that do not have the batch option, for instance bank transactions. Sales transactions are saved in batches.

Integration Manager is a much better way to bring in sales transactions although it's not a free module. It does have business logic validation though so you'll have less problems in the long run. You can map the fields from your source file to the Great Plains destination field in IM. If there is something that needs to be done to the data while importing you can do either simple translations or more complicated vbscript.

Lastly, I prefer to use text files as sources rather than excel files. With excel files, you have to set up named ranges within the file and then not mess with the range or IM screws up. It's a lot more touchy than text files which just read all the data until it gets to the end.

Good luck and feel free to post more questions.

 

[lpapa]

Thanks alot. This is been great to help me start out. I was unsure which option to use to integrate with Great Plains. I agree with using the text file instead of excel files. Much simpler approach. Thanks also about the post and save.

Little steps at a time. My next step is to determine why my Tools/Integrate menu options are greyed out (disabled). I am running the IM.EXE directly from explorer. As far as I know our MIS person registered the product properly.

Thanks,
Lpapa

 

[stef315]

Are you on version 7.5 or 7.0? There was an issue at one point where the Dex.ini file didn't get updated properly. Open the file and add the following lines (substituting the correct path):

IMPath=c:\dynamics\im\im.exe
ImExecPath=c:\dynamics\im\imrun.exe

 

[jazgeek]

lol...

I love the way bugs in GP are known as "issues"


-----------
and they wonder why they call it Great Pains!

jaz

 

[lpapa]

I found the dex.ini file and it did have a path defined for this value and the executable does exist in those respective directories.

The Great Plains version for eEnterprise is 6.00g52, and for Dexterity is 6.00m068.

Here is the contents of the ini file just in case you find something that sticks out.

Thanks again,
Lpapa

[General]
BuildSQLMessages=FALSE
NextEntryID=47
NextGroupID=47
IMPath=C:\Program Files\Great Plains Software\IM\IM.EXE
IMExecPath=C:\Program Files\Great Plains Software\IM\IMRun.EXE
Initial=FALSE
Workstation=WINDOWS
Workstation2=Windows
Synchronize=FALSE
WindowMax=FALSE
BTInterface=NoLoad
Pathname=DYNAMICS/dbo/
AutoDisplayUpdate=TRUE
DynHelpPath=C:\eEntrprs\
DexHelpPath=C:\eEntrprs\
DynHelpManualPath=C:\eEntrprs\Documentation\
DynHelpReportPath=C:\eEntrprs\Documentation\
ReportViewMode=2
FileHandler=SQL
SQLQueryTimeout=0
SQLProcsTimeout=0
DPSInstance=1
SQLRprtsTimeout=0
SQLLogSQLStmt=FALSE
SQLLogODBCMessages=FALSE
SQLLastDataSource=eEnterprise SQL
SQLLastUser=lpaparella
Dictionary Version=6.00g52
ZoomFontUnderline=True
ZoomFontColor=Blue
NoteWindow=37,37,450,299
WindowPosX=66
WindowPosY=87
WindowWidth=960
WindowHeight=700
MagnifyScreenOutput=100

 

[stef315]

Hey jazgeek, I think that's the same in all software. I call them "issues" because there's always something that can be done although it may not always be what we want. Anyway, I just find that negativity doesn't help much.

lpapa, your Dex.ini file looks fine. You just need to open the file, copy and paste those two lines I posted in the file, close and save changes, then start up Great Plains.

Let me know how it goes.

 

[jazgeek]

no worries stef315, I've been with this software since 3.15..... been through my share of "issues"

Merry Holidays to all.



-----------
and they wonder why they call it Great Pains!

jaz