Jolie Tanigawa-Dillon Solution Architect

Default Dimensions -In General Ledger>Main Accounts>Legal Entity Overrides>Default Dimensions - the user can define a fixed or no-fixed value. When the transaction(journal entry) is created using a fixed value - the user can change the fixed value - however when the voucher posts - the fixed value is entered on the voucher.

Default Currency- In Main accounts - when a user defines a default currency - the validate currency code option -Required allows a user to change the required currency however when the voucher posts - the required value is entered on the voucher.

Option #1 Idea: User should get a notification before posting to indicate the value will be changed upon posting.

or

Option #2 Idea: Fixed Value defined should not be allowed to be change on the line.

This idea will allow for the default financial dimensions to populate on the deduction workbench, driven by the main account assigned to the reason code, allowing the user to see default financial dimensions and change if needed.

The default financial dimensions that come from the main account should default on the deduction workbench write-off connecting the default financial dimensions to the deduction write-off reasons.

Fixed Dimensions coming from main account do work as no matter what financial dimensions the user selects, the system will post what is defined as fixed on main account, however this will not meet the expectation of "default financial dimensions" allowing the user to change as needed.

On the Asset Book details the asset lease status shows "closed" however on the lease details grid, the lease status shows "not yet acquired". The lease status on the book and the grid are not in sequence.

The control name is different for both fields.

Idea would be to use the same control name for both fields so the lease status is updated correctly on the grid.

When creating a timesheet, users are commonly required to enter an internal or external comment before moving onto the next day. We see this as a customization for several clients and would like to suggest an idea at the PMA Parameter level to add this control.

Project Management and Accounting>Setup>Project Management and Accounting Parameters

TimeSheet Tab -

Require Internal Comments - Toggle

Require External Comments - Toggle

Please vote on this idea.

When making corrections or write off's in Rebate Management, the changes are not reflected on the Original Sales order. There should be some way to see corrections or write off on each source order.

Here is a video of what I'm suggesting - https://app.usebubbles.com/maUhEfHSbGyPvzZnKnLWK1

In Project Operations, when a user must correct an expense entry- navigates to time & material backlog - user selects entry, then selects CORRECT ENTRIES - error when trying to correct expenses from vendor invoices that come from FinOps. "Some of the entries that you have selected were not added to this correction journal because they do not have a backing time or expense entry as the originating transaction." This error is referenced to the column external reference which indicates that vendor invoices are generated from an external reference.

No error when trying to correct expenses from expense reports that come from FinOps. This is an inconsistency in behavior as both vendor invoices & expenses reports are considered external references. Request is that the behavior works the same for both Vendor Invoices & Expenses from expense reports – and allows for the quick “correct entries” from the Time & material backlog.

Additional information, Vendor expenses use procurement categories assigned to project category.

Environment: Project Operations non-stock

Information: Microsoft time standard time zone is UTC - Universal coordinated time. When a transaction is made for actual transactions the transaction date uses the users specific time zones. The transaction date which is time zone independent shows the correct date.

Issue: When a user changes their local time zone from UTC, and their personalization to their local time zone, then the Document date/Accounting Date are one day off from the transaction date. This poses confusion and inconsistency.

Idea: Solution to make document date/accounting date consistent behavior with transaction date.

Business Value:

Improved decision-making, enhanced trust in the system, reduce risks