You’re offline. This is a read only version of the page.
5
Hi!
We're on GP 18 R2 with Binary Stream's MEM.
We have been adding functionality to a manual e-connect based integration process we have to incorporate the MEM versions of the e-connect sprocs into the call.
The distributions for a particular invoice are shown below (from sql)
Segment setup is [Entity (mem)] - [Location (and Site)] - [doesn't matter] - [natural account] - [doesn't matter]
Everything is as expected in the distributions as compared to our previous import with one primary exception...
In the 'before' state the distribution on the first line, going to 150-196-00-21241-000, was instead going to 150-000-00-21241-000
The important thing to note is the second segment which is our location and 'site' in gp.
Site segment substitution is changing the default '000' segment for the sales records(41003, 43001) to the expected '196' and is leaving the AR record (Account 11201) with the default '000'.
However, the Tax record (account 21241) is being substituted to '196'. My (potentially incorrect) understanding was that site substitution should not have occurred for this balance sheet account.
How is site substitution "choosing" which accounts to substitute the site segment for and which to not since the AR record did not substitute and the Tax record did i am unsure?
Any insights about the "decision" process GP is making would be helpful.
Thanks much!
Hi,
If you open the MEM user contextual Help file in GP, and search for eConnect, it should return quite a few information about the use of MEM with eConnect.
However, the Help file is quite outdated as it appear to be referencing up to GP 2013 only. You may want to open support call with Binary Stream or your partner, since as a paying customer you're entitled to free support.
Share
Report
All responses (
Answers (
