E1: 13: P12115 Allows Retroactive Transfers from Billed Locations (Doc ID 2105810.1)

Last updated on FEBRUARY 11, 2016

Applies to:

JD Edwards EnterpriseOne Capital Asset Management - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

If Location Billings has already processed over a thru date (R1304), the P12115 will allow a subsequent transfer on a date prior to that thru date. The result is that two locations will be billed for the date range between the time asset was retroactively transferred and the thru date on the first time the R1304 was processed. It appears that the Location Transfer program (P12115) will not validate the delimited date (F1304.DDTE) for a job.

Below is an example of how the issue can be duplicated:

1. An equipment record is created with a location start date of 01/01/2016, location M30.
2. The R1304 is run on the asset with a Thru Date = 01/31/2016.
3. Subsequently, the asset is transferred to location YARD using the P12115 and Effective Date = 01/15/2015.
4. Then next time the R1304 is processed, the system will bill the new job (YARD) from 01/15/2016 to 01/31/2016 and not take into account that it was already billed to the previous job (M30) through 01/31/2016.

The request is that the system validate the F1304 Billed Thru Date when a transfer occurs so that the scenario presented above can be prevented. The result could be a warning to the user that the effective date entered in the P12115 is less than the last billed thru date in the Equipment Location Billing table. Another suggestion would be to add a processing option that would generate a hard error if the user attempts this type of retroactive transfer.



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms