web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Import Journal Entry

(0) ShareShare
ReportReport
Posted on by 50

Right now, all of our jounal entries are type into Dynamics GP manually from a spreadsheet.  I would either like to import them directly from the spreadsheet or a separate database table which I would setup through an integration package. 

How do I know what tables in Dynamics GP are being populated when a JE is done manually through the software?

I would think others are importing directly since doing it manually is becoming a big waste of time.  Any help would be appreciated.

Brian

*This post is locked for comments

I have the same question (0)
  • mm123 Profile Picture
    2,535 on at

    Hi,

    We have developed a automatic tool to import excel based Journal entries into GP. If you are interested in learning , please drop a email.

    Regards,

    MV

    nj.tech@hotmail.com 

     

     

  • callen Profile Picture
    4,595 on at

    The SDK provides the data flow for journal entries. The SDK can be installed from the second GP cd under the Tools folder. If you have the DVD, look for the Tools folder and then the SDK folder.

    Basically, the following tables are populated:

    SY00500 -- Batch table

    GL10000 -- GL Transaction Work (header)

    GL10001 -- GL Transaction Amounts Work (line items)

    You'd be better off using Integration Manager, SmartConnect from eOne Solutions, or some other established import tool.

  • Community Member Profile Picture
    on at

    Hi, I would seriously consider one of the integration products available for GP rather than writing directly to the Journel Entry tables themselves...Integration manager works well with straighforward transactions and you can import direct from a spreadsheet or ODBC to a table you create. Your other option is eConnect. The advantage of eConnect is that one failed document doesn't cause the whole integration to fail and you get excellent error messages as to why a particular document failed. With integration manager as its most basic, you might have to manually update the source data so that already integrated transactions are not re-tried..although you could write a script to update a value in the table. You can set the limit of failed transactions that willcause an integration to stop in integration manager for sure...but if you want a seamless integration tool...eConnect is the way to go. The disadvantages of eConnect is that any user can learn to set p integrations in Integration Manager, but you will need expertise with eConnect.

    Best regards,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans