My Oracle Support Banner

Pay_batch_element_entry_api.create_batch_line API Not Populating Input Values Passed In RUP9 compared to RUP8 (Doc ID 2305102.1)

Last updated on FEBRUARY 17, 2019

Applies to:

Oracle Payroll - Version 12.1.3 and later
Information in this document applies to any platform.


On 12.1.3 RUP9 version, Core Payroll - General

Issue reported: pay_batch_element_entry_api.create_batch_line API not populating input values passed in RUP9

During the process of testing the HRMS RUP-10 patch released by oracle recently.
While testing a custom process where is used the Oracle Standard API to create BEE batch and lines.

In RUP-9 Environment
API pay_batch_element_entry_api.create_batch_line is not populating the input values in BEE Lines tables for the element , if the element doesn't have the input values defined.

in Rup-10 Environment
Same API is populating the BEE lines table with input values passed as parameters, irrespective of either the element has these input values defined at element definition or not.
After that, BEE Validation process validating these input values and giving below error message.

Entry values exceed number of input values associated with this element at the effective date.


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.