HR_INFOTYPE_OPERATION - 'MOD' Operation

I am using HR_INFOTYPE_OPERATION FM for changing a infotype depending on the user input.
This FM does not change the record with modify operation (MOD).
Error while trying modify operation is as shown below:
"Infotype does not exist"
The infotype does exist with a single record in the system and I am passing the whole key to the record. I am trying it with infotype 0077.
Any idea why it's not able to modify an existing infotype. If anyone of you have ever used this FM for modify operation then pls let me know.
Thanks!
Rush

Hi Rishi,
I have done the same task which you are doing now that is IT0077 inserting and modifying operations.
Check the below parameters...
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
                EXPORTING
                  INFTY         = C_0077
                  NUMBER        = WA_0077_FR-PERNR
                  SUBTYPE       = WA_0077_FR-SUBTY
                  OBJECTID      = WA_0077_FR-OBJPS
                  LOCKINDICATOR = WA_0077_FR-SPRPS
                  VALIDITYEND   = WA_0077_FR-ENDDA
                  VALIDITYBEGIN = WA_0077_FR-BEGDA
                  RECORDNUMBER = WA_0077_FR-SEQNR
                  RECORD        = WA_0077_FR
                  OPERATION     = C_MOD
                  TCLAS         = C_A
                  NOCOMMIT      = C_X
                IMPORTING
                  RETURN        = R_OPER.
Reward if useful.
Thanks,
Anil.G

Similar Messages

Hr_infotype_operation for operation MOD

Hi,
There is a problem again using HR_INFOTYPE_OPERATION , while trying to create a new record it was successful, but when i tried to change a nonkey field the operation i have used is MOD, and it is not working.
i search for it but found problem with the same one.
can anyone please help me.
the message is: No data selected for the period.
Edited by: xxx xxx on Nov 18, 2010 10:17 PM
Edited by: xxx xxx on Nov 18, 2010 10:17 PM

Hi,
<li>Generally delimitation to ENDDA only. You get the correct record from the existing records, Change ENDDA, modified using the specified function module. Instead of 'LIS9' operation use 'MOD' operation only.
<li>Get the existing record.
CALL FUNCTION 'HR_INFOTYPE_GETDETAIL'
       EXPORTING
            INFTY         = '9906'
            NUMBER        = EMPLOYEENUMBER
            SUBTYPE       = SUBTYPE
            OBJECTID      = OBJECTID
            LOCKINDICATOR = LOCKINDICATOR
            VALIDITYEND   = VALIDITYEND
            VALIDITYBEGIN = VALIDITYBEGIN
            RECORDNUMBER = RECORDNUMBER
            TCLAS         = 'A'
       IMPORTING
            RETURN        = RETURN
            RECORD        = P9906
       EXCEPTIONS
            OTHERS        = 0.
<li>Change the ENDDA of P9906 record.
MOVE DELIMIT_DATE         TO P9906-ENDDA .
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
       EXPORTING
            INFTY          = '9906'
            NUMBER         = EMPLOYEENUMBER
            SUBTYPE        = SUBTYPE
            OBJECTID       = OBJECTID
            LOCKINDICATOR = LOCKINDICATOR
            VALIDITYEND    = VALIDITYEND
            VALIDITYBEGIN = VALIDITYBEGIN
            RECORDNUMBER   = RECORDNUMBER
            RECORD         = P9906
            OPERATION      = CHANGE
            NOCOMMIT       = NOCOMMIT
       IMPORTING
            RETURN         = RETURN
            KEY            = KEY
       EXCEPTIONS
            OTHERS         = 0.
Regards,
Venkat.O

2002 Updation using MOD -Operation.

when we try to update the 2002 infotype using HR_INFOTYPE_OPERATION
it is saving the STDAZ field value as 24
when I pass any value in STDAZ through my frontend?
is typing a message.
: for ex: 1,2,3,4,5,6,7, or 8
For Updation we are using MOD -Operation.

Hi,
STDAZ is automatically calculated from the difference btw BEGUZ and ENDUZ fields.
If you donot fill these fields bur specify STDAZ instead, the system takes the attendance as 1 day and make STDAZ as 24 hours.
Pls use BEGUZ and ENDUZ fields instead of directly updating STDAZ.
Regards,
Dilek

IDSM-2 Inline mode operation - cat6000 Hybrid

Hello, is the inline mode operation on the IDSM-2 IPS 5.1 only supported with catos 8.4(1)?
Thanks!

I agree, the IPS 5.1 release notes http://www.cisco.com/en/US/customer/products/hw/vpndevc/ps4077/prod_release_note09186a0080574954.html#wp1068104 says it requires 8.5(1) go figure.

Voir variable en temps réel en mode operator

Bonsoir,
J'aimerai savoir comment récupérer la valeur des variables à chaque instant des étapes de mes séquences de tests lorsque je suis en mode operator et en mode pas à pas.
D'avance je vous remercie,
Cordialement,
Nelson

Duplicate: http://forums.ni.com/ni/board/message?board.id=4170&message.id=32316
Aurélien J.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Du 30 juin au 25 août, embarquez pour 2 mois de vidéo-t'chat ! Prenez place pour un voyage au coe...

Differential mode operation

Hi:
Could you tell me how the current through AI+ and AI-.There is also one biase resistor from AI- to AIGND.
Attached is the digram that I cut from ni site. The AI- input is also connected to my test fixture ground at the end. I could not see how to current flow. Could you please tell me?
I am in a very urgent. I really a quick reponse.
Regards.
John
Attachments:
Differential Mode Operation.doc ‏87 KB

Hi AnalogKid:
Thanks for your replying. You said current flows through the lump sum parameter RIN nodes (1) and (2) regardless if VS- terminal 0 is connected to ground or not.
Then what is Rin? Rin is the resistor inside the 6250 board or the bias resistors from AI- to ground? Could you please tell me?
Attached is my graph. I take VS as the voltage across 100ohm resistor. Is that correct? I would like to verify with you.
Attachments:
First Picture.JPG ‏33 KB

Are there alternative solutions to disconnected mode operations?

Are there any 3rd party solutions for disconnected mode operations with Oracle databases? I've only been able to dig up Oracle Lite from searching on the web, but I'm interested in other approaches as well.
If anyone has done the research and is willing to share some competing technologies/vendors, I'd appreciate it.
Thanks

Did the same research you did about a year and a half ago and Oracle Lite is best suited for replication with an Oracle Enterprise database. Biggest reason it is easy to build, on the surface anyway. It is scalable and reliable.

HR_INFOTYPE_OPERATION mod not working

Hi all,
Getting a bit desperate here. Using HR_INFOTYPE_OPERATION in 'INS' mode and that is working fine. However, when trying to change one field - ENDDA - with OPERATION=MOD it is just not doing it. Going thru most of the other posts regarding this I get the impression that its a no-go thing. Im using HR_INFOTYPE_OPERATION in a FM that is called thru ALE processing (Process code etc).
ANY HELP IS MUCH APPRECIATED...

Hello,
It is possible to delimit a record, see this example:
DATA: lv_ret TYPE bapireturn1,
      lv_key TYPE bapipakey.
DATA: lv_1 TYPE pa0105,
      lv_2 TYPE p0105.
SELECT SINGLE * FROM pa0105 INTO lv_1 WHERE pernr = '31000417' AND subty = '0021'.
MOVE-CORRESPONDING lv_1 TO lv_2.
lv_2-subty = '0021'.
lv_2-infty = '0105'.
lv_2-endda = sy-datum.
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
    number = '31000417'
IMPORTING
    return = lv_ret.
IF lv_ret IS INITIAL.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
      infty         = '0105'
      number        = '31000417'
      subtype       = '0021'
      objectid      = ''
      lockindicator = ''
      validityend   = '99991231'
      validitybegin = '20060601'
      recordnumber = 0
      record        = lv_2
      operation     = 'MOD'
    IMPORTING
      return        = lv_ret
      key           = lv_key.
IF 1 = 2. ENDIF.
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
    EXPORTING
      number = '31000417'
    IMPORTING
      return = lv_ret.

'HR_INFOTYPE_OPERATION' MOD is not updating my infotype

Hi all,
I have a custom field called ZXXXX in both 2010 and 0015, I'm trying to clear it up if it's populated and update certain infotype record for the particular employee.
but I was able to clear ZXXXX in infotype 0015 but not 2010, I'm using the same code but not understand why it works for infotype 0015 but not 2010. any thought?
Below is the code, thanks all!
DATA l_return1 TYPE bapiret1.
DATA l_return2 TYPE bapiret1.
START-OF-SELECTION.
GET PERNR.
RP-PROVIDE-FROM-LAST P0015 SPACE PNPBEGDA PNPENDDA.
RP-PROVIDE-FROM-LAST P2010 SPACE PNPBEGDA PNPENDDA.
      CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          NUMBER = PERNR-PERNR.
            LOOP AT P2010 WHERE ZXXXX IS NOT INITIAL AND pernr = pernr-pernr.
        CLEAR P2010-ZXXXX.
        CALL FUNCTION 'HR_INFOTYPE_OPERATION'
          EXPORTING
            INFTY                  = '2010'
            NUMBER                 = P2010-PERNR
            SUBTYPE                = P2010-SUBTY
            OBJECTID               = P2010-OBJPS
            RECORDNUMBER           = P2010-SEQNR
            LOCKINDICATOR          = P2010-SPRPS
            VALIDITYEND            = P2010-ENDDA
            VALIDITYBEGIN          = P2010-BEGDA
*           RECORDNUMBER           =
            RECORD                 = P2010
            OPERATION              = 'MOD'
*            TCLAS                  = 'A'
*            DIALOG_MODE            = '0'
*           NOCOMMIT               =
*           VIEW_IDENTIFIER        =
*           SECONDARY_RECORD       =
          IMPORTING
            RETURN                 = L_RETURN1
*           KEY                    =
      ENDLOOP.
      LOOP AT P0015 WHERE ZXXXX IS NOT INITIAL AND pernr = pernr-pernr.
        CLEAR P0015-ZXXXX.
        CALL FUNCTION 'HR_INFOTYPE_OPERATION'
          EXPORTING
            INFTY                  = '0015'
            NUMBER                 = P0015-PERNR
            SUBTYPE                = P0015-SUBTY
            OBJECTID               = P0015-OBJPS
            RECORDNUMBER           = P0015-SEQNR
            LOCKINDICATOR          = P0015-SPRPS
            VALIDITYEND            = P0015-ENDDA
            VALIDITYBEGIN          = P0015-BEGDA
*           RECORDNUMBER           =
            RECORD                 = P0015
            OPERATION              = 'MOD'
*            TCLAS                  = 'A'
*            DIALOG_MODE            = '0'
*           NOCOMMIT               =
*           VIEW_IDENTIFIER        =
*           SECONDARY_RECORD       =
          IMPORTING
            RETURN                 = L_RETURN2
*           KEY                    =
      ENDLOOP.
        CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
          EXPORTING
            NUMBER = PERNR-PERNR.
        END-OF-SELECTION.

Hi Ben,
Let's forget about using FM 'HR_INFOTYPE_OPERATION' for the moment for IT2010 and try to implement this another way - please use the code below for the IT2010 change only.
DATA:
    lif_msg_handler TYPE REF TO if_hrpa_message_handler,
    lo_msg_handler   TYPE REF TO cl_hrpa_message_list,
    lv_ok            TYPE boole_d,
    ls_old_2010      TYPE pskey,
    ls_new_2010      TYPE P2010.
* instantiate the message handler object
CREATE OBJECT lo_msg_handler.
* assign a reference to a rereference variable using the CAST operation
lif_msg_handler ?= lo_msg_handler.
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
          EXPORTING
            NUMBER = PERNR-PERNR.
LOOP AT P2010 WHERE ZXXXX IS NOT INITIAL.
           "AND pernr = pernr-pernr. "<=== you don't need this AND condition as you are using LDB already
     ls_old_2010 = p2010-pskey.
     ls_new_2010 = P2010.
     ls_new_2010-aedtm = sy-datum.      "<===== so that record history is correctly maintained
     ls_new_2010-uname = sy-uname.      "<===== so that record history is correctly maintained
     CLEAR ls_new_2010-ZXXXX.
* transfer the infotype record to the infotype buffer first
    CALL FUNCTION 'HR_ECM_MODIFY_INFOTYPE'
      EXPORTING
        PNNNN           = ls_new_2010               "<======= New/Modfied record
*        text_tab        =
*        modify_text =
         OLD_PSKEY = ls_old_2010                    "<======== Old/Existing record
*        no_auth_check   =
        message_handler = lif_msg_handler
      IMPORTING
        is_ok           = lv_ok.
* process forward only if the transfer to buffer was successful
* - if unsuccessful...
    IF lv_ok IS INITIAL.
*     "<==== Handle your exceptions here.....and CONTINUE processing the next row in the current loop
    ELSE.
* - if successful...
* now flush to transfer from infotype buffer to SAP database
      CALL FUNCTION 'HR_ECM_FLUSH_INFOTYPE'
        EXPORTING
*        NOCOMMIT              = 'X'
          message_handler       = lif_msg_handler
       IMPORTING
         is_ok                 = lv_ok.
   ENDIF.
ENDLOOP.
* unlock the employee - processing now complete
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
          EXPORTING
            NUMBER = PERNR-PERNR.
I'm confident that this will solve your problem - please let me know if it did not.
Cheers,
Sougata.

HR_INFOTYPE_OPERATION Dellimit operation 'LIS9'

Hey All,
     I am trying to write a report to fix some corrupted HR address data(IT0006) using FM HR_INFOTYPE_OPERATION. I know how to use the FM in INS and MOD mode, but this time I am trying to use the delimit operation.
Due to error we have a lot of records with subtype 'Blank', Instead of deleting the corrupted records, I am trying to delemit the records to a older date so that it doesnt show up at the top.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty                  = '0006'
          number                 = wa_p0006-pernr
          subtype                = wa_p0006-subty
          objectid               = wa_p0006-objps
          lockindicator          = wa_p0006-sprps
          validityend            = wa_p0006-endda
          validitybegin          = wa_p0006-begda
          recordnumber           = wa_p0006-seqnr
          record                 = wa_p0006
          operation              = 'LIS9'
          tclas                  = 'A'
          dialog_mode            = '0'
       IMPORTING
         return                 = wa_bapiret1.
When i try to change the enddate so that it delimits the record to that date, it gives me a complex application error.
Any input is higly appreciated.
Thanks

Hi Aparna,
try using the operation 'MOD' with e_p0006 having the modified date
chechk this
e_p0006 = wa_p0006.
e_p0006-endda = 'Delimit date'.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '0006'
number = wa_p0006-pernr
subtype = wa_p0006-subty
objectid = wa_p0006-objps
lockindicator = wa_p0006-sprps
validityend = wa_p0006-endda
validitybegin = wa_p0006-begda
recordnumber = wa_p0006-seqnr
record = e_p0006
operation = 'MOD'
tclas = 'A'
dialog_mode = '0'
IMPORTING
return = wa_bapiret1.
Edited by: Jacks M on Jul 23, 2008 8:25 PM

Infotype MOD operation.

Hi all.
I am using HR_INFOTYPE_OPERATION to delimit the record in my infotype.. I want to modify the ENDDA = sy-datum - 1 in the existing record... But that FM is itself is not working.... is there any alternative to this FM?? Please reply me.. Its very urgent..
My code..
    l_enddate = sy-datum - 1.
    wa_read_pernr-endda = l_enddate.
    CLEAR ls_return.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty         = '9035'
        number        = wa_read_pernr-pernr
        subtype       = wa_read_pernr-subty
        objectid      = wa_read_pernr-objps
        lockindicator = wa_read_pernr-sprps
        validityend   = enddate
        validitybegin = wa_read_pernr-begda
        recordnumber = wa_read_pernr-seqnr
        record        = wa_read_pernr
        operation     = 'MOD'
        tclas         = 'A'
        dialog_mode   = dialog_mode
        nocommit      = space
      IMPORTING
        return        = ls_return
        key           = wa_key.

Hi Elan,
1. When calling the FM, in the parameter enddate,
    make sure you are passing the OLD/EXISTING value
    (which is there in the PA table)
    for the ENDDA field.
2. I also assume you are locking the employee before
   calling this FM.
one sample code as below :
3.
Report abc.
*----------------- Data
DATA : P0015 LIKE P0015.
DATA : RETURN LIKE BAPIRETURN1.
DATA : KEY LIKE BAPIPAKEY.
DATA : RETURNE LIKE BAPIRETURN1 .
*------------- Values (Change as per Requirement)
P0015-PERNR = '1'.
P0015-BEGDA = '2061101'.
P0015-ENDDA = '2061101'.
P0015-LGART = '3075'.
P0015-PREAS = '01'.
P0015-WAERS = 'INR'.
P0015-BETRG = '2500'.
*----- First Enqu
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
NUMBER = p0015-pernr
IMPORTING
RETURN = RETURNE.
*------------- Update
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
INFTY = '0015'
NUMBER = P0015-PERNR
SUBTYPE = P0015-SUBTY
OBJECTID = P0015-OBJPS
LOCKINDICATOR = P0015-SPRPS
VALIDITYEND = P0015-ENDDA
VALIDITYBEGIN = P0015-BEGDA
RECORDNUMBER = P0015-SEQNR
RECORD = P0015
OPERATION = 'INS'
TCLAS = 'A'
DIALOG_MODE = '0'
IMPORTING
RETURN = RETURN
KEY = KEY.
IF RETURN IS NOT INITIAL.
WRITE :/ 'Error Occurred'.
ENDIF.
*--------- Dequeue
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING
NUMBER = P0015-PERNR
regards,
amit m.

Why mod operator is invalid in the loop

code ：
TABLES spfli.
data c type i.
SELECT * FROM spfli.
c = ( sy-linno mod 2 ).
if c = 0.
    format COLOR COL_TOTAL.
else.
    format COLOR col_key.
endif.
WRITE : / sy-vline,(15) spfli-carrid,
         sy-vline,(15)spfli-connid,
         sy-vline.
ULINE AT /(37).
ENDSELECT.
Variable c is 0， never changed in the loop why ?

Hi,
Use it this way:-
data : itab type standard table of spfli with header line.
select * from splfi into table itab.
loop at itab.
"write code here
endloop.
Hope this helps you.
Regards,
Tarun

Help with wrt310n n mode operation

In n mode, i can connect to my laptop from the wireless router. However if I include wep or wpa-personal I cannot connect. the laptop is running vista. beacon int 75, DTIM 1, Frag 2306, RTS 2307
In G or mixed mode all works 54 mbps, but that defeats the purpose of N at 130mbps
I would really appreciate help.
(Mod note: Edited for guideline compliance.)
Message Edited by giantherockstar on 11-18-2008 01:03 PM

Do you use N adapter on the other side.

Using delete/insert mode operator target in mapping

Hello Guys,
Can you help me please to resolve my problem. It's very urgent.
I use OWB 10gR2 and I create a mapping for loading data from table to table.
I got a source table A that I want to integrate into a table B.
I want to put my target table B on delete/insert mode to delete data from B where A.annee = B.annee
before inserting data from A.
How to configure this mapping.
Thanks in advance.
Regards.
fanfita.

you dont have to do anything in particular:
on the target table propperties click on the load type as Delete/Insert and specify the column which you need to check while deleting this can be done by clicking on the column of target table in your mapping and setting the properties such as "load while insert/delete/update etc" , you got to check the delete option of the columns that you want to check while deleting.
If your target table has sequence then delete and insert will generate new sequence id and i am not sure if there is a Foregin key which needs to be considered here so it might be a better option to use update/insert
if there are no dependencies at all then you can go for delete/insert option.
Edited by: Darthvader-647181 on Feb 5, 2009 1:46 AM

Mod Operator malfunctioning

See the following code two different Result for the same thing
First Code with Output which is Wrong
System.out.println( "Mod of 015110 % 7 ===> " + ( 015110 % 7 ) );
Mod of 015110 % 7 ===> 1
Now look at this Code with Output which is Correct
System.out.println( "Mod of 15110 % 7 ===> " + ( 15110 % 7 ) );
Mod of 15110 % 7 ===> 4Can anyone explain why it is like this.....

prometheuzz wrote:
DarrylBurke wrote:
prometheuzz wrote:
If you start an integer value with a zero, it gets interpreted in base 7Base 8 (octal), not?
dbThe horse is already dead Darryl! : )Surely, under the n-1 rules, it's merely dying

HR_INFOTYPE_OPERATION - 'MOD' Operation

Similar Messages

Maybe you are looking for