-
save or minimize transaction when Go To is selected on PO exists message
In GP2015 or later, a feature was added to warn a user if a PO exists for a vendor that a payables transaction has been entered for. If you click the Go To button, the transaction you were working on gets deleted and the PO Navigation window is opened to view PO's for this vendor. The message does not appear until the save button or the post button is activated. If the transaction had multiple distributions added this information will be lost and the user would have to start over again if there was no PO and the transaction should be entered in the Payables Transaction Entry window. I suggest that the Go To button minimize the window and then bring up the PO Navigation window for the vendor instead of deleting the transaction.
-
retroactive deferral to update Originating Master fields in GL Transaction
Currently when you use the Retroactive Deferral window to add a deferral to a posted Sales or Purchasing document the Originating document number and master id do not get populated in the journal entry and the drill back does not drill to Sales or Purchasing transaction. We would like it to work as if the deferral were created in the sub module and the Originating fields be populated in the GL.
-
post immediatly a reverse billing in Field Service
When a reverse invoice is processed in Field Service Utilities, it does not automatically create a Sales Credit Memo in SOP. A new invoice has to be created from Field Service for the same contract and then it will create the credit memo in SOP. This needs to be an immediate posting. -
delete VAT return requires system password
When trying to delete a VAT Return the system password is required. Would it be possible to remove the delete button is the VAT return has been completed and sent to HRMC instead of requiring the system password. -
Report for Future billings in Field Service
We would like to see a report to show future billings on a contract. -
Setup option to change the Bill on Date in Contract Maintenance
In Contract Maintenance, the Bill on Date defaults to the last day of the month and if you bill on any other day, you must remember to change this. It really does not make since to default to the last day of the month if it is a prepaid contract. This should be a setting in the Contract Type window just in case different contract types need a different billing day. What we do is default in the last day of the month based on the month in the Billing: Start Date field. So on a pre-paid, that is the same month as the Contract: Start Date month. If not pre-paid, it is the following month that defaults in to the Billing section and that EOM date is used. We do not have any options or settings that change this. -
utility to update the List Price on an item (not the price list)
Currently if we want to update the List Price on an item we have to use SQL to update the IV00105 table. It would be nice to have a utility like the Update Price List utilities that updates the List Price either by a percentage or an amount. -
Add employee Class to the Employee Card in UK version of GP
The Employee Class field is not available in the UK version of GP. Even though PR is not used in the UK, Employees are tied to Projects in Project Accounting and this field would be needed to default information to an employee.
-
cannot consolidate invoices if functional currency is different than customer currency
When you go to Customer Card>>Address>>Additional>>Service Extensions and try to mark the Consolidate Contract Invoices checkbox a message appears that it cannot be marked because of Multicurrency restrictions. This occurs because the company Functional Currency is not the same as the Customers Currency. We would like to be able to consolidate the contract invoices that are in the same currency, what does it matter what the functional currency is?
-
rolldowns for based on pay codes do not roll down to inactive employees
To replicate the issue, follow these steps:
1) set up 2 employees with an hourly paycode and a related OT paycode
2) inactivate only one of the employees
3) Update the rate on the master hourly paycode in pay codes setup
4) Roll down changes to ALL employees
5) Check the rate on the Master OT paycode in paycode setup to see that the OT rate has been updated to the amount in the related hourly paycode
6) Check the active employee and the OT rate has updated
7) Check the inactive employee and the OT rate did not update
Is there a reason that the OT rate does not update on inactive employees when the related hourly rate does update?
Per Microsoft:
- This functionality does not work for inactive employees, only active employees. Inactive employees were not considered when the rolldown functionality was created from the company setup level.
- The company set up level for inactive employees the rolldown feature does not work for based on pay codes.
- The employee set up level for inactive employees the rolldown feature does work for based on pay codes.
The rolldown should work for all paycode if the ALL employees is marked.
You’re offline. This is a read only version of the page.
