Need of logical database

Hi,
Can any one briefly explain what is the need of Logical database?
In which case , abapers r going for logical database?
regards,
Pooja

Hi Pooja,
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.
GET will fetch the table data immediately
GET LATE
In the LDB when you define the table structure in hierarchy, first it will fetch the higher node data and then all the below node tables data and comes to a second record in the top node table. for this GET Late is used.
You can create any number of primary keys in a table
The programmer need not worry about the primary key for each table.Because Logical database knows how the different tables relate to each other,and can issue the SELECT command with proper where clause to retrieve the data.
i)An easy-to-use standard user interface.
ii)check functions which check that user input is complete,correct,and plausible.
iii)meaningful data selection.
iv)central authorization checks for database accesses.
v)good read access performance while retaining the hierarchical data view determined by the application logic.
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
Reward if useful.
Regards,
Hemant

Similar Messages

Help needed in Logical Database Programming

Hello Gurus,
I am working on a Report on ASSET ACTIVITY BY DATE RANGE .
The program is copied from std. program S_ALR_87011990.
The above std. program displays for the whole financial year. This is modified for a particalar period range in the new leveraged program.
My question is in the below code.
We are fetching data using LDB ADA. The statement "GET anlcv" works fine here, I mean Sy-subrc is 0 and anlcv structure has some data in it.
When it comes to statement "GET anepv" in the below code, we are not getting any data into that structure and sy-subrc NE 0. Then it is skipping all the get statements and directly going to statement " PERFORM abga_simulieren.".
My logic lies in between this Get statement and the perform statement. When i see it in debugging mode my statement is not executed at all.
What needs to be done. Please anyone help me.
GET anlcv.
CHECK select-options.
MOVE anlcv TO sav_anlcv.
GET anepv.
CHECK select-options.
Nur Bewegungen des Jahres des Berichtsdatums durchlassen.
CHECK anepv-bzdat GE sav_gjbeg.
CHECK anepv-bzdat IN so_bzdat. "Added for SIR-3132
Bewegungen in SAV_ANEPV sammeln.
MOVE anepv TO sav_anepv.
APPEND sav_anepv.
GET anlb LATE.
Check auf Bestandskonto bei Gruppensummen erst hier, wegen
fehlender Abgänge/Umbuchungen
IF NOT summb IS INITIAL.
IF NOT anlav-ktansw IN so_ktanw.
REJECT 'ANLAV'.
ENDIF.
ENDIF.
ANLCV aus Save-Area zurueckholen.
CHECK NOT sav_anlcv-anln1 IS INITIAL.
MOVE sav_anlcv TO anlcv.
Abg-Simu: Abgang simulieren.
PERFORM abga_simulieren.
Promise to reward points
Regards
Mac

1) delete line CHECK anepv-bzdat ge sav_gjbeg.
2) test with an asset , which has movements (purchases) in your intervall so_bzdat.
otherwise post a movement (e.g. transaction type 100) with tcode abzon
A.

Regarding Logical database and select statement..

Hi
Experts.
i would like to know the diff b/w logical data base & select statement while using report.
wt is the use of logical databases in R/3. is there   any   advantage used in the reports.
Thanks & Regards..
Spandana.

Dear Spandana,
Go through the below description of LDB. I hope you wil get a fair amount of idea.
SAP comes loaded with all the extras. Among the extras that are most helpful to IT managers are all the access routines needed to pull any business object that managers can think of out of SAP databases. However, SAP has not thought of everything where your particular applications are concerned. SAP organizes its standard database tables to service business units based on conventional business applications. Itu2019s likely your business requires something new, perhaps even something exotic. In that case, you will need to create a new database, using information from different places. Basically, you need a logical database. You need to create a virtual business data object repository consisting of a new kind of record or table that suits your purposes. In addition, the repository should be composed of information that is actually stored in a number of different locations, none of them necessarily logically associated with one another. Letu2019s take a closer look at creating logical databases.
A case for a logical database
Suppose my company manufactures widgets of the most obscure variety, and they are components of other widgets. I sell my widgets as raw material for the more sophisticated widgets built by others, but in some cases I actually partner with other manufacturers in creating yet another class of widget. Now, in my world, I consequently have customers who are also partners. I sell to them and I partner with them in manufacturing and distribution. Also, I need an application that uses both of these dual-use relationships.
Essentially, I have a customer database and a partner database. Neither contains records that are structured to contain the identifying particulars of the other. Thus, I need a hybrid database that gives me tables detailing these hybrid relationships. What can I do? I can go the long way around and write a new database, pulling information from both and creating new objects with a customized program that I write by hand. However, this process is cumbersome and contains maintenance issues. On the other hand, I can use SAPu2019s logical database facility, create my logical database in a couple of minutes, and have no maintenance issues at all.
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.
u2022     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.
u2022     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.
u2022     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.
Regards
Arindam

Logical Database for a Resource

Hello,
I'm looking to write a query in Quickview (SQVI) and I need the logical database for a Resource. Can anyone help?
Thanks,
B

There are two ways for this -
1. To create the functional area with a logical database
Tools => ABAP/4 Workbench => Utilities => ABAP/4 query => Functional Areas.
Give the functional area name and click on Create button
In the next screen give a brief description of the functional area
Specify the name of the logical database, for e.g. Database FI, Application S. This will be the definition for the flight database
Click on the button Functional Group present on the application toolbar, in order to create the functional group for the required fields from the logical database tables
In the functional group box mention the number of the functional group and the description for the functional group
The tables from the logical database are shown in Tables Of Logical Database/Joins while the fields are displayed in the Fields Box
Double click on the table name in order to change the list
Every field that has to be selected in the query should be assigned a functional group number against it
Sometimes the list of fields in the Fields box will not be completely visible. To have a wider display of the list place the cursor in the fields box area and click on Settings => Full Screen from the SAP menu bar
To see the fields from different tables select the table and double click on it.
Once the required fields are selected, save the functional Area by clicking on the SAVE icon on the toolbar, and then Generate the Functional Area by clicking the Generate icon on the toolbar
To add user defined fields to the abap query use the menu bar option GOTO => Additional Field
Give the field name and the table name from the logical database to which the field needs to be included. Click the ENTER button.
On the next screen give the Sequence, description, title and the technical attributes for the field (field type, length). Here you can also specify the formula for the field. Click on the SAVE button to register the data to the database.
Remember that the sequence of the field matters if the second field uses the first field in its code then the second field should have a higher sequence than the first. Tables can also be included to do this use the menu option Goto => Additional Tables
You can include your own selection criteria and parameters to control the data to be selected from the database. For these additions to get activated, code needs to be written for taking care of the additional fields.
To display something before the execution of the actual query, go to the start of selection event via the menu path Goto => Code => Start-of-selection.
To display something just before or after the output of the query, go to the end of selection event via the menu path Goto => Code => End-of-selection.
To display something at the beginning of the page, go to the top of page event via the menu path Goto => Code => Top-of-page.
After finishing everything save and generate the functional area and click on the BACK icon to come out.
2. To create a functional area without a logical database
One of the following can be selected
Based on a single table
Using an ABAP/4 program
Using Table Joins
Using Sequential Dataset
The steps to be followed for creating the functional area are as follows
Tools => ABAP/4 Workbench => Utilities => ABAP/4 query => Functional Areas.
Give the functional area name and click on Create button
In the next screen give a brief description of the functional area
In the Without a logical database area give the base table on which to form the ABAP query
To form the query with two or three tables, we need to create a join. For this check the Table Join Check Box and click on the Table Join button.
NOTE: The tables to be used in the join should have at least one field in common i.e. it should have the same name, domain or data element.
Mention the tables that you want to include in the join condition in the Joined Tables area and press ENTER.
A checkbox will appear against the table names on the left side, and three radio buttons will appear against the tables on the right side specifying the join type.
Base table name remains grayed out. Select the two tables to be involved in the join by clicking the check boxes against them. Use menu path Edit => Join => Define condition to create the join. A mapping between the tables will be displayed on the right hand side. Click on the button provided (with + and down arrow symbol) to specify the join.
Click YES on the Proposal Requested message that gets displayed.
If the join tables have a foreign key relationship then the common fields in the tables will be marked with 00 to indicate that the join has been created. User can create the join by specifying 00, 01 etc. against the fields that qualify for the join.
Complete the join condition by adding more tables if necessary.
Remaining concepts for creating the functional area without a logical database are same as the concepts for creating the functional area with a logical database.
After finishing everything save and generate the functional area and click on the BACK icon to come out.
Thanx!

Why and how we use Logical Database?

Can anybody explain with example why and how we use logical database?
Regards,
Rajan

Hello,
SAP comes loaded with all the extras. Among the extras that are most helpful to IT managers are all the access routines needed to pull any business object that managers can think of out of SAP databases. However, SAP has not thought of everything where your particular applications are concerned. SAP organizes its standard database tables to service business units based on conventional business applications. Itu2019s likely your business requires something new, perhaps even something exotic. In that case, you will need to create a new database, using information from different places. Basically, you need a logical database. You need to create a virtual business data object repository consisting of a new kind of record or table that suits your purposes. In addition, the repository should be composed of information that is actually stored in a number of different locations, none of them necessarily logically associated with one another. Letu2019s take a closer look at creating logical databases.
A case for a logical database
Suppose my company manufactures widgets of the most obscure variety, and they are components of other widgets. I sell my widgets as raw material for the more sophisticated widgets built by others, but in some cases I actually partner with other manufacturers in creating yet another class of widget. Now, in my world, I consequently have customers who are also partners. I sell to them and I partner with them in manufacturing and distribution. Also, I need an application that uses both of these dual-use relationships.
Essentially, I have a customer database and a partner database. Neither contains records that are structured to contain the identifying particulars of the other. Thus, I need a hybrid database that gives me tables detailing these hybrid relationships. What can I do? I can go the long way around and write a new database, pulling information from both and creating new objects with a customized program that I write by hand. However, this process is cumbersome and contains maintenance issues. On the other hand, I can use SAPu2019s logical database facility, create my logical database in a couple of minutes, and have no maintenance issues at all.
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.
u2022     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.
u2022     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.
u2022     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.
Regards
Arindam

Need to restrict selection screen entries in logical database in HR report

After creating custom HR Report Category using Logical database, I need to restrict the options available in the in the selection Screen
for example- for company code i m getting 182 entries, but after running the program, selection-options for company code, i need only first 3 entries, don't want remailing entries
how can i do this?

Hi
You can retrieve the required entries into an internal table and use FM F4IF_INT_TABLE_VALUE_REQUEST to provide them under F4 help.
Regards
Raj

Need to specify LEFT OUTER JOIN while using data from logical database BRM?

I'm trying to extract data for external processing using SQVI. The fields required are in tables BKPF (Document Header) and BSEG (document detail) so I'm using logical database BRM. Note: required fields include the SPGR* (blocking reasons) which don't appear to be in BSIS/BSAS/BSID/BSAD/BSIK/BSAK, hence I can't just use a Table Join on any of these but have to use BSEG, hence BRM.
If the document type is an invoice, I also need to include the PO number from table EKKO (PO header), if present, hence I'd like to add this to the list. However, if I do this, it seems that some records are no longer display, e.g. AB documents.
The interesting thing is that not all records are suppressed, so it's not a simple case of the logical database using an effective INNER JOIN, but the effect is similar.
In any event, is there a way to specify that the link to table EKKO should be treated as an effective LEFT OUTER JOIN, i.e. records from BKPF/BSEG should be included irrespective of whether any records from EKKO/EKPO exist or not?
Alternatively, is there some other way to get the SPGR* fields (for example) from BSEG and still join the BKPF? Of course, one solution is to use multiple queries, but I was hoping to avoid this.

Thanks for everyone's responses, I know how to work around the problem with sql, I am wanting to see if there is a way to make the outer joins filter go in the join clause instead of the where clause with Crystal Reports standard functionality.
We have some Crystal Reports users that are not sql users, i.e. benefit specialists, payroll specialists and compensation analysts who have Crystal Reports. I was hoping this functionality was available for them. I just made my example a simple one, but often reports have multiple outer joins with maybe 2 or three of the outer joins needing a filter on them that won't make them into an inner join.
Such as
Select person information
outer join address record
outer join email record
outer join tax record (filter for active state record & filter for code = STATE )
outer join pay rates record
outer join phone#s (filter for home phone#)
I thought maybe the functionality may be available, that I just don't know how or where to use it. Maybe it is just not available.
If it is not available, I will probably need to setup some standard views for them to query, rather than expecting them to pull the tables together themselves.

Do I need to do authority check for Logical Database?

Hi,
Just to check, do I need to code authority check into a Logical Database or Logical Database will do the check by itself without me coding?
This is because I have a user which does not have rights to infotypes 2000 and above and the logical database still show the user data which belongs to the infotypes 2000 and above.
If I have to code it, how do I go about to do the coding of authority check?
Thanks in advance. Will reward points for good solutions.
Lawrence

Let me give an example
Tables : pernr.
infotypes: 0000, 0001, 2001.
Get pernr.
Do you mean that the 'get pernr' command will not return any data for users who do not have authorisation for infotype 2001?

Use of Logical Database in function module

Hello Experts,
Is there a way of using logical database and Get enent inside a function module.
I am trying to create a RFC for HR module and need this badly. Any help would be highly appriciated.
Thanks,
Gregory fernando

This fm will work fine with all LDBs including PNP
Have you checked the fm documentation ?
a®

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

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

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

Use of Logical database in ABAP Queries

hi,
Can anybody tell me when/why do we use logical database in Infosets for ABAP Query?
Regards,
Divya

hi,
pros: -you need not to define so many own tables, fields and additional codings in your info set
cons: - performance in huge DB's
A.
Message was edited by: Andreas Mann

Logical database in sd

hi experts,
i need standard LDB's related to the tables of sd, mm and fi... can anyone help regarding this.....

Ok so here you are, If you want to edit one go to SE36
LDB name
Logical database short text
50V
Delivery in process
AAV
Logical Database RV: Sales Documents
ABCLAIMLDB
Agency Business: Complaints Processing
ABS
ABAP Book: Customer and bookings
ACAC_ACE_LDBDS
Accrual Object Distribution Server Reporting Table
ACAC_ACE_LDBPS
Accrual Engine Posting Server Reporting Database
ACE_FILA_LDBDS
Accrual Object Distribution Server Reporting Table
ACE_FILA_LDBPS
Accrual Engine Posting Server Reporting Database
ACE_SOP_LDBDS
Stock Option Accounting Distribution Server LDB
ACE_SOP_LDBPS
Provisions for Awards: Posting Server LDB
ACEDS_003
Accrual Object Distribution Server Reporting Table
ACEPS_003
Accrual Engine Posting Server Reporting Database
ADA
Assets Database
AFI
Logical database for orders
AGENCYLDB
Agency Business: Logical Database
AKV
Logical Database RV: Sales Documents
ALV
Archiving Deliveries
ARV
Logical Database RV: Sales Documents
ASV
Request Screen for Summary Information
AUK
Settlement documents
AUW
Allocation Table
B1L
Transfer requirements by number
BAF
BAV-Data collector
BAM
Purchase Requisitions (General)
BANK
Logical Database for Table BNKA
BBM
Archiving of Purchase Requisitions
BC405_DIFF_NODES
Example of Different Node Types
BJF
Loans flow records with date restriction(YR
BKK
Base Planning Object
BKM
Purchase Requisitions per Account Assignment
BMM
Documents for Number
BPF
Treasury Business Partner
BRF
Document Database
BRM
Accounting Documents
BTF
Loan portfolios and flows
BTM
Process Order; Print
BUCHUNGSJOURNAL
LDB for Posting Journal
BUD
LDB For Loans Master Data, Conditions, Documents
C1F
Cash Budget Management
CCLDB_AENR
ECH: Change number with status information
CDC
Document structure
CEC
Equipment BOM
CEK
Cost Centers - Line Items
CFK
Data pool for SAP EIS
CIK
Cost Centers - Actual Data
CKA
Costing
CKC
Sales order BOM
CKM
Material master
CKQ
Material Selection for New Costing Solution
CKS
MiniApp. for the Calculator: Sales Order Data
CKS_WAO
MiniApp: Sales Order Items to be Processed
CKW
Costing run: Material Selection
CMC
Material BOM
CPK
Cost Centers - Plan Data
CRC
Work Centers
CRK
Cost Centers - Total
CRZ
Logical database for courses BC220/BC230
CSC
Standard BOM
CSR
Logical database for archiving BOMs
CTC
Functional location BOM
DBM
MRP Documents
DDF
CUSTOMER DATABASE
DPM
Planned Orders
DSF
Loan Debit Position
DVS
Logical database for archiving DMS data
DWF
Loan resubmission
EBM
Purchasing Activities per Requirement Tracking No.
ECM
Purchasing Documents per Material Class
EHS_OH001
Logical Database for Occupational Health
EKM
Purchasing Documents per Account Assignment
ELM
Purchasing Documents per Vendor
EMM
Purchasing Documents for Material
ENM
Purchasing Documents per Document Number
EQI
Logical Database (Equipment)
ERM
Archiving of Purchasing Documents
ESM
Purchasing Documents per Collective Number
EWM
Purchasing Documents per Supplying Plant
F1S
BC: Planned flights, flights and bookings
FDF
Cash management and forecast
FDK
IS-U/FERC: Drill down to line items and paths
FEF
Cash Management - Memo Records
FILA
Lease Accounting
FMF
Funds Management
FPMF
LDB, reads FPAYH and FPAYP
FRF
Drill-down Selection Screen
FSF
Cash Management Totals Records
FTI_BW_CFM_VALUES
Market Values and Simulated Values in Pos. Mgmt
FTI_LO_PERIODS
Loan/CML Period Evaluations
FTI_LO_POSITIONS
Loan /CML Positions
FTI_SWAP_POSITION
Swap Positions
FTI_TR_CASH_FLOWS
Treasury Payment Information
FTI_TR_PERIODS
Treasury: Period-Based Evaluations
FTI_TR_PL_CF
Treasury: Revenue and Cash Flow Reporting
FTI_TR_POSITIONS
Treasury Positions
FTLM_DB01
Limit Management
FUK
IS-U/FERC: Drill back from document line items
G1S
text
GLG
FI-SL Totals and Line Items
GLU3
Flexible G/L
I1L
Inventory data for storage bin
I2L
Warehouse quants for storage bin
I3L
Inventory documents
IBF
Real Estate Logical Database (Lease-Out)
IDF
Real Estate Logical Database
IDFPLUS
Real Estate Plus Logical Database
IFM
Purchasing Info Records: General
ILM
Archiving Purchasing Info Records
IMA
Logical database for investment programs
IMC
IM Summarization (not usable operationally)
IMM
Inventory documents for material
IMR
Approp. requests (not operationally functional)
IMT
Approp. requests (not operationally functional)
INM
Inventory documents
IOC
Shop floor control - order info system
IPM_ACE_LDBDS
Accrual Object Distribution Server Reporting Table
IPM_ACE_LDBPS
Accrual Engine Posting Server Reporting Database
IRM
Reorganization of inventory documents
J5F
Logical Database for new Nota Fiscal Database
K1V
Generating Conditions
KDF
Vendor Database
KIV
Customer Material Information
KKF
Balance Audit Trail of Open Items
KLF
Historical Balance Audit Trail
KMV
SD Documents for Credit Limit
KOV
Selection of Condition Records
L1L
Evaluation Whse Documents
L1M
Stock movements for material
LMM
Stock Movements for Material
LNM
Stock movements
LO_CHANGE_MNMT
Logical database for engineering change management
MAF
Dataset for Dunning Notices
MDF
Logical Database for Master Data Selection
MEPOLDB
Logical Database/Selection of Purch. Order Tables
MIV
BC: Planned flights, flights and bookings
MMIMRKPFRESB
Selection from Reservations
MRM
Reorganization of material documents
MSM
Material master
NOTIF
LDB for Basic Notifications
NOTIFICATIONS
NTI
Logical database object networking
ODC
Shop floor control - orders per MRP controller
ODK
Orders
OFC
Shop floor control - orders per prod.scheduler
OHC
Shop floor control - orders by numbers
OPC
Shop floor control - orders by material
PAK
CO-PA Segment Level and Line Items
PAP
Applicant master data
PCH
Personnel Planning
PGQ
QM: Specs and Results of the Quality Inspection
PMI
Structure database (plant maintenance)
PNI
PM Planning Database
PNM
Planning database
PNM_OLD
Planning Database
PNP
HR Master Data
PNPCE
HR Master Data (Incl. Concurrent Employment)
POH
Production orders database - header
PSJ
Project system
PTRVP
Travel Management
PYF
Database for Payment Medium Print Programs
QAM
Inspection Catalogs: Selected Sets
QAQ
Inspection Catalogs: Selected Sets
QCM
Inspection Catalogs: Codes
QCQ
Inspection Catalogs: Codes
QMI
Logical database (PM notifications)
QMQ
Inspection Characteristics
QNQ
Quality Notifications
QTQ
Logical database for inspection methods
QUERYTESTLDB
Test LDB for InfoSet Query
R0L
Archive selection: Transfer orders (MM-WM)
R1L
Archive selection: Transfer requirements (MM-WM)
R2L
Archive Selection: Posting Change Notices (MM-WM)
R3L
Archive selection: Inventory documents (MM-WM)
R4L
Archive selection: Inventory histories (MM-WM)
RBL
Archiving of transfer requests
REAO
Real Estate: Logical Database for Architecture
REBD
Logical Database for Real Estate Objects
REBP
Logical Database via Partner (Real Estate)
RECN
Real Estate: Selection by Contracts
RECONTRACT
RE Logical Database: (General) Contract
RHL
Archiving of inventory history
RIL
Archiving of inventory documents
RKM
Reservations for Account Assignment
RLI
Logical Database Reference Location
RMM
Reservations for material
RNM
Reservations
RTL
Archiving of transfer orders
RUL
Archiving of Posting Change Notices
S1L
Stock by storage bins
S1L_OLD
Stock by Storage Bins
S2L
Warehouse quant for material
S3L
Stocks
SAK
Completely Reversed Allocation Documents
SD_KUSTA
Logical Database for Sales Summary
SD_ORDER
Logical database for inquiries, contracts
SD_SALES_DOCUMENT
Logical database for inquiries, contracts
SDF
G/L Account Database
SMI
Serial Number Management
T1L
Transfer orders by number
T1L_OLD
Transfer Orders by Number
T2L
Transfer orders for material
T3L
Transfer orders for storage type
T4L
Transfer order for TO printing
T5L
Transfer orders for reference number
TAF
Treasury
TIF
Treasury Information System
TPI
Functional Location Logical Database
U1S
User master reorganization: Password changes
U2S
User master reorganization: Password changes
U3S
User master reorganization: Password changes
U4S
User master reorganization: Password changes
UKM_BUPA
SAP Credit Management: Business Partner
V12L
Pricing Report
VAV
Logical Database RV: Sales Documents
VC1
List of Sales Activities
VC2
Generate Address List
VDF
Customer Database with View of Document Index
VFV
Logical Database RV: Billing Documents
VLV
Logical Database For Deliveries
VVAV
Logical Database RV: Sales Documents
VXV
SD: Billing Document - Export
WAF
Securities position plus additional master data
WOI
Maintenance Item
WPI
Maintenance plans
WTF
Securities positions and flows
WTY
WTY LD
WUF
Sec.-Determ.master data for positions
I hope this will delh

Logical database of ABAP query

Hi,
Can anybody please let me know what is the Logical database for ETXDCI, ETXDCH & ETXDCJ (Tax tables) with any sales document tables? I need to develop one ABAP query for the users.
I am a Functional person so I would like to know Can anybody please let me know how I can find out the Logical database?
Your time and help will be really appreciate.
Thanks & Regards,
Niki Shah.

Try the BRF logical database.
I found it by searching in which programs the tables were used.
It show program SAPDBBRF which is the program for logical database BRF.
Kind regards,
Arthur Parisius

Logical Database

Hi,
I have the following issue:
we need to make use of BADI 'MD_PURREQ_CHANGE' here I need to use Logical Database 'DBM' in my implimentation method. Shall we make use of Logical Databse in ABAP Objects? If yes, could you give any ideas please?
Thanks & regards
Sreenivas

Hi,
I tried several times, it seems that is not possible to make use of Logical Database from ABAP Objects.
IS there any ideas?
I am providing some more details:
While I was testing the MRP BADI the MDTB table is not being updated with any data . OSS note 440016 says that there is a customizing setting by which you can still update the MDTB table but this would lead to performance issues (easier to query though).
In standard SAP, MRP data is stored as an aggregated list (table is stored as a data cluster and I need an ABAP extract to get something meaningful from it) in table MDTC for improved performance.
Does any body having an ideas on this?
Thanks & regards
Sreenivas

ABAP Logical Database ADA

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

Hi,
A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
Logical database structures
There are three defining entities in an SAP logical database. You must be clear on all three in order to create and use one.
Table structure: Your logical database includes data from specified tables in SAP. There is a hierarchy among these tables defined by their foreign keys (all known to SAP), and you are going to define a customized relationship between select tables. This structure is unique and must be defined and saved.
Data selection: You may not want or need every item in the referenced tables that contributes to your customized database. There is a selection screen that permits you to pick and choose.
Database access programming: Once youve 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
Heres 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) Youll be prompted for a short text description of your new logical database. Enter one. Youll then be prompted to specify a development class.
4) Specify a root node, or a parent table, as the basis of your logical database structure. You can now place subsequent tables under the root table as needed to assemble the data object you want. You can access this tree from this point forward, to add additional tables, by selecting that root node and following the path Edit | Node | Create. Once youve 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 dont have to write a single line of code.
Noted point is we cant add any selection criteria thru our se38 program if you are attaching any LDB to program.Ist of no use.
If you want to change selection criteria to the existing LDB, you have to goto SE36 tcode and provide LDB name and choose "Change" mode by selecting "Selections" Radio button.
declaration of params is different compared to normal se38 program in some aspects.
PARAMETERS :p_curr LIKE bkpf-waers FOR TABLE bkpf OBLIGATORY.
this BKPF table should be one of the node in the "Structure" Radio button.
Thanks
Sivaparvathi
Please reward points if helpful.

Need of logical database

Similar Messages

Maybe you are looking for