My Oracle Support Banner

Loaded Cumulative Mileage Not Loaded To The Correct "Cumulative Mileage Tracking Period" (Doc ID 2271979.1)

Last updated on NOVEMBER 15, 2019

Applies to:

Oracle Fusion Expenses Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.11.1.0 version, Manage Expenses

ACTUAL BEHAVIOR
---------------
Loaded cumulative mileage not loaded to the correct "Cumulative Mileage Tracking Period"


I am experience this issue, when I load cumulative mileage for the tracking period (25/11/16 to 05/04/17) the expectation is any mileage balance loaded under this tracking period should be loaded and viewed under 2016 / 2017 period.
however, after the upload has taken place, the balance is automatically defaulting to the current period (06/04/17 - 05/04/17) instead. Can you please advise why this issue has occurred.

We are currently doing a phase rollout for expenses module and we are gradually loading cumulative mileage related to the existing employee, as part of the business requirement.

Please see attached screen shot for more details.

BUSINESS IMPACT:

if loaded mileage balance does not show in the correct period selected in this scenario (06/04/17 - 05/04/17) this will have a serious impact on mileage calculation for the employees. as we have different Mileage rate to a different mileage distance used by each employeeie: ie: we pay £045/Mile for mileage under 1000 Miles / £0.25/Mile if the mileage exceed 10000 Miles and so on...


ISSUE: Loaded mileage is going to the wrong tracking period and we need a fix for it.

EXPECTED BEHAVIOR
-----------------------
mileage balance loaded under this tracking period should be loaded and viewed under 2016 / 2017 period.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.From the Setup and Maintenance,Go to the task#Manage Cumulative Mileage Determinants
2.Under Manage Cumulative Mileage Determinants,below three rows exits

Business Unit Cumulative Mileage Tracking period Start date End date
---------- ----------- ------ -----
CHDA Business Unit Anually 11/12/15 05/04/16
CHDA Business Unit Anually 25/11/16 05/04/17
CHDA Business Unit Anually 06/04/17 05/04/18

3.Customer is selected the second row (i.e 25/11/16 - 05/04/17) -->Go to 'Actions' button --> Upload

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue,
if loaded mileage balance does not show in the correct period selected in this scenario (06/04/17 - 05/04/17) this will have a serious impact on mileage calculation for the employees. as we have different Mileage rate to a different mileage distance used by each employeeie: ie: we pay £045/Mile for mileage under 1000 Miles / £0.25/Mile if the mileage exceed 10000 Miles and so on...

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.