JD Edwards Human Capital Management: Fixing YTD Gross Pay and PDBA Amounts

JD Edwards Human Capital Management: The Use Case

This issue sounds like a mysterious one, but it could very well happen due to a manual mistake or system issue. For Smartbridge, it happened on a recent project when our client chose to upgrade from JD Edwards EnterpriseOne Tools Release 9.0 to 9.2.

During the project, the data selection for the custom versions of Payroll Driver (R07250) messed up when we promoted it to Tools Release 9.2. The final update, which was the last step in the payroll cycle, selected the records multiple times and processed them repeatedly. When we reviewed the logs, we identified the primary key issues, but did not suspect the data selection itself to be the driver of the problem. After two weeks, we finally realized that data selection was in fact causing the root issue.

The gross YTD (year to date) amounts and PDBA (payments, deductions, benefits and accruals) amounts were incorrect for the first two pay periods in Tools Release 9.2, and continued for subsequent periods thereafter.

The Gross YTD amount gets updated each time by the final update, so altogether, the totals were updated incorrectly. However, this didn’t occur for each member of the company, which made the problem that much more challenging.

Smartbridge is an Oracle Gold Partner

Ultimately, fixing the PDBA amount issue was “less tense” compared to the rest of the challenges. There is a standard UBE (Universal Batch Engine) that will re-post DBAs to the payroll month if the amount in the Summary History Table (F06146) doesn’t correspond to the detail information in the DBA History (F0719). For each employee, the re-post calculates monthly totals for each DBA type, and posts the amounts to the PDBA Summary History. In retrospect, it summarizes by check date.

Correcting the YTD Issue

In this JD Edwards Human Capital Management use case, updating the YTD amounts presented the biggest challenge. There is no popular out-of-the-box process to reference, and the table that consisted of the YTD amount had limited fields. The check control number is the only field we could use to join the other tables.

To solve the problem, we had to build multiple SQL scripts and update the amounts by doing the following:

After implementing some out-of-the-box thinking with JD Edwards Human Capital Management, we were able to solve our clients YTD gross pay and PDBA issue. Our client has not experienced any issues following their upgrade to Tools Release 9.2!

Keep Reading: Understanding Scheduler Resilience in JD Edwards