Parameters in a logical database

Hi all,
Why Parameters defined in a logical databse are not like those defined in a report program?
And what we can do with those one wich declare in a logical database?
Thanks.

hi check this..
if you want to get the data from the LDB you can give the values in the standard screen given and execute it will work like a report but what happens here is the screen comes automatically...and you can disable the screen as said by srinivas gurram reddy....check the simple program...
with logical data base..PNP. copy this and execute it and give the values in the selection screen...
TABLES:PERNR.
INFOTYPES:0002,0008.
GET PERNR.
PROVIDE * FROM P0002  BETWEEN PN-BEGDA AND PN-ENDDA.
ENDPROVIDE.
PROVIDE * FROM P0008  BETWEEN PN-BEGDA AND PN-ENDDA.
ENDPROVIDE.
IF SY-SUBRC = 0.
WRITE:/ P0002-PERNR,P0002-BEGDA,P0002-ENDDA,P0002-VORNA,P0008-ANSAL,P0008-PREAS.
ENDIF.
regards,
venkat

Similar Messages

  • Report Parameters with logical database

    Hello
    I have to read some HR infotypes that are provided with the logical database PNPCE.
    Fort his i have written a report that will use my logical database and get some information.
    What i need,are some new input parameters on the screen that are added by my report:
    parameters: p_persnr type person-pernr,
                        p_name type p0002-nachn,
                        p_sname type p0002-vorna.
    The problem is that i do not know how to link these parameters to my logical database reading.
    When i try to call "get <node>" ,my report is not returning anything.
    Is there a way to send  my parameters as selection parameters to the logical database?
    thank you

    The selection screen 1000 is created dynamically during runtime. I doubt change done by SE51 will solve the issue. In fact there is some code which can help on this.
    INITIALIZATION.
    To restrict the range of PERNRs
      PERFORM z_seloption_restrict USING 'PNPPERNR'.
    *&      Form  Z_Seloption_Restrict
    * Restrict range in select option
    *      -->VALUE(SOP_NAME)  Name of select option as string
    FORM z_seloption_restrict USING value(pv_sop_name).
      IF st_restrict-opt_list_tab[] IS INITIAL.
        CLEAR st_opt_list.
        MOVE: 'EQ' TO st_opt_list-name,
              'X'  TO st_opt_list-options-eq.
        APPEND st_opt_list TO st_restrict-opt_list_tab.
      ENDIF.
      REFRESH : st_restrict-***_tab.
    *  READ TABLE st_restrict-***_tab INTO st_asst
    *                        WITH KEY name = pv_sop_name.
    *  IF sy-subrc NE 0.
      CLEAR st_asst.
      MOVE: 'S'         TO st_asst-kind,
            pv_sop_name TO st_asst-name,
            'I'         TO st_asst-sg_main,
            ' '         TO st_asst-sg_addy,
            'EQ'        TO st_asst-op_main.
      APPEND st_asst TO st_restrict-***_tab.
    *  ENDIF.
      CALL FUNCTION 'SELECT_OPTIONS_RESTRICT'
        EXPORTING
          restriction = st_restrict.
    ENDFORM.                    "Z_Seloption_Restrict

  • Re: logical database

    Hi,
        What is the logical database. I know how to create.
    I think it is useful for dynamic selections of parameters.
    This logical databases use by HR ABAP. Is it right?
    But i heard that these will increase performnace of ur coding. How can u justify these doubts.
    rgds
    p.kp

    Hi paluri,
    1. What is the logical database
       Logical database is nothing
       but a program only,
       which provides the facility of
       a)pre-defined seleciton secreen
       b) facility for GETting records
         (without knowint the databse tables)
    2.   logical databases use by HR ABAP. Is it right?
        Yes, absolutely right. Its mostly used
        in HR.
       But it is also used now a days in other modules
       like FI, SD.
    3. But i heard that these will increase performnace of ur coding
       Yes, it will increase the performanc,e
       in the sense, that,
       the SQL, FMs used for fetching from the database
       is already fine tuned and written
       into the already tested program of logical database.
    regards,
    amit m.

  • How does works default parameters in a program with logical database PNP?

    Hi Friends,
      I have a basic program, i need to filter info with period parameters in a program that uses logical database PNP, but it doesn't work.
      If i use "person selection period" that it's suposed to filter info according to infotype 0001 (as the sap help says), it doesn't work, i use: PNPBEGPS = today and PNPENDPS = today, and the result it's a lot of registers that doesn't meet that criteria.
      Also i tried with: data selection period, today, up to day, current month. And the result it's with the same problem.
      How does works period parameters in a program with logical database PNP?
    This it's the program example, i use the default category.
    REPORT  ZRPHRTEST.
    tables: pernr.
    infotypes: 0001.
    start-of-selection.
    get pernr.
      write: pernr-pernr, p0001-begda, p0001-endda.
    end-of-selection.
    write 'fin'.

    Hi,
    Define pernr table under tables statement then and use GET PERNR event.This get event is followed by End-Of-Selection.
    Syntax: Tables pernr.
                Get pernr.
    Try, activate and test. This should solve your problem.
    Regards,
    Abhijeet

  • How to get the selection parameters from logical database into one of the t

    Hi Sap ABAP Champians,
    How to get the selection parameters from logical database into one of the tab in the tabstrip selection-screen.
    Please help me for this
    Thanks
    Basu

    Hi
    Thanks, that will work, but then I'll have to insert code into all my reports.
    I can see that "Application Server Control Console" is able to rerun a report.
    This must mean that the Report Server has access to the runtime parameters.
    But how?
    Cheers
    Nils Peter

  • Position of parameters of a report using a Logical Database

    Hallo all,
    Is there any way that I can make the parameters defined by me in a report to appear <b>before</b> the ones defined by the Logical Database it is using ?
    I searched but I couldn't find something relevant.
    I would like to avoid having to copy and modify the LDB program.
    Thanks

    Here are a couple of things you can do:
    1.  Right-click on the subreport and select "Format Subreport...".  Turn off the borders on the subreport.
    2.  Right-click on the subreport and select "Size and Position".  Set the X and Y coordinates both to 0.  This will place the subreport at the top-left of the section where it's located.
    3.  In the subreport, suppress ALL of the sections that you're not using.
    4.  Make the height of the subreport fairly small - it will expand to the size of the data it contains.
    5.  Put the column labels in the Page Header of the main report, using markers on the ruler to identify the placement of the left side of each column header.  Be sure to line the markers up to a specific "tick mark" on the ruler.
    6.  In the subreport, place markers at the same tick-marks on the rule as you used for the column labels on the main report.  Then align the fields in the subreport with the markers.
    This should get you close to the format you're looking for.  If it's not exact, you can look at the report in Preview and tweak the position of the column labels to match the data in the subreport.
    -Dell

  • Using infoset based on logical database gives lots of selection parameters

    Hi
    I'm trying to assist a new Crystal user in getting up on running on Crystal using infosets from SAP. Presently a simple infoset based on logical database PNPCE has been built using fields from just three infotypes (to keep things simple).
    When the user logs onto crystal and selects either this infoset, or a query based on the infoset, the very next step requires the user to set 80+ parameters to be null before running the report, and unfortunately those values cannot be saved to if in order to re-run the user has to manually set all the vallues to null again. Clearly this makes it pretty frustrating to use!
    This initial screen does not appear if using an infoset based on table joins, but unfortunately the logical database needs to be used to fulfill certain reporting requirements.
    I've tried saving a selection variant against a query and forcing it's use but these setting don't seem to be picked up by Crystal.
    Are there any Crystal/Query experts out there that can help with this?
    Regards
    Phil

    Hi,
    Is there anyone out there that can help with this? Seems to me like an issue that there 'should' be a soluton to...but I haven't found it yet!
    As a bit of additional info - the use of table join based infosets is not an option primarily because there are a lot of reports required that pull in the OM 'additional fields' that come through automatically when using an LDB. However, for table joins, it requires custom coding to be required to the infoset, which clearly restricts the user base from the ability to build their own reports.
    Regards
    Phil

  • Change selection screen in LDB (KDF logical database - NOT HR)

    Hi All,
    Iu2019d like to use KDF logical database to keep the dynamic selections since user wants to use it but I need to change the selection screen itself. The existing variants for KDF donu2019t meet the user requirements. Some fields I need to hide some add. Like I want to u201Cremoveu201D the field u2018Posting periodu2019 (MONAT) (which is available in dynamic selection screen) and put it on the u201Cmainu201D selection screen.
    Do I need to create my own logical database or there is a way around?
    Could someone give me a practical advice or sample of solution?
    Thanks a lot.

    Thanks Himanshu,
    I did as you suggested but problem is that it does not allow me to hide the whole block.
    I have 3 filelds actually on block KD_0 I need to hide (its from selection screen of KDF logical database.)
      SELECT-OPTIONS: KD_LIFNR FOR LFA1-LIFNR MATCHCODE OBJECT KRED.
      SELECT-OPTIONS: KD_BUKRS    FOR  LFB1-BUKRS.
    SELECTION-SCREEN END OF BLOCK KD_0.
    PARAMETERS KD_INDEX AS SEARCH PATTERN FOR TABLE LFA1.
    What I did is below.  I used sp instead of  u201C=u201D since it has many screen for field KD_LIFNR(for frame, text etc).
    And when I did just for KD_LIFNR it was hidden but when I did the same for KD_BUKRS it was not hidden . The field has stars u201C*********u201D in it.
    Same happen with KD_INDEX. The name of the field is hidden but field not and it filled with ********. Do you have any ideas what it can be?
    I debugged it to catch all screen names but no luck
      loop at screen.
        if screen-name cp 'KD_LIFNR' or
        screen-name cp 'KD_BUKRS' or
        screen-name cp 'KD_INDEX' or
        screen-name = '%B000003_BLOCK_1000' or       
        screen-name = 'SSCRTEXTS-FRAME_TEXT' or
        screen-name = 'SSCRTEXTS-MCID_TEXT' or
        screen-name = 'SSCRTEXTS-STRNG_TEXT' or
        screen-name = 'SSCRFIELDS-SEARCH_BTN' or
        screen-name =  '%B025008_BLOCK_1000' or
        screen-name =  '%F021010_1000' or
        screen-name =  'ALCUR' or
        screen-name =  '%F022012_1000' or
        screen-name =  'EXCDT' or
        screen-name = 'SSCRFIELDS-UCOMM'.
          screen-invisible = '1'.
          modify screen.
        endif.
      endloop.

  • ABAP Logical Database ADA

    Hi All, I am quite familiar with Logical Databases but I need to understand the following.
    1) I am using LDB ADA, but I want to use my own Selection Screen and not the default one that the LDB provides. I know I must put something in AT SELECTION-SCREEN but am unsure what.
    2) Once I get the data, I want to store the data in an internal table - how do I go about doing this? If you can provide a code example that would be great.
    Points for any relevant help.

    Hi,
    A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
    Logical database structures
    There are three defining entities in an SAP logical database. You must be clear on all three in order to create and use one.
    Table structure: Your logical database includes data from specified tables in SAP. There is a hierarchy among these tables defined by their foreign keys (all known to SAP), and you are going to define a customized relationship between select tables. This structure is unique and must be defined and saved.
    Data selection: You may not want or need every item in the referenced tables that contributes to your customized database. There is a selection screen that permits you to pick and choose.
    Database access programming: Once you’ve defined your logical database, SAP will generate the access subroutines needed to pull the data in the way you want it pulled.
    Creating your own logical database
    Here’s a step-by-step guide:
    1) Call up transaction SLDB (or transaction SE36). The path you want is Tools | ABAP Workbench | Development | Programming Environment | Logical Databases. This screen is called Logical Database Builder.
    2) Enter an appropriate name in the logical database name field. You have three options on this screen: Create, Display, and Change. Choose Create.
    3) You’ll be prompted for a short text description of your new logical database. Enter one. You’ll then be prompted to specify a development class.
    4) Specify a root node, or a parent table, as the basis of your logical database structure. You can now place subsequent tables under the root table as needed to assemble the data object you want. You can access this tree from this point forward, to add additional tables, by selecting that root node and following the path Edit | Node | Create. Once you’ve saved the structure you define in this step, the system will generate the programming necessary to access your logical database. The best part is you don’t have to write a single line of code.
    Noted point is we cant add any selection criteria thru our se38 program if you are attaching any LDB to program.Ist of no use.
    If you want to change selection criteria to the existing LDB, you have to goto SE36 tcode and provide LDB name and choose "Change" mode by selecting "Selections" Radio button.
    declaration of params is different compared to normal se38 program in some aspects.
    PARAMETERS :p_curr LIKE bkpf-waers FOR TABLE bkpf OBLIGATORY.
    this BKPF table should be one of the node in the "Structure" Radio button.
    Thanks
    Sivaparvathi
    Please reward points if helpful.

  • How to make use of logical database in reports?

    hi,
    I am working on a Cash Flow Forecast report, which requires the usage of 'PSJ' Logical Database for the selection screen with Profit Center(PRCTR) as one field and the other field being Period ( in MM/YYYY format).
    I have not worked on Logical Database before. Since, its for the first time I am working on LDB, I require help on it.
    How to proceed for this, can someone help me with it?
    On receiving further inputs, I will proceed and might come up with some more queries.
    Regards,
    Ravi

    Hi Hari,
    Thanks a lot for being so patient. yeah, I will just send you a code snippet of mine. My code is of 3000 Lines. Hence, I will send few parts of it. Just go through and let me know if you need any further information from my side.
    Here is the snippet:
    *& TABLES
    TABLES: PROJ,                              "Project definition.
            PRPS,                              "WBS Element Master Data
            COSP,                              "CO: External Table.
            COFP,                              "CO: External Table.
            SETLEAF,                       "Value in sets.
            FAGLFLEXT,                         "Profit Center.
            S031,                              "Statistics: Movements for Current Stocks.
            SETHEADERT,                        "short Description of Sets.
            AFVC,                              "Operation within an Order.
            AUFK,                              "Order master data.
            PRHI,                              "Work Breakdown Structure.
            AFKO,                              "Order header data PP orders.
            NRIV,                              "Number range Intervals.
            SKB1,                              "G/L Account Master (company code).
            FMCI.                              "Commitments Item master data.
    Type Pool
    TYPE-POOLS: SLIS.
    FIELD-SYMBOLS: <DYN_TABLE> TYPE STANDARD TABLE,
                   <DYN_WA>,
                   <DYN_FIELD>.
    DATA: COUNT TYPE I,
          D_PERIOL LIKE COFP-PERIO,
          D_PERIOH LIKE COFP-PERIO,
          D_GJAHRL LIKE COFP-GJAHR,
          D_GJAHRH LIKE COFP-GJAHR,
          D_GJAHR LIKE COFP-GJAHR,
          D_PERIO LIKE COFP-PERIO,
          OBJNR LIKE COSP-OBJNR,
          PKOKR LIKE PRPS-PKOKR,
          G_NRLEVEL LIKE NRIV-NRLEVEL,
          G_BELNR LIKE COFP-BELNR,
         I_OBJ-OBJNR LIKE COFP-OBJNR,
          G_OPNGBAL LIKE FAGLFLEXT-HSL01,
          G_PAYROLL LIKE COSP-WKG001,
          G_PYROL_TAX LIKE COFP-WKGBTR,
          G_PENSION LIKE COFP-WKGBTR,
          G_BTLDGR LIKE COFP-WKGBTR,
          G_REIMPYMT LIKE COFP-WKGBTR,
          G_INTCORCPT LIKE COFP-WKGBTR,
          G_CAPEXP LIKE COFP-WKGBTR,
          G_SLSLDGR LIKE COFP-WKGBTR,
          G_REIMRCPT LIKE COFP-WKGBTR,
          G_TOTPYMNTS LIKE COFP-WKGBTR VALUE 0,
          G_TOTRECPTS LIKE COFP-WKGBTR VALUE 0,
          G_MVMTFRMNTH LIKE COFP-WKGBTR VALUE 0,
          G_CLSGBAL LIKE COFP-WKGBTR VALUE 0.
    DATA: LYEAR(4) TYPE N,
          LMONTH1(2) TYPE N,
          MON1(2) TYPE N.
    DATA: HYEAR(4) TYPE N.
    DATA: LMONTH(2) TYPE N.
    DATA: HMONTH(2) TYPE N.
    DATA: TOTAL(10) TYPE N.
    DATA: SUM(10) TYPE N.
    DATA: G_PSPID LIKE PROJ-PSPID.
    DATA: TOTAL1 LIKE COFP-WKGBTR,
          TOTAL2 LIKE COFP-WKGBTR.
    DATA: G_KOKRS LIKE COFP-KOKRS,
          G_FIPOS LIKE SKB1-FIPOS,
          G_POSIT LIKE COFP-POSIT,
          G_BUKRS LIKE COFP-BUKRS.
    DATA: L_RACCT LIKE FAGLFLEXT-RACCT VALUE '0000220000',
          H_RACCT LIKE FAGLFLEXT-RACCT VALUE '0000227999'.
    DATA: I TYPE I VALUE '74'.
    DATA: P TYPE I VALUE '62'.
    *& SELECT-OPTIONS
    PARAMETERS : S_PRCTR LIKE PROJ-PRCTR.         "Profit Center
    SELECT-OPTIONS: SL_SPMON FOR S031-SPMON OBLIGATORY.            "Period
    *INITIALIZATION
    INITIALIZATION.
      SL_SPMON-SIGN = C_IN.
      SL_SPMON-OPTION = C_BT.
      SL_SPMON-LOW = SL_SPMON.
      SL_SPMON-HIGH = SL_SPMON.
      APPEND SL_SPMON.
    AT SELECTION-SCREEN
    Event which occurs each time the user hits enter on the selection
    Screen.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR SL_SPMON-LOW.
      PERFORM MONAT_F4.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR SL_SPMON-HIGH.
      PERFORM MONAT_F4.
      SELECT SINGLE * FROM PROJ WHERE PRCTR = S_PRCTR.
      IF SY-SUBRC <> 0 AND NOT ( S_PRCTR IS INITIAL ).
        MESSAGE E019.
      ENDIF.
    ALL WBS ELEMENT SELECTION
      SELECT PSPID INTO TABLE I_PROJTAB FROM PROJ WHERE PRCTR = S_PRCTR.
      IF SY-SUBRC = 0.
        LOOP AT I_PROJTAB.
          CALL FUNCTION 'GET_TREE_FROM_PRHI'
            EXPORTING
              I_POSID                   = I_PROJTAB-PSPID
       I_PSPNR                   = 00000000
       NO_BUFFER                 = ' '
            TABLES
              PSP_TREE                  = I_PRHI
            EXCEPTIONS
              INPUT_ERROR               = 1
              PSP_HIERARCHY_ERROR       = 2
              PSP_NOT_FOUND             = 3
              OTHERS                    = 4
       ENDLOOP. " PROJTAB
      ENDIF.
      SELECT * FROM PRPS INTO TABLE I_PRPSVC FOR ALL ENTRIES IN I_PRHI
                      WHERE PSPNR = I_PRHI-POSNR.
      SELECT * FROM AFVC INTO TABLE I_AFVC FOR ALL ENTRIES IN I_PRPSVC
                      WHERE PROJN = I_PRPSVC-PSPNR.
      SELECT * FROM AUFK INTO TABLE I_AUFK FOR ALL ENTRIES IN I_PRPSVC
                      WHERE PSPEL = I_PRPSVC-PSPNR AND AUTYP NE C_TWENTY.
      SELECT OBJNR FROM PRPS INTO TABLE I_OBJ FOR ALL ENTRIES IN I_PRHI
                      WHERE PSPNR = I_PRHI-POSNR.
      IF SY-SUBRC <> 0.
        MESSAGE E010.
      ENDIF.
    I hope that's of some use.
    Thanks & Regards,
    Ravi

  • Select options for the pnp logical database.

    Hi ,
    We get a default selection screen when we use logical database in HR ABAP.
    But we always get the selection elements as "PARAMETERS" and not as "SELECT-OPTIONS".
    How can we change it to select options ....
    I tried all the options in HR- Report categories but it is not working..
    Kindly Help..
    Regards,
    Ashwin.

    >
    ASHWIN JOHARI wrote:
    > Hi ,
    > But we always get the selection elements as "PARAMETERS" and not as "SELECT-OPTIONS".
    > Ashwin.
    Which fields? Almost all of them are defined SELECT-OPTIONS.. you dont' see the range option directly.. click on he options icon & you can enter the ranges.
    ~Suresh

  • Selection screen for logical database PNP..

    hi all,
    I am having a requirement to produce a HR Report where i need to use logical database PNP. Now the issue is i need to supress some of the elements of standard selection screen of PNP and add a couple of fields of mine.
    i have been looking all around and i got few of the below methods.
    its good to use a report category.
    somewhere it says include it in ur program using selection screen block..
    can you please guide me which is the best way and what would be a perfect solution?
    thanks in advance,
    Reena

    Hi reeena,
    1. simple
    2. u want to
      a) add ur own fields
      b) suppress some fields
    3. a) is simple, just add your parameters,
       in your program, and they will appear
       b) use SCREEN logic
    4. just copy paste to get a taste of it
      (it will HIDE the PAYROLL AREA field)
      and add MATNR field
    5.
    report abc.
    TABLES : PERNR.
    PARAMETERS : MATNR LIKE MARA-MATNR.
    AT SELECTION-SCREEN OUTPUT.
      LOOP AT SCREEN.
        IF SCREEN-NAME CS 'ABKRS'.
          SCREEN-INVISIBLE = '1'.
          SCREEN-INPUT = '0'.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    regards,
    amit m.

  • Selection screen of logical database PCH

    Hi all,
    I am writing a report using the logical database PCH. For this report I need the full selection screen of the logical database, especially the structure parameters. However, wenn I test my program, I only get a reduced selection screen without the structure parameters and the "further conditions". According to the documentation I found, this behaviour appears when you set the selection screen version to '900' in the program attributes. In my program, the selection screen version is empty, and I still get the reduced screen. The missing selection fields are even totally unknown to the ABAP compiler. E.g. when I try to assign the field PCHWEGID in my report, I get a "field unknown" error message from the compiler.
    I have compared my report in various aspects to the standard report RHSTRU00 which shows the behaviour I want, I did not find any difference, and yet I get a different behaviour.
    Any ideas how to fix this?
    Thank you
    Alexandre

    Hi,
    Did you declare the below statement?
    TABLES: OBJEC, GDSTR.
    Regards,
    -Sandeep

  • Logical database PTRVP

    hi All,
    I want to change the selection screen for logical database PTRVP, is it possible to change it without changing the database selection program ?
    I tried to look out for selection category for this LDB [ like HR LDBs] but dint find any.
    can you please advise
    thanks

    this is a part of sap library.
    abap progarmming -> logical database ->
    The generated default selection include would look like this:
    Include DBTEST_LDBSEL
    It will be automatically included into the database program
    If the source is automatically generated,
    please perform the following steps:
    1. Replace ? by suitable names (at most 8 characters).
    2. Activate SELECT-OPTIONS and PARAMETERS (delete stars).
    3. Save source code.
    4. Edit database program.
    Hint: Syntax-Check is not possible within this Include!
    It will be checked during syntax-check of database program.
    SELECT-OPTIONS : ? FOR LFA1-LIFNR.
    Parameter for search pattern selection (Type SY-LDB_SP):
    PARAMETERS p_sp AS SEARCH PATTERN FOR TABLE LFA1.
    SELECT-OPTIONS :
    ? FOR LFB1-LIFNR,
    ? FOR LFB1-BUKRS.
    SELECT-OPTIONS :
    ? FOR LFC1-LIFNR,
    ? FOR LFC1-BUKRS,
    ? FOR LFC1-GJAHR.
    SELECT-OPTIONS :
    ? FOR BKPF-BUKRS,
    ? FOR BKPF-BELNR,
    ? FOR BKPF-GJAHR.
    Enable DYNAMIC SELECTIONS for selected nodes :
    Enable FIELD SELECTION for selected nodes :
    If the nodes LFA1 and LFB1 are defined for dynamic selections, and node LFC1 is defined for field selections, the following lines of code will also be generated:
    SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE LFA1.
    SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE LFB1.
    SELECTION-SCREEN FIELD SELECTION FOR TABLE LFC1.
    The automatically-created selection include could be modified as follows:
    Selection criteria:
      SELECT-OPTIONS SLIFNR  FOR LFA1-LIFNR.
      SELECT-OPTIONS SBUKRS  FOR LFB1-BUKRS.
      SELECT-OPTIONS SGJAHR  FOR LFC1-GJAHR.
      SELECT-OPTIONS SBELNR  FOR BKPF-BELNR.
    Self-defined parameters:
      PARAMETERS PSTIDA LIKE SY-DATUM FOR NODE BKPF.
    Dynamic selections for LFA1 and LFB1:
      SELECTION-SCREEN DYNAMIC SELECTIONS FOR NODEE: LFA1, LFB1.
    Field selection for LFB1 and LFC1:
      SELECTION-SCREEN FIELD SELECTION FOR NODE: LFB1, LFC1.
    Here, selections are chosen from the available selection criteria and are given names. An additional parameter PSTIDA is declared and linked to the node BKPF. Dynamic selections are defined for the tables LFA1 and LFB1. Field selections are defined for tables LFB1 and LFC1.
    Edited by: Mohit Kumar on Feb 4, 2009 11:47 AM

  • Selection screen for HR report with logical database PNP

    Hi All,
       I am writing a HR report. And I use the logical database PNP. Also I create a HR report category for this report. In the report category, I can define the selection screen field. But all these fields are selection option format. My question is How can I add parameters, radiobutton group and checkbox in the selection screen. Thanks.
    Alex

    Hi Alex,
    Sorry for replying so late. Please try this tutorial:
    w w w. s a p t e c h n i c a l. c o m -> tutorials -> ABAP-HR -> Creating HR Report category in PNP logical database
    Sorry, I put it like this, because direct link doens't let me post the answer. Don't know why.
    It can also be something with your custom code in selection screen. Though it works fine for, try to remove COMMENTs and observe the result. Maybe parameters are overlapping somehow. First try this:
    SELECTION-SCREEN begin of BLOCK blk2 WITH FRAME TITLE text-002.
    PARAMETERS RefDate type DATS.
    parameter BFlag type c RADIOBUTTON GROUP grp1.
    PARAMETER FFlag type c RADIOBUTTON GROUP grp1.
    parameters days type i.
    PARAMETERS spvsr like PA0001-MSTBR.
    selection-SCREEN end of BLOCK blk2.
    If that works together with the report category, try to extend it with adding a selection-screen comment, but do this in reversed order (comment goes first and FOR FIELD addition is supplied) like this:
    SELECTION-SCREEN begin of BLOCK blk2 WITH FRAME TITLE text-002.
    PARAMETERS RefDate type DATS.
    SELECTION-SCREEN begin of line.
    SELECTION-SCREEN COMMENT 3(10) text-003 for field bflag.  "FOR FIELD, and goes first
    parameter BFlag type c RADIOBUTTON GROUP grp1.
    SELECTION-SCREEN COMMENT 16(10) text-004 for FIELD fflag.  "here two
    PARAMETER FFlag type c RADIOBUTTON GROUP grp1.
    SELECTION-SCREEN end of line.
    parameters days type i.
    PARAMETERS spvsr like PA0001-MSTBR.
    selection-SCREEN end of BLOCK blk2.
    If still not working, see if text-003 and text-004 are not too long (you expect them to be 10 chars), This may somehow affect selection screen.
    You may also try with setting cursor position explicity by:
    SELECTION-SCREEN begin of line.
    SELECTION-SCREEN POSITION 3.
    SELECTION-SCREEN COMMENT (10) text-003 for field bflag. 
    parameter BFlag type c RADIOBUTTON GROUP grp1.
    SELECTION-SCREEN POSITION 16.
    SELECTION-SCREEN COMMENT (10) text-004 for FIELD fflag.  "here two
    PARAMETER FFlag type c RADIOBUTTON GROUP grp1.
    SELECTION-SCREEN end of line.
    It is really hard to identify where can be a bug as it is working fine for me. Keep trying with different variations, it should finally run with some.
    Regards
    Marcin

Maybe you are looking for