MFGImport 2023-05-24

Release Date: 24-MAY-2023
GP Versions: 12/14/16/18
MFG Import Build: 3.66
* Routing Import: (1) added Excel file zoom button, (2) fixed issue with importing notes where some non-alphanumeric characters were stripped from the note (3) Now display “Done” or “Error” at end of process in the Status Message box
* BOM Import: (1) added Excel file zoom button, (2) Now display “Done” or “Error” at end of process in the Status Message box

GP Manufacturing Prevents Deleting Item-Site or Site

Keywords: Manufacturing, Item Delete, Item-Site Delete, Site Delete

You may have tried to clean up data in GP and were prevented from removing an unused or obsolete Item, Item-Site or Site because of a warning message from Dynamics GP Manufacturing such as:

“This site is used in Manufacturing, and can’t be deleted.”

“This item is a component on one or more bills of material. It can’t be deleted until you remove it from those bills of materials.”

If you are trying to remove an Item-Site record, in addition to controls from the Inventory Module (such as there cannot be inventory quantities of the Item), the Manufacturing Module can prevent the delete.

If you are trying to delete an Item-Site, the Manufacturing Module checks the following tables:

  • Work Orders (WO010032)-all MO Statuses except Hold/Canceled, those are ignored, which means the Item-Site combination can be on an MO if the Status is Hold or Canceled.
  • Picklists (PK010033)-unless the MO is Hold/Canceled.
  • BOM Lines (BM010115)
  • Pick Doc Line (MOP1210)-unless the MO is Hold/Canceled.

 

If you are trying to delete a Site, in addition to the tables above, it also checks:

  • Sales Preferences (ISSP0201)
  • Scheduling Preferences (SP010016)
  • MPS Lines (MF010130)
  • QA Preferences (QAPS0032)

 

Deleting an Item checks the following:

  • Work Orders (WO010032)-all MO Statuses
  • Picklists (PK010033)- all MO Statuses
  • BOM Lines (BM010115) – parent or child item

 

A significant hurdle to removing an Item-Site or Site is the fact that Complete and Closed Manufacturing transactions exist that have the Item-Site or Site.

MFG Data Archive can move historical manufacturing data to an archive company database and REMOVE those same records from the live company.  The complete list of tables covered by MFG Data Archive is available at the link below.

Archived Tables (willoware.com)

Additional benefits of archiving data are:

  • Faster lookups
  • Faster reports
  • Faster posting
  • Faster backups

Read more about MFG Data Archive here.

 

MOGenerator 2023-05-19

Release Date: 19-MAY-2023
GP Versions: 12/14/16/18
MOGenerator Build: 4.122
* MOGenV2: Changed timing of when MOP-SOP links are created so that it occurs immediately after adding a record to WO010032. This ensures that the MO is linked to the SOP Line even if other steps in creating the MO fail (such as building the picklist) (#202300681)
* Updated MOP-SOP link routine to subtract Qty Received on MO from the Available Qty To Link

Customization DS0835 Return Item Number Swap

Customization DS0835

Return Item Number Swap

Problem Definition:

ACME has a Salesforce.com integration into GP.  When a piece of equipment is pulled from a customer‘s home and returned, it is currently coming back into the system as the same Item Number used when it was sold.  This causes it to come back in with the cost associated with the original Item Number.  ACME needs to change the Item Number to a “Refurbished” Item Number, which has no cost (or a lesser cost). 

The sales Return makes use of Quantity Types (i.e. On Hand, Returned, Damaged, etc).  Only when the line is returning the quantity to the DAMAGED Quantity Type should the item number be swapped to the Refurbished Item. 


A screenshot of a computer

Description automatically generated with medium confidence

Each sales line will return inventory to only ONE of the available Quantity Types (i.e. the entire returned quantity will be in either On Hand, or Damaged, but not split between both). 

At some point after the Salesforce.com integration creates Sales Returns (Sales Transaction Entry), ACME needs a way to swap the Item Number on the Returns to “Refurbished” Item Numbers, and recalculate the documents.

Solution Overview:

The Refurbished Item Number will be stored as “Substitute Item 1” on the Item Maintenance Options window. 

A utility will be added to GP which a user can run to process all open (unposted) Sales Returns.  The utility will swap the Item Number to its Substitute Item, only when the Return Quantity is in the Damaged Quantity Type, update the Item’s Cost on the SOP line with the Cost from the Item Maintenance window, and recalculate the document. 

Design Features:

Recording Refurbished Item Numbers:

If an Item Number has a “Refurbished” Item Number, it will be stored in the Substitute Item 1 field, as shown below. 

A screenshot of a computer

Description automatically generated

Refurbished Item Utility:

Navigation: Tools >> Utilities >> Sales >> Refurb Item Update 

A screenshot of a system update

Description automatically generated with medium confidence

When the PROCESS button is clicked, the user will be asked:

“This utility changes Item Numbers to Refurbished Item Numbers 

On all unposted Sales Returns.  Continue?” 

If the user answers YES, the utility will: 

  1. Retrieve a list of all unposted Sales Returns.  For each Return: 
  2. Check if the document is currently open by another user.  If so, it will be reported on an Error Log at the end of the process.  If a document is open by another user, it cannot be updated, and will be skipped by the utility. 
  3. For each line on the return, it will check if the Returned Quantity is in the Damaged Quantity Type, and that the Item Number has a Refurbished Item Number in “Substitute Item 1”.  If so it will confirm that Refurbished Item 
  4. Has the same Unit of Measure Schedule 
  5. Has the same Quantity Decimals 
  6. Has the same Currency Decimals 
  7. Is assigned to the Site ID assigned to the Sales Line 
  8. Has the Price Level assigned on the Sales Line in its Price List 
  9. The Refurbished Item has a “Damaged” GL Account on Item Account Maintenance. 
  10. If any of the validations fail in Step #3, that Item Number will NOT be swapped.  It will be reported on the Error Log at the end of the process.  This will not prevent other lines on the same Return from being swapped. 
  11. If the validations pass in Step #3, the Item Number will be changed.  This will have the same effect as if the original Item Number had been deleted from the document, and the Refurbished Item Number added to the document using the same Quantity.  However, the Unit Price of the original Item will remain on the Sales Line. 
  12. The document totals and distributions will be recalculated. 

As documents are being processed, the Status Message at the bottom of the window will display the current document number. 

 

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

www.willoware.com/contact-me/

MOGenerator 2023-05-10

Release Date: 10-MAY-2023
GP Versions: 12/14/16/18
MOGenerator Build: 4.121
* MORI Excel: fixed issue where it was not automatically setting the ImportBOM/ImportRoute flags when the file contained multiple receipts of the same MO (#202300630)

Prorate Setup Time

Keywords: Prorate Setup Time, Prorate Quantity, Standard Cost (FIFO/LIFO Periodic), Actual Cost (FIFO/LIFO Perpetual), Backflush

Summary

When Prorate Setup Time is marked and Setup Labor is backflushed, the MO Receipt applies an incorrect amount of Setup Cost to each piece.

Overview

The online help for Costing Preference Defaults has the following to say about Prorate Setup Time:

Prorate Setup Time

Mark to distribute setup costs for standard cost items, and then select the quantity to use for calculating setup costs for standard cost items.

    • Average Quantity – The setup costs of an item (setup time multiplied by setup labor rate) will be divided by the average quantity of the item. You specify the average quantity of an item in the Item Engineering Data window. 
    • Standard Quantity – The setup costs of an item will be divided by the standard quantity of the item. You specify the standard item quantity in the Standard Cost Changes window. 

Standard Quantity can only be set on the Standard Cost Changes window, so it necessarily can only be used for Standard Cost items.  Average Quantity is set on the Item Engineering window.

The documentation for the Standard Cost Changes window says this about Standard Quantity:

If the item is a finished good, enter a standard quantity for finished good. When you set up preferences for how setup time is prorated for standard cost items, you can choose to use either the average quantity or the standard quantity.

And the documentation for the Item Engineering window says this about Average Quantity:

Optional. The Average Quantity is the default manufacturing order quantity, and is used in calculations if setup costs of standard cost items are prorated by the average quantity.

The only other reference to Setup Costs is on the MO Receipt Entry window.

Use all remaining setup costs

Mark this option to apply all remaining labor and machine setup costs – regardless of whether the labor and machine costs are marked to backflush or not – to the manufacturing order receipt. Setup costs that were previously applied to posted receipts will be deducted from the total setup costs for the manufacturing order. The default setting was set up in the Manufacturing Order Preference Defaults window, but you can change it when entering a manufacturing order. This option is not available if you are reversing a manufacturing order receipt.

Does all of this sound like the Prorate Setup Costs setting, and Standard/Average Quantity, only impact Standard Cost Rollup/Revaluation?

These settings also impact cost CONSUMPTION when backflushing, which with Actual Costing can significantly under-cost the finished good.  With Standard Cost it can result in a Variance.

Example

NOTE: everything below ONLY occurs if the Prorate Setup Time checkbox is marked.

CHAIR-ACTUAL is an actual cost item.  Item Engineering has Average Quantity of 20.

The Routing has one sequence with 1-hour of Setup and 1-hour per piece of Labor Time.  The Labor Cost for both Labor Codes is $40/hour.  Auto-Backflush Labor is marked.

We’ve created an MO for 24 and received one piece.  The Production Costs Labor field is $1000, which is correct.

  • Setup: 1 hour * $40/hour = $40
  • Labor: 24 pieces * 1 hour * $40/hour = $960
  • Total: $40 + $960 = $1000

We’ve received one piece and backflushed labor for $40.08.

  • Setup: We would expect to consume 1/24th of the Setup Cost.  This is one hour of Setup Cost divided by the End Quantity on the MO.  This should be $1.66667
  • Labor: We made one piece, which should take one hour, so this should be $40.
  • Total Labor should be $41.66667 not $40.08.

What is actually happening is the Prorate Setup setting and the Average Quantity are causing the MO Receipt to consume 1/20th of the Setup Cost per piece (remember the Average Quantity setting above?).

  • Setup: (1 hour * $40/hour) / 20 = $2.  So, our starting point for consuming Setup Time is $2 instead of $40.  Manufacturing then takes 1/24th of that (it divides by the MO End Quantity), which results in $0.08333 per piece.
  • Labor: this calculation is correct, which adds $40 in labor.
  • Total: $0.08333 + $40 = $40.08 (rounded to 2-decimals).

The MO Variance screen now shows the numbers after received 23 of 24 pieces.  The total labor consumed is now $921.91, which is 23  * $40.08333.

When we receive the final piece, we will have either (1) undervalued the actual cost inventory, or (2) created a cost variance with standard cost inventory.

Standard Cost

This is the MO Variance for an MO for 24 of CHAIR (standard cost item).  The Routing has the same setup described above.  Note that the Cost Put into WIP ($42) is not what we’d expect (and it is different than what happened with the actual cost item).  In this case it is used 1/20th of the Setup Time per piece and is ignoring the MO End Quantity.

After receiving 23 of 24 pieces, we can see that it is using $42/piece.

  • $42 * 23 = $966

And finally, with the MO complete and all pieces received, we can see that the Costs Put into WIP holds $8 more than Standard.  If we had produced exactly 20 pieces the math would have been correct, if we produced much more than 20 the variance would be even larger.

 

Conclusion

With Actual Cost items the calculation is wrong and significantly under applies Setup Cost.  With Standard Cost items there might be a weak argument in favor of always adding Setup Cost at the prorated value (a kind of “setup overhead”), but even here it would make more sense to apply the full Setup Cost (i.e. Cost/End Qty) to the items produced.

The Prorate Setup Costs setting makes sense when calculating the standard cost of an item during a cost roll-up and revalue, but it should not impact how setup costs are calculated and applied on a Manufacturing Order.

For Actual Cost, it makes sense to NOT have Prorate Setup Costs marked.  Average Quantity on Item Engineering can then be set, if needed, and it will not impact manufacturing orders.

For Standard Cost, you may want to consider only marking the Prorate Setup Costs box immediately BEFORE doing a Roll-up and Revalue, then unmarking it.  It would be important to not process any MO Receipts while the setting is enabled.

 

 

PSTL Combiner Duplicate Key Error

Keywords: PSTL, Professional Services Tool Library, Duplicate Key

When using PSTL Combiner (i.e. combining Items, Customers or Vendors), you can get a duplicate key error:

[Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint ‘PK-tablename-‘. Cannot insert duplicate key in object ‘dbo.-tablename-‘.  The duplicate key value is (AAAAAAA, BBBBB)

This is usually caused by a table that has multi-part key, such as a pricing table where the key fields are:

  • Item Number
  • Vendor ID
  • U of M
  • Date
  • Qty

In such a table if there is pricing for Item A and Item B, and you are combining B into A, there is no way for PSTL to “combine” two price lists.  The same would be true for changing Vendor X to Vendor Y…it would create duplicate price lists and the software has no way to figure out which one to keep.

DO NOT FOLLOW THE STEPS BELOW IN A LIVE COMPANY DATABASE!  MAKE SURE YOU HAVE TESTED AND VALIDATED BEFORE DOING THIS IN LIVE.

For the table getting the error, delete either the A or B set of records.  You need to make a choice of which “source” will be the master record going forward, is it the records from A or from B?  Then run the query below:

delete [tablename] where [ITEMNMBR/VENDORID/CUSTNMBR] = ‘A’

9MAY2023: Update: John Arnold at US Digital shared the script below (link is a text file) he created to identify problems with Customer Combiner prior to running the tool.  Download Script

 

MFGPowerPack 2023-05-02

Release Date: 2-MAY-2023
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.218
* SVC Equip Suite: (1) Equipment Customer Change now works with the RMA Receiving window, (2) In the RMA Line Serial Numbers window when the software detects that the SN being returned does not belong to the Customer on the RMA it will ask if you want to change the customer, and if you answer YES it will automatically do the change without opening the Equipment Customer Change window.

 

MOGenerator 2023-05-01

Release Date: 1-MAY-2023
GP Versions: 12/14/16/18
MOGenerator Build: 4.120
* MOGenV2: (1) fixed issue in Excel import that caused Post To to be blank (#202300567), (2) MO Rescheduling can now be done with all MO Statuses other than Complete and Closed.  NOTE: The MO Entry window requires that MOs be in Open or Quote status to be rescheduled, but the Batch Reschedule window does not have this same restriction.  Rescheduling a Released or Partially Received MO behaves as you would expect–it changes the required dates on Picklist components and the Start/Stop date/time on Routing Sequences.
* Updated Excel imports to use a different excel api property that is not affected by spreadsheet formatting

 

MFGPowerPack 2023-04-20

Release Date: 18-APR-2023
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.217
* Serial/Lot Auto Generate: added support for WilloWare’s LeanMFG module (requires updating to the lastest LeanMFG build)
* NEW TWEAK: Force Reschedule- The MO Entry window does not allow rescheduling released (or above) status MOs even though they can be rescheduled from the Batch Reschedule window. This Tweak adds an Additional Menu item to MO Entry that bypasses controls on that window which prevent rescheduling a Released (or above) MO.

GP Manufacturing Multi-Product/By-Product

Keywords: Dynamics GP Manufacturing, multi-product, co-product, by-product

A GP Manufacturing Order can only produce one item.  Right?

This may surprise you, but a GP Manufacturing Order can produce multiple items at once.  This is often referred to as By-Products, but it can be used for any scenario where you need to make multiple items at once.  Here’s how.

In this scenario we are producing cuts out of a roll of steel.  When we create an MO for 2×8 cuts we could also produce 2×4 and 2×6 cuts.

Additionally, we track lot numbers of the steel rolls so that we can always tell how much of a roll remains by looking at the lot quantity.

When we create a manufacturing order that needs a steel roll we issue the ENTIRE ROLL to the MO, and then return to stock the remainder of the roll.  This could be done by an Issue and Reverse Issue, however we’re doing to do it as a by-product (more on this later).

As shown above, the BOM for the 2×8 SHEET has both of the other possible cuts that could be produced AND the STEEL ROLL all at zero quantity.  It is not necessary to do this, the BOM could have only the STEEL ROLL, but we’ll see later that the extra setup at this point makes it easier to record production.

We have a Manufacturing Order to make 4 of the 2×8 SHEET.   The Picklist includes the “zero quantity” items:

The MO requires 0.12 FEET of STEEL ROLL, but when we check inventory we find that the smallest lot quantity is 20, so we change the Issue Transaction to 20 and post it.

MO Receipts can be posted as needed on the MO, recording additional production of “other” items at the same time.

At this point you could manually add By-Products/Co-Products/Multi-Products manually by clicking the Add Component button and entering the Quantity Produced as a NEGATIVE.  The benefit of adding the POSSIBLE other items to the BOM with zero quantity is you just need to enter the quantity next to each item.  It is much faster.  As shown above the other items that COULD BE produced are shown on the MO Receipt Entry window.  We will produce some of each item.

The software does not calculate the quantity of STEEL ROLL consumed by the co-products so that needs to be done manually.  However, the same would apply when doing a Reverse Issue transaction, and recording it as another co-product eliminates the need to create a separate Reverse Issue transaction.

Posting the MO Receipt will first post “production” of the co-products:

Followed by the normal finished good receipt:

With Actual Cost inventory the by-products go into stock at the last cost (i.e. the Current Cost shown on Item Maintenance).  There isn’t an opportunity to enter a Unit Cost, so costs would need to be adjusted after the fact using the Inventory Adjust Costs utility.

(WilloWare can customize the MO Receipt process for Actual Cost items to perform a cost allocation calculation that apportion the input costs (inventory, labor, machine, etc)  correctly over the items produced.)

When the Actual Cost finished good posts, its cost is the REMAINING costs in WIP (i.e. total cost put into WIP minus By-Product Cost).

With Standard Cost inventory the by-product go into inventory at its Standard Cost, as does the finished good.  The Standard Cost Roll-up routine does not include By-Product costs even if they are included on the BOM, so by-products/co-products when used with Standard Costing will always result in a Variance.

DS1114 Time & Materials Billing Entry Enhancement

Customization DS1114

Time & Materials Billing Entry Enhancement

Problem Definition:

ACME needs to see the Cost Owner Name, not just the ID, when working in the Project Time & Materials Billing Entry window.

Design Features:

T&M Billing Entry Enhancement

When a user clicks on a line in the scrolling window, the Cost Owner “Name” will be displayed in the Title Bar of the T&M Billing entry window.

Table

Description automatically generated

The name will be displayed with a 1-character code to identify the source of the Cost Owner ID. The Codes will be:

E: Employee ID

Q: Equipment ID

M: Misc Log ID

V: Vendor ID

I: Item Number

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

www.willoware.com/contact-me

DS0709 Lock Payables Account

Customization DS0709

Lock Payables Account

Problem Definition:

ACME does not want users to be able to change the Payables Account on the Payables Transaction Entry Distribution window. They would like to lock the Account Number for any PAY line in the window so that users are unable to enter or select a new Account Number.

Design Features:

Payables Transaction Entry Distribution

Navigation: Transactions >> Purchasing >> Transaction Entry >> Distribution Button

Graphical user interface, table

Description automatically generated

The Payables Transaction Entry Distribution window will be restricted so that users are unable to modify the Account Number of any line in the scrolling window where the Type = PAY. The enhancement will do the following:

  1. If the user clicks into the Account Number field in the scrolling window, the user will be warned that the Account Number is not editable and will be unable to continue. The focus of the line will be moved out of the Account Number Field and into the Debit Field. (Please see #3 below for the Debit Field restriction.)
  2. If the user clicks on the Type Dropdown to change the Dropdown from PAY to another option, the user will be warned that the Type is NOT editable and will be unable to continue. The focus of the line will be moved to the Debit Field. (Please see #3 below for the Debit Field restriction.)
  3. If the user clicks into one of the fields below for the PAY line, the Account Number Lookup and Blue Expansion Arrow will be locked to prevent the user from updating the Account Number.

– Debit

– Credit

– Distribution Reference

Assumptions/Requirements:

  • Intercompany Payables Transactions are NOT used.

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

www.willoware.com/contact-me

Customization DS1192 IV Adjustment Number in GL Header Reference

Customization DS1192

Inventory Adjustment Number in

GL Header Reference

Problem Definition:

When Dynamics GP posts an Inventory Transaction to the General Ledger, the GL Transaction Header “Reference” field contains “Transaction Entry”, as shown below:

Graphical user interface, text, application, table

Description automatically generated

ACME would like the Reference Field to contain the Inventory Transaction Number. As shown above, “Transaction Entry” would be replaced by “0000000000000261”.

Design Features:

There is no user interface.

When an Inventory Transaction is posted, the resulting Journal Entry will have the IV Transaction Number in the GP Header Reference field.

Assumptions/Requirements:

  • 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.
  • The functionality described above is intended for the GP Desktop client.

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

www.willoware.com/contact-me

Virtual Trigger VT1427 Auto-fill Payables Transaction Description

Virtual Trigger VT1427

Auto-fill Payables Transaction Description

NOTE: Virtual Triggers is a module from the WilloWare Consulting Toolkit. Virtual Triggers provides the ability to quickly enhance GP functionality with small bits of Dexterity code.

Description of Need:

When creating a Payables transaction, ACME populates the Description with the Vendor ID and the Document Number (Vendor ID + space + Document Number), as shown below:

Graphical user interface, table

Description automatically generated

This makes it easier to find specific transactions at the GL.

Graphical user interface, application, table

Description automatically generated

Description of Solution:

WilloWare will create a Scriptlet for use with Virtual Triggers that will do the following:

  • The user will enter a Vendor ID
  • After entering the Document Number and pressing the TAB key, (or otherwise leaving the field,) if the Transaction Description is empty, it will be populated automatically with Vendor ID + space + Document Number (up to the full length of the Description field.) If needed, Vendor ID will be truncated.
  • If the Transaction Description is already populated, it will not be overwritten.

Assumptions/Requirements:

Requires the separate purchase of WilloWare’s Consulting Toolkit Virtual Triggers module.

For Information about this Virtual Triggers Scriptlet, or any WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

Customization DS1310 Add Text Field to RM Transaction Entry

Customization DS1310

Add Text Field to RM Transaction Entry

Problem Definition:

ACME needs a 50 character text field attached to Receivables Transactions. This field needs to be displayed from Receivables Transaction Entry and Receivables Transaction Inquiry zoom.

Design Features:

Receivables Transaction Entry

Navigation: Transactions >> Sales >>Transaction Entry


The field will be displayed in the same location on Receivables Transaction Inquiry Zoom. This window is not being modified via Modifier. The field is added to the window via code.

Field

Function

Text Field

The Text Field will be labeled “Additional1”. This is a 50 character free text entry field. When a Documment Number is displayed, the string value (if present) will be displayed. When an entry is made or updated, saving the document saves changes to this field. The values of this field will be saved to the SYS90000 table. The values in the table will be:

Object Type = Hardcoded as “SINV”

ObjectID = Document Number

PropertyName = Field Name

PropertyValue = Value entered into the field

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 DS1457 Routing Sequence OSRC Address Info

Customization DS1457

Routing Sequence OSRC Address Info

Problem Definition:

ACME uses Dynamics GP Manufacturing and creates Outsourcing POs from Manufacturing.  Several of their Vendors have multiple locations, and ACME has multiple facilities.  Because the PO created from MFG defaults to the Vendor’s setup they need to remember to change the Purchasing Address information on each PO.  To get around this they have created multiple Vendor records for the same Vendor, and multiple “copies” of each Work Center and assigned the Vendor to the WC.   

Graphical user interface, application, table

Description automatically generated

ACME would like a better way to manage their PO Address requirements.  They would like to be able to assign to an Outsourced Routing Sequence one, or both, of the Addresses highlighted above (Purchase Address ID and Ship To Address ID).  When a PO is created for an Outsourced Routing Sequence the assigned address(es) should default on to the PO (and lines).  This will allow them automatically create a PO with the correct “ship to vendor” information, and the correct “return to our facility” information. 

Solution Overview:

WilloWare will add a new functionality to Dynamics GP that allows ACME to:

  • Set Vendor & Company Address information on an Outsourcing Work Center
  • Set Vendor & Company Address information on an Outsourced Routing Sequence. The Default values will pull from the WC to the Routing Sequence.
  • Set Vendor & Company Address information on a Working Routing Sequence. The Default values will pull from the Planning Routing Sequence, and if not present there, from the WC.

Design Features:

ORSC Address Overview

Outsourcing Addresses override the default Addresses when an Outsourced PO is created from Manufacturing.  Normally the Purchase Address ID comes from the Vendor Maintenance window, and the Ship To Address ID comes from the Company Setup window.   

Outsourcing Addresses can provide a different Vendor Address (i.e. the Vendor has multiple facilities) so you ship to the correct location, and a different Ship To Address (i.e. your own company has multiple facilities) so the Vendor returns product to the correct location.   

Graphical user interface, application, table

Description automatically generated

Outsourcing Address Information can be maintained in the following places:

  • Work Center
  • Planning Routing Sequence
  • Working Routing Sequence

The OSRC Address information for a Planning Routing Sequence will default with the information assigned to the Work Center.

Changes can be made tot eh OSRC Address information on a Planning Routing Sequence so that it can have different Vendor and Company Addresses than the Work Center defaults.

When a new Manufacturing Order is created, GP Manufacturing creates a copy of the Planning Routing attached to the Manufacturing Order. This is called the Working Routing. When MFG creates a Working Routing, the OSRC Address information will be populated from:

  1. The Planning Routing Sequence
  2. If either, or both of the addresses are blank on the Planning Routing Sequence, they will then be pulled from the OSRC Work Center Address information.

If the MO is Rescheduled, (i.e. the “Schedule” button is clicked again,) it will repopulate the OSRC Address Information.

Changes can be made on a Working Routing Sequence to either, or both addresses.

When an Outsourced PO is created:

  • If a Vendor Address ID is present on an Outsourced Working Routing Sequence, this will override the default “Purchase Address ID” on an Outsourced Purchase Order.
  • If a Company Address ID is present on an Outsourced Working Routing Sequence, this will override the default “Ship To Address ID” on an Outsourced Purchase Order.

The address information from the Working Routing Sequence will update the PO Header and Lines and will only affect newly created POs.  Changing OSRC Address information never updates existing POs. 

NOTE: Additional Company Addresses can be created in the Company Address Setup window. Navigation: Tools >> Setup >> Company >> Company >> Address Button

OSRC Workcenter Address Maintenance

Navigation: Cards >> Manufacturing >> Work Centers >> Setup. From the Work Center Setup window >> Additional >> OSRC Addresses

Graphical user interface, table

Description automatically generated

Graphical user interface

Description automatically generated

Field

Function

Vendor ID

Displays the Vendor ID assigned to the Outsource Work Center. (Outsourcing setup must be completed before entering address information.)

Address ID

Enter an Address ID or select one from the Lookup. This is the address you will deliver product to for the outsourced service.

Address Fields

The address fields display the address information but are not editable.

Company

Displays the name of your company from the Company Setup window.

Address ID

Enter a Company Address ID or select one from the Company Address Lookup window. This is the location to which the Vendor will return products after service.

OSRC Address information from a Work Center will default to new Routing Sequences.

When you click the ROLLDOWN button you will be asked: 

Do you want to rolldown the Work Center OSRC Address information to all Planning Routings? 

If you answer yes, the current OSRC Addresses assigned to the Work Center will be applied to ALL Planning Routing sequences that use the selected Work Center. 

Work Center Setup: If the “Outsourced” dropdown is changed from YES to NO, the user will be prompted: “This will delete the OSRC Address information on all routings with this Work Center. Do you want to continue?” If NO, the Outsourced setting will be reset to YES.

Outsourced Work Center Setup: If the Vendor ID is changed the user will be prompted: “This will delete the OSRC Address information on all routings with this Work Center. Do you want to continue?” If NO, the Outsourced setting will be reset to YES.

OSRC Planning Routing Address Maintenance

Navigation: Cards >> Manufacturing >> Routings >> Routing Entry. From Routing Sequence Entry window >> Additional >> OSRC Addresses

Graphical user interface, application, table

Description automatically generated

Graphical user interface

Description automatically generated

When the window opens, if either the Vendor or Company address is blank, and it is set on the Work Center, it will default from the Work Center to the Planning Routing Sequence. The addresses change on the Planning Routing Sequence as needed.

Field

Function

Vendor ID

Displays the Vendor ID assigned to the Routing Sequence

Address ID

Enter an Address ID or select one from the Lookup. This is the address you will deliver product to for the outsourced service.

Address Fields

The address fields display the address information but are not editable.

Company

Display the name of your company from the Company Setup window.

Address ID

Enter a Company Address ID, or select one from the Company Address Lookup window. This is the location to which the Vendor will return product after service.

DELETE removes the OSRC Address record from the Planning Routing Sequence but does not delete either address.

Changes to the OSRC Planning Routing Address information do not affect Working Routings.

Routing Sequence Entry: If the Work Center is changed the user will be prompted: “This will delete the OSRC Address information for this routing sequence. Do you want to continue?” If NO, the Work Center ID will return to the original value.

NOTE: Any changes made to routings through the routing utilities, (i.e. anything under Transactions >> Manufacturing >> Routings) will bypass the OSRC Address functionality. Manually check any affected routings to ensure they have valid OSRC Address information.

OSRC Working Routing Address Maintenance

Navigation: Transactions >> Manufacturing >> Manufacturing Orders >> MO Routing Edit. From the Manufacturing Order Routing Sequence Edit window >> Additional >> OSRC Addresses

Graphical user interface, application

Description automatically generated

Graphical user interface

Description automatically generated

When the Working Routing is created the OSRC Working Routing Address information will be populated as described in the Overview section. It changes here as needed.

Field

Function

Vendor ID

Displays the Vendor ID assigned to the Routing Sequence.

Address ID

Enter an Address ID or select one from the Lookup. This is the address you will deliver product to for the outsourced service.

Address Fields

The address fields display the address information but are not editable.

Company

Display the name of your company from the Company Setup window.

Address ID

Enter a Company Address ID or select one from the Company Address Lookup window. This is the location to which the Vendor will return product after service.

Changes to the OSRC Working Routing Address information can be made at any time but do not update existing POs.

Manufacturing Order Routing Sequence Edit: If the Work Center is changed the user will be prompted: “This will delete the OSRC Address information for this routing sequence. Do you want to continue?”  If NO, the WC ID will return to the original value.  NOTE: if the new Work Center has OSRC Address information it will then populate to the Working Routing Sequence. 

Manually adding a sequence will pull OSRC Address info from the Work Center even if the Sequence Number matches one on the planning routing

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. 

 

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

 

  1. National Accounts functionality is NOT used. 

 

  1. Advanced Distribution functionality is NOT used. 

 

  1. Unless otherwise noted in this document, reporting is not included in this estimate. 

 

  1. Unless otherwise noted in this document, Word Template functionality is not addressed. 

 

  1. 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 

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

www.willoware.com/contact-me/

MFGPowerPack 2023-03-14

Release Date: 14-MAR-2023
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.216
* OSRC Add To PO: (1) fixed issue that could allow user to incorrectly enter a PO Number that does not exist
* SVC Equipment Suite: fixed issue with RMA Serial Entry that caused an incorrect prompt to change the customer

Customization CR1143 SOP Entry Discounts

Customization CR1143

SOP Entry Discounts

Description of Need:

ACME provides per-sales-line discounts based on the Payment Terms. (Discounts are taken up front, per line, rather than at the time of payment.)

Payment Terms are not changed after lines have been entered on the transaction.

ACME would like to automatically apply a line-level discount as Orders are entered, and be able to easily see the Discounted Price (Unit Price – Markdown Amount) for each sales line. The Discounted Price should be visible on both Sales Transaction Entry and Sales Transaction Inquiry.

ACME will record the Discount Percent for the Payment Terms using the Payment Terms Setup window, as shown below.

Graphical user interface, application

Description automatically generated

None of the Calculate Discount On options are marked, so Sales Transaction Entry will not calculate a Discount Available.

Description of Solution:

When entering a Sales Transaction in Sales Transaction Entry, the enhancement will retrieve the Discount Type (Percent or Amount,) and the Value (i.e. 5%,) from the Payment Terms Setup window based on the Payment Terms ID on the Sales Customer Detail Entry window. This will be applied to the Sales Line as the Discount Percent after the quantity is entered (the Markdown Amount and Markdown Percent on the sales lines will be updated, which is saved into the SOP10200. MRKDNAMT and SOP10200. MRKSNPCT fields.)

Table

Description automatically generated

The Discount Price (Unit Price – Discount Amount) will be shown in the Title Bar of the Sales Transaction Entry window (and Sales Transaction Inquiry.) When an existing transaction is viewed, the Discount Price will change in the Title Bar as each line is selected. (As the cursor moves from one line to the next, the Title Bar will update to show the Discount Price for the current line.)

A picture containing table

Description automatically generated

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

www.willoware.com/contact-me/

Customization CR1449- POP Receipt Post SN Performance

Customization CR1449

POP Receipt Post SN Performance

Description of Need:

ACME has some serial numbered items in Dynamics GP that are purchased in very large quantities (such as 100,000).  During PO Receipt Entry the window verifies that each serial number does not exist in either the Serial Master or on another unposted transaction.   

 

During posting it again verifies that the serial numbers do not exist in the Serial Master (but it does not check other unposted transactions).  Because it performs the verification one serial number at a time, the posting process can take more than 40 minutes. 

 

ACME would like to reduce the amount of time it takes to post PO Receipts. 

Description of Solution:

The first option we considered, and tested, was to force the POP Receipt Posting process to skip verification of the serial numbers.  This could work and would be the fastest approach, however it would create an unlikely, yet possible, scenario where duplicate serial numbers are added to GP. 

 

The proposed approach is to modify the POP Receipt Posting process so that it performs a mass validation of POP Serial Numbers against the Serial Master.  This will be a single SQL query that checks for matching serial numbers between the POP Receipt Serials table and the Serial Master.  This approach retains the same data validation that Dynamics GP would otherwise perform one serial number at a time. 

In the unlikely event that a POP Receipt has a serial number that already exists in the SN master, the POP Receipt will not be posted.  An error code will be set on the POP Receipt Header that indicates “One or more line items contains errors.”  This error will print on the POP Receivings Posting Journal. 


This modification to the posting process will apply to Transaction, Batch and Series 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 customization, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

Customization DS1257 List Price Per Site

Customization DS1257

List Price Per Site

Problem Definition:

ACME sells landscaping products, such as stones and pavers.  They have numerous stores.  Due to the difference in the cost of transport to get materials from the manufacturer or quarry to the different stores, each store needs to sell at a different price. 

ACME creates Item Price Lists using “Percent of List Price”.  Contractors may have different negotiated rates so that, for example, one may get 92% of List Price while another has 93% of List.  Since pricing to the customer is based on Percent of List, and the cost to have material delivered to each store is different, in order to maintain a desired profit margin across all sites the “List Price” needs to vary by location (i.e. List Price is higher the further it is from a quarry to account for delivery costs). 

 Additionally, each store may sell a given product in a different Unit of Measure (such as Yards or Tons). 

To accomplish the above requirements, ACME would like:

  • The ability to record an Item’s List Price per GP Location Code (Site ID).
  • The ability to record an Item’s Default Selling U of M per Location Code.
  • In Sales Transaction Entry, have the U of M default based on the “Default Site ID” Selection.
  • In Sales Transaction Entry, have the line item pricing calculated using the Customer’s Price Level and the Site-specific List Price.

ACME is not using Multi-currency, so the List Price is set on the Item Maintenance window.

Design Features:

Item-Site Sales Maintenance

Navigation: Cards >> Inventory >> Item-Site Sales Maintenance, or from Item Maintenance >> Additional >> Item-Site Sales Maintenance

This window is used to set up Site specific selling options for Inventory Items. The List Price and Default Selling U of M can be specified per Site. These values are used in Sale Transaction Entry.

Table

Description automatically generated

Field

Function

Location Code

Enter a Location Code or select one from the Lookup.

Item Number

Enter an Item Number or select one from the Lookup.

List Price

Enter/modify the List Price for the Item in the selected Site.

U of M

Enter/modify the Default Selling U of M for the Item in the selected Site.

NOTE: In Sales Transaction Entry, if the Default Selling U of M- Customer Price Level combination does not exist on the Item’s Price List, the “Default Selling U of M” from Item Price List Maintenance will be used.

When opened from Item Maintenance, the Item Number and Description will be carried over to Item-Site Sales Maintenance from Item Maintenance.

If an Item-Site is not specified above, Sales Transaction Entry will use the normal “default” pricing and Selling Unit of Measure. If selling an Item in a Site needs either a different List Price or a different Unit of Measure, BOTH values must be provided above.

Sales Transaction Entry

There are no user interface changes.

In Sales Transaction Entry, and Sales Item Detail Entry:

  • The Unit Price (and Extended Price) will be calculated using the Customer’s Price List and the “List Price” specified for the “Default Site ID” on the Sales Transaction Entry window. Site-specific List Prices are maintained in the Item-Site Sales Maintenance window.
  • The Sales Line U of M will default to the U of M entered for the Item-Site combination in the Item-Site Sales Maintenance window. If the U of M has not been assigned to the Customer’s Price Level in the Item Price List Maintenance window, the Sales Line U of M will revert to the “Default Selling U of M” from the Item Price List Maintenance window.

Assumptions/Requirements:

  • 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.
  • The functionality described above is intended for the GP Desktop client.
  • Unless otherwise noted in this document, reporting is not included in this estimate.
  • Unless otherwise noted in this document, Word Template functionality is not addressed.
  • Extended Pricing is NOT enabled.

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

www.willoware.com/contact-me/

MFG Import 2023-03-01

Release Date: 1-MAR-2023
GP Versions: 12/14/16/18
MFG Import Build: 3.62
* Changed Import Mapping (BOM and Routing) to allow multiple fields to reference the same source column in SQL, such as allowing the same column that has Item Number to be used for Item Number and Routing Name.

Virtual Trigger VT1151 Assembly Transaction- Change Assemble Quantity

Virtual Trigger VT1151

Assembly Transaction- Change Assemble Quantity

Note: Virtual Triggers is a module from the WilloWare product Consulting Toolkit.

Virtual Triggers provides the ability to quickly enhance GP functionality with small bits of dexterity code.

Description of Need:

ACME uses the Dynamics GP Inventory Assembly transaction in food production. Due to the nature of working with food, there is variability in the quantity of the finished good regardless of the quantity of raw materials consumed. For example, given a certain amount of raw materials, the finished good output could be the desired quantity (i.e. 50 cases), or it could be slightly less or slightly more (49 or 51 cases).

ACME adjusts the Assembly Quantity to reflect the actual quantity produced.

However, when they do this, GP recalculates the raw material quantities and deletes any Lot Numbers selected for the raw materials, which means the user has to then re-select all of the raw material lots.

ACME would like a way to change the Assemble Quantity without losing raw material lot numbers.

Description of Solution:

The solution proposed is based on using WilloWare’s Virtual Triggers module in the Consulting Toolkit Suite. The cost of that module ($1000 + $180/yr Annual Enhancement) is NOT included in this estimate.

See more about Virtual Triggers here: //willoware.com/products/consulting-toolkit/#vt

WilloWare will create a Scriptlet, (a small bit of dexterity code,) which is imported into the Virtual Triggers module. The Scriptlet will add an Additional Menu option to the Assemble Entry window called “Change Assemble Quantity”. Selecting that menu option will:

  • Check that the Assembly Transaction is assigned to a Batch ID
  • Open a dialog window and ask the user to enter the new quantity. They can cancel at this point and not make any changes.
  • If a Quantity is provided, the Assembly Transaction will be saved.
  • It will make adjustments necessary on the Assembly Transaction to change the Assemble Quantity.
  • It will redisplay the document.

After changing the quantity, the user can make adjustments to the finished good Lot Numbers, or Lot Quantity. NOTE: Assembly Entry will not allow the transaction to post if the finished good Lot Quantity does not match the Assemble Quantity.

Assumptions/Requirements:

  • Requires the separate purchase of WilloWare’s Consulting Toolkit Virtual Triggers module.

For information on this Scriptlet, or any other Willoware customization or product, please contact us:

www.willoware.com/contact-me/

Customization DS1455 National Account Customer Transfer

Customization DS1455

National Account Customer Transfer

Problem Definition:

ACME is a real estate company that manages brokers and agents. It is not

uncommon for an Agent to change from one Broker to another. In Dynamics GP, ACME manages the Broker-Agent relationships with the National Accounts functionality. Once a National Accounts relationship is created in GP, it does not easily allow changing a Customer from one NA to another.


ACME needs the ability to move customers between National Accounts.


ACME does not use Multi-currency or Project Accounting.


There may be open invoices for an Agent, and those should move with the Agent to the new

Broker. Partially paid and fully paid documents should remain with the previous Broker.

About

An About window for this product is available from:

Help>>About Dynamics GP>>Additional>>About Customization DS1455

Graphical user interface, text

Description automatically generated

Setup

Users must have access to the windows and reports in this product. The installation routine created a security task called WW_CUSTOM.

It will also create a new Security Role called WW_CUSTOM, and it will assign the WW_CUSTOM Security Task to an existing Role, or by assigning the WW_CUSTOM Security Role to a user.

Design Features:

NA Customer Transfer

In the National Accounts Maintenance window, select the NEW Broker. Add the Agent to the Broker. Instead of receiving a message that the “customer already exists in another national account relationship”, you will be asked if you want to transfer the customer from the old broker to the new one. If you answer yes, the customer will be added to the new Broker.

Graphical user interface

Description automatically generated

Graphical user interface, text, application

Description automatically generated

In the example above, AARONFIT0001 (the Agent) is being moved from VISTATRA0001 to WORLDENT0001. When asked to confirm the change, click YES.

Unpaid open Invoices for the Agent (AARONFIT0001) will be transferred to the new Broker. Complete and partially paid transactions will remain linked to the old Broker.

Graphical user interface, application

Description automatically generated

Payments from the old broker (VISTATRA0001) can still be applied to any partially paid invoices that had been partially paid by the old Broker (VISTATRA0001).

The Agent’s transactions will appear in the “National Account” view for the old Broker. You can also use “Specific Customer” to view only transactions for a specific Agent. Select “Specific Customer” and enter the Customer Number (AARONFIT0001). The Lookup will not show the Agent because that National Account relationship belongs to a different account.

WARNING! Do not DELETE the Customer from the National Accounts scrolling window. That will cause GP to remove the National Account information from every transaction for the Customer, both open and historical.

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

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

www.willoware.com/contact-me

MOGenerator 2023-02-20

Release Date: 20-FEB-2023
GP Versions: 12/14/16/18
MOGenerator Build: 4.115
* MOGenV2: (1) fixed issue in EditAllowed function that caused it to always return false, (2) fixed issue with the ApplyChanges routine that incorrectly returned an error that the End Quantity and Post To Site Are Not Allowed.

MFG PowerPack 2023-02-16

Release Date: 16-FEB-2023
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.215
* SVC Equip Suite: (1) Changed setup to allow longer SOP Numbers but warn user that it reduces the possible configs per SOP Doc, (2) Rebuild Configs Utility: added check that a serial number was produced on an MO that has serial/lot linking before removing the existing config, (3) Equip Customer Change: from RMA Serials window it now asks users if they want to open the Equip Customer Change window rather than requiring it to be opened manually when the entered serial belongs to a different customer
* Sales Forecast Integration, Vendor Pricing Import, Proposed Cost Update, Serial Number Mass Entry, Item Copy: updated Excel communication to avoid issues casued by hidden columns, cell formatting, and regional settings
* Serial Number Mass Entry: addressed issue that was preventing adding serial numbers to SOP Returns

MFG Import 2023-02-10

Release Date: 10-FEB-2023
GP Versions: 12/14/16/18
MFG Import Build: 3.61
* Addressed an issue that caused the import to bring in nulls/zeros when an Excel column included in the import was hidden in Excel. The import routine will now unhide hidden columns if they are included in the import.

MFG PowerPack 2023-02-09

Release Date: 9-FEB-2023
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.214
* SVC Equipment Suite-Equipment Customer Change (ECC): addressed issue with ECC in the RMA Line Serial Numbers window where (1) the RMA Line Serial window will not allow entry of the serial number because it belongs to a different customer, and (2) the ECC window will not open without a serial number. The ECC window will now open with the Customer and Item Number only and allow the user to enter the serial number (#202300142).

Customization CR1350 Rolldown PO Required Date

Customization CR1350

Rolldown PO Required Date

Description of Need:

ACME often changes the required date on the purchase order header. When they do so, they need to manually update the required date on each line. Purchase orders can have up to 150 lines that require changing. ACME would like the option to rolldown the Required Date in a similar manner as the Promised Date.

Description of Solution:

Table

Description automatically generated

After the user updates the Required Date on the Purchasing Date Entry window and clicks OK to close it, they will be asked: “Do you want to roll down the changes to the required date to the line items?”. If the user answers YES, then the required date for each line item will be updated to match.

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 CR0955 Picklist PO Gen

Customization CR0955

Picklist PO Gen

Description of Need:

ACME can have several hundred new Manufacturing Orders at any given time. Some inventory replenishment is planned via MRP, but other items are purchased as needed when MOs are released and the Picklist indicates there are shortages. ACME has the “Allocate Inventory on Release” option marked in Manufacturing Setup, so GP attempts to allocate available inventory when each MO is released.

An existing customization (DS0803) addresses the need to create purchase orders for Picklist items that have shortages. However, since it works on a per-MO basis, it is time consuming to use with hundreds of MOs.

ACME needs to modify the utility to support creating POs for many MOs at one time.

Description of Solution:

Navigation: Transactions>>Manufacturing>>Picklist PO Generator. The window can also be opened for a single MO from Transactions>>Manufacturing Orders>>Pick List>>Additional>>PO Generator

Table

Description automatically generated with low confidence

Range Restrictions:

Required Date, Item Number, and MO Number ranges are used to restrict which MOs are shown in the Available Manufacturing Orders window.

Required Date is the earliest Picklist Item Required Date, which could be the same as the MO Start Date, but the Picklist Required Date will account for any component lead times.

Item Number restricts Available MOs to only those where the Make Item is within the range.

MO Number restricts Available MOs to only those where the MO Number is within the range.

Changing any of the range values causes the Available MOs window to redisplay automatically.

Available Manufacturing Orders:

Available MOs can be moved to the Selected MOs window by clicking the > or >> buttons (Select One, Select All)

The “MO Number” column header is a Zoom which allows opening the MO in MO Entry.

Selected Manufacturing Orders:

When MOs are added to, or removed from, the Selected MOs window, the Picklist Shortages window redisplays (bottom scrolling window).

Picklist Shortages:

Displays one line for each Picklist line-item shortage.

Primary Vendor restricts the Shortages window to show only those lines that have the specified Primary Vendor.

Issue From restricts the Shortages window to show only the lines that have the specified Issue From Site ID.

Add to PO restricts the Shortages window to show only those lines that have an Item-Vendor record for the Vendor assigned to the selected PO. The window will only show Items that can be added to the selected PO without needing to create new Item-Vendor assignments.

Add a single requirement to a PO- A single Shortages line can be added to an existing PO by entering the PO Number into the PO Number field on the Shortage Line, (or select a PO from the PO Number Lookup.)

Important Changes from Current Picklist PO Generator:

PO Header “POP Contract Number” field will no longer be populated with the MO Number, since the requirements from multiple MOs could be consolidated into a single PO. The PO Line Comment will continue to contain the linked MO Number.

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

www.willoware.com/contact-me/

Customization DS0803 Auto-create PO from MO Pick List

Customization DS0803

Auto-create PO from MO Pick List

Problem Definition:

ACME requires the ability to auto-generate Purchase Orders direct from Manufacturing Order Pick Lists for Buy Items with shortages that are not MRP planned for the Item/Site combination.

Purchase Order Lines should be consolidated if multiple lines share the same Vendor ID.

Design Features:

Navigation: Transactions >> Manufacturing Orders >> Pick List >>Additional >>PO Generator

From the Manufacturing Order Pick List, the user will navigate to Additional >>PO Generator. The MO Picklist Shortage PO Generator window will open if the MO Status is set to Released, Partially Received, Hold, Complete or Closed. The window will be view only if the MO Status is set to Hold, Complete, or Closed.

This window is used to create Purchase Orders for the MO Picklist shortages as well as to view previously created Purchase Orders.

C:\Users\Karen\Documents\Clients\Interdyn BMI\Stark Aero\MO Picklist Shortage PO Generator.jpg

Please Note: Unless otherwise noted, all fields below are not editable.

Field

Function

Process

The user will click the PROCESS button to generate or update Purchase Orders for all marked Item Numbers. Please see the section below entitled PROCESS BUTTON for more details.

Mark All

The use will click the MARK ALL button to mark all eligible Item Numbers in the scrolling window. An Item Number is considered eligible if:

  1. It does not have a linked PO Number
  2. It has a PO Number linked, but the PO is at Status NEW

Unmark All

The user will click the UNMARK ALL button to unmark all Item Numbers in the scrolling window.

X

This field is a checkbox. The user will check the checkbox to mark an Item Number to be included in the PO Creation Process.

An Item Number can only be marked if:

  1. It does not have a linked PO Number
  2. It has a PO Number linked, but the PO is at Status NEW.

Item Number

All Item Numbers on the MO Picklist matching the following criteria will display:

  1. The Item Number/Site ID combination in the Item Resource Planning Card has its Calculate MRP for this Item/Site checkbox unchecked.
  2. The Item Number/Site ID combination in the Item Resource Planning Card has its Replenishment Method set to BUY.

Issue From

The Item Number’s Issue From Site ID from the MO Picklist will display.

UOM

The UOM from the MO Picklist for the Item Number will display.

Shortage Qty

The Shortage Qty will be set equal to the Item’s Picklist Required Qty.

Minimum Qty

The Minimum Qty for the Item Number/Site ID combination in the Item Resource Planning Card will display.

Shortage Required Date

The MO Start Date will display.

Vendor ID

The Last Order Vendor ID will default. The user may enter or select a Vendor ID from the lookup should a Last Order Vendor ID not exist or if they wish to change the Vendor ID. The user may NOT update the Vendor ID, if a Purchase Order is already linked to the Item Number.

Please Note: The Vendor ID lookup will only display Vendor ID’s that are assigned to the Item Number.

PO Number

If a Purchase Order Number is already linked to the Item Number, the PO Number will display.

Please Note: To delete a PO Link from a Picklist Line Item, select the Line Item and then click on the Link Button. The user will be prompted, “Do you want to break the link to PO XXXX?” If the user clicks NO, the enhancement will do nothing. If the user clicks YES, the enhancement will break the link.

The Purchase Order itself will NOT be changed. Only the link to the MO Picklist will be removed.

PO Status

The linked Purchase Order Number’s status will display.

PO Qty

The linked Purchase Order Number’s Quantity Ordered will display.

PROCESS BUTTON

When the user clicks the PROCESS BUTTON the enhancement will do the following for all Item Numbers that do NOT already have a linked PO Number:

  1. Group the Item Numbers by Vendor ID.
  2. Generate one Purchase Order Number be Vendor ID.
  3. The PO Header will contain the following detail:
  • PO Type: Standard
  • PO Number: Next chronological PO Number
  • Vendor ID: Vendor ID from scrolling window
  • PO Date: User Date
  • Currency ID: Company’s Functional Currency
  • Purchase Address ID: Vendor ID’s default Bill To Address
  • Bill To Address ID: Vendor ID’s default Bill To Address
  • Ship To Address ID: Company’s Primary Address ID
  • Ship Method: Vendor ID’s default Shipping Method
  • Contract Number: MO Number
  • Payment Terms: Vendor ID’s default Payment Terms
  1. The PO Line(s) will contain the following detail:
  • Item Number: Item Number from scrolling window
  • U of M: U of M from the scrolling window
  • Quantity Ordered: shortage Qty or Minimum Qty from the scrolling window. (The larger of the two Quantities will be used.)
  • Unit Cost: Vendor ID’s Last Originating Cost for the Item Number
  • Site ID: Issue From Site ID from the scrolling window
  • Required Date: MO Start Date
  • Line Comment: MO Number

When the user clicks the PROCESS BUTTON the enhancement will do the following for all Item Numbers that do already have a linked PO Number at Status NEW:

  1. The PO Line’s Quantity Ordered will be updated to the greater of the Shortage Qty or the Minimum Qty from the scrolling window.
  2. The PO Line’s Site ID will be updated to the MO Picklist’s Issue From Site ID.
  3. The PO Line’s Required Date will be updated to the MO Pickist’s Required Date for the Item Number.

Please Note:

ACME should NOT delete Item Numbers from the MO Picklist. If an Item Number is NOT required, the Picklist Quantity should be updated to 0.

Assumptions/Requirements:

  1. Unless otherwise noted in this document, reporting is not included in this estimate.
  2. Multi-Currency is not utilized in the Purchasing Module.
  3. ACME does NOT override MO Picklist Shortages during the MO Release process.
  4. ACME does NOT use the BOM-Routing Link functionality or BOM Lead Time Offset functionality within the Manufacturing module.

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

www.willoware.com/contact-me/

Customization CR1191 Project Maintenance CRM Opportunity ID Control

Customization CR1191

Project Maintenance- CRM Opportunity ID Control

Description of Need:

ACME stores a “CRM Opportunity ID” (CRMOID) in an Extender field on the Project Maintenance window. If the user has not already entered this value, the user should not be allowed out of the Project without entering the CRMOID.

Description of Solution:

When any action in the Project Maintenance window requires saving the record, the proposed enhancement will check if the CRMOID exists, and if not, the user will be warned:

“Please enter a CRM Opportunity ID.”

The attempt to “save” will be aborted and the user will then need to open the Extender window and enter the CRMOID. This will occur with any action that “saves” the Project, such as clicking the Save button, scrolling buttons, or Print button.

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.

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

www.willoware.com/contact-me/

Customization CR1191

Project Maintenance- CRM Opportunity ID Control

Description of Need:

ACME stores a “CRM Opportunity ID” (CRMOID) in an Extender field on the Project Maintenance window. If the user has not already entered this value, the user should not be allowed out of the Project without entering the CRMOID.

Description of Solution:

When any action in the Project Maintenance window requires saving the record, the proposed enhancement will check if the CRMOID exists, and if not, the user will be warned:

“Please enter a CRM Opportunity ID.”

The attempt to “save” will be aborted and the user will then need to open the Extender window and enter the CRMOID. This will occur with any action that “saves” the Project, such as clicking the Save button, scrolling buttons, or Print button.

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.

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

www.willoware.com/contact-me/

Customization DS1358 Contract Number Additional Field

Customization DS1358

Contract Number Additional Field

Problem Definition:

ACME needs a Contract Number field added to the Receivables Transaction Entry and Bank Transaction Entry windows. The field needs to hold 50 characters that is not connected to another ID field within GP. This field does not need to be validated nor does it require a lookup.

The Contract Number must also be visible from the corresponding inquiry windows.

Solution Overview:

This solution will use a Virtual Field to add Contract Number to the requested windows.

Virtual Fields are added to windows at runtime and do not require modified or alternate forms. The Contract Number entered on the windows will be stored in a custom table with key fields to link back to the GP transaction tables.

The table will consist of the following fields:

Table Name: wContractNumbers

Field

Description (* Indicates Key Field)

Key String*

Required Key Field. Since this table will be used for both Bank Transactions and RM Transactions, this field will contain EITHER the Customer Number for RM Transactions or Checkbook ID for Bank Transactions.

Document Number*

The Bank Transaction Number or RM Transaction Number.

Document Type*

The Document Type. Values will match those in the Bank Transactions table or RM Transactions table.

Contract Number

The 50 character string field that stores the contract number.

Additional information regarding using the table for reporting is included in each section below.

Design Features:

Receivables Transaction Entry/Zoom

Graphical user interface, application

Description automatically generated

Graphical user interface, application

Description automatically generated

Field

Function

Contract Number

50 Character field that will be added just above the existing Currency ID field. This field will be editable on the Entry window, view-only on the Zoom window. The value will be saved to the database when the user clicks SAVE.

Table Name: wRMContractNumber

Field

Description (* Indicates Key Field)

Document Type*

The Document Type

Document Number*

The RM Document Number

Contract Number

The 50 character string field that stores the contract number

When a Receivables Transaction is created (and unposted), GP saves the record into the RM_Sales_WORK (SQL Name: RM10301) table. The primary key of this table is RM Document Type and RM Document Number. When a Contract Number needs to be entered, it will be saved to our custom table (wRMContractNumber).

The two tables can use the following relationship to be joined for reports that use the data in the RM_Sales_WORK table.

* Indicates Unique Record Key

RM_Sales_WORK

wRMContractNumber

RM Document Type-All*

————–

Document Type*

RM_Document Number-WORK*

————–

Document Number*

Customer Number

Contract Number

Etc.

After the Receivables transaction is posted, the document is moved into the RM_OPEN (RM20101) table. A unique record can also be found using the RM Document Type and Document Number. Any reports referencing the RM_OPEN table can also use the custom table by using the following join:

RM_OPEN

wRMContractNumber

RM_Document Type-All*

————–

Document Type*

RM_Document Number-WORK*

————–

Document Number*

Customer Number

Contract Number

Etc.

Bank Transaction Entry/Zoom

Graphical user interface, application, Word

Description automatically generated

Graphical user interface, table

Description automatically generated

Field

Function

Contract Number

50 Character field that will be added below the existing Type field. This field will be editable on the Entry window, view-only on the Zoom window. The value will be saved to the database when the user clicks POST.

Table Name: wCMContractNumber

Field

Description (*Indicates Key Field)

Record Number*

This is an auto-generated record number for the Bank Transaction. It is not displayed on the window but is a unique identifier for the record.

Contract Number

The 50 character string field that stores the contract number.

When a Bank transaction is posted, GP saves the record into the CM_Transactions (SQL Name: CM20200) table or CM_Receipts (CM20300). The primary key of these tables is Record Number. When a Contract Number needs to be entered, it will be saved to our custom table (wCMContractNumber).

The tables can use the following relationship to be joined for reports that use the data in the CM_Transactions or CM_Receipts table.

* Indicates Unique Record Key

CM_Transactions

wCMContractNumber

Record Number*

————–

Record Number*

CM Transaction Number

Contract Number

CM Transaction Type

Etc.

CM_Receipts

wCMContractNumber

Record Number*

————–

Record Number*

Receipt Number

Contract Number

Receipt Type

Etc.

GP Transaction Entry/Zoom

Graphical user interface, application, email

Description automatically generated

Graphical user interface, application

Description automatically generated

Field

Function

Contract Number

50 Character field that will be added below the existing Type field. This field will be editable on the Entry window, view-only on the Zoom window. The value will be saved to the database when the user clicks SAVE.

Table Name: wGLContractNumber

Field

Description (*Indicates Key Field)

Journal Entry*

The JE number from the transaction

Contract Number

The 50 character string field that stores the contract number.

When a journal entry is saved, GP saves the record into the GL_TRX_HDR_WORK (SQL Name: GL10000) table. The primary key of this tables is Journal Entry. When a Contract Number needs to be entered, it will be saved to our custom table (wGLContractNumber).

The tables can use the following relationship to be joined for reports that use the data in the GL_TRX_HDR_WORK table.

* Indicates Unique Record Key

GL_TRX_HDR_WORK

wCMContractNumber

Journal Entry*

—————-

Journal Entry*

Etc.

Contract Number

After the GL Transaction is posted, the document is moved into the GL_YTD_TRX_OPEN (GL20000) table. A unique record can also be found using the Journal Entry. Any reports referencing the GL_YTD_TRX_OPEN table can also use the custom table by using the following join:

GL_YTD_TRX_OPEN

wCMContractNumber

Journal Entry*

—————–

Journal Entry*

Etc.

Contract Number

After the GL Transaction is moved to a historical year, the document is moved into the GL_YTD_TRX_HIST (GL30000) table. A unique record can also be found using the Journal Entry. Any reports referencing the GL_YTD_TRX_HIST table can also use the custom table by using the following join:

GL_YTD_TRX_HIST

wCMContractNumber

Journal Entry*

—————–

Journal Entry*

Etc.

Contract Number

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

MOGenerator 2023-01-17

Release Date: 17-JAN-2023
GP Versions: 12/14/16/18
MOGenerator Build: 4.113
* MORI: changes to accommodate “SQL Server Native Client Communication link failure”. Since GP can no longer communicate with the server when there is a network failure it is not possible to validate if an existing connection is still functional. When this error occurs the software will go into a loop attempting to create a new connection until it is successful, or the GP client is terminated.