HR ABAP: Infotype 25 updation

In my server table PA0025 is empty.....even i entered data (annual aprrisal ) for infotype 25 and save then also the table PA0025 is not updated.....!!
Can anybody explain me why its behave like this??? and also
<b>How to update the table PA0025 table?????</b>
Waiting for ur rply...
Thanks,
Biswajit

Hi Biswajit..
Go to HRP1001 and enter the following:
OTYPE = P
OBJID = < The Personnel Number u have created the appraisal for>
PLVAR = current plan (01)
SOBID =  Thsi field will have a unique number that determines the appraisal u have created.
The same SOBID can be seen in PA30 appraisal screen under the following menu options:
View --> Key On
Cheers
Shakir

Similar Messages

  • How to create the sub type field in hr abap infotype

    hi ,
        how to create the sub type field in hr abap infotype.
    regards,
    venkat.

    Try like this also
    creating of infotype please follow these steps ...
    Step 1: Create Infotypes
    i. Goto Transaction PM01 – To create Infotypes:
    ii. Enter the Infotype Number and say create all.
    iii. The following message would display:
    i. PSnnnn Does not exist. How do you want to proceed?
    iv. Click
    v. A maintain Structure screen appears.
    Fill in the short text description and the PS structure of the Infotype.
    Since the fields Personnel No, Employee Begin Date, End Date, Sequential Number,Date of Last Change, Name of user who changed the object are available in the PAKEY and PSHD1 structure, define the PSnnnn structure with only the fields you required.
    vi. Once the PS Structure is created, save and activate the structure.
    vii. In the initial screen of PM01, now click on .
    Create a new entry for the infotype.
    Fill in the values as mentioned below and save.
    Infotype Characteristics:
    Infotype Name of the infotype_ Short Text: __Short Description________
    *General Attributes :
    Time constraint = 1
    Check Subtype Obligatory
    Display and Selection:
    Select w/ start = 3 “Valid record for entered data
    Select w/ end = 5 “Records with valid dates within the period entered
    Select w/o date = 6 “Read all records
    Screen header = 02 “Header ID
    Create w/o end = 1 “Default value is 31.12.9999
    Technical Data:
    Single screen = 2000
    List screen = 3000; List Entry Checked.
    viii. In the initial screen of PM01, now click on .
    Choose the infotype entry in the list.
    Fill in the values as mentioned below and save.
    Technical Attributes:
    In tab section,
    The following attribute values are given:
    Applicant DB Tab = PAnnnn “Infotype Name
    Subtype field = SUBTY
    Subtype table = T591A
    Subty.text tab. = T591S
    Time cnstr.tab. = T591A
    Prim. /Sec. = I Infotype
    Period/key date = I Interval
    and .
    ix. Infotype Screen Modification:
    Edit Screen 2000 from PM01 for the Infotype.
    ABAP Editor for the Infotype Program MPnnnn00 will be displayed.
    Click . Flow Logic will be displayed. There string coding of your own logic.
    Regards
    Pavan

  • 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

  • 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

  • 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 abap custom infotype  updatation

    hiii frnds,
        i creatred custom inotype 9910 and i enterded some data for  this infotype in pa30 when i click on the save it is noty saving in the pa9910 table...... can any one send sample code to save the data into table

    Did you read [Developing an Infotype in Personnel Administration|http://help.sap.com/printdocu/core/print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf] (or more recent documentation) and a guide like [Steps to Customize infotypes|http://wiki.sdn.sap.com/wiki/display/ABAP/StepstoCustomize+infotypes]
    Regards,
    Raymond

  • 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

  • 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

  • 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

  • HR-ABAP-Infotypes concept

    Hi Masters,
                           Can you please let me know the perfect reason for infotypes concept in HR-ABAP.
    1 Why we are using infotypes and exactly what is purpose?
    2.Why we are using LDB's why cannot we extract data directly from database tables?
    3.Can you please give me clear explanations about these infotypes.

    Hi
    Infotype(s) are used in the Personnel Management (PA) module primarily. This is where personnel master data is stored. Data is grouped according to subject matter. The Human Resources component aims to enable the user to process employee data in an effective structure in accordance with business requirements. The data structure of infotypes mirrors a logical set of data records. Infotypes can be identified by their four-digit keys, for example, the Addresses infotype (0006). To facilitate reporting on past employee data, infotypes can be saved for specific periods.
    Some people use the term HR ABAP to describe the method of managing the infotype data. Typically HR logical databases are used which offers more secure methods of accessing the infotype data. Once the infotypes are declared, you can use standard macros to access the data. Table TRMAC holds the macro name and the code behind it. This makes developing HR programs much quicker and easy to turn around.
    HR uses INFOTYPES instead of tables.
    There are different sub modules exist in HR.
    For Personal Admn the Infotypes start with PA0000 to PA1999
    Time Related Infotypes start with PA2000 to PA2999.
    Orgn related Infotypes start with HRP1000 to HRP1999.
    All custom developed infotypes stsrat with PA9000 onwards.
    In payroll processing we use Clusters like PCL1,2,3 and 4.
    Instead of Select query we use PROVIDE and ENDPROVIDE..
    You have to assign a Logical Database in the attributes PNP.
    Go through the SAp doc for HR programming and start doing.
    http://www.sapdevelopment.co.uk/hr/hrhome.htm
    See:
    http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/bb/bdb041575911d189240000e8323d3a/frameset.htm
    see this link you would get information about types of infotypes
    Logical databases are special ABAP programs that retrieve data and make it available toapplication programs. The most common use of logical databases is still to read data fromdatabase tables by linkin them to executable ABAP programs.
    Logical databases contain Open SQL statements that read data from the database.You do not therefore need to use SQL in your own programs. The logical database reads theprogram, stores them in the program if necessary, and then passes them line by line to theapplication program or the function module LDB_PROCESS using an interface work area .
    For further info
    check link http://help.sap.com/saphelp_nw70/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm
    1. A logical database is in fact
    a program only.
    2. This LDB provides two main things :
    a) a pre-defined selection screen
    which handles all user inputs and validations
    b) pre defined set of data
    based upon the user selection.
    3. So we dont have to worry about from
    which tables to fetch data.
    4. Moreover, this LDB Program,
    handles all user-authorisations
    and is efficient in all respects.
    5. tcode is SLDB.
    /people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases
    <b>REward fi suefull</b>

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

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

  • 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

Maybe you are looking for