Updating hr infotype pa0305 with 'HR_INFOTYPE_OPERATION'

Hi everyone i'm trying to update hr infotype pa0305 using fm HR_INFOTYPE_OPERATION but it doesn't work maybe using in worng way.
Maybe someone knows how can i use the second structure q0305 passing trough the parameter called "secondary records".
Thanks in advance,

Sorry for the late, the problem was that the part structure of p305 is empty; the part of wage type and amount exactly.
CLEAR lv_return .
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty                  = '0305'
        number                 = wa_alvgrid2_error-pernr
        subtype                = ''
        OBJECTID               =
        LOCKINDICATOR          =
       validityend            = wa_alvgrid2_error-endda
       validitybegin          = wa_alvgrid2_error-begda
        RECORDNUMBER           =
        record                 = st_0305
        operation              = 'INS'
        tclas                  = 'A'
        dialog_mode            = '2'
         nocommit               = ' '
        view_identifier        = '15'
        secondary_record       = st_q0305
     IMPORTING
       return                 = lv_return
        KEY                    =.
maybe I am in wrong when I pass the secondary record.

Similar Messages

Updating custom infotype with FM 'HR_INFOTYPE_OPERATION' dumps

Hi All,
While updating a custom infotype 9008 with FM 'HR_INFOTYPE_OPERATION', its giving adump.
Except. CX_HRPA_INVALID_PARAMETER.
I am using DIALOG_MODE as '1'. when I enter a valid field value to that particular field ( mandatory field) on that infotype, it gives dump.
Can you suggest something which will solve this?
Thanks.
Dipti.

Hi,
Here is the dump.
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_HRPA_INVALID_PARAMETER
Date and Time          12.11.2008 07:23:32
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_HRPA_INVALID_PARAMETER' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_HRPA_RESOLVE_EXCEPTION=====CP' has to be
terminated.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not
caught in
procedure "RESOLVE_EXCEPTION" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Invalid parameter EXCEPTION, value
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_HRPA_VIOLATED_PRECONDITION", which was raised in the
program "CL_HRPA_MASTERDATA_FACTORY====CP",
specifically in line 6 of the (include) program
"CL_HRPA_MASTERDATA_FACTORY====CM004".
The cause of the exception was:
Precondition Violated
Missing RAISING Clause in Interface
Program                                 SAPFP50P
Include                                 FP50PE10
Row                                     2,152
Module type                             (FORM)
Module Name                             RESOLVE_EXCEPTION
Trigger Location of Exception
Program                                 CL_HRPA_RESOLVE_EXCEPTION=====CP
Include                                 CL_HRPA_RESOLVE_EXCEPTION=====CM001
Row                                     80
Module type                             (METHOD)
Module Name                             RESOLVE
Source Code Extract
Line
SourceCde
50
message_handler = message_handler.
51
return.
52
53
catch cx_sy_move_cast_error.
54
endtry.
55
END-OF-DEFINITION.
56
57
58
try_to resolve_missing_infty_data    cx_hrpa_missing_infty_data.
59
try_to resolve_missing_authorization cx_hrpa_missing_authorization.
60
try_to resolve_invalid_feature       cx_hrpa_invalid_feature.
61
try_to resolve_unexpected_message    cx_hrpa_unexpected_message.
62
try_to resolve_missing_personid      cx_hrpa_missing_personid.
63
try_to resolve_invalid_infotype_db   cx_hrpa_invalid_infotype_db.
64
try_to resolve_invalid_customization cx_hrpa_invalid_customization.
65
try_to resolve_inconsistent_database cx_hrpa_inconsistent_database.
66
67
68
Just to ensure the macro can be used nowhere else.
69
DEFINE try_to.
70
END-OF-DEFINITION.
71
72
If we can not remap we would like to just re-raise the
73
exception like below like "RAISE EXCEPTION exception.".
74
Unfortunately the kernel will then forget about the
75
original source position.
76
77
So this is the fallback strategy. Calling this method
78
is only allowed if the exception can be resolved. Since
79
this is not the case we indicate a parameter violation.
>>>>>
RAISE EXCEPTION TYPE cx_hrpa_invalid_parameter
81
EXPORTING
82
previous = exception
83
parameter = 'EXCEPTION'.
84
85
ENDMETHOD.
Regards,
Dipti.

Creating / updating Custom infotype with different screen

Hi All,
I have created custom infotype having different screen for different subtype(1,2).
From Subtype 1, indotype is automatically updated as it is a standard program. But for subtype 2 i am using HR_INFOTYPE_OPERATION for updating the record which is ending with error, as employee which i am trying to update is already locked by me only through PA30. So this function module ends with Complex error. Please suggest how to update the infotype with subtype 2.
Thanking you..
Best regards
Akshay

Hi All,
I have created custom infotype having different screen for different subtype(1,2).
From Subtype 1, indotype is automatically updated as it is a standard program. But for subtype 2 i am using HR_INFOTYPE_OPERATION for updating the record which is ending with error, as employee which i am trying to update is already locked by me only through PA30. So this function module ends with Complex error. Please suggest how to update the infotype with subtype 2.
Thanking you..
Best regards
Akshay

Infotype updation- alternate solution for FM HR_INFOTYPE_OPERATION.

Hi Expert ,
Right now i am using FM HR_INFOTYPE_OPERATION to insert data to infotype 19.
Problem i am facing is data to be inserted is very large and this takes lot of time.
Is there any other FM which updates infotype in mass i mean using internal table? Since in this FM cant pass internal table so i have to call this FM for every PERNR.
Thanks & Regards ,
JIgar Thakkar.

Hi Jigar
As suggested by Rahul, Use the FM: HR_PSBUFFER_INITIALIZE. This will improve the performance of your code to a great extend. I would personally, use HR_MAINTAIN_MASTERDATA or HR_INFOTYPE_OPERATION to update the infotype 0019. However, both are buffering the data and doing some EXPORT to memory. The result of this is that after a few hundred calls to HR_INFOTYPE_OPERATION or HR_MAINTAIN_MASTERDATA, the buffer gets big enough to impact the performance of the function module. After thousand of updates with HR_INFOTYPE_OPERATION or HR_MAINTAIN_MASTERDATA, each call will take many seconds and your ABAP program will be unusable. Because you run it for high volumes only in the SAP production system, thatu2019s when youu2019ll really see the impact.
The solution is simple. Call this function module to clear the buffer.
CALL FUNCTION 'HR_PSBUFFER_INITIALIZE'.
Hope this helps.
Harsh

Updating infotype screen with screen fields

Hello everyone,
I am working on a RFC to update infotype 0077. Infotype 77 has veteran status as screen fields from Q0077 structure. I am using HR_INFOTYPE_OPERATION to update 77. Could anyone please tell me how to update the screen and database table pa0077.
Thanks for your time and answers.
Rush

Thank you Balaji. I tried updating with HR_INFOTYPE_OPERATION but no luck. Could you please suggest any other way of updating field in info type screen (Q0077 structure) as well as in PA0077 table??
Thanks
Rush

'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.

Updating infotype 0041 using HR_INFOTYPE_OPERATION?

Hi All:
How do we update the dates in infotype 0041 using HR_INFOTYPE_OPERATION? lets say we have 6 dates populated in 41 and we another employee has 9 dates populated. We are reading these records and need to update the dates for all the employee records.
Thanks
Venkata

Hi Venkata,
What you can do is use the HR_INFOTYPE_OPERATION in Change or MOD(Modify) mode i.e.
pass 'MOD' in operation parameter.
Your recordnumber parameter should have the sequence number from infotype record you are updating (field SEQNR). All other parameters should be as it is had been for INS or insert operation.
Regards.

Problem in updation of infotype 1 & 8

Hi all,
I m using funtion module 'HR_MAINTAIN_MASTERDATA' for updation of data in infotype 1 and 8, But basic pay does not updated through that. all other fields are getting updated. I also used HR_INFOTYPE_OPERATION FM, but problem remains same.
<< Moderator message - Everyone's problem is important. Please do not ask for help quickly. >>
Edited by: Rob Burbank on Dec 3, 2010 4:03 PM

hi volker,
Manually am able to update that field UNPSI.
I have checked the table pa0584 manually updated value is found in the table.
But the value which i have inserted using the FM created an empty record with the field UNSPI having 0 value.
I have given all the fields into the record as same as when it is update dmanually.
I dnt knw why the value is not updating.
p0584_2-pernr = wd_comp_controller->gv_pernr.
p0584_2-infty = '0584'.
p0584_2-subty = '0002'.
p0584_2-begda = '20100401'.
p0584_2-endda = '20110331'.
   p0584_2-OBJPS = '01'.
   p0584_2-SPRPS = 'X'.
p0584_2-seqnr = '01'.
p0584_2-UNSPI = ls_actual_details-other_income.
p0584_2-INTYP = '0002'.
p0584_2-WAEHI = 'INR'.
p0584_2-AEDTM = sy-datum.
p0584_2-UNAME = sy-uname.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    infty                  = '0584'
    number                 = wd_comp_controller->gv_pernr
   SUBTYPE                = '0002'
OBJECTID               = p0584_2-OBJPS
LOCKINDICATOR          = p0584_2-SPRPS
   VALIDITYEND            = p0584_2-endda
   VALIDITYBEGIN          = p0584_2-begda
   RECORDNUMBER           = '01'
    record                 = p0584_2
    operation              = 'INS' "lv_op_type
   TCLAS                  = 'A'
   DIALOG_MODE            = '0'
NOCOMMIT               =
VIEW_IDENTIFIER        =
SECONDARY_RECORD       =
IMPORTING
   RETURN                 = return_584_2
   KEY                    = key.
Pls give some solutions
Thanks
Nalla B

Problem updating the infotype 1208 subtype ALUM

Hi,
My requirement is to update the infotype 1208 subtype ALUM with the Value "YES" when I terminate a employee in PA40. ( immediately).
I am using the FM - HR_INFOTYPE_OPERATION which doesn't seem to work.
I tried running a BDC for PA30 , but it is not allowing me to edit the employee and says that i am processing him.
I feel this is an issue with locks. But not sure about how to go with.
Are there any standard classes available or any other method to use to update this infotype while terminating.
Regards,
Karan.

Hi,
try using this method, this will convert the OLD_IMAGE, NEW_IMAGE, parameters into pnnnn table.
this code is the following class.
CL_IM_BR_SALARY_INCREASE,
you need to create your own method, copy the parameters as well.
method READ_IMAGE .
FIELD-SYMBOLS: <f> type any.
DATA: help_prelp TYPE prelp,
        inf_tabname(10).
data: wa_p0008      type p0008,
        wa_p0734      type p0734.
concatenate 'WA_P' p_infty into inf_tabname.
ASSIGN (inf_tabname) TO <f>.
loop at p_image into help_prelp
                  where infty eq p_infty and
                        opera eq p_opera and
                        subty eq '0'.
    CLEAR <f>.
    CALL METHOD cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
      EXPORTING
        prelp = help_prelp
      IMPORTING
        pnnnn = <f>.
      append <f> to pnnnn.
endloop.
endmethod.
Message was edited by:
        javier santana

How to Insert Infotype by FM HR_INFOTYPE_OPERATION

Hi,
I am using HR_INFOTYPE_OPERATION FM to insert and update the infotype.
I am able to update the data but unable to insert.
When I use MOD operation the data is updated successfully but for INS operation it is again rather than inserting record it is updated again.
Please see the following sample code .
REPORT ZHR_UPDATE_INFOTYP.
DATA: G_RETURN LIKE BAPIRETURN1,
      IT_P0003 LIKE P0003,
      G_SUBRC TYPE SY-SUBRC.
data: l_infty type prelp-infty value '0003',
      l_infty_tab type table of pa0003 with header line,
      wa_infty type pa0003.
PARAMETER: P_PERNR LIKE PA0003-PERNR,
          P_MODE TYPE CHAR1.
start-of-selection.
IT_P0003-INFTY = '0003'.
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
TCLAS                 = 'A'
    pernr                 = p_pernr
    infty                 = l_infty
BEGDA                 = '20110905'
   ENDDA                 = '99991231'
BYPASS_BUFFER         = ' '
LEGACY_MODE           = ' '
IMPORTING
SUBRC                 = SUBRC
TABLES
    infty_tab             = l_infty_tab
EXCEPTIONS
INFTY_NOT_FOUND       = 1
read table l_infty_tab index 1 into wa_infty.
CLEAR:IT_P0003.
IT_P0003 = wa_infty.
IT_P0003-ABWD1 = sy-datum - 1.
PERFORM HR_INFOTYPE_OPERATION USING IT_P0003 P_MODE
                              CHANGING G_RETURN
                                       G_SUBRC.
WRITE:/ 'G_SUBRC',G_SUBRC.
*&      Form HR_INFOTYPE_OPERATION
      text
FORM HR_INFOTYPE_OPERATION USING   P_P0003 STRUCTURE P0003
                                    P_P_MODE
                            CHANGING P_P_RETURN
                                     P_P_SUBRC.
DATA: L_OPERATION TYPE PSPAR-ACTIO,
        L_KEY LIKE BAPIPAKEY.
CASE P_P_MODE.
    WHEN '1'.
      L_OPERATION = 'INS'.
    WHEN '2'.
      L_OPERATION = 'DEL'.
    WHEN '3'.
      L_OPERATION = 'MOD'.
    WHEN OTHERS.
ENDCASE.
*--Performing Infotype Operations Using FM
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
    EXPORTING
      NUMBER = P_P0003-PERNR.
   IMPORTING
     RETURN = P_P_RETURN.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
      INFTY                  = P_P0003-INFTY
      NUMBER                 = P_P0003-PERNR
      SUBTYPE                = P_P0003-SUBTY
OBJECTID               = OBJECTID
LOCKINDICATOR          = LOCKINDICATOR
   VALIDITYEND            = P_P0003-ENDDA
   VALIDITYBEGIN          = P_P0003-BEGDA
RECORDNUMBER           = RECORDNUMBER
      RECORD                 = P_P0003
      OPERATION              = 'INS'
   TCLAS                  = 'A'
    DIALOG_MODE            = '1'
NOCOMMIT               = NOCOMMIT
VIEW_IDENTIFIER        = VIEW_IDENTIFIER
SECONDARY_RECORD       = SECONDARY_RECORD
   IMPORTING
     RETURN                 = P_P_RETURN
     KEY                    = L_KEY .
P_P_SUBRC = SY-SUBRC.
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
    EXPORTING
      NUMBER = P_P0003-PERNR.
   IMPORTING
     RETURN = RETURN.
ENDFORM.                    " HR_INFOTYPE_OPERATION
Any help will be greatly appreciate

not solved ,closed sadly

How to update other infotype from source infotype via function module?

Want in source infotype to call a func.module, which shall update other infotype(s) in background.
Have tried out with HR_INFOTYPE_OPERATION, but without success - gives mitchmatch of source it and target it in the internal it buffer tables.
How to do?
Requirements also are to secure rollback, if update of the last of ex. 3 target its fails.
Anyone has experience on this issue?
Regards Søren

Know this functionality - also by means of own coding in the PAI by filling the int. tables dynmeas + initial_values. However the issue remains, i.e. the update has to be done by a function module called from PAI of own infotype, and from a function module you can't trigger the T588Z-functionality.
The update of it0003 from own it9300 is only an example, have general requirements that:
- from own infotype PAI a function module shall be called
- from the function module update of other infotypes
shall take place (modify as well as insert and delete)
- if more infotypes shall be updated from source infotype,
rollback shall take place if ex. update of last target
infotype fails (all to be updated or none!).
Regards Søren

SAP HCM P&F - Update an infotype field which is NOT passed from Form

Dear Experts,
I have a requirement to update the Infotype with the entries in the HCM form (input by Employee in ESS) upon Manager's approval in MSS.
We are achieving this functionality using HCM P&F (FPM) with an Workflow associated. In this Workflow Standard Task (TS17900108) is used to Save the form data into the Database.
But there is one field (APPROVED_DATE) in the Infotype whose value is not from the FORM but should be updated in the Infotype.
Please help me with your inputs.
Regards,
Shankar

Dear Christopher,
I am extremely thankful to you for all the replies. But, unfortunately, we are messed up with this requirement and we couldn't achieve it.
In this regard, could you please give us the step-by-step procedure to achieve this functionality?
Requirement in brief again:
We have designed Overtime HCM form (FPM) using which employee requests for the Overtime. This form is sent for the Manager for approval. We have achieved this functionality. With the Manager Approval, the database is also updated perfectly.
Then we have added one more field in the infotype to track the Approved Date. This field is to be updated along with the other fields (sent from FORM) upon the approval of the manager.
And now though the other fields are updated correctly into the infotype, the approved date is not updated.
Thanks a ton in advance for your guidance as this is very critical and urgent requirement for us.
Regards,
Shankar.

Unable to update OM infotypes

Hi Experts ..
I am using Routine   'RP_INFOTYP IN PROGRAM SAPFP50G' to update infotypes in Webdynpro application .
But Issue is 'When I do a promotion for an employee its updating PA infotypes correct . but OM side I could not find A008 for new position with employee .SO OM infotype is not updating .
So I have debugged and analyzed . I could find 2 structures PSPAR and PSYST are having positions with current and new position when I do promotion using PA40 . but When I do promotion with webdynpro application both structures are having the same position that is new position .
IF anyone face this kind of issue .Please reply .
Thanks
kamesh
Edited by: KAMESH G on Mar 28, 2011 4:33 PM

Issue is resolved after removing files from /var/tmp/. How we can check the total available/used size of /var/tmp.
/dev/md/dsk/d100
40345224 15386130 24555642
39%
/devices
0
0
0
0%
/devices
ctfs
0
0
0
0%
/system/contract
proc
0
0
0
0%
/proc
mnttab
0
0
0
0%
/etc/mnttab
swap
98411724
980 98410744
1%
/etc/svc/volatile
objfs
0
0
0
0%
/system/object
sharefs
0
0
0
0%
/etc/dfs/sharetab
/usr/lib/libc/libc_hwcap2.so.1 40345224 15386130 24555642
39%
/lib/libc.so.1
fd
0
0
0
0%
/dev/fd
/dev/md/dsk/d130
10085921 2416294 7568768
25%
/var
swap
98431612   20868 98410744
1%
/tmp
swap
98410772
28 98410744
1%
/var/run

Updating another infotype in the in_update badi

Hi Experts.
We are upgrading from 4.6c to ECC.
We are updating a lot of infotypes using HR_INFOTYPE_OPERATION (passing no_commit = x) in the in_update Badi.
Now when the infotype being updated in the in_update fails, HR_INFOTYPE_OPERATION internally issues a ROLLBACK WORK.
See these lines from the FM:
IF RETURN IS INITIAL.
READ TABLE MODIFIED_KEYS INDEX 1.
MOVE MODIFIED_KEYS(8) TO KEY(8).
MOVE MODIFIED_KEYS12 TO KEY8.
ELSE.
IF NOT NOCOMMIT IS INITIAL.
ROLLBACK WORK.
ENDIF.
It worked correctly in 4.6c.
Now in ECC, it starts giving a dump - saying that ROLLBACK work is not allowed within the in_update.
Short text of error message:
ROLLBACK WORK during ON COMMIT or ON ROLLBACK
It sounds logical - but I am not sure how come it was working in 4.6c.
Any work arounds to it? Anyone else also encounter it?
Thanks in adv.

Hi Aishi!
I had a short look inside HR_MAINTAIN_MASTERDATA (in HR_INFOTYPE_OPERATION) - seems like there are some call transactions. A call transaction has invariably a commit work inside, so the parameter "nocommit" just defines a "dialog" parameter.
Looks like the logic of the update was changed - or the "in_update" badi wasn't really called in update task earlier.
Best way: search for other ways to update master data (without commits) - at least much better than the risk of additional commits in update task.
BR, Christian

Updating the infotype 9901

Hi,
I have a req, i will get a file and need to update the data from file into the infotype 9901 with other fields too.
can anyone of u provide me with any sample logic.
I may need to create a new record,modify the existing record or delete the record from 9901.
please help me in this.
am new to hr abap.
thanks,
Moderator message: sorry, these forums cannot replace proper training, please search for available documentation or attend classes.
Edited by: Thomas Zloch on Nov 10, 2010 6:21 PM

But still one question remains.
Why the HISTO field is set as 'X'? If this is so, as per SAP documentation, we will never be able to change that text.
SAP Help -
on HISTO field
Historical Record Flag
Allows you to mark infotype records as historical records. Historical records are permanently stored on the database, so that
you can report on the information at a later point in time.
NOTE: You cannot change records once they are marked as historical. As a result, you should not mark records as historical
unless you no longer require them for processing.
Thanks,
Bhaskar
Edited by: Bhaskar Tripathi on Dec 21, 2010 9:22 AM
Edited by: Bhaskar Tripathi on Dec 21, 2010 9:23 AM

Updating hr infotype pa0305 with 'HR_INFOTYPE_OPERATION'

Similar Messages

Maybe you are looking for