Release Date: 3-NOV-2021
GP Versions: 12/14/16/18
MFG Import Build: 2.52
* Added checks for blank records in tables linked-to and populated by the import. This was added as a safeguard to address the following scenario: a client had a blank record in IV00101 (perhaps from a go-live data import) which caused the import utility to link from a blank Template Item Number (blank because it was not being used) to the blank record in the Item Master, which then caused multiple data validation steps to fail and BOM Import would not run. The checks will run before the BOM Import and Routing Import windows open and will warn the user if there are any blanks, and provide instructions on how to fix the problem.
Author: admin
MFG PowerPack 2021-11-02
Release Date: 2-NOV-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 9.187
* Serial Number Mass Entry: attached to the Inventory Assembly Transaction Serial Number Entry window. This window is supported with the “mass add” method of inserting serials directly into the related SQL table, which bypasses the slowness of the GP “multi-select” listviews on the Serial Entry window.
GP18.4 Releases Ready
All of our software is now ready for GP18.4!
We wanted to take this occasion to share with you our thoughts on the 18.x releases. While this new numbering approach gives the impression that each new “DOT” build (18.2, 18.3, 18.4) is just a “service pack”, this is not the case, and it is not how we treat them.
In short, we treat them as MAJOR releases (like going from GP2016 to GP2018). Between each DOT release there can be major changes that affect integrating products, such as:
- New tables in the SQL database
- New columns added to existing tables
- Changes to the sort order of Keys on tables
- New parameters in existing Procedures and Functions (dexterity code)
All of the potential changes mean that integrating software needs to be tested on the latest release of Dynamics GP.
On the topic of software releases, we received a support question recently looking for an explanation of how our build numbers work. We recently changed our software build numbering logic so that regardless of the GP Major Version (i.e. GP2013, GP2015, GP18.4, and so on), a release of one of our products has the same “core” build number.
For example, MFG PowerPack has the current build numbers:
- For GP2013: 12.9.186
- For GP2014: 15.9.186
- For GP2016: 16.9.186
- For GP2018: 18.9.186
The first number is the Major Version, and that must match the GP version you are installing into. For example, if you are on GP2016 you have to install a 16.x.y build of our software.
We think of the next two numbers as the “Internal Major” and “Internal Minor” build numbers, in the example above “9.186”.
The Internal Major number only changes if we need to make changes to the SQL database, such as change a table, adding a table, or creating a stored procedure. For example, if the internal build changes from “9.186” to “10.187” it means that the new release has changes to the SQL database and the full installation routine needs to be run as “SA” with no users in the system. If the internal build changes from “9.186” to “9.187” it means that it is a CODE-ONLY change and the new code (the CNK) can be dropped onto the GP client and you will NOT have to run an installation routine after logging in.
Prior to making this change to our release numbers, as each product was upgraded for a new release of GP we would start the build numbering over again. For example, the first build of MFG PowerPack after upgrading it to GP2018 would be 18.0.1.
We felt this was confusing because MFG PowerPack is actually the SAME code on GP2013 all the way through GP18.4. We build logic into the software so it knows what version of GP it is on, and what is different about that version of GP, and it changes accordingly. For example, GP18.4 has new User Defined Fields on GL Transactions that were not present in GP2013. If MFG PowerPack needs to create a Journal Entry, it checks to see what version of GP it is running in, and then runs the correct “create journal entry line” routine for GP2013 or GP18.4 (one without user defined fields, and one with user defined fields).
We felt that carrying the same internal build number over ALL supported versions of Dynamics GP better reflected the fact that the functionality you get from our product is IDENTICAL across all supported versions of GP. This is the benefit you receive from WilloWare of staying current on software maintenance–even if you do not upgrade GP you are still getting the latest functionality from WilloWare.
Happy Upgrading!
BlanketPO 2021-10-28
Release Date: 28-OCT-2021
GP Versions: 12/14/16/18
BlanketPO Build: 1.41
* Release Entry: addressed issue in the calculation for the Control Quantity and QTY Remaining that incorrectly converted to base quantity when the Control Line was in a UofM other than base.
MFG PowerPack 2021-10-28
Release Date: 28-OCT-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 9.186
* Updated for GP18.4 Release
* Proposed Cost Update: Added fields in the Excel import template to support setting the “Set To Zero” checkbox on the Standard Cost Changes window when importing new proposed costs.
* PowerATP: fixed issue in Free Forward calculation that was retrieving the correct date but incorrect quantity.
Customization CR0701 MO Number Creation Update
CR0701
MO Number Creation Update
Description of Need:
Currently, the MO Number that is auto-generated from the Sales Order is created as SOPNUMBE_LNITMSEQ. ACME would like the MO Number to also include a prefix which will represent the Site which is entered into the Sales Order Document header.
Description of Solution:
Navigation: Setup > Manufacturing > Site Prefix Setup
This window is used to define a Prefix for each Site ID used in the Sales Order to MO creation process.
Field |
Function |
Done Button |
Click the DONE button to exit the window |
Site ID |
Enter or select a Site ID from the lookup |
Prefix |
Enter a one character Prefix to represent the Site ID. A Number or Letter may be entered. |
When an MO is created by the enhancement, the MO number will be generated in the following manner:
- If the Sales Document Header’s Site ID is listed in the Site Prefix Setup window, the first character of the MO will be the Site’s Prefix.
- If the Site ID is NOT listed in the Site Prefix Setup window, a prefix will NOT be added.
The balance of the MO number will remain as is: SOPNUMBE_LNITMSEQ.
Example #1
Site ID NORTH has a Site Prefix of “1”
Sales Order ORD00012 has 2 Sales Lines entered. Each Sales Line will generate an MO.
Two MO’s will be created:
- 1ORD00012_16384
- 1ORD00012_32768
Example #2
Site ID WEST has a Site Prefix of “A”
Sales Order ORD00013 has 2 Sales Lines entered. Each Sales Line will generate an MO.
Two MO’s will be created:
- AORD00013_16384
- AORD00013_32768
Example #3
Site ID EAST does NOT have a Site Prefix set in the Site Prefix Setup window.
Sales Order ORD00014 has 2 Sales Lines entered. Each Sales Line will generate an MO.
Two MO’s will be created:
- ORD00014_16384
- ORD00014_32768
For more information about this design, or any other WilloWare customization or product, please contact us at:
GP PowerPack 2021-10-04
Release Date: 19-OCT-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.155
* NEW TWEAK: Open IRP with Item’s Default Site – if a Default Site ID is assigned to an Item in Item Quantities Maintenance, when the Item is displayed in Item Resource Planning the window will automatically show information for the Item’s Default Site ID.
* SOP Rules: Secure Batch by User ID: Added additional controls to ensure “restricted” Batches do not become locked in batch activity by users who do not have access
MFG PowerPack 2021-10-18
Release Date: 18-OCT-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 9.185
* NEW TWEAK: POGen Integration- PO Generator suggests purchase orders based on quantities in the Item Quantities Master table. However, there are modules, such as GP Manufacturing and Field Service, that create transactions which do not update the Item Quantities until after the transaction posts (for example, unallocated Manufacturing Picklists or unreceived Inter-Site Transfers). PO Gen Integration can pull additional sources of inventory supply and demand into the PO Gen calculation to arrive at more accurate purchasing suggestions.
* Company Switching: addressed an issue that prevented the software from correctly enabling MFGPP options based on company settings when switching companies.
* FULL INSTALLATION ROUTINE REQUIRED FOR THIS BUILD
MFG PowerPack 2021-10-13
Release Date: 13-OCT-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 8.184
* SOP Number to MO Number: addressed issue that prevented it from working with Silent MO Generation (#202101748)
MFG PowerPack 2021-10-06
Release Date: 6-OCT-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 8.183
* Serial Mass Entry: Added mass serial number load into IV Transfer and IV Adjustment rather than automated adding through the UI. This process had been causing the list views to refresh after each addition which caused significant time delays when there are a large number of available serials.
* Vendor Pricing Import: addressed issue that caused date to offset forward by one day
GP PowerPack 2021-10-04
Release Date: 4-OCT-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.154
* SOP Rules: Secure Batch by User ID: (1) Changed trigger point to prevent unauthorized users from locking a batch if they attempt to open one they do not have access to. (2) Added a routine to clear batch activity if user scrolls through documents and reaches one that is assigned to a batch to which they do not have access
GP PowerPack 2021-09-30
Release Date: 30-SEP-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.153
* Bin-to-Bin Transfers: (1) Added controls to From Site to prevent changing it after a Bin-to-Bin Transfer has been started (i.e. a transaction can only be for one Site, it cannot be used to to bin-to-bin transfers for multiple sites at the same time). (2) Added a warning in Setup to alert user if they attempt to enable Bin-to-Bin Transfers when the Inventory Multi-bin functionality is disabled.
* SOP Rules: Secure Batch by User ID: (1) addressed issue that prevented the Rule from allowing access to a secure batch when multiple users are assigned to the same batch.
Customization DS0798: SOP Display Customer-Friendly Description
Customization DS0798
SOP Display Customer-Friendly Description
Description of Need:
ACME utilizes Dynamics GP to enter its Sales Documents. They would like to provide their Sales team with an alternate, more customer-friendly, Item Description during Order Entry.
The customer-friendly Item Description is held in the Customer-Item Maintenance window. A default Customer ID “999999” is used to store all customer-friendly Item Descriptions.
ACME requires this Item Description to display in the Sales Transaction Entry window’s toolbar during Sales Document Entry. The full Customer Item Description of 51 characters must display.
Description of Solution:
Navigation > Transactions > Sales > Sales Transaction Entry
The Sales Transaction Entry window will be updated to display the customer-friendly Item Description in the toolbar. This will look similar to the “Ship Weight” verbiage displayed below:
The customer-friendly Item Description will display during Sales Document entry when the user tabs out of the Item Number field. It will also display if an existing Sales Line is selected.
The customer-friendly Item Description from Customer ID “999999” will display, regardless of the Customer ID entered on the Sales Document. If an Item-Customer Link does not exist for Customer ID “999999”, no Item Description will display in the toolbar.
Please Note: The Toolbar can display up to 78 characters; there for displaying the full Customer Item Description of 51 characters is achievable.
Assumptions/Requirements
The functionality described above is intended for the GP Desktop client.
For Information on this customization, or any other WilloWare customization or product, please contact us at:
Customization CR1111- Customer PO and SOP Order Lookup by Customer ID
CR1111
Customer PO and SOP Order Lookup by Customer ID
Description of Need:
Acme would like the following enhancements to the SOP Update Utility:
- A Lookup on the Customer PO field that will only show Customer POs on SOP orders that belong to the entered Customer ID.
- Restrict the SOP Order From/ To lookups to only sales orders that belong to the entered Customer ID.
- A third radio option to allow removing an item number without having to add a new item is needed.
Description of Solution:
- A lookup and customer lookup window will be added to the Customer PO field so the user can search for Customer PO values that are found in the Sales Order Header table where the Customer ID equals the ID entered in this window.
- The Sales Document Numbers window will be modified so that when opened from the Utility window, it will only display orders where the Customer ID (and Customer PO, if entered) matches the one entered in this window. All other orders will be removed from the list.
- A third radio button option will be added to the window to allow removing the item number entered in the top half of the window. When this option is selected, the Add Item Number and fields below it will be disabled.
Assumptions/Requirements:
- The functionality described above is intended for the GP Desktop client.
For information on this customization, or any other WilloWare customization or product, please contact us at:
Customization CR1172 Billing Entry Enhancements
Customization CR1172
Billing Entry Enhancements
Description of Need:
ACME would like to add the following enhancements to the billing entry process. These automations are intended to make Billing Entry more efficient.
#1: Allow entering the Project Number before entering the Customer ID. After the Project Number has been entered, retrieve the Customer ID from the Project and put that into the Customer ID field.
#2: Automatically populate the Customer PO Number field with the Project PO Number.
#3: Automatically create a “Project Level” Billing Note for the Project. Create the note as shown below, replacing the terms in brackets { } with information from the Project.
Contracted Amount for {Project Practice} – {Project Name} – PO Number: {Project PO Number}
The text shown above in bold red comes from the Default Project Billing Note on Project Billing Settings window. That text should remain unchanged and the additional information appended to it.
Description of Solution:
#1: Before entering the scrolling window, Project requires something in the Customer ID and Currency ID fields. When entering the scrolling window, if Customer ID is not already populated with a Customer Number, it will be filled with a period (“.”) and Currency ID, if not populated, will be filled with “Z-US$”.
After the user enters a Project Number, the enhancement will retrieve the Customer ID from Project Maintenance and fill that into the Customer ID field. It will the execute the Customer ID field code (i.e. what would normally run if you manually entered the Customer ID) to ensure all other fields that get updated based on the Customer Number will be updated correctly (i.e. Customer Name, Bill to Address ID, etc).
#2 and #3: After the Project Number has been entered, the Project PO Number will be used to populate the Customer PO Number field (as long as it is empty), and a “Project Level” Billing Note will be updated using the template described above.
Assumptions/Requirements:
- 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.
- The functionality described above is intended for the GP Desktop client.
For information on this customization, or any other WilloWare product or customization, please contact us at:
MFG PowerPack 2021-09-07
Release Date: 7-SEP-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 8.182
* PowerATP: (1) Fixed site restriction in the Lot Depletion routine so it looks at the “Restrict by INV Site” setting rather than the “Restrict by POP Sites” setting, (2) Performance improvements shorten calculation time by 75%
MFG PowerPack 2021-08-31
Release Date: 31-AUG-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 8.181
* FULL INSTALLATION ROUTINE REQUIRED FOR THIS BUILD
* Item Copy: (1) Added ability to copy all BOM Types. (2) The options for Manufacturing BOM Copy will revert to defaults after installing this build. Recheck your Item Copy Setup to ensure the correct Manufacturing BOM options are selected/unselected.
MFG Import 2021-08-31
Release Date: 31-AUG-2021
GP Versions: 12/14/16/18
MFG Import Build: 2.50
* BOM Import: Fixed issue in date checking logic that incorrectly failed importing dates from a GP client with Danish localization.
Customization CR1102- POP Order Multiple Warning
Customization CR1102
POP Order Multiple Warning
Description of Need:
ACME would like a warning message in Purchase Order Entry when the Quantity entered is not an even multiple of the Item-Site Order Multiple (from Item Resource Planning).
Since the Item-Site Order Multiple quantity is in the Base Unit of Measure, the PO Line quantity needs to be compared to the Order Multiple in the Base Unit. For example, if the PO Line Quantity is in CASE, but the base unit is EACH, the PO Line quantity needs to be compared to the Order Multiple in Eaches.
If the quantity entered is not an even multiple of the Item-Site Order Multiple, the warning should say:
“The quantity entered is not a multiple of the Order Multiple. The Order Multiple is 20.”
In this case “20” is an example of the Order Multiple. The warning will show the actual Order Multiple quantity.
If the Quantity IS a multiple of the Order Multiple, no message will appear.
Description of Solution:
A warning will be added, as described above, to the Purchase Order Entry window, and Purchasing Item Detail Entry window.
The warning will appear after the Quantity is entered/changed if it is NOT an even multiple of the Item-Site Order Multiple.
For information on this, or any other WilloWare customization or product, please contact us at:
MFG PowerPack 2021-08-10
Release Date: 10-AUG-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.180
* Vendor Pricing Import: addressed issue with the Excel integration that could prevent the import routine from terminating the excel.exe process after completing the import. This would leave the import file in a “locked” status with no apparent Excel app running although the process was visible in Process Monitor (#202101356)
* Sales Forecast Import: although no issues have been reported, the same issue may apply to SFI and was addressed by the change above.
* Item Copy: although no issues have been reported, the same issue may apply to Item Copy and was addressed by the change above.
BlanketPO 2021-08-04
Release Date: 4-AUG-2021
GP Versions: 12/14/16/18
BlanketPO Build: 1.39
* PO Close Utility: now automatically cancels the remaining quantity on all lines on the PO so they do not prevent closing the PO, then it closes the PO. Previously it would warn if there were open quantities and then abort closing the PO, which required a user to manually cancel each line (#202101296)
MFG PowerPack 2021-08-04
Release Date: 4-AUG-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.179
* SOP Number to MO Number: Added a control to prevent inserting new SOP lines between existing lines if any of the lines below are already linked to an MO. Because this tweak uses sequential numbering of the MOs based on the SOP lines, inserting a SOP line before a line linked to an MO would break the numbering sequence.
Customization CR0716 SOP User Defined Modifications
Customization CR0716
SOP User Defined Modifications
Description of Need:
ACME requires the ability to track additional Lead Source information during Sales Document Entry. ACME would like two fields added to the Sales User-Defined Fields Entry window:
- Lead Source
- Lead Source SubType
The Lead Source field should be a dropdown. The field should be required. ACME should have the ability to enter the dropdown options.
The Lead Source SubType field should be a string field, which is not required.
Description of Solution:
Navigation: Setup > Sales > Lead Source Setup
The Lead Source Setup window is used to define the Lead Source dropdown options available during Sales Document Entry.
Field |
Function |
Done Button |
Click the DONE button to exit the window |
Lead Source Options |
The user will enter Lead Source Options in the scrolling window. This field is a string field which will hold up to 20 characters. To delete a Lead Source Option, select the option and navigate to EditDelete Row. Lead Source Options which have been assigned to Open or Historical Sales Documents may NOT be deleted. |
Navigation: Transactions > Sales > Sales Transaction Entry > Sales User Defined Fields Entry
The Lead Source Entry window is used to assign the Lead Source and Lead Source SubType per Sales Document.
Field |
Function |
Save Button |
Click the Save button to save the entries and exit the window. |
Lead Source Dropdown |
The user will select an option from the dropdown. This field is required and will default to blank. The user will be unable to close the Lead Source or Sales User Defined Fields Entry window without selecting an option from the dropdown. The Lead Source dropdown will be added to the existing SOP Required Fields Enhancement which does NOT allow the user to save the SOP Document without having certain User Defined Fields entered. |
Lead Source SubType |
The user will enter the Lead Source SubType. This field is a string field which will hold up to 20 characters. |
The Lead Source Entry window will automatically open when the Sales User Defined Field Entry window opens. The Lead Source window will be placed directly to the right of the Sales User Defined Field Entry window similar to the example below. If the user closes the Lead Source window and wishes to reopen it, the Lead Source window may also be opened by navigating to Additional > Lead Source.
Please Note:
- If the Sales Document is transferred, the Lead Source information will transfer.
- If the Sales Document is deleted, the Lead Source information will be deleted.
Navigation: Inquiry > Sales > Sales Documents > Sales Transaction Inquiry Zoom > Sales User Defined Fields Inquiry
The Lead Source window will automatically open when the Sales User Defined Fields Inquiry window opens from the Sales Transaction Inquiry Zoom window. The window will be placed to the right of the Sales User Defined Fields Inquiry window as described above. The fields on the Lead Source window will not be editable when accessed through the Sales Transaction Inquiry Zoom.
For Information on this or any other WilloWare customization or product, please contact us at:
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:
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:
LeanMFG 2021-07-14
Release Date: 14-JUL-2021
GP Versions: 12/14/16/18
LeanMFG Build: 3.50
* Bill of Materials: addressed issue that allowed adding lines (components) without having entered a BOMID.
MFG Import 2021-07-14
Release Date: 14-JUL-2021
GP Versions: 12/14/16/18
MFG Import Build: 2.49
* Routing Import: Removed debug message that was popping a message during import
MOGenerator 2021-07-13
Release Date: 13-JUL-2021
GP Versions: 12/14/16/18
MOGenerator Build: 3.103
* MO Receipt Integration (MORI): (1) Excel integration now supports brining in Picklists, Routings, and finished good Serial Numbers.
SOP-POP MultiLink 2021-06-21
Release Date: 21-JUN-21
GP Versions: 12/14/16/18
SOPPOPMultiLink Build: 1.5
* Added ability to handle Drop Ships in SOP
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-06-17
Release Date: 17-JUN-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 7.177
* Vendor Pricing: Added checks to ensure the pricing table is cleared after each use.
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).
MOGenerator 2021-04-09
Release Date: 9-APR-2021
GP Versions: 12/14/16/18
MOGenerator Build: 3.100
* MOGenerator: addressed issue in MOGenV2 that caused the Create Child MOs utility to run regardless of the CreateChildMO setting.
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.
CompleteCount 2021-02-13
Release Date: 7-APR-2021
GP Versions: 12/14/16/18
CompleteCount Build: 2.50
* Mass Add/Update Utility: You can now save a query, and also edit the tSQL used in the saved query.
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
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.