Skip to Content
Product Information
Author's profile photo Graziela Dondoni

U.S. Tax Reporter Year End 2021

Hello community,

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

To be able to access the Year-end 2021 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 application. You can find detailed information about the Announcement of legal changes on this blog.

Year End notes

3082167 – U.S. Tax Reporter Year End 2021 Announcement 
3085142 – Year End 2021 Phase I for U.S. Tax Reporter -> You can just apply this note via Support Package
3082151 – W-2 / 1099-R Forms, Envelopes and PR Approval letter for year 2021
3100510 – Year End 2021 Phase II for U.S. Tax Reporter -> You must apply the prerequisite note and run the report NOTE_3100510, which is delivered in the prerequisite note:
3120702 – (Prerequisite objects for SAP Note 3100510)
3132965 – Year End 2021 phase III for U.S. Tax Reporter -> You must apply the prerequisite note and run the report NOTE_3134256, which is delivered in the prerequisite note:
3134256 – (Prerequisite objects for SAP Note 3132965).
3123716 – TR: Short dump when generating a Form W-2 that reports a 3-Digit Tax Type
3135634 – TR: Eugene Tax Type 106 not processed into Third party for W2 (FED) TemSe file
3136264 – TR: multiple blank output W-2 form pages for New Jersey employees
3138406 – TR: Year End 2021 additional U.S. Tax Reporter changes.
3138997 – TR: Q4/2021 changes for OH ICESA file format

 

Additional notes

2464161 – TR: W-2 User Guides for HCM US Tax Reporter
2464078 – TR: 1099-R User Guides for HCM US Tax Reporter

Correction notes

3118379 – TAX: RPCALCU0 ignoring tip income after SAP Note 3054328
3118875 – RPCALCU0: technical changes regarding performance for TaxFactory SaaS
3099278 – SAP GUI F4 Amodal control : Search help Internal error table format.

KBAs (Knowledge Base Articles)

2480185 – TR: Tax Reporter – Online W-2 Enhancement Video
3081097 – KBAs (Knowledge Base Articles) for Payroll USA
3124528 – W-4 Legacy Data – Changes in IT0210

ASUG Webcast: HCM U.S. Payroll and Tax Reporting 2021 Year End Update

  • ASUG webcast was concluded on October 7, 2021.
  • Recording and slide deck for the ASUG webcast can be found here.
  • Slide deck is also attached to the SAP Note 3082167 – U.S. Tax Reporter Year End 2021 Announcement.

Limits for 2022

3079731 – BEN: Limits for HSA in Tax Year 2022
3117309 – BEN: Annual limits year 2022
3136963 – GARN: IRS Publication 1494 for tax year 2022.

Kind regards,
Graziela

Assigned Tags

      287 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Darci Meyer
      Darci Meyer

      Hi Graziela,

       

      We were adding the MMU 2020 W2 BOX 12 configuration with Tax Form Group W068.  The correct amounts and the letter D are showing as expected.  The year 20 is not populating as expected.  Has there been a change related to this configuration?

      We would appreciate any information you might have for our issue.

      Thank you,

      Darci

      Author's profile photo Carlos Accorsi
      Carlos Accorsi

      Hi Darci,

      Would you please confirm if the year 20 is not populating at all on Box 12? Or is it being populated with an incorrect value?

      Kind Regards,
      Carlos

      Author's profile photo Darci Meyer
      Darci Meyer

      Good Morning,

      Since our original message we have found  Box 12 MMU  for the tax year 20 (Tax form field showing as  D20- USERRA 401K) is still not working as it has in the past.  When we produce the W2, the field is now only showing the first two characters whereas in the past it has been showing the first three characters in the W2 Box 12

      Past = D18, D19

      Current = D2.

      We found we could edit the text as 20D- USERRA 401K and then only the 20 showed in Box 12.

      Please let us know if you need any additional information.

      Darci

      Author's profile photo Carlos Accorsi
      Carlos Accorsi

      Hello Darci,

      Thank you for the information.

      This scenario is being reviewed by the development team.
      As soon as I have an update, I will let you know.

      Thank you,
      Carlos

      Author's profile photo Carlos Accorsi
      Carlos Accorsi

      Hello Darci,

      This issue has been addressed by SAP Note 3138872 - Tax Year is missing on W2 form for USERRA.
      Please apply it on your system and then retest the scenario.

      Best Regards,
      Carlos

      Author's profile photo Gayathri Nannapaneni
      Gayathri Nannapaneni

      Phase III note is asking for Package while implementing SFP. what to use for this? Information not provided in manual instructions. we tried using local object and Z*, none worked.

      Thanks

      Gayathri

      Author's profile photo Yusef Seidy
      Yusef Seidy

      Pretty sure the package for tax forms is PC_TAX.

      Author's profile photo Gayathri Nannapaneni
      Gayathri Nannapaneni

      Hi,

      Does anyone experiencing issues with PR-W2 rerun? when we delete our spools and rerun, we could see the job count is very less when compared to original run and only few people have spools created.

      Thanks

      Gayathri

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Gayathri,

      I don´t see any other customer reporting this and I notice you already opened a case for SAP.
      My colleague is checking this for you.

      Kind regards,
      Graziela

      Author's profile photo Sandra A. Pelkey
      Sandra A. Pelkey

      Good morning,

      Do you know when the 2022 Tax Tables in BSI Bulletins and Publication 1494 will be out?

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Sandra,

      Some changes for 2022 were released by BSI in TUB 071.
      About the Publication 1494, do you have the IRS link with the changes for 2022? I just found the link for 2021.

      Thank you,
      Graziela

      Author's profile photo Sandra A. Pelkey
      Sandra A. Pelkey

      Thank you Graziela for the update,

      I only see Publication 1494 for 2021 on IRS website.  Do you know when Bulletin 72 will be released?

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Sandra,

      We didn´t receive the API notice yet about Bulletin 72, so we don´t have the date.
      Could you please reach out BSI to get this information?

      Thank you,
      Graziela

      Author's profile photo Sukhbir Singh
      Sukhbir Singh

      Hello Graziela,

      Can you confirm if BSI tub 71 has all FED related changes for 2022? We are planning to import new tub today and don't want to do it twice. 

      It does appear from the documentation below -

      Authority BSI System Code Tax Type QF Update Effective Date Change Description
      FEDERAL 00000000

      WITHHOLDING TAX

      TAX TYPE 001

      YES 01/01/2022

      Changes the wage bracket tables.

      Increases the Nonresident Alien ( NRA) additional withholding amount for 2019 or earlier Forms W-4 FROM $8,250 TO $8,650.

      Increases the Nonresident Alien ( NRA) additional withholding amount for 2020 or later Forms W-4 FROM $12,550 TO $12,950.

      Increases the Foreign Earned Income Exclusion (FEI) annual limit from $108,700 to $112,000.

      Thanks

      Sukhbir

      Author's profile photo Sandra A. Pelkey
      Sandra A. Pelkey

      Good afternoon,

      We reached out to BSI and some 2022 Federal Tax updates came out on Bulletin # 65

       

      Author's profile photo Jennifer Stnons
      Jennifer Stnons

      Publication 1494 (2022) (irs.gov)

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Jennifer,

      Thank you for sharing the link.
      I have reached out Developer to see when the note will be published.
      Anyway, all the changes can be performed manually, using the publication as reference.

      Kind regards,
      Graziela

      Author's profile photo Chandramouly Veeramony
      Chandramouly Veeramony

      FYI - note 3136963 - GARN: IRS Publication 1494 for tax year 2022, is now available for the 2022 tax levy updates.

      Author's profile photo Hemanth Krishnakumar
      Hemanth Krishnakumar

      WASHINGTON CARES ACT TAXES TYPE 113 AND 114.

      Hi Team,

       

      We have employee in Washington who are eligible for WA CARES FUND LTC TAX: TAX TYPE 113 & WA CARES FUND LTC TAX ER: TAX TYPE 114.

      BSI has rescinded in TUB 70. Any idea when BSI will re-activate them or do we need to keep these taxes changes as optional rate override in BSI system. 

      Need your input.

       

      Author's profile photo Chandramouly Veeramony
      Chandramouly Veeramony

      There was a notification from BSI yesterday saying they will reactivate those two tax types. But there was no indication of when they will come through. Our guess is it will be included in TUB 72.

      Author's profile photo Chandramouly Veeramony
      Chandramouly Veeramony

      Graziela Dondoni and team - SAP has released a note 3136513 (BSI: WA cares fund tax updated for tax types 113 and 114) for the WA cares fund.  I believe this note is to reactivate these tax types in SAP. However, what is not clear is do we also need a corresponding TUB from BSI to fully reactivate these tax types.  As of now, these tax types are not active inside the BSI, so even if we reactivate the tax types in SAP and pass it over to BSI, BSI will still not calculate these taxes, right? could you clarify this for us?

      Thanks

      Chandra

      Author's profile photo Suneetha Venati
      Suneetha Venati

      When we are trying to apply SAP note :3136513 , it's getting message "Cannot be implemented". Any one is facing similar issue ?

      we have already implemented below SAP notes also.

      3103555 BSI: Tax Types 113: WA Cares Fund LTC Tax - EE and 114: WA Cares Fund LTC Tax - ER
      3134644 BSI: WA cares fund tax postponed

      Thank you

      Suneetha

      Author's profile photo Roger Oliveira
      Roger Oliveira

      Suneetha Venati the SAP note 3136513 do not have any correction instructions.

      This way, this note cannot be applied in SNOTE transaction as there is no object change to be done.

      Basically this is an informative note.

      Author's profile photo Suneetha Venati
      Suneetha Venati

       

      Thank you for the update Roger.

      WA Long Term Care is not deducted after updating the TUB 70 . We are running  the payroll on January 10th . Business wants to deduct the WA Long Term Care tax in Pay period 01 , is there any workaround to deduct the WA LTC tax ?

      Thank you

      Suneetha

      Author's profile photo Aman Kumar
      Aman Kumar

      Tub 73 is now available. WASHINGTON WA CARES FUND LTC  taxes have been reinstated.

      Author's profile photo Stanette Balser
      Stanette Balser

      Hello,

      We are processing our weekly period 1/2022 payroll and the URME Test run differs from the LIVE run with the Test run matching the wage type reporter total amount.  We have multiple company codes but actually pay from only one.

      We only process garnishments (HR Payee Type 4) in our 3PR and are in a freestanding HCM system.  It appears we have some missing HR Payee numbers when I review the T51RH table and several HR Payees have no HR PAYEE TEXT data.

      We select the Issue Separate Check to Vendor checkbox on each PA0194 record due to a limitation in our FI system.

      I create the FI vendors for our garnishments in our HCM system using FK01.

      I am stumped on what would cause URME itself to work differently for TEST and LIVE runs with TEST matching the Wage Type Reporter total of all our Garnishment WT amounts for the period.

      Any insight is appreciated!

       

       

       

      Author's profile photo David Adams
      David Adams

      This is not the proper thread for this question, but I will attempt to answer it anyways.

      When 3rd party was released many years ago, there were issues with linked creditors, adjusting due dates, etc.  Because of this SAP does not recommend running RPURME00 for only one creditor type.  It does not cause issues in simulation, but can cause problems in production runs.

      There is nothing wrong with running 3rd party remittance for only garnishments, but you need to configure the system so it knows that is all it is running for.  You need to deactivate all other wage types from processing through 3rd party, and then you should be good to go.

      If you run 3rd party again in simulation without specifying the creditor type, and turn the log on - you should be able to see what wage types you have set up incorrectly.  While it is good to clean up the HR Payee tables, your first priority should be setting the wage types correctly.

      As far as the HR Payee tables, whomever deleted payees might have done it incorrectly.  If they did, you might still have supporting entries set up for wage type details assigned to a creditor that does not exist.  This is easy to find by adding the creditor back in development with a dummy name, deleting the lower level entries and then deleting the credit.  WARNING - do not ever delete Ceditors that have actually been used in production.  You can stop using them, and reassign the wage types but you need to leave the creditor there as production has entries referring to it.

      Author's profile photo Stanette Balser
      Stanette Balser

      Thank you David!  I was unaware SAP's recommendation and your information allowed me to correct the issue.

      Much appreciated!

      Stanette

       

      Author's profile photo Mandar Muley
      Mandar Muley

      Hello

      Has anyone noticed any issues with HR_F_MMREF_1_AL (TEMSE file for AL)? We are seeing additional data after the header record and before RS record.

      Screenshot is attached.

      Wanted to check before reporting an incident to SAP.

      HR_F_MMREF_1_AL%20Issue

      HR_F_MMREF_1_AL Issue

      Thanks

      Mandar

      Author's profile photo Cindy Rheinlander
      Cindy Rheinlander

      Our file for HR_F_MMREF_1_AL looks correct with a RA, RE, and RW record between header and RS record.  Do you have a carriage return configured in header record, location 010?  Possibly that is missing?

      Author's profile photo Mandar Muley
      Mandar Muley

      Hi Cindy

      We tried with CRLF at location 10 as well...but it did not resolve the issue.

      Anyways have raised it with SAP.

      Thanks

      Mandar

      Author's profile photo Stanette Balser
      Stanette Balser

      Hello,

      We are executing PU19 test runs and receiving a short dump for one tax company on the HR_F_MMREF_1_OH output.    We are on HRSP H0 And EA C1.

      This is the first year for the failing tax company to execute PU19 outputs.

       In the source code, the termination point is in line 679 of (Include)
       program "RPCTRPUT".
       The termination is due to exception "CX_SY_CONVERSION_NO_NUMBER" occurring in
        procedure "PREPARE_ITEM_FOR_TAPE" "(FORM)".
       This exception was not handled locally or declared in the RAISING
       clause in the procedure's signature however.
       The procedure is in program "RPCTRPU0". The source code begins in line 638 of
       (include) program "RPCTRPUT".
      It appears to be looking for a rate conversion but I don't see any rates are contained in the output format.
      Has any else had this issue?
      Thanks,
      Stanette
      Author's profile photo David Adams
      David Adams

      Did you apply this note?

       

      Component:PY-US-TR
      Priority:Correction with high priority
      Category:Program error
      Release Status:Released for Customer
      Corrections:3
      Manual Activities:0Entry successfully validated
      Prerequisites:0

      Symptom

      In the standard system as currently delivered, when you run the Tax Reporter (PU19) transaction for Form W-2 and you have amounts for a 3-Digit Tax type for example, Tax Type 106, the following dump is generated:

      • Runtime Errors: CONVT_NO_NUMBER
      • Exception: CX_SY_CONVERSION_NO_NUMBER
      • ABAP Program: RPCTRPU0
      Author's profile photo Stanette Balser
      Stanette Balser

      Thank you for the suggestion. Unfortunately, it did not correct the issue.

      Regards,

      Stanette

       

       

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Stanette,

      Are you using any SAPScript from in the generation?

      Kind regards,
      Graziela

      Author's profile photo David Adams
      David Adams

      IF pv_text = true.
      * required when i51t3-amprp 1 - 4
      lv_t_reslt_value = pv_tvalue+i51t3-offst.
      lv_nreslt_value = pv_tvalue+i51t3-offst.
      * For rates we need to do this in order to come up with
      * the right value.
      CLEAR i5ut3-taxfg.
      LOOP AT i5ut3 WHERE txitm = i51t3-txitm
      AND taxfg CA '6789'.
      EXIT.
      ENDLOOP.
      IF i5ut3-taxfg CA '6789'.
      lv_rate_reslt = lv_t_reslt_value * 100.
      lv_nreslt_value = lv_rate_reslt.
      ENDIF.
      ELSEIF i51t3-amprp CA '1BE3DA'.
      lv_nreslt_value = pv_value * 100.
      ELSE.
      lv_nreslt_value = pv_value.
      ENDIF.

      I would set a break point on the top line that I pasted, which is from the form you provided.  This is where it is blowing up.  Then, you can single step through to see the exact line that is causing you the short dump.

      Once you figure out the line that is causing the short dump, you should be able to look in the variables in prior lines to determine what is trying to be converted.  By doing this, you should be able to isolate what part of the form you are using that is causing the error, and figure out what is going wrong.

      Sorry that this is vague, but this should get you into the magnetic tape structure and subsequently get you to a field in T51T3 that access a tax form group or something like that.

      I am glad to try and help more, but you need to get further along in debug so we have a clue as to what is blowing up.

       

       

       

       

      Author's profile photo Stanette Balser
      Stanette Balser

      Graziela,

      I am loading TUB 72 and received an error in the Sync tool when executing the live run.

             Error Text:  It was not possible to insert entry WA 4320201231 in table T5UTX

      I have checked the table entries for WA and the starting entry reflects as below.

      WA Washington 043 Employee Medical Aid Fund Tax 01/01/2011 12/31/9999 9,999,999.99 0.010000000

      The Sync Tool table shows it is attempting to update the T5UTX table as indicated in the screenshot.

      WA%20043%20date%20issue%20T5UTX

      WA 043 date issue T5UTX

       

      Thanks,

      Stanette

       

      Author's profile photo Carlos Accorsi
      Carlos Accorsi

      Hello Stanette,

      The issue you are facing is caused when there is a delinquent record for the tax rates on table T5UTX.
      In order to correct it, you will have to update table T5UTX manually and then rerun the Sync Tool.

      You may refer to 2550829 - Synchronize Payroll Tax Data Update Error.

      Kind Regards,
      Carlos

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Carlos Accorsi we replied the thread at same time... kkkkkk

      Author's profile photo Carlos Accorsi
      Carlos Accorsi

      Graziela Dondoni This is a great team work 🙂

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Stanette,

      This is due the overlap for tax type 043.
      You need to change it manually in T5UTX to fix this overlap.
      After this you will be able to run the Sync tool.

      Kind regards,
      Graziela

      Author's profile photo Padmanabh Srinivas
      Padmanabh Srinivas

      Hi Graziela,

      We have encountered an issue with /Qxx because of the application of OSS Note 3101020, which was released on Dec. 27th 2021.

      We have raised OSS Incident 16164 / 2022 with regards to this issue.  Please look into this at your earliest convenience.

      For example,

      Say, EE has /Q03 in RT and TCRT in last Biweekly period 26.2021, when the OSS note 310120 had NOT been applied yet.

      Also employee's /303 & /603 for FED is already over yearly taxable ceiling $142,800, say $152,800.

      After payroll run for period 26.2021, the note 3101020 was applied.

      Now, in period 01.2022, there is retro back to 26.2021 and the schema (ADDCU function in Final processing) is creating negative amount for YTD /Q03 in TCRT.

      This negative amount is equal to 142,800 minus the YTD /303 in TCRT.  In this case, it would be Negative 10,000 (142,800 minus 152,800).  

      Regards

      Paddy

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Paddy,

      I colleague is assigned to the case and will  verify the issue.

      Kind regards,
      Graziela

      Author's profile photo Kelli Dixon
      Kelli Dixon

      Hi Graziela,

      We see that SAP Note 3136613 has been released stating that BSI has decided to reinstate tax type 113 and 114.  Do we know what BSI regulatory bulletin/TUB this will be delivered in?

      We are currently at BSI bulletin/TUB level 64 and are holding off on applying current BSI bulletins/TUBs until the reinstatement of the tax types 113 and 114 are delivered.

      Thank you in advance for your prompt response.

      Regards,

      Kelli Dixon

      Author's profile photo Carlos Accorsi
      Carlos Accorsi

      Hello Kelli,

      BSI confirmed that the Tax Types 113 and 114 will be reinstated on Regulatory Bulletin 73, released on January, 19th.

      Thank you,
      Carlos

      Author's profile photo Matt Fraser
      Matt Fraser

      Ah, you're faster than me! 🙂

      Author's profile photo Kelli Dixon
      Kelli Dixon

      Dup

      Author's profile photo Kelli Dixon
      Kelli Dixon

      Hi Carlos,

      Thank you for the prompt response.

      I am surprised and concerned that BSI is releasing the update so late in the month.

      As I state in my comment above, we are currently on BSI Bulletin/TUB 64, therefore have not applied the BSI Bulletin that delivers the OASI max or the BSI Bulletin that delivers the 2022 Federal Tax Tables.  So we are not in compliance with the Feds right now.

      BUT if we were to apply up through BSI Bulletin/TUB 72, we would not be in compliance with taking the WA Cares Fund tax.

      Regards,

      Kelli

       

      Author's profile photo Matt Fraser
      Matt Fraser

      I think the state of the law is currently unclear, pending a decision by the state legislature next week. It has to do with whether or not the governor had the authority to tell employers to stop collecting the premiums or not. For this reason, at the moment some employers are electing to collect the premiums, and some are not. Mine is not, so we have the taxes disabled in our tax model. And, we are waiting for 73 to become available next week before we move the latest TUBs in. We did need some of those TUBs, not only for the Federal withholding changes, but also for the latest PFML rate changes, but as the PFML change already came far too late, we handled that with an override in BTXRATE.

      The main thing that getting TUB 73 in will do is enable you to have a choice about whether you withhold premiums or not (via the tax model), whereas if you put 70 in the choice will not be there -- you won't be withholding.

      We plan to move 70, 71, 72, and 73 in after 73 is released, at which point we'll remove our PFML override from BTXRATE, but continue to control WA Cares premiums via the tax model until we get a determination from the legislature and our legal office. As for the Federal withholding rate change, the actual rates didn't change, but the wage brackets expanded higher, so the net result is that some employees may see a reduction in their withholding once 71 is put into place. That should retro back to the beginning of the year, meaning employees will get a one-time bump in take-home pay, rather than a one-time smaller take-home check. They're less likely to complain about that!

      Author's profile photo Kelli Dixon
      Kelli Dixon

      Hi Matt,

      Yes there is some confusion, though in the Governors statement on 12/23/2021, the state of Washington is following the law and will have to begin collecting money from state employee paychecks as of January 1st.

      Author's profile photo Matt Fraser
      Matt Fraser

      Kelli,

      I think it was Carlos who responded to this same question earlier, though I can't now find the actual response. He said that the reinstatement of tax types 113/114 would be in TUB 073 and that is scheduled to be released on January 19th.

      Cheers,
      Matt

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi community,

      Blog updated with notes:
      3135634 - TR: Eugene Tax Type 106 not processed into Third party for W2 (FED) TemSe file
      3136264 - TR: multiple blank output W-2 form pages for New Jersey employees

      Kind regards,
      Graziela

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi community,

      Blog updated with note:

      3138406 – TR: Year End 2021 additional U.S. Tax Reporter changes.

      Kind regards,
      Graziela

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hello community,

      Blog has been updated with SAP note:

      3138997 - TR: Q4/2021 changes for OH ICESA file format

      Kind regards,
      Graziela

      Author's profile photo Eray Kocaman
      Eray Kocaman

      Hi Graziela,

      We generated the file and tried to upload to the agency website. At first it said missing the  name , phone and email address – so we added these. Then it said it was an invalid file layout. Do you want me to raise an incident?

       

      Thanks

       

      Author's profile photo Eray Kocaman
      Eray Kocaman

      I got the file to load the leading top line is the issue – spaces instead of blanks when it comes to adding submitter, phone number and email address – so good there but not sure it is something SAP needs to fix.

      Author's profile photo Euna Lee
      Euna Lee

      Hi,

       

      Can anyone suggest what needs to be checked for "SOAP Framework error: SOAP Runtime Exception: CSoa pExceptionTransport : HTTP se.." after every ADS connection check is successful?

       

      Regards,
      Euna

      Author's profile photo David Adams
      David Adams

      Take a look at ABAP section in Note 944221 - Troubleshooting if problems occur in forms processing

      Author's profile photo Euna Lee
      Euna Lee

      Did that. Passed all the check with flying colors. Makes it even more frustrating... , but Thank you for the response, David.

      Regards,

      Euna

      Author's profile photo David Adams
      David Adams

      I would be glad to try and help you resolve this, but it is tough given the very limited information you have provided.  I think if you would take time to post answers to these questions, it might even help you solve this yourself.

      1. What steps are being processed to create this repetitive error, and where are you seeing it in a spool?
      2. What system are you performing these tests in?  DEV?  QAS?  PRD?
      3. Are you running the utilities in the same system that you are getting the error in?
      4. Did you actually print the test adobe form from the note I gave you or did you just run the step.

      If the issue is in Tax Reporter then have you made sure your configuration is pointing to an appropriate printer set up for Post Script?

       

      Author's profile photo David Adams
      David Adams

      Additional information I found from past issues.

       

      The Device Type names that you have provided are not listed in the SAP Central Note for Printers/device Types

       

      https://service.sap.com/sap/support/notes/8928

       

      However, you can again re-check this note with your printer model and check what suitable device types should be used. As you will find inthis note:

       

      "Device type definitions are stored completely in tables and can be individually adapted, modified or enhanced. If SAP performs such an adjustment for a customer, it constitutes a consulting service, and is generally charged seperately"

       

      SAP has now released the SAP Printer Vendor Program - https://service.sap.com/sap/support/notes/1130927, printer manufacturers can develop and release device types for their printers.

       

      https://service.sap.com/sap/support/notes/1100779 contains a list of all participants

       

      Information about the support for new printer models is contained in the "Printer Vendor Wizard Note" of the relevant manufacturer. A complete list of all "Printer Vendor Wizard Notes" is available in Note 1097990. If your printer model is not listed in one of these "Printer Vendor Wizard Notes", proceed as described in Note 1103826.

      Author's profile photo Euna Lee
      Euna Lee

      Hi David,

       

      Sorry for the delayed response. It's been just hectic with everything.

      We ended up with restarting ADS system and it fixed the issue.

      Thank you so much for all the info.

       

      Regards,

      Euna

      Author's profile photo Hemanth Krishnakumar
      Hemanth Krishnakumar

      Hi Team,

       

      We applied TUB 70 till 73 in BSI. Upon running the sync tool in SAP, iam getting this error message which is attached below. Can i add this entry in T5UTX for Washington tax type 33? Please take a look and kindly do the needful.

       

      ERROR%20MESSAGE

      ERROR MESSAGE

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Hemanth,

      I already replied your question:
      ISSUE WITH TUB 73 | SAP Community

      Kind regards,
      Graziela

      Author's profile photo Matt Fraser
      Matt Fraser

      Hi Graziela,

      I just got this error too, and I noticed that quite a few customers mentioned earlier in this thread having this problem (it is occurring for both tax types 33 and 43). Unfortunately, Note 2550829 seems to be out-of-date. For one thing, the Sync Tool no longer includes "Effective Dates," so everyone is doing "Option 3" all the time with every sync anyway, yet the problem persists. For another, T5UTX cannot be edited directly in SM30, the maintenance view V_T5UTX has to be used instead, so the Note should probably reflect that. And, finally, there should probably be some guidance as to how to properly edit T5UTX, because it's not always clear whether a line should be deleted entirely, have its start date edited (which causes weird artifacts and new rows to be inserted), etc.

      Since so many customers are experiencing this same error, many for the first time after years of problem-free syncs from prior TUBs, it would be helpful if we could see exactly what V_T5UTX for WA 033 and 043 is supposed to look like, since that is the one that seems to be hanging almost everyone up. Or, perhaps this needs to be escalated to BSI, so that they issue a "fix" in the next TUB?

      This is what the error looks like for me:

      Initial%20error%20message

      Initial error message

      And what the sync tool tried to insert:

      Sync%20Tool%20inserts

      Sync Tool inserts

      And what the table looks like before the sync attempt (and after, since it fails):

      V_T5UTX%20WA%20033-043%20overlaps

      V_T5UTX WA 033-043 overlaps

      It's easy to see the incorrect overlaps in 033 and 043 between 1/1/2011-12/31/2018, 1/1/2019-12/31/2019, and 1/1/2011-12/31/9999. I'm assuming that final row end-dated 12/31/9999 should have had a start date of 1/1/2020? But just directly editing that row to change the start date seems to do some weird things. And, since we all have pretty much the same error, this was clearly delivered as a bug by BSI.

      Therefore, I think it would be worthwhile for a Note specific to this WA 033/043 overlap error to be issued with clear, precise instructions on what to do here, since it affects every Washington customer. And, in the short term, what should these tax types look like before we sync the latest TUBs? (For reference, my starting point here is on TUB 066, and I'm trying to apply/sync TUBs 067-073).

      Cheers,
      Matt

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Hi Matt,

      I would delete the last entry with the dates:
      01.01.2011 and 12.31.9999 for both entries WA tax type 33 and tax type 43.

      After this the Sync tool will be able to update the table accordingly.

      Could you try it and let me know?

      Cheers,
      Graziela

      Author's profile photo Euna Lee
      Euna Lee

      it did work for me.

       

      Regards,

      Euna

       

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      Thank you, Euna! I will create a KBA for this specific scenario.

      Kind regards,
      Graziela

      Author's profile photo Matt Fraser
      Matt Fraser

      Thank you Graziela, that worked! I believe it looks correct now:

      Correct%20T5UTX%20WA%20033/043

      Correct T5UTX WA 033/043

      Author's profile photo Graziela Dondoni
      Graziela Dondoni
      Blog Post Author

      I have updated KBA 2550829.

      Kind regards,
      Graziela

      Author's profile photo Theresa Westlund
      Theresa Westlund

      Has anyone else run into an ADS error in the tax reporter log manager?  Any ideas for correction are appreciated.  I checked with Basis team and all tests are working correctly.   thank you.

      Type

      @5C\QError@
      Message Text ADS: com.adobe.ProcessingException: com.adobe.Proc essingException: org.omg.CORB
      id: SUN minor code: 2 completed: No(200,101).

      Author's profile photo Matt Fraser
      Matt Fraser

      Theresa,

      We did not encounter this, but one or two other customers reported the same or a similar ADS error earlier in this thread. Based upon their comments, the solution was simple: restart the ADS.

      Cheers,
      Matt

      Author's profile photo Theresa Westlund
      Theresa Westlund

      Hi Matt; that worked!  thank you.

      Theresa

      Author's profile photo Carlos Accorsi
      Carlos Accorsi

      Hello Community,

      This week BSI has released Regulatory Bulletin 73, which reinstated Tax Types 113 and 114 for the Washington Cares Fund.
      Upon the installation of this Regulatory Bulletin on your system and the inclusion of these Tax Types on the Tax Model, the taxes should be calculated with no issue.

      SAP Note 3136513 (BSI: WA cares fund tax updated for tax types 113 and 114) has also been updated with this information.

      Sincerely thanks,
      Carlos