Author: admin

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/

 

Customization CR1292: Lock Site ID for New PO Req Entry

Customization CR1292

Lock Site ID for New PO Req Entry

Description of Need:

ACME would like to lock the Cost Center field from being changed AFTER the first line has been entered.

Description of Solution:

The enhancement will require ACME to have the Requisition Setup option for Requisition Line Site ID set to “Previous Line’s Site ID.”

A screenshot of a computer Description automatically generated

After the user enters the first line on a PO Requisition, additional lines will be prepopulated with the previous Cost Center (default behavior). If the enhancement sees a defaulted Site ID, it locks the field and its lookup when the focus is placed in the scrolling line. This will not only prevent the user from changing the Site ID on additional lines, but will also prevent the user from changing the Site ID on the first line after the focus has been tabbed out of the line and onto the next.

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. Unless otherwise noted in this document, reporting is not included in this estimate.
  3. Unless otherwise noted in this document, the enhancement will not integrate with 3rd party products. Some examples of 3rd party products would be:
  • An ISV plug-in product including WilloWare products
  • A dexterity customization designed by another developer
  • Dynamics GP Modules including, but not limited to:
  • Project Accounting
  • Analytical Accounting
  • Copy functionality found in SOP, POP and Inventory

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

www.willoware.com/contact-me/

 

MOGenerator 2024-09-18

Release Date:18-SEP-2024
GP Versions: 12/14/16/18
MOGenerator Build: 6.139
* MCTE Integration: New processing routine. (1) It now uses a sql routine to select the next MO to process so it only grabs an MO that can be processed (i.e. the MO isn’t locked, the BOM isn’t locked) rather than taking the next record from wMCTEHdr and then checking if it can be processed. (2) Previously the processing routine would attempt to process all records in wMCTEHdr, which for issue/rev issue would create a backup in the Process Monitor of IV transactions that need to be posted, which eventually could cause GP to lock-up when attempting to process hundreds of records. Processing Issue/Rev Issue now occurs in a daisy-chain where the posting of one IV transaction initiates the next MCTE process to integrate the next Issue/Rev Issue. When all records are processed the MOGen Timer will wait for new records in wMCTEHdr then kick-off the next attempt to process records. Processing Allocation/Rev Allocation has not changed because those do not need to post, so the MCTE processor will go through all such records in wMCTEHdr before shutting down, then the MOGen Timer will start it up again when new records are present.
* Excel Imports: changed method used to read a cell from Excel to ensure that the value only is retrieved from the cell in a manner that is not affected by the presence of a formula or cell formatting.

MFG PowerPack 2024-09-17

Release Date: 17-SEP-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.244
* Quick Disassembly: Fixed issue with Disassembly From BOM routine that could cause and incorrect U of M to be used even though the quantity adjusted is correct (#202401234)

LeanMFG 2024-09-16

Release Date: 16-SEP-2024
GP Versions: 12/14/16/18
LeanMFG Build: 4.65
* Disassembly Wizard: the windows now remembers the last used “Disassemble” option per user and displays that selection the next time the window is opened.
* MO Entry: changed a check performed on the GoTo button that required sites so that it is only applied to the GoTo options that require a complete MO Header.

MFGDataArchive 2024-09-16

Release: 16-SEP-2024
GP Versions: 12/14/16/18
MFGDA Build: 1.33
* Added pre-archive check to confirm table triggers have been removed from the archive database (#202401118)
* MDA History: fixed issue in Data Column display that resulted in no calculation for net change, made change fields bold, made line between tables thicker to improve visual separation

MFG PowerPack 2024-09-11

Release Date: 10-SEP-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.243
* Vendor Pricing: Fixed issue with SOP-POP Preview window where attempting to use the Organize button, or closing the window without creating a PO, would result in an error (#202401114: Illegal address for field ‘Item Number’ in script wSOPPOPreview_RequiredDate_ACHG2)

Customization CR1327: Fuel Surcharge

Customization CR1327

Fuel Surcharge

Description of Need:

ACME needs to apply a fuel surcharge to sales orders and invoices. This fuel surcharge will be a percentage of the sales subtotal.

Description of Solution:

Navigation: Tools>>Setup>>Sales>>Surcharge Setup

Graphical user interface, application Description automatically generated

Field Function
Fuel Surcharge Enter the fuel surcharge that will be used as a percent

Customer Maintenance

The Customer Maintenance window will be updated as follows:

Graphical user interface, application, table Description automatically generated

Field Function
Fuel Surcharge This is an existing User Defined 1 Field. ACME will use the Receivables Setup window to relabel it. The enhancement will read the number entered here as the fuel surcharge percent as entered.

To charge 6%, the user must enter 6, not 0.06
Checkbox This will be a virtual checkbox, meaning the window itself will not be modified. The custom fuel surcharge will only be applied if this checkbox is marked, otherwise it will default to the value in setup. If this box is marked, but no value is entered into Fuel Surcharge, the default amount will be used.

Sales Transaction Entry

The Sales Transaction Entry window will be updated as follows:

A picture containing graphical user interface Description automatically generated

Field Function
RECALC This will be a virtual button, meaning the window itself will not be modified.

Clicking the RECALC button will recalculate the fuel surcharge using the logic detailed below. After the Fuel Surcharge field is updated, the Tax and Totals fields will also be updated.
Fuel Surcharge The Miscellaneous field will be relabeled to Fuel Surcharge.

As items are added to a Sales Order or Sales Invoice, the fuel surcharge will automatically recalculate each time the Subtotal is changed.

The Fuel Surcharge is calculated using the following formula:

Surcharge = Subtotal * % from either Customer Card or Setup, as indicated above.

NOTE: If the customer maintenance setting for using a custom fuel surcharge changes at any time during the life cycle of the order, the next time the Fuel Surcharge logic is applied it will use the new settings.

The Fuel Surcharge can also be applied/ updated by clicking the new RECALC button added to the Sales Transaction Entry window.

The user can manually override the fuel surcharge by entering a new value. If a value is manually entered, adding additional items or clicking the RECALC button will override it if clicked again.

If the user needs to exclude the document from being charged a fuel surcharge, an Additionals menu option will be added to Sales Transaction Entry. Click Additionals >> Exclude Fuel Surcharge.

When Exclude Toggle Fuel Surcharge is selected, the Fuel Surcharge field will be cleared and disabled. No fuel surcharge can be added to the document.

To Re-enable the use of Fuel Surcharges on that document, click the Additionals >> Exclude Fuel Surcharge option again. This will bring the document back to the state where a fuel surcharge can be calculated once more.

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 2024-09-05

Release Date: 4-SEP-2024
GP Versions: 12/14/16/18
LeanMFG Build: 4.64
* MO Entry: (1) Added a posting routine check to ensure no Input Item has an Inventory Account the same as the WIP Account. (2) When adding an Input Item a new check will ensure the Item’s INV Account is not the same as the MO Doc Type’s WIP Acct. (3) The build picklist routine validates that no Inputs have INV Account the same as the WIP Account. (4) Added check when retrieving a document to search for posted input transactions that are not linked to the MO because posting failed, and re-link them. (5) Changed ClearPostingFlag so it also closes the w-memory form to address scenario where the Costed MO Report would attempt to print if a user immediately creates and posts an inventory adjustment after posting an MO Receipt. (6) Added check before posting Outputs that validates unit and extended cost are not negative to address a scenario where a posting failure/GP crash resulted in corrupt Input transactions that caused a negative unit cost to be calculated for the output
* Cost Allocation Percent: Changed datatype to not allow negative values
* MO Distributions: (1) Fixed issue that prevented the window from saving new accounts. (2) Distribution now window validates that INV Account and WIP/Offset Account are not the same.

Customization DS1262: Discontinued Inventory

Customization DS1262

Discontinued Inventory

Problem Definition:

ACME uses Dynamics GP. When they discontinue an item, they need to ensure they sell the remaining inventory of the item before transitioning to its replacement, and they need to ensure the replacement item is purchased rather than the discontinued item.

GP supports some of this process, but other aspects of ACME’s requirements cannot be met with standard GP functionality.

  • ACME will list one or more replacements for a discontinued item using the Manufacturing Module’s “Alternate Items” window.

A screenshot of a computer Description automatically generated

  • Items can be marked as Inactive and/or Discontinued

A screenshot of a computer Description automatically generated

  • When a user changes an Item to be Discontinued on Item Maintenance, ACME would like the user to be prompted: Sell remaining inventory? YES/NO. If the user answers YES the Item Engineering “Use Up Part” checkbox will be marked automatically. ACME can mark/unmark the “Use Up Part” checkbox manually as needed.

A screenshot of a computer Description automatically generated

  • Purchase Order Entry will alert the user that the Item is Inactive and cannot be purchased. It will also prevent purchasing a Discontinued item. ACME requires that if an Inactive or Discontinued Item is entered on a Purchase Order, in addition to being alerted about the status of the item (Inactive/Discontinued) the user needs to be shown the replacement item(s) for the discontinued/inactive Item.

A screenshot of a computer error Description automatically generated

A screenshot of a computer error message Description automatically generated

  • Sales Order Entry will allow selling Discontinued items. It will not allow selling Inactive items. ACME requires that Sales Order Entry ONLY allow selling Discontinued Items if the Use Up Part checkbox is marked.

A screenshot of a computer error Description automatically generated

  • ACME requires that when the remaining inventory of a Discontinued Item is sold, the Item should automatically be marked as Inactive. This will prevent any more sales of the item.
  • In Sales Order Processing, if a Discontinued Item is sold for which there is not enough inventory to meet the Customer’s order quantity, the Shortage Quantity Options window should only allow “Sell Balance”. The user should be alerted that the Item is Discontinued and shown the available replacement items.

Design Features:

Item Maintenance

A screenshot of a computer Description automatically generated

When a user changes the Item Type to DISCONTINUED, they will be prompted:

Sell remaining inventory? YES/NO

If the user answers YES, the “Use Up Part” checkbox on Item Engineering will be marked.

Purchase Order Processing

The messages normally presented by the PO Entry window for discontinued/inactive items will be suppressed and instead the user will see the new Alternate Items window:

 

A screenshot of a computer Description automatically generated

The discontinued/inactive Item will be shown at the top. One or more Alternate Items will be shown in the scrolling window at the bottom. This window will function like a “lookup” window, so that the user can double-click on one of the rows to use that Item Number on the Purchase Order.

Sales Order Processing

If an Item is Discontinued and “Use Up Part” is marked, and there is a quantity shortage, the Sales Quantity Shortage Options window will show only “Sell Balance.”

A screenshot of a computer Description automatically generated

The Alternate Items window (below) will also open automatically and position itself to the right-side of the Shortage Options window. The window has a couple of modes, and the mode below is Display Only. The user will continue, clicking OK on the Shortage Options window to sell the balance. The Alternate Items window will close automatically.

A screenshot of a computer Description automatically generated

The user can then open the Alternate Items window in Lookup Mode by pressing CTRL+Z, (or Additional>>Alternate Items.)

A screenshot of a computer Description automatically generated

Enter the Discontinued Item in the Item Number field. The scrolling window at the bottom will display the available alternate items. Double-click on an alternate to select it and use it in the Sales Transaction Entry window.

Assumptions/Requirements

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
  2. The functionality described above is intended for the GP Desktop client.
  3. Unless otherwise noted in this document, Word Template functionality is not addressed.
  4. The enhancement may not work with Rockton SmartFill.

For information about this design, or any other WilloWare customization or product, please

Contact us:

www.willoware.com/contact-me/

 

Customization CR1348: Kit Window Security

Customization CR1348

Kit Window Security

Description of Need:

ACME uses Inventory Kits. In addition to users who create/edit/maintain the Kit setup, there are other users who need to view the Kits. Since Dynamics GP does not have a Kit Inquiry window, these “view only” users must access the Kit Maintenance window.

ACME would like a way to “lock down” the window for “view only” users.

Description of Solution:

NOTE: a report, and using SmartList, were also considered, but ACME felt those options did not provide the same usability as a Kit Inquiry window. The approach described below, “locking down” the Kit Maintenance window, is significantly less costly than creating a new Kit Inquiry window.

Navigation: Tools>>Setup>>Inventory>>Kit Security

Table Description automatically generated

Once the customization is installed it will immediately apply security to the Kit Maintenance window. Users who have not been granted Full Access in the Kit Security Setup window will have READ ONLY access to the Kit Maintenance window (i.e. Kit Maintenance will behave as-if it is an Inquiry window). Users with Full Access will be able to use the Kit Maintenance window normally (i.e. create new kits, change components, delete kits, etc).

Field Function
User ID Enter a User ID, or select one from the lookup

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/

 

CompleteCount 2024-09-03

Release Date: 3-SEP-2024
GP Versions: 12/14/16/18
CompleteCount Build: 4.63
* Excel Link: fixed issue with exporting to multiple sheets that caused a file error from Excel.
* Added prompt to the GP Stock Count Schedule window to ask users to try the CC Stock Count Schedule window.

LeanMFG 2024-08-29

Release Date: 29-AUG-2024
GP Versions: 12/14/16/18
LeanMFG Build: 4.63

* MO Doc Type Setup: Added a new setup option “Site Segment Override: Require Swap Account Exists”.  This is enabled by default so that existing behavior of LeanMFG does not change.  Unmark this option to allow LeanMFG to use the swap account if it exists but the otherwise the default account.

* MO Entry: The window now only requires that the GL account created by Site Segment Swapping exists if the MO Doc Type setup option “Site Segment Override: Require Swap Account Exists” is marked.

Customization DS1497: Revenue Recognition

Customization DS1497

Revenue Recognition

Problem Definition:

ACME creates receivables invoices for estimated profit sharing to accrue the revenue. When the actual profit sharing amount is determined, ACME needs to back out the estimated invoice and enter the actual profit sharing into GP.

ACME needs a regular process to reverse the estimated invoices.

Solution Overview:

ACME integrates receivables documents into GP from an outside application.

The estimated Profit Sharing Document will be entered as a Sales/Invoice document type and the customer will begin with “C*”. This invoice will have all necessary distributions entered.

The matching actual Profit Sharing Document will be entered as a Debit Memo document type. The customer will be the same as the Invoice, and the Description will be set to the document number of the Invoice.

The reversing document will be created by WilloWare as a Return. The document number will be the same as the original invoice, but with the prefix of “R_”. This return will be posted and applied to the Invoice.

Design Features:

PMSF & Local Incentive Distribution Matching

Navigation: Transactions>>Sales>>PMSF Matching

A screenshot of a computer screen Description automatically generated

When this window first opens, the scrolling window will automatically fill with all available debit memos. The documents will be saved until processed so this window can be returned to and the changes will be saved.

Security will be used to ensure that only one user is Profit Share Matching at a time.

Field Function
Debit Memo Displays the debit memo that was entered into Receivables Transaction Entry. This list will display all Debit Memos belonging to customers that begin with “C*”. The Expansion button will open the debit memo in Receivables Transaction Inquiry Zoom
Debit Amount Displays the debit memo document amount
Customer Displays the Customer ID of the Debit Memo
Sales Invoice When the Debit Memo is added to this list, the enhancement will attempt to locate a matching invoice using the following logic:

Document Type = Sales / Invoice

Document Number = DB Description

Customer = Removes the “C*” from the Debit Memo and replaces it with “Z*’

If an invoice can be located, it will be displayed here. If an invoice cannot be located, this field will remain blank. An invoice can be manually located using the lookup button. Only invoices that belong to the “Z*” customer linked to the Debit Memo will be displayed. The Expansion button will open the invoice in Receivables Transaction Inquiry Zoom

Note: If the document selected is already partially applied to a credit, the user will be warned and it cannot be selected. If the invoice needs to be reversed, it should first be unapplied

If the matched invoice already has a return generated, the user will be warned and it cannot be selected. This situation may arise if the debit memo was previously processed but the return and invoice were manually unapplied
Sales Amount Displays the invoice document amount
Customer ID Displays the Customer ID on the accrual invoice
Process Mark this checkbox to add this line to the list of documents that will be reversed. The checkbox can only be marked the Matched Invoice field is not blank
MARK ALL /UNMARK ALL Click to either mark or unmark all rows in the scrolling window
PROCESS Clicking Process will create Returns for all marked lines. The return will have the following properties:

Document Type: RM RETURN

Document Number: “R_”+Matched Invoice Number

Customer ID: Same as Invoice

Batch ID: “REV_”+MMDDYYYY

Document Date: Same as Debit Memo

Sales Amount: Same as Invoice

Distributions: Reverse of Invoice. For Example:

INVOICE:

The line will then be moved from the Matching into a Historical table and will not appear again. The History table can be used in Smartlists for future reference.

After the Returns are created, the Batch will be posted. After posting, the Returns will then automatically be applied to the Invoice:

If an error occurs during posting, the user will be warned of the condition. The user will need to correct any issues and re-post the batch. Any returns that needed to be manually posted will also need to be manually applied.

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 (unless otherwise noted in this document).
  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-Currency is NOT used.
  6. Taxes and Commissions are 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/

 

Customization DS1177: SVC Preventative Maintenance Service Type Swap

Customization DS1177

SVC Preventative Maintenance Service Type Swap

Problem Definition:

ACME is using Dynamics GP Field Service Preventative Maintenance. When generating Service Calls from Preventative Maintenance, they need to change the default Service Type, depending on a couple of rules described below, so that when the Service Call creates a Sales Invoice it uses the desired Sales and Cost of Sales accounts.

The Service Type needs to be changed as follows:

  • If the Equipment Record is assigned to an active Contract, use the Service Type from the Contract. Active means that the current date (not the GP User Date) falls within the Start/End Dates of the contract.
  • If an active Seller or Vendor Warranty is assigned to the Equipment record, use the Service Type assigned to the Warranty. Active means that the current date (not the GP User Date) falls within the Start/End Dates of the contract. An Equipment Record should not have both Seller and Vendor Warranties, however, if that should happen, use the Vendor Warranty.
  • An Equipment Record should not have both an active Contract and Warranty, however, if that should happen, use the Contract.

Design Features:

cid:image002.png@01D4B88C.7BF87640

When the PM Edit List opens, the enhancement will update the Service Type (as shown above) using the rules described in the Problem Definition section. The Service Type shown in this window will then be used to create the Service Call.

Assumptions/Requirements:

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
  2. The functionality described above is intended for the GP Desktop client.
  3. Unless otherwise noted in this document, reporting is not included in this estimate.
  4. Unless otherwise noted in this document, Word Template functionality is not addressed.

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

www.willoware.com/contact-me/

Customization DS1330: Transfer Credits from National Accounts Child to Parent

Customization DS1330

Transfer Credits from National Acct Child to Parent

Problem Definition:

ACME uses the National Accounts functionality in Dynamics GP. The Parent Account gets invoiced for Child orders. However, the Child receives rebates (which are Credit Memos in GP). Currently, to move a credit from the Child level to the Parent, ACME is manually creating a Debit Memo and applying it to the Child account, then creating a new Credit Memo on the Parent Account. This process is time consuming and loses track of where the credits came from.

ACME would like a more automated way to transfer credits from the Child to the Parent in a National Account relationship, and keep track of the rebate history (i.e. so a credit at the Parent level can be traced to the Child from which it was transferred).

ACME does not use Multi-currency.

Solution Overview:

WilloWare will create a Child Credit Transfer window that shows the total amount of unapplied Credit Memos on Child Accounts in a National Accounts relationship. The user will be able to easily transfer all credits from a Child to a Parent from this window. History of the transfer will be retained so that when viewing a credit at the Child or Parent level it will be easy to see where it went (child to parent).

Design Features:

Child Credit Transfer:

Navigation: Transactions>>Sales>>Child Credit Transfer

Table Description automatically generated

Field Function
Transfer Credits See process description below. The Transfer Credits process moves credits from children to the national account parent
Mark All Mark All customers shown in the window
Unmark All Unmark All customers shown in the window

The Child Credit Transfer window shows Customers that are the Child in a National Accounts relationship which have unapplied Credit Memos (partially or completely unapplied). It does not show other sources of credits, such as Sales Returns. The expansion button will open a window showing a Customer’s Credit Memos that have an unapplied amount.

Table Description automatically generated

The Expansion button on the Unapplied Credit Memos window will open the selected document in the Receivables Transaction Inquiry Zoom window:

Table Description automatically generated

For each Credit Memo on a Child Customer, the utility will:

  1. Create a Debit Memo for the unapplied amount (“Current Transaction Amount”)
    1. The Credit Memo Document Number will be put into the Description field of the Debit Memo.

Graphical user interface, table Description automatically generated

b.

  1. Post the Debit Memo
  2. Apply the Debit Memo to the Credit Memo
  3. Create a Credit Memo for the Parent Customer.
    1. The original Child Credit Memo Document Number will be put into the Description field of the Parent Credit Memo.
  4. Post the Credit Memo

NOTE: putting the “source” Credit Memo number into the Description field of the related “credit transfer” documents is intended to provide some linking between the documents so that, if needed, it will be possible to trace a CM on a National Account Parent to the child’s original document. No inquiry window or reporting is provided in this estimate that ties all of the documents together.

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. Advanced Distribution functionality is NOT used.
  4. Unless otherwise noted in this document, reporting is not included in this estimate.
  5. Unless otherwise noted in this document, Word Template functionality is not addressed.
  6. 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/

 

CompleteCount 2024-08-21

Release Date: 21-AUG-2024
GP Versions: 12/14/16/18
CompleteCount Build: 4.62
* Tolerance Management: (1) Added ability to restrict the window by Item Number and/or Location Code. (2) Added the ability to multi-select and range-select so that a large quantity of records can be moved to a new count. This works with Override tolerance and Remove Override.

A screenshot of a computer Description automatically generated

Customization DS1293- MO Receipt Entry- Bin Selector Override

Customization DS1293

MO Receipt Entry – Bin Selection Override

Problem Definition:

ACME uses Dynamics GP Manufacturing. MO Receipts are performed on handhelds using Accellos.

Pertinent configuration:

  • Inventory multi-bin is enabled
  • Inventory is set to allow adjustment overrides. They frequently drive inventory negative.
  • None of the raw material items are serial or lot tracked
  • Manufacturing is NOT set to Allocate on Release
  • None of the Manufacturing “Display….Warning” checkboxes are marked in the MO Receipt and Close Options section of the Manufacturing Order Preference Defaults window.
  • They always backflush all components. Raw materials are never issued.

When attempting to perform an MO Receipt through Accellos, they often run into a situation where there is a shortage of one or more raw materials. This causes the Accellos processor to fail for that MO and it must be processed manually. Several warnings pop-up during this process:

A screenshot of a computer error Description automatically generated

The user must then click into each component shortage, click the expansion button to open the Bin Selection window, enter the Bin and Qty. When the user clicks INSERT, they are prompted:

A screenshot of a computer error message Description automatically generated

Clicking CONTINUE returns the user to the Bin Quantity Entry window but does NOT insert the selected Bin/Qty. The user must hit INSERT again.

ACME would like the MO Receipt Entry window to bypass the bin quantity checks and automatically draw inventory negative, if required, from the Item-Site Default Material Issue Bin (if that Bin has not been specified, use the Site’s Default Material Issue Bin).

Solution:

WilloWare will create an enhancement for the MO Receipt Entry window that automatically creates the MO Receipt component bin quantity records “as if” the user had manually entered them.

This process will run immediately after the MO Number has been entered, and before the POST button is clicked. Because Accellos uses GP Macros to “type” data into the GP User Interface, this can be thought of as a user keying in data. In the time between entering the MO Number and clicking POST, the enhancement will jump in an automatically enter bin-quantity selections for each component on the picklist.

This will allow Accellos to then post the MO without having the bin related dialog boxes pop-up.

There will be no noticeable changes from the user interface that this process is occurring.

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

www.willoware.com/contact-me/

 

Customization CR0971 Consignment Transfer

Customization CR0971

Consignment Transfer

Description of Need:

ACME sells/fulfills inventory out of Consignment Sites. When an Order is entered it allocates inventory in the primary site called ITASKA. When the order ships, they unallocate each line, transfer the inventory to the CONSIGNMENT site, and then change the site on the Order Lines to CONSIGNMENT so that inventory is allocated in consignment.

As inventory is used out of CONSIGNMENT, they post the Invoice, which consumes the inventory out of CONSIGNMENT.

This process is time consuming, and they sometimes run into the situation where inventory is over allocated in ITASKA, so when they unallocated an Order the inventory is still not available to transfer to consignment.

ACME does not use serial or lot numbers, multi-currency, or multi-bin.

ACME would like to automate the process of transferring consignment inventory.

Description of Solution:

WilloWare will add “Consignment Transfer” functionality to the GP Sales Transaction Entry window. It will be initiated when the Default Site ID is changed:

A screenshot of a computer Description automatically generated

When the Site ID on an Order or Invoice is changed (i.e. from WAREHOUSE to SOUTH), and there are lines on the document which allocate inventory out of WAREHOUSE, the user will be asked: “Do you want to transfer inventory to SOUTH?”.

NOTE: WAREHOUSE and SOUTH are examples. The Consignment Transfer will use the Original Site and New Site entered on the window.

If the user answers YES:

  1. The Consignment Transfer enhancement will perform the following checks before attempting to transfer inventory. If any check fails, the user will be warned and the process will abort.
    1. It will check that the Original Site has enough inventory On Hand for each Item on the Order to allow transferring the full order quantity to the New Site. Sales Lines will be skipped (and no warning presented) if…
      1. it has a Quantity Backordered
      2. it does not have inventory allocated in the Original Site
      3. it is for a serial or lot numbered item
      4. it is a Kit Item
      5. it is a non-inventory Item
    2. It will check that the Inventory Fiscal period is open for the current date (GP User Date).
    3. It will check that each Item on the Order, which is not skipped by the checks in #1, is assigned to the New Site.
  2. If the checks all pass:
    1. Inventory will be unallocated from the Original Site
    2. That inventory will be added to an Inventory Transfer moving the inventory from the Original Site to the New Site
    3. The Inventory Transfer will be posted
    4. Site New Site will be rolled-down to each Sales Line that has the Original Site, and re-allocated in the New Site

The process will mimic the manual process. If the Inventory Transfer fails to post for some reason, the user will need to address the posting issue, complete the posting process, then manually change the Site ID on the sales lines and re-allocate inventory.

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

www.willoware.com/contact-me/

 

LeanMFG 2024-08-16

Release Date: 16-AUG-2024
GP Versions: 12/14/16/18
LeanMFG Build: 4.62
* MO Entry: (1) Changed validation for “setup complete” to no longer include Draw From/Post To sites. This allows the BOM and MO Doc Type to not have default sites and the user is required to enter them manually on each MO. (2) Entering a Draw From Site will now auto-populate the Post To if the Post To is empty. (3) Added new checks on the Tabs and GoTo button to require Sites

GPPowerPack 2024-08-13

Release Date: 13-AUG-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.180
* NEW TWEAK: POP-TWK: Forward Only PO Numbering – prevents the Next PO Number in POP Setup from getting set far backwards to an unused PO. For example, if the current Next PO Number is PO2235 but a user types in PO1002 into PO Entry and PO1002 was never used, then the user clicks Delete (does not use the PO Number), it gets “released” and PO Setup takes it as the new Next PO Number. The intent of POP functioning like this was to allow multiple users to create POs without gaps. For example, three users might open PO Entry and get PO Number PO2002, PO2003 and PO2004. If all of them close PO Entry without creating a PO the PO Number would reset to PO2002. However, that behavior also allows a user to type in PO0020 then close the window and the Next PO Number “resets” to PO0020. “PO Number Forward Only” allows setting a value for how far back the numbering can reset, from 0 (no reset allowed) to 999.

Watch a quick video demo here

Customization CR0276 Bank Rec Stop Payments

Customization CR0276

Bank Rec Stop Payments

Description of Need:

ACME needs to track payments for which a Stop Payment has been issued, and the date when it occurred. This is informational only and should have no effects on the normal functioning of Bank Reconciliation.

Description of Solution:

The Select Bank Transactions window will be expanded to the right, so that two additional columns can be added to the scrolling window. The columns are being added to the right-side of the window to minimize the changes to the window so that long-term maintenance is reduced. During upgrades the window changes often need to be re-done on the new version, so keeping changes to a minimum ensures easier upgrades.

A screenshot of a computer Description automatically generated

The new columns will be:

  • Stop Payment checkbox: The column header will be “SP”. When the box is marked, the Date field will default to the User Date.
  • Date: The Stop Payment Date is the date on which the Stop Payment was issued.

When Stop Payment is marked, a record will be stored in a new SQL table (the name will be provided in the product documentation) that stored the Transaction Number and Transaction Type. When Stop Payment is unmarked, the record for that transaction will be removed from the Stop Payments tables. The Stop Payment Date will be stored in the table also.

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

www.willoware.com/contact-me/

 

GPPowerPack 2024-08-02

Release Date: 2-AUG-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.179
* Bank Deposit Filters: fixed an issue that could cause the Advanced Filters to a create set of selection criteria which results in the Mark All routine finding no records to select, which then puts the Mark All routine into an endless loop (#202401046)

LeanMFG 2024-07-24

Release Date: 24-JUL-2024
GP Versions: 12/14/16/18
LeanMFG Build: 4.61
* MO Entry: (1) Removed the “Mfg Order – History” report and replaced it with “Mfg Order – Costed”. It now includes costing information to make it easier to allocate input costs to outputs. When posting, if costs are not fully allocated you will now be asked if you want to print the Mfg Order-Costed report. Additionally, a new MO Doc Type Setup Option has been added to automatically print the Mfg Order-Costed report when posting completes. On the OPTIONS tab, “Print Mfg Order – Costed” by default is set to not print so it does not alter behavior in existing systems. To enable this report go into each MO Doc Type, click OPTIONS, scroll down to “Print Mfg Order – Costed” and mark the checkbox. (2) Add Component now automatically fills in the BOMID if there is a Default BOM ID for the selected Item.

Mass Delete Old Sales Quotes

Keywords: SOP Quote, SOPTYPE = 1,  Mass Delete

If you have accumulated a large number of unused SOP Quotes in Dynamics GP it can be daunting to consider the best way to remove them.  A quick trick to accomplish this is described below.

WilloWare’s GP PowerPack has a module called Mass Batch Change (shown above).  MBC can be used to move transactions from one batch to another for transactions created in the following windows:

  • Sales Transaction Entry
  • Receivables Transaction Entry
  • Receivables Cash Receipts
  • Payables Entry
  • Manual Payments
  • Assembly Transactions
  • Purchasing Invoice Entry
  • Purchasing Receipt Entry

As shown above, to remove Sales Quotes, add record selection criteria where:

  • SOP Type = Quote
  • Document Date <= 7/18/2019 (in this case removing everything more than five years old)

After the window locates the documents, transfer them to a new batch (DELETE_ME).

Then delete the batch.

Customization DS1214- SOP Fulfillment Bin Transfer

Customization DS1214

SOP Fulfillment Bin Transfer

Problem Definition:

ACME uses Panatrack and Dynamics GP with Multi-bins enabled. Panatrack is used to pick inventory for a Sales Order and it updates fulfillment on the Order. During this process inventory is physically moved to a staging area in the warehouse, but in GP the inventory still appears to be allocated in its original Bin.

To improve inventory accuracy, and facilitate accurate cycle counts, ACME would like to have the inventory that is selected by Panatrack to fulfill an Order, moved from the Bin in which it was picked into the generic FULFILL bin (it is called FULFILL). The Inventory and Sales modules should be updated accordingly to accommodate moving the inventory.

ACME has both Serial Tracked and Non-Tracked inventory. Any given sales line may be fulfilled over multiple partial fulfillments.

Solution Overview:

Normally in Dynamics GP when inventory is allocated for a Sales Line out of “Bin-A”, that information is used to record on the Sales Order where the inventory is coming from to fulfill the Sales Line. In other words, when you select inventory out of Bin-A, Dynamics GP records that bin on the Sales Line. In reality, the inventory has been physically picked out of Bin-A and placed in a “staging bin” until the Order is packed and shipped. This makes it difficult to take a physical inventory count because Dynamics GP still thinks the inventory is in Bin-A.

Using Dynamics GP transactions to perform the task of putting inventory into a staging bin would require first transferring all needed inventory from storage bins into a staging bin, THEN picking inventory for SOP fulfillment out of the staging bin.

WilloWare will create a SQL stored procedure that Panatrack can execute AFTER picking inventory from storage bins. The stored procedure will update the Sales Order, and other tables in GP, so that it appears that all the selected inventory has been transferred from storage bins into a single staging bin called FULFILL and that the Sales Order was fulfilled out of the FULFILL bin.

Design Features:

Panatrack Post Fulfill Procedure

Panatrack can execute a custom “Fulfill Order” “PostSubmitStoredProcedure”. WilloWare will create a SQL stored procedure that Panatrack can execute after SOP fulfillment has been performed that will make it appear in GP “as if” all of the selected inventory that will perform the following:

  • Create an Inventory Bin-To-Bin Transfer transaction to account for moving inventory from the Picking Bin into the Staging Bin (FULFILL).
  • Update the Item-Site-Bin Quantity Master table to reduce inventory (and allocations) in the original bin and increase inventory (and allocations) in the staging bin.
  • If the Item is Lot Numbered: Update the Lot Master.
    • Decrease the original Lot record. If Qty Sold = Qty Received, delete the record
    • Create a new Lot Receipt record
  • Update the SOP Bin Work/History table with the new Bin
  • If the Item is Lot Numbered: Update the SOP Serial/Lot Work/History Table with the new Bin and Date Sequence Number

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

www.willoware.com/contact-me/