Setting LDB selection screen

[Former Member]

Hi,

I use report RFDOPR10 which i copied into ZRFDOPR10 . This report uses

a LDB DDF. In the new report i need to set some values in the selection-screen such as DD_UMSKZ but can't catch up the screen field name.

Is there a way to solve it?

Thanks

[Former Member]

You can supply the selection screen with default values at INITIALIZATION.

You can determine which selection screen is currently processing with the AT

SELECTION-SCREEN event. You can do so with a CASE control structure and evaluate the system field sy-dynnr.

You can create any number of selection sets (variants) for a program. The variants are allocated to the program uniquely.

Creating variants makes sense when you frequently start a program with the same selection default values.

You can mark Start with variants in the program attributes. Users (system, services, reporting) can then start the program only with a variant.

If the program uses several selection screens, you can choose to create a variant for all the selection screens or individually for each selection screen.

Naming conventions and transporting variants

"SAP&xxx" are supplied by SAP

"CUS&xxx" are created by customers (in client 000)

Variants that follow these naming conventions are client-independent and will automatically be transported along with the report. If these naming conventions are not followed, an entry for a request (task) must be added to the object list: LIMU VARI .

You have to assign a name and a description to each variant. By default, variants are available for both online and background processing. You can also define a variant exclusively for use with background processing.

You can protect the variant itself and the individual selection criteria and parameters against unauthorized changes. If you select Display only in catalog, this variant will not be displayed in the general value help (F4).

The type of a selection is determined in its declaration: Type s for SELECT-OPTIONS, type p for PARAMETERS. If you select Selections protected, then the field(s) will not be ready for input. You can use the hide attribute to suppress selection criteria and parameters on the screen, if required, resulting in a less cluttered selection screen.

When you use selection variables, there are three basic ways of supplying your selections with values at runtime:

From table TVARV (type T)

Date fields using dynamic date calculation (type D), such as today's date

User-specific variables (type B); Prerequisite: The selection must be declared with the MEMORY ID addition.

[Former Member]

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.

LDB offers an easy-to-use selection screens. You can modify the pre-generated selection screen to your needs. It offers check functions to check whether user input is complete, correct, and plausible. It offers reasonable data selections. It contains central authorization checks for data base accesses. Enhancements such as improved performance immediately apply to all report programs that use the logical database.

Less coding s required to retrieve data compared to normal internel tables.

Tables used LDB are in hierarchial structure.

Mainly we used LDBs in HR Abap Programming.

Where all tables are highly inter related so LDBs can optimize the performance there.

Check this Document. All abt LDB's

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=...

GO THROUGH LINKS -

http://www.sap-basis-abap.com/saptab.htm

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9bfa35c111d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm

/people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases

www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_Logical_Database_FAQ.html

www.sap-img.com/abap/abap-interview-question.htm

www.sap-img.com/abap/quick-note-on-design-of-secondary-database-indexes-and-logical-databases.htm

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db9bb935c111d1829f0000e829fbfe/content.htm

Gothru the blog which provides info on LDB's:

/people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases

Sample code

TABLES: SPFLI,

SFLIGHT,

SBOOK,

SCARR.

START-OF-SELECTION.

GET SPFLI.

WRITE:/ ’SPFLI: ’, SPFLI-CARRID, SPFLI-CONNID,

SPFLI-AIRPFROM, SPFLI-AIRPTO.

GET SFLIGHT.

WRITE:/ ’ SFLIGHT: ’, SFLIGHT-CARRID, SFLIGHT-CONNID, SFLIGHT-FLDATE.

GET SBOOK.

WRITE:/ ’ SBOOK: ’, SBOOK-CARRID, SBOOK-CONNID,

SBOOK-FLDATE, SBOOK-BOOKID.

GET SFLIGHT LATE.

WRITE:/ ’ GET SFLIGHT LATE: ’, SFLIGHT-FLDATE.

[Former Member]

Hi

go to the transaction SLDB.

and give the LDB name DDF.

click on display button

There u can find the tree structure of that LDB.

And click on 'Selections' button.

There u can find the selection-screen information of that LDB.