Author: admin

Customization DS1011- SOP Pricing by Zone

Customization DS1011

SOP Pricing by Zone

Problem Definition:

ACME is a non-profit who business is primarily Governmental Set Aside contracts in the state of Texas. They sell copy paper. They manually enter the Ship To Address on each Sales Transaction because any given Government entity might have a large number of Ship To addresses. For example, they might sell paper to the city of San Antonio, and the purchasing agent requests that the Order be shipped to a specific building.

ACME does not want to maintain a large number of separate addresses.

One aspect of the contracts is that there can be different pricing by Zone within the state of Texas, where each Zone contains multiple Zip Codes. ACME has created Price Levels in Dynamics GP that match the “Zone”.

ACME has two requirements:

  1. They need a way to map Zip Codes to Price Levels (Zones).
  2. When entering a Sales Transaction, automatically use the Zone Pricing, if it exists. Given the Ship To Zip Code, the system should check the mapping table to see if the Zip Code is mapped to a Price Level, and then if the Price Level exists for the Item the “Zone Pricing” should be used. If Zone Pricing does not exist, GP should use the normal default price level.

Design Features:

Zone Pricing

The installation process for the enhancement will create a mapping table. The table name will be provided in documentation when the enhancement is delivered. It will have two columns:

  • Zip Code
  • Price Level

ACME will maintain the table through the SQL Server. This information changes very rarely.

In Sales Transaction Entry, when an Item is entered, the enhancement will check for a Price Level assigned to the Ship To Zip Code in the mapping table. It will then check if the Price Level is assigned to the Item in Item Price List Maintenance:

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

If so, the enhancement will force Dynamics GP to use the Zone Price Level rather than the default Price Level for the Item-Customer combination.

Assumptions/Requirements:

  • The functionality described in this document is intended for the Dynamics GP desktop client. Unless specified otherwise, all testing will occur in the desktop client only. Projects created in Dexterity should have a very high level of compatibility with the Web Client, but cannot be guaranteed without explicitly including additional time in the estimate for testing in the Web Client.

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

www.willoware.com/contact-me/

 

MFGPowerPack 2025-03-26

Release Date: 26-MAR-2025
GP Versions: 12/14/16/18
MFG PowerPack Build: 15.254
* PowerATP: (1) The “Available” Field label is now a dropdown box providing navigation to: Item Stock Inquiry, Bin Quantity Inquiry, Lot Number Inquiry, Serial Number Inquiry, Purchase Receipts Inquiry, and Item Quantities By Site (the lookup window), (2) PowerATP can now be opened from SOP Entry via the Additional Menu. It will automatically display the Item Number on the selected SOP Line. This provides another way to access PowerATP in addition to the “Open From SOP” option in the ATP Setup Option Set. The “Open From SOP” option takes over the SOP Entry expansion button that would open the GP ATP window and make it open the PowerATP window instead. (3) A new WARNING indicator appears next to Purch Lead Time & Mfg Lead Time if the ATP goes below zero within the Lead Time (i.e. if LT is 30 days and ATP goes negative within 30 days a warning sign appears next to the LT field).

 

 

MOGenerator 2025-03-24

Release Date:24-MAR-2025
GP Versions: 12/14/16/18
MOGenerator Build: 12.148
* MORI2: The Data Collection component added in build 147 was not correctly setting the labor code values on the data collection line, which lead to an incomplete calculation, it was also missing the overheads calculation when a sequence was backflushed and had no labor rate (only overheads).

Customization DS0690: Drop Ship PO Enhancement

Customization DS0690

Drop Ship PO Enhancement

Problem Definition:

ACME currently utilizes Dynamics GP to manage and support Inventory Control. They do not maintain inventory in-house, but supply customers with products directly from vendors via Drop Ship Sales Transactions and Drop Ship Purchase Orders.

Users enter a Sales Transaction and the Sales Line item is flagged as “Drop Ship” by marking the Drop Ship checkbox on the line item. The unit cost is then manually changed on the Sales Line to reflect the Item’s appropriate unit cost from the vendor.

The user then generates a Purchase Order from the Sales Line. The PO’s unit cost defaults from the Vendor ID’s Last Originating Invoice Cost. The user must update the PO’s unit cost to the unit cost entered on the Sales Line. ACME would like this cost to default automatically.

Design Features:

Sales Transaction Entry

The user will navigate to: Transactions >> Sales >> Sales Transaction Entry

The user will enter a Sales Order or Sales Backorder document. The user will enter a Sales Line and mark the Drop Ship flag. The user may update the Sales Line’s Unit Cost field to reflect the true Vendor cost.

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

For Sales Lines which have their Drop Ship flag marked, the following will occur when the user clicks the PURCHASE button form the Actions menu on the Sales Transaction Entry window:

The Sales Line’s unit cost, regardless of whether it has been manually updated, will default as the PO Line’s unit cost for the Item Number on the Purchase Order Preview window- Item Tab. The unit cost will be set when either of the following occurs:

  • The Primary Vendor ID has defaulted when the Purchase Order Preview window opens.
  • A Vendor ID is manually entered or selected from the lookup on the PO tab or the Item tab.

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

NOTE:

  1. The selection of Vendor ID will have no impact on the Item’s Unit Cost in the Purchase Orders Preview window’s Item tab. Regardless of the Vendor ID selected, even if it is updated in the Purchase Order Preview window, the PO Line’s unit cost will always default to the unit cost entered on the Sales Line.
  2. As requested by ACME, the user may manually override the Item’s Unit Cost field in the Purchase Orders Preview window’s Item tab.

Assumptions/Requirements:

  • Multi-Currency is not utilized.
  • The Sales Line’s Unit of Measure always matches the Item’s Default Purchase Unit of Measure.

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

www.willoware.com/contact-me/

 

AI and ERP Best Practice

Keywords: Copilot, AI, ERP data

Date: 17-MAR-2025

Let me start by saying that if you can cite a specific Microsoft document that contradicts the scenario below, please let me know so I can update this post.

I think the following scenario is very concerning.

The difficulty I had in knowing for sure whether or not the following scenario is possible, or is forbidden, is part of the problem.  But let me back up a little bit so you know how I got here.

When WilloWare started we used QuickBooks (on site) and then we moved to an early release of QuickBooks Online (we quickly left the product, you will see why shortly).  Not long after we made that transition, I received the following offer from QuickBooks/Intuit:

Note where the loan offer says, “Congrats on hitting about xxxx annual sales revenue.”  The only way they could have known that was by looking at our ERP system data hosted on their servers.  After some digging, I found this statement in their Terms of Service:

The key phrase is “You grant Inuit permission to use information about your business and experience to help us to provide the Intuit Services to you and to enhance the Services.  You grant Intuit permission to combine your business data, if any, with that of others in a way that does not identify you or any individual personally.” (Bold added for emphasis).

If you use D365 as your ERP system can Microsoft use your data in this way?  After hours of reading legal documents and terms of service, I don’t know.  I turned to Microsoft’s own Copilot, because surely it knows the answer.  Here’s what it had to say regarding Microsoft’s ability to use ERP system data from D365:

Data Usage: Microsoft may use your data to provide and improve its services. This includes using data for service operations, troubleshooting, and enhancing features.

As a follow-up I asked Copilot if anything in any of the Microsoft terms would forbid Microsoft from using D365 ERP data to train Copilot.  It replied:

“As of my latest update, Microsoft does not explicitly state that it uses ERP data from Dynamics 365 to train AI models like Copilot. However, Microsoft does collect and use data to improve its services, which could include enhancing AI capabilities.”

Could “enhancing features” mean training Copilot to be able to coach you on “Best Practices” in your use of D365?

Imagine that you are really good at what you do (I’m sure you are!) and Copilot can learn from your Bills of Material and routings, your manufacturing scheduling patterns and your purchasing patterns, what the Secret Sauce is that makes you successful.  Would you want the “enhanced feature” of a business-trained co-pilot to coach your competitors on how to be better?

 

 

 

Dynamics GP and Tariffs

Keywords: Dynamics GP, tariff, surcharge

Date: 13-MAR-2025

This article discusses methods for handling the scenario where your vendors are subject to tariffs and are passing those costs on to you.  The specific method of passing on those costs, and what you want to do about the costs, dictate which solution you need to take.

There are two ways the tariff costs could be passed on: (1) Increased per unit cost from the vendor, (2) Surcharge on the Vendor Invoice.

NOTE: This article is not addressing companies that have to pay tariffs to a government entity.

Increased Cost

If the vendor is increasing the Unit Cost of the product, then the increased cost will flow through manufacturing into your finished good (if you are using Actual Cost).

Given the highly variable environment the last several years due to supply chain disruptions, fuel costs, and tariffs, we have seen an uptick in requests to convert from Standard to Actual costing in Dynamics GP (yes, this is possible).  So, one consideration is moving to Actual Cost if you are on Standard Cost.

The next question is: How much will the cost of our Finished Good change due to the purchased material cost changes?  With Standard Cost you can use the Standard Cost Changes window to enter the new cost of purchased parts and do a roll-up to see the new finished good cost.

If this affects a large number of parts you can simplify the update using our Proposed Cost Update utility:

MFG PowerPack Proposed Cost Update

If you are already using Actual Cost calculating the expected new cost of the finished good is trickier.  We have a couple of tools that can help you: (1) Indented BOM Report, and (2) Actual Cost Rollup.

The Indented BOM Report run from the BOM Maintenance window and includes the unit cost of each component.

Actual Cost Rollup does a “Standard Cost Rollup” for Actual Cost BOMs.  This routine tallies up the total cost of all components in the entire exploded BOM.  Note that with Actual Cost the roll-up can be tricky because each inventory receipt layer could have a different cost.  To help account for this the Actual Cost Rollup module allows you to enter a “Pending Cost” so you can calculate the finished good cost based on an expected material cost.

MFG PowerPack Actual Cost Rollup

Lastly you need to decide what to do about pricing in Sales.  The finished good cost will contain the price increases from your vendors, so it either stops with you and lowers your margin, or you change pricing and it flows through to your customers.  If the increased costs only affect some parts, you can be strategic about it and notify only the affected customers by running a SmartList on Sales Transactions to find customers who purchased specific items.

Surcharges

The other option is that pricing stays the same from your vendors but they start tacking on a surcharge, and this may already be happening for fuel costs.  For various reason you may want to either include the surcharge in the cost of the inventory or pass through the surcharge to your customers.

To include the tariff/surcharge cost into the inventory cost, consider the Landed Cost module in GP.  Freight, duties and other costs can be recorded separately from the PO/PO Receipt/Invoice and those costs can revalue inventory.  Just be aware of the fact that the Landed Cost Module cannot always accomplish the revaluation and the additional costs hit PPV.

If you use Landed Cost this puts you back into the first scenario where the purchased part unit cost increases and then flows through to the finished good.

Another option is that you want to track the surcharge amount and then allocate that to a surcharge in sales.  As already discussed, the tricky part of this is determining how much surcharge to add in sales based on the parts contained in the exploded BOM of the finished good.  WilloWare has a solution for this.

At a high level the process works like this (this is all automated by our Surcharge module):

  • Add a SURCHARGE item on the PO Invoice to record the surcharge (tariff) amount.  Posting the Invoice debits Accrued Surcharge.
  • In Sales a routine calculates the amount (dollars) of surcharge that should be added to the invoice by exploding the BOM to find the total quantity of buy items used that were subject to the surcharge (tariff).  For example, if the BOM uses 1 of a material that costs $10 and has a 25% surcharge/tariff it would calculate a $2.50 surcharge on the invoice.
  • Add a SURCHARGE item on the Invoice to record the total surcharge.  Posting the Invoice credit Applied Surcharge.

The Surcharge module provides a more precise method of managing pass through surcharges compared to a blanket surcharge.

 

Customization DS1352- Site Specific SOP & POP Posting Accounts

Customization DS1352

Site Specific SOP and POP Posting Accounts

Problem Definition:

ACME is using the site swapping functionality within GP. This works fine for Sales and CoGS in the SOP module, and also the IV account in POP. ACME needs the site swapping extended to the following accounts:

Sales Transactions

  • Accounts Receivables GL
  • Trade Discount (from Document Level Field)
  • Freight (from Document Level Field)
  • Miscellaneous (from Document Level Field)
  • Tax (from Document Level Field)

 

Purchase Order Processing

  • Accounts Payable Trade
  • Accrued Purchases
  • Trade Discount (from Document Level Field)
  • Freight (from Document Level Field)
  • Miscellaneous (from Document Level Field)
  • Tax (from Document Level Field)

Solution Overview:

ACME has already set up a site segment to swap. This enhancement will use the same segment ID and number when swapping the accounts highlighted in the following sections. In either case, if a valid account number cannot be found, the original account number will be used.

Design Features:

Sales Document Posting

The highlighted accounts will have the segments swapped based on the header Site ID when an INVOICE or RETURN is posted, or an edit list is printed. The account numbers will not be updated until the sales document is posted or an edit list is printed.

Graphical user interface, application, table Description automatically generated

Purchasing Invoice Posting

POP does not use default Site ID’s in the header. As a result, the highlighted accounts will have the segments swapped based on the first Site ID found when scanning the lines of the PO INVOICE upon posting, or an edit list is printed. The account numbers will not be updated until the document is posted or an edit list is printed.

Graphical user interface, application Description automatically generated

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 DS1516- Print MC Misc Checks

Customization DS1516

Print MC Misc Checks

Problem Definition:

ACME has its functional currency setup as CAD for their GP Company.  They have a Checkbook setup with USD as the Currency assigned.

They want to be able to use the “Miscellaneous Check” feature in the Financial Series to enter and print a physical USD check so they don’t have to create the Vendor in GP.

If you attempt to select the Checkbook in GP for a Non-Functional Currency Checkbook you get the below message and can’t use the Checkbook.

A screenshot of a computer Description automatically generated

Solution Overview:

This solution will modify the behavior of the Miscellaneous Check window to allow for creating checks in any currency.

Design Features:

Miscellaneous Check

Navigation: Financial >> Transactions >> Miscellaneous Check

The Miscellaneous Check window will be modified to enable Checkbook IDs that use non-functional currency IDs to be used. When one of these Checkbooks is selected, the window will behave as follows:

  1. The title bar will display the Currency ID being used on this check.
  2. ALL currencies displayed on the window will be in the Checkbook currency. In the example below, the $25 displayed and printed on the check, as well as the Credit/Debit in the scrolling window are ALL in USD (Checkbook Currency ID).

A screenshot of a computer Description automatically generated

Viewing Functional Amounts

Navigation: Miscellaneous Check >> Additional >> Functional Amounts

A screenshot of a computer Description automatically generated

(Sample screenshot from elsewhere in GP)

Field Function
Originating Displays the check amount
Functional Displays the amount in the company’s Functional Currency

Print Check and Post

When the Print Check and Post button, or Post button is clicked, the enhancement will first ensure there is a valid exchange rate for the Currency ID and Date. If one cannot be found, a warning will appear and the user cannot continue.

The printing of the check will not change. Since the amount entered is in the Checkbook Currency, it will be printed as displayed.

The posting of the check to the financial module will result in a recalculation of the functional amount based on the originating amount of the check and the assigned exchange rate for that date. The multicurrency information will be included in the document posting.

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 DS0448- Return Authorization

Customization DS0448

Return Authorization

Problem Definition:

ACME supplies flowers to retail outlets. Expired product is collected from the retail outlets and recorded on a Return Authorization (RA) form. The RA form is then used to create a Return in GP.

Entering the RA directly into GP as a return is problematic for a couple of reasons:

  1. There is not an item number on the products
  2. There is additional information on each RA line that is important to ACME for reporting purposes

To identify a specific item from the RA, the Vendor Code/Pull Date column can be used to identify a Vendor in GP. Cross-referencing the Vendor to recent sales invoices for the customer will provide a list of possible item numbers. The user will have to pick from the list of possible options.

The user who enters the RA will not be the same person who approves the RA and creates a Return in GP. The ability to enter the RA should be separate from the ability to approve and submit RAs.

Design Features:

Return Authorization Entry

The Return Authorization Entry (RAE) window will be used to enter the information from the paper RA so that it is captured in GP (in the database.)

Navigation: Transactions >> Sales >> RA Entry

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

Field Function
Credit # The user will start by entering the Credit Number from the RA form. This must be a unique number. It cannot exist as an open RA, (not yet submitted), as an open SOP Return, or as a posted SOP Return. An existing RA can be selected from the Lookup. (See RA Lookup below.)

If an existing Credit Number is entered, it will display the existing RA, or warn the user that the number already exists as a Sales Return. If the RA has already been submitted, it will open in the RA Inquiry window. (see below.)
Customer Number** User will enter the Customer Number, or select one from the Lookup.
Customer Name Displays the Customer Name
Return To Site** The GP Site that the return will be created into. Required field
Date Date from the RA
Store ID Store ID from the RA
Scrolling Window
The window will function like the Sales Transaction Entry window, where it displays one line, and if expanded, the one line becomes very large, filling the entire scrolling window.
Line Increments automatically. Not editable
Shrink Date Date from RA line
Shrink Code Drop-down list with these options:

  • CO (Company Decision)
  • DU (Double up)
  • PPD (Past Pull Date)
  • PQ (Poor Quality)
  • RI (Replacement Item)

NOTE: In the database, drop-down lists are stored as enumerated values.
Vendor Code Vendor Code/Pull Date appear as one field on the RA form. However, since the software needs to attempt to locate a Vendor ID in GP using the Vendor Code, the Vendor Code must be entered separately. The Vendor Code is stored in the Comment-1 field on Vendor Maintenance.
Pull Date A Julian Date code
UPC Code The UPC Code is a “price point” code, and does not tie to an Item Number in GP. This will be a 10 character string field.
Size 10 character string field. User enters the quantity returned
Fields in the Expanded Line view
Item Number** User enters the GP Item Number if known, or selects from the custom Lookup. See RA Item Lookup below.
Item Description When a GP Item Number is selected, the Item Description will populate. This field is editable and can be overridden by the user. This will flow through to the GP Return.
Vendor ID If the Vendor Code maps to a Vendor, and the system can locate that Vendor, this will fill in automatically.
Vendor Name Displays the Vendor Name.
Unit Cost If the Item Number was selected from the Lookup, it will have linked the RA line to the originating SOP Line, and the cost will pull in from the originating sales line. If an item number was manually entered this will display the Current Cost from Item Maintenance
Extended Cost Not editable. Displays Units Shrunk Unit Cost.
Unit Price If the RA line is linked to a SOP Line, this displays the Unit Price from the SOP Line. Otherwise this is zero.
Extended Price Not editable. Displays Units Shrunk Unit Price.
Unit of Measure** Defaults to the selected Item’s Base Unit of Measure. User can change it by entered a different (valid) UofM for the item, or selecting one from the Lookup.
Price Level** If the RA Line is liked to a SOP Line, this pulls in from the SOP Line. Otherwise it is the default Price Level assigned to the Customer, and if that is blank, the default Price Level assigned to the Item.

** Fields that are not required during RA entry, but must be completed before the RA can be submitted. See RA Submission below.

The expanded scrolling window:

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

RA Item Lookup

The RA Item Lookup is opened from the RAE window.

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

The window sorts by Date, then Item Number, so the most recent transactions appear at the top.

Field Function
Vendor ID If Vendor ID is empty on the RAE window, the lookup will show all items from “recent” sales invoices for the Customer for the last 30-days (by default).

If the Vendor ID is populated on the RAE window, the Lookup will show items from “recent” transactions for that Customer where the Primary Vendor for the items matches the Vendor ID. A different Vendor can be selected and the window will refresh to show items where that is the Primary Vendor, or it can be cleared to display all recent sales lines for that Customer.
Find Item Number The “Find Item Number” does a “contains” search on Item Number and Item Description for the string entered. As shown above, entering “GR” returns all items where the Item Number and/or Description contains “GR”.
Display Last By default, it shows last 30 days. Other options are 60 and 90.

Return Authorization Lookup

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

The RA Lookup shows existing documents in either the open (not submitted) or history tables. When opened from the RA Inquiry window the Open/History setting will match the selection on the RA Inquiry window.

Find Credit Number does a “contains” search on the Credit Number field.

RA Submission

The RA Submission window is used to select RA documents to submit as Returns.

Navigation: Transactions >> Sales >> RA Submission

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

Field Function
Mark/Unmark All Marks all Ras that are not currently being edited in RA Entry. Unmark All unmarks all selected documents.
Credit Number Zoom Zoom to the selected document in RA Entry.
Submit Asks the user to confirm they are ready to create Sales Returns, then executes the RA Submission Process.

RA Submission Process

The Submission Process will work like posting from one of the GP Series Post windows. You cannot mark an RA that is currently open in the RA Entry window, otherwise all RAs can be marked.

As the process attempts to create a SOP Return from each RA it will perform data validation on the document, report any errors, and only submit documents where data is complete and accurate. When the process is complete, the RA Submission window will redisplay. If any RAs had errors, they will still remain in the window. Submitted RAs will no longer appear in the window.

Error Conditions:

  • No Customer ID or Invalid Customer ID
  • No Return To Site or Invalid Return To Site
  • No Item Number or Invalid Item Number
  • No UofM or invalid UofM
  • Quantity Error. If the Quantity field contains a number that does not fit within the Item’s Quantity Decimals, it will be reported. For example, if the item is measured in LBS and has 1-decimal but the field shows 10.01 LBS, that is an error.
  • If linked to a SOP Line, the SOP Line reference is valid
    • The document exists
    • The line exists
    • The Document Customer matches the RA Customer
    • The line Item matches the RA line Item

An Error Report will print showing the Credit Number and a description of the error. Line level errors will reference the Credit Number and Line Number.

ACME’s long term plans include deploying a wireless, handheld, web-based user interface for RA Entry. At this time, the assumption is that application would feed data into the RA tables in GP and that the RA Submission window would be used to create Returns from the RAs. The data validation routine is intended to ensure the RA has the minimum amount of valid data needed to create a SOP Return.

An important aspect of entering the RA is selecting the Return Item Number. This builds a link between the RA Line and the originating Sales Invoice Line so that the system can pull the original Cost and Price. This information is not, however, required to actually create a return. The web-based application should provide the ability to create this link to an origination sales transaction, or, after importing the web-data into GP the RAs will need to be manually handled on a per-line basis to select the originating SOP Line.

All SOP Returns will be created in a Batch Named as follows: RA_RET_YYYYMMDD (that is 15-characters, which is the maximum size of the Batch ID field). The Credit Number will become the SOP Document Number.

An RA Submission Report will print showing the list of RAs turned into SOP Returns. The submitted RAs will be moved out of the open RA tables into a matching set of History RA tables.

Return Authorization Inquiry

Navigation: Inquiry >> Sales >> RA Inquiry

This is a view-only version of the RA Entry window.

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

The OPEN/HISTORY radio buttons allow the user to look at unsubmitted or submitted RAs, respectively.

Assumptions/Requirements:

  • Items must have a Default Site specified.
  • A Primary Vendor must be assigned to the Default Site for each Item.

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

www.willoware.com/contact-me/

 

MOGenerator 2025-02-21

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

Customization CR1532- Consolidated Customer Name

Customization CR1532

Consolidated Customer Name

Description of Need:

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

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

Description of Solution:

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

A screenshot of a computer Description automatically generated

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

Navigation: Cards >> Sales >> Customer

A screenshot of a computer Description automatically generated

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

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

A screenshot of a computer Description automatically generated

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

Assumptions/Requirements:

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

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

www.willoware.com/contact-me/

 

LeanMFG 2025-02-13

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

GPPowerPack 2025-02-11

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

Customization DS0978- Miscellaneous Charge Detail

Customization DS0978

Miscellaneous Charge Detail

Problem Definition:

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

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

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

Solution Overview:

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

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

Design Features:

Misc. Charge Setup

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

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

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

Field

Function

Item Number

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

Cost

Displays the Item’s Current Cost

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

Misc Charge Detail Entry

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

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

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

Field

Function

Item Number

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

Description

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

Cost

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

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

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

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

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

SOP Transfers & Posting

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

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

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

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

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

The Reference will be “SOP Misc Charge Detail”.

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

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

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

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

Printing

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

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

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

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

www.willoware.com/contact-me/

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

Customization DS1413

Auto-Create POs and link to Sales Orders

Problem Definition:

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

Solution Overview:

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

See the section below for details of the solution.

Design Features:

Creating POs from Sales Batch Entry

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

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

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

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

The enhancement will:

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

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

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

Assumptions/Requirements:

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

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

www.willoware.com/contact-me/

MOGenerator 2025-01-30

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

Customization DS1576- Minimum Order Fee

Customization DS1576

Minimum Order Fee

Problem Definition:

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

Design Features:

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

Minimum Order Setup

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

A screen shot of a order Description automatically generated

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

Sales Transaction Entry

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

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

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

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

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

Assumptions/Requirements:

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

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

www.willoware.com/contact-me/

 

 

Customization DS0927 Prevent Duplicate Lot Numbers

Customization DS0927

Prevent Duplicate Lot Numbers

Problem Definition:

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

Design Features:

Purchasing Lot Number Entry Controls

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

Or:

Automatically opens when Auto-Receiving a Lot Controlled Item

A screenshot of a computer Description automatically generated

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

Assumptions/Requirements:

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

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

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

www.willoware.com/contact-me/

 

MFG PowerPack 2025-01-15

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

CompleteCount 2024-12-30

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

 

LeanMFG 2024-12-17

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

MOGenerator 2024-12-12

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

GPPowerPack 2024-12-05

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

MFGPowerPack 2024-12-04

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

GPPowerPack 2024-12-01

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

MFGPowerPack 2024-11-25

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

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

A screenshot of a computer Description automatically generated

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

A screenshot of a computer Description automatically generated

MFG PowerPack Lead Time Utility

Price $1800 Manual

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

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

A screenshot of a computer Description automatically generated

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

A screenshot of a computer Description automatically generated

Calculate Manufacturing Lead Times

19-NOV-2024

Keywords: Mfg Fixed Lead Time, Mfg Variable Lead Time

Some quick facts:

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

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

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

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

AvgQty = Average Quantity

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

QNS = Qty Next Start

PNS = Percent Next Start

QT = Queue Time

ST = Setup Time

CT = Cycle Time

MT = Move Time

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

HPS = Hours Per Shift

NS = Number of Shifts

THE CALCULATIONS

PctComplete = 1

IF: QNS > 0 THEN PctComplete = PNS/AVGQty

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

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

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

IF: QNS > 0 THEN PctComplete = QNS/AVGQty

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

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

WCHours = HPS * NS

SetupAndQueue = (QT + ST) / WCHours

MoveAndCycle = (CT + MT) / WCHours

VARLeadTimeLine = MoveAndCycle * PctComplete

FixedLeadTime = FixedLeadTime + SetupAndQueue, rounded to 2 decimals

VariableLeadTime = VariableLeadTime + VarLeadTimeLine, rounded to 4 decimals

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

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

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

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

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

 

 

 

LeanMFG 2024-11-12

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

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

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

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

MFG Data Archive 2024-11-05

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

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

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

 

MOGenerator 2024-11-04

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

MFGPowerPack 2024-10-29

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

GP18.7 Updates Starting Today

Date: 28-OCT-2024

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

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

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

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