Author: admin

Select Checks Filters in GP PowerPack can dramatically reduce the amount of time required to create a PM Check Batch.

Create and save a query (aka a Filter) that identifies a group of invoices to pay, such as a list of Vendors from whom you purchase steel.  Once you create a Filter it is easy to use again by selecting it from a Lookup.

The list of search criteria includes:

• Batch ID
• Current Trx Amount
• Discount Date
• Distribution Account
• Document Currency
• Document Description
• Document Number
• Due Date
• Payment Priority
• PO Number
• Vendor Class
• Vendor ID
• Vendor Name
• Voucher Number
• Plus more…and all of the POP Receivings User Defined Fields

Select Check Filters can also import a list of invoices/vouchers to pay from Excel or SmartList.  Shown below is Select Checks Filter after reading a list of invoice to pay directly from a SmartList Favorite.

If you see an email from NetSuite trying to scare you about C++ and security and Dynamics GP, please consider this:

GP is NOT a web-facing application.  If a hacker is hacking GP they are already inside your system.  If they are inside your system you have much bigger problems than some theoretical development language security issues.  If a hacker is inside your system they are not going after GP, they’re going after your SQL database, emails, files, etc.

Are you concerned that a burglar can look in your medicine cabinet or are you concerned that they’re getting through your front door?

The Manufacturing Calendar windows (Shop Calendar and Work Center Calendar) are funny.  Have you ever looked at the years available in the “years” dropdown list?

The list starts with 1925!  Great Plains (what is now Dynamics GP) was not even created until at least 1930 and even way back then manufacturing planners had figured out that you cannot schedule work in the past.

Seriously though, consider that the list of years is “hard coded”–the original developer typed all of those years into the list when the window was created 90s, and look how far into the future it goes:

Yup, 2026.  So, somebody sat there and typed 100 years into that dropdown, filling it mostly with historical years that would not be used, and then only went forward to 2026.

What is even more astounding is that a developer can write a tiny bit of code to populate the dropdown list at the moment the window opens.  So instead of entering 100 years one at a time, you could have a bit of code that says: start today, count to 10 adding +1 to the year each time.  That’s it!  Now the list starts at today and goes forward ten years, and it will always do that.

Well, here we are getting close to 2026, the list is hard-coded and you are going to need to schedule manufacturing orders.  WilloWare’s got your back!

We just added a new TWEAK to MFG PowerPack called “Calendar Fix”.  The Tweak adds years to the drop-down so it goes out 10 years (User Date plus 10 years).  The Shop Calendar and Work Center Calendar are both covered by Tweak.

Lastly, the above situation is still true as of Dynamics GP build 18.6.1685, and any version of GP prior to that.

SmartList is a wonderful tool!  It makes it so easy to explore your GP data and once you get the desired columns, in the right order, with the Search Criteria you need you can save it as a Favorite for quick access.

And when you need to look at things slightly differently you create another Favorite.  So does everybody else.  Maybe somebody leaves the company and the new person does not know what all of the old Favorites do, so they create new ones.  Eventually your SmartList looks like this:

How do you go about cleaning this up?  Which Favorites are used?  Who uses them?  Can you delete them?

GP PowerPack has a new Tweak called SmartList Activity Tracker.  It watches which Favorites are used, counts how often they are used, when, and by whom.  The result looks like this:

Using this information, you can embark on a project to declutter SmartList!  Keep the things that are used and get rid of the unnecessary stuff you have accumulated over the years.

The Low Level Code (LLC) utility in GP Manufacturing calculates the lowest level at which any component is found.

For example, CBA100 is at level 2 and CAP100 is at level 3.  Material Requirements Planning (MRP) uses this LLC so it knows at which level it needs to start planning (i.e. start at the “top” and work your way down).

Imagine a situation where A uses B which uses C which uses B.  This is a circular Bill of Materials (BOM).  Normally Dynamics GP will not allow you to create this type of arrangement.  However, the LLC Utility has a bug that makes it think there are circular BOMs.

The LLC utility “Maximum Levels” setting provides a “fail safe” to address circular BOMs.  If the utility runs through the A–B–C–B loop 99 times it will stop.  When you look at the LLC code on Item Engineering it will show 99.  An easier way to see this is to look at the Item Engineering SQL table (IVR10015).

The bug in the LLC utility is that it does not traverse straight down each BOM.

When working down 100XLG it should retrieve the specific BOM for BA100G (in this case the MFG BOM for BA100G), and then the MFG BOM for CBA100.  Instead, it retrieves ALL BOMs for BA100G (i.e. the MFG BOM, ENG BOM, all CONFIG and ARCH BOMs).

This is a problem because you could legitimately have parts that can be changed into each other.  In the BOM above perhaps you MAKE BA100G using CBA100, but you also sometimes DISASSEMBLE BA100G back into parts.  You could use one of the Named BOM Types (i.e. ARCH or CONFIG) to store “disassembly” BOMs.  Now when looking at all available BOMs you have this situation:

You use CBA100 to make BA100G, but you can take apart BA100G to “make” a CBA100.

When the LLC utility is traversing down 100XLG it sees it contains CBA100.  At that point it grabs ALL BOMs and starts working down those.  That creates a circular situation because it can proceed down the ARCH BOM which takes it back “up” to BA100G.  It is then stuck in a circle.

WilloWare has a fix for the Manufacturing Stored Procedure in question.  If you would like it, please contact our support team.