HR_infotype_operation

[Former Member]

HI experts,

                In my previous discussion  i asked that HR_infotype_operation is not working inside the badi. all suggested that this will not work inside the badi so user user exits . now i am using this in a program to update infotype 0168  covov field . Here also am getting same mgs from the return parameter and also its not updating.

MSG: 099 no data stored in the selected period.

i tried with commit work and enqueue and Dequeue call function also but all getting fail.

if i use update statement its working fine.

For this functional module i am passing the parameters in wa. and 'mod' is the operation am giving .

please tell me is why it is happening in this functional module or is there any other functional module available to update the infotype.

thanks in advance.

[Former Member]

HI experts,

                In my previous discussion  i asked that HR_infotype_operation is not working inside the badi. all suggested that this will not work inside the badi so user user exits . now i am using this in a program to update infotype 0168  covov field . Here also am getting same mgs from the return parameter and also its not updating.

MSG: 099 no data stored in the selected period.

i tried with commit work and enqueue and Dequeue call function also but all getting fail.

if i use update statement its working fine.

For this functional module i am passing the parameters in wa. and 'mod' is the operation am giving .

please tell me is why it is happening in this functional module or is there any other functional module available to update the infotype.

thanks in advance.

[rajkumarnarasimman]

Hi Sazees.

Use FM HR_INFOTYPE_OPERATION for updating the Infotype, don't use Update statement. It is not recommendable also. 

Kindly check whether date's which are passed to FM are correct.

Regards

Rajkumar Narasimman

[Former Member]

Hai raj,

{code}

CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'

           EXPORTING

             number = WA2-pernr.

         CALL FUNCTION 'HR_INFOTYPE_OPERATION'

           EXPORTING

             INFTY                  = '0168'

             NUMBER                 =  WA2-PERNR

             SUBTYPE                =  WA2-SUBTY

            OBJECTID                =  WA2-OBJPS

*           LOCKINDICATOR          =

            VALIDITYEND             =  '20081231'

            VALIDITYBEGIN           =  WA2-BEGDA

            RECORDNUMBER            =  WA2-SEQNR

             RECORD                 = WA2

             OPERATION              = 'MOD'

*             TCLAS                = 'A'

*           DIALOG_MODE            = '0'

            NOCOMMIT               = 'X'

*           VIEW_IDENTIFIER        =

*           SECONDARY_RECORD       =

          IMPORTING

             RETURN                 = RETURN

*           KEY                    =

                   .

         CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'

           EXPORTING

             number = WA2-pernr.

{code}

in above code for endda parameter am giving '20081231' if i pass like this its showing dump and if i give it as '99992131' its showing that MSG: no data stored in this period.

[rajkumarnarasimman]

Hi Sazees,

You are modifying the existing record here. Kindly check whether the existing record is available for the particular day 20081231 in 0168 infotype. The begin date and end date should match in 0168 Infotype.  if it is available only, system can update the record. The error shows the same.

Regards

Rajkumar Narasimman

[Former Member]

Hi,

Check the below thread, it may help you

[Former Member]

Hi raj ,

ya i checked the endda and begda is same in the database endda = 12/31/2008 begda = 1/1/2008.

for endda = 12/31/9999 oly i an not getting dump expect this endda  any thing am giving ends with dump.

[Former Member]

hi tiki,

now my problem is with endda parameter . for this parameter am able to give oly '99991231' . if i give

'20081231' end up with dump. actually this record with subtype has the endda  '20081231' in my database.

[Former Member]

Hi Sazees,

I am little confused here. Endda '20081231' record is delimited right. Why is it required to modify that. There should be any valid record which you can modify. I am not sure, just a question.

[Former Member]

Hi TIKI,

actually in my sever the database has this value only . for testing purpose am giving. my client need ins3 but in our database we dont have that value so instead of ins3 i gave std3 under some  certain condition i have this endda value only.

so i gave  it. now i need to check weather this infotype will update our database if it  work fine for my database then it should work for my client database also.