Professional Services Tools Library PSTL - Item Number Combiner Error

When using the item number combiner feature of the PSTL, you might encounter an error indicating that there is an invalid object name which is DYNAMICS..syscolumns . As a result, the process is interrupted and will fail to deliver the required results. The encountered errors are included below:

Dynamics..syscolumns

Procedure TACallItemCombine

 

The stored procedure that is designed to manage the whole combine task is "TACallItemCombine", it is encrypted and can not be checked. The error is primarily due to having a static "SQL statement" within the code checking DYNAMICS..Syscolumns. Although, in certain environment the DYNAMICS db itself could have a different name due to the new feature of changing its name. As a result, this process will break up in the middle achieving no results at all.

Item Number Combiner

In my environment, I had Dynamics GP 2015 and the database names are as follows:

• GP Company : GP15R
• Dynamics Company: DYN15

Therefore, the procedure failed to find an object in a database which name is DYNAMICS, and eventually fail. 

In order to work this out, I have created a dummy database with the name 'DYNAMICS', just to force the procedure to proceed since it is encrypted and can not be altered.

Best Regards,
Mahmoud M. AlSaadi

Dynamics GP 2015 RTM – PSTL InValid Versions

Recently, PSTL related case was reported on the community for clients who upgraded to Dynamics GP 2015, it seems there is a problem with the version number of this product and associated dictionary files. Here are the errors:

“InValid Versions ! This version of professional services tools is only compatible on GP 2013”

---

Important Note !
This is not an upgrade issue, it occurs with new installations of GP 2015 as well.
Special Thanks to Heather Roggeveen on this finding !

---

The PSTL loads the form after prompting the message above, then it gives another error message as you click on any of the tools, it indicates that the utility is not registered.

“You are not registered for this selected utility”

 

Resolution
This was reported as a known issue by the support team, and a chunk file was provided on the partner source to get this resolved. To resolve this problem, follow the steps below:

1. Initially, go to control panel and remove the PSTL from the add remove features.
   
   
   
2. Once the PSTL is removed, proceed and download the chunk file from the partner source. Here is the download link. Remember, you need a partner source account. So if you only have a customer source account, refer to your partner to provide you with the download file accordingly.
3. Unzip the the PSTL_GP_14.0.3_Release.zip file (downloaded in the previous step), and put it in your installation folder on the default path (C:\Program Files (x86)\Microsoft Dynamics\GP2015)
   
   Helping Note !
   Take a back up of the whole installation folder before placing the chunk file within, it is quite important before running the new code.
4. Run Microsoft Dynamics GP as an administrator, you will be prompted with a message that new code must be included in the installation folder, click “Yes” to proceed
   
   
5. Why Microsoft Dynamics GP is open, if you see “Customer Exception” instead of PSTL. Have a back up of your dynamics db and company db, and run the script below:
   
   USE DYNAMICS
   DELETE SY07130
   
                             
6. Now open Microsoft Dynamics GO to find the PSTL instead of the customer exception tab.
   
   
    

Best Regards,
Mahmoud M. AlSaadi

Customer Combiner Utility

 

The customer combiner utility is used to combine an existing customer to another existing customer, the source customer is removed from the system while summary information are recalculated for the destination customer, and here’s a detailed illustration of what happens.

1- Customer Card

The two customer apparently have different details in customer card, which can be categorized as below;

• Informational Fields (name, short name, address, country, city, payment terms …etc.)
• Accounts (AR, Sales, Cost of Sales …etc.)
• Options (Credit Limit, Maximum Write off, Minimum Payment, Rate type, statement cycle ..etc. )

All the details of the source customer are removed from the system, while the destination customer card is remained as is.

For instance, credit limit of the destination is not updated to be the sum of both, and the same as well for all definition fields.

Note:

If the two customers are assigned to different currencies, you will not be able to combine them unless both of them are assigned to the same currency.

2- Customer Summary

The summary information (RM00103) are updated for the destination customer to be the sum of both such as (Customer Balance, Aging per amount, Total sales LTD, YTD… etc.)

 

3- Customer Transactions

All the transactions’ details are kept the same with no update on any of the fields. Only the Customer ID field of the source customer is updated with the id of the destination customer.

In this essence, the destination customer will have the balance of both (as shown above) and the unapplied amount (current transaction amount) of both as well.

 

Best Regards,
Mahmoud M. AlSaadi