Validate For Bee Completes In Error But No Hint Why (Doc ID 566897.1)

Symptoms

-- Problem Statement:
Validate for BEE concurrent process completes with Error status but there are no messages in the log file, no errors on the form and no rows in the HXT_ERRORS_F table.

-- Business Impact:
Difficult to complete payroll.
This only affects customers who have Preference: OTL Rules Evaluation=Yes.
Due to this issue, users cannot find which batch is causing the error when
processing groups of batches. This is causing batch processing to be done one
at time and slowing down payroll runs.

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Have a timecard that has more than 24 hours on a day.
2. Make sure that the 24 hour max rule in the HXT_TIMECARD_VALIDATION lookup is set to ERR.
3. Run Validate for BEE and watch it complete with error.
4. Check the timecard and see the batch status is still Hold.

-- Additional Symptoms:
1. Validate for BEE completes with error, the log file looks like:
HXT_VAL_BEE module: Validate for BEE
**Ends** <Date and time>
BATCH ERROR:From BEE Summary View Batch, check Batch Errors and/or Details.

2. Batches are created and have status=Unprocessed.
Navigation: OTL Time Accounting : Mass Info. eXchange:MIX > BEE Summary
Query for Batch Name.
Status is Unprocessed. ( PAY_BATCH_HEADERS.status=U )
or
Navigation: OTL Time Accounting : Mass Info. eXchange:MIX > Batch Element Entry
Query for Batch Name.
Status is Unprocessed. ( PAY_BATCH_HEADERS.status=U )
Click Element Lines -- should have no lines
(PAY_BATCH_LINES should have no rows )

3. Professional User Interface (PUI) Timecard has Batch Status=Hold
Navigation: OTL Time Accounting : Time Accounting > Entry/Validation/Approval
Query for Batch Name. Batch status is Hold
( HXT_BATCH_STATES.status = H )

4. Time Entry Errors form does not show errors.
Navigation: OTL Time Accounting : Time Accounting > Time Entry Errors
Query for Batch. No errors returned.

( HXT_ERRORS_F table has no rows. )
-- Check for any errors on creation_date (enter in same format as SYSDATE)
select trunc(SYSDATE) from dual;
select * from HXT_ERRORS_F
where trunc(creation_date)='&creation_date' ;

-- Workaround:
----------------------

IMPORTANT: When using this workaround, you must review every warning generated by Validate for BEE and do the necessary corrections.

Setup Steps needed for Workaround:
1. Go to the Applications Utilities Lookups form.
Using the HRMS Manager responsibility. navigate to Other Definitions > Application Utilities Lookups.

2. Query for Type=HXT_TIMECARD_VALIDATION

3. Please take a screen shot before making any changes.

4. Change any Tag field with ERR to WRN. You will need to change the following lines:

Code , Meaning
-------------------------------------------------------
24_HOUR_DAY , HXT_39447_DAYTOT_GRT_24
24_HOUR_EDIT , HXT_39315_MAX_HRS_EXCEDED
INSERT_ERRORS , HXT_39338_INS_ERROR_OCC
PERSON_NOT_IN_DB , HXT_39316_PERSON_NF 

5. Save the changes to complete the workaround.

6. Continue with your usual steps.
a. Run Validate for BEE concurrent process.
At least one batch will complete with Warning. Some customers find that it is easier to run each batch separately.

b. Find the errors that need correction.
Responsibility: OTL Application Developer
Navigation: OTL Time Accounting : Time Accounting > Time Entry Errors.
Query for your Batch.
The status will be WRN for Warning.

The errors will now show as Warnings. Ensure that the following are addressed appropriately:
WARNING! Timecard hours cannot exceed 24 in any one day.
WARNING! Hours charged to multiple assignments have exceeded daily max of 24 hours
WARNING! Error occured while trying to insert an error record in TC ERRORS IN TAB.
WARNING! Person not in database. Timecard ID-&TIMECARD_ID Person-&NAME Period end-&PERIOD_END_DATE.

c. Make your corrections on Professional User Interface (PUI) Timecard.
Responsibility: OTL Application Developer.
Navigation: OTL Time Accounting : Time Accounting > Entry/Validation/Approval

d. You may rerun the Validate for BEE concurrent process to verify that you have completed all the necessary changes, otherwise proceed to the next step i.e. runTransfer to BEE concurrent program.

Changes

Customers had applied the 2007 Year End Payroll patches.

Cause

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