LeanMFG Release 2019-09-19

V12.1.39 / 14.1.28 / 16.1.18 / 18.1.10 / “GP Next”
* Compatibility Release for “GP Next”
* Addressed issue in installation routine that caused SQL error (“Invalid length parameter passed to the LEFT or SUBSTRING function”)(#20193743)
* Addressed issue that allows user to close the window during posting which results in an illegal address error (“Illegal address for field ‘cbIsPosting’ in script ‘PostingFlag’. Script terminated”)(#20193691)
* Addressed issue that caused error when user clicked the Input Qty Expansion button when no line was selected in the Inputs Scroll (“Error: set precision passed bad precision value”). (#20192405)

Read More About LeanMFG

MFG PowerPack Release 2019-09-18

V12.2.151 / 14.2.98 / 16.2.64 / 18.2.25 / “GP Next”
* Compatibility Release for “GP Next”
* Where Used Inquiry: (1) addressed issue that caused the window to display duplicates when “View All” was selected (#20192831), (2) added new checkbox (“Expand to where used”) that controls if the treeview displays nodes expanded to the “where used” item, or if all nodes are collapsed, (3) after entering the Item Number, the first valid BOM is displayed, rather than defaulting to MFG BOM. For example, if an MFG BOM does not exist, it would default to the first available BOM sorted by BOM Type (BOMCAT_I) and BOM Name from the BOM Header table (BM010415).
* MO Doc Types: addressed issue that caused the “default” MO Number generated by GP Manufacturing to be retained in the WO Master table (WO010032) after selecting the new Doc Type generated MO Number (#20192671)

GP PowerPack Release 2019-09-12

V12.2.138 / 14.2.81 / 16.2.49 / 18.2.21 / (GP Next)
* NEW SOP Tweak: Require Customer-Item: this tweak prevents sale of an item if an Customer-Item record does not exist. This Tweak can be used to enforce a rule that requires customers to be approved to purchase items, or when they should only purchase certain items, such as private label inventory.
* Sales Pro: Added Customer Items view

Engineer To Order Release 2019-09-10

V12.1.35 / 14.1.18 / 16.1.11 / 18.1.7 / (GP Next)
* Compatibility release for GP “Next”
* Setup: New options for Routing Sequence Increment and Sequence Number Pad. The Routing Sequence Increment will default to the Manufacturing Setup value for “Sequence Spacing”, and if that is not set up (or is zero), it will default to 10 but the default can be changed. The Pad adds leading zeros to the Routing Sequence Number, so a Pad of 4 would result in “0010”, “0020”, “0030”, etc.

Read more about ETO here

GP PowerPack Release 2019-09-04

V12.2.137 / 14.2.80 / 16.2.48 / 18.2.20 / (GP Next)
* Compatibility Release for “GP Next”
* Alert: Addressed issue that can cause an alert to clear if there are multiple alerts, such as a Vendor Alert and a PO Alert.
* idModifier: Complete redesign. idModifier can now be “trained” to update/modify virtually any string (ID) field in core GP tables, 3rd Party Product tables, and custom tables. When creating a new ID profile, idModifier will search the database for a sample value (i.e. AARONFIT0001). It identifies all of the tables/fields that contain the sample. The search feature allows it to locate data in 3rd party tables, and to identify all of the different field names used to store the data (i.e. CUSTNMBR, CPRCSTNM, Bill_To_Customer, etc). New table: W5026IDTables. Table W5026IDFields is dropped.
* Sales Pro Item Lookup: addressed issue that prevented it from displaying the Primary Ship To Address Code from Sales Transaction Entry.

 

To learn more about the new idModifier, click here.

CompleteCount Release 2019-08-31

V12.1.40 / 14.1.30 / 16.1.23 / 18.1.13 / (GP Next)
* “GP Next” Compatibility Release
* WW Internal Resources Update
* Setup: Changed “Enable Stock Tags” to “Enable CompleteCount”
* Value Code Update: Addressed issue that prevented the “Clear Value Code if Item has no Usage/Quantity” from clearing the Value Code from all items without Usage/Quantity. When this option is marked, the update routine will first clear the Value Code from ALL Item-Site records in the selected site, then repopulate the Value Code based on the analysis performed in the Value Code Update window.
* Documentation: updated the documentation in all locations where it references the Value Code setting to provide more information about this field and how it is used.
* Start No Item Count: A new Additional Menu option has been added to the Stock Count Schedule window that allows start a count that contains no Items. This may be used when recording counts in Excel. The Excel Import will add “new” items to the count during the import process.

BlanketPO Release 2019-08-31

V12.1.36 / 14.1.25 / 16.1.11 / 18.1.4 / (GP Next)
* GP “Next” Compatibility Release
* Updated WW Internal Resources

With the next release of Dynamics GP, due later this year, Microsoft is changing the internal build numbering logic within Dynamics GP.  To accommodate this we had to change how our registration key functions.  If your registration key is more than one year old, please contact WilloWare to receive an updated key before installing this update.

MFG PowerPack Release 2019-08-30

V12.2.150 / 14.2.97 / 16.2.63 / 18.2.24
* Serial Number Mass Entry: (1) addressed issue that caused a warning message (“Please select Bin(s).”) on the Manufacturing Component Serial Number Selection window even though no bins are required. (2) Added integration point to GP PowerPack’s SOP Non-Inventory Item Serial/Lot Entry window.

Payables Transaction Inquiry – Document Performance Issue

We recently had a support case regarding very poor performance in the Dynamics GP Payables Transaction Inquiry – Document window.  The client has a very high volume of transactions so the payables transaction tables contain millions of records.

The user reported that the window worked fine in GP2015, but in their GP2018R2 test upgrade environment, using the window froze the GP client and severely degraded performance in the system for other users.  The user had to forcibly kill the GP client.

Our investigation revealed the following.

The window uses a SQL stored procedure to populate a temp table which is used to fill the scrolling window.  The stored procedure (pmBuildTrxInquiryByDateRange) was not using the “no lock” hint, so the query’s table joins looked like this:

There are several queries in the stored procedure that use different tables, none of which use “no lock”.

The client reported that the performance issue was resolved after we updated the stored procedure to use “no lock” in all of the queries, like this:

LabelLink Release 2019-08-16

V12.1.39 / 14.1.22 / 16.1.11 / 18.1.4
* Added support for label printing Automation modules
* Changed based table for SmartList labels from LabelLinkSL to W5424002. The report view name is still LabelLinkSLView.
* Added a new table (W5424001) as a permanent label data store to be used by automation. A new view (LabelLinkAuto) is provided for Automation modules to retrieve label data. Automation modules should delete records from W5424001 after printing, or set the Printed flag in W5424001.
* Added a new table (W5424003) as a permanent label data store to be used by automation when printing SmartList labels. A new view (LabelLinkSLAuto) is provided for Automation modules to retrieve label data. Automation modules should delete records from W5424003 after printing, or set the Printed flag in W5424003.
* LabelLink window: (1) added a “show” drop-down to control whether the window shows All Items, or only Items assigned to the selected label (Items can be assigned to a label in Item-Label Setup). (2) Change the heading on the “remove” checkboxes to “hide” (i.e. Hide Lot Numbered Items) to correctly reflect what happens when one of the checkboxes is marked. (3) Fixed an issue that caused the “hide” checkboxes to not hide the correct items from the display.
* Item Label Setup: added a SmartList import wizard to automate mass assignment of Items to a Label.

Our new support for “automation” removes the need to install label printing software (such as Bartender or Codesoft) directly on each GP Client.  Instead the label data will be prepared and sent to an “automation” server for printing.  This will immediately free the GP client to continue working while labels are printed in the background.  Automation support works with both our standard “transaction” labels (i.e. printing labels from Sales Transaction Entry, PO Receipts, MO Receipts, etc) and with SmartList (printing labels directly from a SmartList Favorite).

Read more about the automation available from some of the labeling software vendors supported by LabelLink:

//www.bartendersoftware.com/software/automation/

//www.teklynx.com/en/products/enterprise-label-management-solutions/sentinel

//www.nicelabel.com/label-management-system/integrated-printing

 

 

 

LeanMFG Release 2019-08-13

V12.1.38 / 14.1.27 / 16.1.17 / 18.1.9
* MO Doc Type Setup: Added two new options, “Disassembly Wizard: Remove Non-IV Items” and “Disassembly Wizard: Reverse Non-IV Costs”. The first option will cause the Wizard to create a Disassembly MO that does not include any non-inventory type items. The second option will cause the Wizard to add non-inventory type items to the Outputs tab and then during posting to create a non-inventory Journal Entry that reverses the debits/credits from the original MO.

MFG PowerPack Release 2019-08-01

V12.2.149 / 14.2.96 / 16.2.62 / 18.2.23
* Vendor Pricing: (1) Addressed issue with import utility that caused it to use an incorrect currency decimals setting which resulted in the price list being invalid (#20192485), (2) Added new error check to look for missing Item-Currency ID assignment records.
* SVC Equipment Suite: (1) Rebuild Configurations Utility: addressed issue that could cause very slow performance/freeze, (2) Added a routine to insert a default SVC Master Records (SVC00999) record if it is missing so that the Field Service stored procedure that creates a New Equipment ID does not fail.

More information about: Vendor Pricing

More information about: Service Equipment Suite

Engineer To Order Release 2019-07-30

V12.1.33 / 14.1.16 / 16.1.9 / 18.1.5
* ME: (1) Added reports for Estimated Quantities, Router, and Other Costs. (2) Addressed duplicate key error caused by copying an ME BOM to a new ME BOM where the BOMID being used would create a duplicate of a subassembly BOM (#20192452)

The PRINT button on the Mfg Estimation window used to print a Bill of Material report.  It now opens the new Print Options window shown below.

Print Options provides access to the original Bill of Material report along with the three new reports (Routing, Other Costs, and Estimation Quantities).

 

GP PowerPack Release 2019-07-22

V12.1.135 / 14.1.78 / 16.1.46 / 18.1.18 Changes 22-JUL-2019
* Select Checks Filters: (1) addressed issue with filtering on Voucher Number that caused error “Incorrect syntax near keyword ‘like'” (#20192402), (2) Added a Delete Row button to the Values list, (3) Added additional controls to the Values List and the Filter Save button to ensure a Filter ID has been entered.

Select Checks Filters works with the Dynamics GP Select Payables Checks window to provide a large number of inclusion/restriction criteria for filtering payables when creating a check run.

If you also have GP PowerPack Tweaks, consider enabling the “PM Select Checks Status Message” tweak to have a status message displayed during the long running check batch building process so you can tell that GP is still working on it!

 

GP PowerPack Release 2019-07-18

V12.1.134 / 14.1.77 / 16.1.45 / 18.1.17 Changes 17-JUL-2019
* SalesPro Item Lookup: (1) addressed issue that cause the GoTo menu options to not open the selected window (#20192232), (2) Added Ship To Address to the window so that Customer Item Sales can be restricted by Ship To Address, (3) The GoTo button options are now dynamically added based on products installed and user security.

SalesPro Item Lookup is an enhanced Inventory Item Lookup for Sales Transaction Entry.

The new Ship To field will default to the Ship To Address Code from Sales Transaction Entry.  It restricts the items shown in the Customer History window (A), and both views shown in window C (Invoices with selected Item, and Items Purchased with selected Item).  Clearing the Ship To field makes the window display information based on all sales invoices for the Customer.

The GoTo button now only shows options that opens windows to which the user has security, and only for products that are installed (i.e. it will not show Manufacturing options if GP Manufacturing is not installed).

LeanMFG Release 2019-06-26

V12.1.37 / 14.1.26 / 16.1.16 / 18.1.8 Changes
* MO Inquiry: Addressed issue that caused it to not show correct Totals at the bottom of the Outputs scrolling window.
* MO Entry: Addressed issue in the Posting routine that was not correctly retrieving the Journal Entry from posted Finished Good Inventory Adjustment if there was also a Non-Inventory Journal Entry (i.e. for labor) and/or a Variance Journal Entry. Although the transactions posted OK, this issue then caused the MO Inquiry window to not show the Posted Output JE (appearing as if it wasn’t created), which caused the window to show that there was a variance even though a Variance JE had not been created. (#20192152)

Manufacturing Order Picklist Draw From Site

The Manufacturing documentation has this to say about specifying sites:

If no issue-from or issue-to site is specified for a component,  default sites will be used.

Default values for the issue-from site site

Refer to the following information about how the issue-from site is determined.

  • The issue-from site from the bill of materials line entered in the Bill of Materials Entry window is used.
  • If a site hasn’t been specified in the Bill of Materials Entry window, the DEFAULT SITE for the item entered in the Item Quantities Maintenance window is used.
  • If a Default Site hasn’t been specified in the Item Quantities Maintenance window, the Draw Inventory From entered in Manufacturing Order Entry window is used. (The default site comes from the scheduling preference you’ve selected for the manufacturing order, but you can change it.)

However, if you leave the BOM Line Issue From Site blank, you cannot get Manufacturing to use the Item’s Default Site when creating a Picklist.  Here’s why…

The BOM Line “Issue From” for CORDG is blank:

The “Default Site ID” for CORDG is SOUTH:

The “Draw Inventory From” site on the Scheduling Preference is WAREHOUSE:

The “Draw Inventory From” site on the Manufacturing Order is populated from the Scheduling Preference, so it is set to WAREHOUSE:

Below is the “Build Picklist” code that sets the Draw From Site:

In plain English this says:

If the “Draw From” site on the BOM Line is empty then

If the Draw From Site on the Manufacturing Order is NOT empty then

Use the Draw From Site on the Manufacturing Order

Else

Use the Item Quantity Maintenance “Default Site”

Else

Use the BOM Line “Draw From” site

 

Note that while we can leave the “Issue From” site blank on the BOM Line, we cannot leave the “Draw From” site blank on the Manufacturing Order–it is a REQUIRED FIELD (shown by the Red, Bold font).  This means that the “Draw From” site on the Manufacturing Order will NEVER be empty.

Re-reading the logic above considering that the “Draw From” site on the Manufacturing Order will always have a value we can see that the “Build Picklist” code will never reach the line that tells it to use the Item’s Default Site.

If the “Draw From” site on the BOM Line is empty (which it is…) then

If the Draw From Site on the Manufacturing Order is NOT empty (which it isn’t…) then

Use the Draw From Site on the Manufacturing Order

Else

Use the Item Quantity Maintenance “Default Site”

Else

Use the BOM Line “Draw From” site

Which means the Draw From Site has two options: Either it is provided by the BOM Line site, or it is provided by the Manufacturing Order.

MFG PowerPack Release 2019-05-06

V12.2.146 / 14.2.93 / 16.2.59 / 18.2.20 2-MAY-2019
* Item Copy: (1) Routing Map now has options for how it creates the Routing Name. Under the “Routing” option, click the image next to the “Default Routing Name” setting to change the default between Destination Item Number and Source Routing Name (2) Under “Item Currency Maintenance” added a new option to zero List Price (3) The installer will now add a stored procedure to the database (wspItemCopyPost) that will run after all other copying tasks. The stored procedure can be edited to include any custom ‘post copying’ updates that are needed.

NOTE: The Minor Version number increments with this release, so the full installation routine needs to be run to create new SQL objects.

Zero List Price appears below the Item Currency Maintenance option:

The Routing Name Default setting appears under the Routing option:

Click on the image to the left of “Default Routing Name” to toggle between the options.

The new stored procedure (wspItemCopyPost)  has no executable code–it is an empty stored procedure that is called at the end of the Item Copy routine.  The stored procedure can be edited to add any additional updates you need to run.

MFG PowerPack Release 2019-04-09

V12.1.145 / 14.1.92 / 16.1.58 / 18.1.19
* Item Copy: (1) the window now remembers the “Zero Standard Cost” setting rather than defaulting to enabled. “Zero Standard Cost” setting has been moved off the header section of the window and is in now under “Item Maintenance” (2) Performance improvements, (3) Under “Item Price List Maintenance” added a new option to zero the price list after copying it. (4) Routing Map now creates a default mapping for the primary routing using the Destination Item Number as the Routine Name if no mapping is provided, (5) The Routing Map now clears after copying an item
* MO Split: Added routine to check that default separator character gets set when the MO Split Setup window is never opened.

Consulting ToolKit Release 2019-04-09

V12.1.24 / 14.1.18 / 16.1.14 / 18.1.6 Changes
* Updated Registration Key module to address issue that caused the product to not recognize the registration key (#20191132)
* Virtual Triggers: Added a visual indicator to the Databases pop-out to show when databases have not been marked (red) versus when at least one database is selected (green)

 

The Virtual Triggers Setup window now highlights the DATABASES pop-out to help remind you to select databases.  When no Trigger is displayed the tab is white:

 

When a Trigger is displayed that has no databases selected, the tab is red:

 

When a Trigger is displayed that has at least one database selected, the tab is green:

 

 

MFG PowerPack Release 2019-03-27

V12.1.144 / 14.1.91 / 16.1.57 / 18.1.18
* Addressed issue #20190930 (Invalid object name mops0100). Error caused by “TWK: Edit MO Status Allocation Override” which wasn’t checking if GP Manufacturing was installed.
* Setup Window: (1) Added ability to display both Registered and Unregistered modules in the Suite. (2) Window now checks if MFG and/or Field Service are installed and only displays Modules and Tweaks that require those modules if they are installed.
* Capable To Promise (CTP): Added additional menu on SOP Inquiry to open the CTP window.
* Where Used Inquiry: addressed issue when zooming to a new Inventory BOM when a current BOM is displayed and it has changes.

 

The MFG PowerPack Setup window now has radio buttons to display Registered and Unregistered modules.The Unregistered Modules view shows all modules contained in the Suite that are not available with the current Registration Key.MFG PowerPack contains many modules that required the Dynamics GP Manufacturing module and/or the Field Service module.  The Setup window will not only display MFG PowerPack modules that can be used (i.e. it will not show a module if it requires Manufacturing and the Manufacturing module is not installed).

 

GP PowerPack Release 2019-03-26

V12.1.133 / 14.1.76 / 16.1.44 / 18.1.16
* Setup window: (1) moved Alerts, Login Monitor, and System Access Lock from the GoTo button into main window, (2) The main window now has an option to view both registered and unregistered modules

 

The GP PowerPack Setup window has new radio buttons to show Registered and Unregistered modules.

The Unregistered view shows all modules in GP PowerPack that are NOT registered.  Additionally, the setup windows for several modules previously appeared only on the GoTo button and not in the main list of Registered Modules.  These include: Alerts, Login Monitor, and System Access Lock.  This was a frequent source of confusion because if you were registered only for Alerts, the main setup window was blank because Alerts was on the GoTo button.  Now these three modules will appear in the main GP PowerPack list of registered modules.

Blanket PO Release 2019-03-24

V12.1.35 / 14.1.24 / 16.1.10 / 18.1.3 Changes 24-MAR-2019
* NEW: Planned Release Wizard. This utility will calculate and create a number of releases, such as creating a release on the first Monday of every month. It can create planned releases using a fixed quantity until the Control Quantity is met, or, it can divide the Control Quantity evenly over releases in a specified time frame.
* NEW: Auto-Firm Releases Utility. This utility will automatically create Firmed Releases when the Required Date meets selection criteria. Releases can be created before the Required Date by using the Vendor Lead Time and/or Purchasing Lead Time.

The new Release Wizard window is shown below.

The Release Wizard is accessed from the PO Release Entry window.  In the example above, it calculated Planned Releases for each Monday between 4/12/2017 and 6/12/2017.  When the desired scheduled is achieved, the Release Wizard can create a Planned Release for each Date/Quantity, adding them to the PO Release Entry window.

MFG Import Release 2019-03-21

V12.1.43 / 14.1.26 / 16.1.14 / 18.1.7
* Changes to log-out routines to prevent resource conflict with Rockton Security Auditor
* BOM Import: if the Component Quantity column in the import spreadsheet was formatted as Text, the import routine converted the string to a currency value using the dexterity function called value(). This fuction interprets any non-numeric character as a “stop” value, so 1,255.55 is returned as “1”. We replaced all use of the value() function with our own routine that correctly parses a complete number from a string.
* Routing Import: the change described above for BOM Import was also applied to the Routing Import utility.

EZImport Release 2019-03-11

V12.1.12 / 14.1.5 / 16.1.3 / 18.1.1 Changes
* First GP2018 Release
* Added Query window: a new GoTo button on the EZ Import Inquiry windows provides direct access to query the EZ Import tables using the new Query window. For example, from the EZ Import Sales Inquiry window, select GoTo >> View Sales Lines, and the query window will show all of the data in the Sales Lines table for the selected Sales Order. The Query window provides a quick way to see all of the “extra” data assocated with a record that is not visible on the Inquiry windows.

GP PowerPack Release 2019-02-14

V12.1.130 / 14.1.73 / 16.1.41 / 18.1.13 Changes
* UPDATE: POP-Tweak: Purchasing Distributions Override–previously contained “PURCH Distributions Override” and “PURCH Distributions By Line”. In this release the second is split out into a separate Tweak (POP-Tweak: Purchasing Distributions By Line). When Purchasing Distributions By Line creates the new distributions, it previously populated the GL Reference with the PO Line’s Item Number. A new setup option allows choosing to fill the Reference field with (1) Item Number, (2) Item Description, (3) Vendor Item Number, and (4) Vendor Item Description. If you currently have Purchasing Distributions Override, the new Tweak “Purchasing Distributions By Line” will be enabled automatically.

CompleteCount Release 2019-02-10

V12.1.38 / 14.1.28 / 16.1.21 / 18.1.11 Changes
* Tag Submit Routing – Lot Reconciliation: a new routine “allocates” the total counted quantity of a Lot Number across the available receipts of a Lot Number (assuming there are multiple receipts of the same Lot Number). Previously the module attempted to “consolidate” split receipts by putting all of the counted quantity onto one lot receipt record and zeroing the others. The new routine eliminates the potential to create a cost variance even through the total count matches the captured quantity. It handles the valuation methods as follows:
** LIFO: it counts forward from oldest receipt to newest so any shortages come out of the most recent recent (the LIFO receipt)
** FIFO: it counts backwards from newest receipt to oldest so any shortages come out of the oldest receipt (the FIFO receipt)
** AVG is treated like FIFO
* Tag Submit Routine now uses ‘User Date’ instead of system date.
* Tag Submit window UI update

MFG PowerPack Release 2019-02-07

V12.1.143 / 14.1.90 / 16.1.56 / 18.1.17
* BOM History Inquiry: addressed issue that prevent setup options from being recognized for BOM History Inquiry.
* MO Split: added a NEW setup option to choose what the Suffix Separator is. Previously the module was hard-coded to use a DASH (i.e. MO00123-001). If MOSplit is already in use, installing this build will detect that and automatically update MO Split Setup to use a DASH as the seprator. Setup will allow using any single character as the separator. This change also addresses a conflict between MOSplit and WilloWare’s MO Generator “Create Child MOs” utility, which also uses a DASH.

MOGenerator Release 2019-01-10

V12.1.90 / 14.1.65 / 16.1.43 / 18.1.10
* MO Receipt Integration: addressed issue in the 7-JAN-2019 build that caused the Build Picklist routine to fail.
* MOGen-Create Child MOs: addressed issue that could cause the routine to run a second time on a Sales Order.

ETO Release 2019-01-18

V12.1.31 / 14.1.14 / 16.1.7 / 18.1.3
* Add/Edit Component: addressed issue that caused error “This BOM Line is already in use” when tabbing out of the BOM Line field.
* ME: Added visual indicator to show when one or more Est Qtys have been marked as Accepted
* ME: Added GoTo option “Create MO”. The ME window can now create a Manufacturing Order for the Item on an Accepted status estimate. If the Estimate is linked to a Sales Line, it will link the MO to the Sales Line.
* ME Notes Windows: added text to the Save and Delete buttons

MFG PowerPack Release 2018-12-05

V12.1.142 / 14.1.89 / 16.1.55 / 18.1.16
* Capable to Promise (CTP): Added integration to SOP Entry. CTP can pull in a selected item, or all items, from a Sales Transaction.
* MO Split: Updated the routine that creates the MOP-SOP record for each split so that it repeats attempting to create the MOP-SOP record until it can confirm the record exists. This was done to address a rare, sporadic issue at a high volume site where a single MOP-SOP (i.e. 1 out of 20 splits) would not get recorded into the MOP-SOP Links table.
* NEW: BOM History Inquiry: This is a “most recently used” list for GP Manufacturing BOM Entry and BOM Inquiry. Also, it adds a hot key (CTRL + Z) to zoom to a selected subassembly. Use CTRL+Z instead of the “Select Item” button on the BOM windows. “Select Item” only works when zooming to a subassembly that has the same BOM Type & BOM Name as the Parent Item (i.e. if the Parent is a MFG BOM and the child is an ENG BOM, it will not zoom to the ENG BOM). The CTRL+Z zoom will load any selected subassembly and as BOMs are viewed they are recorded in the new BOM History window. To return to any previously viewed BOM, simply double-click on it in the BOM History window.

MFG PowerPack BOM History Inquiry

Price $1000

The BOM History Inquiry window is a “Most Recently Viewed” list for the BOM Entry and BOM View windows.  It provides quick access to a previously viewed BOM, making it easy to drill down into lower level assemblies and then quickly return to the top level.

It also adds a universal Zoom feature.  You can drill into any subassembly by clicking on it in the treeview and pressing CTRL+Z.  This will work with any BOM, such as MFG BOM or ENG BOM and also Configured and Archived BOMs.

Quickly retrieve a previously viewed BOM by double-clicking on it in the BOM History window, or click BOM Inquiry to open the BOM in the Inquiry window.

BOM History Inquiry works with both the BOM Entry and BOM Inquiry windows.

BOM History Inquiry also adds a hot-key (CTRL+Z) to zoom to ANY selected subassembly.  This addresses an issue with the “Select Item” button where it retains the BOM Type and BOM Name from the Parent Item when attempting to zoom to the Component, so that if a MFG BOM Parent contains a subassembly of another BOM Type (i.e. ENG, CONFIG, ARCH), the “Select Items” button will only zoom back to the MFG BOM of the subassembly.

MOGenerator Release 2019-01-10

V12.1.89 / 14.1.64 / 16.1.42 / 18.1.9 10-JAN-2019
* MOGen-MO Scheduler: Altered the restriction that prevents MOs from being rescheduled if they have MFG Component Transactions so that it allows Allocations.
* MOGen-Create Child MOs: Added check of Item Type so it only attempts to create MOs for “Sales Inventory” type items regardless of the SUBCAT_I setting in the Picklist table. This is check prevents the utility from attempting to process bad data when Picklists or BOMs have been imported into the SQL tables with invalid information.

ETO Release 2019-01-09

V12.1.30 / 14.1.13 / 16.1.6 / 18.1.2 Changes
* Cost Rollup: Changed the routine so it only pulls Component BOM Type = 6 (Mfg Est BOM) and treats subassemblies coming from GP Manufacturing as “buy” items and pulls their cost from Item Maintenance (#20185960). Previously it was incorrectly including other BOM Types (i.e. MFG, ENG, etc), attempting to recalculate the cost but arriving at $0 becuase the BOM for the item wasn’t located in the ETO module.
* Delete Estimation BOM: the previous build’s change to separate Child Windows into separate Forms causeD the Delete routine to fail without deleting anything.
* Add Component: Addressed issue that would allow entering and saving invalid BOM information for a Component.
* Copy BOM Utility: Routing Name can now be provided when copying a GP Manufacturing BOM.

MOGenerator Release 2019-01-07

V12.1.88 / 14.1.63 / 16.1.41 / 18.1.8
* MOGen-Create Child MOs: Addressed issue with new routine to process phantoms that caused the Reschedule MOs utility to not be able to traverse a series of related MOs (Parent MO–Child MOs).
* MO Receipt Integration: Addressed issue that caused the picklist creation to fail when importing components using the W7158MOPick table and the LNITMSEQ fields is greater than 32767 (#20186038).