Author: admin

GP PowerPack 2021-02-11

Release Date: 11-FEB-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.151
* INV Tweak-Stock Calendar Years: Microsoft released a fix for the Stock Count Calendar window but it only covers GP2016 and GP2018. Our Tweak addresses the same issue for GP2013 and up. This release addresses another script on that window that has a hard-coded date that we did not address in the first release of this Tweak on 5-JAN-2021.

MOGenerator 2021-01-29

Release Date: 29-JAN-2021
GP Versions: 12/14/16/18
MOGenerator Build: 3.98
* NEW – MOGenV2 – A new comprehensive MO integration utility that provides the ability to Create new MOs, Rebuild Picklists, Reschedule MOs, add MOP-SOP Links, as well as to update/change most of the fields on the MO and run the Rebuild the Picklist/Reschedule the MO routines to account for the changes. The utility can use either an Excel spreadsheet for input, or a SQL staging table. This new utility is covered under the Core Utilities License.
* FULL INSTALL REQUIRED

GP PowerPack 2021-01-15

Release Date: 14-JAN-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.150
* Cash Receipt Report: (1) Created alternate versions of the reports that are formatted for emailing from the GP Print window. (2) Added support for printing the Cash Receipt report for posted receipts from the Cash Receipt Inquiry window. (3) This release uses new reports. If you were using modified versions of the previous release reports you will need to re-apply those changes using the new reports.
* FULL INSTALL REQUIRED: the new reports require updates to the GPPP Security Role and Task settings.

Learn more about the Cash Receipt Report.

MFG Import Release 2021-01-08

Release Date: 8-JAN-2021
GP Versions: 12/14/16/18
MFG Import Build: 2.48
* Routing Import: (1) fixed issue in Routing Header creation that could result in more than one routing being marked as Primary, (2) Added validation check and error reporting if import file has multiple routings marked Primary for the same item, (3) Added option to pad Routing Sequence to 2 characters, (4) Window now remembers the last used Routing Sequence Pad setting.

Extended Pricing SQL Locking

6-JAN-2021

A client site that uses our MO Receipt Integration (MORI) module recently reported a frequent occurrence of SQL deadlocking from a stored procedure called sopExtPricingPriceBookSetup.  Microsoft identified MORI as the source of the problem, however MORI does not use that stored procedure or have any interaction with Extended Pricing.

We found the source of the problem in the Dynamics GP Inventory module.  When ANY change is saved to an Item when Extended Pricing is enabled, the sopExtPricingPriceBookSetup stored procedure is called.  Posting an MO Receipt (with or without MORI) adds inventory to the system, which results in an update to the item’s Current Cost.  Saving that change to the Item Master causes the stored procedure to run…twice.

Viewing an item in Item Maintenance and clicking save (without making any changes) runs the stored procedure…twice.  Posting an Inventory Transaction or a PO Receipt also cause the stored procedure to run twice.  Any process in GP that makes a change to the Item Master will trigger the stored procedure to run, so it is running very frequently in any business that is inventory oriented.

The stored procedure appears to have been designed with the assumption that it would run only when creating a new item or making changes to an item’s UofM Schedule.  It deletes all information from IV00107 (Item Price List Options) and IV00108 (Item Price List) for an item where the Price Level ID is “EXTPRCLVL”, then repopulates the table.

For the SQL minded folks: in addition to locking the tables while it needlessly deletes and repopulates them, it uses two global (rather than locally scoped) SQL cursors, which means it will block itself if two calls are made to the stored procedure at nearly the same time.  On the other hand, since the stored procedure begins by deleting from IV00107 and IV00108 you would not want two calls to sopExtPricingPriceBookSetup to both have the ability to repopulate the tables simultaneously.

The issue was particularly noticeable with MORI because the module creates a large number of MO Receipts at a rate not possible if users were manually entering and posting transactions.  A site with a large number of users, or other automated integrations that touch inventory, could also be impacted by this Extended Pricing issue.

Fixing this is tricky.  The heart of the issue is in the GP source code in a “form” called IV_Item (specifically Commit() of form IV_Item).  It should not call sopExtPricingPriceBookSetup for ANY change to the Item Master.  It should only execute for changes to the UofM Schedule and a few other fields used by the stored procedure.  A second option that is less of a “fix” and more like a patch, would be to modify the stored procedure so it checks if repopulating IV00107 andIV00108 is necessary before it deletes everything.  This would technically resolve the issue but would also place an unnecessary load on the system.  Think about it this way–the stored procedure only needs to run when the UofM Schedule changes, which virtually never happens, yet it is running twice for every MO Receipt, Inventory Adjustment and PO Receipt.

There is a third option that was available to MORI.  Since MORI runs by itself on a dedicated GP client, our “fix” for this (which we released in a build yesterday) was to add switch on the MO Generator window to “Disable Extended Pricing”.  MORI now has a way to turn off Extended Pricing only on the GP client running MORI without affecting the rest of the system.

If you are using MORI and Extended Pricing, please download the latest build from www.willoware.com/downloads.

 

 

 

 

MOGenerator Release 2021-01-05

Release Date: 5-JAN-2021
GP Versions: 12/14/16/18
MOGenerator Build: 2.97
* Create MOs: added a new MOGen option called “Use OQM”. Order Quantity Modifiers. When this option is marked, MOs will be created using the OQM logic applied by MRP (i.e. an MO cannot exceed a certain quantity, so multiple smaller MOs will be created).
* Setup: added a new setup option to control whether the MO Gen Status window opens during the Create Child MOs process. The setup option defaults to true so that current behavior does not change (the window always opens). Unmark the option to suppress the window.
* MO Receipt Integration (MORI): a client site reported locking due to a stored procedure called sopExtPricingPriceBookSetup. If Extended Pricing is enabled, each MO Receipt makes updates to the Item Maintenance record (i.e. current cost), and each time a change is saved to the Item Maintenance record the Extended Price stored procedure is called. That stored procedure locks tables in the database which blocks other processes (such as other MORI instances, and other processes using Extended Pricing). This release includes a new option on the MOGen window (Disable Extended Pricing) that will temporarily disable Extended Pricing only on the GP client running MORI. Given that the stored procedure appears to be intended to run when creating a new item and/or changing the UofM Schedule, bypassing it only on the MORI processor should not have any effects on Extended Pricing. You may have observed this issue in a SQL Profiler trace as a large amount of activity on the SQL tables IV00107 and IV00108.  Disabling Extended Pricing affects ONLY the GP client running MORI, and it will be re-enabled automatically when the MOGen window is closed.  While Extended Pricing is disabled by MOGen, do not do anything else in the GP client (i.e. create a Sales Transaction).

GP PowerPack 2021-01-05

Release Date: 5-JAN-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 4.148
* NEW TWEAK-Stock Calendar Years: The Stock Calendar Maintenance window “years” dropdown stops at 2020. This tweak adds years through 2094.

GP PowerPack 2020-12-23

Release Date: 23-DEC-2020
GP Versions: 12/14/16/18
GP PowerPack Build: 4.147
* Shortage Inquiry: addressed issue that caused a SQL error when processing shortages for transactions (like an Inventory Adjustment) with hundreds of lines on the transaction. The change will also improve speed when processing very large transactions.

MOGenerator Release 2020-12-15

Release Date: 15-DEC-2020
GP Versions: 12/14/16/18
MOGenerator Build: 2.96

  • MO Create: Create MO: Added error report when CreateMO is provided with MOP-SOP Link information but the SOP Line does not have a QTY Backordered (or QTY To Backorder).
  • NEW: MO Receipt Integration (MORI): Added Excel import option. MO Receipts can now be created from an excel spreadsheet.
  • MO Receipt Integration (MORI): Fixed issue that affected partial receipts, and processing records that had one or more of a five specific validation errors. In these cases the processor would not automatically move to the next receipt, but rather abort the current process and wait for the timer to restart the MORI processor at the top of the next minute. MORI now immediately moves to the next record and continues processing. If you periodically experience situations where the processor is waiting even though there are pending receipts, this update will eliminate that wait time.

GP Stock Count Ends in 2020

17-NOV-2020 / Updated 5-JAN-2021

The Dynamics GP Stock Calendar Maintenance window has a “year” dropdown list that contains years only up to 2020. If you are using the Dynamics GP cycling counting functionality you will not be able to extend your Stock Count Calendar beyond the end of 2020, which means you will not be able to schedule a count that takes into consideration company down days or perform cycle count assignment.

 

The most recent releases of CompleteCount and GP PowerPack contain a fix for this issue that will extend the Calendar to 2094.

 

Download the update for CompleteCount and GP PowerPack from www.willoware.com/downloads

 

Engineer to Order Release 2020-11-04

Release Date: 4-NOV-2020
GP Versions: 12/14/16/18
ETO Build: 2.37

  • Updates for GP18.3 compatibility
  • ME Copy: (1) fixed issue that caused “This is not a made Item” warning when the ME is linked to a SOP Line and the Quoted Item Number already exists in GP so it does not have a Source Item Number. (2) added check that the ME does not already have Components and/or a Routing. Having either will now prevent using Copy.
  • ME Accept: If the ME is linked to a SOP Line, the Accept process will automatically create an MO for the Item and link it to the SOP Line.
  • Sales Link: When an ME is created from Sales Transaction Entry, the Sales Line Quantity will automatically be added to the Estimation Quantities and marked as Accepted.

SpellCheck Release 2020-10-30

Release Date: 30-OCT-2020
GP Versions: 12/14/16/18
SpellCheck Build: 1.27

  • This release uses a new Microsoft Cognitive Services Spell Check API that replaces the previous Bing Spell Check API. Microsoft will discontinue the Bing API on October 30, 2023. If you are using the GP Web Client with our SpellCheck, or use the web-based spell checking with the desktop GP client, you must update WilloWare SpellCheck prior to October 30, 2023.
  • Updates for GP18.3 release

MFG PowerPack Release 2020-10-21

Release Date: 21-OCT-2020
GP Versions: 12/14/16/18
MFG PowerPack Build: 4.164

  • Capable To Promise (CTP): Added options to control whether Unmet Demand is subtracted from the Available Inventory calculation, and whether On Order is added to it. Both options affect both the calculations in the Finished Goods window, as well as the Components window and the Max Build calculation. The new checkboxes are saved per User ID so that when the window is opened again they are still marked/unmarked.

LeanMFG Release 2020-09-14

Released: 14-SEP-2020
Dynamics GP Versions: 12/14/16/18
LeanMfg Build: 3.46
* GL Posting journals now use the posting journal setup options to control whether they print to screen, printer, file, etc.
With the release LeanMFG will uses the same build number (i.e. 3.46) for all supported versions of Dynamics GP. For example, the complete release number for LeanMFG on GP2013 is 12.3.46, and for GP2018 it is 18.3.46. The unified build numbering helps make more clear that the functionality in LeanMFG is the same across all supported versions of Dynamics GP.

Customization CR1069- Auto-Fulfill SOP Line from MO Receipt

Customization CR1069

Auto-Fulfill SOP Line from MO Receipt

Description of Need:

The normal Manufacturing Receipt posting process detects when an MO is linked to a Sales Line, and does the following:

  • It increases the Qty To Invoice on the sales line
  • It allocates the inventory in the GP Inventory tables

Additionally, ACME has Inventory Control set up to allow Adjustment, Variance and Transfer overrides, and SOP Setup allows Quantity Shortage overrides.

This leads to the following situation with serial numbered finished goods:

Sales Order 1 is entered before Sales Order 2. The MO for Order-1 is generated from SOP, and the MO Receipt is posted. This allocates inventory to Order-1, but does not FULFILL the line, so Serial #1 is still available.

When Sales Order 2 is entered, the shortage can be overridden, and Serial #1 selected for Order #2.

Even without the override scenario, if both MOs have been received, Order #2 can select the inventory produced for Order #1.

ACME would like the serial numbered inventory produced for a Sales Line to be both allocated AND fulfilled, so it is not available to other transactions.

Description of Solution:

There is no user-interface for this enhancement.

When an MO Receipt is posted, it will allocate inventory at the Item Number level, and will also fulfill each SOP Line with the Serial Number(s) produced by the MO linked to the SOP Line. This will:

  • Update the Qty Fulfilled on the sales line
  • Populate the SOP Serial/Lot table
  • Update the Qty Sold in the Serial Master table

The auto-fulfillment will ONLY occur when the MO Receipt is for a serial numbered finished good.

For information on this design spec, or any other WilloWare customization or product, please contact us at:

www.willoware.com/contact-me/

MFG PowerPack Release 2020-08-14

V12/14/16/18 build 4.160 14-AUG-2020
* Sales Forecast Integration: Fixed issue with reading dates from Excel that caused SFI to not see dates in the excel column headers resulting in SFI reporting that the import spreadsheet has fewer dates than the forecast.

Customization CR0996 Return Caps

Customization CR0996

Return Caps

Description of Need:

ACME needs to place a cap on dollar value of product a customer can return in a set period. No automation is required to enforce the cap values.

Description of Solution

Navigation: Tools>>Setup>>Sales>>Return Cap Setup

Field Function
DONE Closes the window
Setup Option There are two Setup Options

  1. Excluded Customer ID’s– Customer entered here will not be evaluated for a potential return cap.
  2. Included Return ID’s– Return ID’s entered here will be used to determine if the customer on the return should have a cap.

A return or customer can be deleted from this window as long as there are no pending or posted returns within the cap period for the selected return or customer.

CAP Transactions

Pending and Posted Returns will not be tracked within the enhancement, rather the transaction amounts are to be queried on demand using the open/historical SOP header table. A Field Service RMA will be recorded against the cap once the RMA is received and the GP Return has been created. The SOP Returns that are linked to the SVC RMA module must be entered in the Return Cap Setup window to be considered in the calculation. This enhancement does not consider SVC RMAs not yet received against the cap.

A SQL View will be included as part of this enhancement so ACME can use it for SSRS reports and Smartlists. The view will contain the following fields:

Customer ID

Cap Amount

Pending Transactions

Posted Transactions

Customer CAP Summary

Navigation: Customer Maintenance>>Additional>>Return Cap Summary

Field Function
OK Closes the window
Customer ID Displays the Customer ID from the Customer Maintenance window
Cap Amount Displays the Cap Value from an Extender window maintained by ACME. Upon project approval, ACME will supply WilloWare with the window and field IDs so it can be retrieved by the enhancement. This field is not editable from this window, and is not saved in the customization.
Pending Amount Displays the unposted document amounts for all Returns that belong the Customer ID.
Posted Amount Displays the posted document amounts for all Returns that belong the Customer ID. A posted Transaction will only be considered if it’s document date falls within the current calendar year.
Remaining Cap Displays the cap room left. If the customer has more returns than cap amount, this value will be negative. It is calculated as:

Cap Amount – (Pending Amount + Posted Amount)

Assumptions/Requirements:

  1. The functionality described above is intended for the GP Desktop client.
  2. Unless otherwise noted in this document, reporting is not included in this estimate.

For information on this design spec, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me

Customization CR1181 Default Price to Lower Quantity Price Break

Customization CR1181

Default Price to Lower Quantity Price Break

Description of Need:

When a Purchase Order line is entered and the quantity is not set up as a price break, ACME would like to remove the warning message “No Vendor Pricing exists. Add it to the list or select an existing price break.” In its place, the cost of the of the break lower than the quantity to be used.

Description of Solution:

Solution as described above. For example, if the vendor is setup with the following price breaks:

And the user enters 15, the line unit cost would default to $1,000.

Note: If the user enters 5, then there will be no cost to use, so in this case, the warning message box WILL appear.

Assumptions/Requirements:

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
  2. The functionality described above is intended for the GP Desktop client.
  3. Unless otherwise noted in this document, the enhancement will not integrate with 3rd party products. Some examples of 3rd party products would be:
  • An ISV plug-in product, including WilloWare products
  • A dexterity customization designed by another developer
  • Dynamics GP Modules, including, but not limited to:

-Copy functionality found in SOP, POP, and Inventory

-Field Service

-Extended Pricing

-Manufacturing

For Information about this Design Spec, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me

Customization CR1085 Sales Email & Print

Customization CR1085

Sales Email & Print

Description of Need:

ACME always emails an Order from Sales Transaction Entry, but sometimes they also need to print a copy for internal use. Since GP clears the window after emailing (or printing), doing both requires re-loading the document. ACME would like a way to more easily email & print an Order.

Description of Solution:

When a user clicks the Email button on Sales Transaction Entry, and they are viewing an Order, they will be prompted:

Do you want to also PRINT this document?

If they answer YES, the system will automatically open and populate the Print Sales Documents window.

The window will be set up to print the same Order that was just emailed. GP becomes “frozen” while the email is sending, but as soon as GP becomes available again, the user can client the PRINT button on Print Sales Documents to send the Order to a printer.

If they do not want to print, the Print Sales Documents window can just be closed.

Users must have security access to the Print Sales Documents window. If they do not, they will still be asked if they want to print, but then they will receive a warning that they do not have access to the window.

For more information about this design spec, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me