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)

eConnect and Intercompany Journal Entry - Does not exist???

(0) ShareShare
ReportReport
Posted on by 7,365

Am I missing something or does eConnect really not support Intercompany Journal Entries?  Does anyone have a workaround?  Would it work to do a regular journal entry and then do some SQL updates to the GL10000 to mark the Intercompany flag and then manipulate the distributions table?  Does the Intercompany Process deal with the Due - To / Due From Accounts at the time of entry or the time of posting?

 Kevin

*This post is locked for comments

I have the same question (0)
  • Michael Marinaro Profile Picture
    9 on at

    Hi Kevin,

     There are many out here with far more development experience than I have, but to my knowledge, there is no way to import an intercompany journal entry using eConnect.  In the past I have worked around this issue when importing PM transactions by creating a journal entry in the destination company as part of my eConnect routine when an intercompany transaction was called for.  Unfortunately, this means that the transaction is not flagged as intercompany in Payables Management. 

    Alternatively, Integration Manager will work but it will be a manual import and will not be as fast if you're importing many transactions.

     Just out of curiousity, what are you trying to achieve?  In you post you made it sound like you are entering the transaction through the front end ("...do a regular journal entry...").  What is the need for eConnect?

    Mike

     

  • K Day Profile Picture
    7,365 on at

     It's basically a big customization that uses PO Processing (non inventory) with intercompany processing similar to Payables Management Intercompany.  Upon posting a batch of Shipment Invoices, we need to record the expenses into one of several companies.  The goal was to automatically create an intercompany transactions in the batch based on the customization, except I just assumed that I would be able to use econnect for the intercompany journal entry.  Then I realized that functionality didn't exist.  So I'm just using the standard eConnect Journal Entry nodes and then running a few procedures to turn them into intercompay journal entries after they are created.  Its actually pretty easy.  Set the intercompany flag in the GL header table and then set the values of the interid and look up the account index in the destination companies for the GL line table.

  • Michael Marinaro Profile Picture
    9 on at

    Sounds good.  We ended importing the PM document with the expense distribution to the due from interco account (from the intercompany accounts table in the DYNAMICS database) and then imported a GL journal entry to the destination company with the expense and due to interco account for each document (of course using multiple JEs if the doc was split to multiple companies) all as part of a single eConnect routine.  Your method is a little bit better because it actually flags the JE's as being intercompany whereas our method doesn't however MS generally frowns upon direct table manipulation so we can't really recommend that to our clients. 

     

  • K Day Profile Picture
    7,365 on at

     If Microsoft didn't want me to manipulate the tables, they should have given me an intercompany journal entry eConnect node!!  Ha.   We actually have tons of customizations and many integrations are direct table imports left over from before the days of eConnect.  We just so many different ERP systems feeding into GP that we have to do what we can to make it work.  We are trying to migrate some of these customizations to eConnect now though and use it exclusively moving forward.

  • Ed Rossy Profile Picture
    30 on at

    K Day,

    Would you mind sharing the code you are using for the following:

    "So I'm just using the standard eConnect Journal Entry nodes and then running a few procedures to turn them into intercompay journal entries after they are created.  Its actually pretty easy.  Set the intercompany flag in the GL header table and then set the values of the interid and look up the account index in the destination companies for the GL line table"

    I am in a situation that requires your exact solution.

    Thanks

    Ed

  • Verified answer
    KevinD Profile Picture
    215 on at

    I actually am working for another company now and don’t have the actual code handy, but I can give you the basic theory.

    What you want to do is to use the standard eConnect Code to create a journal entry and then manipulate it in the tables after it is successfully created.  I suggest as a model that you do a regular journal entry with 2 lines and then an Intercompany one with 2 lines and look at the difference in the Tables.  GL10000 and GL10001.  Find out what makes one a normal JE and what makes the other intercompany.  The main difference is that you flag the intercompany as a 1 in the Intercompany Field, set a flag for “Has Intercompany Distributions” and then you will need to provide the database ID and the Account index from that Destination database ID.  It’s pretty logical with some dynamic SQL and a little temp table in SQL or .Net.  Some of the other ancillary things you need to do depending on your configuration (best practices) is look in DYNAMICS to make sure an intercompany relationship exists between the 2 companies, make sure the accounts in the destination company are active, allow account entry, etc…  You should know all of the entries you want to make ahead of time so you can figure out how to pass that information through .Net.  For example, I might call a function called CreateJE using a dataset, use some constants for accounts so the JE gets created successfully (like all to the same account), then call another function (like UpdateJEToIntercompany) that will update the records for that JE # with the real accounts you want to use.  You should know the account string in the other company you want to use, look it up the GL00105 in the destination company to get the Account Index.

    You don’t have to worry about the Due To / Due From Accounts because GP will do those automatically upon printing the edit list or posting.  That is just part of GP.  You just need to make GP know that it is an intercompany transaction on the unposted transaction by switching the flags and providing the correct information (INTERID and Account Index).

    I'll check around for some of the code I used.  Drop me an email at kevinday17@yahoo.com if you still ahve any questions.

  • Verified answer
    Mohammed Vayalil Profile Picture
    150 on at

    Kevin, Followed your steps and it worked, I like the way you thought through.

    I used eConnect Post stored procedure to accomplish the same.

    Code ref:

    1. taGLTransactionHeaderInsertPost

    UPDATE GL10000

    SET ICTRX=1, ICDISTS=1

    WHERE JRNENTRY=@I_VJRNENTRY

    2. taGLTransactionLineInsertPost

                   UPDATE GL10001

    SET ACTINDX=@I_VUSRDEFND3,

    INTERID=@I_VUSRDEFND2

    WHERE JRNENTRY=@I_VJRNENTRY AND SQNCLINE=CAST (@I_VSQNCLINE AS NUMERIC (19,5))

    Created, posted & intercompany destination came through upon posting.

  • KevinD Profile Picture
    215 on at

    Glad it worked.  You can actually do the same thing for AP Transactions turning them into Intercompany Transactions because the same general logic applies.  Flag it as intercompany, update the Database ID and the Account Index from the Destination company in the Distributions table, and GP will just pick it up as a real intercompany transaction.

  • Douglas Karel Profile Picture
    2,140 on at

    Because it was not a standard econnect node, one of our clients using SmartConnect, had to then buy SmartConnects Node builder to create the node.   Then we could use that node in smartconnect to create the mappings.  

    I also could not believe the steps to go through regarding importing intercompany transactions.

  • Mohammed Vayalil Profile Picture
    150 on at

    SmartConnect nodes is a good option,that way client will feel better.

    Along with eConnect, I have used SC nodes  to push extender data.

    Would you mind to share which specific node did you use for inter-company?

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