Note for FAPP column not allowed

[Former Member]

Dear All,

We had this error message " Note for FAPP column not allowed " during

execution of appraisal form. Upon debugging, we found out objective

setting entered has been truncated and updated into Final Appraisal

column where this column has been set to "No Note".

Please share with me if anybody has come across with this issue before.

Thanks and best regards,

Khairul

[Former Member]

Hi Khairul,

Is there any news or progress on this issue?

We have a similar problem (since february 2011) for 2 employees, not with column FAPP but with column FWGT. This column is available on Category level, but we never used it on Template-level.

Youmentioned you are working on cleaning the form manually. How did you do it, which steps did you do?

Kind regards,

Roald.

[Former Member]

Hi Roald,

During debugging the program, we found out, system was writing to column 2 instead of column 1. So we build simple program to download all affected employees into excel. Then, we manually update the form data for affected employees. We got lucky in our case, only 100 over employees affected. Below are steps for your reference :

1) Download all affected employees data

2) Delete the appraisal forms for affected employees

3) Re-create the appraisal form and update accordingly.

Hope this step able to help you to solve the issue.

Thanks,

Khairul

[Former Member]

Quote: "During debugging the program, we found out, system was writing to column 2 instead of column 1".

I assume this was a bug. Did you report it to SAP? Do you have some technical details about it?

Kind regards,

Roald.

[Former Member]

We have reported this to SAP. As per mention by Michael earlier, this is due to changing current active template that has caused this error.

SAP has advised not to changed current active template but copy and create new template instead.

[Former Member]

>

> Dear All,
> 
> We had this error message " Note for FAPP column not allowed " during
> execution of appraisal form. Upon debugging, we found out objective
> setting entered has been truncated and updated into Final Appraisal
> column where this column has been set to "No Note".
> 
> Please share with me if anybody has come across with this issue before.
> 
> Thanks and best regards,
> 
> Khairul

My only guess is that made you configuration changes to the template in one client and transported the changes to the test client, and used a previously existing document from the old config....if so, create a new appraisal document based on the newly released configured template.

at least that would explain what you are seeing....

[Former Member]

Hi Michael,

Thanks for the reply.

I would like to understand further on this as we are not able to replicate this error in our development system. Kindly, please share with us if there is any step we can use to replicate the error and work on permanent solution.

Currently, we are having more than 10000 employees in Asia Pacific affected by this error and we are working on cleaning appraisal form manually.

Thanks in advance for your cooperation.

Khairul

[Former Member]

>

> Hi Michael,
> 
> Thanks for the reply. 
> 
> I would like to understand further on this as we are not able to replicate this error in our development system. Kindly, please share with us if there is any step we can use to replicate the error and work on permanent solution.
> 
> Currently, we are having more than 10000 employees in Asia Pacific affected by this error and we are working on cleaning appraisal form manually.
> 
> Thanks in advance for your cooperation.
> 
> Khairul

i think to try to replicate you need to have two clients in dev, 1 for config, 1 for testing to replicate the problem

in ur config client take your production template, copy ithe template and make a test template.

transport this new test template into the test client.

generate employee documents for this test template, start processing the employee docs, but don't finish them..

go back to config client with your test template. unrelease the template, remove the notes field, remove a column, release and transport your template. transport now the updated test template to the test client. Test on the previous employees. if you can't replicate, create new employee documents based on that version and repeat the cycle with other changes...

this only a guess as to why you would get a weird error like that. anyways, since it's a production problem you should probably be opening a high ticket with sap.

the bad news if this is your problem, it will be very hard to correct in production...

[Former Member]

Thanks Michael,

I will work on this based on your recommendation. I'll report back once completed.

Thanks again.