Infotype updation

Hi
Our requirement is while performing new hire action using PA40, at IT0002 screen after filling the details and on clicking save
IT0019 should automatically get filled and saved with the termination date(IT0002-gbdat + Yrs) and begin and end dates with that of 0002. How do we go about this. Help would be highly appreciated
Thanks in advance
rama raju

Hi Irfan,
1. Practically i have seen that it is not possible.
2. The systems gives the message
Person is already being used processed by user XXXX.
3. Whether we do online transaction, or BDC
or thru FM,
the system Locks the entry,
and the second time,
issued the above message.
Regards,
Amit M.
Message was edited by: Amit Mittal

Similar Messages

HCM process & Forms - Need logic to handle the Error's when Infotype Update

Hi Experts,
Currently im working with HCM process and forms workflow's. I have ten HCM workflow's and everything is working fine.
Now the issue is, at the time of save, if there is any error like infotype lock or any other Master data error's, then the standard task responsible for save the data, returns the Status as Error.
Already the approval process for the request is carried out, and it can not be make it again. So I need to save the data without re execution of the process or without re-approval.
I searched in standard workflow also. There is no option to handle the Infotype update Error's.
So can any one give me some hint about this? Without the re-initiation i need to save the data's.
Thanks for your time and Suggestions.

If you are using the framework to update specific infotypes and they are locked for "no apparent" reason you'll want to open an SAP message. I would highly discourage you from going down the path of calling that FM, from within workflow no less. Workflow in the framework was not intended to do such operations, this is supposed to be handled in the decoupled infotype framework (through configuration)... not to mention you won't be using the dec. infty framework by calling that function.
While I've had to do this before, it was because of a limitation in the framework not something as trivial as a locked infotype. Who knows, it might actually be locked for a legitimate reason?
Andy

Suggestion on infotype update

Hi All,
The requirement is: Create another infotype during some infotype creation. Two options I could think of are:
1. Create using BADI HRPAD00INFTY - But we should not commit inside badi to prevent incomplete data getting updated in database (from other update statements). So we could just call FM 'HR_INFOTYPE_OPERATION' and leave to the system to commit the changes.
2. Use Dynamic action.
My doubt is: Does dynamic action do the same thing what I just mentioned in point number one i.e. update without immediate commit.
Note: Only the FIRST CORRECT answer will fetch point :P
Thanks,
Bhaskar

HI,
According to my view Dynamic Action will work same as the FM HR_INFO_*. It will itself do the commit..

HR ABAP : Custom Infotype updations through FM HR_INFOTYPE_OPERATION

Hi All,
          Actually, I want to update the custom infotype 3 fields as per my user inputs. I am fetching the data from the PA table acoording to sy-datum falling in the begda, enda limitations. now I am changing the field with new values in the work area. And pass with the following data to the FM.
          But I am getting the error 'No data stored for 9008 in the selected period', eventhough it is already having a data in the database table. I had seen prvious therads, but could not get how they solved the issue.
Please provide the inpus for the following code.
          ( I had also passed the validity start and end from the database entry. at this moment it gets dumped at the statement
assign record to <record> casting type (tabname). "XDP UniCode
where tabname is proposed from t777d-ppnnn. which is a structure and having a value as P9008. If i change the value at debug point to PA9008. it works fine. is there anything extra i need to do to solve this issue? )
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '9008'
number = pernr
"SUBTYPE =
"OBJECTID =
"LOCKINDICATOR =
"VALIDITYEND =
"VALIDITYBEGIN =
"RECORDNUMBER =
record = wa_pa9008
operation = 'MOD'
"TCLAS = 'A'
"DIALOG_MODE = '0'
"NOCOMMIT =
"VIEW_IDENTIFIER =
"SECONDARY_RECORD =
IMPORTING
return = l_bapireturn
key = bapipakey_tab
Regards,
Brijesh Patel

Hi,
Check this code once
Read Infotype9004 Record for the personnel No
    CALL FUNCTION 'HR_READ_INFOTYPE'
      EXPORTING
        tclas           = A
        pernr           = pernr
        infty           = 9004
      IMPORTING
        subrc           = v_subrc
      TABLES
        infty_tab       = it_pa9004
      EXCEPTIONS
        infty_not_found = 1
        OTHERS          = 2.
Read it_pa9004 into wa_pa9004 with some condition.
if sy-subrc eq 0.
Lock the employee for processing infotype 9004
    CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
      EXPORTING
        number = wa_pa9004-pernr.
v_begda = wa_9004-begda.
      v_endda = wa_9004-endda.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = c_9004
          number        = wa_9004-pernr
          subtype       = c_0001
          validityend   = v_endda
          validitybegin = v_begda
          record        = wa_9004
          operation     = c_mod
          tclas         = c_a
         dialog_mode   = c_0
          dialog_mode   = '2'
        IMPORTING
          return        = wa_return.
CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
      EXPORTING
        number = wa_pa9004-pernr.
endif.
reward the points if it is helpful.
Regards,
Srilatha

HR ABAP : Custom Infotype updations

Hi All,
I am new to HR ABAP. Actually, I want to update the custom infotype 3 fields as per my user inputs. I am fetching the data from the PA table acoording to sy-datum falling in the begda, enda limitations. now I am changing the field with new values in the work area. And pass with the following data to the FM.
But I am getting the error 'No data stored for 9008 in the selected period'. I had seen prvious therads, but could not get how they solved the issue.
Please provide the inpus for the following code. I had also passed the validity start and end.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '9008'
number = pernr
SUBTYPE =
OBJECTID =
LOCKINDICATOR =
VALIDITYEND =
VALIDITYBEGIN =
RECORDNUMBER =
record = wa_pa9008
operation = 'MOD'
TCLAS = 'A'
DIALOG_MODE = '0'
NOCOMMIT =
VIEW_IDENTIFIER =
SECONDARY_RECORD =
IMPORTING
return = l_bapireturn
key = bapipakey_tab
Regards,
Brijesh Patel

Hi Remi,
        I have done the same thing. Please see the code. data is also available in the database. But the output is the error message. Please give some inputs on this.
***Updation of the PA9003 Infoty pe with the LTA amount and Medical Amount
    SELECT SINGLE endda
                  begda
                  FROM pa0001
                  INTO (endda, begda)
                  WHERE pernr EQ pernr
                    AND endda GE sy-datum
                    AND begda LE sy-datum.
    SELECT SINGLE *
                  FROM pa9003
                  INTO lwa_pa9003
                  WHERE pernr EQ pernr
                    AND endda >= sy-datum
                    AND begda <= sy-datum.
    wa_pa9003 = lwa_pa9003.
    wa_pa9003-zzallw = zzallw.
    wa_pa9003-zzlta = zzlta.
    wa_pa9003-zzmed = zzmed.
    ADD 1 TO wa_pa9003-seqnr.
***Locking the object
    CALL FUNCTION 'ENQUEUE_EPPRELE'
      EXPORTING
        pernr          = pernr
      EXCEPTIONS
        foreign_lock   = 1
        system_failure = 2
        OTHERS         = 3.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty                  = '9003'
        number                 = pernr
   subtype                = wa_pa9003-subty
   objectid               = wa_pa9003-objps
   lockindicator          = wa_pa9003-sprps
   validityend            = wa_pa9003-endda
   validitybegin          = wa_pa9003-begda
   recordnumber           = wa_pa9003-seqnr
        record                 = wa_pa9003
        operation              = 'MOD'
TCLAS                  = 'A'
DIALOG_MODE            = '0'
nocommit               = space
VIEW_IDENTIFIER        =
SECONDARY_RECORD       =
     IMPORTING
       return                 = l_bapireturn
       key                    = bapipakey_tab
***Unlocking the object
    CALL FUNCTION 'DEQUEUE_EPPRELE'
      EXPORTING
        pernr = pernr.
Regards,
Brijesh Patel

Infotype Updation In HR Module

Can anyone give me a code regarding
When an ALV Editable report is generated there should be Update button on the output screen. Once this button is clicked specific field values displayed on editable report should get updated in infotype.

dear u have to create Screen and Custom Control also
and put Button there
inthe PAI event u can create code for update infotype.
Rewards if useful.

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

Custom infotype updation

Hi Expects,
I am working on custom infotype creation. In my requirement I have used table control concept where user enters multiple records and updates the custom infotype.
For a single PERNR,SUBTYPE, BEGDA and ENDDA I want to update multiple records into the infotype using table control concept.
Ex: PERNR : 25
      SUBTY: 2001
      BEGDA: 01/01/2001
      ENDDA: 12/31/2001
Here by using the function modules 'HR_INFOTYPE_OPERATION' or 'HR_MAINTAIN_MASTERDATA' I am trying to update the custom infotype where sequence number need to be increamented automatically for duplicate entries but only one record is getting updated instead of multiple records.
I have maintained the time constraint as '3'.
Please let me know the procedure to update multiple records at a time into custom infotype.
Regards,
Mahesh.

Hi,
In the custom infotype table, if their are duplicate then the sequence number field value will be created automatically for time constainst '3' but using the function module it is not creating the sequence number but using the modify statement it is working fine.
Ex: Modify PA9002 from table GT_PA9002.
Please let me know the solution for updating multiple records into a custom infotype.
Regards,
Mahesh.

Log records for PA infotype updates

Hi folks,
I have a question related to the working of how the logs gets created when an infotype record is updated. Here is the scenario: I updated an action for an employee record in action infotype through PA40 and using an upload BDC program, the process took me through screens updating infotypes 0,1,2,7,8 and 19 to complete the action process.The changes are recorded in these tables. However when I checked to see the log records, a log record was created only for infotype 0. Also I did verify that all these infotypes are entered in V_t585A, V_t585b and v_t585C to create logs.
My question is: why the log records was not created for other infotypes inspite of defining these infotypes in the log maintainence tables? I am trying to understand this log creation process because most of our processes is directly dependant on it and poses problems .
Any kind of help is really appreciated.
Thanks in advance.
SK

It is a standard setting. The infotypes, their field groups and field group charcterstics are defined in V_T585A, V_T585B and V_T585C. I believe the end users are missing some process. Because it started to happen since a week or so. The same program was picking the records fine earlier and it has not changed.
I do not know what kind of process they follow. what changed now? Since I am the only SAP guy out here, got to find it out.
They are using PA30/PA40 to enroll and the web application. Both these records did not create the log data. The reocrds went through to SAP.
Could there be any step they might be missing?
Thanks for the quick reply,
SK

Help ! OM Infotype Update Error

We were trying to update the OM infotype using the RH_UPDATE_INFTY function module. But we are getting an exceptional error - 'ERROR DURING UPDATE'. Please help us on this.
The process which we used is.. Select the existing infotype record (IT 1029) and make modifications in some of the fields and pass the updated record to the FM.

Hi Radha,
Instead of going for RH_UPDATE_INFTY, you can go for the function module HR_INFOTYPE_OPERATION.
Before using this function module you need to LOCK using ENQUEUE_EPPRELE, so that no other person cannot make any changes to that infotype.
After the changes, you must UNLOCK the infotype using DEQUEUE_EPPRELE.
Sample:
CALL FUNCTION 'ENQUEUE_EPPRELE'
EXPORTING
pernr = wa_hrrecord-pernr
EXCEPTIONS
foreign_lock = 1
system_failure = 2
OTHERS = 3.
IF sy-subrc EQ 0.
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.
CALL FUNCTION 'DEQUEUE_EPPRELE'
EXPORTING
pernr = wa_hrrecord-pernr.
ENDIF.
ENDLOOP.
Regards,
Chandra Sekhar

WD ABAP - HR infotype update

Hi,
I need to develop some custom applications using WDA in ESS for displaying and updating the employee;s infotype records (IT0581, IT0591) and I am new to WD ABAP.
I have completed the beginners tutorials available in sdn and planning to use service call functionality available with WD ABAP in order to display and uppdate infotype records. For this, we are developing some custom RFC;s display data of IT0581, IT0591. Can anybody guide me how to do this ?
Is there any documentation available for same ? What are the best practises or approaches to keep in mind while developing the content for ESS using WDA?
Regards,
Anil Kumar

Hi Buddy
   You are wrongly passing the parameters. Pass the parameters like this
data : ls_pa0006 TYPE pa0006.
data : ls_p0006 TYPE p0006.
DATA : IT_PA0006 TYPE PA0006 OCCURS 0 WITH HEADER LIN
DATA : RETURN LIKE BAPIRETURN1.
DATA : ERROR_TAB LIKE RETURN OCCURS 0 .
SELECT * FROM PA0006 INTO CORRESPONDING FIELDS OF TABLE IT_PA0006
WHERE ENDDA = '99991231' AND PERNR = PERNR .
SORT IT_PA0006 BY SUBTY.
LOOP AT IT_PA0006.
IF IT_PA0006-SUBTY = '1' .
move-corresponding it_pa0006 to ls_pa0006.
ls_pa0006-name2 = co.
ls_pa0006-stras = STREET1.
ls_pa0006-LOCAT = STREET2.
ls_pa0006-PSTLZ = POSTALCODE.
ls_pa0006-ORT01 = CITY.
ls_pa0006-ORT02 = REGION.
ls_pa0006-TELNR = TELEPHONENUMBER.
move-corresponding ls_pa0006 to ls_p0006.
ls_P0006-INFTY = '0006'.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    INFTY                       = '0006'
    NUMBER                   = PERNR
    SUBTYPE                  = '1'
    VALIDITYEND           = IT_PA0006-ENDDA
    VALIDITYBEGIN        = IT_PA0006-BEGDA
    RECORD                   = ls_p0006
    OPERATION              = 'MOD'
   TCLAS                      = 'A'
IMPORTING
   RETURN                   = RETURN.
I think OPERATION = DIS will not be the correct here. Change operation to insert that is correct. Cehck this code it will work.
Regards
vijay

HR Infotype Update

Hello,
In WDA, I am trying to update an infotype i.e. 0021.
I have made a call to the FM HR_INFOTYPE_OPERATION.
Now I get an error in the function module that the record that I am trying to access does not exist, although it is there.
This particularly happens when I use the operation mode as 'MOD'.
When I use operation mode as 'INS', it goes and updates the record.
So if the operation mode is 'INS' then it should insert a record rather than updating.
Happy Coding,
Rahul

Hello Thomas,
Is there any standard documentation on this particular FM that I can read.
I have been trying to search but could not find one.
Happy Coding,
Rahul

Infotypes Update

Hi experts,
Im new to HR ABAP. I need to update the Infotype address 0006 particularly Sub type 003.
Can any body help me regarding this.
Any links documents are more welcome.
Thanks,
helps will be appreciated.

Hi,
Please check the following link for enhancing the SAP standard Infotypes
http://help.sap.com/saphelp_erp2005vp/helpdata/en/4f/d526be575e11d189270000e8322f96/content.htm
Regards,
Aditi

Infotype Update gives error

Hi,
I tried to update infotype 0000 with HR_INFOTYPE_OPERATION.
It gave me a error with name ASSIGN_BASE_TOO_SHORT
Following is the error analysis.
Pls guide me.
Error analysis
    The source field is too short.
    In the running program "SAPLHRMM" a field should have been assigned to a field
    symbol, which is shorter than the type of the field symbol.
    This is not possible.
    It is a statement of the form ASSIGN f TO <fs> CASTING...
    or ASSIGN f TO <fs> with a field symbol that was created with the
    STRUCTURE addition.
I have called my FM like this.
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = WA_p0000-pernr.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          INFTY                  = '0000'
          NUMBER                 = WA_P0000-PERNR
*   SUBTYPE                =
*   OBJECTID               =
*   LOCKINDICATOR          =
         VALIDITYEND            = P0000-endda
         VALIDITYBEGIN          = p0000-BEGDA
*   RECORDNUMBER           =
          RECORD                 = WA_P0000
          OPERATION              = 'MOD'
         TCLAS                  = 'A'
         DIALOG_MODE            = '0'
*   NOCOMMIT               =
*   VIEW_IDENTIFIER        =
*   SECONDARY_RECORD       =
       IMPORTING
         RETURN                 = w_return
*   KEY                    =
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
        EXPORTING
          number = WA_p0000-pernr.
TIA.

Hi ,
I am also using the same function module and it is giving me the same dump can you let me know how did you solved the problem.
Error in ASSIGN in the program "SAPLHRMM".
Regards,
Manohar

Infotype update on claim request status

Hi,
I have one scenario where I have to update a z infotype on & every processing status for claim request. The processing status gets changes on creation & approval process through workflow. I am using the standard workflow for claim & reimbursement & implement the BADI to get the approval level. I have three levels of approval level.
Is there any way to update IT through the same BADI or another BADI "HRPBSIN_COMPLETE_UPDATE". Pl. give suggestion.
Thanks,
Snita Shaw

Hi,
You can use the badi HRPBSIN_NEXT_APPROVER to update the custom infotype.
Ex. If you want to save some fields of custom infotype when the employee applies, check the "Approver Level = 1."
If you want to save some fields when 1st level manager approves " Approver Level = 2."
Based on these "Approver Level" you can create and change the custom infotype.
Regards,
Jyothi

Write Direct INFOTYPE updates to PCL4 cluster

Hi All,
We have a custom info type (9999) and that info type is being updated in a back ground program which does direct updates (Insert/Modify/Delete) to table PA9999.
We have a requirement to show change logs for this info type. After Change logs configuration, Changes done by users are working fine. However changes done in background program are not showing up in change logs.
Is there a way to write direct updates to PCL4 cluster? Please let me know if there are any Function Modules or any other way to achieve this.
Thanks,
Swapna.

Hi Swapna,
Please do not use direct updates on the infotype,
There is HR_INFOTYPE_OPERATION function module which will do the updation of infotype in many operations
MOD, INS, LIS9, DEL etc.
Read the documentation and correspondingly use it. Dont forget to lock and unlock employee before using this function moduel.
If you use these function modules rather than direct updates the change log will also be taken care of, authroization checks would be taken care of, time constraints etc.
Regards,
Divya

Infotype updation

Similar Messages

Maybe you are looking for