time constraint for 0294

[former_member202689]

Hi dears,

I want to use infty 0294 in my company. but i have a difficulty when I want to create second record for my IT.

I have created one record from 01.01.2012 to 31.12.9999

now i want to create second record from 01.05.2012 to 31.12.9999

I want the IT automaticly delimite old record.

I have done configurations in V_T582A:

Time constraint = 1

Create w/o strt = 1

Create w/o end = 1

But nit is no effect. Please help me.

regards,

Samir

[Former Member]

Hope you have to go for User exit for this functionality Samir.

[former_member202689]

Hi Praveen,

This IT is russian specific. I will try to contact via russian experts. If u find any solutions please write me.

regards,

[Former Member]

Hi samir,

Please change the settings as below and try

Time constraint = 1

select w/start 3

select w/end 5

select w/o date 1

create w/o str blank

create w/o end 1

[former_member202689]

thank you for ur respond

But I did ur configurations. No effect.There is NUMBER field in IT 0294. I think delimitation depends on this field.this field generates numbers automaticly. Have you any idea?

reagrds

[Former Member]

i don't think number field will have any impact on this.

please cross check if you have maintained Create w/o strt value as blank and also for Subtype field blank. try doing this.

if this doesn't work out then when ur creation the 2nd record in pa30 for 294 info type, instead of using create option please use copy option so that old record will be delimited.

[Former Member]

hi,

for multiple records time constraint need to be maintained as 03 instead of 01 for it 0294 in table V_T582A.

[Former Member]

hi,

did u explore the working conditions tab in it294.... i guess u can use tht instead of entering a new record in 294...

[Former Member]

Number generation is based on the Settings in SPRO for Personal Management-Personal Administration-Personal Data-Russia Specific Settings-------

It is not related to timeconstraint.

Understand the functionality of the infotype. I think its a book of record for Every employee, which should exist from the date of joining to 31.12.9999

If u try to create another Entry, system is taking it as another book of records for the employee from the given start date to 31.12.9999

If u can understand the functionality and the need of maintaining different records, it would be helpful to go further.

Even after changing the Timeconstraint to 1 from 3, the error shows about the interval rather than delimiting of the record. There would be someother logic to this functionality.

Correct me if I'm wrong.

[former_member202689]

Hi, rajendra

I have checked V_T582A table again. Subtype filed is not blank. there is INWRN.

Have any idea?

Do I have to empty this field?

regards

[former_member202689]

I think you are right Praveen

But I want it automatic delimitation.How can I do it?

regards

[Former Member]

Hello

Please keep TCC (Time constraint class) as 2 then when ever you create another record, old one will get delimited and new one will be created..

Regards,

Amit Goyal

[former_member202689]

Hi,

TCC 2 shows error message only. Not delimit old records.Have you other idea?

regards

[Former Member]

Hi Samir,

I couldnt able to identify why the system considers all the entries as new one and adding it instead of delimiting. Give me some time to come back on this.

In the mean while there is a option to make the customization as needed.

I had observed the following.

1. When we create a new record the system considers the start date(eg.,01.01.2010) and end date as (31.12.9999)

2. When you create a another record for the start date for 01.01.2011 the system considers it with the default end date as 31.12.9999

In this case we can change the first record end date as 31.12.2010 and save. then proceed to create second record with 01.01.2011 to 31.12.9999.

We have to check whether any dynamic action can be written to CHANGE the previous record end date or not.

Even though we create dynamic action and follow those steps to create a new record the change information for the first record will change to current date, which is normally not a good practise.

Think on this option and give me some more to time to come with other solution if possible.