Comments

  • 1-8 of 8
  • Marcella Gerola

    I have confirmation that the patch to correct the reported issue has been delivered with 19C

    We have not seen this issue occuring since this upgrade

  • Marcella Gerola

    Hi Britta

    I am a bit surprised about Edge... 

    I have read about IE but not Edge. Do you have a formal communication on this subject?

    Jennifer, could it be an issue with the pop up blocker for Edge? I see that by default the pop up blocker is active

     

  • Marcella Gerola

    HI Umakanth,

    I am not familiar with the Supplier Audit report (we only have expense).

    What precisely are you attepting to report here?

    The changes made by an Auditor on an expense report before completing the audit?

    Who would be the audience of such a report?

    Thank you

  • Marcella Gerola

    It is just one user. Nobody else has reported the issue.

    He attempted the same action few hours later and could complete the task.

    I did not do anything to solve the issue.

    It would be great to know how to "see the incident log" as suggested.

  • Marcella Gerola

    Hi Umakanth

    we also experienced the same issue.

    In our case it was due to what I call an "orphan record" that is to say an itemized record missing the parent.

    We cannot reproduce the issue but I believe this is occuring when a user attempt various times to correct an entry by changing the dates and/or the currency.

    Orphan rcords are not visible on the audit screen and can only be detected when running the Expense Diagnostic report.

    This record caused an error in the reimbursement process since :

    - it had no expense type

    - it was dated with a date prior to the employee assignment where default expense account was populated.

    The interface is ending in error in this case because there is no valid default account that can be used (neither from the expense type nor from the default account from the employee assignment).

    A bug is open (BUG 30215407) and is pending a patch.

    In the meantime, Oracle provided a query that can be used to detect in advance orphan records.

    SELECT A.* FROM
    (SELECT
    (SELECT EER.EXPENSE_REPORT_NUM FROM FUSION.EXM_EXPENSE_REPORTS EER WHERE EER.EXPENSE_REPORT_ID = EE.EXPENSE_REPORT_ID) EXPENSE_REPORT_NUM,
    (SELECT EER2.EXPENSE_STATUS_CODE FROM FUSION.EXM_EXPENSE_REPORTS EER2 WHERE EER2.EXPENSE_REPORT_ID = EE.EXPENSE_REPORT_ID) EXPENSE_REPORT_STATUS_CODE,
    EE.*
    FROM fusion.EXM_EXPENSES EE
    WHERE EE.ITEMIZATION_PARENT_EXPENSE_ID IS NOT NULL
    AND EE.ITEMIZATION_PARENT_EXPENSE_ID != '-1'
    AND (EE.ITEMIZATION_PARENT_EXPENSE_ID NOT IN
    (
    SELECT EE2.EXPENSE_ID FROM fusion.EXM_EXPENSES EE2
    )
    OR
    EE.ITEMIZATION_PARENT_EXPENSE_ID IN (SELECT EE3.EXPENSE_ID FROM FUSION.EXM_EXPENSES EE3 WHERE (EE3.EXPENSE_REPORT_ID != EE.EXPENSE_REPORT_ID OR EE3.EXPENSE_REPORT_ID IS NULL)))) A
    WHERE A.EXPENSE_REPORT_NUM IS NOT NULL 

    Hope this helps

  • Marcella Gerola

    Thank you Julien

    from what I see this helps mass updating the default currency for all active users at a given point in time. This is a good start and we are certainly going to use it for all the already existing users.

    What we are attempting to find is the ability to default, at the user creation step, the proper currency, according to the user's country.

    This is for all users that will be created after this first mass update.

    Do you see any way to configure the default currency by country?

  • Marcella Gerola

    Thank you Zoe

    I am really looking forward to implementing the screens and notifications simplifications announced with the 19B.

    Users are struggling to use itemization and have multiple screens.

    A question on the activation though: if we activate the option by opting in as described in the documentation, can we still opt out if, after the initial tests, we consider that the feature is not mature enough?

    I see that the changes will become mandatory with version 20 so we have a bit of time to get it right before pushing it to the users (either on UAT or live)

  • Marcella Gerola

    I fully see the need of adding a filter relying on department and/or employee location.

    We are now live with one country, about 1500 users and 2 legal entities

    As a rule for our company all reports must be audited.

    In one week 150 reports have been submitted and there is no easy way for the auditors' team to organise its work effectively.

    There is also no easy way to review the employees one legal entity at a time.