Structure of ldb

hi experts
what are the structure of logical database

Hi
Check the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/db9b8535c111d1829f0000e829fbfe/frameset.htm
Thanks
Vijay
Plz reward points if helpful

Similar Messages

PN AND PNP Structure IN LDB PNP

hi
i can't find what definition about PN and PNP structure In LDB PNP.
how to get these infomation!
thank you very much!

thank you very much !
when i use LDB PNP in report , the PN and PNP structure variable will work in program.
but i don't find PN and PNP structure definition in LDB PNP (SAPDBPNP).
i want to konw PN and PNP of fields how work in SAPDBPNP. and to know what's meaning about PN's filed and PNP's filed.

What are structures of logical database.

hi
what are structures of logical database.

Dear Chaitanya,
The structure of LDB can be divided into three sections:
>Structure
>Selection
>Database Program
STRUCTURE:
The structure defines the data view of the logical database. It adopts the hierarchy of the database tables defined by their foreign key relationships. This also controls the sequence in which the tables are accessed. It determines the structure of the other components and the behavior of the logical database at runtime.
The structure of a logical database is usually based on the foreign key relationships between hierarchical tables in the SAP System. Logical databases have a tree-like structure, which can be defined as follows:
· There is a single node at the highest level. This is known as the root node.
· Each node can have one or several branches.
· Each node is derived from one other node.
The nodes must be structures defined in the ABAP Dictionary or data types from a type group. Normally, these are the structures of database tables which the logical database reads and passes to the user for further evaluation. However, it is also possible, and sometimes useful, to use ABAP Dictionary structures without an underlying database. For technical reasons, the maximum number of nodes allowed in the structure of a logical database is 300.
Any executable ABAP program that has a logical database linked to it can contain a GET statement for each node of the structure. When you run the program, the corresponding event blocks are processed in the sequence prescribed by the hierarchical structure of the logical database. If a program does not contain a GET statement for every node of a logical database, the processing passes through all the nodes that lie in the path from the root to the nodes specified by GET statements.
If you call a logical database using the function module LDB_PROCESS, the depth to which the system reads is controlled by an interface parameter.
SELECTIONS:
The selections define a selection screen, which forms the user interface of the executable programs that use the logical database. Its layout is usually determined by the structure. You can adapt the selections to your own requirements and also add new ones. When you link a logical database to an executable program, the selections of the logical database become part of the standard selection screen of the program (screen number 1000). If you call a logical database using the function module LDB_PROCESS, the selections are filled using interface parameters.
The selections in a logical database are defined using the normal statements for defining selection screens, that is, PARAMETERS, SELECT-OPTIONS and SELECTION-SCREEN. In a logical database, you can also use the additions VALUE-REQUEST and HELP-REQUEST to define specific input and value help. You define the selection screen in a special include program known as the selection include.
When you write programs using a logical database, you can also add your own program specific selections. The standard selection screen then contains the database-specific selections, followed by the program-specific selections that you have defined.
When the system generates the selection screen for an executable program, database-specific selection criteria and parameters are only displayed if you have declared an interface work area for them in your program using the NODES or TABLES statement.
Suppose you have a selection include containing the following lines:
SELECT-OPTIONS slifnr FOR lfa1-lifnr.
PARAMETERS pbukrs LIKE lfb1-bukrs FOR TABLE lfb1.
The selection criterion SLIFNR is linked to table LFA1, the parameter PBUKRS to table LFB1. If the TABLES statement in an executable program (report) declares LFA1 but not LFB1, SLIFNR is displayed on the selection screen, but PBUKRS does not appear.
The selection screen of a logical database can contain dynamic selections as well as static ones. Dynamic selections are extra, user-defined selections that the user can make as well as using the static selections defined in the selection include. To improve performance, you should always use this option instead of reading more data than you need and then sorting it out in the application program.
To make dynamic selections available for the node nodeof a logical database, the selection include must contain the following statement:
SELECTION-SCREEN DYNAMIC SELECTIONS FOR NODE|TABLE node.
If the node node is requested by the user of the logical databases, the dynamic selections are included in the selection screen. A user can then choose Dynamic selections to enter extra selections for the corresponding fields. If you call the logical database using the function module LDB_PROCESS, you can pass a corresponding parameter. You can use these selections in dynamic statements in the logical database program to read data. The values of the program-specific selection criteria that you defined for a node for which dynamic selections were available are also passed to the logical database. The user can also define the fields for dynamic selections as a selection view for the logical database.
The selection screen of a logical database is part of the standard selection screen (number 1000) of the executable program to which the logical database is attached. It has a standardized layout - the selection criteria and parameters appear on separate lines in the order in which they were declared. You can change the layout using the SELECTION-SCREENstatement.
The runtime environment generates the selection screen with number 1000 for every program in which the attributes do not contain a different selection screen version. You can prevent certain input fields from the selection screen of a logical database from appearing on the selection screen by defining selection screen versions with a screen number lower than 1000 in the selection include, and entering this version number in the program attributes. By pressing F4 there, you can get an overview of the selection screen versions defined in the logical database concerned. To define a selection screen version, use the statements SELECTION-SCREEN BEGIN|END OF VERSION. Within these statements you can use SELECTION-SCREEN EXCLUDEto specify fields that you do not want to appear on the selection screen.
If the attributes of an executable program contain the number of a selection screen version, the version is used in the standard selection screen. Although the input fields that you excluded from the selection screen are not displayed, the corresponding selections still exist, and you can still edit them in the program or by calling the function module LDB_PROCESS.
DATABASE PROGRAM:
The database program contains the ABAP statements used to read the data and pass it to the user of the logical database. There is a container for special subroutines into which, amongst other things, the data from the database tables is read. These subroutines are called by the reporting processor in the runtime environment in a sequence that has been predefined by the structure. The database program is determined by the structure and selections and can be adapted or expanded to meet your requirements.
The name of the database program of a logical database ldbconforms to the naming convention SAPDBldb. It serves as a container for subroutines, which the ABAP runtime environment calls when a logical database is processed. The sequence of the calls and their interaction with the events in executable programs or the function module LDB_PROCESS depends on the structure of the logical database.
A logical database program usually contains the following subroutines:
· FORM LDB_PROCESS_INIT
Called once only before the logical database is processed. It prepares it to be called more than once by the function module LDB_PROCESS.
· FORM INIT
Called once only before the selection screen is processed.
· FORM PBO
Called before the selection screen is displayed, each time it is displayed. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS.
· FORM PAI
Called when the user interacts with the selection screen. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS. The interface parameters FNAME and MARK are passed to the subroutine.
FNAME contains the name of a selection criterion or parameter on the selection screen.
MARK describes the selection made by the user: MARK = space means that the user has entered a simple single value or range selection. MARK = '*' means that the user has also made entries on the Multiple Selection screen.
· FORM LDB_PROCESS_CHECK_SELECTIONS
Called instead of the subroutine PAI if the logical database is called using the function module LDB_PROCESS without a selection screen. This subroutine can check the selections passed in the function module interface.
· FORM PUT_node
Called in the sequence defined in the structure. Reads the data from the node nodeand uses the
PUT node.
statement to trigger a corresponding GETevent in the ABAP runtime environment. The PUT statement is the central statement in this subroutine: It can only be used within a subroutine of a logical database. The logical database must contain the node node, and the subroutine name must begin with PUT_node. The PUT statement directs the program flow according to the structure of the logical database. The depth to which the logical database is read is determined by the GET statements in the application program or the interface parameter CALLBACK of the function module LDB_PROCESS.
First, the subroutine PUT_root is executed for the root node. The PUT statement then directs the program flow as follows:
i. If the database program contains the subroutine AUTHORITY_CHECK_node, the first thing the PUT_node statement does is to call it.
ii. Next, the PUT statement triggers a GET event in the runtime environment. If there is a corresponding GET nodestatement in the executable program to which the logical database is linked, the associated event block is processed. If the CALLBACK parameter of the function module LDB_PROCESS is filled accordingly, the corresponding callback routine is called.
iii. The PUT statement directs the program flow
(a) To the next subroutine of a node that follows directly, if a lower-level node (not necessarily the very next) in the same subtree is requested by GET in the executable program or in the function module.
(b) To the subroutine of a node at the same level, if the preceding node branches to such a node and if a GET statement exists for such a node in the executable program or the function module.
The PUT statement in that subroutine starts again at step (i). In the subroutine of the lowest node in a subtree to be processed using GET, the program control does not branch further. Instead, the current subroutine is processed further. When a subroutine PUT_node has been executed in its entirety, the program flow returns to the PUTstatement from which it branched to the subroutine PUT_node.
iv. When control has returned from a lower-level subroutine PUT_node, the PUTstatement triggers the event GET node LATEin the runtime environment.
· FORM AUTHORITY_CHECK_node
Called automatically by the PUT node statement. In this subroutine, you can specify authorization checks for the appropriate node node from the structure of the logical database.
· FORM PUT_ldb_SP
Called when the user makes a selection using a search help to process the key chosen in the search help. ldb is the name of the logical database. From this subroutine, you can use the entries in the search help tables to read the relevant entries from the root node root. The processing in the program can then be triggered using PUT root. The subroutine PUT_root is then not called automatically.
· FORM BEFORE_EVENT
Called before an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value START-OF-SELECTION, to call a subroutine before this event.
· FORM AFTER_EVENT
Called after an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value END-OF-SELECTION, to call a subroutine after this event.
· FORM par_VAL, selop_VAL, selop-LOW_VAL, selop-HIGH_VAL
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
· FORM par_HLP, selop_HLP, selop-LOW_HLP, selop-HIGH_HLP
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
Example
Suppose that in the logical database structure, LFB1 is a branch of LFA1.
and that the following selection criteria are defined in the selection include:
SELECT-OPTIONS: slifnr FOR lfa1-lifnr,
sbukrs FOR lfb1-bukrs.
A section of the database program would then read:
FORM put_lfa1.
SELECT * FROM lfa1
WHERE lifnr IN slifnr.
PUT lfa1.
ENDSELECT.
ENDFORM.
FORM put_lfb1.
SELECT * FROM lfb1
WHERE lifnr = lfa1-lifnr.
AND bukrs IN sbukrs.
PUT lfb1.
ENDSELECT.
ENDFORM.
An executable program (report) linked to the logical database could contain the lines:
GET lfa1.
WRITE lfa1-lifnr.
GET lfb1.
WRITE lfb1-bukrs.
In this example, the runtime environment calls the routine put_lfa1 after the event START-OF-SELECTION. The event GET lfa1 is triggered by the statement PUT lfa1.
Once the corresponding event block in the program is complete, PUT lfa1 branches to the subroutine put_lfb1.
From this subroutine, the event GET lfb1 is triggered in the application program. If LFB1 is the last node to be read, processing resumes with the SELECTloop in put_lfb1. Otherwise, the program flow moves to the subroutine put_node of the next node. At the end of the SELECT loop of the last node, processing resumes in the SELECTloop of the node at the next level up. The example of programming using nested SELECT loops is only used to make the program flow clearer. In a real logical database, you would avoid doing this in order to minimize the number of database accesses.
Regards,
Rajesh K Soman
Please reward points if helpful.

LDB..

Hii All,
Any one pls send me some interview ques on LDBs??
Regards,
Kavitha

Hi Kavitha,
pls find here some general ques for interview,
1.     Preparation of the data records by the L.D.B and reading of the data records in the actual report are accomplished with the command pair Put and Get.
2.     The three main elements of LDB are Structure, Selections, and Database Program.
3.     In LDB what determines hierarchy of the tables?
Structure.
4.     In general what are the two ways in which one can retrieve data from tables?
Using Select statements, Database Program.
5.     With LDB one can modify the pre-generated selection screen to their needs (T/F).
Yes.
6.     Logical databases are programs that read data from Database tables (Dictionary Structures).
7.     The event Get<table name> LATE process all tables that are hierarchically superior to the <table name>. (True/False)
False. It processes all tables that are hierarchically inferior to the <table name>.
8. The Database Program of LDB is a collection of SUBROUTINES, which selects data and passes it to the report.
9.     The layout of the Database program is determined by both Structure and Selections.
10.      The order in which data is made available to the report depends on Structure of the LDB.
11.     Apart from the structure and selections of the LDB the GET statements in the report determines the behavior of the database at runtime.
12.     Node at the highest level in the structure is known as Root.
13.     There can be more than one node at the highest level in the structure. (T/F)
False. One can define only one node at the highest level in the structure on LDB.
14.     All nodes in the structure of LDB need not be defined in the ABAP/4 Dictionary (T/F).
False. One has to define all nodes in the Dictionary or one has to select all nodes that are defined in the Dictionary.
15.     It is not possible to use ABAP/4 Dictionary Structures without an underlying database using LDB. (T/F)
True. One can use additionally related tables, along with the tables defined in the structure of LDB.
16.     Dynamic selections allow the user to define further selections for database access in addition to the selection criteria already defined in the LDB selections.
17.     Check statement can be used along with the event GET in the report for checking the selections, which are not table-specific values.
18.     In sense of Database Management System (DBMS) LOGICAL DATABASE is a database Structure. (T/F).
False.
19.     It is not necessary to maintain the Parent-Child relationship between the tables in Logical Database Structure. (T/F)
False. One has to maintain the Parent-Child relationship.
20.     Is it possible to extract data from tables without using the event GET in the report with an appropriate LDB. (T/F).
False. One can extract data from tables using Select statements in a report, though the report is having a LDB attribute.
21.     What sorts of tables one can se in designing the hierarchy of a LDB?
Tables, which are having Foreign Key relations.
22.     A report program, which uses only SELECT statements, is called SQL Report.
23.     One cannot use SELECT statements in a report program linked to a Logical Database (T/F). False.
24.     Is it true that the Logical Database reads the data from the database tables using Select Statements (T/F).
Yes. We are coding that in Database part of LDB.
25.     In a report with an LDB attribute, you do not have to define how the information should be retrieved from the database tables, but only how the data should be represented on the screen. (T/F).
True.
26.     One can use the event GET in a report without LDB attribute. (T/F).
False.
27.     The last character of the LDB name denotes Application.
28.     The structure of Logical Databases reflects the Foreign Key dependencies of hierarchical tables in the SAP system.
29.     It is mandatory that for each table in the LDB hierarchy there should exist one GET statement in the report. (T/F).
False. It is not necessary.
30.     What happens if a report does not contain a GET statement for a particular node of a Logical Database.
Process will transfer to the next event.
31.     In a Logical Database, one can define input fields on the selection screen with Select-Options and Parameters statements.
32.     Suppose a logical database program contains the following lines:
SELECT-OPTIONS CONNID FOR SPFLI-CONNID.
PARAMETERS CARRID LIKE SFLIGHT-CARRID FOR TABLE SFLIGHT.
What will be the output, for the above two statements?
Only select-options connid for spfli-carrid will be displayed on the screen.
33.     Consider a report with F1S attribute, what will be the output for the following code. Whether you will get the data from spfli and sflight or not, with corresponding tables statement,
     GET SPFLI.
     GET SFLIGHT.
     Write:/ spfli-carrid, spfli-connid, sflight-fldate, sbook-bookid.
     Yes, you will get the data from spfli and sflight.
34.     Consider a report with F1S attribute, what will be the output of the following code. Whether you will get the data from sbook or not, with corresponding tables statement.
GET SPFLI.
GET SFLIGHT.
Write:/ spfli-carrid, spfli-connid, sflight-fldate, sbook-bookid.
You cannot extract data from sbook.
35.     Identify any errors in the following code and correct the same, and what will be the output. If there exists corresponding tables statement, for spfli, sflight, sbook.
GET SPFLI.
GET SBOOK.
Write:/ spfli-carrid, spfli-connid, sflight-fldate, sbook-bookid, sbook-class.
No syntax errors. You will get data from all the three tables.
36.     Does the following two statements do the same task? If so which one takes less time and which one is recommended.
     Select * from spfli where spfli-carrid = LH and spfli-connid = 400.
     Endselect.
     Select * from spfli. Check: spfli-carrid = LH and spflid-connid = 400.
     Endselect.
    -Yes they will do the same task. Second Select statement takes less time and is recommended.
37.     If you want to improve the response time (time to access data) Logical Databases permits you to achieve this using VIEWS.
38.     Is there any upper limit (max) to the possible number of nodes in a logical database structure? If so what is the limit?
Yes, there is an upper limit for defining number of nodes in a Logical Database Structure.
Maximum nodes = 1200 / length where length = max. Length of name in the structure.
39.     In the structure of Logical Database nodes at different levels are displayed in the same columns. (T/F) If false what types of nodes are displayed in the same columns. If true what type of nodes are not displayed in the same columns.
False. Nodes at same levels are displayed in the same columns.
40.     What are the advantages of Logical Databases?
It 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.
41.     Though all the ABAP/4 Dictionary Structures that exists in the structure of the LDB, being defined in Database Program, we are defining the Dictionary Structures in the Report. What is the reason for such declaration?
By declaring so we are providing work areas for data passing between Logical Database and Report. In addition, the logical database configures the selection screen depending on the selection of database tables.
42.     Is it mandatory to declare all the tables in Report by the key word tables for all the tables that exist in the structure of LDB, and are being defined in the Database part of LDB.
No, It is not mandatory to declare all tables in report.
<b>
Rewards points if useful</b>
rgrds
shazia

Creating Logical Database

hi,
   i need to display Outstanding Liability GRNs in my report. for that report, i have created a Logical Database.
The structure of ldb is,
BSIS>Bkpf->Bseg--->Rseg
    My Input fields
                    GL Account
                    Plant
                    Fiscal Year
                    Grn Date
    Now my problem is,
                 Time taken to give the output is very high(Nearly 450 seconds for 1 month duration)
      Is there any alter way to create the Logical database using some other tables?
      In logical Database can i create Internal tables?
      Thanks,
      Neptune.M

Hi,
you can create the view or index to make it faster
regards
vijay
Message was edited by: Vijay Babu Dudla

Structures LDB PCH

I need create a selection-screen belong to the LDB PCH, On the selection-screen there are two blocks: Objects and Reporting period. I need a third block named Event selection, so how is the structure for get this?
My statement is
TABLES: objec .
I appreciated much yours suggestion.
Regards.

Hi Ajay,
Go To Reports Attribute -
> You will see field Selection screen --- enter screen no 901 ..as empty selection screen.
~Bhawanidutt

LDB PNP, selection screen, org structure field name ?

Hi,
Generally, what are the names of the additional selection-screen fields? There are twenty odds pnp...., the standard ones. But what is the name of the org. structure, the 4th button selection options group fiels? (I need ids of all Org units from org. structure subtree, or the root org id at least)
Thanks,
Piotr

...this it is with headerline...
Sergey big spasiba
Piotr

Structure STRUC of ldb PCH

is there any documentation for structure STRUC of log. database PCH?
Meaning of the fields etc.

Hello Volker
Not able to get any detailed documentation on the structure. But from my experience of using this structure for quite a while now, i am giving you a brief explanation on the important fields,
SEQNR     -   This will be a unique number for each Org. Object
LEVEL      -   This will provide the level of Org. Objid in the tree structure of the organization
OTYPE     -   Object Type Of the Related Object
PDOWN   -    PDOWN stands for Obtect Type Down, which actually hold the sequence number (SEQNR) of the immd. downward Org Object for Botton Down evaluation ath
PNEXT     -    PNEXT stands for Object type Next, if there are multiple Org. Objects in the same level it will hold the sequence (SEQNR) of the next Org. Object which was retrieved based on the evaluation path
PUP-        - PUP stands for Pointer Up which mean it will hold the Sequence number (SEQNR) of the Org. Object parent to the current Org. Object for Top Down Evaluation path
PPREV     - PPREV Stands for Pointer Previous. if there are multiple Org. Objects in the same level it will hold the sequence (SEQNR) of the previous Org. Object which was retrieved based on the evaluation path
May be if you can execute the FM "RH_STRUC_GET" for a Particualr Object ID and Evaluation path, it will return a table of STRUC type which can show more information on the points mentioned before.
Please let me know if you need more information regarding anyother fields.
Regards
Ranganath

Logical Database PGQ structure usage

Hello Everyone,
I have a question regarding Logical Database(LDB) usage...How to use the structure defined in LDB. We are using PGQ Logical database in one of custom programs. The structure of the LDB as hierarchy or tree is:
QALS
      QAVE
      QMFEL
      QAPO
           AFFHD
           QAMV
                QAMR
                     QASE ---> From this table
                QASV
                     QASR ---> From this table
and etc
The code was something like this in the program:
GET QALS.
GET QAPO.
GET QAMV.
GET QAMR.
Now, my requirement is to get data additionally from QASE and QASR tables..So, I tried modifying the code according to the hierarchy structure defined in the PGQ LDB(check bold statements):
GET QALS.
GET QAPO.
GET QAMV.
GET QAMR.
<b>GET QASE.
GET QASV.
GET QASR.</b>
But in runtime I see that QAMR and QASE is filled up with # data ...I am not sure if is right way to do....Is this the way to use the structure defined in the Logical database? QAMV and QASV lie in the same level of hierarchy and I have to use them to get QASE and QASR data...Let me know, if I am not clear...
Thanks for taking your time and I appreciate if some one can help me.
--- Ashley

Hi Ankur
You can use program SAPDBPGQ that is program created to test logical database PGQ. Then you can get only part responsible for nodes QALS, QAPO and QAMV
Best regards

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

How to retreive data from a table and a structure

Hi experts,
I have a requirement to create an ALV report. I have to include fields from two tables 'PA0001' and 'CATSDB' and from one structure 'CATSAPPR'. I am able to retrieve data from tables using INNERJOIN. But i have no idea how to deal with Structure.
I know that structure does not contain any data.
But i am not able to find any transparent table which has field 'ORDERTEXT' . I found field 'ORDERTEXT' only in structure 'CATSAPPR'.
So please anyone tell me, either any transparent table which has field 'ORDERTEXT' or please tell me how to deal with structure, in this case.
Please help me,
Thanks in advance
Anu

check this
Table-Fields                     Short descriptn
AUFK- KTEXT          Order master data
COCH- KTXT              Process Management: Control Recipe Header
COCHP- KTXT             PI sheet: Control Recipe Header
COMPHDR- KTEXT    OCM: Comparison results, indiv. records for order headers
HIKO- KTEXT              Order master data history
MAAVC_MDO- KTEXT      MPO: Individual Master Data for Orders
MCHPVS- AUFTEXT                           Batch Record: Shadow Table for Link to Archive
OCMHOMO_ARCH- KFELD          Backup Table of Homogeneity List in Case of Archiving
PSJHIEDATA- KTEXT                       Hierarchy data to test LDB PSJ
TEWOCODEST- DESCRIPTION                      Order Codes (Texts)
TEWOCODET- KTEXT           Allocation of Message Codes to Order
VLCSMORDER- KTEXT                                                   VELO : Service Order
VSAUFK_CN- KTEXT               Version: Order master data
Yogesh N

How to Add a new fields in the selection screen of LDB.

Hi All,
I want to add a new fields in the selection screen of LDB & then i need to select the data for that fields.
So could you please tell me for that where i need to add the code for selecting the data.
Thanks
Roli

Hi
welcome to SDN forum
If you are designing your own LDB with your own tables you can define tree structure and then the selection screen for the tables
if you wants to modify the std LDB of SAp means take the access key and to modify that code
if you add the extra field you have to modify the where conditions in the code also
see the doc
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=%2flibrary%2fabap%2fabap-code-samples%2fldb+browser.doc
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
Re: **LDB**
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.
Regards
anji

LDB IN HR-ABAP

LIST LDB'S CONCERNED TO THE DIFFERNENT PARTS OF HR MODULE LIKE PP,PA,OM ,PLEASE

Hi Raghunandan,
SAP HR Transaction Codes
Master Data
PA10 - Personnel file
PA20 - Display HR Master Data
PA30 - Maintain HR Master Data
PA40 - Personnel Events
PA41 - Change Hiring Data
PA42 - Fast Data Entry for Events
PRMD - Maintain HR Master Data
PRMF - Travel Expenses : Feature TRVFD
PRML - Set Country Grouping via Popup
PRMM - Personnel Events
PRMO - Travel Expenses : Feature TRVCO
PRMP - Travel Expenses : Feature TRVPA
PRMS - Display HR Master Data
PRMT - Update Match code
PS03 - Info type Overview
PS04 - Individual Maintenance of Info types
Time Management
PA51 - Display Time Data
PA53 - Display Time Data
PA61 - Maintain Time Data
PA62 - List Entry of Additional Data
PA63 - Maintain Time Data
PA64 - Calendar Entry
PA70 - Fast Data Entry
PA71 - Fast Entry of Time Data
PBAB - Maintain Vacancy assignments
PT01 - Create Work Schedule
PT02 - Change Work Schedule
PT03 - Display Work Schedule
Payroll
PC00 - Run Payroll
PC10 - Payroll menu USA
PE00 - Starts Transactions PE01 PE02 PE03
PE01 - Schemas
PE02 - Calculation Rules
PE03 - Features
PE04 - Create functions and Operations
PE51 - HR form editor
PRCA - Payroll Calendar
PRCT - Current Settings
PRCU - Printing checks USA
PRD1 - Create DME
SM31 - Maintain Table
SM12 - Locked Secessions
TSTC - Table Look up
SPRO - IMG
SE16 - Data Browser (Table Reports)
PP03 - PD Tables
PPOM - Change Org Unit
PO13 - Maintain Positions
PO03 - Maintain Jobs
Benefits
PA85 - Benefits - Call RPLBEN11
PA86 - Benefits - Call RPLBEN07
PA87 - Benefits - Call RPLBEN09
PA89 - COBRA Administration
PA90 - Benefits Enrollment
PA91 - Benefits - Forms
PA92 - Benefits Tables - Maintain
PA93 - Benefits Tables - Display
PA94 - Benefits - Access Reporting Tree
PA95 - Benefits IMG - Jump to Views
PA96 - Benefits reporting
PA97 - Salary Administration - Matrix
PA98 - Salary Administration
PA99 - Compensation Admin - rel. Changes
PACP - HR-CH : Pension fund, interface
General Reporting
PM00 - Menu for HR Reports
PM01 - Dialogs in HR - Create Custom info types
PRFO - Standard Form
PSVT - Dynamic Tools Menu
PAR1 - Flexible Employee Data
PAR2 - Employee List
Organizational Management
PPOM - Change org Unit
PO03 - Maintain Jobs
P013 - Maintain Position
PO10 - Maintain Organizational Unit
PP01 - Maintain Plan Data (menu-guided)
PP02 - Maintain Plan Data (Open)
PP03 - Maintain Plan Data (Event-guided)
PP05 - Number Ranges
PP06 - Number Ranges Maintenance HR Data
PP07 - Tasks/Descriptions
PP69 - Choose Text for Organizational Unit
PP90 - Setup Organization
PP01 - Change Cost Center Assignment
PP02 - Display Cost Center Assignment
PP03 - Change Reporting Structure
PP04 - Display Reporting Structure
PP05 - Change Object indicators (O/S)
PP06 - Change Object indicators OS
PPOA - Display Menu Interface (with dyn.)
PPOC - Create Organizational Unit
PPOM - Maintain Organizational Plan
PPOS - Display Organizational Plan
PQ01 - Events for Work Center
PQ02 - Events for Training Program
PQ03 - Events for Job
PQ04 - Events for Business Event Type
PQ06 - Local Events
PQ07 - Resource Events
PQ08 - Events for External Person
PQ09 - Events for Business Event Group
PQ10 - Events for Organizational Unit
PQ11 - Events for Qualification
PQ12 - Resource Type Events
PQ13 - Events for Position
PQ14 - Events for Task
PQ15 - Events for Company
PSO5 - PD : Administration Tool
PSOA - Work Center Reporting
PSOC - Job Reporting
PSOG - Org Mgmt General Reporting
PSO1 - Tools Integration PA-PD
PSOO - Organizational Unit Reporting
PSOS - Position Reporting
PSOT - Task Reporting
Recruitment
PB10 - Initial Entry of applicant master data
PB20 - Display applicant master data
PB30 - Maintain applicant master data
PB40 - Applicant events
PB50 - Display applicant actions
PB60 - Maintain Applicant Actions
PB80 - Evaluate Vacancies
PBA0 - Evaluate Advertisements
PBA1 - Applicant Index
PBA2 - List of applications
PBA3 - Applicant vacancy assignment list
PBA4 - Receipt of application
Infotype tabes :0000,0001,0002,0006,0007,4000,40001,40002 etc
DB Tables :PA0000,PA0001,PA0006,PA0007 etc
****Reward points if found useful
Regards,
Naresh

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

HR-ABAP: Defaulting Radio Button on Selection Screen of PNP LDB

Hi all,
I am using PNP LDB (Logical Database) for program which is used for Payroll Results.
Now I have a requirement wherein it is necessary to select 'Up to today' as default on the selection screen.
We are having 4.7C version of SAP. I tried following code in INITIALIZATION event:
Initializing Selection Screen Data Selection Option to 'Up To Today'
INITIALIZATION:
MOVE: 'X'    TO    pnptimr4, " This is the option which I want as Default selection.
         space TO    pnptimr1,
         space TO    pnptimr2,
         space TO    pnptimr3,
         space TO    pnptimr5,
         space TO    pnptimr6.
But still I dont see this Radiobutton getting selected as Default selection while running the program.
By Default it selects Option : 'Other Period' (pnptimr6).
Any Idea how to resolve this ??
Regards,
Avinash

hi...
When the INITIALIZATION event occurs, you can set default values for the selection screen.
The fields for the data selection are defined in structure QPPNP.
Possible values for field PNPTIMED are:
D     =      Today (key date)
M     =     Current month
Y     =     Current year
P     =     To current date
F     =     From today (from current date)
The person selection fields are defined in include program DBPNPSEL. They are internal tables that must be filled using APPEND.
so in intialization you have to write code as
PNPTIMED : P.
so up date will be defaulted in selection screen.
award points if helpful.

Structure of ldb

Similar Messages

Maybe you are looking for