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

Customization CR0883 Social Security Number Security

Customization CR0883

Social Security Number Security

Problem Definition:

ACME records Social Security Numbers (SSNs) in the GP database and needs to tighten security on who can see those numbers. Since they have two employees with the same First and Last Names, users do need to see the last 4 digits of the number to help identify the employee.

Only two users should have access to change and view the entire SSN.

The SSN controls need to be applied to the Employee Maintenance SSN field, and the Vendor Maintenance Options Tax ID field.

Description of Solution:

Navigation: Tools >> Setup >> Company >> SSN Security

Users in this list will be able to view the complete SSN, and edit the SSN field, on the windows where the SSN controls are applied.

SSN Control will be applied to:

  • The SSN field on Employee Maintenance
  • The Tax ID field on Vendor Maintenance Options

In Employee Maintenance, for users who are not in the SSN Security list, the SSN field will be hidden (red box, above), and the SSN will be displayed in the Title Bar of the window. Only the last 4 digits will be displayed.

In Vendor Maintenance Options, for users who are not in the SSN Security list, the Tax ID field will be hidden (red box, above), and the SSN will be displayed in the Title Bar of the window. Only the last 4 digits will be displayed.

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-07-28

V12/14/16/18 build 4.159
* Tweak Unlink MO from SOP: added support for unlinking Split MOs
* Tweak Purchase Request Resolution GoTo MRP Workbench: this tweak was assigned an incorrect internal ID which caused it to enable/disable in conjuction with BOM History Inquiry. PRR to MRP Workbench now has a new internal ID so you will have to re-enable it in the MFG PowerPack Setup window.

NOTE: with the 28-JUL-2020 release of MFG PowerPack we are changing our release numbering scheme to use a common build number for the product regardless of the GP Major Version. The current build for GP2013 to GP2018 is 4.159 (as in 12.4.159 or 18.4.159). The functionality in our software is the same across all supported GP versions, which is better indicated by using a common build number. So if you are on GP2013 or GP2018 using build 4.159 of MFG PowerPack you can expect the same functionality.

GP PowerPack Release 2020-07-22

V12/14/16/18 build 4.144 Changes 22-JUL-2020
* NEW Tweak: RM Short Pay Alert – when applying a Customer’s payment, if it is short, an alert is presented.

NOTE: with the 22-JUL-2020 release of GP PowerPack we are changing our release numbering scheme to use a common build number for the product regardless of the GP Major Version. The current build for GP2013 to GP2018 is 4.144 (as in 12.4.144 or 18.4.144). The functionality in our software is the same across all supported GP versions, which is better indicated by using a common build number. So if you are on GP2013 or GP2018 using build 4.144 of GP PowerPack you can expect the same functionality.

MFG PowerPack Release 2020-07-14

V12.4.158 / 14.4.105 / 16.4.71 / 18.4.32 / “GP Next” 13-JUL-2020
* PowerATP: addressed issue in MFG Picklist requirements calculation that incorrectly calculated quantity in base (#20204564)
* Vendor Pricing: added check for Inactive items to prevent Vendor Pricing Inquiry from attempting to display & set pricing in PO Entry.
* Installation: addressed “cannot find object” error when installing into environments that do not have GP Manufacturing installed (#20202938)
* NEW TWEAK: BOM Entry GoTo Standard Cost Changes. This tweaks adds a new menu option to the GoTo button on BOM Maintenance to access the Standard Cost Changes window.

Read more about MFG PowerPack here

Consulting Toolkit Release 2020-06-20

V12.2.26 / 14.2.20 / 16.2.16 / 18.2.8 / “GP Next” Changes 22-JUN-2020
* NEW: Virtual Fields- Add fields to any dexterity based window without using Modifier.
* FULL INSTALL REQUIRED: This release contains new tables to support Virtual Fields. Running the full installation process with all users out of GP will be required.

GP PowerPack Release 2020-06-12

V12.4.143 / 14.4.86 / 16.4.54 / 18.4.26 / (GP Next)
* Tweaks: (1) Remove “GL Reconcile to GL Date Validation”. This was addressed by Microsoft in GP2013. (2) “IVN Item Class User Defined”-made Class UDF Labels display on the Item Class window in addition to Item Maintenance (3) Remove “INV: Set IV Batch Post To GL Checkbox”. This was added by Microsoft in GP2010. (4) Relabeled the three “Select Checks” tweaks to “Select Checks/Build Pay”. (5) “PM: Vendor Approval” controls now applied both Payables Entry and Purchase Order Entry (6) Removed “RM: Customer Address UDF Labels”. This was added by Microsoft in GP2013. (6) “SOP: Cancel Drop Ship” tweak–addressed issue in the SOP-POP Cancels window that prevented deleting lines.
* idModifier: added option to bypass duplicates check

Customization DS1075 Secondary Vendors

Customization

DS1075 Secondary Vendors

Problem Definition:

ACME enters Payables invoices and checks in Dynamics GP. The invoice and check will both be entered for the Vendor (the “Primary”) but a second vendor needs to be associated with the invoice (the “Secondary”). The relationship

The Secondary vendor needs to be referenced on the check stub that is send to the Primary vendor. ACME uses Mekorma to print checks.

ACME would also like the ability to display the Secondary Vendor ID and Name on Edit List and Posting Reports

When ACME displays a vendor in the PM Transaction Inquiry – Vendor window, the scrolling window must display the invoices where the displayed vendor is the Secondary Vendor.

Controls need to be added to Payables Transaction Entry to prevent a Vendor Invoice (Document Number field) from being reused. GP currently has controls to prevent this on a per vendor basis, but ACME needs to consider by Secondary Vendor too.

Design Features:

Secondary Vendor

Navigation: Transactions >> Purchasing >> Transaction Entry >> Additional >> Secondary Vendor

Field

Function

SAVE

Saves the Secondary Vendor to the transaction.

DELETE

Deletes the Secondary Vendor from the transaction.

Vendor ID

Enter or select a Vendor ID to assign as the Secondary Vendor. The Secondary Vendor cannot be the same as the Primary Vendor.

Name

Displays the name of the Vendor ID

The Secondary Vendor window will be accessed from the Additional menu on the Payables Transaction Entry window. When a Secondary Vendor has been linked to the Payables Transaction, the Secondary will be displayed in the Payables Transaction Entry header (NOTE, it will not be in red in the enhancement):

The Secondary Vendor will also be visible from the title bar on the Payables Transaction Entry Zoom window, but the Secondary Vendor window WILL NOT be accessible as to prevent changing the vendor after the invoice has been posted.

Report Modifications:

Check Printing

ACME uses Mekorma for their check printing and would like the Secondary Vendor Name to print on the check stub. Mekorma will provide the customization of the check stub. The following is the table format that will store the Secondary Vendor.

Table: wSecVendor

Field

Function

VCHRNMBR

*Key Field. The PM Transaction Voucher Number.

DOCTYPE

*Key Field. The PM Transaction Document Type.

VENDORID

The Primary Vendor ID of the transaction.

SecVendor

The Secondary Vendor ID linked to the transaction

* wSecVendor table will need to be joined to the Vendor Master table (wSecVendor.SecVendor to PM00200. VENDORID) in order to retrieve the Vendor Name of Secondary Vendor for the required Voucher and Document Type.

** The table name is for illustrative purposes to assist Mekorma in producing and estimate of work. Actual table name must be confirmed after project approval. Upon project approval WilloWare has agreed to provide Mekorma with a SQL CREATE and SELECT statement to use for their development and testing.

Batch Edit and Posting Reports

WilloWare will add a report writer function to the enhancement that will allow ACME to include the Secondary Vendor ID and Name to any GP report that has access to the Payables Voucher Number and Document Type via a calculated field, such as when printing an edit list or posting journal.

WilloWare will provide the report writer function as well as instructions on its use. ACME will perform all report modifications. This estimate does not include time to modify GP reports.

Payables Transaction Inquiry- Vendor

Navigation: Inquiry >> Purchasing >> Transaction by Vendor

The window will function as normal, meaning when a Vendor ID is entered, all documents (INV, PMT, etc.) that were entered into GP for the vendor will display in the scrolling window.

The enhancement will ADD INV transactions where the Vendor ID was selected as the Secondary Vendor. The added INV transactions must also meet the restrictions as entered. (Document Number, Date or Type From/To as well as the Include checkboxes). The Document Number and Voucher/Payment Number hyperlinks will take the user to the inquiry window for the transaction, as normal.

The enhancement will not display applied primary vendor PMT transactions but applied PMTs can be viewed by clicking the Unapplied Amount hyperlink to open the Payables Apply Zoom.

Payables Transaction Entry Controls

Navigation: Transactions >> Purchasing >> Transaction Entry >> Document Number field

Note: The functionality described below will NOT be active if the Payables Setup Option ‘Allow Duplicate Invoices Per Vendor’ is set to YES.

Standard GP functionality will prevent the user from entering a value in the Document Number field if it previously on another voucher for the same vendor. For our purposes, GP validates the Document Number on Current Voucher for Primary Vendor to Previous Vouchers where the same vendor was the Primary Vendor. The enhancement will add the following validations, looking for duplicate document numbers on vouchers where:

  1. Current Voucher Primary vendor was the Secondary Vendor on a previous Voucher
  2. Current Voucher Secondary vendor was the Primary Vendor on a previous Voucher
  3. Current Voucher Secondary vendor was the Secondary Vendor on a previous Voucher

If any of the additional validations fail, the user will be presented with the message:

Assumptions/Requirements

The functionality described in this document is intended for the Dynamics GP desktop client. Unless specified otherwise, all testing will occur in the desktop client only. Projects created in Dexterity should have a very high level of compatibility with the Web Client, but cannot be guaranteed without explicitly including additional time in the estimate for testing in the Web Client.

For information on this Design Spec, or any other customization or product, please contact us at:

//willoware.com/contact-me/

Customization DS1074 SOP Mass Update

Customization

DS1074 SOP Mass Update

Problem Definition:

ACME enters all Sales Order using a default site. The Order ID is set up to Allocate By = None. They have a large number of stores, and delivery personnel. To fulfill an order, it is transferred to invoice, and the Site (Store used to fulfill the order) and Shipment Method (Delivery person’s name) are changed on the Invoice.

ACME uses the Sales Orders Navigation List to select multiple Orders to transfer. The process of updating individual Invoices after the transfer is time consuming.

ACME would like a way to more easily and quickly change the Site (Store) and Shipment Method (Delivery person) during the transfer process.

Solution Features:

Update Sales Orders

After clicking the TRANSFER button in the Sales Orders Navigation List, the Sales Transfer Document window opens. The Update Sales Orders window will open automatically and position itself to the right of the Transfer window.

The window will display Orders where the Order ID has Allocate By = NONE. If any other documents are included in the transfer, they will not be displayed in this window.

Field

Function

Order

Displays the Sales Order Number

Customer ID

Displays the Customer Number

Site ID

Displays the currently assigned Site ID (Default Site) from the Sales Order Header.

This field is a drop-down list which contains all available Site IDs. A new Site ID can be selected by choosing an option from the dropdown list.

Ship Method

Displays the currently assigned Shipping Method from the Sales Order Header.

The field is a drop-down list which contain all available Shipping Methods. A new Shipping Method (Delivery person) can be selected by choosing an option from the dropdown list.

BUTTONS

Done

Closes the window and applies changes.

The changes made to Site ID and Ship Method are applied to the documents. The values will be updated on the Sales Order Header, and on all Lines.

If necessary, new Item-Site records will be created.

Cancel

Closes the window without making any changes to the Sales Orders.

Assumptions/Requirements:

  • The functionality described in this document is intended for the Dynamics GP desktop client. Unless specified otherwise, all testing will occur in the desktop client only. Projects created in Dexterity should have a very high level of compatibility with the Web Client, but cannot be guaranteed without explicitly including additional time in the estimate for testing in the Web Client.
  • Multi-Bins is NOT enabled
  • Inventory is not serial or lot tracked
  • ACME Overrides Shortages in SOP
  • Sales Kits are not used
  • Orders are set to Allocate By = NONE

For information on this Design, or any other customization or product, please contact us at:

//willoware.com/contact-me/