US Tax Reporter - W2c - Long index time causing system to time out

[amrice]

When running W2c's for 2021 our system times out. I have contacted Basis and they gave me a long running server - over 24 hours but the indexing time is taking over 12 hours.

Details

Tax Company: we only have 1 - State of NC

Reporting period end date: 12/31/2021

Payroll Results up to: 6/30/2022

We are not doing automatic selection. Manual selection=61 employees

Mag tape and combine MMREF-2 boxes both checked.

When prompted we are overwriting the last set of W2cs that we did on 4/30/2022 (we process W2cs quarterly).

We are generating in the background. When prompted we select immediate processing (or even if we set up a date/time) the system takes 12 hours to generate the jobs. It appears to be indexing table T5UYY. We are not having this issue for other years - only 2021. When we last processed 2021 W2cs it took over 12 hours for the job to start (my screen stays on the immediate start time screen until indexing is complete and then the job starts). Once the job starts it finishes in less than 5 minutes.

Our Basis team has stated it is just indexing/reading the table and it has to read the entire table to find 61 employees (or how many ever we are processing).

Has anyone else had this issue? We generate over 89,000 W2s. I am in the process of deleting PCL4 test clusters for 2021 to see if that helps.

Thank you

Aimee Rice

[bkmill0]

Hi Aimee - did you ever resolve this issue? We are facing the same thing, and all notes have been applied. TIA!

[graziela]

Hello Aimee,

I recommend the steps from SAP note:
414496 Fill Job Performance

This helps on similar scenarios.

Kind regards,
Graziela

[amrice]

We have UTRJS set to 5000. We normally generate approx 90,000 W2's with about half of those actually generating a PDF that has to be printed. This configuration has been in place since 2008 - when we went live. Why all of a sudden is 2021 causing an issue when other years prior to 2021 execute/go to the background immediately? The issue isn't when the jobs are started in the background - it is when we select 'background' on PU19, then 'immediate' or 'schedule'. It takes 24+ hours for it to go from dialog to actually start in the background. It's not listed on SM37 as released or waiting. It literally does not go to the background, the screen stays on 'immediate' for 24+ hours then it goes to the background. Once it is running in the background the W2c job runs very quickly (of course the W2 jobs take a little longer but still less than 4-6 hours).

[amrice]

Thank you. We applied the note to our test clients - it was successful with the job starting within a few seconds. However when we applied it to our production client, it took over 6 hours to index (and for the job to start). Any other ideas or suggestions?

Thanks

Aimee

[graziela]

Hello Aimee,

Please, apply SAP note:
3223713 - TR: Execution not finishing due to concurrency issues

Kind regards,
Graziela

[amrice]

Graziela,

Even though we applied the note we are still experiencing this issue. We are trying to generate 56 2021 W2cs and it is taking the system 24+ hours to go from dialog to background. Any other ideas? Do we need to open a ticket?

Thank you for your help.

Aimee