Author: admin

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/

 

MRP Move In, Move Out, Cancel in PowerATP

11-JUL-2024

Today brings an exciting update to PowerATP–the ability to include in the ATP calculation MRP suggested cancels, move-ins and move-outs.  PowerATP can now give you an easy to understand view of the MRP suggestions and the impact they will have on inventory availability.

A screenshot of a computer Description automatically generated

The Red X shows MRP Cancel suggestions.  Not only is it showing Manufacturing Orders for BA100G that should be cancelled, but it is also showing the impact on BA100G from cancelled Manufacturing Orders for 100XLG (which eliminated the Picklist demand for BA100G).

Move-Ins are indicated with the UP ARROW.  MO0057-0001 is shown on the suggested move-in date of 5/12/2017 (the orignal due date was 6/29/2017).

Move-Outs are indicated with a DOWN ARROW.  They are shown on the suggested move-out date.

You can see the impact of the MRP suggestions by toggling the Include MRP checkboxes and refreshing the display.

MFGPowerPack 2024-07-10

Release Date: 10-JUL-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.242
* PowerATP: (1) Moved inclusion of MRP Cancel suggestions to its own setup option (previously Cancels were brought in if MRP MOs or MRP POs were included), (2) Added options to include MRP Move In and Move Out suggestions, (3) Added icons in the Document Number field to indicate Cancels, Move-Ins and Move-Outs, (4) Cancels are no longer shown as separate “demand” lines, the quantity is zeroed so it is removed from the ATP calculation.

MFGPowerPack 2024-07-09

Release Date: 9-JUL-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.241
* PowerATP: Added checkbox to the Option Set to open PowerATP from the Sales Transaction Line instead of opening the GP ATP window. To enable this feature, mark the “Open from SOP Line” checkbox in an Option Set, then click the User Default button and add your User ID to the User Default window. If “Open from SOP Line” is marked in an Option Set and the Option Set is the default for a User ID, when the user clicks the ATP blue arrow in SOP Entry it will open PowerATP instead of the GP ATP window.
* NEW TWEAK: Post Data Collection Journal Entries- normally the Data Collection window will create and save Journal Entries, which then need to be posted through the GL Batch or Series Post windows. This Tweak will post the transactions at the moment they are created.

Customization CR1017 Write Off Small Balances

Customization CR1017

Write Off Small Balances

Description of Need:

ACME would like to automate the process of small document write offs for the following documents:

  • Invoices with the amount remaining of $15.00 or less, unless:
  1. The document is on a Scheduled Payment Plan.
  2. The original document amount is $15.00 or less.
  • All outstanding Late Fees if the original invoice amount is paid in full.
  • All outstanding Finance Charges if the original invoice amount is paid in full.

Description of Solution:

The user will continue to use the Write Off Documents window to perform the write off process.

Navigation: Routines>>Sales>>Write Off Documents

A screenshot of a computer Description automatically generated

The enhancement requires the user select the Writeoff Type = Underpayments and the Create One Writeoff per = Document, but all other entries and selections, including the Customers filters can be used to further restrict documents.

To activate the enhanced functionality, click Additional >> Write Off Small Balances. When the enhancement is active, the window title bar will be updated to read: Write Off Documents ~ Small Balance Enhancement.

NOTE: The below functionality will only occur if the enhancement is active.

When the PROCESS or PREVIEW buttons are selected, the enhancement will use the user entered filters in addition to the enhancements requested to only return the following documents:

SALES / INVOICES where:

Amount remaining less than or equal to the value entered into the Writeoff Limit Field ($15.00)

AND

The invoice is not on a Scheduled Payment Plan.

AND

The original invoice amount was equal to or less than the value entered into the Writeoff Limit Field ($15.00)

DEBIT MEMOS where:

The Customer PO field is “LATE FEE”

AND

The original invoice was paid in full. The original invoice number is stored in the transaction Description field.

AND

The late fee is not on a Scheduled Payment Plan.

FINANCE CHARGES where:

The Customer PO field is “FINANCE CHARGE”

AND

The original invoice was paid in full. The original invoice number is stored in the transaction Description field.

AND

The finance charge is not on a Scheduled Payment Plan.

All other documents that might normally be included by GP will be ignored.

The user can click PREVIEW to review the documents that will be written off.

Click the PROCESS button to execute the GP Write off process for the entered documents. As part of the custom processing, the enhancement will add the following to the Credit Memo description, depending on the document type of the written off debit:

SALES/INVOICES- “Write-Off Small Balances

LATE FEE or FINANCE CHARGE- “Interest & Late Fees”

Assumptions/Requirements:

  1. The functionality described above is intended for the GP Desktop client.
  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
  • MDA
  • Analytical Accounting
  • Copy functionality found in SOP, POP and Inventory
  • Field Service
  • Extended Pricing
  • Manufacturing

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

www.willoware.com/contact-me/

 

LeanMFG 2024-06-26

Release Date: 26-JUN-2024
GP Versions: 12/14/16/18
LeanMFG Build: 4.60
* MO Entry: (1) MPP On The Fly: added check for available inventory before allowing addition of components, (2) Added User Defined Fields to MO Entry
* FULL INSTALLATION ROUTINE REQUIRED WITH THIS RELEASE. This release adds new SQL tables to support the User Defined Fields

Multi-Product Production On-The-Fly

25JUN2024

Keywords: multiple finished goods, multi-product production

WilloWare’s LeanMFG module supports multiple methods of manufacturing:

  • Regular discrete manufacturing where a list of raw materials (Inputs) is used to produce a finished good (Output).
  • Disassembly/reverse assembly where a single item (Input) is taken apart into multiple items (Outputs).
  • Batch Processing where the raw material quantities are based on a specified quantity of finished good.  For example, all of the raw materials could be specified on the BOM based on a 12,000LB batch of the finished good.  This addresses a common issue with discrete manufacturing software where the raw materials must be specified based on a “per unit” of finished good output, which results is very small quantities that cannot be recorded accurately in software.
  • Multi-Product where there can be one or more raw materials which are turned into two or more finished goods.  For example, a single piece of leather may be turned into multiple belts and wallets.

Released today is a new extension of the multi-product manufacturing functionality.  Previously a Multi-Product Bill of Materials was required by LeanMFG, which listed the possible inputs and outputs.  Now you can perform Multi-Product Production on-the-fly!  As you add Outputs to a Multi-Product Manufacturing Order, the components of the Output are added to the Inputs (raw materials).

From the MO Entry window, Outputs tab, click the ADD OUTPUT button.

A screenshot of a computer Description automatically generated

Select the finished good item and BOM and enter the quantity to produce.

A screenshot of a computer Description automatically generated

The finished good is added to the OUTPUTS tab:

A screenshot of a computer Description automatically generated

And the components are added to the INPUTS tab:

A screenshot of a computer Description automatically generated

This process can be repeated to add as many items to the Outputs list as needed.

Going back to the leather scenario above, now production can be recorded on the fly as workers determine what can be made from a particular piece of leather.  The belt may require various pieces of hardware (buckles, decorations, etc) which get added to the Inputs when “belt” is added to the Outputs, while the hide itself is added to the Inputs manually.

The new Multi-Product on-the-fly capability creates a streamlined easy to use process that gives production staff the information they need (i.e. what are the extra bits and pieces needed to make a belt) while making it as simple as possible to record production (simply put what you are going to make on the Outputs tab).

LeanMFG 2024-06-25

Release Date: 25-JUN-2024
GP Versions: 12/14/16/18
LeanMFG Build: 3.59
* MO Entry: (1) enabled Extended Cost field and calculation for Unit Cost when Ext Cost is entered. (2) For Multi-product, added “Add Output” window that allows adding a new Output to the MO and all of its components from a Regular BOM get added to the Inputs. This supports “Multi-product on the fly”. (3) Fixed issue where default output allocation percent was not set correctly.

GPPowerPack 2024-06-24

Release Date: 24-JUN-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.178
* Bank Deposit Filters: a previous change (b164) added Deposit Slip Preview. The auto-redisplay functionality of this window creates a situation where it is impossible to unmark a marked deposit. This build resolves that issue. (#202400816)

Customization DS1382 SOP Shortage Override

Customization DS1382

SOP Shortage Override

Problem Definition:

Currently, ACME’s Sales Entry personnel are entering Orders without allocation/fulfillment. The Orders are processed by a second user who then performs fulfillment by line. If shortages exist, it requires the user to make the correct choice in the Sales Quantity Shortage Options window, and then also enter Bin and Quantity information in the Sales Bin Quantity Entry window. This extra data entry is time consuming and error prone.

ACME would like Dynamics GP to always override shortages for certain customers. They would like the Sales Entry personnel to not need to choose “Override Shortage” in the Sales Quantity Shortage window, and it should automatically fulfill from the Default Sales Fulfillment even if it requires overriding shortages in the bin.

Solution Overview:

WilloWare will provide a customization that allows specifying Customer IDs for which the Sales Transaction Entry will “silently” override shortages and fulfill from the default Sales Fulfillment Bin.

Design Features:

ACME Setup

Navigation: Tools >> Setup >> Company >> ACME Setup

Table Description automatically generated with medium confidence

The Customers entered in this list will have their Sales Order “silently” allocated and fulfilled, regardless of shortages. See next section for details.

Field Function
Customer ID Enter a Customer ID, or select one from the Lookup
Name Displays the Customer Name

Silent Allocation/Fulfillment

When a Sales ORDER is entered in Sales Transaction Entry, and the Customer ID is listed in the ACME Setup window, the following will occur:

Graphical user interface, text, application Description automatically generated

Graphical user interface, application Description automatically generated

If there is a shortage in the SITE, the Sales Quantity Shortage Options window will very quickly open and then close. The customization will automatically select “Override Shortage” and “click” the OK Button. The user will not have to interact with the window, and it may open/close so quickly that it is not visible.

Next, if there is a shortage in the Default Sales Order Fulfillment bin, the order will be fully allocated out of the default bin even if that requires driving the available quantity negative in the bin. This step will not be visible to the user as the Bin Quantity Entry window will not open.

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/

 

MFGPowerPack 2024-06-18

Release Date: 18-JUN-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.240
* MO Split: This only impacts 3rd party integrations into MO Split. Added additional controls to prevent the following scenario: MO00123 is split and then deleted so MO00123 no longer exists in the WO Master but the splits do (MO00123-001, etc). In some cases when MFG is generating the “next MO number” it cycles backwards to fill in a gap in the numbering sequence so it reuses MO00123, or an integration provides it. This results in a confusing situation where MO00123 and MO00123-001 are for different item numbers.

MFGPowerPack 2024-06-04

Release Date: 4-JUN-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.239
* Vendor Pricing:changed Vendor Price Maintenance to allow entering QTY Price Breaks for single units (i.e. QTY 1 to 1 is $5, QTY 2 to 2 is $4, QTY 3 to 3 is $3 and so on). This allows the Start/End Qty to be the same on a line but incrementing between lines.

MFGPowerPack 2024-05-24

Release Date: 24-MAY-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.238
* Sales Forecast Integration (SFI):(1) fixed issue when importing into an empty forecast from Excel which would result in the following error (Violation of PRIMARY KEY constraint ‘PKSC020130’. Cannot insert duplicate key in object ‘dbo.SC020130’), (2) removed CSV support

 

GPPowerPack 2024-05-22

Release Date: 22-MAY-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.177
* Sales Pro: when the View is set to Customer History or Customer Items, and the user enters an Item Number (or picks one from the Item Number Lookup), and the Item does not exist in the Customer’s History or list of Customer Items, the window will display ‘NOT FOUND’ next to the Item Number field. This helps prevent user errors when there are multiple Item Numbers that are similar because the scrolling window will be positioned with the ‘nearest’ Item Number that exists. For example, if “BOX-11” does not exist in the Customer’s History but “BOX-12” does, ‘NOT FOUND’ will display next to the Item Number field while the scrolling window will be positioned on “BOX-12”.

 

CompleteCount 2024-05-21

Release Date: 21-MAY-2024
GP Versions: 12/14/16/18
CompleteCount Build: 4.61
* Mass Add: fixed issue with “Query Save” functionality that prevented it from retrieving correctly after saving.
* CC Stock Count Maintenance: fixed issue that could prevent opening the Mass Add window with a new Stock Count ID.
* Excel Link: performance enhancements significantly speed export to excel (export of 3000 records went from 2 minutes to 5 seconds).

GPPowerPack 2024-05-16

Release Date: 16-MAY-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.176
* UM Schedule Change Utility: (1) Added a data validation check on IV30300 to catch invalid Units of Measure, which can cause the update to fail.
* Mass Batch Change: fixed issue that left a stranded batch activity record in the following scenario: open MBC, select an existing query, change the Destination Batch, save the query, close GP, the lock is cleared when the user logs in again. This build ensures Batch Activity is cleared when the Batch ID is changed.

MOGenerator 2024-05-07

Release Date:7-MAY-2024
GP Versions: 12/14/16/18
MOGenerator Build: 6.137
* MO Scheduler: fixed issue when “rebuild picklist” is false that causes the required date on all picklists to be updated

MOGenerator 2024-04-30

Release Date:30-APR-2024
GP Versions: 12/14/16/18
MOGenerator Build: 6.136
* FULL INSTALLATION ROUTINE IS REQUIRED. This build removes SQL table constraints on two MOGen tables.
* MO Scheduler/Create MOs/MOGenV2: For MO Scheduler and Create MOs, changed the DUEDATE column in W7158Import header to allow date/time. For MOGenV2 changed the STRTDATE column in W7158MOGen2date to allow date/time. Providing a time is optional. If provided the utilities will create an MO/schedule an MO/reschedule an MO using the Date & Time provided.

MFGPowerPack 2024-04-25

Release Date: 25-APR-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.237
* OSRC Add To PO: fixed issue where an incorrect PO Number could remain in the window and be used after the warning that it cannot be used (#202400483)

MOGenerator 2024-04-10

Release Date:10-APR-2024
GP Versions: 12/14/16/18
MOGenerator Build: 5.135
* MCTE Integration: added integration of Picked By user id
* MOGen window: fixed issue that was causing the timer minutes setting to not save/retrieve correctly

GP PowerPack Auto-Select Lot Numbers

Price $2400Manual

Automatically Select Lot Numbers with the click of a button!

A screenshot of a computer Description automatically generated

WilloWare’s Auto-Select Lot Numbers enhancement in GP PowerPack adds the ability to automatically select lot numbers in the following windows in Dynamics GP:

  • Item Lot Number Entry (Item Transaction Entry)
  • Item Transfer Lot Number Entry
  • Item Bin Transfer Lot Number Entry
  • Assembly Serial/Lot Entry
  • Sales Lot Number Entry
  • Purchasing Returns Lot Number Entry
  • Transfer Lot Number Entry (SVC In Transit Transfer)
  • Depot – Lot Number Entry (SVC Depot Work Order)
  • Service Lot Number Entry (SVC Service Call)
  • RTV Outbound Lot Number Entry (SVC Return To Vendor Entry)

Auto-Select Lot Numbers considers the SORT setting so that the lot selection is done by Date Received, Lot Number, or Expiration Date.  It also looks at the Bin Restriction (where present) and only pulls inventory from the specified bin.

GPPowerPack 2024-04-03

Release Date: 3-APR-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.175
* NEW Email Cash Receipt Report: This feature only works with 18.5 and above. The WilloWare Cash Receipt Report includes Apply information, while the GP report does not.
* NEW Auto-Select Lot Numbers: adds ability to auto-select lot numbers. The auto-select function uses the Sort By setting and Bin restriction. If Sort By is by Lot Number then auto-select is performed in lot number order, likewise with Date Received and Expiration Date. If the Bin restriction is set, auto-select only draws inventory from the specified bin. Auto-Select Lot Numbers is added to the following windows:
* Item Lot Number Entry (Item Transaction Entry)
* Item Transfer Lot Number Entry
* Item Bin Transfer Lot Number Entry
* Assembly Serial/Lot Entry
* Sales Lot Number Entry
* Purchasing Returns Lot Number Entry
* Transfer Lot Number Entry (SVC In Transit Transfer)
* Depot – Lot Number Entry (SVC Depot Work Order)
* Service Lot Number Entry (SVC Service Call)
* RTV Outbound Lot Number Entry (SVC Return To Vendor Entry)

MOGenerator 2024-03-29

Release Date:29-MAR-2024
GP Versions: 12/14/16/18
MOGenerator Build: 5.134
* FULL INSTALLATION ROUTINE REQUIRED. This release includes new SQL tables for the MCTE integration.
* MCTE Integration: NEW – First release of MFG Component Transaction Entry (MCTE) integration. Supports Allocation, Reverse Allocation, Issue, Reverse Issue of non-tracked inventory without multibins. All Items from the picklist can be added to the transaction in the quantities specified on the picklist (i.e. “Mark All” on the MCTE window), or only specific items and quantities can be added to the transaction.
* This release contains a second dictionary (W7159) called “Mfg Interface”. This dictionary is required but has no installation requirements.The MOGen dictionary is W7158).

Simplify Payables

Select Checks Filters in GP PowerPack can dramatically reduce the amount of time required to create a PM Check Batch.

Create and save a query (aka a Filter) that identifies a group of invoices to pay, such as a list of Vendors from whom you purchase steel.  Once you create a Filter it is easy to use again by selecting it from a Lookup.

The list of search criteria includes:

  • Batch ID
  • Current Trx Amount
  • Discount Date
  • Distribution Account
  • Document Currency
  • Document Description
  • Document Number
  • Due Date
  • Payment Priority
  • PO Number
  • Vendor Class
  • Vendor ID
  • Vendor Name
  • Voucher Number
  • Plus more…and all of the POP Receivings User Defined Fields

Select Check Filters can also import a list of invoices/vouchers to pay from Excel or SmartList.  Shown below is Select Checks Filter after reading a list of invoice to pay directly from a SmartList Favorite.

GPPowerPack 2024-03-18

Release Date: 18-MAR-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.174
* Select Checks Filters: (1) Filters- fixed datatype map so that fields are linked to the correct datatype in the Values list. (2) Added currency datatype to list of values for filtering on Current Transaction Amount (3) Clicking Apply on the Filters window now automatically runs the Build Batch/Add to Batch routine (4) Changed the appearance of the Mark All/Unmark All button so it is more obvious that it is a button. (5) Added Import from Excel and Import from SmartList

MFGPowerPack 2024-03-13

Release Date: 13-MAR-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.235
* PowerATP: (1) Added MRP Cancel Suggestions, (2) Fixed issue when zooming to PowerATP that could result in error and closing the window, (3) Fixed display of Purch Lead Time, Mfg Lead Time, Buyer ID and Planner ID so it pulls from the Site values when a Site is provided.
* SOP Backorder All: fixed issue with Quote to Order transfer that could result in doubling the QTY Backordered (#202300257)

NetSuite C++ Hoax

If you see an email from NetSuite trying to scare you about C++ and security and Dynamics GP, please consider this:

GP is NOT a web-facing application.  If a hacker is hacking GP they are already inside your system.  If they are inside your system you have much bigger problems than some theoretical development language security issues.  If a hacker is inside your system they are not going after GP, they’re going after your SQL database, emails, files, etc.

Are you concerned that a burglar can look in your medicine cabinet or are you concerned that they’re getting through your front door?

LeanMFG 2024-03-05

Release Date: 5-MAR-2024
GP Versions: 12/14/16/18
LeanMFG Build: 3.58
* MO Entry: fixed issue with cost allocation to finished good that occurs when the components have more currency decimals than the finished good. This applies to systems where Multicurrency is NOT enabled and currency decimals on the output item is less than the input item(s), or Multicurrency IS enabled and the Item Currency decimal places setting for the functional currency with the Output item is less than the Item Currency decimal places setting for the input(s).
* Added label to GoTo buttons for better appearance with Action Pane menus
* This release will notify POWERUSERs when there is a new version of the software available for download.

MFG Calendar Date Fix

The Manufacturing Calendar windows (Shop Calendar and Work Center Calendar) are funny.  Have you ever looked at the years available in the “years” dropdown list?

The list starts with 1925!  Great Plains (what is now Dynamics GP) was not even created until at least 1930 and even way back then manufacturing planners had figured out that you cannot schedule work in the past.

Seriously though, consider that the list of years is “hard coded”–the original developer typed all of those years into the list when the window was created 90s, and look how far into the future it goes:

Yup, 2026.  So, somebody sat there and typed 100 years into that dropdown, filling it mostly with historical years that would not be used, and then only went forward to 2026.

What is even more astounding is that a developer can write a tiny bit of code to populate the dropdown list at the moment the window opens.  So instead of entering 100 years one at a time, you could have a bit of code that says: start today, count to 10 adding +1 to the year each time.  That’s it!  Now the list starts at today and goes forward ten years, and it will always do that.

Well, here we are getting close to 2026, the list is hard-coded and you are going to need to schedule manufacturing orders.  WilloWare’s got your back!

We just added a new TWEAK to MFG PowerPack called “Calendar Fix”.  The Tweak adds years to the drop-down so it goes out 10 years (User Date plus 10 years).  The Shop Calendar and Work Center Calendar are both covered by Tweak.

Lastly, the above situation is still true as of Dynamics GP build 18.6.1685, and any version of GP prior to that.

MFGPowerPack 2024-03-01

Release Date: 01-MAR-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.234
* NEW: MFG Tweak-Shop Calendar Year Fix- the MFG Shop Calendar “years” dropdown only goes to 2026. Enabling this fix will populate the Years dropdown to the User Date plus 10 years.

MOGenerator 2024-02-22

Release Date:22-FEB-2024
GP Versions: 12/14/16/18
MOGenerator Build: 4.133
* Fixed issue with Action Pane style menus that caused GoTo buttons to navigate incorrectly
* MOGenV2: fixed issue in rescheduling routine that forced picklist rebuild

Declutter SmartList

SmartList is a wonderful tool!  It makes it so easy to explore your GP data and once you get the desired columns, in the right order, with the Search Criteria you need you can save it as a Favorite for quick access.

And when you need to look at things slightly differently you create another Favorite.  So does everybody else.  Maybe somebody leaves the company and the new person does not know what all of the old Favorites do, so they create new ones.  Eventually your SmartList looks like this:

How do you go about cleaning this up?  Which Favorites are used?  Who uses them?  Can you delete them?

GP PowerPack has a new Tweak called SmartList Activity Tracker.  It watches which Favorites are used, counts how often they are used, when, and by whom.  The result looks like this:

Using this information, you can embark on a project to declutter SmartList!  Keep the things that are used and get rid of the unnecessary stuff you have accumulated over the years.

MFGPowerPack 2024-02-20

Release Date: 20-FEB-2024
GP Versions: 12/14/16/18
GP PowerPack Build: 8.173
* COMPLETE INSTALLATION ROUTINE REQUIRED FOR THIS BUILD.
* New Tweak: SYS-SmartList Activity Tacker: creates an access log for SmartList Objects so you can monitor which ones are used, and which ones are not, and reduce SmartList clutter by getting rid of unused SmartLists.
* Added label to GoTo buttons for better appearance with Action Pane menus
* This release will notify POWERUSERs when there is a new version of the software available for download.

MFGPowerPack 2024-02-15

Release Date: 15-FEB-2024
GP Versions: 12/14/16/18
MFG PowerPack Build: 13.233
* Fixed case sensitivity issue in the Actual Cost Rollup installation routine. If you had an installation error with the previous build and your database is Case Sensitive, drop the stored procedures below before installing this build:
— wspRollupCosts
— wspCreateBOMLev1Pending
— wspBuildBOMLev2File
* PowerATP: added Additional Menu to access PowerATP from (1) MRP Workbench, (2) PAB Inquiry, (3) MRP Quantities Query, (4) Pegging Inquiry

Dynamics GP Low Level Code Fix

The Low Level Code (LLC) utility in GP Manufacturing calculates the lowest level at which any component is found.

For example, CBA100 is at level 2 and CAP100 is at level 3.  Material Requirements Planning (MRP) uses this LLC so it knows at which level it needs to start planning (i.e. start at the “top” and work your way down).

Imagine a situation where A uses B which uses C which uses B.  This is a circular Bill of Materials (BOM).  Normally Dynamics GP will not allow you to create this type of arrangement.  However, the LLC Utility has a bug that makes it think there are circular BOMs.

 

 

The LLC utility “Maximum Levels” setting provides a “fail safe” to address circular BOMs.  If the utility runs through the A–B–C–B loop 99 times it will stop.  When you look at the LLC code on Item Engineering it will show 99.  An easier way to see this is to look at the Item Engineering SQL table (IVR10015).

The bug in the LLC utility is that it does not traverse straight down each BOM.

When working down 100XLG it should retrieve the specific BOM for BA100G (in this case the MFG BOM for BA100G), and then the MFG BOM for CBA100.  Instead, it retrieves ALL BOMs for BA100G (i.e. the MFG BOM, ENG BOM, all CONFIG and ARCH BOMs).

This is a problem because you could legitimately have parts that can be changed into each other.  In the BOM above perhaps you MAKE BA100G using CBA100, but you also sometimes DISASSEMBLE BA100G back into parts.  You could use one of the Named BOM Types (i.e. ARCH or CONFIG) to store “disassembly” BOMs.  Now when looking at all available BOMs you have this situation:

You use CBA100 to make BA100G, but you can take apart BA100G to “make” a CBA100.

When the LLC utility is traversing down 100XLG it sees it contains CBA100.  At that point it grabs ALL BOMs and starts working down those.  That creates a circular situation because it can proceed down the ARCH BOM which takes it back “up” to BA100G.  It is then stuck in a circle.

WilloWare has a fix for the Manufacturing Stored Procedure in question.  If you would like it, please contact our support team.