About LDB

Hai Gurus,
I am new to ABAP. and I wants to know about LDB concepts.
1. What is LDB and where it is used ?
2. I wants to step by step process with using SE36 ? (With Demo)
Please Help Me..

Hi Reddy,
Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables by linking them to executable ABAP programs.
One can attach a LDB in a report by going to GoTo--Attributes and menton the name of the LDB there.
Every LDB has a default selection screen which can or cannot be hidden.Also,one can modify it using the keyword Exclude.
By using the LDB,there is no need to write the select statement sin your program if the LDB fits your requirement.But if in case,you need data from one more table which is not included in the LDB hierarchical stucture,you can write the select statement and fetch the data.
Ideally,we do not create our own LDBs but instead can copy the standard ones and modify them accordingly and use them in the reports.
For more detailed informaton regarding the LDB,you can refer to the link below:
http://help.sap.com/saphelp_46c/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/frameset.htm
In case you have any further clarifications,do let me know.
Regards,
Puneet Jhari.

Similar Messages

Ldb enhancement

Hi experts,
I have a few doubts about ldb in hr abap.can anyone explain me....
1. how can we do enhancement for an ldb.
2. how can we make ldb selection screen field as mandatary.
Thanks in advance
Sudha
Edited by: sudharaniG on Aug 23, 2011 9:49 AM

Hi Andy,
Thanks for the response....
my requierement here is to change the selection screen of the ldb.
by default we have all the filelds with no intervals option. can we change for any field as with intervals?
Thanks
Sudha

Steps to create LOGICAL DATABASE in sap

hi guys,
i have gone through many documents about LDB. But, i didnt get the steps to create a LDB.
plz provide me with the steps to be followed to create a LDB.
thnx,
shivaa.

Hi Shiva,
This might help you!
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 youu2019ve 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
ABAP/4 (Advanced Business Application Programming language, version 4) is the language created by SAP for implementation and customization of its R/3 system. ABAP/4 comes loaded with many predefined logical databases that can construct and table just about any conventional business objects you might need in any canned SAP application. However, you can also create your own logical databases to construct any custom objects you care to define, as your application requires in ABAP/4. Hereu2019s 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. Youu2019ll be prompted for a short text description of your new logical database. Enter one. Youu2019ll then be prompted to specify a development class.
4. Now comes the fun part! You must 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 youu2019ve 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 donu2019t have to write a single line of code.
Watch out!
The use of very large tables will degrade the performance of a logical database, so be aware of that trade-off. Remember that some tables in SAP are very complex, so they will be problematic in any user-defined logical database.
Declaring a logical database
Hereu2019s another surprising feature of logical databases: You do not assign them in your ABAP/4 Code. Instead, the system requires that you specify logical databases as attributes. So when you are creating a report, have your logical database identifier (the name you gave it) on hand when you are defining its attributes on the Program Attributes screen. The Attributes section of the screen (the lower half) will include a Logical database field, where you can declare your logical database.
Logical databases for increasing efficiency
Why else would you want to create a logical database? Consider that the logical databases already available to you begin with a root node and proceed downward from there. If the data object you wish to construct consists of items that are all below the root node, you can use an existing logical database program to extract the data, then trim away what you donu2019t want using SELECT statementsu2014or you can increase the speed of the logical database program considerably by redefining the logical database for your object and starting with a table down in the chain. Either way, youu2019ll eliminate a great deal of overhead.
Reward if useful.
Thankyou,
Regards.

What exactly are Logical Database in Programs?

Hi Experts,
While digging deep into the programs, using the T-Code SE93/SE38, we come across Logical Database.
what is the functionality and use of this Logical Database?
Best Regards,

Normally moderators reject unresearched questions, but this one has not been discussed much for it's security aspects.
In the ABAP forums you will find a lot of discussions about LDB's ("LDB" is your search term).
Please do a search and reconsider and focus your question more.
What is it about LDB's that you would like to discuss?
Cheers,
Julius

GET statement and internal table

Hi community,
I use the GET statement and I want to use some older code segments.
I read somewhere that I can use the result of GET like an internal table.
So I tried to get the content of bsid into my internal table it_bsid. But that doesn't seem to work.
Do you have any advice in this?
I wanted to do the following:
TABLES:
        KNA1,
        BSID,
        BKPF.
DATA:
      it_bsid TYPE TABLE OF bsid WITH HEADER LINE,
      is_bsid LIKE LINE OF it_bsid,
GET bsid.
LOOP AT bsid.
APPEND it_bsid.
ENDLOOP.
-or-
GET bsid.
LOOP AT bsid INTO is_bsid.
APPEND is_bsid TO it_bsid.
ENDLOOP.
But in both cases I get an error.
' "VERSION ... ." expected after "BSID" '
Do you know what is the reason for that?
Regards
Tobias
Edited by: Tobias Oelschlaeger on Feb 29, 2008 4:18 PM

Hi Tobias,
first you have to assign a logical database which has BSID to your program (in program attributes).
Then GET is the event triggered by the next BSID record according to your selection. You can not LOOP here but you may append to an internal table. This table may be processed using LOOP in the END-OF-SELECTION event.
Read some documentation about LDB [Logical Databases|http://help.sap.com/erp2005_ehp_01/helpdata/en/f0/ca4584260211d28a430000e829fbbd/content.htm] - it may help to understand the concept of this obsolete technique.
Regards,
Clemens

Alternative for "check select-options" for select query.

hi all,
my report is using a "GET" syntax, followed by "check select-options".
My senior told me to replace the Get syntax with select query.
Now, my program also has dynamic selection screen.
the dynamic selection screen almost has all the fields of database table.
so, what is the way to replace this check select-options while applying select query?
can you tell me how dynamic selection screen fields are populated? are they stored in some internal table?
thanks for help.

HI
Here is some points about LDB.
Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables by linking them to executable ABAP programs.
However, from Release 4.5A, it has also been possible to call logical databases using the function module LDB_PROCESS. This allows you to call several logical databases from any ABAP program, nested in any way. It is also possible to call a logical database more than once in a program, if it has been programmed to allow this. This is particularly useful for programs with type 1.
Logical databases contain Open SQL statements that read data from the database. You do not therefore need to use SQL in your own programs. The logical database reads the program, stores them in the program if necessary, and then passes them line by line to the application program or the function module LDB_PROCESS using an interface work area
For further on LDB's refer to this link.
[http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm]
Hope this will help.
Reward if helpful.
Sumit Agarwal

Optimization of DDF logical database

Hi,
I'm working on a program that uses DDF logical database to list accounting documents. In order to do this, we use three get sentences to loop into KNB1, BSID and BKPF tables.
It's something like that:
GET bkpf.
gjahr is a range with several values
CHECK bkpf-gjahr IN gjahr.
checta is a range with several values
CHECK bkpf-blart IN checta. "1
GET bseg.
CHECK bseg-bschl EQ '01' OR bseg-bschl EQ '11' OR "2
bseg-bschl EQ '12' OR bseg-bschl EQ '02'.
GET gseg.
PERFORM list_document.
But my problem with this code is that it takes too much time to generate the report. Doing some performance analysis on execution, I've determined that the problem is with the access to tables of logical database (the "get" sentences).
So I need to improve report performance, but I don't know how can I do this, maybe if the get returns only the fields I need for execution instead of all table fields runtime would be better, but I'm not very sure if this is possible.
Another option could be changing GET sentences for SELECT, but looking into LDB code I see that as well as hard to change probably it will be useless.
So any information about LDB optimization, or how to improve this kind of reports would be very appreciated.
Thanks in advance
Best regards

Hi Raymond,
first of all thanks for your answer, as you say it'd be better to use selection screen instead of check sentences, and I'll also use "GET bkpf FIELDS ..." to get only those fields that I need.
I've tested this improvements but I believe that it doesn't decrease too much execution time, so I need to find more solutions to optimize access to logical databases.
For Rob, maybe you're right and using LDB isn't the best solution, but I got this program done and I can't modify its way of retrieving data, only optimize it. To sum up, I can't erase LDB only optimize its execution.
So any help in LDB optimization would be very appreciated.
Thank you very much to both

Logical data base and Contexts

Hi everybody,
I wanna know about LDB's and contexts.I read it in the abap docu and understood the concept of LDB but contexts i couldnt follow,
so i want its explaination with some good examples.
Regards
akmal

Refer this link:
http://help.sap.com/saphelp_47x200/helpdata/en/9f/db95f835c111d1829f0000e829fbfe/frameset.htm
By
Yuvaram

Question about PNP...LDB

Hi All,
I have been asked a simple but strange question about PNP LDB. When we assigned logical database in our program, it will basically create a selection screen, which have certain fields. Like Today.. Some date ranges. Person assigned number, company code, company status.
From my standpoint I know when ever we give selection to PNP screen we have to check this selection parameters in our programs, like date range ,person number, employee status etc .RIGHT?
Somebody ask me that without checking selection in our report I mean any parameters, it can filter the record, my Answer was BIG NO. You need to check all the parameters in your program.
Next question asked by me was what the purpose of PNP. I replied that rather then declaring and doing bunch of databases SAP provide logical database so current all the records and do what ever you like to do.
What you think guys?
Thanks

Here`s the question , when I am giving "1"active employee in employee status why its pulling up the information for '0' withdrawn employee?
Message was edited by: Saquib Khan

About pernr orgeh on selection screen (PNP LDB)

Hi All,
ITS URGENT.....
i am tryieng to retrive the holiday compensation data from P0001 P2001 infotypes
i got screen but when i am tryieng to access the data by using person number (PERNR) WITHOUT GIVING ANY INFORMATION its coming out of the GET PERNR Event.
IF ANYBODY HAVE THE LOGIC PLEASE SEND ME .....
THX IN ADVANCE...........
MAHEN........

Hi,
IT2001 would give you results for absences and not compensation, look into IT0083 i think for leave compensation details..
as far as get pernr event is concerned follwings things are mandatory..
tables: pernr.
infotypes: 0001,2001.
start-of-selection.
get pernr.
Here you can retrive data if available..
like:
p2001-pernr
or
p0001-pernr.
end of selection.
please check if the data is present in infotypes with the period specified on the selection screen.
And always use addition MODE n while retrieving data from time infotype 2001 onwards...

Doubt about report FBL5N of screen field:Open items and Cleared items

hi
i know the report FBL5N is use DDF LDB and the report work flow is BSID->BKFP->BSEG
but i don't know to differentiate Open Items and Cleared items in this report.
Open items and Cleared items stand for a field flag in these table (BSID,BKFP,BSEG )? if true the field is?
or they must be calc in program ? if true what about calc rules?
waiting for help! thank you!

Hi,
Here is the difference in Open Items and Cleared Items.
In FI first the document is Open (when it is posted) so the entry is made in table BSID. Once the document is cleared, it will move from BSID to BSAD. And for Cleared item you will see Clearing Document no and Clearing date values updated (these are blank when the item is open).
The only difference in Open and Cleared is via Clearing Document and Clearing Date. If the values are present, it means document is cleared.
Hope this helps.
ashish
Message was edited by:
Ashish Gundawar

Access DB (& .ldb file) does not close after crystal reports

Post Author: mgold
CA Forum: Crystal Reports
Access DB (& .ldb file) does not close after crystal reports
Hi! We have a VB application using Crystal Reports 6 that has worked successfully on hundreds of systems for over 10 years. Now, on one network, the application and access database does not close. It seems to hang on the [.Close] command.
When we open the application an peruse the screens without opening up a report (using crystal reports), the application and access db closes fine. But as soon as we run a report and then close the report and try to close the application, the access db does not close. Many of the screens open the db and grab data from the access db, but it's only after running crystal reports that we have this problem. (Please see more information below.)
Setup: Application and data (access 97 db) reside on a server in the same folder, but application shortcut is kicked off on client PC. Kicking off the shortcut on the client PC means that the image/process runs on the client PC (not on the server). In this problem case, the application shortcut is on a Windows XP Pro Version 2002 SP2 PC with the app & data on a Windows 2003 server. Users are local Admins on their PCs with "Full Control"over the directory and files on the server where the data (access 97 db) resides. This type of setup is typical and has worked without any problems for clients.
The application is written in Visual Basic, using Crystal Reports 6 (using DAO). We close the recordset, set it to zero and then it hangs on closing the db (.Close command).
A few key pieces of information:
- The application closes fine if the app & data (access 97 db) are on a local PC. This includes closing fine if the application is run directly on the Windows 2003 server where the data is stored.
- It worked on this client's network until sometime in the last few weeks.
- One thing that changed is that the company is using VMWare on its servers. Not sure if they started using VMWare at the same time as it started failing. This may be unrelated. Possibly other things changed, but can't get any more information ... yet.
- It works fine running the application from a Windows Vista PC with a user who is a domain admin.
- The access db and application hang for about 10-20 minutes and then eventually closes. It appears that somehow
Crystal Reports is keeping the db open, but I'm not sure why.The application doesn't quit and the database doesn't close even if I try to end the task with the Task Manager.
- The Crystl32.ocx version being used is 8.0.0.4 (if that matters).
- I copied 6 month old program files and database files to a test folder on the Windows 2003 server. It fails using these files that worked fine 6 months ago.
Any ideas or help would be greatly appreciated! If you know of another good place to post this, please let me know.
Thanks!
- Mark

Crystal doesn't support tables in HTML interpretation.
You can probably work your way around this by doing Replace() calls on the relevant tags.
See:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233313337333033383334%7D.do
The supported HTML tags are:
" html
" body
" div (causes a paragraph break)
" tr (causes only a paragraph break; does not
preserve column structure of a table)
" span
" font
" p (causes a paragraph break)
" br (causes a paragraph break)
" h1 (causes a paragraph break, makes the font bold
& twice default size)
" h2 (causes a paragraph break, makes the font bold
& 1.5 times default size)
" h3 (causes a paragraph break, makes the font bold
& 9/8 default size)
" h4 (causes a paragraph break, makes the font bold)
" h5 (causes a paragraph break, makes the font bold
& 5/6 default size)
" h6 (causes a paragraph break, makes the font bold
& 5/8 default size)
" center
" big (increases font size by 2 points)
" small (decreases font size by 2 points if it's 8
points or larger)
" b
" i
" s
" strike
" u
The supported HTML attributes are:
" align
" face
" size
" color
" style
" font-family
" font-size
" font-style
" font-weight

LDB(Logical Database) selection screen

Dear Contributors,
I am hopefull for finding solution to my problem from one of you.
My requirement is i would like to pass all the elements of the selection screen of LDB to non-sap application so as they can replicate and show all those parameters there. Once those are filled from there then i need to take them and process the LDB.
My question is i dont know how to get the selection screen parameters. I tried using FM 'RPY_DYNPRO_READ' and passed progname and screen number in that. It gave back all the parameters but we cant co-relate which parameter is from which table (like we say MATNR like MARA-MATNR).
Without having Technical details of field, non-sap application could not able to process it or show the required F4 help etc
Anyone know about it, can guide me....
Regards
Munish Garg

call function 'LDB_CONVERT_LDBNAME_2_DBPROG'
       exporting ldb_name             = headsg-logdb "#EC DOM_EQUAL
                  flag_existence_check = space
       importing db_name              = logdbprog
       exceptions others               = 1.
if sy-subrc eq 0.
    call function 'SELOPTS_AND_PARAMS'
         exporting program              = logdbprog
         tables     selpars              = dbselpars
         exceptions program_non_existent = 1
                    subroutine_pool      = 2
                    load_problems        = 3
                    others               = 4.
endif.

HOW TO IMPLEMENT SCREEN VALIDATION IN LDB?

Hi,
I am making use of Logical Database in my report, and I want to do screen validation with the screen which already exists in the system? Is it possible to do so? If yes, then how? The LDB, I am using is PSJ.
Also, I would like to know, can we define our own selection screen incase of LDB? How is that possible if the answer is yes to it.BUt here I am not talking about dynamic selection screen. What I mean to say is that..., can we restrict the selection screen in LDB, by defining the fields which are required in the selection screen on execution of the report?
Someone, please guide.
Points will be rewarded for a satisfactory answer.
Thanks & Regards,
Ravi

Hi Ravi,..
Chk out the link - http://help.sap.com/saphelp_erp2005/helpdata/en/60/183d78163011d2953c0000e8353423/frameset.htm
Yes, we can define our own selection screen and that will come right below your LDB selection screen.
AND also LDB selection screen can be restricted ..for this you have to code in PBO of report for hiding the elements which u don't required.
Regards
Mithlesh

Want to have own selection screen in HR-ABAP report using LDB

Hi experts,
        I am working on HR-ABAP report using LDB pnp and infotypes..But, here we get the built in selection criterion..but I want my own selection screen to be displayed..whats the solution for this??? Is it possible to create my own selection screen instead of default one..and how???
Please help me..its very urgent..

Hi,
chk this out:
Create Report Categories
In this step, you define the report categories and determine the layout
   of the standard selection screen for these report categories. You can
   create report categories for programs or queries that are based on the
   PNP or PNPCE logical databases.
The definition of report categories is divided into two sections:
o   In the Change Report Category view, you define general attributes
       such as sort order, input fields for date, and so on.
o   In the Change Selection Criteria view, you define which selection
       fields of the logical database should be avaliable on the selection
       screen.
Example
You want to set up your system so that your employees can only start
   evaluation reports for Payroll if they use a payroll area. Within a
   payroll area, you should be able to select according to personnel
   number. Additional selection criteria should not be possible and you
   should not be allowed to enter a sort sequence.
Standard settings
The standard system already contains report categories. You can find the
attributes of the report categories in the table.
Note the following five report categories in particular:
o   Report category ' ' is the SAP default report category for
    programs that are based on the PNP logical database.
o   Report category PNPCE is the SAP default category for programs that
    are based on the PNPCE logical database.
o   Report category '00000000' is the customer-specific default category
    for programs that are based on the PNP logical database.
o   Report category '0PNPCE' is the customer-specific default category
    for programs that are based on the PNPCE logical database.
o   Report category __X2001 is the default category for Queries that
    are based on an InfoSet of the PNP LDB.
o   Report category QUEPNPCE is the default category for queries that
    are based on an InfoSet of the PNPCE LDB.
The default report categories are used when a report is called if
    the report has not been assigned a report category.
Parameters and Options for Report Categories of the LDB PNP and PNPCE
Parameters and Options in Screen Area General Data
   If you activate this parameter, you can only enter data on the data
   selection period if you use reports that have been assigned. The
   same date entries are then used for the person selection as for the
   date selection.
o   Matchcode allowed
   If you activate this parameter, you have use of a Matchcode
   pushbutton (search help) if you use reports that have been assigned.
   This pushbutton enables you to perform the person selection.
o   Sort allowed
   If you activate this parameter, you have use of a Sort pushbutton if
   you use report that have been assigned. This pushbutton enables you
   to define a sort order before you execute the report.
o   Organizational structure allowed
   If you activate this parameter, you have use of an Org.Structure
   pushbutton if you use reports that have been assigned. This
   pushbutton enables you to perform the person selection.
   Note:
   For more information about these options, see the online
   documentation under this path:
   SAP Library -> Human Resources -> Reporting in Human Resources
   Management -> Standard HR Reports -> Report Selection Screen in
   Human Resources Management.
Parameters and Options in Screen Areas Data Selection Period/Person
Selection Period/Payroll Area/Period/Year
o   Options for data selection period and person selection period (key
    date and so on)
    Here you define which options for date and person selection are
    available for reports that have been assigned.
o   Options for payroll area/period/year
    Here you define which options for selection using payroll
    area/period/year are available for reports that have been assigned.
Parameters and Options in Screen Area Selection View
o   Type/Name
    This parameter enables you to use selection views to define report
    categories. You use the selection view selected here to determine
    which fields are available in the Dynamic Selectionsy.
Note:
    You create selection views for the PNP and PNPCE logical databases
    in the Object Navigator (SE80):
    1. Start the Object Navigator (SE80)
    2. Choose Workbench -> Edit Object.
    3. Choose the More... tab page and the Selection view on this tab
    page.
    4. Choose Create.
    5. In the Create Selection View dialog box, choose the For any
    tables option.
    6. In the Name of view field, enter a name for your selection view.
    7. In the Tables dialog box, enter the name of the table from which
    you want to use fields.
    Note:
    When you enter the table name, observe the naming convention in
    Personnel Administration:
    Infotype number: nnnn -> table name: PAnnnn
    8. Choose Continue.
    9. In the Functional groups area, define functional groups by
    assigning a name and a number.
    10. Assign fields from the selected tables to the functional groups
    by entering the number of the desired functional group in front of
    each field.
    11. Save your entries.
For more information about adjusting the dynamic selections using
your own selection views, see the online documentation under the
following menu path:
SAP Library -> Human Resources -> Reporting in Human Resources
Management -> HR Standard Reports -> Report Selection Screen in
Human Resources Management -> Enhancing the Selection Screen -
Dynamic Selections.
If you do not want to offer dynamic selections, make the following
settings:
-   LDB PNP: In the Selection view field, enter PNP_NO_FREE_SEL.
-   LDB PNPCE: Leave the Selection view field empty.
Parameters and Options in Screen Area Data Selection Period/Person
Selection Period/Payroll Area/Period/Year
o   Available input parameters, date or period entry (today, key date,
   all, and so on), and standard value.
   Using the Standard value option, you define which of the selected
   options is shown.
Parameters and Options in Screen Area CE Selection Fields
o   CE selection fields (external person ID, grouping reason, grouping
   value)
   Using the options in this area, you define whether the external
   person Id, grouping reason, or grouping value are available on the
   selection screen.
   Note:
   These parameters are only relevant for you if you implement
   Concurrent Employment (see also note 517071).
Parameters and Options in Screen Area Selection view
o   Dynamic selections as dialog box
    If this switch is set, you can call the dynamic selections as a
    dialog box.
o   Dynamic selections active
    If this switch is set, the dynamic selections of the logical
    database are active at the start of the report.
Note that the following combinations are possible for the last two
    options mentioned:
Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/inactive
    Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/active
    Dyn.Sel. as dialog box/Dyn.Sel. active: active/inactive
Activities
1. Choose Edit -> New entries.
2. Enter an abbreviation and a long text for the report category.
    The customer name range for report categories is 0-9.
3. Select the For the PNPCE logical database checkbox, if you want to
    create a report category for a program or for queries of the PNPCE
    logical database.
4. In the General Data screen area, choose the desired options.
    If you want to use selection IDs, you must have first created and
    grouped selection Ids. The IMG path to do this is given in the
    parameter description section.
5. In the Data selection period/person selection period or Selection
    period screen area, choose the desired options.
6. In the Selection view screen area, choose the desired options.
7. In the CE selection fields screen area, choose the desired (only
    possible for report categories of the LDB PNPCE).
8. Save your entries.
9. Choose the subactivity Permitted selection criteria.
10. Choose Edit -> New entries.
11. In the Select option field, use the input help to select each field
    that should be available on the selection screen.
12. Select the checkbox in the 1.page column, if you want this selection
    field to be available directly when you call the selection screen.
Further notes
13. If you want to copy entries, you still have to enter the selection
    parameters again in the subsequent screen.
o   If you create the report category '000000000', a selection screen is
    generated according to report category '00000000'for all reports for
    which a report category has not explicitly been assigned.
Assign Report Categories
In this step, you assign a report category to your reports.
Example
You have created your own report, for example ZPCTEST1, and would like
    it to have the selection screen that corresponds to that of the
    evaluation report for Payroll, which is assigned to report category
    '__M00001'.
    Assign report category '__M00001' to the report.
Requirements
You must have defined the Report Categories.
Standard settings
SAP Standard Reports:
In the standard system, reports are assigned a report category. If you
    want to override these assignments, perform the activities described
    here. If you want to assign report categories to standard reports using
    SE38, this represents a modification.
Customer-Specific Reports:
For reports you have developed yourself, you can either assign report
    categories by performing the activities described here or directly in SE38.
Recommendation
Only assign a report category if you have created your own reports or if
the selection screens in the standard system do not meet your
requirements.
Activities
1. Choose Edit -> New entries.
2. Perform the required assignment using the Program name and Report
   category fields.
3. Save your entries.
reward if helpful
regards,
madhumitha

About LDB

Similar Messages

Maybe you are looking for