Dynamics GP

It would be helpful o be able to inactivate a Supervisor Code (HR & Payroll - Setup - Supervisor) and have the ability to restrict a Supervisor lookup based on Active/Inactive Supervisor Codes.

When using PTE Timesheets for Project Accounting, if the start date for your Timesheet Periods begins in the previous year the user will be prompted with a message that states, "The timesheet for this period has been approved or submitted. Do you want to enter another timesheet for this period?" While it does not hurt anything or affect payroll, it can be misleading to users and cause them to second guess if they had previously entered time for that period already or not.

The reality of the issue is that the pay period 1 begins in 2024, but ends in 2025. The system sees that the user already entered data for period 1 and prompts them with the message. However, this is period 1 for 2025, and it is looking at period 1 for 2024 which began in 2023 and ended in 2024.

The suggestion would be add code for this specific scenario to avoid user confusion and worry. While it does not hurt anything, it can be misleading and a change would avoid this.

Good afternoon,

Issue: - PO's are not pulling the system date.

When the user opens the existing PO, the system date is flipping back to the PO creation date, and the user needs to manually change the date.

A PO return that is not posted does not allocate inventory. The reason it is not posted is because they are awaiting the credit from the vendor but would like the inventory allocated so that it cannot be sold.

Customer had a new user enter a JE number in 2024 that was used in 2017 - because it was a different year - it was allowed.

Can you add an option in the GL setup, like is in Payables, to not allow override the JE number at transaction entry? Seems like it would be an east fix.

When using fulfillment orders, we cannot VOID them, only delete, if them import incorrectly. This is causing a major issue with customers because maybe after a few days, a fulfillment order is found to be wrong, so they delete it, then it resets the next master number, so when another import is done, it crashes because it continues on with the next number and tries to use the next consecutive numbers.

What would happen if we decided to not use a master number at all, - would it allow us to void the fulfillment order?

Also, do we need to check the box to maintain history of voided SOP documents?

It appears that there are no existing settings or configurations that would allow Customer\Vendor transactions to post 'Through' the General Ledger by default.

Typically, if a module lacks specific setups for this purpose, the next place to check would be under the general posting settings (Tools>Setup>Posting>Posting). However, upon examination, there are no particular setups for Customer/Vendor Consolidation in this section either.

The lookup screen for GL accounts does not allow users to only show "Active" accounts. Also, there is not an option to "Set as Default View".

Add a Navigation List for Inventory Batches to allow for printing multiple Edit Lists, deleting empty batches, and posting 1 or more from the Navigation List.

Currently when items are entered on orders, the Date Shipped is auto filled with the User Date. Ideally, this date would be blank at the order stage. Currently, when you transfer the order to Invoice, this date is not updated.

Example: The order is entered on March 1st the Date Shipped field per line is automatically populated with the User Date of 05/01. When the user transfers the Order to Invoice, Shipped Date on the Line Item still shows the original User Date when the order is created. The only way to update this field is to manually go to each line on each invoice to update.

Request: Make the Actual Date Shipped field were editable at the Header Level on the Sales Order and Sales Invoice and prompt user to see if this change should be Rolled Down (similar to date changes on PO documents).