time constrains

suredarreddy_pulimamidi — Mon, 27 Aug 2007 12:44:29 GMT

can anybody give what is time constrain and what are the different types of time constrains used in ABAP-HR?

Re: time constrains

Former Member — Mon, 27 Aug 2007 12:48:26 GMT

hi,

In master data, the time constraint is a definite feature of the infotype or subtype. Due to the time constraint of infotypes, several special features must be taken into account when processing time data. Views of time data are generally not practical.

In time infotypes, data is determined on the basis of the validity period.

When you enter an absence record, the number of days of absence is calculated on the

basis of the absence period.

In a view, new partial periods are created without any changes being made to infotype

data. This would lead to incorrect results in time infotypes, since this data depends on the

validity period.

For example, if, a leave record extends from the middle of January to the middle of February and 20 days of leave are calculated for this period, then a view for the month of February would result in a leave record which extends from the beginning to the middle

of February. The number of days of leave would not have changed and the information would be incorrect.

In master data, the time constraint is a definite feature of the infotype or subtype. There are no time dependencies between infotypes and subtypes.

Time data is basically different. Let us assume that an employee becomes sick during vacation. The leave record is then delimited on the first day of the sickness, and the sickness record follows. Likewise, the system prohibits the entry of a leave record that coincides with a sickness record. The same also applies to overtime during a sickness.

The time dependency of time infotype records is not limited only to dependencies between records of one and the same infotype, but covers all infotypes and subtypes. The time constraint of time infotypes is not an attribute but is defined by the relationships between infotypes.

Moreover, certain time infotype records have specific clock-in/clock out times. Several

records may therefore exist for one infotype on a particular day.

Since views require explicit data and this prerequisite is not fulfilled by time infotypes,

you should not use joins and projections for time data.

Time infotype tables are processed with the LOOP statement since the PROVIDE statement limits, and thus changes, the infotype begin and end dates to the data selection

period.

check these threads....

hope this helps!!!

<b>Reward if helpful.</b>

Re: time constrains

Former Member — Mon, 27 Aug 2007 14:14:11 GMT

Hi,

The following time constraint indicators are permissible:

-1 No overlapping and no gaps.

Eg : Infotype 0000 - Actions

Real world example is : Now if manager wants to see status of employee from 1st jan to let say 30th march. (Status would be "Active" and "OnLeave/Inactive" ). So in a table, for that employee there should be information from day one till end of the day without any gap or without any repetitive info for single day.

-2 No overlapping but time gaps are permitted.

Eg : Infotype 0021 - Family Details

If suppose employee joined XYZ organization on 1st jan and left that org on 31st December. And again later on after 4 years he joined the same org ie XYZ then inthis case gap is allowed but there should not be overlap.

-3 Overlapping and and time gaps are permitted.

Eg : Infotype 0019 Monitoring of Task

One employee can have more than one address or telephone numbers.

topic time constrains in Application Development and Automation Discussions

time constrains

Re: time constrains

Re: time constrains