Skip to Content

U.S. Tax Reporter Year End 2017

Hello community,

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

SAP Notes

2588780 – TR: Year End 2017 Additional U.S. Tax Reporter Changes for WV

2594678 – TR: South Carolina SUI electronic file rejected by Tax Authority

2592961 – TR: Idaho W-2 electronic file rejected by Tax Authority

2593662 – TR: HR_F_MMREF_PR is not showing Roth Contribution information

2591465 – TR: Year End 2017 Additional U.S. Tax Reporter Changes for MS

2590720 – TR: W-2 Electronic File for Missouri not printing Federal Income Tax Withheld in record RS

2590703 – TR: Year End 2017 Additional U.S. Tax Reporter Changes for GA, NM and VT.

2589559 – TR: Short Dump in Log Manager when clicking to display a deleted Online W-2 PDF Form

2587198 – TR: Year End 2017 Additional U.S. Tax Reporter Changes For DC, HI, KS, MA, MT, WI

2585266 – TR: Transaction PC00_M10_ONW2 displays only the first page from an Online W-2 form

2583106 – TR: Year End 2017 Additional Changes for Puerto Rico Tax Reporter

2581466 – BSI: Tax Type 95 for South Dakota

2571096 – Year End 2017 Phase III for U.S. Tax Repórter

2579526 – TR: Online Selections for W-2 (3228) infotype incorrectly denies saving records due to TR production run

2567753 – TR: Q4/2017 Functional changes for U.S. Tax Reporter

2564514 – TR: Long time running Tax Reporter

2559178 – GARN: Runtime error TABLE_INVALID_INDEX for GRORD

2541636 – REC: Payroll Reconciliation Splitter background jobs issue

2545333 – Year End 2017 Phase II for U.S. Tax Repórter

2565244 – TR: Employee’s Last Name is not being displayed on Form W-2 for Puerto Rico

2559933 – TR: Tax Reporter W-2 selection-screen for test mode presents overlapping elements

2563715- When you run payroll, you get Runtime Error GENERATE_SUBPOOL_DIR_FULL with exception CX_SY_GENERATE_SUBPOOL_FULL

2546739 – TR: Tax Reporter attempts reading nonexistent payroll results for Form 941-X

2548989 – TR: Online W-2 generation error “Export error: Attribute ‘AT_TRW2_RUN_TYPE’ is not valid”

2518875 – Year end 2017 Phase I for U.S. Tax Reporter

2519671 – U.S. Tax Reporter Year End 2017 Announcement

2499667 – PY: When-paid entries missing in CRT when executing the payroll driver for US/CA

2464078 – TR: 1099-R User Guides for HCM US Tax Reporter configuration

2464161 – TR: W-2 User Guides for HCM US Tax Reporter configuration

2463999 – TR: Tax Reporter User Guides for HCM US Tax Reporter configuration

2466222 – TR: Year End Tax Reporter Documentation for HCM US Tax Reporter

Knowledge Base Articles

2588925 – Tax type 87 for New York

2552908 – Incorrect formulas in BTXFORM table

2529963 – U.S. Tax Reporter Year End 2017

2480185 – Tax Reporter Solution Educational Videos

Additional information

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

To access HCM US site, please go to and select United States, then select Find all US-related documentation, then choose SAP ERP U.S. Tax Reporter Solution document.

To be able to access the Year-end 2017 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.

Thank you,

Kind regards,

Graziela Dondoni

You must be Logged on to comment or reply to a post.
  • Hi Everybody,


    Thanks for your candid feedback, appreciated. Taken!


    Now, one thing that we also expect from our decades old users and experts is to analyze as to why SAP delivered the way they delivered and guide other newer member of SAP community to think in the right direction. It is not that SAP has not delivered similar code to do calculation before. Yes, we had a few options how we could have delivered this Legal Change and we picked the one that could be delivered in short time. I have been in touch with Authority from December last year. They published the spec on Jan 23rd only after I escalated expressing how employers and software vendors are tense because of them not publishing yet and with the type of change they are asking. I even expressed that they need to think from Software vendors point of view as well when releasing such changes that late.


    The new requirement on RV record for State of WV is pertaining to Form IT103 (Annual reconciliation). This form is not a new form for employers and SAP does not deliver form IT103. You can use Tax Reporter to generate one though and I am sure you (employers) have been submitting this form in past years.  Above all this is not an employee level form but at a company level. So you have different options –

    1. To re-run Production and have the amount in cluster you can use –
      1. BadI
    2. Due to time constraint and not being able to re-run production (this will not create entries in cluster), you can
      1. Plug in the amounts in “Ordirectly” field of RV record. This is not complicated, is it?


    Yes, one thing that we could have done better (which due other Year End tasks and urgency to release this SAP Note was missed)  is to mention in the SAP Note that users who do not wish to re-run Production can use “Ordirectly” field on RV record. We have already updated and released  the SAP Note 2588780.


    Blogs are open for all users to help each other and guide the users who are not familiar with the potential of Tax Reporter Solution. I would request all experienced Users/independent consultants using this blog or any other Jam site to help others on how they can achieve the results. In this case I would have expected that a response would have been something like  - “You don’t have to write the custom code and re-run Production but plug in entries in “Ordirectly” for the applicable location on RV record”.


    We already have this item on our pipeline to be evaluated for automatic calculations and to be considered for next year end.  Again this is for consideration and is subject to change based on prioritization of Legal Changes that might come up.

    Best Regards,
    Mani Kak
    Product Manager, Globalization Product Management

    Local Solutions. Global Success.
    Visit GS Jam for more info
    SAP Globalization Services  SAP HR USA

    GS-US finder page  TR Solution Document


    • Thank you for the update Mani.

      We will consider option 2 provided by you (and updated in blog) for this year and hope you will come up with the full / permanent solution by next year (2018 year end).


      Thank you,


    • If you are asking for Tax Reporter then no, there is no year round blog/Jam. This Blog is only active and actively monitored by some during the year end time.

      We would like to see how many SAP customers are actively participating, helping each other and are benefitting from the blog before we open it for Year round (blog/Jam). Currently when i click on some of the names, i don't even know which company they are employees of and/or independent consultant.

      we have a JAM site for Benefit Solution - ACA in pilot phase.

      Take Care,



    WV is using this form HR_MMREF_1_GEN which is a generic form and is used by other states such as AZ, DC, ND and DE.


    If we update the "or directly" field with WV's information, how will it affect the forms used by these other states?

  • Hi Graziela,

    Should an update to a Federal or State EIN trigger a W-2C in Tax Reporter?

    In this example, the company generated W-2s for all employees and later noticed the EIN for OH was incorrect. They updated T5UTI and now they want to issue W-2cs. The W-2s have been filed with an as of date. They select manual selection for W-2Cs and use a later as of date. However, the W-2C is not being produced. Is this the expected behavior?


  • Hello Folks, we are applying the new BSI Cyclic S (10.0s) and found a new local tax authority named "UNKNOWN LOCAL" , BSI tax code - 00248888. Anyone know anything about this new "unknown" tax authority? its mapped to Maryland (MD).




  • Hello

    IRS has reduced the limit for HSA to $6850  (Bulletin No. 2018–10). Will a SAP note be released for this?

    If so, when is it expected?




    • Hello MANDAR MULEY ,

      I believe that you are referring to the legal change published on

      Am I right?

      If so, I recommend you check the legal change notification at the link above. The development team post there information about upcoming legal changes and its planned release date.

      You can also filter the results for the desired subjects.

      Please notice that this Blog Thread aims to address issues only with Tax Reporter and Year End process, posting another subjects may cause confusion.


      Roger Oliveira

  • Hello,  We're having trouble with our 1st quarter 2018 SC SUI electronic filing.  Has anyone been able to produce the new EFW2 format?  Our system is only producing MMREF-1 and SSA Disk and the state is rejecting those.  We've applied Notes 2594678 & 2618261.


    Lou Ann


      Hi Lou Ann,


      Did you have any luck resolving this issue?

      We are having the exact issue and we also applied the notes you mentioned and it didn't work for us either.




  • Hello Team,  I had noticed something on the Arizona State Tax withholding formulas that I wanted to bounce it off with the folks here (including SAP folks on this blog).  Tax formulas are delivered in table BTXFORM;  for Arizona state, (BSI authority#), there were few incorrect formulas created by the BSI-SAP Synch program (TCODE: HRPAYUS_SYNC_TAX_DT).  Since these formulas were not in BSI (formula numbers 36 to 41),  they were ignored and calc defaulted to default formula for the state.  SAP identified the issue and raised a note 2552908 to manually remove these formulas from table.  However this note wasnt attached to any HR Support pack, which is unusual.

    I opened a message with SAP but the response I got was not convincing.  According to the SAP message this note is a knowledge article and wont be released with any support pack.  This is an unusual and weird stand to take, particularly when this table is a SAP delivered and maintained table and issue was caused by the SAP standard program.  My only concern here is many customers are going to miss this supposedly "knowledge article" note unless the issue is identified through internal process.  By attaching to a support pack, even though its a manual implementation note,  it will ensure all customers have an opportunity to implement them.




      Hello Chandra,

      I have wrote the SAP Knowledge Base Article 2552908 and this will not be included in any Support Package as this doesn´t contain any code corrections.

      The fix for the Synchronization tool was delivered in SAP note:
      2332038 BSI: Tax Formulas are incorrectly retrieved by value-helps in the system

      Once note 2332038 you don´t need to apply the manual steps from this KBA 2552908.
      P.S. Note 2332038 has been delivered by SP

      Hope this clarifies.


      • Thanks Graziela.  You do have to apply note 2552908 after applying note 2332038.  Note 2332038 only fixes the Sync tool so it doesnt create such problems in future.  However the incorrect formulas created prior to the fix would have to be removed (note 2552908).  Unless these incorrect formulas are removed from the system,  and if an employee chooses any of these incorrect formulas (formula number 36-41) via ESS or by any other,  BSI will default to the standard formula creating confusion.



        • Hi Chandra,

          Yes, first you apply note 2332038 and only the manual steps from KBA 2552908 will fix the incorrect formulas. But there isn´t any source code in this KBA, that´s why there isn´t any Support Package associated to it.


          • Thanks Graziela.  I understand there is no source code and this requires manual implementation.  Are we saying notes are included in the support package only if it has source code corrections or those that doesnt require manual implementation?  I'm not sure if that is correct.  There are several instances of 'manual' only note that are included in the support package. The most recent ones being the new Oregon tax type 96, which is included in the support package (SP#56) but needs manual implementation.



  • Hi Community,

    I would like to inform I have created the blog for Year End 2018:

    You may want to follow the blog!!! I will update it with the some important information till the end of this week.