topic Re: Using Infotype 2050 in Application Development and Automation Discussions

Using Infotype 2050

Barada_Swain — Tue, 11 Dec 2007 09:07:12 GMT

Hi All,

I have a requirement to use infotype 2050 in a program. Now when I checked in the database there are no assosciated table. Some one suggested PA2050, but that table is not present. I could get only one structure named P2050.

I have also tried to use FM HR_READ_INFOTYPE but the same error comes.

Is there any config settings etc need to be done.

My requirement is the Employee Leave records - which is infotype 2050. Is there any other way in which I can fetch the relevant info for this.

Please reply ASAP.

Thanks

Baradakanta.

Re: Using Infotype 2050

Former Member — Tue, 11 Dec 2007 09:23:32 GMT

Hi..

check this table <b>T554S</b>

Re: Using Infotype 2050

Barada_Swain — Fri, 14 Dec 2007 13:02:07 GMT

Hi Sheeba,

Thanks for the reply but after checking the above table I could not find out my requirement. Let me specify it in more detail.

The program is to do a resource(employees) scheduling for a span of 6 months for a plant. Now the flow of the program says that I have to take the details of the employees leaves etc from SAP and then I will do the scheduling so that all the employees are equally loaded all through the period.

I accept I don't know much about HR module. So, can you suggest a answer so that I could get the employees leave schedule.

It may be a table(or join of multiple tables) or say any other infotype which I can use.

Thanks and regards.

Re: Using Infotype 2050

Former Member — Fri, 14 Dec 2007 13:26:26 GMT

hi,

is ur requirement any way related to absentees maintenence?....

let me know if so, i l try to send u a porgram. mail id is sabah_683@yahoo.co.in

Re: Using Infotype 2050

Former Member — Fri, 14 Dec 2007 13:30:25 GMT

or u can use this function module which perfoms operationson infotype:

p0002-begda = p_date.

CALL FUNCTION 'HR_INFOTYPE_OPERATION'

EXPORTING

INFTY = '0002'

NUMBER = pernr-pernr

SUBTYPE =

OBJECTID = p0002-objps

LOCKINDICATOR = p0002-sprps

VALIDITYEND = p0002-begda

VALIDITYBEGIN = p0002-endda

RECORDNUMBER = p0002-seqnr

RECORD = p0002

OPERATION = 'INS'

TCLAS = 'A'

DIALOG_MODE = '0'

NOCOMMIT =
VIEW_IDENTIFIER =
SECONDARY_RECORD =

IMPORTING

RETURN = return

KEY =

try giving ur infotype numbet inthe infty argument and fill the required parameters in the func module.......

any help furhter ask, i ll try tosolve but cant guarantee as am also not wel versed inHR

Re: Using Infotype 2050

Barada_Swain — Fri, 14 Dec 2007 13:34:43 GMT

Hi Sabahuddin,

Thanks for the reply. I am exactly not sure if only absentee maintanance will do the job. Because I think absentee maintenance will be a little more detailed lavel work than the functionality I want.

Can you mention in a little detail what your program does? May be I will be more clear then.

Thanks.

Re: Using Infotype 2050

Former Member — Fri, 14 Dec 2007 19:52:22 GMT

Hi,

IT2050 exists in DB in form of structure P2050 only.

It is used in tr. PA30 for example to output screen 'Annual Calendar' so that absences (IT2001) can be generated for the whole year.

It cannot be read in the program with macro or FM 'HR_READ_INFOTYPE' though.

If you need simething simular in your report check RPTABS50.

Vladimir.

Re: Using Infotype 2050

Barada_Swain — Sat, 15 Dec 2007 06:11:27 GMT

Thanks All of you for the replies. Just let me know one thing now.

IT2001 table has the absences for the whole year as said by Vladimir. So does it has the absences in the future periods also ot it contains only the histotical data.

My program will do the projected scheduling for the future periods. So can I use IT2001 data for the absences and somehow interpret them (manully) to print out a Calender. Also would I have to mix this data along with the holidays(defined holidays) to filter out the working days in the output. If yes where can I get that holidays data?

Thanks in advance.

Re: Using Infotype 2050

Barada_Swain — Tue, 20 Jan 2009 05:45:35 GMT

We convinced the client to use custom tables to maintain the projected leaves data.

So we are not using Infotype 2050 anymore and hence closing the thread.

Regards

Barada