Hide records of Tranining Histroy in Custom infotype

My client is maintaing Training History in a customzed infotype. There are few records which has a end date, and client want to hide these recrods in overview mode.
Is it possible to hide these records at infotype level, or is there any better option to this.
Thanks in advance
GB

It can be customized in the infotype attributes (T582A).
If this does not meet you requirements, you can do it in the PBO Module for screen 3000.

Similar Messages

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

  • Error while editing an automaticlly populated record of  a custom infotype

    hi,
    a query in HR ABAP.
    i have created a custom Infotype to store the CTC details of an employee. this custom IT needs to get the records auto populated, when they are created in Infotype 0008.
    i have used the exit. EXIT_SAPFP50M_002  inside which  an include program is written  :ZXPADU02
    using this, the records made to get create automatically in the custom IT.
    but when we try to modify or delete those records thru the tcode PA30,
    it does not allow to do so and throws a standard error message. as  below.
    Specified subtype is invalid
    Message no. PG088
    please help me out to fix this issue.

    the exact point of the std error is,
    i do the folowing steps.
    1)_ for auto creating a record in custom IT Pa**** , i goto transaction, PA30, create record in IT 0008 with a basic Pay., click on save.
    on saving , the EXIT_SAPFP50M_002 is called where i ve written a Z inlcude Program, which inserts the record in custom IT PA****.  this is successful.
    2) when i try to change or delete the same record which i ve created as above, through the Tcode PA30 for custom IT, PA
    ****, i get the error.
    hope the problem is clearly mentioned

  • Creating / Updating Custom Infotype Records

    Hello everbody,
    We implement alot of custom HR infotypes in our system, both PA &  HRP.
    For the past several we have been using BDC (Batch-Input) recorded functions in order to update / create the records in our infotypes.
    We're currently facing an upcoming ECC upgrade , and I would like to lead a change that will eventually lead to us using generic SAP supplied functions.
    I've researched a few functions that might do the trick:
    RH_INSERT_INFTY:
    This one is giving me an SY-SUBRC 2 error code - Insert error, I tried to select a current record and insert it as different objid but this doesnt work.
    HR_INFOTYPE_OPERATION:
    I've read of several people that recommended using this function, but it is not released by SAP and I couldnt get it to work as well.
    BAPI_HRMASTER_SAVE_REPL_MULT:
    This one seems to work for sap infotypes but I dont think it suits custom infotypes.
    What is the "official" way of doing such operations?
    thanks in advance,
    Eli.

    Hello Dilak,
    Im currently trying to insert a new infotype record of infotype HRP9226.
    First I call function RH_GET_NEXT_NUMBER to get an objid.
    then I fill an HRP9226 line.
    after this i call the function:
    call function 'RH_INSERT_INFTY'
    exporting
    FCODE = 'INSE'
    vtask = 'S'
    ORDER_FLG = 'X'
    COMMIT_FLG = 'X'
    AUTHY = ' '
    PPPAR_IMP =
    OLD_TABNR = ' '
    REPID = ' '
    FORM = ' '
    KEEP_LUPD =
    WORKF_ACTV = 'X'
    tables
    innnn = hrp9226_line
    ILFCODE =
    EXCEPTIONS
    NO_AUTHORIZATION = 1
    ERROR_DURING_INSERT = 2
    REPID_FORM_INITIAL = 3
    CORR_EXIT = 4
    BEGDA_GREATER_ENDDA = 5
    OTHERS = 6
    I'm getting an "Error_During_Insert" and Im out of options regarding what I can possibly do.

  • Custom Infotype not displaying locked records in the list screen (3000)

    I have a custom infotype (9xxx) that will not display the locked records (locked indicator (sprps) is set to X) in the list screen (3000) in PA20 and PA30.
    Any ideas on what may be causing the records to not display in the list screen?
    Thanks,
    Ted

    Hi,
    for creating both employee and appliciant infotype you must check 'Both'  in PM01  IT tab.
    Regards.

  • Record not appearing in custom infotype without selecting the period.

    Hi All,
    I have created a HR Custom Infotype for Medical Examination. Whenever i create a record for a particular employee and again i click on the Display button for the same employee, a message is diplayed "No data stored for Medical Examination details in the selected period". And when i select the ALL radio-button in the period selection area,only then the record is displayed. Why is it so that manually i need to select the ALL radiobutton to display the record? It is not so for other infotypes. Is there any solution for this, i mean can we change some settings to resolve this issue?
    Thanks in advance,
    Arpita Raizada.

    In PA20/30 we have period from and to dates on screen. If any date is entered on these screens then data from infotype is displayed based on these dates.
    If your record doesn't overlap/falls with these entered dates then system displays the message. Changes the period dates accordingly and system will display the records valid as of entered date.
    Regards,
    Ramnivas

  • About to use HR_INFOTYPE_OPERATION to create customer infotype issue:

    hi
    i want to create infotype use function(HR_INFOTYPE_OPERATION).
    this infotype is customer infotype.
    the first scenario is:
      i'm be sure no data about one employee in this infotype(9004).
      to call with data upload function and put data into internal table IT_PA9004.
      and the table data as follow:
    one line: it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080201' , it_pa9004-endda = '20080930'
              it_pa9004-zzvalue = 50 (customer field).
    two line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080201' , it_pa9004-endda = '20080930'
              it_pa9004-zzvalue = 60 (customer field).
    three line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080101' , it_pa9004-endda = '20081031'
              it_pa9004-zzvalue = 70 (customer field).
    four line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080101' , it_pa9004-endda = '20081031'
              it_pa9004-zzvalue = 80 (customer field).
    i run the programme and get information is:
    11022887 insert ok.
    11022887 insert ok.
    11022887 insert ok.
    11022887 insert ok.
    but i use the transation PA30 to view all data:
    in database just exist one row:
    four line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080101' , it_pa9004-endda = '20081031'
              it_pa9004-zzvalue = 80 (customer field).
    the second scenario is:
    in database the infotype have exist one row:
               pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ02',
               pa9004-begda = '20080318' , pa9004-endda = '20080318'
               pa9004-zzvalue = X (customer field).
    and i create another row:
    line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ02',
              it_pa9004-begda = '20080318' , it_pa9004-endda = '99991231'
              it_pa9004-zzvalue = 80 (customer field)
    i run the programme and get information is:
    11022887 insert ok.
    the three scenario is:
        set  HR_INFOTYPE_OPERATION of import parameter operation = 'MOD'
        in any scenario will get error :not exist subtype .
    what heppend about HR_INFOTYPE_OPERATION working,i had to use this function to
       create other infotype of SAP owner.
       and will create successfully.
    so i thank it may be config Constraints about customer infotype.
    is time Constraints effect?
    so i want to how to check it?
    and if i want to create one infotype for customer using PM01 what some thing
    must be taken into account.
    think you advance.
    partial source code as follow:
    FORM ACTION_INSERT .
      DATA: P_FLAG TYPE C.
      DATA: WA_LOG LIKE LINE OF DATA_LOG.
      DATA: PP_ACTION TYPE PSPAR-ACTIO.
      LOOP AT IT_PA9004.
        CLEAR P_FLAG.
        CALL FUNCTION 'HR_PSBUFFER_INITIALIZE'.
        PERFORM lock_employee USING IT_PA9004-pernr CHANGING P_FLAG.
        PP_ACTION = IT_PA9004-ACTION.
        PERFORM HR_INFOTYPE_OPERATION USING IT_PA9004 PP_ACTION CHANGING P_FLAG.
        IF P_FLAG IS INITIAL.
          if test_run = space.
            COMMIT WORK.
          else.
            ROLLBACK WORK.
          endif.
          write:/ it_pa9004-pernr,'insert ok'.
        ELSE.
          ROLLBACK WORK.
          write:/ it_pa9004-pernr,'error'.
        ENDIF.
        PERFORM unlock_employee USING IT_PA9004-pernr .
      ENDLOOP.
    ENDFORM.                    " ACTION_INSERT
    FORM LOCK_EMPLOYEE  USING    P_PERNR
                        CHANGING PP_FLAG.
      CHECK PP_FLAG IS INITIAL.
      CLEAR P_RETURN.
      CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = P_PERNR
        IMPORTING
          return = P_RETURN
        EXCEPTIONS
          OTHERS = 01.
      CALL FUNCTION 'HR_INITIALIZE_BUFFER'
        EXPORTING
          pernr = P_PERNR.
      IF P_RETURN IS NOT INITIAL.
        PP_FLAG = '1'.
      ENDIF.
    ENDFORM.                    " LOCK_EMPLOYEE
    FORM HR_INFOTYPE_OPERATION  USING    P_PA9004 LIKE IT_PA9004
                                         P_ACTION type PSPAR-ACTIO
                                CHANGING PP_FLAG.
      CHECK PP_FLAG  IS INITIAL.
      DATA: bapipakey type bapipakey,
            P_SUBTY TYPE P9004-SUBTY,
            PP_9004 TYPE TABLE OF  P9004 WITH HEADER LINE.
      CLEAR P_RETURN.
      REFRESH PP_9004.
      MOVE-CORRESPONDING P_PA9004 TO PP_9004.
      IF P_ACTION = 'INS'.
        PP_9004-AEDTM = SY-DATUM.
        PP_9004-UNAME = SY-UNAME.
      ENDIF.
      IF P_ACTION = 'MOD'.
        PP_9004-AEDTM = SY-DATUM.
        PP_9004-UNAME = SY-UNAME.
      ENDIF.
      APPEND PP_9004.
      P_SUBTY = P_LGART.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '9004'
         subtype       = 'FQ03'
          subtype       = P_SUBTY
          number        = PP_9004-pernr
          validityend   = PP_9004-ENDDA
          validitybegin = PP_9004-begda
         RECORDNUMBER  = pp_9004-seqnr
          record        = PP_9004
           operation     = 'INS'
         operation     = P_ACTION
          nocommit      = 'X'
        IMPORTING
          return        = P_RETURN
          key           = bapipakey
        EXCEPTIONS
          OTHERS        = 0.
      IF P_RETURN IS NOT INITIAL.
        PP_FLAG = '9'.
      ENDIF.
    ENDFORM.                    " HR_INFOTYPE_OPERATION
    FORM UNLOCK_EMPLOYEE  USING    P_PERNR.
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
        EXPORTING
          number = p_pernr
        IMPORTING
          return = P_RETURN
        EXCEPTIONS
          OTHERS = 01.
    ENDFORM.                    " UNLOCK_EMPLOYEE

    hi
    i want to create infotype use function(HR_INFOTYPE_OPERATION).
    this infotype is customer infotype.
    the first scenario is:
      i'm be sure no data about one employee in this infotype(9004).
      to call with data upload function and put data into internal table IT_PA9004.
      and the table data as follow:
    one line: it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080201' , it_pa9004-endda = '20080930'
              it_pa9004-zzvalue = 50 (customer field).
    two line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080201' , it_pa9004-endda = '20080930'
              it_pa9004-zzvalue = 60 (customer field).
    three line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080101' , it_pa9004-endda = '20081031'
              it_pa9004-zzvalue = 70 (customer field).
    four line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080101' , it_pa9004-endda = '20081031'
              it_pa9004-zzvalue = 80 (customer field).
    i run the programme and get information is:
    11022887 insert ok.
    11022887 insert ok.
    11022887 insert ok.
    11022887 insert ok.
    but i use the transation PA30 to view all data:
    in database just exist one row:
    four line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ03',
              it_pa9004-begda = '20080101' , it_pa9004-endda = '20081031'
              it_pa9004-zzvalue = 80 (customer field).
    the second scenario is:
    in database the infotype have exist one row:
               pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ02',
               pa9004-begda = '20080318' , pa9004-endda = '20080318'
               pa9004-zzvalue = X (customer field).
    and i create another row:
    line:it_pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ02',
              it_pa9004-begda = '20080318' , it_pa9004-endda = '99991231'
              it_pa9004-zzvalue = 80 (customer field)
    i run the programme and get information is:
    11022887 insert ok.
    but in database just exist the first data
               pa9004-pernr = '11022887' ,it_pa9004-subty = 'FQ02',
               pa9004-begda = '20080318' , pa9004-endda = '20080318'
               pa9004-zzvalue = X (customer field).
    the three scenario is:
        set  HR_INFOTYPE_OPERATION of import parameter operation = 'MOD'
        in any scenario will get error :not exist subtype .
    what heppend about HR_INFOTYPE_OPERATION working,i had to use this function to
       create other infotype of SAP owner.
       and will create successfully.
    so i thank it may be config Constraints about customer infotype.
    is time Constraints effect?
    so i want to how to check it?
    and if i want to create one infotype for customer using PM01 what some thing
    must be taken into account.
    think you advance.
    partial source code as follow:
    FORM ACTION_INSERT .
      DATA: P_FLAG TYPE C.
      DATA: WA_LOG LIKE LINE OF DATA_LOG.
      DATA: PP_ACTION TYPE PSPAR-ACTIO.
      LOOP AT IT_PA9004.
        CLEAR P_FLAG.
        CALL FUNCTION 'HR_PSBUFFER_INITIALIZE'.
        PERFORM lock_employee USING IT_PA9004-pernr CHANGING P_FLAG.
        PP_ACTION = IT_PA9004-ACTION.
        PERFORM HR_INFOTYPE_OPERATION USING IT_PA9004 PP_ACTION CHANGING P_FLAG.
        IF P_FLAG IS INITIAL.
          if test_run = space.
            COMMIT WORK.
          else.
            ROLLBACK WORK.
          endif.
          write:/ it_pa9004-pernr,'insert ok'.
        ELSE.
          ROLLBACK WORK.
          write:/ it_pa9004-pernr,'error'.
        ENDIF.
        PERFORM unlock_employee USING IT_PA9004-pernr .
      ENDLOOP.
    ENDFORM.                    " ACTION_INSERT
    FORM LOCK_EMPLOYEE  USING    P_PERNR
                        CHANGING PP_FLAG.
      CHECK PP_FLAG IS INITIAL.
      CLEAR P_RETURN.
      CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = P_PERNR
        IMPORTING
          return = P_RETURN
        EXCEPTIONS
          OTHERS = 01.
      CALL FUNCTION 'HR_INITIALIZE_BUFFER'
        EXPORTING
          pernr = P_PERNR.
      IF P_RETURN IS NOT INITIAL.
        PP_FLAG = '1'.
      ENDIF.
    ENDFORM.                    " LOCK_EMPLOYEE
    FORM HR_INFOTYPE_OPERATION  USING    P_PA9004 LIKE IT_PA9004
                                         P_ACTION type PSPAR-ACTIO
                                CHANGING PP_FLAG.
      CHECK PP_FLAG  IS INITIAL.
      DATA: bapipakey type bapipakey,
            P_SUBTY TYPE P9004-SUBTY,
            PP_9004 TYPE TABLE OF  P9004 WITH HEADER LINE.
      CLEAR P_RETURN.
      REFRESH PP_9004.
      MOVE-CORRESPONDING P_PA9004 TO PP_9004.
      IF P_ACTION = 'INS'.
        PP_9004-AEDTM = SY-DATUM.
        PP_9004-UNAME = SY-UNAME.
      ENDIF.
      IF P_ACTION = 'MOD'.
        PP_9004-AEDTM = SY-DATUM.
        PP_9004-UNAME = SY-UNAME.
      ENDIF.
      APPEND PP_9004.
      P_SUBTY = P_LGART.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '9004'
         subtype       = 'FQ03'
          subtype       = P_SUBTY
          number        = PP_9004-pernr
          validityend   = PP_9004-ENDDA
          validitybegin = PP_9004-begda
         RECORDNUMBER  = pp_9004-seqnr
          record        = PP_9004
           operation     = 'INS'
         operation     = P_ACTION
          nocommit      = 'X'
        IMPORTING
          return        = P_RETURN
          key           = bapipakey
        EXCEPTIONS
          OTHERS        = 0.
      IF P_RETURN IS NOT INITIAL.
        PP_FLAG = '9'.
      ENDIF.
    ENDFORM.                    " HR_INFOTYPE_OPERATION
    FORM UNLOCK_EMPLOYEE  USING    P_PERNR.
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
        EXPORTING
          number = p_pernr
        IMPORTING
          return = P_RETURN
        EXCEPTIONS
          OTHERS = 01.
    ENDFORM.                    " UNLOCK_EMPLOYEE

  • Need to create maintenance view for a custom infotype

    A custom infotype 90XX is created. The data cannot be modified or created through PA30 in this infotype. Through PA 40 actions only we can create/change the record/data. We have created some 1000 records in it. Now can we create a maintenance view for the infotype so that we can create, delete or change the data in the infotype as and when we want.

    Hi,
    pls chk dat u have maintained the 'Infotype Charecteristics' and 'Technical Attributes' correctly.
    thanks,
    teja.

  • Custom infotype creation issue

    Hi Experts,
    I have a requirement to create a custom infotype based on certain conditions. But there is a problem while saving data in the infotype. The infotype is populated from another infotype automatically through dynamic actions.
    But while saving the data for the first time it happens as per the requirements and data gets saved properly.
    But when the data is saved for the second time for the same pernr , the previous data is over written even though the new record starts with a different begin data.Also i have created the infotype with time constraint '1'.
    can you please let me know if i am missing anything while creating or is this a logic issue .? all the logic has been coded in the flow logic part of the screen.
    also if i dont save the data in the infotype it does not pop up any message like 'data not saved' which usually happens with every infotype. Please clarify me on this as well...
    Thanks,
    Raj Thilak.

    Hi,
    Check the logic how it is updating the custom infotype . I think it is nothing to do with creation of custom info type
    Regards
    Krishna

  • Custom Infotype length limitation

    Hi,
    I have a requirement to create a custom infotype in ECC 6.0 with a table control which can have a maximum of 50 line items. Something similar to basic pay infotype and PA0008. While going through the SAP documentation I found the below statement .
    "A new infotype is limited to a maximum of 1000 positions. This restriction is due of the length of structure PRELP, which is used as a container during infotype processing."
    This is available at
    http://help.sap.com/saphelp_erp60/helpdata/en/60/d8d8c7576311d189270000e8322f96/frameset.htm
    In our implementation, each record of standard table PA0008 could go upto 1200 characters with a maximum of 40 line items in the table control. We never used more than 5 line items and never had any problem.
    Since the custom table control can have upto 50 line items, each record of my custom table pa9xxxx could go upto 4000 characters and I'm concerned that if this is going to be an issue. Any suggestions in this regard please ?
    Thanks for your time,
    Kumar.

    Hi Venkata
    Please see notes 563145 and 1168062 for help
    Please also be aware that custom infotypes and the effects of changing structures are the customers responsibility
    Best wishes
    Stuart

  • Change Pointers not being created for HR-PA Custom Infotype

    Problem Description:
    We have a custom Infotype in SAP to store the data for contingent employee - Infotype 9001. Change pointers is
    turned on. We are running the program RBDMIDOC to send changes to Oracle IDM using message HRMD_A. The change
    detected for all infotypes except 9001. For 9001, the change pointer is not created.
    The following are the current configuration details:
    IDOC Extension Created to Idoc type HRMD_A07 (ZHR_EXT)
    custom segment zhr_seg
    Change pointers are switched on.
    Change pointers switched on for message Type HRMD_A.
    IDOC configuration created for Port / Process code etc.
    Maintenance of view T777D - Added ZHR_SEG.
         If I add the segment ZHR_SEG as a 2nd segment to Infotype 0000, I dont get a syntax error. But the changes for Infotype 9001 are not picked up.
         If I add the segment ZHR_SEG as a segment to Infotype 9001, I get a syntax error - check EDI: Syntax error in IDoc (mandatory segment missing) below.
    EDI: Syntax error in IDoc (mandatory segment missing)
    Message no. E0072
    Diagnosis
    The segment ZHR9001 has the attribute 'Mandatory' in the syntax description of the basic type HRMD_A07 (customer enhancement ZHR_EXT). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
    This error may have been triggered by an unidentifiable segment before the expected mandatory segment.
    Procedure
    Please check the IDoc or the syntax description of the basic type HRMD_A07 (customer enhancement ZHR_EXT).

    Were you able to resolve the issue?
    If yes, could you please share what was done to resolve it.
    Your help will be greatly appreciated.

  • Regarding Custom infotype 9006 data maintanance

    Hi,
    There was an error showing while creating a record for custom infotype "9006" .
    This infotype cannot be maintained directly
    Message no. PG170
    Diagnosis
    You cannot maintain this infotype directly.
    Like the Archived Objects infotype (0283), it can only be maintained by the system, and not manually.
    System Response
    Manual maintenance is not permitted.

    It seems to me as some custom code is causing this error message. Can you get an ABAPPER to debug and check where this error message is being issued?
    IT 9006 is a custom infotype, therefore either the message is appearing because the infotype has been copied from a standard infotype such as 0283, or this error message has been deliberately introduced by the infotype creator.
    Atleast I could not find any table where this attribute is maintained.

  • Creation of custom infotype

    Hi all,
    I have a requirement wherein i need to create a infotype.
    In this infotype if the Anzhl value of absence quota type  is reduced the relavent quota types which are linked to it should also get reduced.
    Actually when a leave is approved, the quota is reduced and reflected in 2006 only but here in my case it should get reflected in the new infotype also by creating a seperate record with the entitlement and reduced values.
    for ex awart1
    suppose for 20 days is reduced from awart1. Awart2 and awart3 are linked to awart1.
    simultaneously 20 days quota needs to be reduced from awart2 quota, as well as some 5 days from awart3.
    so there will be two records of this new infotype
    and also, the ANZHL of the relevant quotas will be reduced
    when the leave gets cancelled, these two records will be deleted and quota will be reinstated back
    Please help me by providing pointers in this regard.
    Thanks in advance.
    Regards,
    Durga.

    Hi
    use the  t-code  PM01  to create new custom infotype..i wiht in 9000-9999 number range..
    Have a search on SDN  for the same..............therea re lots of  thered for the same...
    ..lakhan

  • Validation Issue in Custom Infotype

    I have Copied an Infotype from 0582 . so it created an custom database table PA9***. After final completion  during testing the user are creating the records and saved and it is working fine till now. The Problem is when users try to change the same Record that is just created , the information is not getting updated , the system also gives an information message 'No Changes Found' inspite of obvious changes. I Verified the information from both data base table and end user screen, it is not getting updated in neither of the Places. Please Help. any Further Information needed ask Me.

    Hi Shanthi,
    I am having the same problem.
    I had created a custom infotype ,But when I try to view it through PA30 in Display mode.
    the fields are still enabled.
    Whereas , in create mode, its working fine.
    Please guide me the steps to disable the fields in Display mode in PA30.
    Thanks
    Kanupriya.

  • 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

Maybe you are looking for

  • HT1203 Using the same Apple ID for more than one ipod.

    I am soon going to be purchasing a new ipod, so i was wondering if i can use my previous apple ID for my new ipod or if i have to create new apple ID and make a new itunes on my computer? (using windows)

  • Many to many relationship does not work on certain role played dimension

    Hi, I have a cube with role playing Account dimension, used once as "Account" and once as "Other Account" dimension. I've added Trip dimension related to the account dimension by a bridge table AccountTrip  making a many to many relationship (many ac

  • Facebook Contacts Profile Pics not updating on Incredible

    Just like the title says - after syncing everything with facebook to my current contacts (people) list, the current facebook display picture appears.  However, if one of my contacts changes their facebook display picture - it won't change in the cont

  • Encoding in AC3 (A.Pack)..miss some sound

    Hello, I have a problem with a movie i encode for a DVD. The movie begin with no sound, and around one minute begin but with "white noise" (in fact background noise). When i encode the aif files in AC3 this background noise disappear (in fact the sou

  • Yosemite and Gmail

    Since upgrading to Yosemite on my MacBook Pro w/retina I keep having issues with mail headers.  My incoming emails are showing with the "From" field showing a different name than that of the sender as well as a different email than would be correct f