Author: admin

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.

Customization DS1070 Item-Country Security

Customization DS1070

Item-Country Security

Problem Definition:

Some ACME products are restricted by federal law from being sold to certain countries. ACME needs a way to track in GP which countries are prohibited for an item, and to prevent use of that item in Sales Transaction Entry if it is prohibited based on the Customer’s Ship to Address. The following controls are needed:

  1. Record which countries are forbidden for an Item
  2. Prevent using an Item on Sales Transaction Entry if the Item is not allowed for a given Ship To Address’s country code
  3. Not allow changing of the Ship To Address Code on a transaction where the change would result in Items being disallowed
  4. Require Country Code on Ship To and Bill To Addresses used in Sales Transaction Entry
  5. Specify certain users as having the ability to Override the following condition and allow use of a forbidden Item: If the Bill To is Forbidden but the Ship To is Allowed. When this override occurs, create an audit trail of who did it and when.
  6. Prevent changes of Ship To Address information on the Sales Transaction (all changes must be recorded on the Customer Address Maintenance window).

Solution Overview:

The Country Code field on Customer Maintenance, and Customer Address Maintenance, will store the Country Code for the address.

Graphical user interface, application Description automatically generated

A new window will be added to assign “Prohibited” Countries to an Item.

Another window will be added to record a list of User IDs which are allowed to override a Bill-To-Disallowed & Ship-To-Allowed conflict.

In Sales Transaction Entry, the desired controls listed above will be applied to control which items can be used, and what changes can be made to the Ship To Address Code.

Design Features:

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

This window is used to maintain the list of Country Codes to which the Item CANNOT be sold.

A picture containing graphical user interface Description automatically generated

Field

Function

Item Number

User enters an Item Number, or selects one from the Lookup

Country Code

User enters a Country Code, or selects one from the Lookup

Approval User Setup:

Navigation: Setup >> Sales >> Approval User Setup

This window is used to maintain the list of Users who may approve a restricted Bill To Address Code with a non-restricted Ship To Address Code on a Sales Document.

C:\Users\Karen\Documents\Clients\MRP\Biolase\Approval User Setup.jpg

Field

Function

User ID

User ID will be entered or selected from the Lookup. Only User ID’s entered will be granted privileges to approve Bill To Addresses with restricted Country Codes. The Password for each User ID will be their Dynamics GP Password.

Sales Transaction Entry:

Require Country Code:

When creating a new Sales Transaction the enhancement will require that both the Bill To and Ship To Addresses have a Country Code. If either is blank, NO lines will be allowed on the transaction. The Bill To and Ship To cannot be changed on the Sales Transaction—all changes must be done on Customer Address Maintenance.

Lock Ship To Address Entry:

Navigation: Transactions >>Sales >> Sales Transaction Entry >> Sales Customer Detail Entry >> Sales Ship To Address Entry

Graphical user interface, text, application Description automatically generated

When the Sales Ship To Address Entry window is accessed from the Sales Document, all fields on the window will be locked and unable to be edited.

Control Change of Ship To Address Code:

There are two locations on a Sales Transaction where the Ship To Address Code can be changed:

  1. On the main Sales Transaction Entry window

Table Description automatically generated

  1. On the Sales Customer Detail Entry window

Graphical user interface, application Description automatically generated

When the Ship To Address ID is changed in either of these locations, the system will check if the change is allowed. It is only allowed if the Country Code on the new Ship To does NOT conflict with any of the Item-Country assignments from the Item-Country Maintenance window. If the change is NOT allowed, the user will be warned and the Ship To Address ID will reset to the original value.

Item Entry Controls

Condition: Ship To- NOT ALLOWED

When an item is added to a Sales Transaction, the enhancement will check if the Ship To’s Country Code is prohibited for the Item. If so, the Item will not be allowed.

Condition: Ship To-ALLOWED, Bill To-ALLOWED

When an item is added to a Sales Transaction, the enhancement will check if the Ship To’s Country Code is prohibited for the Item. If not prohibited, it will next check if the Bill To’s Country Code is prohibited for the Item. If not, the Item will not be allowed.

Condition: Ship To-ALLOWED, Bill To-NOT ALLOWED

When an item is added to a Sales Transaction, the enhancement will check if the Ship To’s Country Code is prohibited for the Item. If not prohibited, it will next check if the Bill To’s Country Code is prohibited for the Item. If it is prohibited, the Override Entry window will open (see next Section).

SOP Line Ship To Address ID:

The Ship To Address ID field and Lookup will be disabled on the Sales Line. The Ship To cannot be changed on a per-line basis.

Override Entry:

When a user enters an item on a Sales Transaction where the Ship To Address Country Code is allowed, but the Bill To Address Country Code is restricted, the following window will open requiring a User ID and Password to continue:

C:\Users\Karen\Documents\Clients\MRP\Biolase\Bill To User Approval.jpg

Field

Function

User ID

User will enter or select their User ID from the Lookup

Password

User enters their corresponding Dynamics GP Passwork

If an authorized user is not available to provide the override, or cannot provide the correct User ID and Password, the Item will NOT be allowed on the transaction. Once an Override is provided for a Transaction, it applies to all new lines added to the transaction (the Override is only provided once for the document). A record will be kept of which documents were overridden, by who, and when.

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

Contact Me (willoware.com)

Customization DS1020 Sort RM Cash Apply by Document

Customization DS1020

Sort RM Cash Apply by Document

Problem Definition:

ACME enters an Invoice (i.e. 001234), and then may also add Debit Memos and/or Finance Charges using the Invoice Number as a prefix (i.e. 001234DM, 001234FC, etc.)

When they receive payment, it is difficult to find all of the related documents because the Apply Cash Receipts window sorts by Document Type and then Document Number.

ACME would like the window to sort by Document Number.

Solution Overview:

The Apply Cash Receipts window will sort automatically by Document Number.

Design Features:

Apply Cash Receipts

There is no user interface for this enhancement. The Apply Sales Documents scrolling window will sort by Document Number, then Document Type, so that all “related” Document Numbers are sorted together.

Table Description automatically generated

Assumptions/Requirements:

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

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

Contact Me (willoware.com)

GP PowerPack 2023-01-07

Release Date: 7-JAN-2023
GP Versions: 12/14/16/18
GP PowerPack Build: 7.164
* Updated API Key (see //willoware.com/lastpass-hack/)
* Bank Deposit Filters: NEW- Added Deposit Slip Preview window that shows a list of only the cash receipts marked for deposit.

The new Deposit Slip Preview windows is an efficient way to quickly confirm the cash receipts you have marked for deposit.   You can keep the Deposit Slip Preview window open while marking deposits, and it will refresh automatically as you mark receipts, so you can keep track of where you are in a pile of checks!

LastPass Hack

If you have not heard about the LastPass hack, you can find lots of information about it on the internet.  Here is the nutshell:

  • Hackers acquired a copy of the entire LastPass customer password database
  • Changing your LastPass master password is pointless now because the hackers have a copy of the entire database
  • Passwords are encrypted, but the web-address and “other” information is unencrypted.  This means hackers can look at the data and target a customer’s password vault that has bank accounts, for example
  • It is only a matter of time before hackers can use automation to guess your Master Password and get access to everything

We used LastPass at WilloWare.  NONE of our customer data in the LastPass vault.  But what it does contain is the API key our software uses to:

  • Create a new support case.  Such as when you click the “Send To WilloWare” button on our About window
  • Send an error message to us from the “Ooops” window
  • Retrieve a new or updated Registration Key by clicking the “Get Key Online” button on our Registration window

The old API key could, in theory, be used to access our Zendesk account and send phishing emails to our customers.  This has NOT happened.  To ensure it cannot happen we have deleted the old API key and will be including a new API key as we release new builds of our products and customizations.

Effectively immediately you will not be able to create a new case, submit error messages, or retrieve a new Registration Key through our software.

If you install an update to any of our products or customizations with a build date after 5-JAN-2023 it will have the new API key and normal functionality will return.

  • As of 8-JAN-2023 all products have been updated with the new API Key

Customization DS1417 Additional Description Field on RM Transaction

Customization DS1417

Additional Description Field on RM Transaction

Problem Definition:

ACME needs a second Description field added to the Receivables Transaction Entry. This field also needs to be accessible via SmartConnect.

Design Features:

WilloWare will use Virtual Fields to add an additional string field to Receivables Transaction Entry for the user to enter a second Description field. The field will be located in the following location and labeled Description 2. Due to limitations of Virtual Fields, this field cannot be included in the tab sequencing with the other fields.

Graphical user interface, text, application Description automatically generated

A matching field will also be added to Receivables Transaction Inquiry Zoom.

When a value is entered into this field and the transaction saved, the additional Description value will be saved to a custom table. This table can be joined to the RM Transaction table and will have the following fields:

Document Type – Integer. Key Field

Document Number – String. Key Field

Description 2 – 60 Character String Field

The name of the table will be provided by WilloWare so ACME can use it for importing and reporting.

Assumptions/Requirements:

  1. The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables unless otherwise noted.
  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 about this design, or any other WilloWare customization or product, please contact us:

www.willoware.com/contact-me/

Customization DS1248 Certificate of Insurance

Customization DS1248

Certificate of Insurance

Problem Definition:

ACME needs to track which vendors must have a Certificate of Insurance and the Expiration Date of the Certificate. Additionally, when the Certificate expires, they need to have the Vendor automatically put on hold.

Solution Overview:

A new “Additional” window will be added to Vendor Maintenance which will be used to enter/maintain the Certification of Insurance Information.

A login routine will fire when the first user logs-in for the day. The routine will check for expired Certificates and put those vendors on hold.

Design Features:

Certificate of Insurance

Navigation: Vendor Maintenance >> Additional >> Cert. of Insurance

Text, table Description automatically generated

This window is used to enter/maintain/update a Vendor’s Certificate of Insurance information.

Field

Function

Vendor ID

Displays the Vendor ID from Vendor Maintenance. A Vendor must be displayed in Vendor Maintenance before the Certificate of Insurance window will open.

Cert. of Insurance Req.

Mark this box to indicate that the Vendor must have a Certificate of Insurance.

Expiration Date

Enter the expiration date of the Certificate of Insurance.

Vendor Hold

The first user to log-in to GP each day will trigger a routine that puts Vendors on HOLD if they are required to have a COI and its Expiration Date has passed (i.e. Expiration Date < today).

Graphical user interface, application Description automatically generated

Assumptions/Requirements:

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

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

Contact Me (willoware.com)

Customization DS1320 Vendor Contract Pricing

Customization DS1320

Vendor Contract Pricing

Problem Definition:

While testing WilloWare’s Vendor Pricing module prior to purchasing and implementing it, ACME uncovered several requirements that could not be met by the module, and WilloWare determined that it would not be cost effective to modify the core product to address these requirements. Specifically, ACME needs to maintain the Vendor Pricing as a “Contract” and capture additional information pertaining to each contract, and they need pricing to be determined based on the Required Date rather than the Release Date.

ACME needs to report on the Quantity Limit on a contract, the Quantity currently on PO, and the Quantity Received. There needs to be a clear link between the Contract and the PO Lines created based on that Contract. Reporting will be created by RBC and/or their Partner.

One of the required Contract fields is “Threshold Percent”. When the total quantity on PO is within a specified percentage of the Contract Total Quantity (say 5%) it triggers warnings and alert emails, as follows:

  • If creating a PO for the Item-Quantity will bring the total purchased within the Threshold Percent of the Contract Total Quantity, warn the user that the order will be within the Threshold Percent of the contract but allow them to continue (i.e. “Purchasing this item brings the contract within 5% of the contract total”). Email a notification to the Notifications Emails specified on the Contract.
  • If creating a PO for the Item-Quantity will bring the total purchased to 100% or more of the Contract Total Quantity, warning the user that the order will exceed the contract, but allow them to continue (i.e. “Purchasing this item brings the contract over the contract total. The PO will be placed On Hold.”). Email a notification to the Notifications Emails specified on the Contract. Also, put the PO on HOLD.
  • If creating a PO for an Item where the Required Date is after the End Date of the last available contract, the software will present a warning but allow them to continue (i.e. “The End Date for this Contract has expired.”) For example, if the Required Date is in August but the last available Contract has an End Date of July 31. Email a notification to the Notification Emails specified in the Contract.

The conditions above could result in multiple warning conditions. When that happens, the warning should provide the user with both.

The Threshold Percent and the Notifications Email Addresses will be stored in GP, but email alert will be handled via a SQL job created by ACME and/or their Partner.

The “warnings” mentioned above will be displayed inside Dynamics GP.

See the Solution Description section for the Contract fields.

Design Features:

Contract Maintenance

Navigation: Cards >> Purchasing >> Contract Maintenance

Graphical user interface, table Description automatically generated

Field

Function

Contract ID

Start a new contract by creating new Contract ID. Click the NEW button to have the system auto-generate a new Contract ID. The Contract ID will be created using the 4-digit year and an incrementing number. For example: 202200001. This is a required field.

Description

Enter a description for the contract

Vendor ID

Enter a Vendor ID or select one from the lookup. This field is required.

Contract Number

Enter the Contract Number from the contract document provided by the Vendor.

Start Date/End Date

Enter the Start/End Dates for the contract. Both are required and End Date must come after Start Date. See Start Date/End Date controls below.

Quantity

Enter the contract quantity. Quantity needs to be greater than zero. This is a required field.

Warning Threshold

The percentage entered here affects when warnings appear in GP. For example, 5% will cause a warning to appear when adding an item to a PO and the quantity will bring the total ordered on the contract to within 5% of the Contract Total Quantity. 0% will cause no warnings to appear until the Total Quantity is reached/exceeded.

Notifications

Enter one or more emails for people to be notified when the Warning Threshold is reached and when the Contract Total Quantity is reached/exceeded.

VIEW

Items on Contract or Purchase Orders. See below for more details.

SAVE

Saves the Contract and clears the window.

DELETE

Asks user: Do you want to delete this contract and all linked Vendor Price Lists? If the user answers YES, the contract and all linked price lists will be deleted.

CLEAR

Clears the window without saving changes. NOTE: date changes are saved to the Contract and linked Vendor Price Lists immediately. Clicking Clear after a date change does not undo the date change.

NEW

Creates a new Contract ID

DELETE ROW

If a Vendor Price List is attached, the user will be ask:

Do you want to remove this line and delete the linked Vendor Price List?

If the user answers YES, the line will be removed and the price list deleted.

If no price list is linked, the line will be deleted without prompting.

NOTE

Clicking the Note button opens up a window where the paperclip opens the Doc Attach window. This will allow ACME to attach scans of the Contracts to the Contract in GP.

Start Date/End Date Controls

When creating a new contract, as an item is added to the contract, the software will check that it does not conflict with another contract for the same Item and same Vendor. For example, if the new contract is for APR-1 to JUN-30, and the user enters ITEM-A, but that Vendor already has a contract for ITEM-A with a period of JAN-1 to JUN-30, the user will be warned of the overlap and prevented from using the item. An item can only be added to a contract when there is no overlap between contract start/end date for the same Item-Vendor.

When changing dates, the software will perform a check to ensure the date change would not overlap with an existing contract. Changing dates on an existing Contract will primarily occur if the Contract Total Quantity has not been reached and they extend the End Date to finishing consuming the total quantity. The check will be performed as follows:

1. Does the Vendor have any other Contracts where the new date falls with the Start/End dates of the contract? If not, then the change is allowed. If so, then:

2. Does the contract have ANY items in common with the current contract? If not, then the change is allowed. If so, the user will be warned as follows:

“Contract ID 202100003 / Contract Number 20209902231 has conflicting Start/End Dates. The date change is not allowed.”

At that point the date will revert to the original value.

If a date change is allowed, and if Price Lists exists in Vendor Pricing Maintenance for the Contract, changing the Start/End Dates will prompt the user: Do you want to change the Start/End Date on all linked Vendor Price Lists? If the user answers YES, the new date will be rolled down to all linked Vendor Price Lists. If the user answers NO, the date will revert to its original value.

Items On Contract View

To create a Vendor Price List for the contract, first add one or more Items to the contract. Items must be added to the contract before pricing can be created.

Specify the Quantity you expect to purchase of each item. The window will ensure that the total quantity entered for all items equals the Contract Total Quantity. You will not be allowed to save the contract or exit the window until the Item Quantity matches the Total Quantity. Attempting to Save, Clear, Scroll, Lookup, etc will be prevented, and the user warned, until the quantities match.

If there are NO items on the contract, the contract can be saved with whatever Contract Total Quantity has been entered.

After entering one or more items, click on an item, then click the Expansion Button (blue arrow) to open the Vendor Pricing window.

Graphical user interface, application, table Description automatically generated

The Vendor Pricing Maintenance window will default to the Default Purchasing U of M. Item Number and Vendor ID will be populated automatically based on the Contract. Start Date and End Date will also default from the Contract and will be locked.

Purchase Orders View

Graphical user interface Description automatically generated

When PO’s have been created based on the Contract, they will appear here in the Purchase Orders view. Click on a row in the window, then click the PO Number zoom (PO Number column header) to open the PO in the PO Entry window.

Contract Lookup

Table Description automatically generated

Opens from the Lookup button next to Contract ID.

Field

Function

Contract ID

Defaults to whatever portion of the Contract ID was entered on the Contract Maintenance window. This field will restrict the window to all contracts that contain the value entered into the Vendor ID field. For example, entering “2021” will display all contracts where the Contract ID contains “2021”.

Vendor ID

Enter a Vendor ID, or a portion of a Vendor ID. This will restrict the window to all contracts that contain the value entered in the Vendor ID field. For example, entering “33” will return all contracts where the Vendor ID contains 33.

Item Number

Enter an Item Number, or a portion of an Item Number. This will restrict the window to all contracts that contain the value entered in the Item Number field. For example, entering “DCP” will return all contracts that are for an Item Number containing “DCP”.

Contract Num

Enter a Contract Number, or a portion of a Contract Number. This will restrict the window to all contracts that contain the value entered in the Contract Number field. For example, entering “940” will return all contracts that have a Contract Number containing “940”.

View

Options are ACTIVE and ALL. Active shows only contracts with a Start Date on or after today. All shows all contracts.

Any of the fields at the top of the window can be used alone, or in combination, to restrict the list of contracts displayed.

Controls and Enhancements

See the Problem Definition section for the conditions that will cause warnings to be displayed, and the language used on the warnings. This is referred to below as the Warning Conditions. The warnings will appear in the following locations:

Purchase Order Generator

The Vendor Pricing Inquiry window will be modified to have a large “status” box at the bottom of the window. The warning will be displayed in a YELLOW BOX at the bottom of the window with bold black text. When the focus is in a line in the PO Generator window, and purchasing the item would trigger a Warning Condition, the warning message will be displayed at the bottom of the Vendor Pricing Inquiry window. The Vendor Pricing Inquiry window will be modified to display the Contract NUMBER.

Graphical user interface, application, table Description automatically generated

NOTE: The GoTo button will include an option that provides access to the Contract Maintenance window.

Purchase Request Resolution

The Select Cost window will be modified to have a large “status” box at the bottom of the window. The warning will be displayed in a YELLOW BOX at the bottom of the window with bold black text. When the focus is in a line in the PRR window, and purchasing the item would trigger a Warning Condition, the warning message will be displayed at the bottom of the Select Cost window. The Select Cost window will be modified to display the Contract NUMBER on the expanded scroll window line (i.e. next to Vendor Name).

Graphical user interface, application Description automatically generated

NOTE: A GoTo button will be added to the Select Cost window to provide access to the Control Maintenance window.

Purchase Order Entry

The Vendor Pricing Inquiry window will be modified to have a large “status” box at the bottom of the window. The warning will be displayed in a YELLOW BOX at the bottom of the window with bold black text. When the focus is in a line in the PO Entry window, and purchasing the item would trigger a Warning Condition, the warning message will be displayed at the bottom of the Vendor Pricing Inquiry window.

The Vendor Pricing Inquiry window will be modified to display the Contract NUMBER.

Graphical user interface, application, table Description automatically generated

Changing the Quantity on the PO Line may cause the warning to appear, or disappear, if the quantity causes the Warning Condition to alter.

NOTE: The GoTo button will include an option that provides access to the Contract Maintenance window.

PO Line Link to Contract

When a PO Line is created, regardless of the source (i.e. PO Generator, Purchase Request Resolution, or PO Entry), the enhancement will link the PO Line to the Contract (assuming the item is contracted. This does not apply to non-contracted items). The software will always link a PO Link to the contract from which it was created. Even if the Contract Total Quantity has been consumed, and/or the End Date has passed. Such conditions are not normal and will result in the warnings and emails previously covered.

The linking is important because the links allow a calculation of the total quantity ordered on a Contract. Creating the link implicitly means the PO Line Quantity will be subtracted from the linked Contract Total Quantity.

The linking will occur as follows:

  • The PO Line ProjNum field, which is not visible on the User Interface, will be populated with the Contract ID. This will allow for easy linking on reports between PO Lines and the Contracts that generated them.
  • The PO Line Comment Text field (and Comment_1) will be populated with: “Cont#” and the Contract NUMBER. For example:

Graphical user interface, application Description automatically generated

Putting the Contract NUMBER into this location will cause it to print on GP reports. If needed, ACME can add additional text below the Contract NUMBER line to have additional information print on the report.

Vendor Pricing

The Vendor Pricing will be changed to use REQUIRED Date rather than Release Date.

  • Purchase Request Resolution has a Required Date field. That will be used instead of Release Date.
  • Purchase Order Generator does not have dates. It is assumed the requirement is “now”. All pricing will be selected based on PURCHASE ORDER DATE from the Generate Suggested Purchase Orders window.
  • Purchase Order Entry: Vendor Pricing will use the Required Date from the Purchasing Date Entry window. In the event a PO is created with different Required Dates on each line, Rise will need to change the Required Date in the Date Entry window BEFORE adding a line. Then enter the PO Line. Then change the date again as needed.

Graphical user interface, table Description automatically generated

  • The “U of M” label will be changed to “Purch U of M” on Vendor Pricing Maintenance and Inquiry will be changed.
  • When the Vendor Pricing window is opened directly (i.e. not from a Contract line item), it will check if any Item/Vendor combination entered into the window is already on a Contract. If so, it will not allow the user to continue. The Vendor Pricing for contracted items must begin from the Contract Maintenance window. This prevents accidental creation of a price list for an item that conflicts with a Contract. Non-contract items can be set up in the Vendor Price Maintenance window without any restrictions.

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 at:

Contact Me (willoware.com)

MFG PowerPack 2022-12-15

Release Date: 15-DEC-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.211
* Serial Number Mass Entry: The paste field has a limit of 32,000 characters. To insert a very large number of serials, a user would need to paste close to the capacity of the window, insert, then repeat the process. This build addresses an error where subsequent paste/insert would generate a duplicate key error. (#202202385)

MFG Import 2022-12-12

Release Date: 12-DEC-2022
GP Versions: 12/14/16/18
MFG Import Build: 3.59
* Routing Import: (1) Added ability to export Map, (2) Fixed issue with import from excel where an error occurred because it was incorrectly attempting to execute a status update that occurs with SQL table imports.
* BOM Import: Updated the Map Export routine so it provides the default value used then the field map is “Default”

MFG PowerPack 2022-12-08

Release Date: 8-DEC-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.210
* PowerATP: addressed issue with Item Number zoom that did not correctly identify the Security Role POWERUSER so it could not open Item Maintenance or Item Inquiry (#202202316). However, this issue was not specific to the PowerATP window, any Item Number zoom in MFG PowerPack would have experienced the same issue, as will several other zooms.
* NEW TWEAK-Turn off Job Cost Menus: this turns off the Job Costing right-click menus which allows GP to again display the normal right-click menu to Insert Row, Delete Row, Copy, etc.

Job Cost Menus ON:

Graphical user interface, application, table Description automatically generated

Job Cost Menus OFF:

Graphical user interface, application, table Description automatically generated

MOGenerator 2022-12-06

Release Date: 6-DEC-2022
GP Versions: 12/14/16/18
MOGenerator Build: 4.111
* MORI: “Check for Shortages”–fixed an issue in this routine that was not accounting for phantoms and therefore giving an inaccurate “picklist shortage” error when non existed. (#202201984)

Customization DS1394- PO Generator Enhancements

Customization DS1394

PO Generator Enhancements

Problem Definition:

ACME would like to add the following functionality to the PO Generator windows:

  • They need to add a Note to some lines and have the Note added to the PO Line Comment when the PO is created.
  • They need an indicator that allows them to quickly see which lines have Notes in the PO

Generator Preview window.

Graphical user interface, application Description automatically generated

  • Item Maintenance Options User Defined #5 is used to store “Average Monthly Use”. They need to see this number on the PO Generator windows.

Additionally, ACME would like to be able to identify which POs came from PO Generator and have them automatically put On Hold until reviewed by a user.

Design Features:

PO Generator Enhancements

Navigation: from either the Suggested PO Preview window, or the Suggested PO Detail window, select Additional >> Add/Edit Note

Table Description automatically generated

Graphical user interface, text Description automatically generated

A window will open where you can enter a note (up to 500 characters, the PO Line Comment is limited to 500 characters). Once a note has been added, the Vendor Name field will show “** NOTE”—this change is on the user interface only and will not affect the Vendor Master or the Purchase Order (“**NOTE” will NOT flow through to the PO).

Graphical user interface, application Description automatically generated

The Average Monthly Use quantity for an Item will be displayed in the Title Bar of the windows. In the PO Generator Preview window the Avg Monthly Use quantity will change when different lines are selected.

Graphical user interface, text, application Description automatically generated

The PO Generator Item Note will be carried over to the PO Line Comment when a PO is created.

Purchase Orders created from PO Generator will automatically have the HOLD flag set on the PO. Doing this will have update the following fields in the PO Header (POP10100):

  • HOLD = 1
  • ONHOLDBY = User ID who was running PO Generator
  • ONHOLDDATE = User Date when the Hold was added

To ensure that POs created by PO Generator can be pulled into a SmartList, the USER2ENT field in the PO Header (POP10100) will be set to POGEN. This does NOT need to exist as a User ID in GP.

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 at:

Contact Me (willoware.com)

Customization DS1438 SOP Invoice Lines from List

Customization DS1438

SOP Invoice Lines from List

Problem Definition:

ACME is using WilloWare’s SOP-POP Multi-Link module. (SOP-POP MultiLink (willoware.com)

They have Sales Orders with several lines, and as the sales lines are received, SOP-POP Multi-Link automatically moves the quantity bucket form Qty to Back Order to Qty to Invoice. ACME needs the ability to specify which lines get transferred to invoice.

Solution Overview:

This enhancement will be active from the Sales Transfer Documents window when accessed from Sales Transaction Entry (not Sales Batch Entry)

Navigation: Sales Transaction Entry >> Transfer Action Button

Graphical user interface, text, application Description automatically generated

The enhancement will only be active when transferring an Order to an Invoice. See next section for more details.

Design Features:

SOP Transfer Line Selection

Navigation: Sales Transfer Documents>> Additional >> Transfer Line Selection

Table Description automatically generated

By default, GP will transfer ALL lines that are eligible to be invoiced to a single invoice. The SOP Transfer Line Selection window will allow ACME to select only specific lines and quantities to be transferred. If this window is not used during the transfer process, then all lines will be transferred (default behavior).

Field

Function

APPLY

Sends the marked/unmarked status back to the sales order. If APPLY is not clicked, then any changes made will not be applied.

CANCEL

Closes the window without making changes.

MARK All

Marks all lines in the window.

UNMARK ALL

Unmarks all lines in the window.

Sales Order

Displays the sales order being transferred.

Item Number From/To

Allows the user to enter an item number or a range of item numbers to filter the list.

Scrolling Window

Displays all the sales lines with a Qty to Invoice > 0. By default, all lines will be unmarked. Use the checkbox to indicate the line should be transferred.

Transfer Qty

This is the quantity that will be transferred to invoice. By default, this value will be the maximum amount (Invoice Qty), but can be reduced if only part of the line is to be transferred. Partially transferring a line will allow the line to be transferred multiple times until all the Qty to Invoice has been transferred.

If lines have been marked, the Sales Transfer Documents title bar will be updated to include the text

“ – Sales Line Selections”.

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

When the user clicks TRANSFER, only line quantities marked will be moved to invoice.

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

Contact Me (willoware.com)

GP PowerPack 2022-11-12

Release Date: 12-NOV-2022
GP Versions: 12/14/16/18
GP PowerPack Build: 6.162
* NEW * FAST Sales Serial Entry: Replaces the Sales Serial Entry window with one that is FAST with large quantities of serial numbers. It has Serial Number and Bin search fields that allow locating records using “contains”, “begins with” and “ends with” search (plus other options). Select multiple serial numbers by “marking” them, rather than having to click on the serial number and then click insert.

GP PowerPack FAST Sales Serial Entry

Price $1800 Demo Manual

FAST Sales Serial Entry replaces the standard Dynamics GP Sales Serial Entry window with one that can easily handle very large number of serial numbers. In GP2013 Microsoft added the ability to “multi-select” serial numbers which required changing the “Available Serial Numbers” scrolling window to a list view window. A list view is similar to the SmartList window, it allows multi-select but it is very slow to fill with data. If you have several hundred serial number, or more, the standard Sales Serial Entry window takes a very long time to open because the list of Available Serial Numbers needs to populate first with ALL serial numbers.

The FAST Sales Serial Entry window replaces the list views with scrolling windows which are very quick to load. The FAST Sales Serial Entry also provides:

  • The ability to search for serial numbers using contains, begins with, ends with and more
  • The ability to restrict by bin using contains, begins with, ends with and more
  • The ability to quickly choose a serial number by marking it (rather than having to select and click insert)

The window will open automatically instead of the standard GP Sales Serial Number Entry window. It works with Sales Transaction Entry and Sales Separate Fulfillment.

Graphical user interface, table Description automatically generated

Serial Number Search: Choose a search operation (Is, Is not, Contains, etc), then enter a search term and press the TAB key.  The Available Serials window will redisplay.  Click the red X to clear the field and refresh the list.

Bin Search: Choose a search operation (Is, Is not, Contains, etc), then enter a search term and press the TAB key.  The Available Serials window will redisplay.  Click the red X to clear the field and refresh the list.

Auto Select: Auto Select will pick the number of needed serial numbers based on the Item’s Valuation Method.  For example, LIFO will pick serials from the bottom of the list first where FIFO will pick from the top of the list.

MFG Import 2022-11-11

Release Date: 11-NOV-2022
GP Versions: 12/14/16/18
MFG Import Build: 3.58
* BOM Import: (1) fixed issue with Valuation Method validation that was preventing import of standard cost components into an actual cost finished good. (2) added ability to export the BOM ImportMap setup (see GoTo Button on Import Map Setup)

MOGenerator 2022-11-08

Release Date: 8-NOV-2022
GP Versions: 12/14/16/18
MOGenerator Build: 4.110
* MORI: (1) Now truncates the error log (note) at the bottom (oldest errors) for an MO if it reaches the maximum length of a note, and then it continues to add new errors to the top, (2) Added check for a locked BOM before attempting to process an MO Receipt, (3) Added a new “next MO” selection routine that is entirely SQL based to reduce the possibility of collisions between two GP client processors.

 

Should I update GP?

Yes.

There are tens of thousands of GP users poking around every nook and cranny of the software every day.  Every release contains not only new features, but bug fixes.  Even after decades of heavy use people are still able to come up with unique things to do to the software that shake out a previously unknown issue, and Microsoft fixes it.

A bit off topic for this post…but consider for a moment the implication of usage history (or lack thereof) with a newer ERP package.

A major benefit of Annual Enhancement is being able to get the latest version of the software which includes new features that you may use, and fixes that may be relevant to you now and perhaps ones you WILL wish you had in the future if you postponed updating.

A few years back WilloWare changed our build numbering logic to what we call a “unified build number”.  In the past, each build of our software for each GP Major version had its own build number.  For example, GP PowerPack would have looked like this:

  • v12.2.137 (for GP2013)
  • v14.2.80 (for GP2015)
  • v.16.2.48 (for GP2016)
  • v18.2.20 (for GP2018)

We have always maintained ONE code base for ALL GP versions, and within that one code base were all of the options needed to make it work on the different versions of GP.  If something was different in GP2016 versus GP2018 we would add “switches” in our software so it could figure out which version of GP was in use and use the correct version of its code to be compatible with the version of GP.

The single code base means that new features and fixes are available across all supported versions of GP (currently we’re still supporting GP2013).  To reflect this, we started using one build number across all versions of GP.  We compile the code separately for each GP major version and that is shown in the first part of the build number (i.e. “12”).  The next two numbers are internal.  For example:

  • v12.2.138
  • v14.2.138
  • v16.2.138
  • v18.2.138

The “2.138” is our internal build.  “2” will change to “3” if there are SQL object changes, and the final number always increments with each release (so “138” to “139”).

We just completed updating all of our products for GP18.5, and the ReadMe file for the products will note something like “Updated for GP18.5 Release”.  Does this mean it only has changes relevant to GP18.5?  No.

Our products have a large amount of “common” code–it is the same in every product.  If you open the About window for one of our products, at the bottom you will see a section like this:

This is reporting on the state of our internal reusable code modules and the asterisk indicates there is a newer version of that module.  The WW Resources are how our products interact with GP and SQL Server.  For example, they control how we open a window, or execute a query in the database.

We have so many users hammering away in GP and our products that they find things, and we try to fix or improve them quickly.  If it is critical, we will roll out new builds of all modules immediately, however many changes are good to have but not critical.  For example, we recently made some changes to our SQL module to improve performance and robustness when faced with server-side failures.

This type of change is not noted in the ReadMe file of your WilloWare product, but it is tracked internally in the change history each WW Resource.

Every release of our software applies to every version of GP, so the “GP18.5” releases, at a minimum, contain the latest updates to all of the “internals” of whatever product you have.

The primary benefit of Annual Enhancement is the ability to receive these updates, and we are always working hard to make our software the best it can be.  When you ask, “Should I update my WilloWare software?” the answer is Yes.

MFG Import 2022-11-07

Release Date: 7-NOV-2022
GP Versions: 12/14/16/18
MFG Import Build: 3.57
* Routing & BOM Imports: (1) addressed issue with error reporting module that caused it to incorrectly identify that an import had errors, (2) fixed yellow highlight on Error Log button so it correctly switches between yellow and normal background when there are errors/no errors, (3) changed label on Errors window button from “Re-Process” to “Clear Error Log”, (4) Import button now automatically clears error log if it hasn’t already been cleared by the user.

MFG PowerPack 2022-11-03

Release Date: 3-NOV-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.205
* Quick Disassembly: fixed issue created in build 10.198 which added the an option to merge quantities for the same item into one line. When disassembling from an MO, this change resulted in adding the previous line’s quantity to each new line. (#202201900)

MOGenerator 2022-11-01

Release Date: 1-NOV-2022
GP Versions: 12/14/16/18
MOGenerator Build: 4.109
* Updated for GP18.5 Release
* MORI Error Log Window: (1) addressed issue in the Date Restriction field that cause it to not restrict by the date entered (#202202022), (2) added Date search criteria so window can be restricted by date equal to, greater than/equal to, less than/equal to, or not equal to, (3) Next/Previous buttons in expanded scroll now move between records correctly.

MFG PowerPack 2022-11-01

Release Date: 1-NOV-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.204
* Vendor Pricing: addressed issue where the PO Entry window was not allowed to open after creating a PO from the MRP-Planned Orders window because the Vendor Pricing window was still open. Vendor Pricing now automatically closes after successful creation of the PO so that the PO Entry window can open. (#202202037)

MFG Import 2022-10-31

Release Date: 31-OCT-2022
GP Versions: 12/14/16/18
MFG Import Build: 3.56
* Routing & BOM Imports: addressed issue with error reporting module that could cause an ‘incorrect syntax’ error when importing from Excel and there is invalid data the file. The error reporting would still correctly reports all errors and the import would run fine if the file data is all valid.
* Boo! Happy Halloween from WilloWare!

MFG PowerPack 2022-10-27

Release Date: 27-OCT-2022
GP Versions: 12/14/16/18
MFG PowerPack Build: 12.203
* FULL INSTALLATION ROUTINE REQUIRED
* This release includes a new SQL table
* Updated for GP18.5 Release
* BOM Alternates-Picklist: this release contains a major update to the Picklist Alternates window. Previously the window assumed that Primary-Alternate items were swappable (i.e. if you are short 8 of the Primary you can use 8 of the Alternate). The Picklist Alternates window can now handle two types of Primary-Alternate Relationships. One where the items are interchangeable and you could use some of both in a single Manufacturing Order, and one where you can use the Alternate in place of the Primary, but not both at the same time. Often when items can be measured in decimals, there is not a good way for the software to determine if one can be used to meet a shortage of the other, or if it must be used in place of the other. There is now a default “alternate item usage” setting, and also the ability to specify that setting per Primary-Alternate Item relationship. Color coding in the window now uses colored Dots (for Primary-Use Up Item relationships) and colored Squares (for Primary-Alternate Item relationships). The color coding has been refined to provide more information about the availability and/or shortage of the Primary-Alternate/Use Up items. NEW SETUP IS REQUIRED BEFORE USING BOM ALTERNATES.
* Item Class Serial/Lot Mask: The setup window has been updated so that when a new Template Item is used the window will generate the next available serial/lot number and use that as the starting point for all items in the Item Class. Previously it attempted to retrieve that “maximum” existing last generated serial/lot number, which could cause it to inadvertently flip to an incorrect last serial/lot.