Author: admin

MFG PowerPack Release 2017-05-01

V12.0.110 / 14.0.57 / 16.0.23 1-MAY-2017
* Vendor Pricing: addressed issue with multicurrency, when viewing a PO in Functional it is incorrectly using the value of the Alternate Cost (when no Price List was available) in the Originating Currency, as the Amount in the Functional Currency.
* Exploded BOM Report: addressed Illegal Address error in LLC calculation (#20171998)
* Quick Disassembly: addressed Illegal Address error caused by closing the IV Transaction window before clicking Process on the QD window (#20172045)
* OSRC Description & Cost enhancement: now work on the “Manufacturing Order/Purchase Order Link by Vendor” window

GP PowerPack Release 2017-04-25

V12.0.107 / 14.0.50 /16.0.18

  • ELA: Addressed syntax error when multiple lots are auto-generated during a PO Receipt and the Item has required lot attributes (#20171935)
  • SOP Print Defaults: addressed issue when transferring from Batch Entry that caused some options to be marked even though the batch did not contain the indicated SOP Type.

MFG PowerPack Release 2017-04-19

V12.0.108 / 14.0.55 / 16.0.21

  • Vendor Pricing: addressed issue with multi-currency where the Last Cost was pulled (in Functional) and used on the PO (in Originating).  It now pulls Last Cost if the PO Line Currency is Functional, and Last Originating if the PO Currency matches the Last Originating Currency ID.

GP PowerPack Release 2017-04-19

V12.0.106 / 14.0.49 /16.0.17

  • Extended Lot Attributes: addressed ‘illegal address’ error (#20171851)
  • SOP Print Defaults: addressed ‘illegal address’ error (#20171240)
  • SOP Print Defaults: added support for printing from SOP Batch Entry window
  • SOP Transfer Auto-Mark Options: added support for Batch Transfer

 

 

MFG PowerPack Release 2017-04-12

V12.0.107 / 14.0.54 / 16.0.20
(1) Scrap Reporting: addressed issue that caused the report to not display the User Defined Scrap Status codes, when present, and instead only used the default codes. NOTE: if you have modified this report, please see the “Preparation Steps” at www.willoware.com/install. The instructions discuss how to export the existing modifications and remove the modified reports dictionary prior to installing the new code.
(2) Updated WW Internal Resources

Consulting Toolkit Release 2017-04-06

V12.0.16 / 14.0.10 / 16.0.6

  • Virtual Triggers: (a) added support for storage or temporary parameters, (b) added an Export utility, (c) addressed issue that caused a ‘cannot find table’ error (#20171196)
  • Execute Stored Queries: addressed issue that caused a get/change error when attempting to execute a Query when the parameters window was left open from a previous query (#20171132)

SpellCheck Release 2017-04-03

V12.0.17 / 14.0.8 / 16.0.5  Changes 3-APR-2017

  • Addressed issue that cause get/change error on wSpellTrigs (#20170975)
  • Added check to ensure SpellCheck does not generate an error if Windows is missing MSXML2.DLL, or cannot access the internet (#20170928)
  • SpellCheck now automatically disables invalid SpellCheck locations, and provides more detailed messages about the issue (#20170129).
  • Setup window now provides more informative error messages for potentially invalid spell checking locations
  • Updated WW Internal Resrouces

Pro Forma Invoicing

Summary of Requirement

ACMECO makes innovative carrying solutions for the imaging world.  These are specialized backpacks, shoulder bags, camera pouches, rolling cases, etc., designed specifically for the needs of photographers and videographers.

Their worldwide distributors place orders on Business Portal, which feeds into Dynamics GP as Sales Transactions. ACMECO has the products made in overseas factories (China), and shipped in containers to the US.

There are two aspects of this process that require additional functionality in Dynamics GP.  First, the sales order lines need to be manually reviewed and split into smaller quantities based on freight container size and requested ship date.

Second, when a container is ready to be shipped, ACMECO needs to produce a pro forma Invoice to their customer for the shipment, and then record receipt of payment against the pro forma invoice.

 

Design Specification

DS0036

Material Test Report

Summary of Requirement

ACMECO manufactures equipment for Oil and Gas drilling.  The materials used (steel) in the manufacturing process have a large amount of testing data associated with each Lot Number that need to be tracked from purchasing through to distribution.

In some cases ACMECO acts only as a broker and never takes possession of the inventory, so they need to be able to record the material information for Lots that do not exist in inventory.

Conceptually the Lot Attributes window in Dynamics GP performs the correct function (in terms of tracking information), but needs to be expanded to track many more pieces of data.  Additionally, some fields are calculated based on the input in other fields.

ACMEco also needs to perform queries in Sales on the data to locate Lots of material that have particular characteristics.

ACMEco sometimes needs to record supplementary test information for a specific customer’s order (large amount of free notes).

Lastly, ACMEco needs to generate a report that shows all of the material information associated with the Lot when the product is sold.  There is a specific format for this Material Test Report (Certificate of Analysis).

 

Design Specification

DS0030

DS0030_MTR_Maintenance

DS0030_MTR_Sample

Smart Bin Lookup

Summary of Requirement

ACMECO manufactures forged steel pressure flanges.  The materials used include alloys, stainless, and carbon.  The material in stock has a wide range of physical attributes, some of which are coded into the Item Number.  To fulfill customer requests, ACMECO needs to quickly locate on-hand material that has certain characteristics (i.e. Material Type and Pressure Rating).

Bins are being used to group inventory by Material/Pressure Rating.

All purchased material is received into a default Bin, then manually transferred (Bin-to-bin transfer) into the correct bin for the material/pressure rating.

There are a large number of bins (about 650), so the user has to scroll through a large number of bins to select the correct one for the material.  This situation also makes it very easy to pick the wrong bin.

The combination of Material, Pipe Size and Item Class determines the Bin.  The Item Numbering logic is as follows:

 

Finish Material Pressure Rating Type Pipe Size
Char 1,2 Char 3,4 Char 5,6 Char 7,8 Char 9, 10

A solution is desired that will look at the Item being transferred, and restrict the list of displayed Bins so that only valid bin(s) are in the lookup.  It should also prevent the user from manually typing in an incorrect bin.

 

Design Specification

DS0027

POP to SOP Freight

Summary of Requirement

ACMECO creates drop-ship purchase orders from sales order processing.  When the PO invoice is received, the freight charges need to be passed along to the customer.  Currently this is a manual process that requires locating the linked sales order, and adding a line to the sales order for the freight charges.

A sales order could be linked to more than one PO, so as each PO is received the additional freight charges are manually added to the sales order as additional “freight lines”.

The desired solution would automate the process of adding freight charges from PO invoices to the linked sales orders.

 

Design Specification

DS0023

One Step Void Check and Voucher

DS0018

Void Check Enhancement

 

Problem Definition

ACMECO is a company that handles property foreclosures. They print checks in advance to be executed during the foreclosure sale. Often the sale is canceled and the checks and associated vouchers in AP need to be voided.

This is a two-step process in Dynamics GP:

1) Void the check

2) Void the voucher

Additionally, after the check is voided it no longer shows which vouchers it was originally associated with.

With a large customer they will have numerous voided checks and vouchers that require quite a bit of manual time to research which voided vouchers were assigned to which voided check. They need to maintain this association for quality and audit purposes.

There are two key requirements:

  1. When voiding payments provide a method to automatically void the associated vouchers
  2. Retain the original apply information, and provide a method to view that information

Design Features

Modifications to Void Historical Payables Transactions (VHPT)

When the applied Payment is voided, and the associated Voucher (or vouchers) is “un-posted”. The Voucher is removed from History and moved back into the Open transaction table. The distributions and any other applied document records are also moved back into the open tables.

The original apply record (of the voided Payment and the Voucher it was applied to) is deleted. This action loses the historical integrity of voided documents. Retaining this information is an objective of this design.

VHPT has the ability to void multiple payments (payments, returns, credit memos) for multiple vendors at the same time. When the user clicks the VOID button, the custom code will capture document information for each voided document and move the historical apply information to another table so that it can be referenced later.

When the void process is complete, a new window will open called Void Applied Vouchers. This window will display all of the Vouchers to which the voided payments had been applied, and all will be auto-marked to be voided.

VoidAppliedVouchers

The user will be able to select a document in the window and zoom to view the document in an Inquiry window. NOTE: the window will only display documents that CAN be voided—i.e. they have no other payments applied to them, or all payments that were applied to them have been voided.

When the user clicks the VOID button they will be prompted to confirm they want to void the selected transactions.

Modifications to Payables Apply Zoom (PAZ)

When the user opens Payables Apply Zoom, which is used to view the apply information for all payables document types, a new Extras menu will be available: Extras >> Additional >> Voided Apply.

A new window, Payables Voided Apply Zoom will be created to show the historical apply information. It will look identical to the existing Payables Apply Zoom window:

Bill of Lading

Summary of Requirement

ACMECO distributes agricultural chemicals, pesticides and fertilizers.  They are currently using Dynamics GP, and are looking for a way to eliminate some manual record keeping by the Traffic Department and Scale Operators, by bringing this external data into the system.

The external information falls into three broad areas:

  • The Traffic Department records information about the freight company or customer’s truck that will pick up the product. This information is used to generate the Shipping Schedule Report
  • Scale Operators record information about each individual shipment that is used to produce a Bill of Lading Document
  • Additional information needs to be captured about each Item Number to handle concentration and purity calculations (Conversion Factors).

Design Specification

DS0014

DS0014_Instructions

BOL Sample

 

Tracking Eaches Selling Feet

Summary of Requirement

ACMECO sells drywall and other building materials.  The products are purchased from vendors in many different units of measure, but are always treated as “eaches” by ACMECO.

For example, drywall is purchased per Thousand Board Feet, but is sold as 1-Sheet.  In some cases this conversion does not result in an exact conversion—such as a conversion yielding 4.999 sheets which should actually be 5.

Dynamics GP requires the unit of measure used on a Purchase Order Receipt and a Vendor’s Invoice to match the unit of measure used on the Purchase Order.

Since ACMECO treats their inventory in whole units, the desired solution would allow them to set up inventory in whole units in Dynamics GP, while being able to:

Print Purchase Orders showing a Unit of Measure used by the vendor (such as MSF or MLF).

Receive the Vendor’s Invoice in the vendor’s units of measure and easily match it to the quantity received (in whole units).

 

Design Specification

DS0012

DS0012_Instructions

 

International Shipping

Summary of Requirement

ACMECO is an exporter.  They need to have a specific format to Quotes, Orders and Invoices to capture insurance and freight/shipping related costs.  These details should appear in an extended “subtotals” sections on the sales documents.

ACMECO needs to list the item(s) being sold, then display one or more lines related to shipping (freight, insurance, duties, etc), then display a subtotal, then have additional lines of added processing costs, and another subtotal, and so on.  While there are often no more than two or three such sections, there could be many.

ACMECO have Spanish and English speaking customers.   A secondary requirement is to support printing documents in Spanish or English.  A Spanish speaking customer should always get documents in Spanish.

 

Design Specification

DS0006

DS0006_Instructions

 

Manufacturer Representative

Summary of Requirement

ACMECO sells direct (where they act as a distributor), and also as a representative of a manufacturer. In the rep sales, ACMECO receives a commission from the manufacturer for the sale, but manufacturing, order fulfillment and invoicing all occur through the manufacturer. Sales Transactions are either completely direct (ACMECO has the inventory) or completely done as a representative (MFSO).

The process is as follows:
– Customer places an order with ACMECO
– ACMECO takes the order and sends order information to the manufacturer (this is referred to below as a Manufacturer’s Sales Order, or MFSO).
– The manufacturer sends back confirmation of order information (quantities & pricing), and commission rates.
– The manufacturer fulfills the order and invoices the customer. The manufacturer sends a shipping notification to ACMECO to alert them that the order has been fulfilled (this may be in several partial shipments)
– ACMECO creates a commission invoice to the manufacturer for the sale (the Invoice is not sent to the manufacturer). Commission Invoice may be for the commission due on a partial shipment.

ACMECO needs to record the sale and keep a historical record of it, and also needs to know for which sales lines commissions have already been invoiced and paid.

The desired solution will:
– Allow ACMECO to take sales orders in GP and track them in history
– Communicate order information electronically to the manufacturer (optional)
– Automate creation of Commission Invoices.

  • A Sales Order is entered in GP
  • When Items are added the system captures the default commission percent for that item and stores it on the Sales Line
  • Order is printed and sent to Manufacturer
  • Manufacturer sends back confirmation of order. This has the Manufacturers Order Number (to be recorded in a SOP User Defined Field)
  • Any necessary changes are made to the Order
  • Manufacturer sends notification of shipment to ACME, and sends Invoice and Product to Customer
  • A Commission Invoice is automatically created in AR for the commission due on the items fulfilled by the shipment
  • When the Order is completely Invoiced it will move to history
  • Manufacturer send payment for Commission, which is applied to the AR transaction.

 

Design Specification

DS0003

DS0003_Instructions

 

Granite and Marble Slabs

Summary of Requirement

ACMEco imports and sells granite slabs. Granite is shipped in a Bundle, which contains a number of Slabs granite where the total square footage contained in the Bundle is about 300 square feet. A Slab is approximately 126 inches by 54 inches, or about 50 sq ft, so there is usually about 6 or 7 Slabs in a Bundle. The between-Slab variation in dimensions can be about +/- 10 IN.

Most granite is imported, and a Packing Slip will be received about 3 weeks prior to receipt of the granite. The Packing Slip details the number of Bundles, Slabs, and the Slab Dimensions. The producer usually measures the Slabs in CM, so ACMECO needs to convert to IN, however some manufacturers do provide measurements in IN.

During receipt each Slab is measured. ACMECO tends toward using a “generous” measurement. The difference in measuring techniques between the producer and ACMECO usually results in a variance between the received quantity and what is on the Packing Slip.

ACMECO will have an Item Number for each type or style of granite, such as Classico or New Venetian Gold. It is further assumed that there will be a separate Item Number for each Thickness—so 2cm Classico has a different number than 3cm Classico.

The Item Numbers will be Lot Controlled, and the base Unit of Measure is a square foot (SQFT). There will be one Lot Numbered generated for each Slab. For example, if a Slab were received with 126×54 IN, LOT123 would appear in the system as having 47.25 SQFT On Hand.

Since a Lot Number is a “group” of square feet of granite, which is actually a single Slab, a key requirement is the ability to store the actual dimensions of the slab attached to the Lot Number. This requirement has effects that flow from PO receiving, to Inventory maintenance, through to Sales Orders, fulfillment, and warranty claims.

The following sections describe in more detail the impact of Slab Dimensions in each area of the Dynamics GP inventory system, and present the proposed solution in each area.

 

Design Specification

DS0002

DS0002_Instructions

 

GPPowerPack Release 2017-03-21

V12.0.105 / 14.0.48 /16.0.16

  • U of M Change Utility: addressed issues that could cause the following tables to not update correctly: IS010210 (Mfg Shipping History Line), MOP1210 (MOP_PickDoc_Line), IV00104 (Item Kit Master), IV00106 (Item Purchasing).  Picklist now updates for all MOs that are not Complete or Closed.

Quickly Create And Update Items with Item Copy

ItemCopy (in WilloWare’s MFG PowerPack Suite) creates a new Item by copying settings from an existing Item.  “But wait,” you say, “Doesn’t GP already have an Item Copy?”

Yes, but the list of what the GP Item Copy can copy is pretty short (see above).

WilloWare’s Item Copy covers much more, including all of the Manufacturing related information.  It has options for copying Notes (Item Notes, Routing Sequence Notes), mapping Routings to the new Item, choosing which BOMs to copy, and much more.

The real unique power of WilloWare’s Item Copy is that it can create AND update Items from an Excel spreadsheet, or from a SQL staging table.

Sample of the staging table

Sample of the Excel spreadsheet

In both examples, the first row shows a “add new item” record, and the second row shows an “update existing” record.

By using the table or Excel import utilities, a large number of new items can be created quickly by copying from “template” items.

It can also update specific fields on existing items, and as part of creating a new item.

When importing from Excel, field updates are created by using the Table Name and Field Name as the column header, such as IV00101.USCATVLS_1.  The “new value” is entered into the rows below the column header.

The Excel spreadsheet shown above would update CAP100 to set the User Category #1 field to “Rev 2”.

The Excel and Table import utilties provide an easy way to load all of the setup needed for new items when implementing GP.  In a simple manufacturing environment, the Template Item could have a simple 1-step routing, which could be copied to new items, saving the step of needed to manually create hundreds or thousands of routings.

It could also be used as part of an on-going integration to support an external quoting system, or engineering system, which needs to create new items.  A simple integration to the staging table (New Item & Template Item) are all that would be needed to automatically create the Items in GP.

MFGPowerPack Release 2017-03-16

V12.0.106 / 14.0.53 / 16.0.19

  • ItemCopy: added functionality to mass import new items from Excel, or via a table Import. The Excel and Table import utilities can also update existing items.
  • Serial/Lot Mass Generate: addressed issue that caused an illegal address error when the Serial/Lot Entry window was close before the Generate window (#20170825).
  • Addressed issue that caused Class Not Registered error in functions that attempt to use Excel when Excel is not installed (#20170777).
  • Sales Forecast Import: addressed illegal address error caused by closing the window while it is importing a forecast (#20170763).

 

 

GPPowerPack Release 2017-03-10

V12.0.103 / 14.0.46 /16.0.14

  • Bank Deposit Filters: fixed an issue with the “Mark All” support added in v11.0.129/ 12.0.83 / 14.0.26 (9-MAR-2016) which could incorrectly calculate totals for the deposit. When this happens the Receipt Count (RCPTCOUNT) and/or Deposit Amount may not match the total of transactions recorded on the deposit in CM20300. To resolve, void the Deposit and re-enter it.  With this release the Mark All button can only be clicked once.  If the Filters are changed and Mark All is clicked again, the user will be warned that previous selections will be unmarked if they continue.

GP Report Extender Video

GP Report Extender (GP-REX) is a Report Writer enhancement that allows easily adding any field, from any table, to any GP Report Writer report.

You do not need to know VBA or Dexterity.  You just need to be able to write a simple SQL query.

The new video demo shows how easy it is to add a field…from a different DATABASE…to a report running in Fabrikam.

View the video here: //youtu.be/ArEgnkmXwpI

 

MOGenerator Release 2017-03-08

v12.0.61 / 14.0.36 / 16.0.14

(1) Go GP2015 (v14)/GP2016 (v16): exposed the following procedures for service based architecture: Extern_CreateMO1, Extern_CreateMO2, Extern_CreateMO3, Extern_CreateMO4, Extern_MORIBatch, Extern, MORISingleMO.

MFGPowerPack Release 2017-02-27

V12.0.105 / 14.0.52 / 16.0.18

  • PowerATP: the routine that retrieves Sales demand was not netting it against linked Purchase Orders. The POs were correctly netting against Sales demand.  The result was that Sales demand would remain in the calculation while the POP supply disappeared.  This has been fixed.  SOP demand now nets against POP so the demand and supply both are removed from the ATP calc when the documents are linked.
  • Serial Number Pre-Assign: now supports Lot Numbers (module name has been changed to Serial/Lot Pre Assign). Also, the module now supports custom business logic for generating serial/lot numbers.

More Info…

To learn more about Serial/Lot Pre-Assign, check-out the manual:

Serial/Lot Pre Assign

 

 

 

MFGPowerPack Release 2017-02-10

V12.0.104 / 14.0.51 / 16.0.17

  • EMOS Options: added “APS Integration” to support Releasing MOs through the Edit MO Status window that were rescheduled by Planet Together
  • EMOS Query: added a query builder to create queries for restricting the MOs displayed in the Edit MO Status window
  • Updated WW Internal Resources

More Detail…

EMOS (Edit MO Status) Query allows building a complex query to retrieve subsets of MOs in the EMOS window.  For example, you could retrieve only MOs that have a Configured BOM and a Routing Sequence that occurs in Work Center SAW.

The EMOS Query joins the following tables in its queries:

Work Order Master

Picklist

Working Routing

Item Master (joined to the Work Order Master Parent Item, and also to the Picklist Component Item)

Item Engineering (joined to the Work Order Master Parent Item, and also to the Picklist Component Item)

Dynamics GP Report Extender

We just released (06-FEB-2017) an exciting new feature in Consulting Toolkit called GP Report Extender (GP-REX).  GP-REX adds Report Writer functions that allow retrieving data from any table in the database.

A quick internet search on “Dynamics GP Report Writer” and “How can I add a field” yields pages of results.  This has been a frequent challenge with Report Writer for the entire history of Dynamics GP.  If a table is not already linked to the report, or a table linked to the report does not have relationships defined to the needed table, the is no way to get the data on to the report.

GP-REX solves this problem by providing Report Writer functions that execute SQL Stored Procedures.  The Report Writer functions pass parameters to the Stored Procedures where anybody proficient with tSql can code a query to retrieve the desired information.

Report Extension

Use GP-REX to:

Retrieve information from 3rd Party Products or customizations

Perform complex text manipulations (i.e. masking a SSN or Bank Account)

Perform complex calculations

Update other tables (since GP-REX is in SQL, you could have it add records to a table to track each time a report is printed, or make other updates to the database during printing)

Perform language translations (i.e. have column headers and item descriptions print in the Customer’s language)

Add amount paid, or a “Paid In Full” message, to an invoice

Think of GP-REX as Report Writer functions that are actually stored procedures.  It unleashes the capability of tSql  to accomplish any task* you want from a calculated field on a GP Report.

* By “any task” we mean anything you can do with tSql. 🙂

We at WilloWare are very excited to bring you this new tool that solves such a common problem.  Read more about it here:

//willoware.com/products/consulting-toolkit/

 

CTK Release 2017-02-06

V12.0.15 / 14.0.9 / 16.0.5

  • GP Report Extension (GP-REX)-report integration that provides the ability to add any field from any table to a GP Report Writer report.  As long as the GP report has the key fields that allow retrieving the desired data from a SQL table, the information can be pulled on to the report.
  • Updated WW Internal Resources

 

LeanMFG Release 2017-01-31

V12.0.26 / 14.0.15 / 16.0.5

  • BOM Maintenance: Removed ‘required’ property from Draw From/Post To sites.  Sites can now be entered on the BOM Header, or Lines, both or neither.  Sites set on the BOM Header or Lines are given precedence over sites set on the MO.
  • MO Entry: MO Entry now uses sites in the following manner: when a new MO is created the sites will come from the BOM Header, if present, and then the Default Sites from the MO Doc Type Setup.  The Sites can then be changed on the MO.  When the picklist is built, sites will come from the BOM Lines if present, then the MO.
  • Updated WW Internal Resources.
More Detail…

Sites can be used in the following manner:

  • Sites set on the BOM Header but not on the BOM Lines.  When the MO is created, the BOM Header sites will populate the Draw From and Post To Sites on the MO.  By default, components will be drawn from and posted to the “default sites”.  However, changing the sites on the MO would cause components to draw from the new site, and the made item to post to the new site.
  • Sites not set on the BOM Header, but set on one or more BOM Lines.  This will force the system to always draw components which have a Site specified on the BOM Line to be consumed from the specified site.  Sites on the MO will be used to as the Draw From for any BOM Lines which do NOT have a site specified.
  • Sites not set on the BOM Header or Lines.  The MO Sites will come from the default sites specified on the MO Doc Type.  Creating an MO Doc Type per Site, and assigning Sites to the MO Doc Type, would be a quick way to always default to the correct sites for that location.

Lastly, Sites can also be manually changed on a per-line basis on the Inputs and/or Outputs tabs of the MO Entry window.

MOGenerator Release 2017-01-30

V12.0.60 / 14.0.35 / 16.0.13

  • MOGen: Deleting a Parent MO from the MO Entry window will now prompt if you want to also delete Child-MOs, then proceed to delete all of the linked Child-MOs.
  • Error Log: added sorting options to the Error Log window
  • Updated WW Internal Resources
More Detail…

MO Generator creates Parent-Child MOs for the top level assembly (i.e. 100XLG) and the child assemblies below it (i.e. BA100g).  Deleting a Parent MO from MO Entry will follow the normal checks that Manufacturing performs before allowing an MO to be deleted.  If the Parent MO can be deleted, MOGen will prompt:

Delete Child MO

As the Child-MOs are deleted, progress is displayed in the Title Bar of the MO Entry window:

Delete Child MO

The MOGen Error Log window previously sorted by the Date Time Stamp field, which is a string field.  This resulted in the field sorting as a string, which put “30 AUG” and “30 NOV” together, for example.

MO Gen Error Log Sort

The window has a new Sort By drop-down list, which can sort by Date (the actual Date field), and Manufacture Order Number (which is sorting the Error Description field alphanumerically).

 

GPPowerPack Release 2017-01-27

V12.0.102 / 14.0.45 /16.0.13

  • Extended Lot Attributes: fixed ‘unknown identifier’ error in Lot Attribute Maintenance when returning to the Lot Entry window in LeanMFG (#20170370).
  • New Tweak: PM Apply Zoom-Zoom to Document
  • Updated WW Internal Resources
More Detail…

PM Apply Zoom to Doc

The Payables Apply Zoom window shows applied documents, but it is a dead end.  There is no way to get from a document in the scrolling window to view it in an inquiry window.

The new Tweak (PM Apply Zoom – Zoom to Document) adds an Additional Menu option (“Zoom to Document”), which allows selecting a document in the scrolling window and opening it in the appropriate inquiry window.

MFGPowerPack Release 2017-01-25

V12.0.103 / 14.0.50 / 16.0.16

  • ItemCopy: the COPY button on Item Maintenance will now prompt the user for which Item Copy they want to use: GP, WilloWare, or Ask Each Time. The setting can be cleared from the GoTo Button on the WilloWare ItemCopy window, so that the next time the user clicks the COPY button it will again ask them what action they want the button to perform.
  • Updated WW Internal Resources.
More Detail…

WilloWare’s ItemCopy can be launched from Item Maintenance via the Additional Menu, or by clicking the COPY button.

Item Copy

When you click COPY, it will prompt:

Item Copy

The choice made here is saved, per user.

Item Copy

The ASK option will prompt the user each time COPY is clicked.  Otherwise, selecting the GP or WILLOWARE option will result in the desired window opening directly without being prompted.

Item Copy

The setting can be cleared from the GoTo button on WilloWare’s Item Copy.  The next time COPY is clicked on Item Maintenance, it will prompt again for the user to make a choice about which action the button should perform.

LeanMFG Release 2017-01-25

V12.0.25 / 14.0.14 / 16.0.4

  • MOEntry: fixed registration key issue that caused the “Serial-Lot Copy” option to not display on the GoTo Button
  • BOM Maintenance: (a) fixed illegal address error when the window is closed while the treeview is displaying (#20170198). (b) Added Default BOM Line Spacing so it uses 10 if Setup does not specify another value. (c) Added control on BOMLine to enforce it being greater than zero. (d) Added Item Description to the BOM Simple report.
  • Serial-Lot Linking: Mark All button now considers the “Use Serial/Lot Link Qtys” option and, if marked, it will automatically link all available component quantities.
  • BOM Inquiry: (a) fixed illegal address error when the window is closed while the treeview is displaying (#20171097). (b) fixed Report button so it prints the BOM Simple report and attachments.
  • Update WW Internal Resources

MFGPowerPack Release 2017-01-19

V12.0.102 / 14.0.49 / 16.0.15

  • BOM Alternates: changed to prevent multiple “flashes” of the Alternates window after clicking Schedule MO.
  • Setup Window: relabeled “Features” as “Modules”
  • MO Doc ID: fixed issue that caused the “Remember My Doc ID” option to fail to automatically select the correct Document ID.
  • BOM Archive: fixed illegal address error caused by closing window while it is creating the archive BOM (#20168099)
  • Updated WW Internal Resources

SpellCheck Prior Builds

V12.0.15 / 14.0.6 / 16.0.3  Changes 5-AUG-2016

  • SpellCheck converted to use a web-service. MS Word is no longer required.  SpellCheck now supports the Web Client.
  • Updated WW Internal Resources

V12.0.14 / 14.0.5 / 16.0.2  Changes 14-JUN-2016

  • Updated WW Internal Resources

V12.0.13 / 14.0.4 / 16.0.1  Changes 8-MAY-2016

  • Updated for GP2016 (v16)
  • GP2010 (v11) discontinuation of maintenance & support

V11.0.17 / 12.0.12 / 14.0.3 Changes 30-MAR-2016

  • When registering spell check locations, added check that the product for a spell check location is still installed

V11.0.16 / 12.0.11 / 14.0.2 Changes 1-DEC-2015

  • Made SpellCheck window an internal resource so users always have security access
  • Updated WW Internal Resources

V11.0.15 / 12.0.10 / 14.0.1 Changes 28-JAN-2015

  • Updates for GP2014 (v14)
  • GP10 Discontinuation of maintenance & support

V10.0.18 / v11.0.14 / 12.0.9 Changes 29-SEP-2014

  • Updated WW Internal Resources

V10.0.17 / v11.0.13 / 12.0.8 Changes 17-SEP-2014

  • Updated WW Internal Resources

V10.0.16 / v11.0.12 / 12.0.7 Changes 17-JUL-2014

  • Updated WW Internal Resources

V10.0.15 / v11.0.11 / 12.0.6 Changes 13-SEP-2013

  • Updated WW Internal Resources
  • Installation process inside GP can now be run under DYNSA
  • Installation process now creates a default Security Role called SPELLCHECK and assigns the SPELLCHECK Security Task to the Role.

V10.0.14 / v11.0.10 / 12.0.5 Changes 31-JUL-2013

  • Updated WW Internal Resources

V10.0.13 / v11.0.9 / 12.0.4 Changes 26-JUNE-2013

  • Updated WW Internal Resources

V10.0.12 / v11.0.8 / 12.0.3 Changes 2-FEB-13

  • Updated WW Internal Resources
  • MSWord now pops to the foreground
  • Converted to use web-based help documentation

V10.0.11 / v11.0.7 / 12.0.2 Changes 17-JAN-13

  • Fixed issue with Spell Check Setup that was causing GP to hang when searching for windows within a form.

V10.0.10 / v11.0.6 / 12.0.1 Changes 19-NOV-12

  • Updated WW Internal Resources
  • First GP2013 Release

V10.0.9 / v11.0.5 Changes 10-FEB-2012

  • Updated WW Internal Resources

V10.0.8 / v11.0.4 Changes 16-SEP-2011

  • Install: fixed install process “task” error. The installation process creates a security TASK called SPELLCHECK.  In some international environments this generated an error due to a date formatting issue.
  • Updated to new Install form that can install into all Company databases at the same time.
  • Fixed hidden carriage return added by SpellCheck when returning the corrected string/text.

V10.0.7 / v11.0.3 Changes 28-MAY-10

  • SpellCheck Setup: added a Done button to prevent confusion with Save button. Save button no longer allows saving a blank trigger location.  A line can now be selected without having to mark/unmark the “Disable” checkbox.

V10.0.6 / v11.0.2  Changes 4-MAY-10

  • Added routine to auto-create a security Task for SpellCheck in v10 and higher.

V10.0.5 / v11.0.1 Changes 28-APR-2010

  • Removed proprietary dictionary and spell check routine, integrated into MS Word
  • Added ability to attach SpellCheck to any string or text field.

V10.0.4 Changes 19-FEB-09

  • Released as Freeware

V10.0.3 Changes 16-May-2008

  • Corrected name on Registration Window
  • Relocated source dictionary files to GP\Data folder

V10.0.2 Changes 4-Apr-08

  • New Release.

Preactor Integration Prior Builds

V12.0.10 / 14.0.6 / 16.0.4 Changes 14-DEC-16

  • Export: changed BOM Export (aka Picklist Export) to subtract Qty Issue, Allocated and Backflushed from the Picklist Quantity.  Previously it always exported the full Qty Required.

V12.0.9 / 14.0.5 / 16.0.3 Changes 21-OCT -16

  • Setup: added syntax check on custom export query to ensure the tSql is valid (#20166444)
  • Import: changed date parsing routing to use SQL datepart() function (#20166211)

V12.0.8 / 14.0.4 / 16.0.2 Changes 28-JUL -16

  • Export utility: (a) added option to include (or not) inventory stock records where zero quantity is available, (b) Changed PO Qty records to pull Required Date rather than Due Date

V12.0.7 / 14.0.3 / 16.0.1 Changes 26-JUL -16

  • Updates for GP2016 (v16) release
  • Updated WW Internal Resources
  • Export utility now exports Inventory and Purchase Orders based on Picklists rather than the Bills of Material for the made items.

V11.0.10 / 12.0.6 / 14.0.2 Changes 1-APR-16

  • Update WW Internal Resources

V11.0.9 / 12.0.5 / 14.0.1 Changes 25-MAR-15

  • Discontinuation of GP v10 development and support
  • Upgrade to GP2015
  • Changed name of system generated Security Task and Role to API

V10.0.8 / 11.0.8 / 12.0.4 Changes 24-JUL-14

  • Updated WW Internal Resources

V10.0.7 / 11.0.7 / 12.0.3 Changes 14-APR-14

  • Updated WW Internal Resources
  • Added support for exporting Available Inventory information to Preactor

V10.0.6 / 11.0.6 / 12.0.2 Changes 1-SEP-13

  • Updated WW Internal Resources
  • Installation can now be run under DYNSA
  • Installation process will create a default Security Role called PREACTOR and assign the PREACTOR Security Task to the Role
  • Added WR010130.DONECB_I to wvPreactor

V10.0.5 / 11.0.5 / 12.0.1 Changes 15-FEB-13

  • First GP2013 Release.
  • Updated WW Internal Resources
  • Updated to use web-based help documentation

V10.0.4 / 11.0.4 Changes 29-MAR-11

  • Changed BOM Export routine to use a tSql view (wvBOMExport). The view can be modified to alter the BOM Export to meet site-specific requirements.

V10.0.3 / 11.0.3 Changes 10-MAR-11

  • Changed BOM Export routine to use the Picklist file (PK010033), to sum quantity requirements, and to not export the phantom item (just the components).
  • Export to CSV routine now strips apostrophes, commas and quotation marks

V9.0.3 / 10.0.2 / 11.0.2 Changes 4-FEB-11

  • Added support for Preactor v11 BOM-Routing Link functionality in the BOM Export file.

V9.0.2 Changes 21-JAN-10

  • Added Uninstall window

V9.0.1 Changes 24-MAY-09

  • Initial Release

MOGenerator Prior Builds

V12.0.57 / 14.0.32 / 16.0.10 Changes 1-DEC-2016

  • MORI: (1) no longer requires MFG BOM if an alternate BOM is specified in MOHdrOpt, (2) no longer requires a Primary Routing if an alternate Routing is specified in MOHdrOpt, (3) ProcessSerLot now registers triggers once, then enables/disables on subsequent use, (4) Added MOSer table to support single receipts with multiple serial numbers, (5) Running multiple instances of MORI: Added a second check of wMOHdr Status immediately before processing starts to ensure a second processor has not already started on the same record.
  • MOGen-Create Child MOs: (1) now reads the parent’s picklist (rather than BOM) to create subassembly MOs, (2) Parent picklist’s draw from site becomes the child MO’s post to site, (3) Child MO Draw From site is determined, in the following order,  by looking at the BOM Line Issue From Site assigned to the component (if any), or the Component’s BOM Header record Default Issue From site, or the Scheduling Preference. (4) It now allows MOs to be created with past due Due Dates.
  • Fixed sql conversion error that occurred when updating time fields in non-USA SQL deployments.

V12.0.56 / 14.0.31 / 16.0.9 Changes  26-OCT-2016

  • Auto-Generate Child MOs from SOP: changed integration point so that it runs automatically for both Manual MO and Silent MO generation.  Creating Child MOs will now happen automatically without prompting the user.
  • Auto-Generate Child MOs: create child routine was incorrectly validating Item-Site combinations for the subassembly items against the MO Post To site rather than the Draw From Site.

V12.0.55 / 14.0.30 / 16.0.8 Changes 4-OCT -2016

  • MORI: when MORI creates a split-MO to record a partial receipt, and the Default Scheduling Preference does not have sites specified, it generated a picklist missing the Issue From Site. This caused a $0 Inventory Adjustment, which a material variance on the MO equivalent to the value of the missing raw materials.  The root cause is that Manufacturing’s Quick MO code (which MORI uses to create a picklist), only uses the Issue From Site specified on the Scheduling Preference. So if it is blank on the Scheduling Pref, it will be blank on the Quick MO Picklist.  MORI now corrects this, setting the Issue From on the Picklist to the Issue From on the MO.

V12.0.54 / 14.0.29 / 16.0.7 Changes 30-SEP -2016

  • MORI: added support for posting an MO receipt for an MO that has any of the following- Outsourced POs, WIP Data Collection, Component Transaction “Allocations”. This is only supported when posting a single receipt for an existing MO, it is not supported for posting partial receipts.
  • Schedule Preference Lookup: fixed issue that causes illegal address error when the lookup is opened from two different locations at the same time.

V12.0.53 / 14.0.28 / 16.0.6 Changes 23-AUG -2016

  • MO Receipt Integration: replaced call to MFG code with our own code because the MFG code does not check if a working routing exists before attempting to delete it, which resulted in errors when creating split MOs. (#20164463)
  • Installation: fixed error caused by process that updates wspMOGenInvenCheck if that procedure already exists (#20164809)
  • MO Receipt Integration: added routine to clear pre-entered ser/lot table for an MO Receipt prior to adding new ser/lot (#20165075)
  • MO Receipt Integration: added “batch processing” to MORI. It can now process a “batch” of MO Receipts at once, before waiting for posting to complete and the timer to kick-off another batch of receipts.

V12.0.52 / 14.0.27 / 16.0.5 Changes 15-AUG -2016

  • MO Receipt Integration: to improve processing speed, added a dex.ini switch to process receipts in groups (i.e. batches of 20). MORI defaults to batches of 0.  Add MOGenBatchSize=20 to the dex.ini file to change to a batch size of 20.  MOGenBatchSize=0 will process one receipt, then wait for the timer to kick-off another receipt, and MOGenBatchSize=20 will process 20 receipts, then wait for the timer to kick-off another batch of receipts.  It is recommended to use the smallest batch size possible to allow manufacturing time to finish posting receipts.
  • Updated WW Internal Resources

V12.0.51 / 14.0.26 / 16.0.4 Changes 4-AUG -2016

  • MOGen: (a) added wspMOGenChildAltRouting as a dummy stored proc that can be edited by the end-user to provide a Routing other than the Primary Routing. This is called when creating Child MO’s linked to parent MO. (b) MOGen now reports the Qty when ‘invalid qty’ is detected., (c) DROP PROC wspMOGenInvenCheck.  Parameters change with this build.  If you have customized the proc you will need to re-create your changes after installing this build. ReqDate was removed, and ParentMO was added.

V12.0.50 / 14.0.25 / 16.0.3 Changes 27-JUN -2016

  • MO Receipt Integration: fixed issue that cause MO Receipt to post without consuming components when (1) It is a complete receipt against an existing MO, (2) it is marked as the final receipt and (3) the picklist is being imported.
  • MO Receipt Integration: added check that receipt quantity is greater than zero (#20163854)
  • Updated WW Internal Resources

V12.0.49 / 14.0.24 / 16.0.2 Changes 15-JUN -2016

  • MOGen: Fixed issue in the “Create MO” utilities where if the import data for the first MO to be created has an error, it caused the remaining items to also fail to generate MOs but produce no error messages.

V12.0.48 / 14.0.23 / 16.0.1 Changes 17-MAY -2016

  • Updates for GP2016 (v16) release
  • GP2010 (v11) development and support discontinued
  • Added check that Excel can be Opened (#20162922)
  • Added deadlock handling to AllocateAll (#20161400)

V11.0.51 / 12.0.47 / 14.0.22 Changes 21-APR-2016

  • MO Receipt Integration: (a) added check to processor so it does not attempt to process receipts for locked MOs, or MOP-SOP linked MOs where the SOP Document is locked, (b) receipts for existing MOs no longer require the Item Number and Post To Site as they will be pulled automatically from the MO.

V11.0.50 / 12.0.46 / 14.0.21 Changes 29-MAR-2016

  • Update WW Internal Resources (#20161108)

V11.0.49 / 12.0.45 / 14.0.20 Changes 11-MAR-2016

  • Import utilities now clear screen when finished
  • MO Scheduler: (a) added ability to reschedule child MOs when parent MO is rescheduled, (b) fixed issue that was causing MOScheduler to incorrectly report there was activity on an MO which prevented re-scheduling.

V11.0.48 / 12.0.44 / 14.0.19 Changes 3-MAR-2016

  • Manual MO Gen: fixed issued that caused process to hang when generating child MOs (20160844)

V11.0.47 / 12.0.43 / 14.0.18 Changes 20-JAN-16

  • Added check during install to see if wsopMOGenInvenCheck already exists (20160285)
  • MOGen: MO Scheduler utilities: (1) can be provided a new due date and will reschedule the MO

V11.0.46 / 12.0.42 / 14.0.17 Changes 20-JAN-16

  • MO Receipt Integration: added suppression of “Sales Order Crossreference” report when receiving MOs linked to Sales Order.

V11.0.45 / 12.0.41 / 14.0.16 Changes 11-DEC-15

  • MO Receipt Integration: added Bin Number to the MOHdrOpt table. Integrations can now specify a Material Receipts bin for each MO, rather than using the default Material Receipts Bin on the Item-Site.

V11.0.44 / 12.0.40 / 14.0.15 Changes 11-NOV-15

  • MOGen: added MO Gen Status table (W7158MOGenStatus) which gets updated each time MOGen runs so that an unattended processor can be monitored remotely (20151898).

V11.0.43 / 12.0.39 / 14.0.14 Changes 28-OCT-15

  • MO Receipt Integration: Status on split MOs was not being set to NEW
  • MOGen: Added a new setup option: Use System Date. When MOGen is left running unattended, marking this option will cause it to automatically update the User Date each day.

V11.0.42 / 12.0.38 / 14.0.13 Changes 29-SEP-15

  • MOGen: The GP MFG scheduling routine only checks Down Days after it removes LTO. Correct behavior is to check Down Days in a way that results in changing the MO Dates based on LTO using Work Days.  This build replaces the MFG scheduling logic with our own scheduling routine that correctly calculates LTO work days.

V11.0.41 / 12.0.37 / 14.0.12 Changes 4-SEP-15

  • Added check to startup routine to confirm GP Manufacturing is installed.
  • MOGen: scheduling Child MO’s now checks for the Work Center Down Days when calculating the child’s Due Date.
  • MO Receipt Integration: now sets Status to 9999 while the MO Receipt is being processed. Changed the timing of when it sets Status to Done (2) so that it occurs after all posting is completed.

V11.0.40 / 12.0.36 / 14.0.11 Changes 25-AUG-15

  • MOGen: (a) changed description on child-MOs created for a phantom to reference upper-level parent MO, (b) child MO’s now created at same status as parent
  • Auto-Reschedule: added Setup option to control whether or not the Picklist is rebuilt during rescheduling.

V11.0.39 / 12.0.35 / 14.0.10 Changes 23-AUG-15

  • MO Receipt Integration: (a) Fixed issue where it would try to ‘consume’ phantoms. It now correctly allocates and consumes the components of phantoms, (b) ImportBOM – fixed issue where lot number allocations would have two or more lines including a negative quantity line.  Lot components are now correctly selected, allocated and consumed, (c) MOP-SOP Linking: it now looks for MOP-SOP Linking, and updates the linked Sales Order/Invoice as needed, and allocates the inventory, (d) when doing a “LastReceipt” as the only receipt for an MO, the system checks the Default Close Option and will either backflush components based on the quantity received, or consume the entire picklist quantity.

V11.0.38 / 12.0.34 / 14.0.9 Changes 21-AUG-15

  • Auto-Reschedule Child MOs- if Child MO’s are created, and the top-level Parent MO is rescheduled, MOGen can automatically reschedule the children. A new option in Setup enables/disables this feature.

V11.0.37 / 12.0.33 / 14.0.8 Changes 18-AUG-15

  • MO Receipt Integration: fixed issue with ser/lot numbered components that prevented them from being consumed correctly.

V11.0.36 / 12.0.32 / 14.0.7 Changes 29-JUL-15

  • API: the two methods (Extern_CreateMO2 and Extern_CreateMO4) which provide MOP-SOP linking functionality now look at the Down Days setting and Due Date Offset on the MFG Sales Preferences window.

V11.0.35 / 12.0.31 / 14.0.6 Changes 23-JUL-15

  • MO Receipt Integration: added MOHdrOpt table to provide overrides to default values. MOHdrOpt can be used to specify a specific BOM (i.e. a config BOM), a specific routing (i.e. by default the primary routing is used), and a Scheduling Preference.

V11.0.34 / 12.0.30 / 14.0.5 Changes 23-JUL-15

  • MO Receipt Integration: (a) fixed issue with “last receipt” setting when the final receipt needs to close the MO short of the full end quantity, (b) changed processor so it retrieves records by dex_row_id so that it always gets the ‘oldest’ record first, rather than by MO Number.

V11.0.33 / 12.0.29 / 14.0.4 Changes 21-JUL-15

  • MO Receipt Integration: (a) fixed issue with “last receipt” setting when there is only one receipt for the MO

V11.0.32 / 12.0.28 / 14.0.3 Changes 25-JUN-15

  • Added Application Programming Interface (API) functionality to provide the ability for other applications to use MOGen to create manufacturing orders.

V11.0.31 / 12.0.27 / 14.0.2 Changes 13-MAR-15

  • MO Receipt Integration: (a) fixed issue with importing routings which caused an error on the SETUPTIME_I field, (b) added routine to ensure the Working Routing Auto-Backflush Labor and Machine options are always set to TRUE.

V11.0.30 / 12.0.26 / 14.0.1 Changes 26-JAN-15

  • Updates for GP2015.
  • Changed MO Due Date restriction so it accepts “today” or after (rather than requiring due date in the future).
  • Removed requirement that child items be Make To Stock to be included by MOGen.
  • Fixed Scheduling Preference Lookup
  • Added stored procedure wspMOGenInvenCheck. End-user can modify this stored procedure to provide custom logic to determine whether or not an MO should be created for a subassembly.

V11.0.29 / 12.0.25 Changes 28-OCT-14

  • MO Receipt Integration: added detailed process logging

V11.0.28 / 12.0.24 Changes 14-OCT-14

  • MO Receipt Integration: added additional checks to ensure MOGen is correctly notified when processing for an MO has completed; removed use of ‘default form’ in MOGen processing script, replaced with fully qualified names.

V11.0.27 / 12.0.23 Changes 7-OCT-14

  • MO Receipt Integration: fixed issue with timer when importing partial receipts which caused it to not post the ‘split MOs’.

V11.0.26 / 12.0.22 Changes 6-OCT-14

  • MO Gen – Manual Entry: fixed issue where MOGen could create multiple copies of child-MOs. This was caused by a trigger re-registering each time the user switched companies

V11.0.25 / 12.0.21 Changes 3-OCT-14

  • MO Receipt Integration: changed processor so that it waits for posting to complete before starting to process another import record; added a status message showing number of records remaining.

V11.0.24 / 12.0.20 Changes 27-SEP-14

  • Updated WW Internal Resources

V11.0.23 / 12.0.19 Changes 12-SEP-14

  • MO Receipt Integration: when lot controlled components are included, and a specific lot number is provided, a new check has been added to see if there are negative allocations on the lot in the lot master (IV00300).

V11.0.22 / 12.0.18 Changes 5-SEP-14

  • Fixed issue with selecting lots imported in MOPick that caused the lot selection routine to loop.

V11.0.21 / 12.0.17 Changes 30-AUG-14

  • Fixed issue with MO Receipt Integration that caused it to not correctly allocate & consume serial/lot numbers from the MOPick Table.
  • MO Receipt Integration now supports backflushing serial/lot controlled components without needing to provide them in the MOPick table. Standard MFG auto-selection logic is applied.  Previously there was a check to prevent processing if the BOM had serial/lot controlled components and they were not provided in MOPick.  This restriction has been removed and the software will now auto-select serial/lot controlled components if they do not exist in MOPick.

V11.0.20 / 12.0.16 Changes 8-AUG-14

  • Fixed issue with MO Receipt Integration and Serial/Lot Numbers when multi-bins is enabled which caused the serial/lot to be created with a bin assigned.

V11.0.19 / 12.0.15 Changes 22-JUL-14

  • TABLE MIGRATION: MOHdr, MOPick and MORouting all have a new key column called SEQUENCE1, and MOHdr has a new column called LastReceipt. These changes were made to support integrating multiple partial receipts on existing MOs in GP. Data will be migrated automatically.  Existing integrations must take into account the new columns.
  • Fixed issue with MO Receipt Integration when running on the timer where it doesn’t pick up new MOs added to the table.
  • Updated WW Internal Resources

V11.0.18 / 12.0.14 Changes 7-MAY-14

  • Updated WW Internal Resources
  • Added MO Receipt Integration functionality.

V11.0.17 / 12.0.13 Changes 18-MAR-14

  • Updated WW Internal Resources
  • Setup window: fixed issue where setup option for “Auto-generate from SOP” was not displaying

V11.0.16 / 12.0.12 Changes 30-JAN-14

  • Updated WW Internal Resources
  • MOGen: major redesign of the UI to support new import options (Excel MO’s to create Child MOs, Excel Experlogix MOs). A new integration table supports external integrations that feed data into a SQL table rather than Excel.  Table import supports imports to (a) create MOs, (2) create child MOs, (3) process Experlogix MOs.
  • Error Reporting: MOGen no longer produces a report. All errors are recorded in a new error logging table (W7158ErrLog).
  • Scheduled Integrations: MOGen now has a “timer” mode where it can be set to run unattended and look for new records (in an Excel file, or the Import table) at a time interval set by the user.
  • The “Auto-generate from SOP” option no longer requires that users have security access to the MOGen window.

V11.0.15 / 12.0.11 Changes 13-SEP-13

  • Updated WW Internal Resources
  • The installation routine inside GP will now create a default Security Role called MOGEN and assign the MOGEN Security Task to the Role

V11.0.14 / 12.0.10 Changes 30-APR-13

  • Updated WW Internal Resources
  • Installation can now be run under DYNSA
  • Added Auto-Generate from SOP: MOGen will kick-off automatically when an MO is created from SOP.

V11.0.13 / 12.0.9 Changes 30-APR-13

  • Updated WW Internal Resources

V11.0.12 / 12.0.8 Changes 19-APR-13

  • Updated WW Internal Resources
  • Removed restriction in selection statement for subcomponents which required the primary routing to be present. This causes the items to be skipped.  This has been changed so those items are included but reported as errors.  Also added a check on the subassemblies to ensure they have an Item-Site record for the Post-To site assigned to the top level.  If not, they are skipped and reported as errors.

V11.0.11 / 12.0.7 Changes 19-FEB-13

  • Updated WW Internal Resources
  • Update addresses an issue where MOGen picked-up on the “max” MO Number from the MO master when attempting to generate new MO Numbers. An errantly entered MO0123 for an MO (instead of MO0000123) resulted in MOGen trying to always pick-up at MO0124 instead of the Next Num from MFG Setup of MO0000124 (for example).

V11.0.10 / 12.0.6 Changes 14-DEC-12

  • Updated WW Internal Resources
  • All MO’s will now have dates automatically adjusted to the first available non-Down Day.
  • LTO Offset calculation was not considering the Offset From setting causing the child due date to always be calculated x-days before the parent’s Start Date.

V11.0.9 / 12.0.5 Changes 22-OCT-12

  • Updated WW Internal Resources
  • Addressed an issue where the scheduling routine was not creating Suggested Shipments for MO’s with outsourcing. It also adds a new routine to re-update the working routing after scheduling the MO so the sequences have updated start/end dates from CRP.

V10.0.9 / 11.0.8 / 12.0.4 Changes 19-SEP-12

  • BuildPicklist trigger was re-registering multiple times causing multiple copies of subassembly MOs to be created.

V10.0.8 / 11.0.7 / 12.0.3 Changes 19-SEP-12

  • Removed a constant from wMfg:BuildMRP.
  • Updated WW Internal Resources

V10.0.7 / 11.0.6 / 12.0.2 Changes 13-SEP-12

  • Updated WW Internal Resources
  • Added Excluded Items and User Preferences

V10.0.6 / 11.0.5 / 12.0.1 Changes 30-JUL-12

  • Moved BuildPicklist trigger registration to WinPre on MOGen
  • Added support for Lead Time Offset
  • Updated WW Internal Resources
  • First GP2013 (v12) Release

V10.0.5 / 11.0.4 Changes 4-JUN-12

  • Added MO Status setting and ability to Allocate on Release

V10.0.5 / 11.0.3 Changes 4-JUN-12

  • Updated WW Internal Resources
  • Changes to date handling for international date formats

V10.0.4 / 11.0.2 Changes 19-APR-12

  • Updated WW Internal Resources

V10.0.3 / 11.0.1 Changes 6-JAN-2012

  • First Release on GP2010

V10.0.3 Changes 10-JUNE-2010

  • New MOs were not correctly updating MRP data

V10.0.2 Changes 11-MAY-2010

  • Added MO Description field

V10.0.1 Changes 31-MAR-2010

  • First Release

MFGPowerPack Release 2017-01-11

V12.0.101 / 14.0.48 / 16.0.14 Changes 11-JAN-2017

  • Sales Forecast Integration: (1) added option to export Sales History, (2) Import now marks invalid items in the spreadsheet by putting “<< Invalid Item” in the Item Description column, (3) Import will now add quantities if the same Item appears multiple times in the spreadsheet.
  • Batch Processing: changed trigger registration on Work Center Operations “Select” button to use the “new” Select button on/after GP12.0.1482 rather than GP12.0.1745.