After Upgrade to HRMS K Rup4 Unable to Transfer Elements to BEE, Batch Status Set to VE (Doc ID 951612.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Time and Labor - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
***Checked currency 11-SEP-2015**

Symptoms

After applying HRMS Family Pack K RUP4, notice that batches containing PTO Elements do not process through Transfer to BEE.  The following error can be seen in the FND_LOG_MESSAGES.


per.plsql.pay_batch_element_entry_api.line438 1.00 Error has been raised...
per.plsql.Leaving:pay_batch_element_entry_api.create_batch_line.90 1.00 90
per.plsql.hxt_util.line16 1.00 ORA-20001: PAY_6306_INPUT_VALUE_FORMAT: N, UNIT_OF_MEASURE, Date
per.plsql.hxt_util.line16 1.00 Oops...others
per.plsql.hxt_util.line16 1.00 Batch processing. Batch Id = 24864661 - Error attempting to insert BEE information: (ORA-20001: PAY_6306_INPUT_VALUE_FORMAT: N, UNIT_OF_MEASURE, Date). : =>
per.plsql.hxt_util.line16 1.00 Error attempting to insert paymix information
per.plsql.hxt_util.line16 1.00 Batch processing. Batch Id = 24864661 - Error attempting to insert BEE information: (User-Defined Exception). : =>
per.plsql.hxt_util.line16 1.00 back from calling insert_pay_batch_errors
per.plsql.hxt_util.line16 1.00 Batch processing. Batch Id = 24864661 - User-Defined Exception : =>


The issue can be reproduced at will with the following steps:
1. Create a timecard which has atleast one PTO Element
2. Run the Transfer time from OTL to BEE
3. Run the OTLR Process Validate for BEE and Transfer to BEE, notice that BEE does not contain
Elements and the Batch status is VE.

Changes

Apply HRMS Family Pack K Rup4

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