cancel
Showing results for 
Search instead for 
Did you mean: 

North Carolina wage detail requires N record.

Former Member
0 Kudos

Hello,

The requirement is NC unemployment file now requires N record. The MMREF format ( HR_F_MMREF_UI_NC) does not work because the record length is 512 characters which is not acceptable . Oss note 1479435 has provided a new ESC format ( HR_F_ESC_UI_NC) which again has a character length of 512 charaters. So the only option left is to fix the ICESA format (HR_F_UNEMP_NC). Need some help, regarding how to add the N record to this ICESA format.

Appreciate your help.

Thanks

Kris

Accepted Solutions (1)

Accepted Solutions (1)

former_member182083
Active Contributor
0 Kudos

Hello,

It should be 80, kindly change it to 80

Tax form HR_F_ESC_UI_NC NC SUI Tape/Diskette (ESC)

-


Output event 0000 Header Information

Location on tape 007 Rec length *** if more than 3

Take from field Or directly 512 <-- Change this to 80, this will solve the problem.

This needs to be fixed by SAP development, they will fix it.

With Regards,

S.Karthik

Former Member
0 Kudos

Karthik,

Yes they fixed it, they have released a new ESC format for Q2, 2010.

Appreciate your response.

Thanks.

Edited by: Krish_murt on Jul 23, 2010 9:38 PM

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Kris,

Can you please re-check the requirements, here is what I have found regarding the MMREF format for NC:

MMREF Diskette/CD Specifications

This record layout uses the Code RE - Employer Record and the Code RS - Supplemental Record as prescribed for state wage reporting by the Social Security Administration. Another record - Code N u2013 can be used for reporting the NCUI 101 record as shown on page 14. (Note: The N record which is now required should be the first record in the file.)

u2022

All data records must be a fixed length of 512 characters followed by carriage return and line feed characters.

u2022

If you have alternative data, please open an OSS ticket with that information attached.

Kind regards.

Former Member
0 Kudos

Hi Giselle,

Thankyou for replying back, the changes they have introduced for Q2,2010 fixed the issue we had.

Thanks

Kris