After HRMS RUP17 Costing Errors ORA-01426: numeric overflow and Going To Suspense Account If Logging is Not Enabled (Doc ID 2996123.1)

Last updated on AUGUST 02, 2024

Applies to:

Symptoms

Costing going to suspense account after applying RUP17 patch

The behavior is one random person cost allocation goes off and had to delete that person from the costing and enable GMFZT, then run the costing, that person get processed again and no errors

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Apply Patch 34444470 - R12.HR_PF.C.DELTA.17
2. Navigate to HRMS Manager> Submit processes and Reports > Submit  costing process .  Process completed in error 
3. Check message in PAY_MESSAGE_LINES table using the following SQL 
         select line_sequence, message_level, source_id "Assignment Action ID",payroll_action_id,
         assignment_action_type, assignment_id, source_type, line_text
         from PAY_MESSAGE_LINES m,
         PAY_ASSIGNMENT_ACTIONS a
         where m.source_id = a.assignment_action_id
         and a.payroll_action_id in (select payroll_action_id from pay_payroll_actions where request_id = &REQUEST_ID)
         order by source_id desc, line_sequence asc;

4. if enabled logging GMFZT in PAY_ACTION_PARAMETERS Table as per Note 376430.1 and run costing , it works without any error.

Changes

 Apply Patch 34444470 - R12.HR_PF.C.DELTA.17

Cause

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