MEM stands for Multi-Entity Management®, a product written for Dynamics GP by Binary Stream Software. This product allows organizations to manage multiple legal entities (companies) in one single database. The facility is assigned as payables transactions are entered or batches created.
What does the MEM Connector do?
The MEM connector provides an interface between MEM and Mekorma so that facility information can be printed on payables checks. The software uses SQL scripts to access Binary Stream tables to retrieve the necessary information.
Depending on which version of Multi-Entity Management is set up for your company, you will find the facility (entity) fields for payables in either the MEM Centralized category, or the MEM Decentralized category. Payroll can only use the Decentralized category.
MEM Centralized: A Centralized process uses one checkbook to pay multiple entities. Transactions for multiple entities can appear on one payables check. In this case, the Facility Name or ID will be printed on each voucher line. Facility Address is generally not used in this setup. For correct alignment of columns on the check stub if using subtotals, the connector provides common voucher line fields which must be used with the Facility ID or Name when creating the stub layout.
MEM Decentralized: A Decentralized process uses multiple checkbooks to pay multiple entities. Only one facility is reported per check. The Facility Name, ID and Address will be printed in the header area of the check or stub.
Please note: Binary Stream has changed the process for entering and storing a legal name for entities when using MEM for Payables in Decentralized mode. The Facility Company Name should now be retrieved from the BSSIEntityLegalName column of table B3900400 starting from the MEM version listed in the table below.That is, entity description will be printed with entity legal name.
|A1||GP Version||MEM Version|
|2015||14.00.1079||506s11 (and later)|
|2016||16.00.0404||601s05 (and later)|
|2018||All Builds||All Builds|
All prior versions should use the former process, which retrieves the entity name from the GL Segment table (GL40200).