Expense Request Package

[sarahh]

A few issues:

1) Initmenu script should probably ship as not enabled. After install, when a privileged user logs in, the Expense window is open on screen.

2) If you create a request without a short description in the header, the pop-up advising that a description is needed misspells description. Create a description - attempt to save with no 'Request Description'. Message will have description misspelled.

3) If you create a request with a completed header but no lines and SAVE, it will not save nor will it alert you to any issue. Should probably behave like SO and PO. Start a request, finish Header tab, Save. Request disappears.

[jstandring]

Fixed in attached Update V4.4.1

[sarahh]

The quote ability within the Expense Request Package is great. It'd be nice if we could request a quote, using the formatted report, from a vendor for Inventory items without it having to be linked to a Project. So, instead of through the Expense Request section, it could be from Planned Orders.

It could go like this: Planned Orders by Planner Code - choose Purchased item, right click, Quote Request...potential item sources show up and a Quote Request is generated based on that vendors part number and description from their item source.

[sarahh]

Thank you so much!

S

[sarahh]

The option to associate a Project with an expense requests disappears if the expense request is non-inventory. However, in the Purchase Order, both non-inventory and inventory items can be associated with a project. Also, inventory is spelled wrong within the Expense line item (see Non-Inventroy).

Steps to Reproduce:
Set up a Project. Begin creating an Expense request and notice that, when toggling between inventory and non-inventory the option to associate with Project disappears.

 

[jstandring]

Thanks for the feedback.

Will look into the fixes and resubmit when ready.

1) Initmenu script should probably ship as not enabled. After install, when a privileged user logs in, the Expense window is open on screen.

Answer: Agreed we removed the script from our live xTuple due to user feedback.

2) If you create a request without a short description in the header, the pop-up advising that a description is needed misspells description. Create a description - attempt to save with no 'Request Description'. Message will have description misspelled.

Answer: Will Correct the text

3) If you create a request with a completed header but no lines and SAVE, it will not save nor will it alert you to any issue. Should probably behave like SO and PO. Start a request, finish Header tab, Save. Request disappears.

Answer: Will add an warning message to inform the user.

-----------

The option to associate a Project with an expense requests disappears if the expense request is non-inventory. However, in the Purchase Order, both non-inventory and inventory items can be associated with a project. Also, inventory is spelled wrong within the Expense line item (see Non-Inventroy).

Answer: Will correct the errors.