Author: admin

CompleteCount 2021-07-29

Release Date: 29-JUL-2021
GP Versions: 12/14/16/18
CompleteCount Build: 3.51
* NEW TABLE added with this release. The COMPLETE INSTALLATION ROUTINE is required.
* Stock Tag Inquiry: can now view both unposted and posted Stock Tags
* Excel Export/Import: (1) added Counted By column in the export/import file (2) imported file name information is now retained with the Stock Count and moved to Stock Tag History when the count is submitted. (3) addressed issue with the Excel Import routine that could leave a stranded Excel process with a file lock on the import file.

MFG PowerPack 2021-07-28

Release Date: 28-JUL-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.178
* Edit MO Status (EMOS) Query: Add Copy/Paste function that supports pasting a list of MOs into the EMOS Query window which can be used to restrict the MOs shown in the Edit MO Status window (CR1334).
* NEW: SOP Number to MO Number: MO’s created from Sales Transaction Entry will be created with the SOP Number and a SOP Line Number (such as ORD1227#0001).

Customization CR0457 Automated Forecast

Customization CR0457

Automated Forecast

Description of Need:

ACME Would Like:

  • Ability to specify Item Classes to include on a Forecast. Specify the item classes linked to a specific Sales Forecast ID.
  • Specify number of months forward to forecast. Forecast quantity is the quantity sold for the same period the previous year.

Requirement:

  • User creates a Forecast “header” containing the Plan Name and Forecast Period. The Start Date/End Date are not important as those will be calculated and updated automatically.

Description of Solution:

Navigation: Tools >> Utilities >> Manufacturing >> Auto-Forecast

Field Function
Plan Name User selects an existing Manufacturing Sales Forecast. The following information must be on the Forecast:

  • Plan Name
  • Period (Quantity and Type, i.e. 2 Weeks)
  • Forecast Start Date

The Forecast End Dates and History Start/End Dates are not important and will not be used. The Forecast End Date will be set automatically when the Auto-Forecast utility is run.
Forecast Periods This is the number of periods to forecast forward.

If the period is “2 Weeks” and the desired forecast should cover 1 year, Forecast Periods should be 24 (i.e. 24 two-week periods.)
Item Class The Item Class or Classes to include on the forecast. All items in the Class(es) will be forecasted and added to the forecast.
SAVE Saves the Auto-Forecast information
UPDATE The user will be prompted to confirm they are ready to update the Forecast before it proceeds. See below.

The forecast quantity will be calculated from sales history for each item during the same period during the prior year. For example, if forecasting 5/1/2020 to 5/14/2020, the total sales (less returns) will be pulled form 5/1/2019 to 5/14/2019.

The first time the utility is run, or if a new item is added to the class, all periods will be populated on the forecast from available sales history (or filled in with zero). For an existing forecast, historical periods will be filled with zeros until the current period is reached. Then all future periods will be populated with data from sales history.

The period size (i.e. 2-weeks) will be used from whatever is on the Sales Forecast. The number of periods to forecast will be stored on the Auto-Forecast window, above. Each time the utility is run, it will add “new” periods to the end of the existing forecast without changing numbers for any currently forecasted periods. Therefore, if it is one month later than the last time the utility is run, and it is forecasting 1-year, the utility will add 1-month to the end of the forecast.

Update

The update process will check if any new items need to be added to the forecast based on the Item Class. If not, the items on the forecast will be used to drive the forecast. If a user manually adds items to the forecast, those will be included in the Auto-Forecast update.

For each item, the utility will:

  • Find the last forecast period on the forecast
  • Calculate how many additional forecast periods need to be added
  • Get sales history for each one of those periods
  • Add the sales history to the forecast
  • Update the Forecast End Date

For Information on this, or any other WilloWare customization or product, please contact us at:

www.willoware.com/contact-me

MOGenerator 2021-06-18

Release Date: 18-JUN-2021
GP Versions: 12/14/16/18
MOGenerator Build: 3.102
* MO Receipt Integration (MORI): (1) Added ability to include service type items when importing a picklist for an MO Receipt. This can be done only for Actual Cost finished goods.y (2) Imported Picklists (ImportBOM=TRUE) can now be brought in without lot/serial numbers and the system will auto-select lots/serials.

MFG PowerPack 2021-05-21

Release Date: 1-JUN-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.176
* Vendor Pricing: (1) Addressed issue in the Select Cost window that resulted in the cost being displayed at $0 or at an incorrectly rounded amount. (2) Added controls to prevent user from having more than one “create PO” window open at a time, such as PO Entry and Request Resolution. This is required because the Vendor Pricing windows cannot manage pricing for two different PO creation processes at the same time. (3) Addressed issue that caused incorrect cost retrieval when creating a PO for a foreign currency Vendor but using the functional currency.
* PowerATP: Added a new field called Free Forward Date which shows the first date after which there are no shortages for the item.

MFG PowerPack 2021-05-21

Release Date: 21-MAY-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.175
* Capable To Promise (CTP): resolved issue that started in build 164 that prevented the CTP window from exporting all rows to Excel.

MOGenerator 2021-05-12

Release Date: 12-MAY-2021
GP Versions: 12/14/16/18
MOGenerator Build: 3.101
* MO Receipt Integration (MORI): a manufacturing procedure called mmopAllocateAll sometimes reports an error condition that indicates an MCTE Allocation transaction was NOT created when in fact it did create the transaction and allocate inventory for at least some of the items on the Picklist. Previously MORI would report an error from this as “Component Quantity Shortage”. This release changes the error message as follows: “mmopAllocateAll error (#). Reverse Allocate PickDoc XXXX”. It will report the error number returned by mmopAllocateAll for use in trouble-shooting by WilloWare. When this occurs, Manufacturing may have created an MCTE Allocation transaction which should be Reverse Allocated. # = error number. XXXX = PickDoc Number.

MFG PowerPack 2021-05-03

Release Date: 3-MAY-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.174
* Serial/Lot Mass Generate: the new GP “list view” displays for available serials and selected serials appear to crash when rapidly inserting around 60 serial numbers. This release addresses the issue in all affected GP Serial Entry windows(#202100593).

MFG PowerPack 2021-04-22

Release Date: 22-APR-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.173
* Time Card: (1) addressed issue that could prevent auto-tab from moving to the correct field. (2) NEW: Added integration to GP Manufacturing’s Automated Data Collection. Enabled in Time Card Setup, data recorded through the Time Card window will add records into the ADC table (SF010550) which are then picked-up by the ADC processor and turned into labor/machine transactions for the MO.  TimeCard executes the ADC processor automatically which eliminates the need to set a GP client as the “Data Collection Processor”.

MFG PowerPack 2021-04-20

Release Date: 20-APR-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.172
* Vendor Pricing: addressed an issue with the last change to Vendor Pricing that caused it to load a price into the PO Line before a quantity was entered and then prevented changing to the correct price.
* Item Copy: Scrap Accounts from the Scrap Reporting module are now included when copying Item Maintenance
* Limited User: all windows in the suite are now available to Limited Users.

MFG PowerPack 2021-04-16

Release Date: 16-APR-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.171
* SOP Backorder All – The software was not correctly reading the registration key for this feature, causing it to always be enabled regardless of whether or not it was enabled in the Setup window (#202100549).

MFG PowerPack 2021-02-26

Release Date: 7-APR-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.170
* Vendor Pricing: (1) The GP POP module uses the “last unit cost” of an item, and multiplies UP to arrive at the UofM Cost (i.e. calculating a CASE cost based on the EACH cost). Since Vendor Pricing supports pricing at different UofMs, this could result in a loss of accuracy at 5-decimals when calculating DOWN from a UofM Price to the Base Unit Price needed by POP. This release addresses that situation by checking that POP arrives at the correct UofM Price and fixing it if necessary. (2) Zooms now pull through the UofM along with the Vendor and Item. (3) The Select Cost window now shows the cost in the Item’s Currency Decimals.

GP PowerPack 2021-03-30

Release Date: 30-MAR-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.152
* BE-Bank Deposit Filters: The Save, Clear, Delete, Post and Print buttons are now locked while the Advanced Filters window is open. This addresses an issue where the deposit number can be cleared from all records in CM30200 if (1) filters are selected in the Advanced Filters window, (2) The Redisplay button is clicked, and then (3) the Delete button is clicked on the Deposit Entry window (#202100425). Further testing found that other combinations of actions involving the toolbar buttons while Advanced Filters was open could result in either clearing or overwriting the deposit number.

MOGenerator 2021-03-26

Release Date: 26-MAR-2021
GP Versions: 12/14/16/18
MOGenerator Build: 3.99

* MOGen status table: update frequency increased so that time/date stamp updates with each MO processed rather than each processing “loop”.
* Fixed issue with registration key that prevented MORI – Excel from appearing in the dropdown list
* Added check that fiscal periods are open before attempting to create/post MO Receipts

LeanMFG 2021-03-06

Release Date: 6-MAR-2021
GP Versions: 12/14/16/18
LeanMFG Build: 3.49
* MOEntry: Adjusted calculations performed when allocating costs to multiple outputs to improve accuracy when percentages extend to 5 decimals. The calculation change affects allocation by Quantity, Shipping Weight, and Fixed Percentage.

MFG PowerPack 2021-02-26

Release Date: 25-FEB-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.169
* Vendor Pricing: (1) Added option to use Future Price Lists. Disabled by default so normal functionality is not affected. When enabled, Vendor Pricing will pull pricing from a future price list based on the Release By Date. (2) Added User Defined Fields to Price List Maintenance. Each Price List can now have 8 string fields, 4 numeric fields and 4 date fields.
* FULL INSTALLATION PROCESS REQUIRED WITH THIS BUILD

LeanMFG 2021-02-22

Release Date: 22-FEB-2021
GP Versions: 12/14/16/18
LeanMFG Build: 3.48
* MOEntry: (1) changed behavior of Output QTY field for Lot Controlled items. Previously if a Lot Number had been entered for the Output QTY, and the QTY was subsequently changed, it would remove the Lot Number(s) and require re-entry. Now if there is only one Lot Number, it will keep the Lot Number and adjust the Lot Quantity automatically. (2) Fixed Output line ser/lot indicator so it does not disappear after changing the Output Qty.

MFG PowerPack SOP Backorder All

Price $1800 Manual

SOP Backorder All overrides the normal document allocation and fulfillment logic on Sales Orders so that regardless of any available inventory, the Quantity Ordered is set to Backordered.  This is particularly useful with GP Manufacturing when all finished goods are made to order as it prevents GP from allocating available inventory produced for another Order.  For the same reason, it can also be helpful when Orders are entered with a long lead time before shipment.

When enabled, all Sales Inventory items on all Sales Orders will have the Quantity Backordered set automatically to the Sales Line Quantity.  Setup options for the module provide the ability to restrict the Backorder All functionality by:

  • SOP Order ID
  • SOP Batch ID
  • Site ID
  • Item Class
  • Item Number
  • Customer Class
  • Customer Number

The CUSTOM option can be used to add your own business rules to control which items are backordered.  For example, you could have it only backorder items that have a GP Manufacturing Bill of Materials and are set to Make To Order on Item Engineering.

MFG PowerPack 2021-02-16

Release Date: 16-FEB-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 6.168
* NEW: SOP Backorder All- Automatically set the QTY on a Sales Order to Backordered regardless of available inventory. Control when this happens by Site, SOP Order ID, SOP Batch ID, Item, Item Class, Customer or Customer Class. You can also create your own custom logic to control Backorder All using whatever criteria are required.

CompleteCount 2021-02-13

Release Date: 13-FEB-2021
GP Versions: 12/14/16/18
CompleteCount Build: 1.49
* GP Stock Calendar year fix: Microsoft released a fix for the Stock Count Calendar window but it only covers GP2016 and GP2018. Our fix 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 fix on 17-NOV-2020.

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.