Thursday, September 18, 2014

Going Beyond 5 Decimals

3d man sitting in front of question mark

Recently I was asked how to get Dynamics GP to calculate a unit price using more than five decimals. They were tired of constantly dealing with the few pennies of rounding differences.

Multicurrency to the rescue!

Since Multicurrency uses more precision when doing the translation, you can set up a new currency that will use many more decimals. Here’s how it went.

The problem:

The actual unit price of an item was $0.00491256. The system could only use the first five decimals, so they ended up with a price of .00491. If they were to sell 10,000 of these, the extended price would be $49.10 instead of the correct price of $49.13. Sure, GP can easily dispense with that extra 3 cents, but it’s a pain.

A solution:

Create a new currency (I’ll call it $NEW) with an exchange rate of .000001 set to multiply. Enter the sale using the $NEW currency. When the currency is translated into the functional currency, the desired value of $0.00491256 is used as the unit price.

When entering the transaction using the $NEW currency, you would use a unit price is $4,912.56. When the price is translated into USD, you end up with this: $4,912.56 * .000001 = .00491256. Problem solved.

Just as an aside, changing the unit of measure schedule was not a viable alternative in this case.

Until next time!

Leslie

Tuesday, September 9, 2014

Product ID and Product Name

The table below lists the various products that are commonly available on the Dynamics GP install DVD media. I got this list originally from the Dynamics GP worksheet prepared by Microsoft.

Product ID

Product

0

Dynamics

1

Dexterity

258

Project Accounting

309

Fixed Assets

346

Manufacturing

414

Human Resources

949

Field Service

1042

Interfund Management

1045

Revenue Expense Deferrals

1058

Cashbook (Bank Management)

1150

Scheduled Installment

1157

Collections Management

1235

Safe Pay

1428

Electronic Reconcile

1493

SmartList

1632

Cash Flow Management

1838

Technical Service Tools

1878

Excel-Based Budgeting

1911

HRM Solution Series

2150

Payment Document Management

2199

Business Activity Statement

2277

Purchase Order Enhancements

2416

Control Account Management

2547

Enhanced Commitment Management

2788

Enhanced Intrastat

2992

CopierSeries

3096

VAT Daybook

3104

Advanced Security

3180

Analytical Accounting

3258

Encumbrance Management

3278

Report Scheduler

3830

SmartList Builder

4067

ML Checks

4421

Grant Management

4522

Payroll Integration to Payable

4612

Advanced Go Tos

4621

Analysis Cubes for Excel

4933

Certification Manager

4955

Employee Health and Wellness

5597

HITB Report

5967

Fixed Assets Enhancements

5982

Export Financial Data

6499

Dynamics Online

6831

Date Effective Tax Rates

7131

Canadian Payroll

8811

Direct Debits & Refunds

If you look in the ‘upgrade’ section of Customer/PartnerSource, a worksheet is available that includes the products and their various build numbers.

Until next time!

Leslie

Monday, September 8, 2014

LOADING STORED PROCEDURES - Create_Requester_Procs_cursor

Technorati Tags: ,,

hanging_off_a_custom_street_sign_12007

Recently I did an upgrade from GP2010 to GP 2013 R2 (build 1745) and ran into a variety of problems.

I thought I’d share them here, in the event someone else is faced with the same issues.

Some background on the upgrade, we switched about everything you could:

 

  1. Switched SQL Server physical machines.
  2. Moved from a physical machine to a virtual server.
  3. The names of the servers, and the SQL server changed.
  4. Moved from Server 2008 to Server 2012.
  5. Moved from SQL 2008 R2 to SQL 2014.
  6. Moved from GP 2010 to GP 2013.
  7. Moved an eConnect web commerce application.
  8. Moved AVALARA’s web service.
  9. Several 3rd party products were involved.

After several attempts to do things that did not solve the problem, the following DID solve the problem. My thanks goes out to fellow MVP Richard Wheeler who gave me the tip to shrink the transaction log.

  1. Restore the databases to the new server
  2. Execute the Upgrade scripts suggested by Microsoft
    1. Account_Framework_Validation.sql
    2. Check_Workflow_Status.sql
    3. eConnect_Out_Setup.sql (this is really not necessary)
    4. Invalid_Records_POTables.sql
    5. Payroll_Work_Tables.sql
  3. Truncate the eConnect_Out_Setup table
  4. Shrink the transaction log of the target databases:
    1. DBCC SHRINKFILE ('DB_Log.ldf', 1), etc;
  5. Install Dynamics 2013 on the new Server
  6. Update the tables using DynUtils
  7. Import the eConnect_Out_Setup table records that were previously removed in step 3.

You most likely do not have to complete all of the above steps. But it worked for me, so I stopped.

I had done several upgrades before this one and never had a problem. I guess I just got lucky this time Smile.

Until next time,

Leslie