Author: admin

MOP-SOP Links and MO Receipts

Posted: 17-SEP-2022

Keywords: Dynamics GP Manufacturing, MOP-SOP Links, MO Receipt Entry

The issue discussed below applies to all current versions of Dynamics GP.  We released an update today for MFG PowerPack that has a new Tweak called “MO-SO Receipt Warning” that is intended to address the issue.

We recently discovered problem with Dynamics GP Manufacturing Order Receipt Entry window where it allows creating and posting an MO Receipt when the MO is linked to a SOP Document and that document is currently in use (i.e. open in Sales Transaction Entry).  Normally manufacturing will allocate the inventory to the linked SOP line, and update SOP Line quantities accordingly.

What happens is the following:

  • The finished good inventory correctly posts to the Inventory Module
  • The quantity is allocated in the Inventory Module (Manufacturing assumes that it will be updating the SOP Line to reflect the allocation)
  • Since the SOP Document is locked, Manufacturing cannot update the SOP Line
  • The SOP Line then cannot be manually allocated/fulfilled because it is still linked to the MO.
  • The inventory cannot be used because the Inventory Module sees it as allocated

The only way to address the situation is to (1) break the MOP-SOP link and (2) run inventory reconcile.  At that point the SOP Line can be manually allocated/fulfilled.

The new Tweak in MFG PowerPack hooks into an existing check performed by the MO Receipt Entry window and forces the warning below if the linked SOP Document is in use.

Graphical user interface, text Description automatically generated

The reason we took this approach is that there are 3rd Party products (such as Warehouse Management Systems) that integrate into this window to create MO Receipts.  Since the warning above, and the condition that creates it, is a normal behavior of the MO Receipt Entry window, our hope is that such integrations will already have a method to handle this warning.  Where if we had added an additional warning specific to the MOP-SOP condition, that might cause the 3rd Parties to fail.  If you do deploy this Tweak in a system that has an integration, please test carefully before enabling it in a live system.

MFG PowerPack 2022-09-16

Release Date: 16-SEP-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 11.202
* Actual Cost Rollup: changes to the stored procedures to correct a case sensitivity issue for binary sort databases (#202201726). If you are binary sort and received an install error, dr0p table WCT00003 then rerun the full install routine to automatically recreate the table and stored procedures. This issue affects binary sort SQL installs only.
* MO Split: addressed issue that could cause a duplicate key error on MOP10223 when doing MO Receipts with Split MOs (#202201737)
* Vendor Pricing: addressed issue in the PO Item Detail Entry window where it was not picking up changes to the Release By Date so it continued to use the Document Date for pricing. This build adds a feature to the Release By Date field so that when you enter it date it will automatically update the Required Date (if needed) so it is the same as the Release By Date. This prevents a warning from GP that the Required Date cannot be before the Release By Date, and it means you can enter only the Release By Date if desired.
* NEW Tweak: MO-SO Receipt Warning- this Tweak is intended to fix a big with the Manufacturing Order Receipt Entry window. If an MO is linked to an SO, and the SO is in use (i.e. open in Sales Transaction Entry), the MO Receipt window will allow creating and posting a receipt. This results in the finished good inventory being added to inventory and allocated (because manufacturing thinks it will be allocating the inventory to the SO). However, the SO is locked so it cannot be updated. The SO then cannot be manually fulfilled because it is linked to the MO, and the inventory module incorrectly shows the inventory as allocated so it cannot be used. The only way to fix the situation is to (1) break the MO-SO link and (2) run inventory reconcile. This Tweak will warning users that the MO is in use and prevent creating the MO Receipt.

DS0852 Sales Entry Enhancements

DS0852

Sales Entry Enhancements

Problem Description:

Drop-Ship

ACME brings Sales Orders into Dynamics GP via EDI. It is not known when the order is integrated whether or not it will be processed as a Drop-Ship. When ACME manually reviews Orders after integration, a decision is made that an Order should be a Drop-Ship.

Currently they are manually removing each sales line, and re-entering it as a Drop-Ship. A Sales Order is always either completely Drop-Ship, or not. There is never a mix of Drop-Ship lines and regular lines. If there were a mix, they would manually set each line as needed.

Additionally, the Shipping Method on each line is changed to DIRECT SHIP.

ACME would like a way to quickly convert an entire order to Drop-Ship, and change the Shipping Method to DIRECT SHIP.

Exceptional Demand

ACME uses Sales Demand in their Sales Forecasting and sometimes needs to exclude a Sales Order from forecasting. Currently this is done by manually marking the Exceptional Demand checkbox on the Sales Item Detail Entry window, for each line on the order.

ACME either excludes all lines from forecasting (marks the Exceptional Demand box on all lines), or all lines are included. There is never a mix of some lines excluded and some lines included. If there were a mix, they would manually set each line as needed.

ACME would like a way to quickly set the Exceptional Demand flag on all lines on a Sales Order (or to unmark it on all lines).

Design Features:

Drop-Ship

Navigation: Sales Transaction Entry >> Additional >> Convert to Drop-Ship

Conversion to Drop-Ship will only be allowed if the SOP Type = Order.

The user will be prompted to confirm they want to convert the entire Order to drop-ship. If they answer yes:

  1. The system will confirm that:

    1. multi-bins is NOT enabled
    2. the order does NOT contain serial/lot controlled items

If either is true, the user will be warned and the Convert to Drop Ship process will stop.

  1. Each line on the order will be converted to Drop-Ship.
  2. Inventory will be unallocated at the Item-Site.
  3. The Shipping Method will be changed to “DIRECT SHIP” and the user will be prompted to roll the change down to the lines.

Exceptional Demand

Navigation: Sales Transaction Entry >> Additional >> Toggle Exceptional Demand

Selecting the navigation above will have the follow effect on the Exceptional Demand checkboxes on the sales lines:

  • If none are currently marked, all will be marked
  • If some are currently marked, all will be unmarked
  • If all are currently marked, all will be unmarked

Since the Exceptional Demand checkbox is always available regardless of SOP Type, the Toggle Exceptional Demand optional will work on any SOP Type.

The Title Bar of the Sales Transaction Entry window will display the Exceptional Demand status.

When all of the lines on a Sales Transaction have the Exceptional Demand checkbox marked, “Exceptional Demand” will appear in the Title Bar of the Sales Transaction Entry window (as shown below).

If some of the lines are NOT marked (and some are), it will display: Exceptional Demand*

If none of the lines are marked, Exceptional Demand will not display.

The example below is just to emphasize the LOCATION of the text—it will NOT be red. It will appear in the same font/color as the title of the window.

Graphical user interface, application, Word Description automatically generated

Assumptions/Requirements:

ACME does not use Multi-Bin

ACME does not use Serial/Lot Tracking

MFGImport 2022-08-09

Release Date: 9-AUG-2022
GP Versions: 12/14/16/18
MFG Import Build: 3.54
* FULL INSTALLATION ROUTINE REQUIRED
* This build adds a new table for tracking errors in the integration
* Added support for table-driven integrations into the BOM and Routing.
* Added an external integration point (API) for use with GP web services and dexterity-based integrations.

GPPowerPack 2022-07-28

Release Date: 28-JUL-2022
GP Versions: 12/14/16/18
GP PowerPack Build: 5.159
* Bank Deposit Filters: addressed issue that could cause a very long delay when clicking the Mark All button when filters have been applied.
* TWK-POP: PURCH Distribution Override – added check for Inactive account. User will now be warned if the selected account is inactive and the window will revert to the previous account.

MFG PowerPack Actual Cost Rollup

Price $3600 Manual

The Standard Cost Maintenance windows in GP Manufacturing do not allow use of Actual Cost (FIFO/LIFO PERPETUAL) Items.  In an Actual Cost environment it is difficult to see what the total cost of production will be which in turn makes it difficult to produce Quotes or Estimates for customers.

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

The Actual Cost Rollup utility provides a place to set a pending cost change and date for actual cost raw materials, perform an Actual Cost Rollup, and view items that have a new cost because of the rollup.

Graphical user interface, table Description automatically generated

The Actual Cost Rollup follows the same logic as the GP Manufacturing Standard Cost Rollup, so the rollup includes:

  • Labor rates and overheads
  • Machine rates and overheads
  • Routing Times
  • Bills of Material Component Quantities and Shrinkage
  • Item Engineering Standard Cost Shrinkage
  • Item Resource Planning Shrinkage Factor
  • In dates/out dates/Effective Dates

Actual Cost Rollup also works with Standard Cost items and can perform a risk-free roll-up on those items too.  Since Actual Cost Rollup does not have the ability to CHANGE the cost of standard cost items it can be used to perform planning activities without the chance of accidentally revaluing inventory.

MFG PowerPack 2022-06-30

Release Date: 30-JUN-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 11.200
* The FULL INSTALLATION ROUTINE is required with this release
* Item Copy: changed timing of when wspItemCopyPost is executed from after each node to once per Destination Item Number.
* Proposed Cost Update: address issue with the Zero Cost flags that caused it to not allow Material to be zeroed (#202201210)
* Update to Scrap UDF Labels to allow more fields in a future release
* NEW: Actual Cost Rollup- this utility performs a cost rollup on actual cost (and standard cost) inventory items.

MFG PowerPack 2022-06-22

Release Date: 22-JUN-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 10.199
* Vendor Pricing: added UDFs fields to the Excel import (#202201152)
* MFG Tweak: Use MO Number for IV Transaction Number- added check for blank MO Number so if retreiving the MO Number fails during posting GP will revert to using the default IV Transaction Number (#202201146)

Engineer To Order (ETO) 2022-06-21

Release Date: 21-JUN-2022
GP Versions: 12/14/16/18
ETO Build: 2.40
* Copy Utility: (1) Fixed issue in the Copy utility that caused it to not copy the routing if the BOM ID and Routing ID were different (#202201188), (2) Fixed issue that prevented copying if source BOM from the MFG Module was created without a Fixed Qty UofM

MFG PowerPack 2022-06-02

Release Date: 2-JUN-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 10.198
* Vendor Pricing: fixed issue that zeroed the price with Manufacturing and Outsourced Routing Sequences when Manufacturing is configured to create the PO Item on the fly using the MO and Routing Sequence (#202201048)
* Quick Disassembly: added an option to merge quantities for the same item if an item number can appear multiple times on a BOM or Picklist.

GPPowerPack 2022-06-01

Release Date: 1-JUN-2022
GP Versions: 12/14/16/18
GP PowerPack Build: 5.157
* Login Controls: Addressed issue with the Set Company control that caused an error (Illegal address for field User ID) in some installations when Remember Company was marked
* SOP Tweaks (Customer PO-Check For Duplicates, Customer PO-Require Unique): A new setup option allows choosing which type of window is used for the SOP Customer PO Inquiry, either modeless or modal. Modeless is a normal GP window that can stay open when using other windows. Modal is like a warning dialog box–you must close it before you can interact with another window.

Customization DS1360 MO Receipt: Import Finished Good Lots

Customization DS1360

MO Receipt: Import Finished Good Lots

Problem Definition:

ACME produces bales of non-wood ag-based fiber using Microsoft Dynamics GP Manufacturing to record the manufacturing activities. Each Manufacturing Order can produce 30-50 bales, each of which is recorded with a separate lot number and weight (the finished good quantity).

They are currently set up with multi-bin turned on, the finished items are lot tracked and many of the components are lot tracked. They backflush the components. Currently they need to manually enter 30-50 separate lots numbers and the quantity (weight) for each lot. They are not recording any lot attributes.

ACME would like to improve the speed and ease of data entry by having a way to copy (or import) the Lots/Quantities from Excel into the MO Receipt.

Solution Overview:

WilloWare will add a custom Copy/Paste window into the MO Receipt Entry process where users can copy/past a list of finished good Lot Numbers (bales) and the quantity (weight) for each bale.

Design Features:

Lot Number Import

Copy the finished good lot numbers and quantities from Excel. The data must be in two adjacent columns as shown below.

Table Description automatically generated

Navigation: Manufacturing Lot Number Entry >> Additional >> Lot Number Import

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

Paste (CTRL+V) the lots/quantities into the Lot Number Import window as shown above.

Click the IMPORT button.

The import process will first make sure that a BIN has been provided. If not, it will stop and ask the user to enter a BIN. It will then add the list of Lot Numbers and Quantities to the “Lot Numbers Selected” window.

NOTE: if the total of the copy/pasted Lot Quantities is greater than the Quantity Remaining To Select, the import routine will stop when the next lot quantity to import would exceed the Remaining To Select. For example, if the Quantity Remaining To Select is 2 and the next Lot Number to import has a quantity of 12.30, the utility will not attempt to import it.

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 customization, or any other WilloWare customization or product, please contact us:

//willoware.com/contact-me/

Customization CR1407- ITT Visibility to MRP

Customization

CR1407

ITT Visibility to MRP

Description of Need:

ACME uses Dynamics GP Manufacturing.

They need to have full visibility to inventory balances, supply/demand and movements throughout the system. They use In-Transit Transfer documents.

In-Transit Transfer documents are not visible to MRP. ACME requires an enhancement that will provide them with visibility to both the demand and supply requirements of unshipped and/or unreceived ITT’s.

Description of Solution:

In-Transit Transfers: Visible to MRP

Please Note: The Regeneration Type must be set to Full Regeneration on the MRP Regeneration window. The enhancement will NOT function properly if this setting is changed to Net Change.

Graphical user interface, text, application Description automatically generated

The user must manually click the PROCESS button on the MRP Regeneration window to run MRP. Clicking the PROCESS button will run the following processes prior to the MRP Regeneration process. The processes described below create/maintain “bogus” planning documents that make ITT supply/demand visible to MRP:

  1. Review unshipped quantities on In-Transit Transfer (ITT) documents to mimic DEMAND. In the ITT example below, there are 25 pieces of item MRP TEST, which have been entered on the ITT document to be supplied from Site QUALITY and shipped to Site NORTH via the INTRANSIT Site. This quantity has NOT yet been shipped.

Graphical user interface, application, table Description automatically generated

Even though the 25 pieces are allocated to the ITT document, they still show as being available to site Quality as viewed through the MRP Workbench:

Graphical user interface, table Description automatically generated

To simulate demand, the enhancement will create a dummy Manufacturing Order and Picklist. The Manufacturing Order number will be set to Z-INTRANSIT. The Manufacturing Order Item Number will be set to INTRANSIT. The Routing will be set to INTRANSIT. (This Item does not need to be an Item in the Item Master. This Item does not need to have a MFG BOM or MFG Routing assigned.) The Manufacturing Order will be set to status OPEN and its PICKLIST will be built.

The Manufacturing PICKLIST will contain the unshipped ITT requirements. Each required Item Number/Site combination will appear as a single line item on the PICKLIST. The sum of the requirements for each Item Number will populate the Required Qty field. The PICKLIST Items/Quantities will NOT be allocated. The PICKLIST Required Date will be set to the System Date. The PICKLIST Items/Quantities will be set to Backflush. The ISSUE FROM Site on the PICKLIST will be set to the ITT’s From Site ID. In the example above, because the ITT has not yet been shipped, the ISSUE FROM Site would be set to QUALITY.

  1. Review shipped quantities on In-Transit Transfer (ITT) documents to mimic DEMAND. In the ITT example below, there are 25 pieces of item MRP TEST, which have been entered on the ITT document to be supplied from Site QUALITY and shipped to Site NORTH via the INTRANSIT Site. This quantity HAS BEEN shipped.

Graphical user interface, application Description automatically generated

Even though the 25 pieces are allocated to the INTRANSIT Site from the ITT document, they still show as being available to site INTRANSIT as viewed through the MRP Workbench:

Table Description automatically generated

The enhancement will add these demand lines to the Manufacturing Picklist as described in #1 above. However, for shipped lines the following alteration will be made:

  • The ISSUE FROM Site on the PICKLIST will be set to the VIA SITE ID. In the example above, because the ITT has been shipped, the ISSUE FROM Site would be set to INTRANSIT.
  1. Review shipped and unshipped quantities on In-Transit Transfer (ITT) documents to mimic SUPPLY. In the ITT example below, there are 25 pieces of item MRP TEST, which have been entered on the ITT document to be supplied from Site QUALITY and shipped to Site NORTH via the INTRANSIT Site. This quantity has NOT yet been shipped.

Graphical user interface, application Description automatically generated

These 25 pieces are NOT visible as supply to Site ID North as viewed through the MRP Workbench.

Table Description automatically generated

Even when the ITT document has been shipped, MRP still does NOT recognize the supply coming to the final destination Site ID. To simulate supply, the enhancement will create a dummy Purchase Order which will include both shipped and unshipped ITT quantities. The Purchase Order number will be set to Z-INTRANSIT. The Purchase Order will hold the following detail:

  • Purchase Order Date: Will be set to the System Date
  • Vendor ID: INTERNAL. (The enhancement will NOT validate that this Vendor ID exists. It is the responsibility of ACME to ensure that the Vendor ID is setup within Dynamics GP.)
  • Currency ID: Company’s Functional Currency
  • PO Status: RELEASED

The PO Lines will contain the following detail:

  • Item Number: Item Number from the ITT Record
  • Quantity: (Qty Ordered – Qty Received)
  • U of M: UOM from the Requisition record
  • Unit Cost: $0.00
  • Site ID: To Site from the ITT record
  • Required Date: Promised Date of the ITT Document
  • Current Promised Date: Promised Date of the ITT Document
  • PO Line Status: Set to RELEASED
  • Vendor Item Description: Tracking Reference of the ITT Document
  • Ship Method: Ship Method of the ITT Document

Please Note: If the Item Number/Vendor ID assignment does not already exist, the enhancement will auto-create the link.

Internal ACME Process Controls Are Required:

  1. Users should NOT allocate parts, issue parts, receive or close the Z-INTRANSIT Manufacturing Order. The Manufacturing Order should NOT be utilized in actual Manufacturing Processes. The enhancement will NOT prevent users from doing any of the above.
  2. Users should NOT copy, receive, cancel, delete, void, print, invoice or close etc. the Z-INTRANSIT Purchase Order. The Purchase Order should NOT be utilized in actual Purchasing transactions. The enhancement will NOT prevent users from doing any of the above.

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
  • Extended Pricing

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

//willoware.com/contact-me/

CompleteCount 2022-03-30

Release Date: 30-MAR-2022
GP Versions: 12/14/16/18
CompleteCount Build: 3.53
* Submit Stock Tags: addressed issue the in Lot Number Over Allocation routine that was incorrectly identifying the over-allocated lot number when multiple lots for an Item exist in one Bin.
* Excel Link: addressed issue that could leave a stranded background Excel process that locks an import file.

MO Generator 2022-02-09

Release Date: 9-FEB-2022
GP Versions: 12/14/16/18
MOGenerator Build: 3.106
* MOGen Core Utilities: (1) NEW-A custom “selection query” can be created to only pick certain records to process. For example, when running two processors each can have a query that pulls a different range of item numbers so there is no chance they can overlap. The query can also be used to allow an integration to “stage” records that are incomplete and have them processed only when certain criteria are met. (2) Addressed issue where the Reschedule MO utility, and MOGenV2 RescheduleMO with RebuildPicklist=false, would reschedule the MO and routing but not update the Required Date on the picklist lines with the new MO Start Date.

Customization DS1150 PO Release Utility

Customization DS1150

PO Release Utility

Problem Definition:

ACME uses Dynamics GP with Nolan’s Intercompany POP-SOP module. Currently they automatically create PO’s which then need to be manually printed, which Releases the PO and triggers Nolan’s POP-SOP to create a Sales Order.

ACME would like to eliminate the time-consuming process of manually printing/releasing PO’s. They would like an automated utility that Releases PO’s and triggers the Nolan software.

Solution Overview:

WilloWare will create a utility that can be run un-attended (using a GP client) that will automatically Release Purchase Orders.

PO Release Utility:

Navigation: Tools >> Utilities >> Purchasing >> PO Release Utility

The PO Release Utility directly “releases” a New Purchase Order without printing the PO.

Field

Function

Run Continuously

In this mode, the utility will keep running until the STOP button is clicked

Run For/Hours

Enter the number of Hours. In this mode, once START is clicked, the utility will run for the specified number of hours, then stop and close GP.

PO Selection Query

The PO Release Utility will use the PO Selection Query to identify the next PO to release. The Utility will be hard-coded to only select PO Status = NEW (POSTATUS=1), so the Selection Query provides additional restrictions.

The Selection Query is free-text entry box and should only contain PO Header fields (POP10100). No check will be performed to control this, but inclusion of other tables/fields will cause an error when START is clicked.

When multiple PO’s are returned by the query, the Utility will take them in order by DEX_ROW_ID. This ensures that the oldest are processed first. Also, the Utility will check the DEX_LOCK table and skip a PO if it is in use.

See this link for information about setting up Windows Scheduler to run GP and the PO Release Utility automatically:

//willoware.com/scheduling-mogenerator/

NOTE: For the PO Release Utility to work correctly, Nolan must be configured to print the NC_IOP_Audit_Trail_Report to file.

Assumptions/Requirements:

  1. The functionality described above is intended for the GP Desktop client.
  2. Reporting is not included in this estimate.

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

www.willoware.com/contact-me/

MFG PowerPack 2021-12-15

Release Date: 15-DEC-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 10.189
* THIS BUILD CREATES A NEW SQL STORED PROCEDURE. FULL INSTALLATION ROUTINE REQUIRED FOR THIS BUILD
* Vendor Pricing: (1) Added a new costing method called Custom. This calls a stored procedure (wspVendorPricingGetPrice) where you can add whatever custom pricing logic is needed for an Item. Custom Pricing can be used as the Primary or Secondary pricing method. (2) Vendor Pricing now works with the SOP Purchase Order Preview window.

MO Generator 2021-12-01

Release Date: 1-DEC-2021
GP Versions: 12/14/16/18
MOGenerator Build: 3.105
* Exclude Items Window: Addressed issue caused by a change to the Item Master (IV00101) in GP18.3. In that build (and after) the Item Master now contains a User ID column, which after the upgrade is blank. User ID is set automatically when a Item record is changed to the User ID that made the change. When the Exclude Items window retrieved an Item Number it was also pulling in the blank User ID, which wiped out the User ID already set on the line. The window now ensures that User ID has been reset to the correct value after retrieving them Item record (#202101955).

MFG Import 2021-11-03

Release Date: 3-NOV-2021
GP Versions: 12/14/16/18
MFG Import Build: 2.52
* Added checks for blank records in tables linked-to and populated by the import. This was added as a safeguard to address the following scenario: a client had a blank record in IV00101 (perhaps from a go-live data import) which caused the import utility to link from a blank Template Item Number (blank because it was not being used) to the blank record in the Item Master, which then caused multiple data validation steps to fail and BOM Import would not run. The checks will run before the BOM Import and Routing Import windows open and will warn the user if there are any blanks, and provide instructions on how to fix the problem.

GP18.4 Releases Ready

All of our software is now ready for GP18.4!

We wanted to take this occasion to share with you our thoughts on the 18.x releases.  While this new numbering approach gives the impression that each new “DOT” build (18.2, 18.3, 18.4) is just a “service pack”, this is not the case, and it is not how we treat them.

In short, we treat them as MAJOR releases (like going from GP2016 to GP2018).  Between each DOT release there can be major changes that affect integrating products, such as:

  • New tables in the SQL database
  • New columns added to existing tables
  • Changes to the sort order of Keys on tables
  • New parameters in existing Procedures and Functions (dexterity code)

All of the potential changes mean that integrating software needs to be tested on the latest release of Dynamics GP.

On the topic of software releases, we received a support question recently looking for an explanation of how our build numbers work.  We recently changed our software build numbering logic so that regardless of the GP Major Version (i.e. GP2013, GP2015, GP18.4, and so on), a release of one of our products has the same “core” build number.

For example, MFG PowerPack has the current build numbers:

  • For GP2013:  12.9.186
  • For GP2014:  15.9.186
  • For GP2016:  16.9.186
  • For GP2018:  18.9.186

The first number is the Major Version, and that must match the GP version you are installing into.  For example, if you are on GP2016 you have to install a 16.x.y build of our software.

We think of the next two numbers as the “Internal Major” and “Internal Minor” build numbers, in the example above “9.186”.

The Internal Major number only changes if we need to make changes to the SQL database, such as change a table, adding a table, or creating a stored procedure.  For example, if the internal build changes from “9.186” to “10.187” it means that the new release has changes to the SQL database and the full installation routine needs to be run as “SA” with no users in the system.  If the internal build changes from “9.186” to “9.187” it means that it is a CODE-ONLY change and the new code (the CNK) can be dropped onto the GP client and you will NOT have to run an installation routine after logging in.

Prior to making this change to our release numbers, as each product was upgraded for a new release of GP we would start the build numbering over again.  For example, the first build of MFG PowerPack after upgrading it to GP2018 would be 18.0.1.

We felt this was confusing because MFG PowerPack is actually the SAME code on GP2013 all the way through GP18.4.  We build logic into the software so it knows what version of GP it is on, and what is different about that version of GP, and it changes accordingly.  For example, GP18.4 has new User Defined Fields on GL Transactions that were not present in GP2013.  If MFG PowerPack needs to create a Journal Entry, it checks to see what version of GP it is running in, and then runs the correct “create journal entry line” routine for GP2013 or GP18.4 (one without user defined fields, and one with user defined fields).

We felt that carrying the same internal build number over ALL supported versions of Dynamics GP better reflected the fact that the functionality you get from our product is IDENTICAL across all supported versions of GP.  This is the benefit you receive from WilloWare of staying current on software maintenance–even if you do not upgrade GP you are still getting the latest functionality from WilloWare.

Happy Upgrading!

MFG PowerPack 2021-10-28

Release Date: 28-OCT-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 9.186
* Updated for GP18.4 Release
* Proposed Cost Update: Added fields in the Excel import template to support setting the “Set To Zero” checkbox on the Standard Cost Changes window when importing new proposed costs.
* PowerATP: fixed issue in Free Forward calculation that was retrieving the correct date but incorrect quantity.

Customization CR0701 MO Number Creation Update

CR0701

MO Number Creation Update

Description of Need:

Currently, the MO Number that is auto-generated from the Sales Order is created as SOPNUMBE_LNITMSEQ. ACME would like the MO Number to also include a prefix which will represent the Site which is entered into the Sales Order Document header.

Description of Solution:

Navigation: Setup > Manufacturing > Site Prefix Setup

This window is used to define a Prefix for each Site ID used in the Sales Order to MO creation process.

C:\Users\Karen\Documents\Clients\Tribridge\ABS\Site Prefix Setup.jpg

Field

Function

Done Button

Click the DONE button to exit the window

Site ID

Enter or select a Site ID from the lookup

Prefix

Enter a one character Prefix to represent the Site ID. A Number or Letter may be entered.

When an MO is created by the enhancement, the MO number will be generated in the following manner:

  • If the Sales Document Header’s Site ID is listed in the Site Prefix Setup window, the first character of the MO will be the Site’s Prefix.
  • If the Site ID is NOT listed in the Site Prefix Setup window, a prefix will NOT be added.

The balance of the MO number will remain as is: SOPNUMBE_LNITMSEQ.

Example #1

Site ID NORTH has a Site Prefix of “1”

Sales Order ORD00012 has 2 Sales Lines entered. Each Sales Line will generate an MO.

Two MO’s will be created:

  1. 1ORD00012_16384
  2. 1ORD00012_32768

Example #2

Site ID WEST has a Site Prefix of “A”

Sales Order ORD00013 has 2 Sales Lines entered. Each Sales Line will generate an MO.

Two MO’s will be created:

  1. AORD00013_16384
  2. AORD00013_32768

Example #3

Site ID EAST does NOT have a Site Prefix set in the Site Prefix Setup window.

Sales Order ORD00014 has 2 Sales Lines entered. Each Sales Line will generate an MO.

Two MO’s will be created:

  1. ORD00014_16384
  2. ORD00014_32768

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

//willoware.com/contact-me/

GP PowerPack 2021-10-04

Release Date: 19-OCT-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.155
* NEW TWEAK: Open IRP with Item’s Default Site – if a Default Site ID is assigned to an Item in Item Quantities Maintenance, when the Item is displayed in Item Resource Planning the window will automatically show information for the Item’s Default Site ID.
* SOP Rules: Secure Batch by User ID: Added additional controls to ensure “restricted” Batches do not become locked in batch activity by users who do not have access

MFG PowerPack 2021-10-18

Release Date: 18-OCT-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 9.185
* NEW TWEAK: POGen Integration- PO Generator suggests purchase orders based on quantities in the Item Quantities Master table.  However, there are modules, such as GP Manufacturing and Field Service, that create transactions which do not update the Item Quantities until after the transaction posts (for example, unallocated Manufacturing Picklists or unreceived Inter-Site Transfers).  PO Gen Integration can pull additional sources of inventory supply and demand into the PO Gen calculation to arrive at more accurate purchasing suggestions.
* Company Switching: addressed an issue that prevented the software from correctly enabling MFGPP options based on company settings when switching companies.
* FULL INSTALLATION ROUTINE REQUIRED FOR THIS BUILD

MFG PowerPack 2021-10-06

Release Date: 6-OCT-2021
GP Versions: 12/14/16/18
MFG PowerPack Build: 8.183
* Serial Mass Entry: Added mass serial number load into IV Transfer and IV Adjustment rather than automated adding through the UI. This process had been causing the list views to refresh after each addition which caused significant time delays when there are a large number of available serials.
* Vendor Pricing Import: addressed issue that caused date to offset forward by one day

GP PowerPack 2021-10-04

Release Date: 4-OCT-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.154
* SOP Rules: Secure Batch by User ID: (1) Changed trigger point to prevent unauthorized users from locking a batch if they attempt to open one they do not have access to. (2) Added a routine to clear batch activity if user scrolls through documents and reaches one that is assigned to a batch to which they do not have access

GP PowerPack 2021-09-30

Release Date: 30-SEP-2021
GP Versions: 12/14/16/18
GP PowerPack Build: 5.153
* Bin-to-Bin Transfers: (1) Added controls to From Site to prevent changing it after a Bin-to-Bin Transfer has been started (i.e. a transaction can only be for one Site, it cannot be used to to bin-to-bin transfers for multiple sites at the same time). (2) Added a warning in Setup to alert user if they attempt to enable Bin-to-Bin Transfers when the Inventory Multi-bin functionality is disabled.
* SOP Rules: Secure Batch by User ID: (1) addressed issue that prevented the Rule from allowing access to a secure batch when multiple users are assigned to the same batch.

Customization DS0798: SOP Display Customer-Friendly Description

Customization DS0798

SOP Display Customer-Friendly Description

Description of Need:

ACME utilizes Dynamics GP to enter its Sales Documents. They would like to provide their Sales team with an alternate, more customer-friendly, Item Description during Order Entry.

The customer-friendly Item Description is held in the Customer-Item Maintenance window. A default Customer ID “999999” is used to store all customer-friendly Item Descriptions.

ACME requires this Item Description to display in the Sales Transaction Entry window’s toolbar during Sales Document Entry. The full Customer Item Description of 51 characters must display.

Description of Solution:

Navigation > Transactions > Sales > Sales Transaction Entry

The Sales Transaction Entry window will be updated to display the customer-friendly Item Description in the toolbar. This will look similar to the “Ship Weight” verbiage displayed below:

The customer-friendly Item Description will display during Sales Document entry when the user tabs out of the Item Number field. It will also display if an existing Sales Line is selected.

The customer-friendly Item Description from Customer ID “999999” will display, regardless of the Customer ID entered on the Sales Document. If an Item-Customer Link does not exist for Customer ID “999999”, no Item Description will display in the toolbar.

Please Note: The Toolbar can display up to 78 characters; there for displaying the full Customer Item Description of 51 characters is achievable.

Assumptions/Requirements

The functionality described above is intended for the GP Desktop client.

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

www.willoware.com/contact-me