Are the logical database obsolete?

Hi
I read that the logical database it's obsolete, and we should use the function module LDB_PROCESS. I was used to use the logical database pnp, if i want to implement my programs in the new way, what should i change? and how could this impact in the programs?.
Thanks in advance,
Regards,
Albio.-

New Logical database is PNPCE...but still you can use the PNP logical database.
if you use HR_READ_INFOTYPE function module..no need to worry which lbd u are using

Similar Messages

What are the logical databases belongs to HR module.

Hi experts,
Please explain What are the logical databases belongs to HR module.
Thanks,
Rashmi

Hi Rashmi,
There are three LDBs in HR.
1. PNPCE or PNP
2. PCH
3. PAP
Good Luck
Om

What are the logical database source (SQVI) should i use for quick viewer

Dear expert,
Would like to seek for your help, how to use (SQVI) quick viewer/SAP query to generate the listing of and can I use SQVI -quick viewer and select the data source as logical database source to generate in order to generate the listing of GL account number,GL account descrition , tax category,posting without tax allowed column in the query by company?
Between, what are the data source should I use for logical database to generate the query with listing of GL account number,GL account descrition , tax category,posting without tax allowed column in the query by company?
Please help.
Many Thanks.
Regards,
Karen

Hi,
Thank you for the prompt reply, what I would like the query to generate is the master data GL listing for GL account,GL description,Tax category, posting without tax allowed column where i use BRF as the data source for logical database to generate the quick viewver but the BRF data source do not have the GL description.
How I can join table/join query or what are the data source should i use so that i can able to generate the query with GL master data listing by company code by display GL account,GL description,Tax category, posting without tax allowed?
Between,do you have any reference/link/document on the how to use the SQV1?
Also, what the difference between SQV1 and SQ01 ?
And also what are the sap query,inforset query,quick viewer mean for and what are the difference between them also when should i use sap query,inforset query,quick viewer to generate the query?
Please help.
Many thanks.
KH

One of the functional groups of the Logical Database "SDF" does not appear.

Hello,
I have a problem with the logical database "SDF". It has already defined 3 functional groups. When I select the buttom "display the contents" I can see all these groups with their owns fields.
The problem is that when I use a transaction which contains this logical database, in the dynamic selections I can only see two of the functional groups. The last one doesn't appear there and I don't know why.
How can I resolve my problem?
Thank you very much in advance.
Best Regards.

1 hour is the default timeout for "ExternalCommandTimeout". So, it could be that this one measure group's fact query is taking longer than 1 hour for the first record. You can see the query in the error messages and might like to try it out
manually. Note, a common issue is with referenced dimensions or Distinct Count when an inner join or Order By are added to the fact queries.
A simple solution might be to simply increase the ExternalCommandTimeout in the SSAS properties page. Try 7200, and if it completes in less than 2 hours, or fails after exactly 2 hours, you know this is the issue.
Richard

Do we have macros which we can use for the Logical Database PCH

Dear Friends
I would like to know when we are using the
Logical Database PCH .....do we have any macros
for getting latest record etc.
i.e i mean to say the macros which we use
Rp-provide-from-last in PNP logical Database
do we have same facility in PCH logical database please let me know
regards
madhuri.

hi madhuri,
we use same macro.
instead of get pernr .
in pnp here we give
GET OBJEC.
use this macro
PAP_PROVIDE_FROM_FIRST P0001 SPACE PA$BEGDA PA$ENDDA
PAP_PROVIDE_FROM_LAST P0001 SPACE PA$BEGDA PA$ENDDA.
regards,
sandeep patel
Edited by: Sandeep patel on Jul 4, 2008 1:33 PM

How to execute the logical database.

how to execute the logical database.

There are two ways of using a logical database - either by linking it with the executable program(specify the LDB name in the program attributes) or by using the function module LDB_PROCESS.
1.Data read by the logical database is passed back to the program using the interface work areas.Use GET statements in the report.
GET events are implemented internally as FORM routines.
2.If you call the logical database using the above function module, the selection screen of LDB is not displayed.It uses special subroutines called callback routines, which are called by the function module and filled with the required data.
Please refer the following link for more details.
http://help.sap.com/saphelp_nw70/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm

What are the logical structure and physical structure in oracle

what are the logical structure and physical structure in oracle and how can allocate a DB block size as default size is 8192?

From the Concepts Guide
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/toc.htm
The physical structures are:
Datafiles
Control Files
Redo Log Files
Archive Log Files
Parameter Files
Alert and Trace Log Files
Backup Files
The Logical Structures are:
Tablespaces
Oracle Data Blocks
Extents
Segments

Who are the logical receivers

i couldn't understand who are the logical receivers after reading help.sap. please take one example and tell the importance of logical receivers.
Thank you

Hi Ajay,
Logical routing involves the definition of business services/systems for your interface.
Technical routing involves the definition of the communication channels, adapters, etc.
From a general point of view, whenever you talk about logical routing as such, it deals with the security and authentication aspect. By mentioning the business sytems/services for the interface, you are clearly telling, which client and logical system name XI should talk to, to either send or receive data...and technical routing involves exactly how the data will be sent or received.
Regards,
Sushumna

The logical database ADA

< MODERATOR: Message locked. Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. Do not offer or request points. >
Where do the following fields draw their underlying data from? We need to present the logic behind the data pulled from the following structures.
KTANSW in ANLAV table (structure)
ANLCV derives its partly from table ANLC and the remaining is derived on the basis of some computation.
how does it calculate
NAFA_GJE in ANLCV
and
ANSW_GJE in ANLCV
(Real urgent. Immediate delivery of full points)

look to transaction SE36:
structure and database program SAPDBADA - (PUT ANLAV and PUT ANLCV)
hope that helps
God's blessing to you ALL!
Andreas

What are the logical decisions to make a plant

Dear All,
i know that i am going to ask a very basic question but it is not as simple as seems to be.
Scenario is as undermentioned:
At one premises there is a production unit for cement manufacturing and another unit for power generation. i have made cement plant now please tell me eighter we should make power generation plant or we can handle it under the same cement plant.
Requirement for power generation are that they have to produce power for cement plant and also they sell power to Gowernment. please guide me why we make plant and on the bais of what factors we decide plant.what r the technical reasons to make a plant. what are the requirements which are fulfilled if we make power generation as a plant and what r the requirements which are not fulfilled if we dont make it as a plant.
please guide me the basic factors on the basis of which we decide plant. in detail

Hi,
You might be knowing that, a Plant is a place where production of goods, services are done and provided to external parties.
As you are generating cement from one plant and power from another plant and selling both the product. So, you have to capture the cost and profit for both and you create two different plant.
Now you come to conclusion, if you don't create two plants what will happen? It's self explanatory.
Madhava

What are the openoffice database drivers to establish JDBC? how to code?

I want to use open office database .Please help me how to code inorder to link that open office database with java using jsps.Please tell me.
Edited by: tamminenih on Mar 31, 2009 6:36 AM

You can find information on how to connect here http://dba.openoffice.org/FAQ/specific.html.
Apparently, it is simply mySQL. There is a lot of documentation on the web on how to establish a mySQL JDBC connection. You will need the mySQL connector JAR for the JDBC classes, which can be downloaded from mySQL.
To stitch together a JSP all the way to the back end, you will likely have to do this yourself. There are dozens of tutorials and examples, even cookbooks for how to do so.
- Saish

Problem in using the logical database

The start-of-slection event is not getting triggered. It will get triggered sometimes and sometimes it will never get triggered. Can anyone explain why it is happening so ?

Hi Nishanth,
1. It will get triggered sometimes and sometimes it will never get triggered
How have u tested this ?
2. Immediately after START-OF-SELECTION,
just give one status message (without any condition)
and then EXIT.
3. Now run your program, SEVERAL TIMES,
It must get triggered every time.
(u can see the message in status bar)
4. START-OF-SELECTION.
MESSAGE s999(yhr) WITH 'abc'.
EXIT.
regards,
amit m.

Logical Database being obsolete, we migrate towards...?

Hello.
I have been asked to rewrite a program Z that is in a lack of performance lately. I have looked at it and saw that it was using a logical database. After fixing and changing a few performances things like the SELECT/ENDSELECT and that kind of usual perfomance stuff, I read in my research that I did that it was still maintainted and used on the old programs but it is now something obsolete.
After reading on what it is and how big is their impact, I was wondering what is now replacing them when you need something similar on a newer program.
For example, in the request I have, the DDF logical database is used and is huge too. Though, in the new version, where I will try to prevent myself of using a logical database due to the fact it is obsolete, I am wondering what I can use instead to make a similar job.
After all, a huge concept like Logical Databases /has/ to have something that took over to replace them, right?
Thanks in advance for your help!

Hello again,
I understand what you mean but the performance cost actually is too high to be neglected. The program is actually making a call of GET KNA1, GET KNB1 and GET BSID which means 3 loops blocks in each other, not counting the possible loops needed in internal tables. This is quite a problematic at the moment because this old program now uses those three GET and the massive amount of datas in those three tables makes it that the performance is leading mostly to a short dump than a good final result.
This is why I was looking for an alternate way, looking towards if the Logical Database who is still used but declared "obsolete" was now having a replacement nowadays.
As far as the datas are concerned, to answer your question, the archivages of them happened time after time after time and everyday. It is getting to a point that we are too close of the actual date to even think of more archivage. Believe me, the datas involved, since this problem started, has been verified over and over again. But I know it was an option and thank you for suggesting it.
So it is really a perfomance issue and since the Logical Database takes a lot of performance, like John Armytage confirmed, I am trying to find an alternative to all this. Any suggestions? I still have not found anything that is replacing Logical Database today.

Using Logical Databases and the Tables or Nodes Statement

I want to start using Logical Databases whenever possible, but it seems that I need to use the Tables or Nodes statement for the Get statement to work. Is there anyway to avoid Tables/Nodes statement since they are obsolete (and still use LDBs)?
Message was edited by: Jason DeLuca

Hi Jason,
1) table statement is obligatory:
-> look at abap-docu to GET:
node is a node in the logical database that is assigned to the report (type 1 program) in the program attributes. <b>You must declare the node in the report using the NODES statement (or the TABLES statement, if the node is of the type "table").</b>
2) some ldb-selections from the selection screen
depends on the table-statement too, i remember...
regards Andreas

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.

Are the logical database obsolete?

Similar Messages

Maybe you are looking for