Regarding ldb pnpce and my customized infotype

i have created my own infotype name '9777' and with the help of
'hr_infotype_operation' i m inserting the data into this infotype
now i m creating a report in which i m using ldb pnpce,
but after the execution of GET PERAS the infotype table p9777
is not populating but except this other infotypes tables are populating
,plz help me to sort out this problem.

hi after the bapi did you used the commit .
use this for the creation of an employee
BAPI_EMPLCOMM_CREATE
o give  your code here

Similar Messages

  • Regarding LDB pnpce

    hi experts,
    i m in need to create a report means i have to design the
    screen,in which i have to use LDB pnpce for HR,but if i select
    program type "module pool" in the report attributes  the filed
    LDB name is not coming means but when i select executable the LDB field is coming but when i select type module pool the it is not coming
    ....plz help me is there any way so that i can use ldb as well
    as module pool report type...............

    Hi
    you can call even LDB by using FM LDB_PROCESS. then you can attach the report to screen that you have designed.
    what you have to do is goto SE38---> Create a new report of type executable and don't select any LDB .
    2. Call teh function module LDB_PROCESS from the report and pass teh LDb name to this Fm
    [further Information|http://help.sap.com/saphelp_nw70/helpdata/en/64/237f8cd43711d1950b0000e8353423/content.htm]
    Regards
    Pavan

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

  • How to give pernr in range using LDB PNPCE

    I am using LDB PNPCE and in report category i want to give select option for pernr that will accept pernr in ranges also.So Please tell me how to give ranges of pernr.
    Thanx in advance.

    Hi,
    You mean that you want to set a range of personnel numbers as default on selection screen when running the report?
    If so, you can do that. That field is PNPPERNR, it is a select-option, set default values for it in event INITIALIZATION of your report.
    pnppernr-sign = 'I'.
    pnppernr-option = 'BT'.
    pnppernr-low = ....
    pnppernr-high = ...
    append pnppernr.
    Thanks

  • HR LDB PNP and customer infotypes in 640

    Hello,
    I encountered the following problem during an upgrade from 4.6C to SAP ERP Central Component 5.0. When using logical database PNP and customer infotypes the syntax check produces the following syntax error:
    - INCLUDE report "%_HR9731" not found
    I have added an example program below. Prerequisite for this program is that the cutomer infotype 9731 exists in the system.
    Has anyone experienced this problem before? And if so, is there a solution? I can program some workarounds, but I prefer a solution, which does not involve changing my code.
    Regards,
    Marcel
    REPORT ZTESTINFOTYPES.
    tables: pernr.
    infotypes: 0000,
    0001,
    0002,
    9731 mode n.
    start-of-selection.
    get pernr.
    write / p0002-pernr.
    end-of-selection.

    Hi all,
    "You will have to run report RPUMS40CCI (XPRA for generation of
    infotype include) for existing customer-defined infotypes.
    If you have not run this report then please do so.
    The report RPU40CCI creates the infotype include %_HRnnnn (nnnn =
    infotype number) and the additional data structure Pnnnn_AF (nnnn =
    infotype number) for the given infotype, provided that the correspondin parameter ("generate infotype include" or "generate additional data
    structure") are set on the selection screen. If the parameter "maintain only T77ID" is set, no infotype include or additional data structure is maintained, only those entered in table T77ID."
    Best Regards
    Silvio Galery

  • Custom infotype will also come in PNP Ldb

    Hi Friends-
    If we create a custom infotype which is starting from 9  eg  9001 , then  if we use PNP LDB   would this Ldb  provide me data for thsi custom infotype also apart from all PA standard infotype ?
    Regards
    Meeta

    Hello Meeta,
    It will not be a part of PA Info types.
    Yes, you will be able to get values of the custom info type in the GET PERNR and END-OF-SELECTION loop as you get values for other standard info types. For this you need to declare the custom info type same as you declare info types for which you want data in your program.
    Hope it helps.
    Thanks,
    Jayant

  • Authorization for LDB PNPCE &PNPPS and table T77S0

    Hi folks ,
    I’m working on a very interesting requirement , I have developed an Ad hoc query , which is reading IT0019 ( Monitoring dates infotype ) with field called task type . I take a test login and give task type which is equal = ‘w’ . When I was running that query in test login to see security is in place or not . I found that whenever there’s two recs in IT0019 with task type ‘W’ 9 which test login has authorization and ‘W2’ ( which test login doesn’t have authorization ) its not pulling up any record . its giving no data . to make sure I again went in to Infotype IT0019 and delete the task type (W2 : the one which test login doesn’t have authorization ) . then I run the query . it pull up one record . So my question is how can I handle this situation in Adhoc query . I mean logically speaking it should pull up at least one record for which it has authorization . I am using LDB PNPCE .
    Moreover , I debug the query and I came to know its reading the the table T77S0 using class : CL_HR_T77S0.
    I read the about table (T77S0) , another question if I set another entry in the table with PNPPS and AUTSW. Will it works . Can I control it?
    http://help.sap.com/saphelp_erp2005/helpdata/en/84/49ba3b3bf00152e10000000a114084/content.htm
    Thanks,
    SK

    Hello Amit,
    you have to run the "copy" action ,while changing OM objects. then only it will effect in IT 0001
    if you will click on change then it will not update in PA.
    so click on Copy then do the changes and save it. it will update IT 0001.
    We had the same issue. if you get any solution then let me know.
    OR
    Will you try running  RHINTE30 Report
    do batch input session and run it via SM35
    Thanks and Regards
    Jaydeep Jadhav

  • What is the main diff b/n ldb pnp and pnpce?

    hi ,
    what is the main diff b/n ldb pnp and pnpce?
    thanks.

    Hi Arun,
      PNP/PNPCE  - Both are Logical Databases for PA Module
    In PNPCE - CE stands for Concurrent Employment.
    The differnces are:
    The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
    The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
    Hope this helps you.
    Regards,
    Chandra Sekhar

  • How to create custom infotype for training and event management

    hai freinds can any one tell me how to create custom infotype for training and event managment with following fields
    PS No – PA0000-> PERNR
    Name   - PA0001 -> ENAME
    IS PS.No. – PA0001-> PS no. of Immediate Superior
    IS name PA0001 -> ENAME
    thanx in advance
    afzal

    Hi,
    Your question is not clear for me. Since it is a TEM infotype, it could be a PD infotype.
    If you wish to create a PD infotype, use transaction PPCI to create the infotype.
    But before that you need to create a structure HRInnnn (where nnnn is the infotype number) with all the fields relevant for the infotype.
    If you wish to create a PA infotype, use transaction PM01 to create the infotype.
    But before that you may be required to create a strcuture PSnnnn  (where nnnn is the infotype number) with all the fields relevant for the infotype.
    Regards,
    Srini

  • Create Custom Infotype and handle Modification/Updation

    Hi All,
    I need to create a custom infotype and handle few checks while creating/updating the existing one.
    I have gone through the existing threads and have figured out the creation part.
    Could anyone tell me where i need to code the checks while creating/updating.
    I tried editing the PBO/PAI of the Module pool program, but as its standard, is asking for access key. Do we need to code this in any userexit or implement BADI.
    For example,
    a) i need to check that only one instance of the infotype should be valid for an  
        employee at a time
    b) This infotype should be created for only Employees and not contingent workers.
    c) Few fields on the body section needs to be updated/modified.
    Thanks and Regards
    Manish.

    You can use the IN_UPDATE or AFTER_INPUT Methods of the BAdI HRPAD00INFTY to perform your validations.
    Arya

  • How we create custom infotype and how to configure with its subtypes.

    hai abap-hr gurus,
    how to create custom infotype and how to configure with its subtypes. when i am creating infotypes i am not getting how to configure subtypes.
    plz help me for this with an example code.
    thanks..
    kiran kumar

    Hi Kiran,
        Please fallow the below steps to create the custom infotype. If you have any quires let me know.
    For Creation of Infotype first Go to Transaction PM01, Enter the custom Infotype number which you want to create, it should be a 4 digit number and have to start with 9xxx.
    then select the `Employee Infotype' radio button
    after that select the `PS Structure Infotype'
    then click on Create… A separate table maintenance window appears
    then Create a PS structure with all the fields you want on the infotype
    Save and Activate the PS structure
    now Go back to the initial screen of PM01
    Click on `All' push button. It takes a few moments
    Click on `Technical Characteristics’. Infotype list screen appears
    Click on `Change'(pencil) button
    Now select your Infotype and click on `Detail' (magnifying glass) button
    Give `T591A' as subtype table & also Give `T591S' as subtype txt tab
    Give your subtype field as subtype field & Save and come back to PM01 initial screen
    Click on `Infotype Characteristics' … Infotype list screen appears
    Click on `Change' (pencil) button & on New Entries
    and then Enter your Infotype number and short text Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference
    to fill yours). Now save ur entries
    Now the Infotype is created and ready to use.
    If you want to change the layout of the Infotype as per your
    requirement…
    In the PM01 initial screen…Select `Screen' radio button and give
    2000 as the screen name, then click on edit.
    In the next screen.. Select `Layout Editor' and click `Change'.
    Screen default layout appears…here you can design/modify the
    screen..change the attributes of the fields..etc.
    Save and activate. (Don't forget to `Activate at every level)
    Regards,
    Ramakrishna kotha.

  • Regarding using of LDB PNPCE  in sap hr

    Can some one please tell me how to disable some of the selection screen fields and blocks of LDB PNPCE selection-screen which are not used in my report selection-screen?
    Thanks,
    Phanisreedhar.L

    *: Report:  ZP_POSTCODE                                                :
    *: Author:  www.SAPDev.co.uk                                           :
    *: Date  :  2004                                                       :
    *: Description: Displays report of employees by postcode area,         :
    *:              includes current travelling allowances (i.e. parking   :
    *:              permit or transport card etc..)                        :
    *: Use:         Help encourage the use of car sharing and public       :
    *:              transport where appropriate.                           :
    REPORT  zp_postcode.
    type-pools: slis.                                      "ALV Declarations
    NODES: pernr.
    INFOTYPES: 0000, 0001, 0002, 0006, 0008, 0014, 0105, 0121.
    SELECTION-SCREEN BEGIN OF BLOCK pcode WITH FRAME TITLE text-s01.
    SELECT-OPTIONS: so_pcode FOR p0006-pstlz.
    SELECTION-SCREEN END OF BLOCK pcode.
    TYPES: BEGIN OF t_output,
      pernr       TYPE p0001-pernr,   "personnel name
      anredtxt    TYPE t522t-atext,   "title (based on p0002-anred)
      fname       TYPE p0002-vorna,   "first name
      lname       TYPE p0002-nachn,   "last name
      orgtx       TYPE t527x-orgtx,   "dept
      fte         TYPE p0008-bsgrd,   "fte
      parking(20) TYPE c,
      payslip     TYPE t526-sachn,        "payslip address
      telno       TYPE p0105-usrid_long,  "tel number(p0105-usrty = 0020)
      email       TYPE p0105-usrid_long,  "email (p0105-usrty = MAIL)
      postcode    type p0006-pstlz,
    END OF t_output.
    DATA: it_output TYPE STANDARD TABLE OF t_output INITIAL SIZE 0,
          wa_output TYPE t_output.
    *ALV data declarations
    data: fieldcatalog   type slis_t_fieldcat_alv with header line,
          gd_tab_group   type slis_t_sp_group_alv,
          gd_layout      type slis_layout_alv,
          gd_repid       like sy-repid,
          gt_events      type slis_t_event,
          gd_prntparams  type slis_print_alv,
          gd_count(6)    type n,
          gd_outtext(70) type c,
          gd_lines       type i.
    *START-OF-SELECTION.
    START-OF-SELECTION.
    clear: gd_count.
    GET pernr.
    Infotype 0121 is used to store multiple contracts for personnel.
    Field p0121-hpern contains the personnel number for the main contract.
      PROVIDE * from p0121 between pn-begda and pn-endda.
      Check if main contract
        if p0121-pernr ne p0121-hpern.
          reject.
        endif.
      ENDPROVIDE.
      add 1 to gd_count.
      concatenate 'Processing personnel data'(m10) gd_count into gd_outtext
                separated by ' '.
    Display indicator for employee count
      perform progress_indicator using gd_outtext.
    Retrieve datd from infotypes
      rp_provide_from_last p0000 space pn-begda pn-endda.
      rp_provide_from_last p0001 space pn-begda pn-endda.
      rp_provide_from_last p0002 space pn-begda pn-endda.
      rp_provide_from_last p0006 space pn-begda pn-endda.
      rp_provide_from_last p0008 space pn-begda pn-endda.
      rp_provide_from_last p0014 space pn-begda pn-endda.
    Check post code
      CHECK p0006-pstlz IN so_pcode.  "cp
    Post code
      wa_output-postcode = p0006-pstlz.
    Personnel number
      wa_output-pernr = pernr-pernr.
    Personnel title
      SELECT SINGLE atext
        FROM t522t
        INTO wa_output-anredtxt
       WHERE sprsl EQ sy-langu AND
             anred EQ p0002-anred.
    First name
      wa_output-fname = p0002-vorna.
    Last name
      wa_output-lname = p0002-nachn.
    Organizational Unit text (dept)
      SELECT SINGLE orgtx
        FROM t527x
        INTO wa_output-orgtx
       WHERE sprsl EQ sy-langu AND
             orgeh EQ p0001-orgeh AND
             endda GE sy-datum.
    FTE
      wa_output-fte = p0008-bsgrd.
    Parking / travel deducted?
      CASE p0014-lgart.
        WHEN '7180' OR '7181' OR '7182'.
          wa_output-parking = text-002.
        WHEN '7183'.
          wa_output-parking = text-001.
        WHEN '7171' OR '7172' or '7173' or '7174' or
             '7175' or '7176' or '7177' or '7178'.
          wa_output-parking = text-003.
      ENDCASE.
    Payslip Address
      SELECT SINGLE sachn
        FROM t526
        INTO wa_output-payslip
       WHERE werks EQ p0001-werks AND
             sachx EQ p0001-sacha.
      PROVIDE * from p0105 between pn-begda and pn-endda.
      Telephone numbers
        if p0105-usrty = '0020'.
           wa_output-telno = p0105-usrid_long.
        endif.
      Email address
        if p0105-usrty = 'MAIL'.
           wa_output-email = p0105-usrid_long.
        endif.
      ENDPROVIDE.
      append wa_output to it_output.
      clear: wa_output.
    *END-OF-SELECTION.
    END-OF-SELECTION.
    describe table it_output lines gd_lines.
    if gd_lines gt 0.
      perform build_fieldcatalog.
      perform build_layout.
      perform display_alv_report.
    else.
      message i003(zp) with 'No records found'.
    endif.
    *&      Form  PROGRESS_INDICATOR
          Displays progress indicator on SAP screen
    form progress_indicator using p_text.
      call function 'SAPGUI_PROGRESS_INDICATOR'
          exporting
            PERCENTAGE = 0
               text       = p_text.
    endform.                    " PROGRESS_INDICATOR
    *&      Form  BUILD_FIELDCATALOG
          Build Fieldcatalog for ALV Report
    form build_fieldcatalog.
      fieldcatalog-fieldname   = 'PERNR'.
      fieldcatalog-seltext_m   = 'Personnel No.'.
      fieldcatalog-col_pos     = 0.
      fieldcatalog-outputlen   = 10.
    fieldcatalog-emphasize   = 'X'.
    fieldcatalog-key         = 'X'.
    fieldcatalog-do_sum      = 'X'.
    fieldcatalog-no_zero     = 'X'.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'ANREDTXT'.
      fieldcatalog-seltext_m   = 'Title'.
      fieldcatalog-col_pos     = 1.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'FNAME'.
      fieldcatalog-seltext_m   = 'First Name'.
      fieldcatalog-col_pos     = 2.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'LNAME'.
      fieldcatalog-seltext_m   = 'Last Name'.
      fieldcatalog-col_pos     = 3.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'ORGTX'.
      fieldcatalog-seltext_m   = 'Department'.
      fieldcatalog-col_pos     = 4.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'FTE'.
      fieldcatalog-seltext_m   = 'FTE'.
      fieldcatalog-col_pos     = 5.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'PARKING'.
      fieldcatalog-seltext_m   = 'Parking/Metrocard'.
      fieldcatalog-col_pos     = 6.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'PAYSLIP'.
      fieldcatalog-seltext_m   = 'Payslip Add.'.
      fieldcatalog-col_pos     = 7.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'TELNO'.
      fieldcatalog-seltext_m   = 'Telephone'.
      fieldcatalog-col_pos     = 8.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'EMAIL'.
      fieldcatalog-seltext_m   = 'E-mail'.
      fieldcatalog-col_pos     = 9.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
      fieldcatalog-fieldname   = 'POSTCODE'.
      fieldcatalog-seltext_m   = 'Post code'.
      fieldcatalog-col_pos     = 10.
      append fieldcatalog to fieldcatalog.
      clear  fieldcatalog.
    endform.                    " BUILD_FIELDCATALOG
    *&      Form  BUILD_LAYOUT
          Build layout for ALV grid report
    form build_layout.
      gd_layout-no_input          = 'X'.
      gd_layout-colwidth_optimize = 'X'.
      gd_layout-totals_text       = 'Totals'(201).
      gd_layout-zebra             = 'X'.
    endform.                    " BUILD_LAYOUT
    *&      Form  DISPLAY_ALV_REPORT
          Display report using ALV grid
    form display_alv_report.
      gd_repid = sy-repid.
      call function 'REUSE_ALV_GRID_DISPLAY'
           exporting
                i_callback_program      = gd_repid
                is_layout               = gd_layout
                it_fieldcat             = fieldcatalog[]
                i_save                  = 'X'
           tables
                t_outtab                = it_output
           exceptions
                program_error           = 1
                others                  = 2.
      if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      endif.
    endform.                    " DISPLAY_ALV_REPORT
    The following program allows you to retrieve all the individuall sickpay values for a given period and person.This data is then exported to memory using the memory id entered on the selection screen. This thereforeallows you to submit this program from another program and then process the data within the calling programby importing the data from memory.  Click here for example .
    Report:  ZSXP_ABSENCE_DATA                                           **                                                                      ** Author:  www.SAPdev.co.uk                                            **                                                                      ** Date  :  12.02.2003                                                  **                                                                      ** Description: Retrieve maternaty/Sickness Absence data*                                                                      ************************************************************************REPORT ZSXP_ABSENCE_DATA      LINE-SIZE 100 NO STANDARD PAGE HEADING                MESSAGE-ID 5g.TABLES: t554s, pernr, pcl1, pcl2.INCLUDE rpclst00.INCLUDE rpc2rx09.                      "Payroll results datadefns-Intl.INCLUDE rpc2rxx0.                      "Payroll results datadefns-Intl.INCLUDE rpc2rgg0.                      "Payroll results datadefns-GBINCLUDE rpcfdcg0.                      "Payroll results datadefns-GBINCLUDE rpcdatg0.INCLUDE rpc2cd00.                      "Cluster Directory defns.INCLUDE rpc2ps00.                      "Cluster: Generierte SchematasINCLUDE rpc2pt00.INCLUDE rpcfdc10.INCLUDE rpcfdc00.INCLUDE rpppxd00.INCLUDE rpppxd10.INCLUDE rpcfvp09.INCLUDE rpcfvpg0.INCLUDE rpppxm00.INFOTYPES: 0001,                       "Organisational assignment           0002,                       "Personal Data           0003,                       "Payroll Status           0088,                                            "SMP           2001,                       "Absences           0086.                       "SSP/SMP ExlclusionsDATA:   ssp_weeks TYPE p DECIMALS 2 VALUE 0.DATA:   ssp_total TYPE p DECIMALS 2 VALUE 0,        total_val TYPE p DECIMALS 2 VALUE 0,        smp_weeks TYPE p DECIMALS 2 VALUE 0,        smp_value TYPE p DECIMALS 2 VALUE 0,        gross     LIKE pc207-betrg,        dis_gross TYPE p DECIMALS 2 VALUE 0.DATA: gd_begda(10) TYPE c,      gd_endda(10) TYPE c.DATA: ld_orgtxt LIKE t527x-orgtx.DATA: name(30).DATA: BEGIN OF itab OCCURS 0,      pernr LIKE p0002-pernr,      perid LIKE p0002-perid,      name  LIKE name,      END OF itab.TYPES: BEGIN OF t_report,   pernr   TYPE pernr-pernr,   "8   name    TYPE name,          "30   awart   TYPE p2001-awart,   "4   begda   TYPE p2001-begda,   "10   endda   TYPE p2001-endda,   "10   wkspaid TYPE p DECIMALS 2,  "10   amtpaid TYPE p DECIMALS 2,  "10  END OF t_report.DATA: it_report TYPE STANDARD TABLE OF t_report INITIAL SIZE 0,      wa_report TYPE t_report.DATA: moabw LIKE t001p-moabw.DATA: printheader TYPE i VALUE 1,      gd_success  TYPE i. NCALE declarationsTYPES : BEGIN OF pfra0_pcale,           annee(4) TYPE c.        INCLUDE STRUCTURE pcint.TYPES : END OF pfra0_pcale.TYPES : pfra0_tab_pcale  TYPE  pfra0_pcale  OCCURS 0.DATA:  it_ncale TYPE STANDARD TABLE OF pcnat INITIAL SIZE 0,       wa_ncale TYPE pcnat,       it_pcale TYPE  pfra0_tab_pcale,       pcale  TYPE  pfra0_tab_pcale.* SMP/SSP absence datadata begin of it_msa occurs 0.        include structure pc27j.data end of it_msa.parameters: p_memid type char30.************************************************************************STAR-OF-SELECTIONSTART-OF-SELECTION.gd_begda = pn-begda.gd_endda = pn-endda.gd_begda6(2) = '01'.gd_endda6(2) = '01'.refresh: it_msa.clear:   it_msa.GET pernr.*    PERFORM IMPORT_PC USING GD_SUCCESs.  PERFORM get_rgdir.  while gd_begda le gd_endda.    PERFORM get_new_rg USING gd_begda.    CALL FUNCTION 'CALCULATE_DATE'        EXPORTING*             DAYS        = '0'             MONTHS      = '1'             START_DATE  = gd_begda        IMPORTING             RESULT_DATE = gd_begda.  endwhile.  msa[] = it_msa[].  EXPORT msa TO MEMORY ID p_memid.&---------------------------------------------------------------------&      Form  GET_RGDIR&-------------------------------------------------------------------FORM get_rgdir.  rp-init-buffer.  CLEAR rgdir.  REFRESH rgdir.  MOVE pernr-pernr(8) TO cd-key-pernr.  rp-imp-c2-cd.  IF rp-imp-cd-subrc = 0.                                "rgdir success    SORT rgdir BY seqnr ASCENDING.    CLEAR rgdir.  ENDIF.ENDFORM.-----------------------------------------------------------------**       FORM get_new_rg                                               **-----------------------------------------------------------------**       ........                                                      **-------------------------------------------------------------------**  >  search_date                                                   **-----------------------------------------------------------------FORM get_new_rg USING search_date.  DATA: rg_day TYPE d,        rgbeg  TYPE d,        rgend  TYPE d.  MOVE: search_date TO rg_day.  CLEAR: msa.  LOOP AT rgdir WHERE void NE 'V'.    MOVE: rgdir-fpbeg TO rgbeg,          rgdir-fpend TO rgend.    IF ( rgbeg <= rg_day ) AND       ( rgend >= rg_day ) AND       rgdir-srtza = 'A'.        "Must be periods actual set of results      EXIT.    ENDIF.  ENDLOOP.  UNPACK rgdir-seqnr TO rx-key-seqno.  MOVE pernr-pernr(8) TO rx-key-pernr(8).  rp-imp-c2-rg.  append lines of msa to it_msa.  IF rp-imp-rg-subrc <> 0.   rg fail  ELSE.*   rg success  ENDIF.ENDFORM.Text elements------------------------------------------------------*  001     Sickness History for SSP 1*  002     Employee Name.*  003     National Insurance Number.*  004     Payroll Number.*  005     Sickness Start Date*  006     Sickness End Date*  007     Number of weeks paid*  008     system-error:*  009     No SSP / SMP record found*  010     Absence type*  011     No. weeks paid*  012     Amount*  013     Organisation Unit.*  T01     Sickness Absence typesSelection texts--------------------------------------------------------* SO_SAP          SAP Att./absence types* SO_SMP          SMP Att./absence types* SO_SPP          SPP Att./absence types* SO_SSP          SSP Att./absence types
    Uses Logical database 'PNP'(entered in program attributes) to retrieve various personnel data and downloadit to an excel / tab delimited file.
    .......................................................................: Report:  ZDOWNEMPDATA                                               ::                                                                     :: Author:  www.SAPDev.co.uk                                           ::                                                                     :: Date  :  2004                                                       ::                                                                     :: Description: Downloads employee data to TAB delimited flat files    ::                                                                     ::.....................................................................:.......................................................................: Report:  ZDOWNEMPDATA                                               ::                                                                     :: Author:  www.SAPDev.co.uk                                           ::                                                                     :: Date  :  2004                                                       ::                                                                     :: Description: Downloads employee data to TAB delimited flat files    ::                                                                     ::.....................................................................:REPORT  zdownempdata                                         .INFOTYPES: 0000, 0001, 0007, 0008, 0121, 0615.NODES: pernr.TABLES: t001p.TYPES: BEGIN OF t_employee,*        INCLUDE STRUCTURE hrms_biw_io_occupancy.  begda     TYPE begda,  endda     TYPE endda,  pernr     TYPE pernr_d,  rfpnr     TYPE rfpnr,  bukrs     TYPE bukrs,  werks     TYPE persa,  btrtl     TYPE btrtl,  persg     TYPE persg,  persk     TYPE persk,  orgeh     TYPE orgeh,  stell     TYPE stell,  plans     TYPE plans,  kokrs     TYPE mast_coar,  kostl     TYPE mast_cctr,  abkrs     TYPE abkrs,  molga     TYPE molga,  trfar     TYPE trfar,  trfgb     TYPE trfgb,  trfkz     TYPE trfkz,  trfgr     TYPE trfgr,  trfst     TYPE trfst,  bsgrd     TYPE bsgrd,  ansal     TYPE ansal_15,  ancur     TYPE ancur,  empct     TYPE empct,  stat2     TYPE stat2,  ncsdate     TYPE hiredate,  sltyp     TYPE p_sltyp,  slreg     TYPE p_slreg,  slgrp     TYPE p_slgrp,  sllev     TYPE p_sllvl,  ansvh     TYPE ansvh,  vdsk1     TYPE vdsk1,  sname     TYPE smnam, END OF t_employee.DATA: it_employee TYPE STANDARD TABLE OF t_employee INITIAL SIZE 0,      wa_employee TYPE t_employee.TYPES: BEGIN OF t_emptexts,*        INCLUDE STRUCTURE hrms_bw_txt_employee.  DATEFROM     TYPE RSDATEFROM,  DATETO     TYPE RSDATETO,  PERNR     TYPE PERSNO,  TXTMD     TYPE EMNAM, END OF t_emptexts.DATA: it_emptexts TYPE STANDARD TABLE OF t_emptexts INITIAL SIZE 0,      wa_emptexts TYPE t_emptexts.TYPES: BEGIN OF t_contract,*        INCLUDE STRUCTURE pa0615.  pernr TYPE p0615-pernr,  begda TYPE p0615-begda,  endda TYPE p0615-endda,  aedtm TYPE p0615-aedtm,  ctype TYPE p0615-ctype,  cbeg  TYPE p0615-cbeg,  cend  TYPE p0615-cend, END OF t_contract.DATA: it_contract TYPE STANDARD TABLE OF t_contract INITIAL SIZE 0,      wa_contract TYPE t_contract.DATA: it_tabemp TYPE filetable,      gd_subrcemp TYPE i,      it_tabempt TYPE filetable,      gd_subrcempt TYPE i,      it_tabcont TYPE filetable,      gd_subrccont TYPE i.DATA: gd_downfile TYPE string.SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME TITLE text-001.PARAMETERS: p_emp   LIKE rlgrap-filename,            p_empt  LIKE rlgrap-filename,            p_cont LIKE rlgrap-filename.SELECTION-SCREEN END OF BLOCK block1.***********************************************************************at selection-screenAT SELECTION-SCREEN ON VALUE-REQUEST FOR p_emp.  REFRESH: it_tabemp.  CALL METHOD cl_gui_frontend_services=>file_open_dialog    EXPORTING      window_title      = 'Select File'      default_filename  = '.xls'      initial_directory = 'C:\'      multiselection    = ' '  "No multiple selection    CHANGING      file_table        = it_tabemp      rc                = gd_subrcemp.  LOOP AT it_tabemp INTO p_emp.  ENDLOOP.***********************************************************************at selection-screenAT SELECTION-SCREEN ON VALUE-REQUEST FOR p_empt.  REFRESH: it_tabemp.  CALL METHOD cl_gui_frontend_services=>file_open_dialog    EXPORTING      window_title      = 'Select File'      default_filename  = '.xls'      initial_directory = 'C:\'      multiselection    = ' '  "No multiple selection    CHANGING      file_table        = it_tabempt      rc                = gd_subrcempt.  LOOP AT it_tabempt INTO p_empt.  ENDLOOP.***********************************************************************at selection-screenAT SELECTION-SCREEN ON VALUE-REQUEST FOR p_cont.  REFRESH: it_tabcont.  CALL METHOD cl_gui_frontend_services=>file_open_dialog    EXPORTING      window_title      = 'Select File'      default_filename  = '.xls'      initial_directory = 'C:\'      multiselection    = ' '  "No multiple selection    CHANGING      file_table        = it_tabcont      rc                = gd_subrccont.  LOOP AT it_tabcont INTO p_cont.  ENDLOOP.************************************************************************START-OF-SELECTION.START-OF-SELECTION.GET pernr. Selecting the latest infotype record  rp_provide_from_last p0000 space pn-begda pn-endda.  rp_provide_from_last p0001 space pn-begda pn-endda.  rp_provide_from_last p0007 space pn-begda pn-endda.  rp_provide_from_last p0008 space pn-begda pn-endda.  rp_provide_from_last p0121 space pn-begda pn-endda.  rp_provide_from_last p0615 space pn-begda pn-endda.  MOVE-CORRESPONDING p0001 TO wa_employee.  wa_employee-rfpnr = p0121-rfp01. "?????  MOVE-CORRESPONDING p0007 TO wa_employee.  MOVE-CORRESPONDING p0008 TO wa_employee.  MOVE-CORRESPONDING p0000 TO wa_employee.  SELECT SINGLE molga    FROM t001p    INTO wa_employee-molga   WHERE werks EQ p0001-werks AND         btrtl EQ p0001-btrtl.  SELECT SINGLE trfkz    FROM t503    INTO wa_employee-trfkz   WHERE persg EQ p0001-persg AND         persk EQ p0001-persk.  CALL FUNCTION 'HR_ENTRY_DATE'    EXPORTING      persnr                     = pernr-pernr*   RCLAS                      =*   BEGDA                      = '18000101'*   ENDDA                      = '99991231'*   VARKY                      =   IMPORTING      entrydate                  = wa_employee-ncsdate* TABLES*   ENTRY_DATES                = EXCEPTIONS   ENTRY_DATE_NOT_FOUND       = 1   PERNR_NOT_ASSIGNED         = 2   OTHERS                     = 3            .  IF sy-subrc <> 0.* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.  ENDIF.* append employee data  APPEND wa_employee TO it_employee.  CLEAR: wa_employee.  wa_emptexts-datefrom = p0001-begda.  wa_emptexts-dateto   = p0001-endda.  wa_emptexts-pernr    = p0001-pernr.  wa_emptexts-txtmd    = p0001-ename.* append employee texts data  APPEND wa_emptexts TO it_emptexts.  CLEAR: wa_emptexts.  MOVE-CORRESPONDING p0615 TO wa_contract.* append employee contract data  APPEND wa_contract TO it_contract.  CLEAR: wa_contract.************************************************************************END-OF-SELECTION.END-OF-SELECTION. download employee data  IF NOT p_emp IS INITIAL.    gd_downfile = p_emp.    CALL FUNCTION 'GUI_DOWNLOAD'      EXPORTING        filename              = gd_downfile        filetype              = 'ASC'        write_field_separator = 'X'      TABLES        data_tab              = it_employee.    IF sy-subrc EQ 0.      WRITE:/ 'Employee file downloaded to',              gd_downfile.    ELSE.      WRITE:/ 'There was an error downloading Employee file to',              gd_downfile.    ENDIF.  ENDIF.* download employee texts data  IF NOT p_empt IS INITIAL.    gd_downfile = p_empt.    CALL FUNCTION 'GUI_DOWNLOAD'      EXPORTING        filename              = gd_downfile        filetype              = 'ASC'        write_field_separator = 'X'      TABLES        data_tab              = it_emptexts.    IF sy-subrc EQ 0.      WRITE:/ 'Employee text file downloaded to',              gd_downfile.    ELSE.      WRITE:/ 'There was an error downloading Employee text file to',              gd_downfile.    ENDIF.  ENDIF.* download contract data  IF NOT p_cont IS INITIAL.    gd_downfile = p_cont.    CALL FUNCTION 'GUI_DOWNLOAD'      EXPORTING        filename              = gd_downfile        filetype              = 'ASC'        write_field_separator = 'X'      TABLES        data_tab              = it_contract.    IF sy-subrc EQ 0.      WRITE:/ 'Employee contract file downloaded to',              gd_downfile.    ELSE.      WRITE:/ 'There was an error downloading Employee contract file to',              gd_downfile.    ENDIF.  ENDIF.

  • Custom infotype in HCM and Extraction into BI

    Hi
    I am unable to build a custom extractor from view in hcm to extract the infotype 0102.
    could you please help me out in understanding hcm custom extractions?
    The error message was: Invalid extract structure template PA0102.
    Can I not create a custom extractor over any infotype? what about the custom infotypes?
    Please help me in understanding this: If we create a custom infotype in R3, will all the data related to that reside in one underlying table or not?
    Can I create a custom extractor to extract from the custom infotype without ABAP?
    Thanks
    Sarah

    Hi Sarah,
    I guess your is related to some of the amount or quantity fields included in pa0102. Check it out. They must point to unit fields also included in pa0102. In case they do not, it is not possible to use that table for extraction. You need to create a view on it as well as on the unit tables and include the unit fields into your view. Then it will work.
    kind regards
    Siggi

  • Displaying Custom Infotype in the Overview Section of LSO_PV10 and LSO_PV1A

    Dear experts,
    We would like to display the custom IT in the Overview Section of Create Course Run (LSO_PV10) and Change Course Run (LSO_PV1A) screen. User currently can create and edit some standard ITs from this overview section.
    Currently, the custom IT has been built and configured to Object Course (E). It can be displayed from PP01 when choosing Object E.
    How can we display the custom infotype to the standard Create Course Run (LSO_PV10) / Change Course Run screen (LSO_PV1A) Overview area?
    Many Thanks!
    Regards,
    Ripin

    Hai,
    I also faced your problem. I created business event. but when i am checking the business event, but results nil. But system is showing no. for that it is not showing object and relation.
    For that i create again object and realationships for that event. Automatically, system overlap that event.
    it it is helpful or not, i don't know. If it is helpful , do like that way.
    Thanks

  • Custom Infotype : Only for Disply Mode Change and Create Should be disable

    Dear Experts,
                        I Created a custom infotype in PM01 for Exit process , my client requirement is this infotype  only shows the details .
    Could you please tell me how to disable the Create and change button in PA30 Screen ?
    Regards,
    Sivakumar.A

    hi siva
    In PM01 itself you have option module pool, select that option go to screen program.
    there select field->dbl clk-> screen attributes pop up will come.
    there you have to change the input/output option
    Regards
    Deva

Maybe you are looking for