web
You’re offline. This is a read only version of the page.
close
  • Validation of Expense Report header financial dimensions

    Expense report line Financial Dimensions are validated currently against the setup in the GL module, such as the Configured Account Structures and Advanced Rule Structures. All GL transactions need to be validated the same way, whether they originate from expense report lines or the header.


    When a user clicks Submit to workflow, if there are any invalid account + financial dimension combinations, they will receive an error message and must correct the accounting before it will allow submit to workflow. The same validation should occur at the Header level of the expense reports to avoid users submitting expense reports with invalid header (AP) account + financial dimension combinations.

  • When Procurement category used for Purchase Order line detail and Unit is left blank, system is rounding Quantity ordered

    When using Procurement Category instead of Items or Products, the default value in 'Units' field on Purchase Order Line details is blank. If a user does not select a Unit from the drop down and instead leaves the value blank, then enters a decimal quantity in the 'Quantity ordered' field, the system will round the value to whole units.


    For example, the quantity 4.75 is entered - system will override the value entered with 5. If we make 'Units' a required value and move the field to the left so a user cannot skip over the 'Units' field by default, the issue is mitigated but this requires either customization or forcing form changes and publishing to the user groups which over-writes their default form in PO Lines.


    If the system updated value for the whole unit is not corrected, the PO Line quantity can be incorrect and result in order errors and invoice matching errors.