Time Constraint???

[#1]

Hi Gurus,

please explain what is a

time constraint - 1

time constraint - 2

and

time constraint - 3

Please explain with an example pleaseeeee.

Warm Regards,

Zulfikarlos

Edited by: Zulfikarlos on Sep 27, 2011 6:02 PM

[Former Member · Accepted solution]

Time Constraint

A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:

1: An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.

Infotype 0000 (actions), infotype 0001 (organizational assignment ) are few examples for TC 1

2: Only one record may be available at one time, but time gaps are permitted.

Infotype 0025 (appraisals) is an example for TC 2

3: Any number of records may be valid at one time, and time gaps are permitted.

Infotype 0022 (Education) is an example for TC 3

Other possible time constraint indicators are as follows:

A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.

View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.

Infotypes with time constraint A may not be deleted.

Infotype 0003(Payroll status) is an example for TC A. There can be only one record for an employee

B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.

Infotypes with time constraint B may be deleted.

T: The time constraint varies depending on the subtype.

Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y Time Constraint Reaction.

Regards

Ravikumar

[former_member148407]

Hi,

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.

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.

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.

Time Constraint 3

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

Hope this helps.

Thanks

Ranjeeta

[Former Member]

Hey,

Thank you all for the valuable time you guys have put it to explain time constraint, thanks once again.

Warm Regards,

Zulfikarlos

[Former Member]

hi Zulfikarlos,

i suggest you to please search the forum before you post the question.

BTW please follow the link to find the answer

[;

Regards,

mohammed

[Former Member]

if we make more simple

1 - allows only one record, without any gap (every time one record should be there) - org assignment, one record should be there every time.

2 - allows only one record, but gap is allowed (a record can or can't exist, but allows only one) - like esi, only one esi is allowed, but there r employees without esi also

3 - allows more than one record, allows gap (one or more than one record can use, but not mandatory) - like loan, more than one loan is allowed

[Former Member]

Hello;

About time constraints...

1: An infotype record must be available at all times. This

record may have no time gaps. You may not delete the record last

stored on the database because all records of this infotype

would otherwise be deleted.

For example IT0000-IT0001-IT0008

For an employee who entered at 01.01.2011 allowed records are:

01.01.2011 - 31.01.2011 Sales Responsible

01.02.2011 - 31.03.2011 Sales Specialist

01.04.2011 - 31.12.9999 Senior Sales Specialist

Records which can not be excepted are:

01.01.2011 - 31.01.2011 Sales Responsible

01.01.2011 - 31.03.2011 Sales Specialist (This is not allowed. If Time constraint is 1 then first record 01.01.2011-31.01.2011 will be deleted)

01.03.2011 - 31.12.9999 Senior Sales Specialist (This is not allowed. If Time constraint is 1 then first record 01.01.2011-31.03.2011 will be delimited with 28.03.2011)

Also records with gaps are not permitted. For example...

01.01.2011 - 31.12.2012

01.04.2013 - 31.12.9999 This is not allowed for time constraint as there must be existing record for 01.01.2013-31.03.2013.

2: Only one record may be available at one time, but time gaps

are permitted.

For example employee's address can be an example. He may not have two address at the same time but if he is staying with someone else he may not have address.

Records acceptable are:

01.01.2011 - 31.12.2013

01.04.2014 - 31.12.9999

Here gap between 01.01.2014 and 31.03.2014 are allowed in time constraint 2.

But you may not enter a record between 01.11.2013-31.03.2013 as it overlaps with record 01.01.2011-31.12.2013. To save the record record 01.01.2011-31.12.2013 must be delimited with 30.10.2013

3: Any number of records may be valid at one time, and time gaps

are permitted.

You can enter as many record as you want. There can be gaps etc. For example employees can have more than one mail at the same time. He may not have mail for a while etc.

For example:

01.01.2010 - 30.04.2010 okanc bbbb.com

01.01.2011 - 31.12.9999 okanc cccc.com

01.01.2011 - 31.12.9999 okanc dddd.com

Edited by: Okan Caliskan on Sep 27, 2011 6:32 PM