(773) 384-9264  

Customer Feedback
  • "It’s been really nice working with you, Jamie and Ruby! Thank you for your continued support to Frank, Rimerman Consulting."

    Beverly MCSM (GP Partner)
  • "Thanks for the late-night support the other night!... Client was operating as it should this morning!   WOOO HOOOO !"

    Maureen ACAE (GP Partner)
  • "Have I told Alba-Spectrum this year yet how F A S T the newsletter selection is now ???? Wow. Thank you very much!"

    Dennis Westbrook
  • "We were successful last night in completing the production deployment of Terminations WF. Ricardo was fantastic and we could not have done this without him"

    Tawna KProject Manager (Credit Management)
  • "[We are] so grateful for Jeff’s help, and Jeff has been so good to...ZTrim in all of his support."

    John ECFO (Agricultural Ingredient Technology)
  • "First off, thanks for all the great suggestions. I’ll let you know what we find out. Many thanks for your help"

    Mark BDeveloper (Telephone Company)
  • "I will e-mail you back to let you know I was successful with HJE – which I expect to be. I really appreciate how you helped me."

    Michele DurkinConsultant (GP Partner)
  • "...thank you both for taking some time out to help me troubleshoot the issue of creating a project directly into the GP tables without the benefit of using the web services."

    Jesse CPrincipal (GP Partner)
  • "For example, when an AE calls to confirm rates, there’s not a 30 second pause waiting for the billing schedule to open. It’s absolutely immediate, literally, click, click, click. It’s a huge difference."

    Vince FCredit Manager (Media Data Service)
  • "So far everything seems to be working fine. We have had it in production now for almost a month and have not experienced any problems."

    Mark MFinance Manager (Custom Woodwork)
  • "Alba will always be my choice for quality innovation on ANY project you put in their lap from websites to Great Plains implementations, customizations and people who think 'outside the box'. "

    Robert DCEO
  • "Rod, your team’s flexibility and quality of service have been appreciated."

    Nicholas NController (Financial Trading)
  • "I most heartily and sincerely recommend him and his firm for any software implementation task."

    John PCFO (Tourism Association)
  • "[the] team delivered several enhancements to Great Plains, significantly improving our sales order entry process, shipment routing, and handling of catch-weight items."

    Eddie HPresident (Food Products)
  • "You have come very highly recommended by other companies. I have been impressed with your professionalism and attention to detail."

    Timothy CPresident (Uniform Manufacture)
  • "I am very happy that Andrew was able to fix our invoice system. Your company is very professional and performs excellent service."

    Allen ZCFO (Oil Company)
  • "I don't know who your company president is, but you guys did great job and I hope he/she sees this email."

    Nathan M.Finance (Marketing Communications)
  • "I heartily recommend Alba to any developer or end user seeking to make the most of their GP investment."

    Brett GPresident (Software Development)
  • "Thank you for all your patience and hard work getting this all processed. Here at Friedr Dick Corp we are looking forward to a wonderful professional relationship."

    Jill DAccounting Manager (Home Furnishings)
  • "I think we are going to be a great team working forward on the Miami project."

    Jesse CPrincipal (GP Partner)
  • "As usual, superb product and service!! Everything is working great and all my users love the modification. Thanks again!"

    Michael LController (Healthcare Storage)
  • "[W]e thought your product GP Posting Server was the better solution. The interface is better, it is easier to understand, and there are more options considering the auto transfer feature. We compared it to the Envisage Post Master Enterprise software."

    Tom BSenior IT Administrator (Medical Implements Company)

CMU FAQ

CMU supports the following Dynamics GP modules:

  • System and Company
  • General Ledger
  • Bank Reconciliation
  • Fixed Assets
  • Payables Management
  • Receivables Management
  • Inventory Management
  • Purchase Order Processing
  • Sales Order Processing
  • Invoicing

No. The standard procedure for running a merge is that all source companies and the destination company must exist in the same SQL instance.

CMU cannot merge companies across two or more SQL instances.  All source companies must be under the same SQL instance as the target company.  As a workaround, you can perform a GP migration to transfer the source companies to the same SQL instance where the target company resides.
The recommended is to merge twenty (20) companies at a time or in a single merge project run.  Merging more than one twenty (20) companies may result in performance issues depending on the size of the databases and resources allocated in the server.
The fiscal period, functional currency, and account format (number of segments and segment length) of the source and destination companies must be the same.  If there are discrepancies, the configuration in the source company needs to be adjusted using tools like PSTL before a merging is carried out.
During the pre-merge validation process in CMU, duplicate master files are recognized by CMU.  This allows the user to validate the uniqueness of the master files and modify the records before a merging is carried out.  When a duplicate record is found, the record from the source company will be combined in the destination company and the attributes in the target company will remain unaffected, maintaining their original state.  Except for Checkbook IDs and Bank IDs, these should be unique IDs from the destination company.  Otherwise, the pre-merge validation will fail, and the merge run will not proceed.  Modify the Checkbook and Bank IDs via PSTL prior to performing a merge run.  For more information, refer to the Company Merge Utility – Implementation Checklist document.  

For Budget IDs that are found to be duplicate, if not changed, will remain as is when merged to the target company. However, if the GL codes from the source company within the budget is unique from the Target company, then the budget amounts per unique GL account code from the source company will be copied over to the target company within the duplicate Budget ID in the target company.  The budget amounts in the Target company will remain as is and will not be updated.   
We have prepared an Implementation Checklist that will serve as your implementation guide for performing merge projects.  Identified in there are recommended hardware requirements at minimum, pre and post merge activities like reconciliation, banks and check links. This is a documentation that will be provided on the purchase of the software.
Yes, use the Append renumber transformation method.  When using the Append transformation method, the original document number is kept, and a suffix or prefix is added to the document number when merged to the destination company.  
Yes, use the Export Mapping Table report to produce the csv file of the mapping tables in a merge project.  Each mapping table contains the Old Values from the Source Company and the New Value in the target company.  You may refer to CMU User Manual for further details on how to generate the report.
Yes, the capability to schedule the execution of merges is available. You can specify the merge schedule within the Setup Execution Plan phase while creating the merge project. This allows you to define when the merge process will occur. By incorporating this scheduling functionality into the merge project setup, teams can efficiently plan and automate the merging of companies.
An Entity Assignment script from Binary Stream is being utilized within CMU.  However, each merge project is treated uniquely, hence we recommend reaching out to Binary Stream to define your requirements.  

In CMU, the Enable Entity Assignment should be set to Yes allowing to define the Entity IDs for each source company.  In Binary Stream’s Entity Assignment script, retrieve the Entity ID value from the ALBS_Mapping tables to map out the entity ID of the source company records.