Author: admin

MOGenerator 2025-02-21

Release Date:21-FEB-2025
GP Versions: 12/14/16/18
MOGenerator Build: 12.146
* MORI2: First release of MORIv2. This is the next version of MORI that is now based on the MO Receipt Entry window functionality (where the original MORI was based on the Quick MO window). This release does not change or replace the original MORI, there is no impact on existing MORI integrations. When MORIv2 is enabled a new Import Type will be available on the MOGen window. MORIv2 uses a different set of integration tables.

Customization CR1532- Consolidated Customer Name

Customization CR1532

Consolidated Customer Name

Description of Need:

ACME needs to group customers for reporting. GP does not offer an existing field that will serve this purpose. ACME would like this field added to the Customer Maintenance window and have the following properties:

  1. Contain a lookup so that the user can select values that have already been entered for previous customers.
  2. Contain user security so that only selected users can modify the value.

Description of Solution:

Navigation: Tools >> Setup >> Sales >> Consolidated Name Security

A screenshot of a computer Description automatically generated

FIeld Function
User ID Enter or select from the lookup a User ID. User IDs entered into this window will have the ability to add or modify Consolidated Names.

Navigation: Cards >> Sales >> Customer

A screenshot of a computer Description automatically generated

A new, read-only field will be added to the Customer Maintenance field labeled Consolidated Name. This field will be added using “virtual fields.” Virtual Fields are added at runtime and do not require modification to the window.

To add or edit the Consolidated Name, navigate to Additional >> Add/Edit Consolidated Name

A screenshot of a computer Description automatically generated

Field Function
Customer Number Displays the customer from Customer Maintenance.
Name Displays the name from Customer Maintenance.
Consolidated Name Enter or select from the Lookup a Consolidated Name. This is a 64 character, UPPERCASE text field. Values entered here will not be validated against any other values stored in the database. If the Lookup is selected, the custom lookup window will display all distinct values that have been previously entered for other customers. Values will be displayed as entered.

Assumptions/Requirements:

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
  2. The functionality described above is intended for the GP Desktop client.
  3. National Accounts functionality is NOT used.
  4. Advanced Distribution functionality is NOT used.
  5. Unless otherwise noted in this document, reporting is not included in this estimate.
  6. Unless otherwise noted in this document, Word Template functionality is not addressed.
  7. Unless otherwise noted in this document, the enhancement will not integrate with 3rd party products. Some examples of 3rd party products would be:
  • An ISV plug-in product including WilloWare products
  • A dexterity customization designed by another developer
  • Dynamics GP Modules including, but not limited to:
  • Project Accounting
  • MDA
  • Analytical Accounting
  • Copy functionality found in SOP, POP and Inventory
  • Field Service
  • Extended Pricing
  • Manufacturing

For information on this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

 

LeanMFG 2025-02-13

Release Date: 13-FEB-2025
GP Versions: 12/14/16/18
LeanMFG Build: 5.70
* MO Entry: (1) Default Cost Allocation Method now set to Manual in case it does not get set by the BOM, (2) Fixed issue that caused the IV Transaction Header Transaction Quantity Total to not be updated correctly. This issue appears if IV Checklinks is run and returns the message “Transaction quantity total was adjusted for document number MO0123”. The TRXQTYTL value in the IV Trxn Hdr does not impact posting or costing. (3) Fixed issue that could result in incorrect batch totals for the LEANMFG holding batch. This had no impact on posting but would appear when running IV Checklinks.
* NEW: Inventory Transaction Inquiry: SourceDoc zoom – added zoom to MO Inquiry.

GPPowerPack 2025-02-11

Release Date: 11-FEB-2025
GP Versions: 12/14/16/18
GP PowerPack Build: 9.187
* SOP Rules: NEW- “SOP Document ID-Buyer ID” and “UserID-BuyerID”: Link a Buyer ID to a SOP Document ID and/or a GP User ID. When a PO is created from SOP the linked Buyer ID will be populated on the PO Header. It uses DocID-BuyerID first. If that does not exist it uses UserID-BuyerID.

Customization DS0978- Miscellaneous Charge Detail

Customization DS0978

Miscellaneous Charge Detail

Problem Definition:

ACME is one of the world’s largest manufacturers of quality canoe, kayak, and stand-up paddles. They conduct both direct to consumer sales, and sales to resellers/distributors. The B-to-C line is handled through a web-store which integrates into Dynamics GP. The B-to-B line has some additional requirements that are not well addressed by GP.

The B-to-B line sometimes needs to record several “additional charges”, such as delivery fees or other processing fees. These cannot be added as additional lines on the transaction because they would be included in the Commissions Calculation and in the Payment Terms calculation.

The additional charges also need to post to separate GL accounts, and print on the sales documents (both open and historical).

Solution Overview:

WilloWare will add to Sales Transaction Entry the ability to record a list of additional charges. These charges will be an extension of the Miscellaneous Charges field in a new window called Misc Charge Detail.

When a Sale Invoice is posted, the enhancement will post a separate Journal Entry that reverses the credit to the Misc. Charges account, and instead posts a “detailed” miscellaneous charges transaction based on the Misc Charge Detail entries.

Design Features:

Misc. Charge Setup

Navigation: Tools >> Setup >> Sales >> Misc Charge Setup

A screenshot of a computer AI-generated content may be incorrect.

Misc Charge Setup is used to record the Items that will be available in Sales Transaction Entry in the Misc Charge Detail window. The Item Numbers entered here must be Item Type = Misc Charges. No other Item Types will be allowed.

Field

Function

Item Number

Enter a Misc Charge Item Number, or select an Item Number from the Lookup. Only Item Type = Misc Charge Items will be allowed.

Cost

Displays the Item’s Current Cost

The window will also check that each Item has a GL Account entered in the Inventory Account field on the Item Accounts window. If the Item is missing an account, the user will be warned and not allowed to continue with the Item.

Misc Charge Detail Entry

A close-up of a list AI-generated content may be incorrect.

The Misc Charge Expansion button will open both the Sales Tax Schedule Entry and the new Misc Charge Detail windows.

A screenshot of a computer AI-generated content may be incorrect.

Field

Function

Item Number

Enter a Misc Charge Item Number or select one from the Lookup. The window will only allow Accept Misc Charge Items from Setup. The Lookup will only show the Misc Charge Items from Setup.

Description

The Description defaults to the Item Description from Item Maintenance, but it can be changed in this window. The changes do not affect the actual Item Description, but are saved with the Misc Charge Detail.

Cost

Defaults to the Current Cost from Item Maintenance, but it can be changed on this window.

The same Misc Charge Item Number can be entered multiple times, if needed. As shown above, there are two “shipping” lines.

Saving the Misc Charges will update the Total Misc Charge on the Sales Transaction Entry window, and if applicable, recalculate taxes.

When Misc Charge Details have been entered, the Miscellaneous field will be locked (not editable), and the background color will be yellow.

If the Misc Charge details are NOT entered, the user will still have the ability to enter a Misc Charge directly into the field.

SOP Transfers & Posting

When a Sales Document is transferred, the Misc Charge Details will come along with the transfer to the new document. The Misc Charge Details can be edited as needed on the new document.

When a Sales Invoice is posted, the normal SOP Posting logic will occur, which is to CREDIT the Miscellaneous Fees account from Sales Posting Account Setup for the total amount in the Miscellaneous field.

The enhancement will then create and post a second Journal Entry which DEBITS the Misc. Fees account, and CREDITS the Inventory Account associated with each of the Misc Charge Items listed in the Misc Charge Detail Entry window.

A white background with black text AI-generated content may be incorrect.

The Batch ID will be upper case User ID and the date (YYYYMMDD).

The Reference will be “SOP Misc Charge Detail”.

The Distribution Reference on each line will contain the SOP Number (i.e. STDINV2277)

The enhancement will also work for Returns. If Misc Charge Details are entered, the Debit and Credit are reversed from Invoice posting. For example, posting the Return DEBITS the Misc Fees Account, so the enhancement will Credit that account, and Debit each of the Misc Fee Inventory Accounts.

It is assumed that users will not manually change the SOP Distributions to create multiple entries for the Type = MISC distribution. Prior to creating the Misc Charge Detail Journal Entry, the enhancement will check that the amount posted to the Misc Fees account matches the Total in Misc Charge Detail Entry, and if not, it will NOT create the adjusting journal entry.

The Journal Entry Number will be recorded in the SOP Misc Charge Details table for reporting purposes.

Printing

When a SOP Form is printed, the Misc Charge Details will print in the body of the report as shown below:

A close-up of a receipt AI-generated content may be incorrect.

NOTE: This example uses the Word Template because it was easy to mock-up the desired output. ACME uses GP reports and Liaison to email the documents.

For information on this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

Customization DS1413- Auto-Create POs and Link to Sales Orders

Customization DS1413

Auto-Create POs and link to Sales Orders

Problem Definition:

ACME uses True Commerce EDI and imports an 850 PO Document. This creates a batch of Sales Orders each day. ACME needs to create POs for each sales order and create a link between the sales line and PO line.

Solution Overview:

There will be no user interface for this enhancement. A progress bar will appear to indicate the enhancement is working and a report will print at the end to display the linked sales orders and purchase order information.

See the section below for details of the solution.

Design Features:

Creating POs from Sales Batch Entry

Navigation: Transactions >> Sales >> Sales Batches >> Additional Menu >> Create POs

When the enhancement is installed, an Additional menu option called Create POs will appear on the Sales Batch Entry window.

Graphical user interface, text, application, email Description automatically generated

The user will enter or select a sales order batch from the lookup.

The enhancement will:

  1. Ask the user “Are you ready to create and link POs?” Answering “YES” will kick off the process.
  2. Validate that the document type is ORDER (Other document types such as back orders and invoices will be skipped.)
  3. Validate that there are no links present. If one or more lines on a document are already linked to a PO, the document will be skipped. The report that prints at the end will identify this error.
  4. If the sales document passes the above validation, a new PO will be created. There will be one PO per Sales Order. The PO will have the following details:
  5. Type = Drop-Ship
  6. PO Number = Next Available
  7. Vendor ID = ‘001264’ (This is hardcoded)
  8. Ship To Address ID = Customer Ship To Address ID from the Sales Order
  9. Required Date = Sales Order Requested Ship Date
  10. Mark the PO to Allow Document Commitments.
  11. Once the PO is created, the enhancement will loop through each sales line where the Item Type is Sales Inventory, and do the following:
  12. Mark the line as Drop-Ship
  13. If the Item is serial/lot tracked and is fulfilled, the line will be unfulfilled
  14. If the line has been allocated, unallocated inventory
  15. Set the line quantities to Back Order
  16. Add a matching PO line to the new PO

If the Sales U of M is not a valid Purchase U of M, then an error will be reported and the line will be skipped.

  1. Create a SO-PO link
  2. Add a line to the report that prints at the end
  3. After all sales orders have been processed, a report will print that either lists an error condition or the SO-PO link information.

Assumptions/Requirements:

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
  2. The functionality described above is intended for the GP Desktop client.
  3. National Accounts functionality is NOT used.
  4. Advanced Distribution functionality is NOT used.
  5. Multi-bins is NOT enabled.
  6. Multi-Currency is NOT used.
  7. Unless otherwise noted in this document, reporting is not included in this estimate.
  8. Unless otherwise noted in this document, Word Template functionality is not addressed.
  9. Unless otherwise noted in this document, the enhancement will not integrate with 3rd party products. Some examples of 3rd party products would be:
  • An ISV plug-in product including WilloWare products
  • A dexterity customization designed by another developer
  • Dynamics GP Modules including, but not limited to:
  • Project Accounting
  • MDA
  • Analytical Accounting
  • Copy functionality found in SOP, POP and Inventory
  • Field Service
  • Extended Pricing
  • Manufacturing

For information on this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

MOGenerator 2025-01-30

Release Date:30-JAN-2025
GP Versions: 12/14/16/18
MOGenerator Build: 12.145
* MCTE Integration: Complete rewrite of the MCTE integration (Manufacturing Component Transaction Entry Integration). This release can handle all aspects of MCTE Issue transactions. It handles multi-bins, serial/lot-tracked inventory, and non-tracked. It can automatically issue all items from the picklist and auto-select bins, serial numbers and lot numbers. It can handle partial issues of specific items, and you can provide specific bins to issue from, as well as provide specific lot and serial numbers to issue.
* FULL INSTALLATION PROCESS REQUIRED:(1) rebuilds wMCTEItemDtl to drop the ITEMNMBR column, (2) creates wspAllocBinQtys stored procedure

Customization DS1576- Minimum Order Fee

Customization DS1576

Minimum Order Fee

Problem Definition:

ACME needs to implement a rule on sales orders where if an order subtotal is below a specified threshold amount, a fee will be added to the order. This fee needs to be automatically applied, or automatically removed when an order is saved.

Design Features:

The following functionality will only be active for Sales Quotes and Orders.

Minimum Order Setup

Navigation: Tools >> Setup >> Sales >> Minimum Order Setup

A screen shot of a order Description automatically generated

Field Function
Min Order Threshold Enter the threshold value that will be used to determine if a fee is required. Any document subtotal that is below this amount will have the fee added. If the subtotal is greater than or equal to this amount then no fee will be added.
Min Order Fee Enter the amount of the fee that will be added to the sales document.
Min Order Item Enter the Item Number that will display on the sales order for the fee. The fee will be added to the sales order as a NON-IV item, so this value cannot be an item that already exists in the item master, but the field format must conform to SOP line-item rules, so will be an upper case string with a maximum of 30 characters.

Sales Transaction Entry

Each time a sales order or quote is saved, the enhancement will check to document subtotal. If the subtotal is less than the threshold amount, the user will be notified: “This order total is below the minimum order threshold of $XX and a minimum order fee will automatically be added. Do you want to continue?”

If they click CANCEL, the save operation will stop and the user has the ability to add more items to the sales order to take it over the threshold amount.

If they click CONTINUE, the non-inventory item from the setup window will be added as the last line of the sales document with a quantity of 1 and a unit price equal to the min order fee from the setup window. All other fields will duplicate the entry of a non-inventory item in standard GP.

If commissions and/or taxes are being calculated for this document, the fee will also be included in this calculation.

If the Subtotal is greater than the threshold amount AND the minimum order fee is on the document, then the enhancement will check if the subtotal minus the fee is still greater than the threshold. If it is then the user will be notified: This order does not require the minimum order fee. Do you want it removed? If the user answers YES then the enhancement will remove the line and recalculate the document.

Assumptions/Requirements:

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
  2. The functionality described above is intended for the GP Desktop client.
  3. National Accounts functionality is NOT used.
  4. Advanced Distribution functionality is NOT used.
  5. Unless otherwise noted in this document, reporting is not included in this estimate.
  6. Unless otherwise noted in this document, Word Template functionality is not addressed.
  7. Unless otherwise noted in this document, the enhancement will not integrate with 3rd party products. Some examples of 3rd party products would be:
  • An ISV plug-in product including WilloWare products
  • A dexterity customization designed by another developer
  • Dynamics GP Modules including, but not limited to:
  • Project Accounting
  • MDA
  • Analytical Accounting
  • Copy functionality found in SOP, POP and Inventory
  • Field Service
  • Extended Pricing
  • Manufacturing

For information on this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

 

 

Customization DS0927 Prevent Duplicate Lot Numbers

Customization DS0927

Prevent Duplicate Lot Numbers

Problem Definition:

ACME makes stents for cardiac surgery. When they receive a shipment of a product, all units received will be assigned to one lot number. ACME needs controls added to GP to prevent using a duplicate Lot Number when they receive additional shipments of the same product.

Design Features:

Purchasing Lot Number Entry Controls

Navigation: Receivings Transaction Entry >>Select a Lot Controlled Item>> Qty Shipped Expansion Arrow

Or:

Automatically opens when Auto-Receiving a Lot Controlled Item

A screenshot of a computer Description automatically generated

Controls will be added to this window so that when the user attempts to insert an entered Lot Number into the window on the right side of the screen, the system will first check to see if the Lot Number is found on an existing receipt (posted or open) for the displayed item. If found, the user will be warned of the condition and the Lot Number will not be inserted.

Assumptions/Requirements:

The customization will not validate any other transaction type that increases inventory, such as positive inventory adjustments.

The customization will only scan other purchasing receipts for the same item number when validating if the lot is a duplicate.

For information on this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

 

MFG PowerPack 2025-01-15

Release Date: 15-JAN-2025
GP Versions: 12/14/16/18
MFG PowerPack Build: 15.252
* Serial Number Mass Entry: (1) added PASTE button. This new paste routine can handle over 1 million serial numbers. Copying from a source and using the PASTE button is about 4x faster than importing from Excel.  (2) redesigned window to focus on PASTE button rather than paste-to-textbox.

CompleteCount 2024-12-30

Release Date: 30-DEC-2024
GP Versions: 12/14/16/18
CompleteCount Build: 5.64
* Updates for GP18.7
* Submit Tags: fixed an issue with serial/lot numbers where the variance quantity calculations would be incorrect if the total quantity was correct but mix of serial/lots changes (i.e. for the came item, add SN1 remove SN2, or add +1 LotA and remove -1 LotB.)
* Mass Add: Item Inactive flag, Site Quantity and Bin Quantity are now available as selection criteria when adding item-site/bin records to a Stock Count (i.e. only add bins that have inventory).
* Build Stock Count: this new window replaces CompleteCount’s use of the GP Stock Count Schedule window. Build Stock Count is significantly faster than the GP Stock Count Schedule and has additional features for working with a Stock Count. Do not use the GP Stock Count Schedule window when CompleteCount is installed.
* Post Stock Count: this new window replaces CompleteCount’s use of the GP Stock Count Entry window. Post Stock Count is significantly faster than the GP Stock Count Entry window and has additional features for working with a Stock Count. It brings Reason Codes and Distribution Accounts to the front so they are easier to enter/edit. Do not use the GP Stock Count Entry window when CompleteCount is installed.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.

 

LeanMFG 2024-12-17

Release Date: 17-DEC-2024
GP Versions: 12/14/16/18
LeanMFG Build: 5.68
* MO Doc Types: Added several new options:(1) MPP Add item: Combine same component quantities, (2) Order Date: Set to User Date when created, (3) Order Date: Lock Field, (4) Document Date: Set to User Date when posting, (5) Document Date: Lock Field, (6) GL Post Date: Set to User Date when posting, (7) GL Post Date: Lock Field

MOGenerator 2024-12-12

Release Date:12-DEC-2024
GP Versions: 12/14/16/18
MOGenerator Build: 11.144
* MOGenV2: changed datatype of RescheduleMO from boolean to integer. This field now supports three inputs: 0 = do not reschedule, 1 = rebuild working routing and reschedule, 2 = reschedule without rebuild
* FULL PROCESS INSTALLATION REQUIRED: The installation routine alters the W7158MOGen2 table to change the RescheduleMO datatype from tinyint (GP boolean) to smallint (GP integer).

GPPowerPack 2024-12-05

Release Date: 5-DEC-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 9.185
* Shortage Inquiry: addressed errors caused by user closing the window while it was attempting to display results (#202401663)
* FAST Sales Serial Entry: addressed issue where the “sort by” set to “serial number” would cause the “Available Serials” selection criteria to not alter the list of available serials or the Auto-Select routine. Available Serials restrictions and Auto-Select worked fine when “sort by” was set to “Date Received” (#202401662)

MFGPowerPack 2024-12-04

Release Date: 4-DEC-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 15.250
* Vendor Pricing: addressed the following issue-a PO is released for 10, then 8 are recevied and no more will be received, instead of cancelling the remaining 2 on the PO the user changes the QTY Ordered from 10 to 8. This caused Vendor Pricing to flip the Unit Cost to zero, which then resulted in an error loop from GP that the Unit Cost could not be changed. Vendor Pricing will now be inactive for a PO Line once any quantity has been received (#202401655).

GPPowerPack 2024-12-01

Release Date: 2-DEC-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 9.184
* NEW TWEAKS: (1) TWK-SOP: Email Editable In History, (2) TWK-RM: Email Editable In History, (3) TWK-POP: Email Editable In History. All three enable editing in the Email Detail Entry window when resending historical documents. This allows manually changing email addresses and refreshing them by pulling the defaults from the Customer or Vendor Setup.

MFGPowerPack 2024-11-25

Release Date: 25-NOV-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 15.249
* NEW: WW MFG Lead Times Utility: this utility replaces the GP Manufacturing Lead Times window. It runs significantly faster than the core GP Lead Times utility. It also adds reporting of which Item-Site lead times were updated, creates a historical before/after snapshot, has the ability to update specific Item-Sites separately based on Site-Specific Routings, and has Lead Time Batch that stores a list of Item-Site-Routing so you can easily run updates on subsets of records. It also addresses a couple of bugs present in the core GP utility.

Run the utility for one item, all items, or a Batch.

A screenshot of a computer Description automatically generated

The Lead Time Batch contains a list of Item-Site-Routing Name.  The utility performs Item-Site specific lead time calculations using the Routing assigned for each Site.

A screenshot of a computer Description automatically generated

MFG PowerPack Lead Time Utility

Price $1800 Manual

The Lead Times Utility calculates the Manufacturing Fixed and Variable Lead Times shown on the Item Resource Planning window. The WilloWare utility has several important improvements over the similar utility provided in the Manufacturing Module:

  • It is significantly faster because it only updates Item-Site records where the lead times have changed (the MFG utility updates all records even if there is no change). Also, the WilloWare utility runs completely in SQL while the MFG utility primarily is dexterity.
  • It supports assigning a Routing to each Item-Site record which it uses to perform Item-Site specific updates (the MFG utility updates all Item-Sites to the same value using the Primary Routing).
  • It generates a report after the utility runs shows the before and after values on the records it updated (the MFG utility provides no feedback).
  • It tracks all changes (before and after values) in a history table along with the Date and User (the MFG utility just performs the mass update).
  • It correctly handles Quantity Next Start and Parallel Sequences (the MFG utility has bugs in how it handles routings that use either or both of those features).

A screenshot of a computer Description automatically generated

The Lead Times Utility can update one item, all items, or specific item-sites using a Lead Time Batch.

A screenshot of a computer Description automatically generated

Calculate Manufacturing Lead Times

19-NOV-2024

Keywords: Mfg Fixed Lead Time, Mfg Variable Lead Time

Some quick facts:

  • It looks at the Primary Routing for each made item.
  • It does not explode the BOM and calculate the TOTAL lead time to make a top-level item as-if all of the subassemblies need to be made.
  • It updates the two lead times fields on each Item-Site where the replenishment method is NOT “buy”.
  • When calculating all items it uses the Item Engineering table.  If an item is not in the table it will not be updated.

To see the total lead time to make an item, look at WilloWare’s Lead Time Inquiry in MFG PowerPack. Lead Time Inquiry calculates the total time needed to make an item and can include (or not) usage of available inventory of both make and buy items.  If available inventory is excluded the lead time includes purchasing all buy items in the assembly and making all subassemblies.

The calculation performed by the Manufacturing Lead Times window is provided below.  The first few sections describe where the data is coming from, the calculations are at the end.

ITEM ENGINEERING: Average Quantity.  If the field has a value other than zero it uses that value, otherwise it uses 1.  If you calculate all items the utility runs through all records in the Item Engineering table, which means if you have incomplete setup (i.e a missing record in Item Engineering) the item will not be updated by the utility.

AvgQty = Average Quantity

ROUTING: It gets the routing sequences for the item’s Primary Routing.  For clarity we are leaving out information about how it handles parallel routing sequences, suffice to say the calculations below are applied (see note at the end about parallel routing sequences).

QNS = Qty Next Start

PNS = Percent Next Start

QT = Queue Time

ST = Setup Time

CT = Cycle Time

MT = Move Time

WORK CENTER: It gets the Work Center record using the Work Center ID and the first record with an Effective Date <= User Date.  Note that the User Date can be set to a date that is not the current date and that could cause the lead times to be updated using previous Work Center setup.

HPS = Hours Per Shift

NS = Number of Shifts

THE CALCULATIONS

PctComplete = 1

IF: QNS > 0 THEN PctComplete = PNS/AVGQty

ELSE IF: PNS > 0 and PNS < 1000.0 THEN PctComplete = PNS/1000.0

* Dividing by 1000 is correct, it has to do with how GP stores the data

If QNS and PNS are zero, PctComplete stays 1. PctComplete is used later in the calculations below.  NOTE: the calculation when QNS > 0 is incorrect, this is a bug.  It should be:

IF: QNS > 0 THEN PctComplete = QNS/AVGQty

ELSE IF: PNS > 0 and PNS < 1000.0 THEN PctComplete = PNS/1000.0

As it is, if you use Quantity Next Start the PctComplete value will always be zero, and the Variable Lead Time calculation will always result in zero.  We have fixed this in MFG PowerPack’s Lead Time Utility.

WCHours = HPS * NS

SetupAndQueue = (QT + ST) / WCHours

MoveAndCycle = (CT + MT) / WCHours

VARLeadTimeLine = MoveAndCycle * PctComplete

FixedLeadTime = FixedLeadTime + SetupAndQueue, rounded to 2 decimals

VariableLeadTime = VariableLeadTime + VarLeadTimeLine, rounded to 4 decimals

The calculations above are repeated for each routing sequence and the last two values (FixedLeadTime and VariableLeadTime) accumulate the total as each routing sequence is processed.  These values are used to update the two lead time fields in Item Quantities Maintenance.  All Item-Site combinations where the Replenishment Method is not BUY will be updated.  This means you cannot have Site-Specific Lead Times.

Note the rounding could cause a slightly smaller lead time, which could impact planning.  This is not technically a bug, but it would be preferable if it always rounded UP so that you would allow more time in the schedule rather than less.

Parallel Routing Sequences: the Calculate Manufacturing Lead Times window does not correctly handle routings with parallel sequences.  When the routine looks for parallel sequences it does so only by the Routing Sequence Number, so it retrieves all routing sequences from all routings that have a sequence running parallel to, for example, sequence 100. If you use parallel routing sequences on SOME but not ALL routings, this will cause the routings without parallel sequences to have incorrect lead times. (zeros). 

WilloWare has just release our own Lead Time Utility that not only addresses the two bugs described above, but also offers important key improvements:

  • It is significantly faster because it runs completely in SQL and only updates items if there are changes
  • It provides a report at the end of the process showing which items changes along with the before and after values
  • It has a lead time history table where it tracks the date of each change, the user who made the change, and the before/after values with each change.

 

 

 

LeanMFG 2024-11-12

Release Date: 12-NOV-2024
GP Versions: 12/14/16/18
LeanMFG Build: 5.67
* MO Entry: (1) Added additional ways to access BOM Notes: MO Header section of the window, Outputs scroll, Outputs scroll. The Item Number Zoom in these locations is now a droplist that provides access to Item Maintenance and BOM Maintenance. (2) BOM Zoom will now try to open BOM Maintenace first, if the user does not have access it will try BOM Inquiry.
* MO Doc Types: There is a new Option called “Copy BOM Note to MO Note”. By default this will be false for existing and new MO Doc Types. Enabling this option will cause the BOM Note to copy to the MO Note when creating a new MO. This happens after selecting or changing the BOMID.
* BOM Maintenance: (1) BOM Copy-Item Description field is now disabled. (2) BOM Copy: Fixed issue with Item Description during copy where it was brining over the Item Description from the Item on the copied BOM. (3) BOM Export now exports Multi-Product BOMs.
* BOM Inquiry: (1) BOM Export now exports Multi-Product BOMs.
* Lot Entry: Lot Attributes can now be entered/edited directly in the scrolling window where new Lot Numbers are added. The window now has Show Detail and Show Summary button on the top-right corner of the scrolling window. Click Show Detail (Expand Window) to enter attributes.
* Updates for GP18.7
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.

The MO Entry window now has multiple places where BOM Maintenance can be accessed.  In all of these locations the Item Number Zoom is now a droplist with options to access Item Maintenance or BOM Maintenance.

There is a new MO Document Type Option called “Copy BOM Note to MO Note”.  When this is enable creating a new MO or changing the BOMID will copy the BOM Note to the MO Note.

Lot Attributes can now be entered/edited in the same scrolling window where you add the Lot Numbers.  You no longer need to open the Lot Attribute Entry window.

MFG Data Archive 2024-11-05

Release: 5-NOV-2024
GP Versions: 12/14/16/18
MFGDA Build: 3.35
* NEW: Archive Inquiry: view archived manufacturing documents from the live company
* NEW: Serial/Lot Trace window integration to the Archive. Inquiries in this window will now pull into the display and related manufacturing documents from the Archive Database. Archived documents will be shown with an asterisk, such as MO001234*
* Updates for GP18.7
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.

The new Archive Inquiry window provides a Smartlist-like user interface for searching data in the Archive while inside the live company.

The new integration into the Serial/Lot Trace Inquiry window pulls data from the Archive database into the inquiry making it easier to quickly locate source documents when performing a serial/lot trace.

 

MOGenerator 2024-11-04

Release Date:4-NOV-2024
GP Versions: 12/14/16/18
MOGenerator Build: 10.143
* MO Query window now saves each user’s last used “Validate Query For” setting.
* Excel Imports – addressed issue that could cause invalid dates when attempting to read a cell with certain formatting
* Core Utilties (MOGenv2): Added new table to support adding “pre-entered” serial/lot numbers to a manufacturing order.
* Updates for GP18.7
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.

MFGPowerPack 2024-10-29

Release Date: 29-OCT-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 14.248
* Serial Number Mass Entry: made the window wider to work better with Action Pane menus
* Updates for GP18.7
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.

GP18.7 Updates Starting Today

Date: 28-OCT-2024

We are starting on the 18.7 updates to our software!  You will see new releases of everything over the next few weeks.  They will be released every few days in the following order:

  • GP PowerPack
  • MFG PowerPack
  • MO Generator
  • MFG Import
  • MFG Data Archive
  • Blanket PO
  • LeanMFG
  • SpellCheck
  • Complete Count
  • Consulting Toolkit
  • Engineer To Order (ETO)
  • EZImport
  • Item Process Tracking
  • LabelLink
  • SOP-POP MultiLink
  • Preactor Integration

Nearly 25% of our customers are on a Dynamics GP version below GP2018(18).  We are currently doing all of our “base” development on GP2013, then upgrading and testing across all versions above that.  If you are current on Annual Enhancement you have access to all new features and fixes on any version of Dynamics GP from GP2013 and up!

If you are not regularly updating your WilloWare products you are missing out!  We regularly add new features, and we love incorporating your feedback into our products.  Be sure to let us know what you would love to see in our products and in GP.  Our 18.7 releases are not just for people on GP18.6, they are for YOU.

Dynamics GP Support

Date: 28-OCT-2024

You have likely heard recently about one or more of the following:

  • GP Lifecycle
  • Dynamics GP Roadmap
  • Microsoft Support
  • Timelines
  • Or even the scary and completely wrong “end of life”.

If you own your license, GP will keep running for as long as you want it to.  Here are some statistics from our customer list–the version and the percent of our customers on that version.

  • 10% – GP2016
  • 7% – GP2015
  • 4% – GP2013
  • 1% – GP2010
  • 1% – GP10

This means that 23% of our customers are on a version of Dynamics GP below GP2018/18.x!

We provide support to ALL of our customers regardless of the GP version and we will continue to do so.  Does it matter if Microsoft provides “support” for the version of GP you are running?   According to a significant portion of our customers the answer appears to be no.

 

 

GPPowerPack 2024-10-24

Release Date: 24-OCT-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.182
* Kit Transactions: the routine that adds the kit components to the transaction was not checking the Item Type so it was attempting to add non-inventory items (Misc Change, Flat Fee, Service) to the transaction. These will now be exluded and added to an error log report. They will not prevent the rest of the kit components from being added to the transaction. (#202401424)

MFGPowerPack 2024-10-17

Release Date: 17-OCT-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.246
* Post Data Collection Journal Entries: extended the Tweak to support Journal Entries created by Automated Data Collection. The ADC transactions can be coming from the ADC window or integrated into SF010500 (ADC_Input_Records). The posting journals will not print, there will be no print dialog pop-up.

MFGPowerPack 2024-10-16

Release Date: 16-OCT-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.245
* Item Class Serial/Lot Mask: (1) Changed the SN/Lot rolldown process to include a check that the rolldown hit all items in the item class and if not re-execute the rolldown until it can confirm complete rolldown. This change is to address a report of a sporadic “roll back” in the serial numbering sequence (#202401317), (2) Added check when saving an Item from Item Maintenance if the Class Ser/Lot has incremented (a couldn’t update the item because it was open in Item Maintenace) apply the new Last Generated Ser/Lot to the item.

 

 

We still have clients using GP2010!

That is the headline because if you hear that “support is ending for GP” just consider for a moment that WilloWare still has businesses using GP2010, which is incredibly out of the support window.  It still runs, it supports their business, and it does not shut off.

Fortunately, if you own the license, the software just keeps working.  These customers all have GP Partners who are committed to supporting them and helping them, and ISVs (like WilloWare) who stand by their products.

One more anecdote: A friend of mine is in IT management for a very large national insurance company.  He recently told me they use an IBM Mainframe application that is at least 40 years old.  They have developers who can make changes to it to address new areas of business, such as coverage options for Uber and Lyft drivers.  Since the software does what they need the enormous cost to replace it would not result in a benefit to the organization.

I’m sharing these stories with you so that when you consider the Dynamics GP Lifecycle, one thing you can be sure of is that it will keep running for many years to come, and long past Microsoft’s end of support.

–Brenner

Run IV Reconcile 5x Faster

Date: 2-OCT-2024

Keywords: Reconcile Inventory Quantities, Speed

If you have a lot of Item Numbers and/or Location Codes it creates an enormous number of Item-Site combinations, all of which combine to give the Inventory Reconcile process a lot to do!  Running Inventory Reconcile may take many tens of hours.  It may take days.  Perhaps it takes so long that you only run it over holidays.

There is a relatively simply way to make it run 5x faster.  In true social media style, this is definitely a “hack”.  While we have tested this and it does work, you may have other modules installed in your system or other unique characteristics that could cause this trick to not work.  Please be sure to trial it in a test company before running it on your live data.

When you click the PROCESS button on Reconcile Inventory Quantities the Inventory Reconcile routine adds an activity record in DYNAMICS..SY00800.  If you have Manufacturing installed it also adds “locks” in the company database MOP10223.  If you attempt to start another IV Reconcile process from a second GP client it is these activity records which prevent it.

How do you make IV Reconcile run 5x faster?  Run it simultaneously on five GP clients!

Divide and conquer.  Figure out how to divide your inventory into equal sized groups, such as A-K and L-Z (this would not actually work because it would miss everything after “K” such as “KA”, but you get the idea).  Technically A-K and K-Z would only overlap on a single Item Number “K”.

Log into the first GP and start IV Reconcile on the first range of items.  Then delete the Reconcile record from SY00800 and everything from MOP10223.  Note that MOP10223 holds MO locks for other parts of Manufacturing, such as MO Entry, so clearing this table should only done when you know that users are not going to be working in Manufacturing.

Now start IV Reconcile on a second GP client.  Clear the tables again if you are going to start a third processor.  This process can be repeated as many times as you like.  Do NOT delete the records after starting the last processor.

Most of the “work” of the reconcile process is performed within the GP client so this procedure splits the workload allowing you to run IV Reconcile more quickly on a given range of items, or to get through more items in the same amount of time.

 

 

Customization CR1508: MFG Allocation Settings

Customization CR1508

MFG Allocation Settings

Description of Need:

ACME has GP Manufacturing set to allocate the picklist when the MO Status is changed to Released. Due to the length of the manufacturing process, they would like to have control over which items on a picklist are automatically allocated, leaving the rest to be manually allocated/issued at a later date.

Description of Solution:

Navigation: From BOM Maintenance, go to Additional>>Allocation Settings, or, CARDS>> Manufacturing>> BOM Allocation Settings

A screenshot of a computer Description automatically generated

NOTE: When the BOM Allocations Settings code is installed, no inventory will be automatically allocated until allocation settings are established.

When opened from BOM Maintenance, the BOM Allocation Settings will display the BOM shown in the BOM Maintenance window. Individual components can be marked to Auto-Allocate by marking the checkbox next to the component. Click the Mark All button to mark all components, and the Unmark All button to unmark all components.

NOTE: The window does NOT display subassemblies. It shows ONLY the first level components. Phantom Subassembly allocation settings must be set on the Phantom BOM. You cannot have different settings for a Phantom BOM used in one parent item versus another parent. Phantom BOM component allocation settings are linked to the Phantom BOM and will be the same in every parent that uses the Phantom.

Assumptions/Requirements:

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
  2. The functionality described above is intended for the GP Desktop client.
  3. National Accounts functionality is NOT used.
  4. Advanced Distribution functionality is NOT used.
  5. Unless otherwise noted in this document, reporting is not included in this estimate.
  6. Unless otherwise noted in this document, Word Template functionality is not addressed.
  7. Unless otherwise noted in this document, the enhancement will not integrate with 3rd party products. Some examples of 3rd party products would be:
  • An ISV plug-in product including WilloWare products
  • A dexterity customization designed by another developer
  • Dynamics GP Modules including, but not limited to:
  • Project Accounting
  • MDA
  • Analytical Accounting
  • Copy functionality found in SOP, POP and Inventory
  • Field Service
  • Extended Pricing
  • Manufacturing

For information on this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

 

Customization CR1107: Retainage Tracking

Customization CR1107

Retainage Tracking

Description of Need:

ACME needs to track and report on Retainage applied to certain Accounts Receivable documents.

Description of Solution:

Navigation: Transactions>>Sales>>Retainage

A screenshot of a computer Description automatically generated

Customer Number: Enter a Customer Number or select one from the Lookup.

The scrolling window will display all Invoices in the Receivables Open Table (RM20101).

Retainage is the only editable field. The user can enter/change the Retainage amount as needed.

B.A.R. = Balance After Retainage. Displays the Current Amount – Retainage.

For information on this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/