IT9 error in Portal

[Former Member]

Dera gurus

While editing the bank details in ESS by employee, system showing an error message showing that

Data record <personnel number> 9999123120050701000 has grouping value "" instead of "40"

What is this error and how to solve it

Thanks in advance

Kumar

[siddharthrajora]

also to avoid this error reoccuring again

Read the note 783499

CCURE PC_UI in table T77S0.

In the T77S0 table, the CCURE PC_UI indicator is not set.

Solution

You have to set this indicator. After you set the indicator, you have to

execute the following reports:

o RPUFACECPRFN (required), adjustment of T582G from T582A-CPRFN

o RPUFACEVIEKN (required), adjustment of P0003-VIEKN in accordance

with the IVWID feature

o RPUFIXDS (not required but recommended), correction of possible

inconsistencies in the PSHRD-GPRVL field.

Note that the IVWID feature must be maintained correctly so that the

RPUFACEVIEKN report creates correct occupancies.

Usually this indicator cannot be maintained. If you implement the

attached program corrections, you will now be able to maintain the

indicator.

implement Note 845592.

When the infotype 0009 is modified, the system is regrouping data

for the infotypes which are checked releavnt according to the table

T582G. Retroactivity is checked via V_T582A

Please note that

Entries in the payroll past are not allowed in the infotype 0009: the

flag V_T582A-EPAST is set to 'E'. Therefore the error message is

triggered. This is the standard customizing. This customizing makes

sense as there is no need to change the infotype 0009 once the payroll

had run. The bank transfer already occured and the changing in the past

won't 'call back' the bank transfer. Moreover the payroll function is

reading the infotype 0009 to the actual date (SY-DATUM). Therefore the

infotype 0009 can not be changed in the payroll past.

[Lukas_Weigelt]

Hi,

Run the Report RPUFIXDS for respective pernr. This should solve the problem.

EDIT: Jesus, you are fast Prashant 😛

regards, Lukas

Edited by: Lukas Weigelt on Jun 3, 2011 9:30 AM

[former_member182598]

Hi Kumar,

You have to run the RPUFIXDS report for the personnel number (the pernr assigned to the user who is getting this error) in the R/3 system and it should solve the issue.

Thanks

Prashant