topic Re: Is date important in validating pernr table fields? in Application Development and Automation Discussions

Is date important in validating pernr table fields?

siongchao_ng — Wed, 31 Mar 2010 04:29:21 GMT

Hi all,

I am validating set of pernrs selected based on payroll area. I am checking whether this set of pernrs' KOSTL field in infotype 0001 is empty. If it is empty, program list out the affected pernrs with error message.

Problem:

I am checking for payroll area '09' which in turns give me a set 6 employees. The program list all 6 employees with error message "KOSTL in infotype 0001 is invalid". A quick check with transaction PA30 indicates all 6 employees's KOSTL field is actually filled with data at all. What could be the problem here?

The current code is as followed:

Note: payroll period is derived from payroll area entered by user.

Select pernr into table t_pernr from PA0001 where begda <=a_payperiod-begda

and endda >=a_payperiod-endda.

Loop at t_pernr into w_penr.

Select KOSTL into table abc from PA0001 where KOSTL in t_value_check.

Endloop.

t_value_check is as follow:

sign | opt | low | high

I | eq | |

Edited by: Siong Chao on Mar 31, 2010 6:29 AM

Re: Is date important in validating pernr table fields?

OttoGold — Thu, 01 Apr 2010 07:59:30 GMT

How comes you have 112 posts and 0 points? Maybe that means you have never helped a living soul and that is why people don´t want to help you? You will also find troublesome to get some help around here in future. Otto

Re: Is date important in validating pernr table fields?

Former Member — Fri, 02 Apr 2010 03:10:24 GMT

comments deleted.

Re: Is date important in validating pernr table fields?

siongchao_ng — Thu, 08 Apr 2010 07:50:24 GMT

Solved. It is date related problem.