Types of time constraints??

[Former Member]

Hi all,

What are the different types of time constaints??

Is it just 1[No gaps, no overlapping], 2 [Gaps are allowed but no overlapping]

and 3[both gaps and overlapping is allowed]

or are there any other types of time constraints other than 1,2 and 3

Warm regards,

Hari Kiran

[Former Member · Accepted solution]

Hi Hari Kiran,

Other time constraints:

A: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint A may not be deleted.

B: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint B may be deleted.

T: Time constraint varies depending on subtype.

Z : Refers to time management infotypes.Time constraint for these ITs depend on time constraint class in table V_T554S_I. Collision checks : V_T554Y

Regards,

Dilek

[Former Member · Accepted solution]

Thank you Dilek.

Regards,

Hari Kiran

[Former Member · Accepted solution]

you're welcome

Dilek

[Former Member]

Hi Experts,

I wish to know abt the time constraint classes, and time restraint classes of time recording data required for collision checks.

table V_T554Y -global time constraint reaction speaks about the time constraint classes, but I am not able to decipher the time constraint string.

pls guide

Kavita

[Former Member]

Hi Hari

Apart from 1, 2, 3 there are some other types of Time Constraints: A, B, T, Z.

The Infotypes with TC type A must exist, must have only one record in its lifetime, and these ITs cannot be deleted.

Example: IT0003 (Payroll Status)

The Infotypes with TC type B must have only one record in its lifetime.

Example: IT0031 (Reference Personnel numbers)

The Infotypes with TC type T will have subtypes, and the TC is based on the subtype.

Example: IT0009 (Bank Details)

The Time Mnagegement Infotypes will have TC type Z .

Example: IT2001 (Absences)

~Ranjith

[sikindar_a]

check V_T582A take help of f4 yes u can find other time constaints like T and all those things

for time constraints

Edited by: Sikindar on Oct 17, 2008 4:35 PM

[Former Member]

ok,

Thank you for the answer.

Regards,

Hari Kiran

[Former Member]

Hi Sikindar,

Can you 1 example for timeconstraints 1 ,2 ,3 and the purpose of time constraints.

Looking forward for your reply

[sikindar_a]

Here it is

Other time constraints:

A: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint A may not be deleted.

B: Only one record may ever exist for the infotype (from 01/01/1800 - to 31/12/9999). Infotypes with time constraint B may be deleted.

T: Time constraint varies depending on subtype.

Z : Refers to time management infotypes.Time constraint for these ITs depend on time constraint class in table V_T554S_I. Collision checks : V_T554Y

Apart from 1, 2, 3 there are some other types of Time Constraints: A, B, T, Z.

The Infotypes with TC type A must exist, must have only one record in its lifetime, and these ITs cannot be deleted.

Example: IT0003 (Payroll Status)

The Infotypes with TC type B must have only one record in its lifetime.

Example: IT0031 (Reference Personnel numbers)

The Infotypes with TC type T will have subtypes, and the TC is based on the subtype.

Example: IT0009 (Bank Details)

The Time Mnagegement Infotypes will have TC type Z .

Example: IT2001 (Absences)

rule that determines whether collisions in time data are allowed, and if so, specifies how the system reacts to such collisions.

Time contraints comprise the following:

Time constraint classes that determine which collisions in time data records are allowed

Time constraint table that contains the time-based collisions allowed in the time data records

Time constraint indicator that displays whether a new data record that collides with an existing time data record can be transferred to the system or whether the transfer is prohibited

When you update an infotype, old data is not lost but archived for historical evaluation. The system records a specific period of validity for each infotype, This enables the system to store more than one infotype record at the same time, even if their validity periods overlap. This means that the time relationships between infotype records must be defined. The concept of time constraints enables you to do this.

HR master data uses the following three time constraints:

Time Constraint 1

For the entire time that the employee works at the enterprise, exactly one valid infotype record must exist. The validity periods of the individual records must not overlap. If a new record is created, the system automatically uses the start date of the new record as the delimitation date of the old record. Gaps are only allowed between the employeeu2019s entry date and the start date of the first record.

Time constraint 1 must be used for all of the infotypes containing information that must be available at all times. This is particularly true of personal and organizational assignment data.

If a record is delimited because of time constraint 1, the system displays an appropriate message.

Time Constraint 2

No more than one valid record can exist at any one time. Records with constraint 2 must not overlap. Their existence is not obligatory. If a new record is created, the system automatically delimits the previous record, if one exists.

If a record is delimited because of time constraint 2, the system displays an appropriate message.

Time Constraint 3

Any number of valid records can exist at any one time. The individual records do not conflict with each other.

[Former Member]

Can you give the examples for time constraint 1 ,time constraint 2 ,time constraint 3

iam clear the concept, but when we use for which infotypes/subtypes we will apply these time constraint 1 .2&3