Quantcast
Channel: SCN: Message List - SAP ERP HCM Payroll North America
Viewing all 2280 articles
Browse latest View live

Re: T51R5 - 3PR Due Date

$
0
0

Hello,

 

We are working on setting up garnishment payments using EFT, which create addenda 7 records in our bank file.  It is my understanding that when the 3rd party postings are completed, a Child Support garnishment is supposed to pass a value of "4" Garnishment and Child Support Payee(s) (V0 split type 'G') to table T51R5, but it is sending it through with a value of "2" Tax Payee(s).

 

Has anyone else had issues with this and if so, how is it remedied?  Is it possible to modify the value in the V_T51R5 table after processing but before payment?

 

Any input would be greatly appreciated!!

 

Vicki


Re: Garnishment: State Tax Levy

$
0
0

Hello,

 

Anyone got the same problem and figured a solution on how the rule for Wisconsin State Tax Levy can be implemented?

 

Thanks,

Mitesh

Re: Affordable Care Act (ACA)

$
0
0

Hello Carlos,

 

Based on your email, we applied the first note 2222144 - BEN: UDO Note - Affordable Care Act (ACA) - 1st SAP ACA Update and when performing the post implementation step in SA38 we got the following error:

 

Program RPU_BENUS_UDO_NOTE_2222144 does not exist. What did we miss? This note PDF didn't indicate any pre-requisite.

 

All,

 

Your input will be helpful.

 

 

Note: We are on HRSP 92

 

Thanks

Ashwini

Re: IT0165 - Limits on Deductions

$
0
0

Thanks Ameet, thats helpful to know.

Re: Affordable Care Act (ACA)

$
0
0

It seems like a number of people are having issues with applying the Post-HRSP92 Notes. I just finished applying them to our DEV system without any issues, so I thought I'd detail that a bit here for others as a reference. Note that I'm not talking about the various configuration steps in the user guide, etc -- I'm Basis, not the Benefits Analyst! But as far as getting the Notes in cleanly so the Benefits Analyst has a good base to start from, here's what I did.

 

  1. With SPAM, apply HRSP 92 (SAP_HR 604.92 and EA-HR 604.92), along with Support Stack 17 to our ERP 6.04 system. Also updated kernel to 7.21_EXT pl600. You're going to need this HRSP for Year-End Legal Changes for Tax Reporter anyway, so go for it.
  2. In SNOTE, download Notes 2222144, 2211233, 2230800, and 2211234 (1st and 2nd ACA Updates and their associated UDO Notes). Note that you will not be implementing these Notes in numerical order.
  3. With SNOTE, apply Note 2222144 (BEN: UDO Note - Affordable Care Act (ACA) - 1st SAP ACA Update) (version 2) in the normal fashion. This creates the program for the next step. Save this to a new transport request.
  4. In SE38, execute RPU_BENUS_UDO_NOTE_2222144. Run it in Test mode first and ensure that all lights are green (except the one yellow stating it's a test run). Then run it in Update & Activate mode. Online activation is fine. Save the changes to the same transport as step 3.
  5. In SNOTE, apply Note 2211233 (BEN: Affordable Care Act (ACA) - 1st SAP ACA Update) (version 6) in the normal fashion. Use the same transport to save the new and changed objects.
  6. Read the post-implementation manual instructions in the PDF attached to Note 2211233.
    1. Download ACA_Files.zip that is attached to Note 2211233 and extract three form XML files from it to a temporary location on your workstation.
    2. In transaction SFP, locate and change form HRBENUS_1095C_2015. Go to Utilities... Uploading form... and find the file SFPF_HRBENUS_1095C_2015.XML that you extracted and upload it. Save the form; use the same transport request. Activate the form.
    3. Repeat step 2 for forms HRBENUS_1095B_2015 and HRBENUS_1094C_2015.
    4. Note: these forms already exist in your system. You are uploading new versions. I recommend searching for the form names vs typing them in to ensure no mistakes.
  7. In SNOTE, apply Note 2230800 (BEN: UDO Note - Affordable Care Act (ACA) - 2nd SAP ACA Update) (version 5) in the normal fashion. This creates the program for the next step. Use the same transport request.
  8. In SE38, execute RPU_BENUS_UDO_NOTE_2230800. Just like the previous one, run it in Test mode first and ensure all the green lights (except the test mode warning), then run it in Update & Activate mode. There will be a few screens to confirm things, but it should be pretty obvious what you're doing. Save changes to the same transport request.
  9. In SNOTE, apply Note 2211234 (BEN: Affordable Care Act (ACA) - 2nd SAP ACA Update) (version 7) in the normal fashion, saving everything to the same transport request.
  10. Read the post-implementation manual instructions in the PDF attached to Note 2211234.
    1. In SM30, change view V_T5F99K0, hit New Entries, and create an entry as shown in the PDF. Save your changes to a new transport (because this is client-specific and needs a customizing transport, whereas everything up to now has been in a workbench transport).
    2. Change view V_T5F99K1, hit New Entries, and create the two entries as shown in the PDF. Note that you should be able to use the search help to find Option ACAOF after creating the entry in the previous substep, so the order is important here. Save your changes to the customizing transport you created in the previous step.
  11. You're done! Now turn it over to your functional benefits analyst/configurator and point him/her to the instructions and FAQs in Notes:
    1. 1910650: BEN: FAQ about Affordable Care Act (PPACA)
    2. 2060131: Announcement Note for Information Reporting for Employer Sponsored Coverage and Minimum Essential Coverage
      1. This is the one with the attached User Guide.
    3. 2167502: BEN: Main Note - Affordable Care Act (ACA)
      1. Overview of the features, views, programs, etc
    4. 2219762: BEN: Affordable Care Act (ACA) - Frequently Asked Questions

 

One final note: all of the above Notes are supposed to be included in HRSP 93, so if you can wait....

 

Cheers,

Matt

Re: Affordable Care Act (ACA)

Re: Affordable Care Act (ACA)

$
0
0

Hello Matt,

 

This is extremely helpful. I can't thank you enough. Will keep you posted on the progress on my end.

 

Thanks

Ashwini

Re: Affordable Care Act (ACA)

$
0
0

Hi Carlos,

 

I don't have '1H' for all the employees anymore after I had removed 'WA' from V_T77BENUS_ASPCC, but I have '1B' for who should have '1E' and no amount in Line15.

 

Should having 'WA' be a problem? or would it be affected by some other configuration I did?

 

Could you advise where I should check for the line 15?

 

Thank you.

Euna


Re: BSI Tax Factory 10.0

$
0
0

Hi everyone,

 

Now it's my turn. I'm applying Cyclic 10i to my DEV TaxFactory server, and it doesn't seem to be taking. This is an update from Cyclic 10f (so, skipping g and h). I'm currently on TUB 49.

 

The client update went fine, no hitches, and it reports itself as being Cyclic i. It's the cyclic update file that then gets applied via the client that I'm having a problem with.

 

Using the System Tools... Manual Update link in the client, I browsed to and found the TFU10i.nrq file that I downloaded. I processed it normally, and it ran for about a minute, maybe a bit less -- a normal length of time. The dta, man, and upd output files look normal. At the end of the dta file I see G, H, and I cyclic data listed. The upd file has lots of "record processed successfully" messages.

 

But, in the View Summary there's no listing for cyclic I. Only my regulatory updates and then the last cyclic shown is F. Backing out back to the System Tools page, under Maintenance Tools the Cyclic is still reported as F. And, back in my DEV ERP system, in the Sync Tool, the Level in BSI Client shows Cyclic F.

 

I tried importing the cyclic three times, but keep getting the same result. I downloaded it again -- same size to the file as previously, and imported it a fourth time, having logged out, restarted the browser, cleared browser cache.... nothing.

 

Anyone seen this behavior before? I don't think I'm missing anything (after all, I wrote the blog on cyclic updates, right? ), but who knows.

 

Does it need a higher TUB level than 49? Should I update TUBs first?

 

Thanks,

Matt

Re: BSI Tax Factory 10.0

$
0
0

The only time I have seen this behavior is when the file acted like it was loaded but it was actually still loading and the output files were not available for viewing.  I have pretty much always applied the cyclic before the bulletins, if I am applying a cyclic.  Do you have a backup to where you could try again with cyclic g or h?  We are currently at cyclic g and bulletin 59.  Have not started on year end yet.

 

Please keep us updated on this!

Thank you, Anna

Re: Affordable Care Act (ACA)

$
0
0

Good day,

 

on our form 1095-C line 16 we are not seeing code '2D' for the limited non-assessment during which the EE is not enrolled in health coverage yet. I looked through the code and cannot find where 2D would be set. According to the documentation we should not configure the feature since standard IRS rules should be applied by the program.
Any ideas?


Thanks and best regards,

 

Mathias

Overpayment recovery and /561 automatic

$
0
0

Hi All,

 

We have configured over payment recovery functionality in SAP payroll, All config is in place, but system is recovering the amount in the next payroll run.

 

As we are running the overpayment recovery report, which is updating the infotype 0909.

 

So infotype 0909 is also updated and system is recovering the amount under /561.

 

Please suggest how to stop automatic recovery under /561.

 

thanks

Veer

Re: BSI Tax Factory 10.0

$
0
0

Hi All,

 

We are going from cyclic D to F1 with our support pack upgrade but when we apply the .nrq file to BSI we get an error "Current Cyclic Bulletin is D. Engine revision is D. Cyclic Data F1 is out of sequence. Cannot process this bulletin; the record was processed unsuccessfully." I thought that all cyclic's were cumulative and you did not need to apply individually? Is that not the case when going from D to another cyclic? Has anyone seen this before?

 

Thanks,

Jamie

Re: BSI Tax Factory 10.0

$
0
0

Hi Jamie,

 

As you may have seen, I'm having my own issues with Cyclic F right now, but a different error message than you are seeing. You're correct, cyclics are cumulative. I wonder if the error has to do with your TF client software? Did you update the client to Cyclic F first? I think you need to do that before applying the cyclic data file.

 

Cheers,

Matt

Re: Employee Medicare Tax withholding is not calculating correctly on negative supplemental wages

$
0
0

Hi Ameet,

 

I set the switch " ADTMD" to "ON" for country grouping 10 in table V_T5F99K2, still the issue is not resolved.


Please suggest if I need to check some other tables.

 

Thanks,

Santosh

 

 

 


Re: Affordable Care Act (ACA)

$
0
0

Hi Carlos,

 

It was T74HR. We hadn't configured that table. So, we have '1E' now. However, having 'WA' in  V_T77BENUS_ASPCC is still a problem.

 

Thank you.

Euna

US Payroll Tax

$
0
0

Hi All,

 

For US Payroll BSI tax + Payroll interface / RFC how to check the synch between both system

 

One report is "RPUBTCU0"

 

Is there any other report to check the synch between PY and BSI

 

thanks

 

 

SK

Re: W-2PR box 16

$
0
0

Denise were you able to figure this out?

Re: BSI Tax Factory 10.0

$
0
0

Still no luck getting Cyclic 10.0.i data to load. I have tried updating all the other components I could think of, including a Tomcat update, a JRE update, a SQLJDBC driver update... None of it made a difference (though they were probably good things to get done anyway). I also applied a couple of Regulatory Bulletins to a) see if those failed also, and b) see if there might actually be an undocumented minimum Bulletin level for this Cyclic. The Regulatory Bulletins applied without a problem, and that made no difference to the Cyclic. So, instead of Bulletin 49, I'm now at 52 (I stopped there, as I've seen others write that they were successful with the Cyclic at or below this bulletin level).

 

I even completely uninstalled and reinstalled Tomcat and the TaxFactory client. The only thing I didn't replace entirely is my database.

 

I haven't tried using tfloader at the command prompt yet, and I might try that tomorrow. I'm done for tonight, however, and in any case, it shouldn't require resorting to that, so even if that ends up working, something is still wrong.

 

I have submitted a Customer Incident about this, so we'll see.

Re: US Payroll Tax

$
0
0

Hi,

 

To verify SAP connection to BSI TF, report is RPUBTCU0.

 

To verify SAP connection to BSI TF for BSI Tax Locator, report is RPUTLTU0.

 

Generally you can also test the connectivity between BSI and SAP when you run payroll.

Payroll will throw an error message as "RFC connection for BSI Tax Factory version is not available".

 

Thanks,

Ameet

Viewing all 2280 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>