Hello community,

This is our U.S. Affordable Care Act (ACA) Information Reporting 2016 blog post.

If you have questions about 2016 ACA reporting, you can post it here.

This blog will be updated with tips and SAP Notes related to this subject.

—–
More information about the planned legal change please read the SAP note below:

2359091 – Announcement Note for Affordable Care Act Information Reporting 2016
—–

Kind regards,

Roger Oliveira

To report this post you need to login first.

328 Comments

You must be Logged on to comment or reply to a post.

  1. Mathias Raffel

    Dear all,

    we are doing our correction run (only 3 EEs left) and in trxn HRBENUS_ACA_EVAL which we run after the 1094-C was printed, the node for EE Status info does not show any data.
    Has anybody else seen this issue?

    Thanks and best regards,

    Mathias Raffel

    P.S. I will open and incident.

    (0) 
  2. Mathias Raffel

    Dear all,

    do any of you see issues with the correction process? We corrected 3 SSNs and ran the data collection programs.
    Now the 1094-C for the new Run ID is checked as ‘corrected’ and there is data past line 18. Both should not be the case since we only corrected 1095-C data. And in the XML trxn we have hence two sets of two XML files, one set for 1094-C correction and the other for 1095-C corrections. We should only see one set.

    Thanks and best regards,

    Mathias

     

    (0) 
    1. Mathias Raffel

      I think it is related to table HRBENUS_D_REPORT having ‘Res. Type’ a ‘C’ again like last year. If I change it to ‘O’ manually, the 1094-C is issued correctly (the CORRECTED flag is not checked and only data through line 18 shows). SAP had a patch last year but it looks like the issue came back.

      Thanks and best regards,

      Mathias

      (0) 
        1. Mathias Raffel

          Good morning Margaret,

          thank you for your reply! I already opened an incident last week and now we have two open incidents for our correction process:

          • 134249 / 2017 ACA – Form 1094-C is incorrect for our correction run
          • 126294 / 2017 ACA – trxn HRBENUS_ACA_EVAL – no EE status information for correction run

          Thanks and best regards,

          Mathias Raffel

          (1) 
  3. Roger Oliveira Post author

     

    Hello Community,

    SAP Note 2440229 – ACA: Error in Force Replacement

    This note deliveres some corrections to force replacement scenarios as for example the error message ‘Database entry not found with table key APPL: ACA RUNID: 00000000000000000000′.

    For those who already have one of the pilot releases of this note, please deimplement it from the system and do the implementation process again as it contains a new version available.

    Regards,

    Roger Oliveira

    (0) 
    1. Debbie Satterfield

       

      We have implemented this note in our development system but the error message ‘Database entry not found with table key APPL: ACA RUNID: 00000000000000000000′. still persists.  Any additional thoughts?

      Thanks.

      Debbie Satterfield

      (0) 
      1. Roger Oliveira Post author

         

        Hi Debbie,

        Did you apply the last version of the note?

        Did you face any error during the note implementation? Please check the note log at SNOTE transaction and confirm that all the correction instructions were applied and the objects are active.

        Are you performing a force replacement scenario or a correction one?

        Regards,

        Roger Oliveira

         

        (0) 
        1. Debbie Satterfield

           

          Hi Roger.

          Thanks for the response.

          We are creating a correction file.    The note was applied shortly before I sent the message so I assume it would be the latest version.

          All instructions were applied and all objects are active but we still have the issue.

          Regards,

          Debbie Satterfield

          (0) 
        2. Debbie Satterfield

           

          Hi Roger,  I know this is an incredibly busy time for everyone but we are quickly approaching our 60 day deadline with IRS to have a corrected file submitted.  We first filed on Feb 21st so we only have a few days left.  We have opened incident 147138 / 2017 ACA: Corrections File cannot be created and implemented the notes as recommended with no success.  Could you possibly take a look for us?

           

          Thanks and best regards,

          Debbie S.

          (0) 
  4. Nancy Brister

    Our XML file was rejected due to a schema validation error, AIRSH100. The following messages appear.

     

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘SepSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘OctSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘NovSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘DecSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘DecSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘MaySafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JanSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘MaySafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JanSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JanSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘DecSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘SepSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JanSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘FebSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘SepSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘OctSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘NovSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘DecSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘SepSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘OctSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘NovSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘DecSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JanSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘FebSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘MarSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AprSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘MaySafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JunSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘JulSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘AugSafeHarborCd’, Line Number in file = 1;

    • /Form109495CTransmittalUpstream/Form1094CUpstreamDetail/Form1095CUpstreamDetail/EmployeeOfferAndCoverageGrp/MonthlySafeHarborGrp

    – element ‘SepSafeHarborCd’, Line Number in file = 1;

    I tired following the instructions in note 2393903 – ACA How to validate the XML structure but I don’t get the option to validate the files. Has anyone else encountered this error?

     

    (0) 
    1. Margaret West

      Hello Nancy,

      One possible reason could be improper use of QlfyOfferMethodTrnstReliefInd. Could you please your data file if the node “QlfyOfferMethodTrnstReliefInd” is present? Then check your configuration for line 16 of Form 1095-C (ex. Code 2I is reserved for reporting year 2016).

      Regards,

      Margaret

      (0) 
    1. VINAYA KANDADI

      Hello Kiran ,

      We are facing the same issue .

      Were you able to get a resolution to this issue .

      If so could you please let us know.

      Thank you ,

      Vinny

       

      (0) 
  5. Deborah Moses

    We have submitted several xml files to the IRS, all of which have been rejected due to multiple reasons.  The first files were rejected because of schema validation errors.  We applied 2 SAP notes (2410470 and 2419025), validated our schema following IRS instructions, and submitted Replacement files to the IRS.  The Replacement files were also rejected due to a Manifest-025 error.  I haven’t had any luck finding much documentation on this error, so I contacted the AIR Mailbox, and the instructions that were sent back are extremely technical.  Has anyone else encountered this particular error – Manifest ‘ChecksumAugmentationNum’ must match the IRS-calculated ‘ChecksumAugmentationNum’ value of the transmission.  If so, were you able to resolve it to successfully submit files?  Thanks all.

    (0) 
    1. Al Ling

      Hi Deborah,

      We got a Manifest-025 error when we corrected one date directly in the XML as opposed to regenerating the entire file.  All you have to do is generate a new MD5 checksum figure and put it into the corresponding manifest XML for your file.

      Best,

      Al Ling

      (0) 
    2. Roger Oliveira Post author

      Hi Debora,

      The purpose of the field ‘ChecksumAugmentationNum’ is to avoid to process incorrect information due a change in the content of the XML file.

      This value is generated by the SAP system during the report execution and it considers all the content from the file.

      For this reason, if you manually perform a change at the content it will be reject for security reasons.

      This is an option that helps to prevent attacks called ‘man in the middle’.

      So, SAP does not recommend to perform changes at the XML file manually as it create a breach and the possibility of the file being reject.

      Regards,
      Roger Oliveira

      (0) 
      1. Angela Payne

        Hi all,

        I had to change my byte size and check sum because the B forms has “-” in the phone number and I didn’t want to apply all the notes to catch up.  I was able to calculate the check sum using this little calculator.

        http://onlinemd5.com/

        I replaced what was in the manifest file with the number it generated and it all worked great!  The IRS accepted the file.

        Thanks
        Angela

         

        (1) 
  6. Al Ling

    Hello everyone,

    We have submitted our XML files to the IRS and currently have a status of “accepted with errors.” This morning, I went through the process of correcting an employee on our QA system and producing “corrected” 1095C forms and files.  Much to my surprise, when I executed HRBENUS_ACA_XML, it produced two sets of XML files, and they appear to be (at a quick glance) identical.

    I have asked our basis team to apply SAP Note 2419025 to our QA system and am going to re-run the process, but I was curious if any of you who are further along in your correction process have experienced this.

    Best regards,

    Al Ling

    (0) 
    1. Margaret West

      Hello Al,

      Two sets of XML files could be due to employee classification changes and/or changes to the information on Form 1094-C during your Correction process. If no such corrections/changes were made, please open an incident under PA-PA-US-BN and we will look into it.

      Regards,

      Margaret

      (0) 
      1. Al Ling

        Margaret,

        Thank you.  There should not have been any 1094C changes, unless changing the ending date on infotype 0171 would trigger a 1094C change.  I am going to re-test again this afternoon and will update the thread shortly.

        Thanks,

        Al

        (1) 
    2. Mathias Raffel

      Al and Margaret,

      that looks exactly like one of the problems I am facing with the correction process. The 1094-C is marked as ‘corrected’ even only 1095-Cs got corrected. Since the XML trxn sees the two corrections, it creates two sets of XML files:

      • 134249 / 2017 ACA – Form 1094-C is incorrect for our correction run

      Al, can you check if you see the other issue I am facing as well? In trxn HRBENUS_ACA_EVAL do you see any data in the node ‘Employee Status Information’ for your correction run? For us that data is missing:

      • 126294 / 2017 ACA – trxn HRBENUS_ACA_EVAL – no EE status information for correction run

      Thanks and best regards,

      Mathias Raffel

      (0) 
      1. Debbie Satterfield

         

        Hi Mathias,

         

        Have you found a resolution for the no EE status information for correction run?  We are faced with this same issue and are unable to send our correction file?  We get the error Database entry not found with table key APPL: ACA RUNID: 00000000000000000000 when we try to create the XML corrections file.  Thanks for any advice or input you can provide.

        Regards,

        Debbie Satterfield

         

        (0) 
        1. Mathias Raffel

          Hi Debbie,

          for our issue with the missing EE status information SAP note 2444446 fixed it. But your error looks different compared to ours. Not sure if the note will fix that.

          Best,

          Mathias Raffel

          (0) 
      2. Al Ling

        Hi Mathias,

        I believe my 1094C was also marked as “corrected” as well.  I am about to re-test our correction scenario now that we have updated/corrected some PERNRs in our test/QA system.  I will update you with the results and whether or not I see data in the node.

        Best regards,

        Al

        (0) 
      3. Al Ling

        Hi Mathias,

        I believe you are correct.  Our 1094C is also being marked as ‘corrected’ as part of this process, even though I am only adjusting data for select employees.  So, I think you are correct in submitting an incident for this.  I wonder if I need to do the same so it would get more “coverage”?

        I am going to try one additional test on a ‘clean’ test system (one without a prior production run so I can see if these multiple correction XMLs are created there).

        In HRBENUS_ACA_EVAL, however, I AM seeing Employee Status Information for my correction run.

        Thanks and best regards,

        Al

        (0) 
        1. Mathias Raffel

          Hi Al,

          SAP provided pilot note ‘2444447 – ACA: Incorrect counts in Form 1094-C for Correction’ and I just applied and tested it. Unfortunately the 1094-C is still marked as ‘corrected’ and too much information is provided on the form past line 18. And hence two sets of XML files are generated.

          We had the similar problem last year and it might still be based on the HRBENUS_D_REPORT table entry for the correction run ID where the ‘result type’ is C. When I switch it to ‘O’ it works correctly. And I see ‘O’ in the correction runs from last year in this table.

          Thanks and best regards,

          Mathias Raffel

          (0) 
          1. Al Ling

            Mathias,

             

            Thanks.  I am getting it put on now.  Once you applied it, did it correct/resolve your two sets of XML files being created for a correction run?

             

            Best,

            Al

            (0) 
            1. Mathias Raffel

              Hi Al,

              yes, that last note fixed the 1094-C and XML problem we encountered.

              Now we are just waiting for the IRS letter for a password reset….

              Best,

              Mathias

              (0) 
              1. Al Ling

                Hi Mathias,

                Glad it resolved your issue.  We are still getting two XML files when we attempt to process a correction run after applying this latest note.  I may resort to submitting an incident with SAP and see what they say.

                Thankfully, my HR team is still working through correcting the master data on those employees that kicked out so we aren’t in total crisis mode to get these corrections submitted, but I am most certainly ready to get this done and over with!

                Best,

                Al

                (0) 
                  1. Al Ling

                    Hi Joelle,

                     

                    No, I have not made any further progress.  In fact, our HR team is still gathering all of the required/missing data, so I have hit the “pause” button until they can give me a subset to test with.  We recently refreshed our QA system from our PRD system so I have clean data to test with.

                    I have not checked for SAP Notes for a while so I wonder if there are now some additional ones to apply.

                    Thanks,

                    Al

                    (0) 
  7. Nancy Schulz

    Margaret/Roger:

    We have applied all known ACA Update Notes.   We just attempted to submit a file to IRS and it rejected due to a space before the ‘count’ (see the space before the number):

    Form1095AttachedCnt> 6525</Form1095CAttachedCnt

    This problem did not exist prior to us applying all the recent ACA Note Updates.   We looked at our old files (prior Notes) and the space was not there.

    We have opened a VERY HIGH ticket with SAP (144368/2017) as we are rapidly running out of time on getting at least some type of successful attempt of a file transmission.   Our previous attempts were all due to schema formatting errors, which were resolved by the ‘Notes’, but now we have a new problem and the file is REJECTing

    Can you please take a look.

     

     

    (0) 
      1. Nancy Schulz

         

        Margaret/Roger:   Would you please look at incident 144368.  We got this schema error (from IRS) after implementing all Notes (that were available on March 23).

        SAP Support was getting a memory error when trying to re-create the problem and this has been going on since March 23.   We now believe we corrected the memory error so they should be able to re-create the problem in our system

        Can you please take a look.    There is a space before the number in the tag:   Form1095AttachedCnt> 123</Form1095CAttachedCnt

        This space happens in this tag for any RunIDs that we generate XML on and it not unique to any specific RunID.

        (0) 
  8. Margaret West

    Hello Community,

    Version 1.7 of the SAP ACA User Guide for 2016 is now available in SAP Note 2359091 – Announcement Note for Affordable Care Act Information Reporting 2016.

    Regards,
    Margaret

     

    (0) 
  9. Deborah Duron

     

    We have submitted two xml files for single ALE to the IRS which were rejected due to Schema validation error with employee data. We have corrected the employee data in SAP and have followed the steps in the user guide for Generation of Replacement Forms and Files. However, when generating the XML file for the replacement, we are missing the ALE member information from Parts II and III of 1094 C in the replacement file.

    Upon Executing HRBENUS_ACA_PERSON for rejected receipt ID, a new run id was generated and populated HRBENUS_D_PERSON table for original record with new run id and replacement record types. Also, table HRBENUS_D_ADDATA was populated with new Run ID for all records in original run.  Upon executing the HRBENUS_ACA_ALE report, some of the ALE fields were created for the new run.  Missing following ALE fields for replacement run ID: NAP_COUNT_**, NEE_COUNT_**, NEN_COUNT_**, PTN_COUNT_**, EMP_COUNT_**, EMP_TRAN_CNT_**, FTE_COUNT_**, and FTE_TRAN_CNT_**. I believe the missing fields for the new run ID is the cause for not seeing the 1094 C data in the replacement file. I have not submitted the replacement file because it is missing the 1094 C data. Has anyone else encountered this particular issue?  If so, how were you able to resolve it?

    (0) 
    1. Margaret West

      Hello Deborah,

      Please see section 3.8 of version 1.7 of the SAP ACA User Guide for 2016 in SAP Note 2359091 – Announcement Note for Affordable Care Act Information Reporting 2016. This section with provide you with instructions on the Replacement and correcting employee master data process.

      Regards,

      Margaret

      (0) 
      1. Deborah Duron

         

        I followed the instructions for the replacement process, section 3.8 of version 1.7.  My issue is that the replacement XML submission does not have any of the employee counts that represent 1094 C Part III.  The counts were in the original XML file but are not in the replacement.  How do I get the Full Time employee and Total Employee counts in the replacement file?

        (0) 
  10. Austin Chapman

    We have one employee that is being rejected by the IRS and are not sure how to resolve this issue.  Employee was a contractor 1/1/2016 – 2/8/2016 and therefore excluded based on our configuration.  Employee was hired 2/9/2016 and is reflected as FTE March – December.  The XML does not generate an  AnnualOfferOfCoverageCd entry since they were not employed full time.  In addition, it does not generate MontlhyOfferofCoverageGrp entries for January or February.

    Has anyone had this issue?  If so, were you able to resolve it?

     

    (0) 
    1. Rose Nguyen

       

      We had a similar scenario with 2 interns who became full-time employees (FTE) mid-year.  To get the MonthlyOfferCoverageGrp values when they were not FTE to resolve the AIR error, we updated feature UBAIC for the specific PERNR and overrode feature UBAAS for Box 16.   Please make sure their master data is accurate.  Then ran the Correction process to generate form 1095C for the employees and xml files for the IRS.   You may see the 2 sets of xml files that Mathias and Al encountered.   We loaded the xml set for the 1095C correction to the AIR system & was accepted.

      (0) 
  11. Siva Shanmugam

    Dear All,

     

    I am getting error:

    There is an error in ACA standard SAP Class

    cl_hrpayus_employee_factory=>create

    This class doesn’t create  correct instance of the following interface for certain retired employees with many assignments.

    go_employee                    TYPE REF TO if_hrpayus_employee.

    We get an error with Info Type 000 stating – Infotype 000 cannot be found. Infotype 000 exists on that particular record.

     

    (0) 
  12. SAIRAM SAI

    Hi Team,

    I am facing an issue with AATS communication testing issue with one of the Tax company.

    This is the new tax company for the year 2016. We successfully submitted remaining 7 companies XML files to IRS which we did for 2015.

    I have some doubts. Could you please clarify.

    1. In which system (Quality  or Production) we need to do AATS test scenario.
    2. Are there any mandatory SAP notes to be applied. (Already we submitted remaining 7 tax companies XML files to IRS)
    3. Could you please send the link for User manual for AATS communication testing scenario.
    4. Shall we need to prepare dummy benefit plan and employee for this testing.

    Please advice us at the earliest.

    Regards,

    Sairam.

     

     

    (0) 
    1. Margaret West

       

      Hello Sairam,

      1. Quality system since you will be creating non-production test data
      2. For list of mandatory SAP Notes, please see SAP Note 2359091 – Announcement Note for Affordable Care Act Information Reporting 2016
      3. For more information on AATS 2016 testing and the cookbooks, please see SAP Note 2385115 – ACA: 2016 AATS Scenarios
      4. You will need to follow the IRS AATS Narratives, which will be non-production test data. For helpful tips on creating test employees and benefit plans, please see:
        1. ASUG Webcast: Affordable Healthcare Act (ACA) November 3, 2016: slide 6
        2. ASUG Webcast: Affordable Healthcare Act (ACA) May,12: Note: Although this webcast was for reporting year 2015, the steps on slides 7-13 are similar for reporting year 2016 that you might find helpful.

      Regards,

      Margaret

      (0) 
  13. SAIRAM SAI

    Hi Margaret,

    Thanks for the reply.

    At present I am facing the below issue.

    The Issue is as below.

    [TPE1106] The manifest file does not match our current schema .In particular, our system identified a potential issue with the following elements. irs:EIN and documentSystemFileNm.

    I have used the narraitves 7 for testing and EIN as per that 0000000710.

    Could you please advice me to resolve the issue at the earliest.

    Regards,

    Sairam.

     

     

    (0) 
    1. Margaret West

      Hello Sairam,

      Please recheck your implementation of SAP Notes (make sure that all UDO reports were executed correctly (including the third step, when possible)), configuration (in particular the separate 2015 and 2016 date range in V_T77PAYUS_TXCMP), and implementation of the HR Attributes.

      Regards,

      Margaret

      (0) 
  14. SAIRAM SAI

    Hi Margeret,

    With your advice we were able to submit AATS communication file to IRS.

    But it was rejected.

    The errors are showing as below.

    Form 1094C ‘Business name’ and ‘Employer EIN’ in Employer InformationGrp must match with IRS data base.

    Form109495C Transmittal upstream / form 1094c upstream details/ Employer Information group/Employer EIN.

    I have followed the Narraitives 7 and named tax company as TEST  carrtestseven.

    Please advice us to resolve the issue.

    Regards,

    Sairam.

    (0) 
  15. SAIRAM SAI

    Hi Margaret,

    Now the error related to Form 1094C ‘Business name’ and ‘Employer EIN’ in Employer InformationGrp must match with IRS data base is rectified.

     

    At present while downloading XML files are being saved with TEST prefix, which we were unable to upload to IRS site. IRS system is showing the rejection.

    The Error showing as [TPE1106] DocumentSystemFileNm

    Here I am attaching the screens related to the same.

    The DocumentSystemFileNm in manifest file  including Prefix “TEST”.

    I have maintained the Tax company as TEST  with CARRTESTEVEN s details; Mapped the EIN number 000000710 to tax company TEST in EIN to BSI tax company node.

    Also mapped Tax company to  to Tax authorities, Tax types, Employer ID number.

    Please advice us at the earliest.

    Regards,

    Vikram.

    (0) 
    1. Margaret West

      Hello Sairam,

      Please ensure that you have the appropriate entries as described in the Cookbook AATS Submission 7 document attached to SAP Note 2385115 – ACA: 2016 AATS Scenarios. For example, in the last section Communication Test, step 6 describes the appropriate entries for RPCBENUS_ACA_XML. In particular, please recheck step 6.c. Deselect Test mode.

      Regards,

      Margaret

      (0) 
  16. SAIRAM SAI
    Hi Margaret,
    Already we deselected Test mode while executing HRBENUS_ACA_XML
    As per Narratives 7, we need to fill AATS TEST SCENARIO as 7; But I did not find field AATS TEST SCENARIO.
    Some we need to restrict Prefix TEST in the generated Manifest XML file.
    Please advice.
    Regards,
    Sairam.

     

    (0) 
    1. Margaret West

      Hello Sairam,

      When you execute transaction HRBENUS_ACA_XML, AATS TEST SCENARIO is the last field on the parameter screen of this report.

      Regards,

      Margaret

      (0) 
  17. SAIRAM SAI

    Hi Margaret,

    Thanks For your suggestion. By that, Prefix TEST in the generated Manifest XML file issue was solved.

    But We are getting another error.

    <?xml version=”1.0″ encoding=”UTF-8″ standalone=”true”?>

    -<ns3:FormBCTransmitterSubmissionDtl xmlns:ns3=”urn:us:gov:treasury:irs:msg:form1094-1095BCtransmittermessage” xmlns:ns2=”urn:us:gov:treasury:irs:common” xmlns=”urn:us:gov:treasury:irs:ext:aca:air:ty16″>
    -<ACATransmitterSubmissionDetail>
    -<TransmitterErrorDetailGrp>
    -<ns2:ErrorMessageDetail>

    <ns2:ErrorMessageCd>HEADER-003</ns2:ErrorMessageCd>

    <ns2:ErrorMessageTxt>The Header ‘UniqueTransmissionId’ must not be a duplicate of the ‘UniqueTransmissionId’ from another transmission</ns2:ErrorMessageTxt>

    </ns2:ErrorMessageDetail>

    </TransmitterErrorDetailGrp>

    </ACATransmitterSubmissionDetail>

    </ns3:FormBCTransmitterSubmissionDtl>

    Could you please advice us to resolve the error.

    Regards,

    Vikram.

    (0) 
    1. Margaret West

      Hello Sairam,

      It could be that you submitted the same file to the IRS again. You can call the IRS to determine the reason for this error in their system.

      Regards,

      Margaret

      (0) 
  18. Margaret West

    Hello Community,

    Version 1.8 of the SAP ACA User Guide for 2016 is now available in SAP Note 2359091 – Announcement Note for Affordable Care Act Information Reporting 2016.

    Regards,
    Margaret

     

    (0) 
  19. Mathias Raffel

    Dear all!

    Just an FYI… today we filed our corrections for the issues detected by the IRS based on our original filing.

    We received the status ‘Accepted’ and are closing the project now.

    Thank y’all for the ongoing support!

    Best regards,

    Mathias Raffel

     

    (2) 
    1. Debbie Bouhenguel

      Mathias,

      WOW, hooray for you and your colleagues!! I wanted to express my appreciation for the insight, advice and clarity that you have provided over the past 18 months via this blog. I have relied on the knowledge you have shared more times than I can say. I look forward to working with you on future projects, though hopefully they will not be as convoluted, complex or confounding as the ACA :-).

      Debbie B

       

      (2) 
      1. Mathias Raffel

        Debbie!

        Thank you for the kind words! I believe it was a great group effort with all of us helping each other and learning from each other! Your contributions were always insightful as well!

        Definitely let’s stay in touch for the next challenges. The new EEO-1 reporting change is on the list but still too early to say how it will play out.

        Best regards,

        Mathias

         

        (1) 

Leave a Reply