Skip to Content
Product Information

U.S. Tax Reporter Year End 2018

Hello community,

This is our U.S. Tax Reporter Year End 2018 blog. If you have questions about 2018 Year-End reporting, you can post it here. This blog will be updated with tips, best practices and, SAP Notes related to this subject.

SAP notes:

Related to PY-US-TR:

2683055 – U.S. Tax Reporter Year End 2018 Announcement
2687379 – TR: Q3/2018 Functional changes for U.S. Tax Reporter
2728080 – TR: Q4/2018 Functional changes for U.S. Tax Reporter
2680733 – Year End 2018 Phase I for U.S. Tax Reporter
2698729 – Year End 2018 Phase II for U.S. Tax Reporter
2733416 – Year End 2018 Phase III for U.S. Tax Reporter
2734441 – TR: Form W-2/W-2c PR Boxes 16, 16A and 16B for 2018
2730601 – TR: Tax rate field rounding issue
2741517 – TR: Year End 2018 Additional U.S. Tax Reporter Changes for Localities
2745587 – TR: Form 1099-R is created with only one page
2745965 – TR: Year End 2018 Additional U.S. Tax Reporter Changes for NE, OK and RI
2742519 – TR: Wrong length of ExcessWages in Florida UI XML after applying SP
2743323 – TR: EFW2 SSA file format for Puerto Rico missing required information
2743848 – TR: Prerequisite customizing for SAP Note 2743323
2757513– TR: 1099RC Not generating new 2018 Employee or Employer Copy forms
2767381– TR: Puerto Rico W-2c Electronic File Updates for 2018

Important correction:

2721724 – BSI: Incorrect log of TaxFactory SaaS Logical Port Information when running RPCALCU0

Related to PY-XX-PF:

2643877 – Runtime error OBJECTS_OBJREF_NOT_ASSIGNED in payroll program
2471158 – Corrections to function for restricting access to payroll data with a time-dependent authorization (SAP Note 2365304)
2683888 – Performance issues in Wagetype reporter(H99CWTR0)

Additional information:

Regarding a Washington Paid Family and Medical Leave Calculation, I have created a new blog, so for any questions regarding PFML post in the new blog, this blog is related to Tax Reporter issues.

ASUG Webcast

The Year-end content is now available on sap.com Globalization Finder page at the SAP ERP US Tax Reporter Solution document solution.

To access HCM US site, please go to https://www.sap.com/products/enterprise-management-erp/core-hr-module/americas.html# and select United States, then select Find all US-related documentation, then choose SAP ERP U.S. Tax Reporter Solution document.
Maintenance Planner:

https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ==)/support/mp/index.html

https://help.sap.com/doc/9c9945692df94231b8dc323afe48a58e/latest/en-US/loio6a17e10646f647bc8ace581ebc039b05.pdf

To be able to access the Year-end 2018 in the Globalization finder page you need to be logged on (similar to SAP Service Marketplace) because it is a gated area and would need authorization.

To review the planned Legal changes for US, start the Announcement of Legal Change and filter SAP U.S.

Thank you,

Kind regards,

Graziela Dondoni

272 Comments
You must be Logged on to comment or reply to a post.
  • Also we installed note 2722361 ,  installed the SYST and CUST files,  followed the manual steps.  Executed the BSI Sync program (BSI updated to level 154).  However BTXFORM table entries are missing for WA (00530000) for new tax type 100,101,102,103.  It only has tax types 99 for WA.  Also the TT field attribute in table BTXFORM is still showing as 2 char.  What am I missing here?

     

    Thanks

    Chandra

      • Thanks Katherine.  Looks like there are more notes to apply for the WA FML,  not just one as originally indicated.  I found the below three related notes for SAP 608.

        2724688 – TAX: Changes in Payroll Driver log and Sync Tax Data due to 3-digit Tax Type enablement

        2732298 – Prerequiste objects for SAP Note 2731200

        2731200 – BSI – Change BTX screens due to 3-digits Tax Type change

         

        Thanks

        Chandra

        • Update: after applying all the other four notes (2722361, 2724688, 2732298, 2731200 ) it does appear to calculate correctly.  The BTXFORM table got synched for WA with TT>99 through the BSI Sync program update.  And the Tax calculation is happening correctly for TT87, TT99 and TT100.

          Also to answer my own question above (regarding different formula for TT100) – the default formula for TT100 for WA is 1;  if there is a need for different formula (FN2 or 3), it would have be done via BTXRATE table.

          However I do notice that in the BTXRATE table,  if you try to enter TT100 for WA,  and enter any formula number,  it errors out:  “No entry in table BTXFORM for <xx>” where xx = formula number.

          Thanks

          Chandra

           

           

          • Hi Chandra,

            We applied all SAP notes you mentioned in your message and WA EE FML, EE Medical and ER Medical leave premiums are calculating correctly in the payroll 01-2019 but in the subsequent payrolls, system is deducting higher premiums. Not sure why. Did you have this issue? if yes, can you please let me know how you resolved it?

            Thanks,

            Venkat

    • The WA PFML is still NOT working correctly even after applying all the required notes. For those wondering how to pass different formulas for TT 100, it is done via table T5UTD (not BTXRATE). If FN 1 is passed, BSI will calc the ER portion, if FN 2 is passed, BSI will calc combined EE portion for ER and if FN 3 is passed, ER is exempt (zero).

      Taxes calculate correctly in the first period including the limit but in subsequent period, it does not work correctly because in the BSI interface, SAP is not passing YW and YT parameters for A0 tax type to BSI. With no YW and YT parameters on A0, tax types 888 and 999 does not know the YTD taxes which is required for correct calculation. This is the issue that needs to be fixed.

      Regards,

      Thomas

      • Thomas / Venkata,  please make sure to map the tax types 888, and 999 in BSI.  Not sure if that is causing the issue but I just ran for the second pay period and is working fine (the WT amounts are good).  Also validate if note 2711990 is applied (this was not in my list before but came up when we were applying 2723361.

        and good to know about T5UTD.

        Thanks

        Chandra

        • Chandra, I don’t believe you should have to map 888 and 999, SAP said these are internal and only used in the BSI interface and do not appear anywhere in the system. If they need to be mapped in BSI TF, the TUB update should take care of that and no manual work should be needed on our part.

          Do you get the same taxes in 2nd period if /787, /799 and /7A0 are the same in both periods?

          Regards,

          Thomas

          • Even though they are virtual tax types, it still has to be mapped in the BSI Tax Type Mapping table – it should be mapped to the SAP Tax Type value (888,999 respectively).

            If you are using BSI Tax Locator you should see an error for WA when creating IT 207/208.  You are correct that the TT mapping in BSI TT mapping should have been taken care by the sync program but it didn’t.

            Yes, I’m seeing correct values for /487, /499, /4A0,  /787, /799 and /7A0 for period 2 and 3 and the TCRT values appear correct as well.

            Thanks

            Chandra

          • Hi Chandra,

            I mapped tax types 888 and 999 in BSI TaxFactory and still same issue, higher premiums in payroll 2, 3 …

            Thomas, please let me if you find solution for this.

             

            Thanks,

            Venkat

          • Venkat,

            At this time, I don’t think manually mapping the virtual tax types is the fix. Rather, you need to ensure that you run the Sync tool after you have applied all the Notes. If you run it before applying some of the “3-digit tax type” bugfix Notes, it fails to correctly sync down anything higher than tax type 099.

            Cheers,
            Matt

          • Chandra and Thomas,

            I’ve seen absolutely nothing in any documentation from SAP about performing manual mappings of tax codes 888 and 999 for the WA PFML solution. What exactly are you doing to perform this mapping? Which table are you referring to?

            If this is a bug in the solution as delivered by BSI and SAP, we should press for them to deliver a fix quickly, as we’re all under fairly tight deadlines to get this working in our systems. At a minimum, if there’s additional manual activity required not handled by implementing TUBs and Notes (and the Sync tool), that should be officially documented.

            Cheers,
            Matt

          • Matt,  I was referring to the “Map Tax Types” node in the BSI Tax Factory software to map 888 and 999 Tax types with SAP values for 888 and 999.  Whenever a new tax type is created, this mapping has to be done in BSI for smooth functioning.  I believe this mapping is completed by the BSI sync tool (and this would happen in the config client, otherwise it will be a manual activity).   However I did not expect this to be the case for 888 and 999, as they are noted as virtual tax types.

            However during my testing of the tax locator for WA, I did get an error stating “BSI error: 0008 NO TAX TYPE IS MAPPED TO EE TAX-CALC DEPENDENCY-DO NOT USE USE THE TAX TYPE MAPPING TOOL TO ASSIGN YOUR CODE.” .  The “EE TAX-CALC DEPENDENCY-DO NOT USE” referenced in the error is the description for tax type 888 in BSI.  After completing the mapping, the error went away.

            At this time I do not know if mapping 888 and 999 is the root cause of the issue Thomas had noted.  If this solves Thomas’ issue, then I agree that either this is addressed in the BSI-SAP Sync program or at least documented in the note as manual activity.  I would also suggest to add all the required notes to be documented in the WA FML note, so it is easier to have them implemented together.  I had to spend few hours scrambling to get all the notes collected and applied.  At present the one note that details out the new functionality for WA FML does not list ALL the prerequisite notes for implementation.

            Thanks

            Chandra

          • I checked with the analyst who is doing the configuration in our system (I’m basis, my job was to apply Notes and TUBs), and he did not perform any manual mappings of 888 or 999, yet we are not having any issues with later period testing as you and Thomas had indicated. However, we ran the Sync tool twice… once before applying the other Notes that fix the 3-digit tax code issue, and then again after applying a new TUB (154) and all those Notes. The 2nd time I noticed that it sync’d many more tax types down (and/or up?). So, I wonder if that was the actual fix, to ensure you run the Sync tool AFTER applying all the Notes.

        • Hi guys,

          I mapped tax types 888 and 999 in TF and it still didn’t work. I am still having the same issue as Venkat. In Venkat’s example, in period 01-2019, the taxes are correct. 4875.12 * 0.004 = 19.5.

          6.5 (/487) + 5.85 (/499) + 7.15 (/4A0) = 19.5 so period 1 is correct.

          Period 02-2019 is not correct (amt is supposed to be the same as period 01) because of the issue I pointed out which is that YW and YT parameters are not being passed in tax type 100 (A0) in SAP-BSI interface.

          But good news, a new OSS note was just released that should fix this issue.

          2736529 – TAX: Incorrect cumulation of YTD amounts for tax types 100 and above

          We’ll apply this and test it out.

          @Matt Fraser, official documentation would be nice but I am just trying to get this to work so willing to try any suggestions. But you’re right, the update shouldn’t require us to do any manual work and if it does, it should clearly state that.

          • Hi Thomas,

            Are you able to find the solution for this issue? BSI saying we are not passing tax types 888/999 from our payroll. they are asking us to contact SAP.

            Message from BSI:

            In your SAP script for the Payroll 2, you are not passing the required tax type 888/999 from your payroll.

            The year to date wages and taxes are required for those tax types.

            Refer to your payroll vendor for assistance with the configuration.

            Thanks,

            Venkat

          • This issue has been resolved after applying these SAP notes

            2736319 – TAX: Virtual Tax Types 888 and 999 are not restricted to WA

            2737921 – TAX: Washington Paid Family Leave not calculated correctly when the employee is not resident in WA

             

  • Graziela,

    I Just noticed that the SUI form for Oklahoma is not displaying a “Contributions Due” in line 6 or line 12 for 4th QTR.  Should i submit OSS incident for this?

    Thanks!

    Matt

    • Matt,

      Please ensure that you have applied all the three phases of the Year End and if the issue still persists, please open and incident.

      If this is a new field, please provide the legal requirement in which your understanding is based too.

      Regards,

      Roger Oliveira

  • Hi,

    we have BOX 16B for Code I is not working even though we mapped EXSI with wage type for Puerto Rico. anyone experiencing this? we did logged OSS but not having any attention.

     

    thanks

    Gayathri

    • Hi Gayathri,

      There is some corrections that were listed under this legal change: https://launchpad.support.sap.com/#/legalchangenotification/detail/GSCBNA-1007

      It mentions the SAP note 2734441 – TR: Form W-2/W-2c PR Boxes 16, 16A and 16B for 2018

      Did you have it implemented on your environment?

      Regards,

      Roger Oliveira

  • Hi,

    We have installed all the notes for WA PFL.  When I run payroll I get a BSI Message that states: “The Washington Employee/Employer Paid Family Leave insurance requires an internal-only recalculation of the Washington EE/ER Tax-Calc dependency- Do not use.”

    The tax calculation is not correct.  Can anyone offer some ideas on how to resolve this?

    Averil

    • Looks like Tax type 888/999 is not being sent to BSI.  Can you check the USTAX node in the payroll log, under processing > BSI Interface node; there should be entries for tax type 888 and 999.

      Refer note 2722361, there is a section for tax types 888/999 and how its reflected.  Also, as noted by Matt above, make sure to run the BSI -SAP Sync tool/program in SAP to sync-up. After all the notes are applied, it is important to run the sync tool again to catch-up any missing entries.

       

      Thanks

      Chandra

    • Hi Averil,

      Apply these two notes to resolve your issue

      2736319 – TAX: Virtual Tax Types 888 and 999 are not restricted to WA

      2737921 – TAX: Washington Paid Family Leave not calculated correctly when the employee is not resident in WA

      Thanks,

      Venkat

  • Hi Pals – We are running recon report (RPCPRRU0) using splitter (RPCPRSU0) for 2018 whole year for full population ( ~80000 EEs) including retirees. We are splitting job into 99 jobs using splitter. The jobs are getting completed successfully however while compiling all the output ( all spools) program is getting terminated due to internal table memory issue (No more memory available to add rows to an internal table.). Our basis team has set parameters to 20gb-20gb. Anyone else is facing same issue? Also if we run it directly through recon its taking forever to complete.
    I have open message with SAP but to luck so far. We have being using same report from past 8 yrs with no issues.
    Any help would really appreciated. Thanks

    • Hello Gayathri,  we have similar issue (about 200k EE and retirees) and have raised an OSS to SAP.  But so far the response from SAP is not encouraging.  The response has been like “reduce the population for the report” ; there is no issue noted in the program, etc.  Even reducing by payroll area (about 90K population) didnt resolve.  We raised the memory parameters to 40gb (not recommended) but still the job was not able to finish as its not able to write a large file size (about 22gb) to the temporary file path in the OS before output in the spool.  Refer my earlier post here on this topic.

      Thanks

      Chandra

  • We have employees that live in PA and work in NY. Previously the system has only been withholding NY taxes which is what was expected. However, with the first payroll of 2019, the system is now withholding both PA and NY withholding. There has been no master data changes made and we cannot see where any tax bulletins were made to change with tax process.

    Has anyone else seen this issue before or have any guidance?

    Thanks,

    Katherine

    • Hi Katherine,

      This blog thread is available for Tax reporter year end process and update, seems that scenario provided is related with tax calculation rather than the main topic here. Am I correct?

      Despite that, I recommend you to compare the BSI scritps at the payroll log and check if they have any difference.

      It is also recommended that you download this script and execute a batch test on BSI side.

      This way you can narrow down the scenario and check the possible root cause.

      Regards,
      Roger Oliveira

    • Katherine, please analyze note 2736319 which was released as a side-effect to 2722361 and mentions issues relating to NY taxes.  You can apply this and check if it solves the issue.

       

      Thanks

      Chandra

      • Hi Thomas,

        This exactly cumulation issue was identified only in these releases.

        Are facing the same cumulation issue on a 6.08 environment?

        Regards,

        Roger Oliveira

        • Hi Roger,

          We are not sure it’s same issue or not. The Washington Family and Medical premiums processed fine in payroll 01-2019 but not in payroll 02-2019. We have opened a high priority incident with SAP and waiting for response.

          1866 / 2019 – Washington Family and Medical Leave premiums are not calculating correctly in payroll 02-2019

          Thanks,

          Venkat

  • Hi Graziela/Roger

    The new State wide transit tax (096) introduced for Oregon in June 2018 is not reflecting in Box 14, any inputs/guidance please.

     

    Thanks

    Madhu.

    • Madhu-

      I had posted this same query earlier if you check other comments and this was a response that I received.  It does NOT appear to be a REQUIREMENT from Oregon for this year.

       

      https://www.oregon.gov/DOR/programs/businesses/pages/statewide-transit-tax.aspx

       

      Where does the new statewide transit tax get reported on the Form W-2?

      ​There isn’t currently a requirement to report the statewide transit tax on the Form W-2. We’re analyzing the impact of adopting an administrative rule that requires statewide transit tax wages and withholding to be reported in Box 14 of the W-2. This prospective rule change would be part of our fall 2018 rulemaking process. The draft rule would be posted on our website for review, and there would be the opportunity for public comment on the potential impacts of this requirement.

  • Hello Team, we are seeing some incorrect tax calculation for WA FML for out-of-state residents but working in WA.  In such a scenario,  the tax types 87,99 are not getting calculated but only TT100 is being calculated.  Also we are seeing BSI error messaging saying “4101
    CAN NOT PROCESS DUPLICATE RESIDENT STATE WA”;

    Anyone noticing this?

    I have opened a ticket for this.

    Thanks

    Chandra

    • Hi Chandra,

      Please implement SAP note:
      2737921 – TAX: Washington Paid Family Leave not calculated correctly when the employee is not resident in WA

      Let me know the results.

      Thanks,
      Graziela

      • Thanks Graziela.  We applied the note 2737921 and it did resolve the issue.  Now the WA FML is calculating correctly for WA non-residents.  Thanks for the quick response.

        Thanks
        Chandra

      • Hi Graziela, I have applied all below SAP Notes regarding WA for PFML and I am getting negative values for TT 87 and other new TT and not passing the correct parameters like Pay period wages for TT:888 and TT:999 in BSI Interface file. Please let me know if I am missing any configuration Changes.

        2702115, 2711990,2724688,2732298,2731200,2722361,2736319,2737921,2736529

         

  • Hello Team,

    We have discovered an issue with the new 1099R employee copy form, HR_F_1099R_EE_18.  Currently, this form is not generating a second page with the pensioner has a second state with withholding.  Is anyone else having this issue?

    Thank you,

    Linda Mundy

  • Hi Team,

    Can you verify or let me know please, WA PFML wage deduction calculation are based on Total Gross earning or only on Taxable Earning ( Gross wage -(minus) Non Taxable contribution), for example Retirement plan contribution or others, or how your PFML base wages are accumulated in your organisation

     

    Thanks

    Ali

    • Ali Kazmi –  SAP is calculating WA FML based on Taxable Earnings (Gross wages minus non taxable contributions like retirement plan contributions).  I’m not sure about the WA FML legal definition of the gross wages subject to WA FML tax.

      Thanks

      Chandra

    • Hello Deborah,

      Phase I and Phase II Year End notes.
      2680733 – Year End 2018 Phase I for U.S. Tax Reporter
      2698729 – Year End 2018 Phase II for U.S. Tax Reporter

      Regards,
      Graziela

  • Hi Team

    PFMLA WA wages are not accumulating in /5U0 Total employee Tax  and also not displaying on Rem statement, but it calculate correctly, does  any one have idea ?

    Thanks Veeramony for your response, but Paid Family Leave WA will be calculated on Gross wage

    Thanks

    Ali

    • Thanks Ali.  Do you have any reference that says WA FML should not include retirement plan contributions? if so,  we need to adjust our tax model.  Ours were modeled after NY FML.

      As regards /5U0, in our case it does include the WA FML taxes in the payroll results. 

      For Rem Statement,  you would have to make config change to include the new tax types to appear in the Rem. Statement. Hope this helps.

      Thanks

      Chandra

      • Thanks Chandra.

         

        There is another issue if there is retro pays from 2018, retro pays getting added into PFML base wage, and calculate PFML deduction, which look not correct as PFML starts from 01/01/2019 and hour worked in prior months are not eligible for PFML  does any one have same issue or idea how to tackle that

         

        Ali

  • Hi Team,

    When running the 1099-RC, we are missing the 1099-RC ‘Employee copy’ and ‘Employer copy’ 2018 version forms after installation of 2018 Year End Phase II oss note (#2698729). Has anyone else experienced this issue?

    Forms:

    HR_F_1099R_EE_18′ (Employee)

    HR_F_1099R_ER_18′ (Employer)

    FYI – we have opened OSS incident: 10568 / 2019 1099RC Not generating new 2018 Employee or Employer Copy forms

    Max

  • Good morning everyone!!

    I have encountered an issue that I am hoping maybe someone can give me guidance on.

    This year we had to include our Group Term Life technical wage type /BT1 to Box 12 code C. We have a few employees with negative values therefore no W2 is being generated. A YANA entry have been done on IT0221 but when payroll is ran the wage is not being processed as expected. When comparing the PCL of wage types /BT1 to other wage types previously used on IT0221 both PCL 82 and PCL 74 (used in the rules read when processing IT0221) the values for wage type /BT1 are the same as the others. Has anyone ran into this same issue?

    Any feedback is greatly appreciated. Thanks again.

    Evelyn Campos

  • Can anyone give me an explanation of the yellow message below in regards to the Washington Paid Leaves that were implemented recently?

     

    At least one employee has different Paid Family/Medical Leave YTD

    Thanks,

    Katherine

    • Katherine James the error message indicate a tax model config issue.  Refer to note 2722361 for explanation:

      When building the virtual Tax Types 888 and/or 999, in case the system finds different YTD Wages for the non-exempt Washington Paid Family and Medical Leave relevant Tax Types, it will issue a message warning the user about a possible configuration error in Tax Model, because all these Tax Types should be calculated using the same taxable wages. In case the Display Log checkbox is marked in the selection screen of the Payroll Driver (US), the following message will be logged for each affected employee:

      Employee has different YTD wages for Paid Family/Medical Leave tax types (HRPAYUS_MESSAGES310)

      If the Display Log checkbox is not marked in the selection screen of the Payroll Driver (US), the following warning message will be logged only once in the general mesage section of the Payroll Driver (US):
      At least one employee has different Paid Family/Medical Leave YTD wages (HRPAYUS_MESSAGES311)

      If you receive this general message, you can execute the Payroll Driver (US) in simulation mode again with the Display Log checkbox marked to know which employees are affected.

       

      Thanks

      Chandra

      • Chandra,

        Thanks for taking the time to reply. I know which employees are affected but what I still do not understand is what is the possible configuration error? Are you able to provide some more details to what I should be looking for in the configuration?

        Thanks,

        Katherine

        • Katherine James please review the Tax model configuration for all of the WA PFL tax types.  In the tax model,  all of the PFL tax types that has been configured for WA (T5UTY) should have the same identical taxable wages (T5UTM).  So check if the tax combo mapped to these tax types are the same; if different, check if these have identical tax classes assigned in T5UTM.

          Thanks

          Chandra

          • Chandra,

             

            Thank you for your reply. I am still unsure of what I need to do since the taxable wages I see are all the same and the tax model looks ok. I guess I am not completely understanding what I need to be looking for so I am opening a ticket with SAP so someone can help me with my specifics.

            Thanks!

            Katherine

          • Hi Katherine,

             

            I am also seeing the same warning message for some of my employees. Did you get any response from SAP that why it is giving a warning? If yes, can you please share with us.

             

            Thanks,

            Bhairava

  • When trying to run the correct employees with Retroactive Changes under employee copy for a W2 in Tax Reporter it is NOT picking up the employee even though we did a PAUY YAWA retro adjustment for this employee after his W2 was run and prior to saving the filing date. Why will this employee NOT pick up? Any thoughts? What table or flag is used to pick up these retro changes for this radio button in Tax Reporter?

  •  

    Here is link from WA paid leave, and we called them and confirm Gross wages ( before any deduction)

    https://paidleave.wa.gov/employers#helpcat55

    What are gross wages?

    In Paid Family and Medical Leave, wages are generally referred to as gross wages without tips. Gross wages include, but are not limited to, salary or hourly wages, sick leave, vacation leave, holiday pay, bereavement leave and paid time off, bonuses, stocks as part of a compensation package and the cash value of meals and lodging when given as compensation.

    Wages are defined in statute (RCW 50A.04.010) as the remuneration paid by an employer to an employee (up to the Social Security cap for premium assessment)

  • We have loaded SAP Note 2736038-TR-Year End 2018 Additional US Tax Reporter Changes, along with it’s prerequisite note 2737197.  When reviewing the changes to the Hawaii W2 mag file, the system is repeating each record twice (RA through RF).  In addition, the system is creating 2 Hawaii W2 mag files.

    Is anyone else experiencing this issue?

    Thank you,

    LInda

     

    • Hi Graziela,

      I performed further research and discovered this HI W2 mag file error occurred after installing SAP Note 2587198, YE 2017 Additional TR W2 Mag File changes, which we did not load until May 2018.

      The SAP Note 2736038 -TR-YE 2018 Additional US Tax Reporter Changes did not correct the doubling of records and files for HI.

      Do you have any information on this issue?

      Thank you,

      Linda

  •  

    Hi everybody,

    Just FYI  ….for employers with PR reporting –

     SAP released Note 2743323 and associated Note 2743848 to correct the PR SSA file.

    Also, SAP note 2743729 was released for PA.

    If you come across any issues, please open V High incidence so that our support staff can help you out.  Also the solution document for TR has been updated with YE notes that were released after additional notes for Year End  2018 – TR Solution Document

    All the best,

    Mani

  • Hello community,

    The following notes are released:

    2741517 – TR: Year End 2018 Additional U.S. Tax Reporter Changes for Localities
    2742519 – TR: Wrong length of ExcessWages in Florida UI XML after applying SP
    2745587 – TR: Form 1099-R is created with only one page
    2745965 – TR: Year End 2018 Additional U.S. Tax Reporter Changes for NE, OK and RI

    Regards,

    Graziela

  • Hi Everyone,

    We are trying to upload the West Virginia W-2 file but are getting a Invalid File Format error.  I noticed that the RV record is blank, thus giving us the error.

    In our system, W-2 form HR_F_W2 is linked to form HR_F_MMREF_1_GEN for WV.  That generic file has blank information for RV.

    I will manually update the form to HR_F_MMREF_1_WV (Sequence 092) and regenerate the W-2s in test mode for the correct file be generated.

    This issue was addressed in note 2603381 – TR: Electronic File format for Form W-2 for West Virginia is printing Generic, released February 13, 2018, but it only applied to component SAP-HRCUS version 600, and we are on 604.  The manual steps in that note are what I will follow in my update.

    https://launchpad.support.sap.com/#/notes/2603381

    Is anyone else having this issue?

    Thanks,

    Larry Gershman

     

    Quick follow-up:  I made the change in our Sandbox system and ran for a couple of WV employees.  The RV line appeared with data but all of the data starting with position 33, First Quarter Tax Due, is zeroes.  Perhaps SAP can also look into this.

    Larry

    • Hello Larry,

      As per note 2588780:

      Attention: The Record RV is required to report data from the Form WV/IT-103 (Annual Recconciliation), which is not supported by the standard SAP solution. To report data on this record, you can follow one of the options listed below:

      1. If you have not run the production yet, or if you can re-run the production, then SAP suggests you to:
        1. Implement the new Business Add-In (BAdI) HRPAYUS_B_TR_TFF, method IF_HRPAYUS_TR_TFF~CHANGE_WVXX in order to fill in the positions as shown in the table below. Apart from “Number Of Tax Statements Transmitted” field, all other fields must not contain decimals and need to be rounded;
      2. If you have already run the production and a re-run is not possible, SAP suggests you to:
        1. Enter the related amounts in “Or Directly” field of RV Record for the positions as shown in the table below. Apart from “Number Of Tax Statements Transmitted” field, all other fields must not contain decimals and need to be rounded. Important: This option will not store the amounts in Cluster PCL4.

      Regards,
      Graziela

  • Hi Graziela,

     

    Is there any updated version of user guide available on Affordable care Act as of 2018? We are in possession of a 2016 one at the moment.

    Please advise.

     

    Thanks

    Madhu

    • Hi Madhu,

      This blogs post aims to cover only Year end issues.

      For ACA questions, there is a specific Jam group in which you can check this information.

      Please read SAP note 2700329 – ACA: FAQ Note for Affordable Care Act Reporting 2018

      Regards,

      Roger Oliveira

        • Hi Chandramouly,

          As this thread aims to provide information only for Year End process, we decide to keep them splitted into two different threads.

          If we add here ACA information it may mislead other members to post about it.

          This way would be very diffcult to us moderate and reply the post, as well, making impossible to you guys find a information.

          Regards,

  • Hi,

    In trying to create CORRECTED 1099R forms for 2018, we are getting only blank pages for the employee copy (form HR_F_1099R_EE_18).  Prior year forms work fine and the 2018 employer form (HR_F_1099_ER_18) works fine.  Has anyone anyone else seen this behavior, or otherwise been able to successfully print 1099RCs for 2018?

    Thanks,

    Gregg

      • Hi Graziela,

        Yes, SAP Product Support provided me with note:“2757513 – TR: Blank PDF form when trying to visualize a 1099RC employee copy”

        And this resolved the issue.

        Thank you,

        Gregg

  • Hello Graziela,  this is not related to YE.  However we are facing issue with respect to the MO new tax formula (note 2737549) implementation.  There is a pre-requisite note (2738114) mentioned that is required to be applied before implementing 2737549.  However there appears to be some confusion in the note 2738114 documentation. Note 2738114 documentation says it is applicable for SAP608 level (including the manual correction).  But when we try to implement via SNOTE, the note is rejected with message “Cannot be implemented”.  Can you guys clarify? I’m opening a message as well.

    Thanks

    Chandra

    • Hi,

      WE did implemented this note. However we do see an issue on PA record for position 501 number of employee counter counter stooped at 1 even though we have multiple employees.

       

      any idea? how this position gets updated?

      thanks

      gayathri

  • The new SUI laws for Indiana and Louisiana require we report an employee’s SOC. SAP has 2 tables for maintaining the SOC, table T5U25 for jobs and table T5U28 for positions. Tax reporter only outputs the SOC value when it is assigned to the position, V_T5U28_C. We have over 2000 positions in Indiana alone, but only 45 jobs.

    Standard SAP supports assigning the SOC at the job level, but tax reporter is not updated to read the job. This required over 2000 entries for Indiana. Using the job, as SAP delivered, resolves the issue. Please make the appropriate update in RPCTRCU8 (see note 2253023) to read the position then job if no entry is found for a position.