E1: 07: 77: Generate T1 CF Records based on F06116 HMCU (Doc ID 2646524.1)

Last updated on JUNE 18, 2021

Applies to:

Symptoms

Generate T1 CF Records based on F06116 HMCU

R072902 PO #1 (Tax/DBA AAI Source) determines which home company and home business unit are used to perform the AAI lookup for both Tax and DBAs.  

Unfortunately, the choices are basically limited to either using the values from the Payment Header (F07350) – which is typically a single record unless there are other values, such as print method equal = ‘S’ or ‘C’, for example, which would cause a separate (additional) Payment Header (F07350) record to be generated – or the Employee Master (F060116) values.  It appears that – by design – the timecard values are not used to perform the AAI lookup for the T1|CF entries.  In other words, the search home company and search home business unit either come from the F07350 or the F060116; not from the F06116.

R072902 PO #3 (Home Business Unit Source), controls the home business unit (HMCU) on the F063951 record.  A value of a <blank> in this PO will result in the F07350 HMCU being used to populate the F063951 HMCU; a value of ‘1’ will result in the F060116 HMCU being used to populate the F063951 HMCU.  Again, the timecard (F06116) value is not used by design.

That is very inconvenient and will lead to a massive costing issue in our business as we do have that case a lot (employee works for two or more BUs in the same month.)

The Payroll recovery cost in T4 works fine and credit the amount according to BUs entered in F06116 and T2 works fine as well.
But T1 doesn't work in the same way, however, the results will be unbalanced between the accruals and benefits debited on (X)BU and the Payroll recovery cost credited to (X)BU.

Changes

Cause

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