Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Customized Infotype for 2001 - Issue

Former Member
0 Likes
382

Hi,

A New company ,Resolution(X) has joined our company(Y) and payroll was made active from 01.08.2007 for resolution employees

Resolution employees’ historical absence records need to be stored

It can not be stored in Info type 2001 as all employees in resolution(X) are hired in Y as of 01.08.2007 .

So no data prior to this date can be loaded in the system for resolution

I have created a customer info type to store the historic records of resolution employees absences .

This is just for the reference purpose and will not effect any payroll calculations prior or after 01.08.2007 .

Issue :

Though I have created a custom infotype .. if i try to save a record which has a date prior to the joining date in company Y, I get an error . This is a std sap error .

Is there any way to overlook this check of dates?Any config settings?

Hi,

A New company ,Resolution(X) has joined our company(Y) and payroll was made active from 01.08.2007 for resolution employees

Resolution employees’ historical absence records need to be stored

It can not be stored in Info type 2001 as all employees in resolution(X) are hired in Y as of 01.08.2007 .

So no data prior to this date can be loaded in the system for resolution

I have created a customer info type to store the historic records of resolution employees absences .

This is just for the reference purpose and will not effect any payroll calculations prior or after 01.08.2007 .

Issue :

Though I have created a custom infotype .. if i try to save a record which has a date prior to the joining date in company Y, I get an error . This is a std sap error .

Is there any way to overlook this check of dates?Any config settings?

1 REPLY 1
Read only

Former Member
0 Likes
354

There was a setting issue for the infotype ... Time constraint was set.

Hope this helps anyone who faces this issue again.