Pnpce logical database

hi,
How to create report catagory using pnpce logical database?
Thanks,
sunil

Hi
For using PNPCE
1) go to attributes give logical data base as PNPCE .
2) In attributes only you have button HR reort Category click on that button and select the relevant selection criteria or you can create yours own .
3) in Report pogram Use Table : Pernr .
4) Use GET PERNR. to get the values
5) Use macro RP Provode from last lets say P0001 based on BEGDA and ENDA
Regards
Hitesh

Similar Messages

  • Additional i/o fields to infoset query based on PNPCE logical database

    Hi All,
    I have a requirement to add two additional input and output fields "job function" and "job family" to a infoset query based on logical database PNPCE. I am new to writing code in infset query and there are so many code areas in infoset query. I am confused where to write code and how to limit the output list based on the user selection to the additional fields "Job function" and "job family". have any one done this in the past?. is there sample code somewhere to do something similar to this?
    Your help will be much appreciated with points! (as per our community guidelines)
    Regards,
    Arul

    Hello Arul,
    Your question would be better answered if you post it in on of the Business Intelligence Forums. Please close this thread and goto:
    Expert Forums » Business Intelligence
    or
    /community
    Regards,
    Manny

  • HR PNPCE logical Database and  rp-sel-ein-aus-init. not working

    Hi Forums,
    I want to set the employment status to (<> 0) and I have put this code
    isn't this macro supposed to achieve this?
    INITIALIZATION.
        rp-sel-ein-aus-init.

    Hi,
        I simply wrote the below .. and the "Employment Status" field is filled with NE 0 (not equal to '0')
        Check if you are missing something.
    TABLES: pernr.
    NODES peras.
    initialization.
    rp-sel-ein-aus-init.
    START-OF-SELECTION.
    GET peras.
    Regards,
    Srini.

  • Logical  database and program selection filter

    Hi experts ,
    In my program i have to select pernr through logical database selection and payroll area through manual coding .
    Could you tell me how to give the filter condition in program.I am  using PNPCE Logical database .
    Thank you.
    Devika.

    I guess you mean to modify the screen layout during AT SELECTION-SCREEN OUTPUT via
    AT SELECTION-SCREEN OUTPUT.
      LOOP AT SCREEN.
        screen-active = 0.
        MODIFY SCREEN.
      ENDLOOP.
    This does hides all screen elements but the screen is still displayed.

  • Restrict Select-Options for Logical Database field

    The way we restrict select options for custom defined select option fields on selection screen.. can we restrict select options for standard Logical Database fields?
    i.e. report uses PNPCE logical database and has field called PERNR. I want to restrict select options for this PERNR field so that it has options for 'Select single values' only.
    Thanks,
    Falguni
    Edited by: Falguni V on Nov 13, 2010 6:42 AM

    You can user AT SELECTION-SCREEN event, and check whether any record is having high value for PNPPERNR.

  • Authorization on PNP logical database

    My limited understanding of authorization on reports that uses PNP/PNPCE logical database is that if a user who runs the report does not have authorization for any of the declared infotypes then the report stops with message 'no authorization for infotype ...'.  And if the user has authorization for the infotypes but do not have authorizations for some of the PERNRS then it will only display those records that user have authorization for and shows message saying no. of skipped records (of those that user did not have authorization).
    Programmers here say that the users who do not have authorization for some infotypes should still be able to see list for other infotypes that they do have authorization for.
    -- Please shed some light on this and guide me if there is a cookbook/document out there about this.
    Thanks a bunch.
    Netra

    Hi Neha,
    Adding further.
    Each report is different in its own way and there are various ways of controlling the access to the Reports based on ur scenario.
    The first check happens at the P_ABAP level where in it checks the access to the program corresponding to that report and level of access (1,2).
    If these are missing then it goes further to check for the explicit access
    in objects like
    P_ORGIN, P_PERNR etc.
    Now in some of these reports the processing is designed in such a way that if the access to an IT is not available it throughs a error message and the processing of the report stops at that instance (this depends on the message type which has been defined at that instance to be displayed) so at this instance you need to have access to that IT to proceed further but in some other cases the check does happen but the processing continues without stopping at that check failure(example is P_PERNR, the check happens but is not required for processing the report).
    This is one example but there could even more criterion based on which the processing of the report is terminated or allowed to continue depending on the reports utility
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/dbaabc35c111d1829f0000e829fbfe/frameset.htm">The different message types and their significance is as follows</a>
    So what you have been told by programmers is true in some cases but surely not accross all the HR reports and all auth objects.
    Hope this helps
    Manohar
    Message was edited by:
            Manohar Kappala

  • Difference between PNP and PCH logical database

    WHats the difference between PNP nd PCH? When to use which??
    Tx

    Hi,
    The Difference is only with in an SAP R/3 system in which Concurrent Employment is active, reports are executed by the PNPCE logical database. The general logic of the PNPCE logical database corresponds to the PNP logical database. The PNPCE logical database can also process the concept of Concurrent Employment.
    HR Logical Databases
    In Human Resources (HR), the following logical databases can be used as a data source for HR InfoSets:
    PNP (PNPCE)
    PAP
    PCH
    By selecting a logical database, you determine the HR data that can be reported on using an InfoSet.
    Logical Database PCH
    This logical database generally enables you to report on all HR infotypes. However, you are advised not to use this logical database unless you want to report on Personnel Planning data.
    Logical Database PNP (or PNPCE)
    Use logical database PNP to report on HR master data. It is possible to use logical database PCH to access this data, but PNP meets such reporting requirements more quickly because it is best suited to the task of selecting persons.
    Logical database PNP enables you to access HR master data and infotypes from Personnel Planning. For example, you have the following options:
    Reporting on the costs, number of attendees booked, and instructor for a business event on which an employee is booked
    Reporting on working time and planned compensation for a position that an employee occupies
    Reporting on the validity and proficiency of a qualification that an employee fulfils
    From a technical perspective, this means you can use PNP to report on all of the infotypes that exist for objects (infotype 1000) that have a direct relationship (infotype 1001) with the Person object.
    The ability to access infotypes from Personnel Planning using logical database PNP is a special feature that you can only use in the context of SAP Query and Ad Hoc Query. You cannot use this functionality for ABAP reports you programmed yourself.
    You can also use logical database PNP to report on data from Personnel Time Management (infotypes 2000 to 2999) and Payroll (special payroll infotypes for the USA and customer infotypes; for more information, access Customizing for the Human Resources Information System and see Payroll Results).
    Logical Database PAP
    Logical database PAP enables you to access data from Recruitment.
    Check this link for more details
    http://help.sap.com/saphelp_erp2004/helpdata/en/e1/e1f83f6e5a11d687620000e82158f1/frameset.htm
    <b>Reward points</b>
    Regards

  • Logical Database - PNP, PCH, PNPCE

    Hi Experts,
    Im New to ABAP HR,
    I would like to know about the logical databases we are using .
    Logical Database - PNP, PCH, PNPCE, basic principles
    If any body cud let me know about the differences , requiremnts , associated with these Logical databses will be much helpful for me.
    Thanks
    Rohini Devi
    [email protected]

    Hi Rohini...
    Global Employee Programming
    Thanks
    Message was edited by:
            Aslam Riaz

  • Logical Database PNPCE and inherited Sub Area

    Hi,
    I have asked this in the HR forum but no response......
    I have a report using Logical Database PNPCE to find some values from a couple of info types. When I select a unit (from the 'OrgStructure' button at the top of the screen), say 111, and all its sub-units with no selections in the selection screen, I get one person displayed. This is correct and this person is in a sub-unit 3 levels down (unit 333).
    I then added a selection to only display people in units with Personnel SubArea 'OTEC'. Now I get no results output. When I look in PPOME, I can see that unit 333 has Personnel SubArea 'OTEC' but it is inherited from '111'.
    In PP01, unit 111 has an Account Assignment entry (Info Type 1008) but 333 does not.
    Does anyone know how to report on this?
    Is there a flag somewhere that tells the LDB to check for inherited units?
    If not, any ideas if there is a function out there to find the superior unit for these sub-units?
    Thanks.

    Thanks,
    I am aware of that FM but how do I find the parent unit in a clever fashion?
    The structure could have multiple levels e.g.
    Unit 1 - Unit 2a - Unit3a......
           - Unit 2b
           - Unit 2c
    Unit 1 is the parent and all the below units inherit from it.
    The LDB is looping through an internal table with a list of the units. It finds Unit 1 but not the rest.
    So, when the LDB is looking for Unit 3a, how does it know that Unit 1 is the parent?
    If I use that FM, I think I would have to look for all units above it and see if there is an Info Type 1008 exists. Seems like a lot of processing for something that should be simple?
    Kroc.

  • How to pass a default value in selection screen of logical database pnpce

    Dear All,
    Can any one tell me how to pass a default value in selection screen of logical database pnpce .
    Regards
    Rakesh Singh

    Hi Rakesh,
    Go to SE36 (logical database Builder).First enter PNPCE in Logical Database and press documentation,here you will get the details of exactly what is PNPCE and how it works.After that select selections in subojects in se36 only and enter display ,there you have the include from where you acn get the idea.
    Regards,
    Rahul

  • Logical Database (PNPCE) , selection screen hide.

    Hi Gurus,
             i have couple of questions related to logical database pnpce.
    1.Since i know logical database has there own selection screen , my requirement is i want to add my custom fields to the selection screen other than what is provided is it possible or not.
    2. i want to hide the selection screen of the logical database, but i do want to create my own in which i will be declaring some select options of the standard logical database screen has, like pernr, organisation unit, etc, how do i communicate the entered data with the logical database if i dont use the logical database standard selection screen, hope i could able to explain my problem, please see into my problem and let me know thanks in advance,
    hussaini

    Hussain,
    LDB have standard selection screens, if at all you want to customize those standard selection screen you would have to define a report category for your program. You`ll have to configure in the spro settings for your corresponding report category.
    If you would like to declare your own selection criteria, you can very well do it and these criteria are visible below the standard selection criteria. You can process these elements in your program and not in the LDB standard program. Use the normal selection screen events in your program for processing your selection criteria.
    Hope this info is helpful, reward points if convinced.
    Regards

  • How to extend dynamic selection for Logical Database PNPCE

    Hi All,
    I need to extend dynamic selection for Logical Database PNPCE. Can someone able to help with steps?
    Thanks
    Ranjith

    Hi All,
    I need to extend dynamic selection for Logical Database PNPCE. Can someone able to help with steps?
    Thanks
    Ranjith

  • HR Reporing Payroll using Logical Database PNPCE

    Hi ALL
    Can any body explain me how can we do HR Payroll reporing using logical database PNPCE.
    In the program attibutes as mentioned we need to scee 900 for payroll reporting, but when I use PNPCE I cant see that screen in the Dropdown.
    can any body help me with this.
    regards
    AJ

    check this program..
    REPORT    ZHR_PAYROLL_EX1
               MESSAGE-ID ZZ
               LINE-SIZE 132
               LINE-COUNT 64(2)
               NO STANDARD PAGE HEADING .
                  T A B L E S                                            *
    TABLES    : PA0001 ,        "Infotype 0001
                 PCL1,           "HR Cluster 1
                 PCL2,           "HR Cluster 2
                 T549A,          "Payroll Accounting Areas
                 T549Q.          "Payroll Periods
                  I N C L U D E S                                        *
    *--Standard Include for US Payroll
    INCLUDE RPC2RUU0.            "Cluster RD data definition
    INCLUDE RPC2CD00.            "Cluster CD Data-Definition
    INCLUDE RPC2CA00.            "Cluster CA Data-Definition
    INCLUDE RPC2RX00.            "Cluster RF data definition internat. part
    INCLUDE RPPPXD00.            "Data definition buffer PCL1/PCL2
    INCLUDE RPPPXD10.            "Common part buffer PCL1/PCL2
    INCLUDE RPPPXM00.            "Buffer handling routine
                    INTERNAL TABLES
    *Internal Table to Hold data from PA0001
    DATA : BEGIN OF I_0001 OCCURS 0,
              PERNR LIKE PA0001-PERNR,  "Personnel Number
            END OF I_0001.
    *Internal Table to Hold data from PA0001
    DATA : BEGIN OF I_FINAL OCCURS 0,
              PERNR LIKE PA0001-PERNR, "Personnel Number
              GAMNT LIKE PC207-BETRG,  "Gross Amount
              NTAMT LIKE PC207-BETRG,  "Net Amount
              PAYDT LIKE PC261-PAYDT,  "Pay Date
              RUNDT LIKE PC261-RUNDT,  "Run Date
              VORNA LIKE PA0002-VORNA,  "First Name
              NACHN LIKE PA0002-NACHN,  "Last Name
            END OF I_FINAL.
    *Internal Table to Hold data from PA0002
    DATA : BEGIN OF I_0002 OCCURS 0,
              PERNR LIKE PA0002-PERNR,  "Personnel Number
              VORNA LIKE PA0002-VORNA,  "First Name
              NACHN LIKE PA0002-NACHN,  "Last Name
            END OF I_0002.
    Control record type
    TYPES     : BEGIN OF T_T569V,
                   ABKRS    LIKE T569V-ABKRS, "Personnel Area
                   PABRJ    LIKE T569V-PABRJ, "Accounting year
                   PABRP    LIKE T569V-PABRP, "Accounting period
                   STATE    LIKE T569V-STATE, "Status of Control Record
                   ADRUN    LIKE T569V-ADRUN, "HR: Special payroll run
                 END   OF T_T569V.
                      STRUCTURES
    DATA : WA_T569V TYPE T_T569V.    " Work area for t569v
                     DATA
    DATA : V_PABRJ  LIKE T569V-PABRJ,  "Accounting year
            V_PABRP  LIKE T569V-PABRP,  "Accounting period
            V_BEGDA  LIKE SY-DATUM,     "Begin Date
            V_ENDDA  LIKE SY-DATUM,     "End Date
            V_FPPER(6) TYPE C,          "For Period
            V_SEQNR  LIKE PC261-SEQNR.  "Sequence Number
       SELECTION SCREEN
    Selectio Screen Block for Employee Selection.
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
    SELECT-OPTIONS : S_PERNR FOR PA0001-PERNR, "Pernr
                      S_DATE  FOR SY-DATUM.     "Date
    SELECTION-SCREEN END OF BLOCK B1.
       START-OF-SELECTION
    START-OF-SELECTION.
    *Get Data from pa0001
       PERFORM GET_DATA_FROM_0001.
    *Get Data from pa0001
       PERFORM GET_DATA_FROM_0002.
    *Get CHAD Details
       PERFORM GET_PAYDATA.
       END-OF-SELECTION
    END-OF-SELECTION.
       IF NOT I_FINAL[] IS INITIAL.
    *Print the Final Report.
         PERFORM PRINT_REPORT.
       ENDIF.
                    T O P  O F  P A G E
    TOP-OF-PAGE.
    Display Header
       PERFORM DISPLAY_HEADER.
                    S U B - R O U T I N E S
    *&      Form  get_data_from_0001
          Get Data from 0001
    FORM GET_DATA_FROM_0001.
       SELECT PERNR                     "Personnel Number
              FROM PA0001
              INTO TABLE I_0001
              WHERE PERNR IN S_PERNR AND
                    ENDDA >= S_DATE-LOW AND
                    BEGDA <= S_DATE-HIGH .
       IF SY-SUBRC = 0.
         SORT I_0001 BY PERNR.
       ENDIF.
    ENDFORM.                    " get_data_from_0001
    *&      Form  get_data_from_0002
          Get Data from 0002
    FORM GET_DATA_FROM_0002.
       SELECT PERNR                     "Personnel Number
              VORNA
              NACHN
              FROM PA0002
              INTO TABLE I_0002
              WHERE PERNR IN S_PERNR AND
                    ENDDA >= S_DATE-LOW AND
                    BEGDA <= S_DATE-HIGH .
       IF SY-SUBRC = 0.
         SORT I_0002 BY PERNR.
       ENDIF.
    ENDFORM.                    " get_data_from_0002
    *&      Form  populate_chad_coinage_table
          text
    FORM GET_PAYDATA.
       LOOP AT I_0001.
         READ TABLE I_0002 WITH KEY PERNR = I_0001-PERNR BINARY SEARCH.
         IF SY-SUBRC = 0.
           I_FINAL-VORNA = I_0002-VORNA.
           I_FINAL-NACHN = I_0002-NACHN.
         ENDIF.
    Read Result Directory for Payroll Results for a Employee.
         PERFORM CU_READ_RGDIR.
    Get Sequence Number & Associated Payroll Results.
         PERFORM GET_PAYROLL_RESULTS.
       ENDLOOP.
    ENDFORM.                    " get_paydata
    *&      Form  cu_read_rgdir
          Reag rgdir to get the results with conty grouping 'TD'
    FORM CU_READ_RGDIR.
       DATA : V_MOLGA  LIKE T500L-MOLGA ."Country Grouping
    *Call function module to get Results
       CALL FUNCTION 'CU_READ_RGDIR'
         EXPORTING
           PERSNR          = I_0001-PERNR
         IMPORTING
           MOLGA           = V_MOLGA
         TABLES
           IN_RGDIR        = RGDIR
         EXCEPTIONS
           NO_RECORD_FOUND = 1
           OTHERS          = 2.
       SORT RGDIR BY SEQNR.
    ENDFORM.                    " cu_read_rgdir
    *&      Form  get_payroll_results
          Get Sequence number
    FORM GET_PAYROLL_RESULTS.
       LOOP AT RGDIR WHERE   SRTZA = 'A' AND
                         VOID IS INITIAL AND
                         REVERSAL IS INITIAL AND
                         OUTOFSEQ IS INITIAL AND
                         PAYDT    IN S_DATE.
         V_SEQNR = RGDIR-SEQNR.
    *-- Macro Call for Germany
         RP-INIT-BUFFER.
         RX-KEY-PERNR = I_0001-PERNR.
         RX-KEY-SEQNO = V_SEQNR.
         RP-IMP-C2-RU.
         LOOP AT RT WHERE LGART = '/559'.
           I_FINAL-PERNR = I_0001-PERNR.
           I_FINAL-GAMNT = RT-BETRG.
           I_FINAL-PAYDT = RGDIR-PAYDT.
           I_FINAL-RUNDT = RGDIR-RUNDT.
           APPEND I_FINAL.
           CLEAR  I_FINAL.
         ENDLOOP.
       ENDLOOP.
    ENDFORM.                    "get_payroll_results
    *&      Form  display_header
          Display Header
    FORM DISPLAY_HEADER .
       FORMAT COLOR 1.
       ULINE.
       WRITE:/1 SY-VLINE,
             (15) 'Empl Number',
             SY-VLINE,
             (20) 'First Name',
             SY-VLINE,
             (20) 'Last Name',
             SY-VLINE,
             (15) 'Pay Date',
             SY-VLINE,
             (15) 'Run Date',
             SY-VLINE,
             (25) 'Gross Amount',
             132 SY-VLINE.
       ULINE.
       FORMAT COLOR OFF.
    ENDFORM.                    " display_header
    *&      Form  print_report
          Display Report
    FORM PRINT_REPORT .
       LOOP AT I_FINAL.
         WRITE:/1 SY-VLINE,
               (15) I_FINAL-PERNR,
               SY-VLINE,
               (20) I_FINAL-VORNA,
               SY-VLINE,
               (20) I_FINAL-NACHN,
               SY-VLINE,
               (15) I_FINAL-PAYDT,
               SY-VLINE,
               (15) I_FINAL-RUNDT,
               SY-VLINE,
               (25) I_FINAL-GAMNT,
               132 SY-VLINE.
         ULINE.
       ENDLOOP.
       SKIP 2.
       WRITE:/1 'Period Begin Date:',(25) V_BEGDA.
       WRITE:/1 'Period End   Date:',(25) V_ENDDA.
    ENDFORM.                    " print_report

  • Logical database PNPCE

    Hi
      I have created a custom OM infotype 9910 which will data with Object ID either 'O' (Org Unit) or S (Position) .
    I am using Logical database PNPCE in my report. I have declared the infotype at the declaration part with infotypes 9910 statement
    When the get peras event is triggered in program the table p9910 is not filled with values even though there is record in HRP9910 with Object ID 'S' for the employee position who i am interested in.
    I think there is some link missing. For the OM infotype records to be filled during get peras event do i need to give any other selection value like evaluation path or i have to use a different event. Please advice
    Suitable answers will be rewarded
    Thanks,
    Kasi

    I don't think PNPCE does anything with HRP infotypes.  PNPCE is all about PA data since PERNR is the main key.  Logical DB PCH is the one that deals with HRP Infotypes.

  • SQ01 - Name of Manager field for logical database PNPCE

    Hi,
    I am stumped and need your help.
    I have defined an infoset ZZ_HR_DATA with logical database. In the Infotype 0001, under additional selections, I have the field "Name of superior (organizational assignment)" and it's technical name is SYHR_A_P0001_AF_MANAGERN. I am OK so far.
    When I define a query against this info type, it is not showing as a field to select. What went wrong?
    The query shows another similar field SYHR_A_P0001_AF_MANAGERN and Quickviewer is displaying this as well.
    Regards
    Venny

    I figured this out. User error..
    Thanks
    Venny

Maybe you are looking for