My Oracle Support Banner

E1: 48S/52: Add Functionality to Workfile Generation (R48120) to Use Additional Field When Validating Records to Pull Into Table (Doc ID 2112602.1)

Last updated on FEBRUARY 04, 2019

Applies to:

JD Edwards EnterpriseOne Contract and Service Billing - Version 9.0 and later
Information in this document applies to any platform.


Client has used all the PRTR values and has reset them to to be used again in payroll processing. This has caused an issue where the PRTR value is being reused and it is finding the number, however, it is giving a mixture of the information from the original record that had this PRTR and the new record that has this value. This is causing issues in billing as the previous record has already been billed and the new record has incorrect values to process.

It appears the Workfile Generation (R48120) is finding the PRTR value and not checking any further for a duplication or to verify the correct information is being pulled into the workfile for processing.

It is requested to add functionality to use more fields to validate the appropriate record for billing rather than just one field.

The following fields are required to match in order to update the records and it is requested to add some or all of these when accessing the records:

History (F0618) fields must match:
G/L Date (F0911 DGJ = F06116/F0618 DGL)
Batch Number (F0911 ICU = F06116/F0618 GICU)
Business Unit (MCU)
Object (OBJ)
Subsidiary (SUB)
Subledger (SBL)
Subledger Type (SBLT)

If only one is possible it requested to use the GL date and there is a number of years between the records that are involved.




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

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