Logical Database o/p in ALV

Dear Expert.
I have to call AFI logical database in ZPROGRAM. If I write GET DIAUFK (root node)
How do I fetch data form parent and child node?
O/p should come as ALV on that alv pop-up will come on that pop up list of transaction displayed which will work on click.
Please suggest.
START-OF-SELECTION.
GET DIAUFK .
*get late
*GET DIIHPA.
GET DIIFLO .
*GET DIQMEL.
MOVE-CORRESPONDING DIAUFK TO ITAB.
*MOVE-CORRESPONDING DIQMEL TO ITAB.
APPEND ITAB.
GET DIAUFK LATE.
IF S_ERDAT NE SPACE AND S_WERKS NE SPACE.
ITAB-ERDAT = S_ERDAT .
ITAB-WERKS = S_WERKS .
ENDIF.
END-OF-SELECTION.
LOOP AT ITAB.
IT_FINAL = ITAB.
APPEND IT_FINAL.
ENDLOOP.

Try exploring FM 'LDB_PROCESS'
<removed by moderator>
Edited by: Thomas Zloch on Aug 9, 2010 2:56 PM - don't ask for ...

Similar Messages

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

Use logical database to fetch data in FI reports

Hi All,
          is it possible to fetch data using logical database for FI module ALV reports.
please provide me details.
Thks
Shailesh

look at the logical database tables for the FI module
BMM                  Documents for Number
BRF                  Document Database
BRM                  Accounting Documents
DDF                  CUSTOMER DATABASE
KDF                  Vendor Database
SDF                  G/L Account Database

ABAP query using logical database KDF is not populating custom fields

Hi Experts ,
I created two following queries
1.       VENDORCATKDF – uses KDF logical database
2.       VENDORCATLFA1 – uses table = LFA1
I’m pulling the same information in both queries:
·         Vendor Number
·         Country
·         Vendor Name
·         Vendor Category (custom fields added to LFA1)
The results for the query that uses the logical database KDF is incorrect. It doesn’t pull in the flag on the custom field LFA1-ZMRO.   Even though the logical database KDF is made up of the table LFA1 and has these fields.
Is there something that can be done – so that all of these “custom” category fields under LFA1 (such as LFA1-ZZMRO) – get pulled into queries – when we use the logical database KDF ?

Hi,
I have got the error removed by ensuring that fields from one table are a part of one line ( taking help of ruler) only. But the underlying problem remains, the output is not ALV but List output.
I do not think having additional fields in the query is reason for this.
Is it bcoz iI am adjusting the output length of columns to ensure no hierarchical error ?
Can we not have a query using LDB which is shown as SAP List?
Regards,
Garima.

HR Logical database PNP. OO to fill table dynamic table from PNP ?

Hi all
I want to get some stuff from the HR logical database into a dynamic table
Here's a real simple example that writes info out to a normal list.
(report is based on using Logical DB PNP)
tables: pernr.
INFOTYPES: 0001, "Organizational Assignment
 0002. "Personal Data
SELECT-OPTIONS: language FOR p0002-sprsl.
INITIALIZATION.
pnptimed = 'D'.
GET pernr.
PROVIDE * FROM p0002 BETWEEN pn-begda AND pn-endda.
 CHECK language.
 WRITE: / p0002-pernr,
 sy-vline,
 p0001-ename,
 sy-vline,
 p0002-sprsl,
 sy-vline,
 p0002-gbdat.
ENDPROVIDE.
endform.
Now what I want to do is replace the write stuff by appending the entries into a dynamic table which I will display as an ALV Grid.
so I add my structure in the data declarations
types: begin of s_elements,
 pernr type p0002-pernr,
 ename type p0001-ename,
 sprsl type p0002-sprsl,
 gbdat type p0002-gbdat.
drop_down_handle type int4.
types: end of s_elements.
include zz_jimbo_incl.
build the dynamic table
create data dref type s_elements.
assign dref->* to <fs>.
i_routine = 'POPULATE_DYNAMIC_ITAB'.*
i_names = 'NAME_COLUMNS'.
i_gridtitle = 'HR TEST'.
invoker = sy-repid.
i_zebra = 'X '.
i_edit = ' '.
call function 'ZZ_CALL_SCREEN'
 exporting
 invoker = invoker
 my_line = <fs>
 i_gridtitle = i_gridtitle
 i_edit = i_edit
 i_zebra = i_zebra
 i_names = i_names
 i_routine = i_routine
 importing
 z_object = z_object
 dy_table = dy_table.
Now to populate the dynamic Itab the routine below is entered.
form populate_dynamic_itab changing dy_table.
assign dy_table->* to <dyn_table>.
create data dy_line like line of <dyn_table>.
assign dy_line->* to <dyn_wa>.
However I can't use GET / PROVIDE / ENDPROVIDE in a Form.
Anyway round this ---seems HR has an aversion to OO.
Cheers
jimbo

Hi,
well, GET_PERNR is a so called event_statement. It has nothing to do with ABAP 00.
Normally it will be like this:
START-OF-SELECTION.
GET_PERNR.
PROVIDE ....
END-OF-SELECTION.
-> and here the CALL SCREEN NNNN for ALV-Display.
Provide-statements you can use in forms of course, and as many times you want during GET and END-OF-SELECTION.
But as I understood : you just want to save the write-statements?
I always develop a DDIC-Structure, declarate the data objects in the programm, read the data via Provide into the infotypes, and then make a move-corresponding to my structure. and display it.
Normally no problem.
kind regards
maik

ABAP Objects and table processing (with logical databases)

I have a report that is written right now using procedural abap and a logical database. The report is structured follows (high level):
start-of-selection.
get pernr.
perform get_it0001 using wtab.
perform get_it0002 using wtab.
perform get_it0003 using wtab.
append wtab to itab.
end-of-selection.
call function 'reuse_alv_grid_display'
 exporting
 i_structure_name = 'itabstructure'
 tables
 t_outtab = itab.
So basically I'm going through a bunch of personnel numbers, getting a few infotypes and outputting to ALV. I don't see where ABAP Objects is going to help me for this particular program.
Can somebody show me where OO ABAP would make this easier? Does it even make sense to use OO when you're processing with a logical database? (Not just PNP, but any logical database in general).
Thanks in advance.

Hello Lee
I assume that the routines GET_ITnnnn are written by yourself. For reading infotypes ABAP Objects provides us with same very helpful classes as shown below:
* define data
DATA:
 gif_employee type ref to if_pt_employee,
 go_employee type ref to cl_pt_employee,
 gt_infotypes TYPE tim_tmw_itlist_tab,
 go_control TYPE REF TO if_pt_td_control,
 go_data TYPE REF TO if_pt_td_base,
 go_pnnnn TYPE REF TO if_pt_td_itnnnn,
 gt_p0001 TYPE TIM_P0001_TAB,
 gt_p0002 TYPE TIM_P0002_TAB,
 gt_p0003 TYPE TIM_P0003_TAB.
start-of-selection.
GET pernr.
* Create employee instance
gif_employee = cl_pt_employee=>get_employee( pernr ).
go_employee ?= gif_employee.
* Get master infotypes (0001, 0002)
CALL METHOD go_employee->get_master_data
 EXPORTING
 im_begda = id_fromdate
 im_endda = id_todate
 IMPORTING
* EX_I0000 =
 EX_I0001 = gt_p0001
 EX_I0002 = gt_p0002
* EX_I0007 =
* EX_I0008 =
* Append all other required infotypes to itab
APPEND '0003' TO gt_infotypes.
CALL METHOD go_employee->get_infotypes
 EXPORTING
 i_itlist = gt_infotypes
 i_fromdate = id_fromdate " start date
 i_todate = id_todate " end date
* I_FILTER =
 i_noauthcheck = 'X'
 IMPORTING
 e_result = gt_infty_request
 e_retcd = gd_retcd.
* Please see documentation of parameter e_retcd...
LOOP AT gt_infty_request INTO go_control.
 go_data = go_control->data. " get data object
* Casting
 TRY.
 go_pnnnn ?= go_data.
 CATCH cx_sy_move_cast_error.
 CONTINUE.
 ENDTRY.
* Convert infotype (semi-transparent -> transparent)
 CALL METHOD cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
 EXPORTING
 prelp = lo_pnnnn->prelp
 IMPORTING
 pnnnn = gs_p0003.
 APPEND gs_p0027 TO gt_p0003.
ENDLOOP.
The class CL_PT_EMPLOYEE provides us already with very easy access to so-called master infotypes (000, 0001, 0002, 0007 and 0008). All other infotypes can be read using method GET_INFOTYPES.
Using these classes we have a very convenient and standardized way of accessing all kinds of infotypes.
Regards
Uwe

Getting results from LDB (Logical Database)

Hi All,
I have a requirement where i need to pass LDB results to external application. It can be any LDB. Like in SE36 we put the LDB name and execute and final results are shown in ALV. I dont need it to display in ALV but from my custom program, need that output table which stores these results.
I tried using LDB_PROCESS but that need custom subroutine names to pass in that, i tried passing the same and results also came but thing is every logical database will have different tables in that, it'll be impossible to create those many subroutine to handle each and every table. So i need a generalized solution like se36 processes the data for any LDB.
Is anyone knows how can i achieve this?
Regards
Munish Garg
9041793217

Hello
Generally any LDB will have a event which triggers the data to be populated in the tables/memory. Now these data retrieval is written in a sub-routine "Perform PUT_<eventnamt>". So any LDB will have the sub-routine named "PUT_<eventname>" in its main program. May be you can create the sub-routine name dynamically using this method.
Regards
Ranganath

Logical database PSJ for tcode CJI3 - add additional

Hi,
I need to create the customized program which refer to standard program RKPEP003 (CJI3) with additional fields require to be added in selection screen and ALV report.
I checked in program attribute for program RKPEP003, there is no selection screen version exist for this logical database. Could anyone advise how do I add the additional fields in either selection screen/ ALV report (eg: Vendor). Thanks.

Hi,
I managed to add the additional fields (eg: Vendor) in ALV report in CJI3 using the user exit.EXIT_SAPLKAEP_001.
Now, I require to add this field in the CJI3 selection screen. I tried to maintain this field via SE36 - Maintain selection Views, but the Vendor field (eg: EKKO-LIFNR) which I required is not able to display out. Anyone have any ideas on it or how should I add this additional selection screen option?

Logical database PNP (Suppress message)

Hi,
      we are having 1 report which is using logical database PNP
      this is being shown in ALV
      when the user runs the report the output is shown and after pressing BACK button the below lines are being shown
Personnel numbers skipped by the database driver
Reason 1: insufficient authorization, no. skipped personnel nos.:
this is being done by logical databse program SAPDBPNP
is there any way to supress this mesasge
thanking you in advance
regards
Sai easwar

I belive this is not concurent employment why we need to use
PNPCE
Please be specific about your question
Regards

Asset Reporting - Copying Logical Database ADA

Can you please assist with the following query? Im trying to include the following standard R3 ffields within standard R3 reports AR01 (Asset Balances) & AR18 (Depreciation Simulation):
                                Table            Field Name            Data Element
Serial Number            ANLA            SERNR                AM_SERNR
Inventory Number       ANLA            IVNR                   INVNR_ANLA
To date I have been unsuccessful in my endeavours.
I have been discussing with an ABAPer and have been discussing the creation of Z transactions to give me the information Im looking for.
Im looking for help, assistance and expertise whether the following would be recommended or even technically feasible.
·     Is it possible to copy logical database ADA to say ZADA (if yes how would I or the ABAPer go about this)?
·     Is there a way to link existing R3 reports to the new logical database
As the majority of the R3 reports appear to be linked to ADA the aim is to amend this once and not require creating lots of Z reports.
Any help you could provide would be greatly appreciated
Best regards,
Paul

Hi Paul,
this is strange, what release are you on?
I have just checked AR01 on ECC 6.0, and it offers everything you need. On the selection screen of AR01, you can add selection criteria on both Serial number and Inventory number. Plus, you can display both fields in the ALV list.
The data may be stored on table ANLA physically, but the logical database ADA is using a structure (ANLAV) instead. Both SERNR and INVNR are available in that structure. On the selection screen, you have to use the Dynamic selections button. And in the ALV list, you simply add the 2 columns, best idea wold be to save it as a variant for future use.
Anyway, logical databases can be copied in SE36, you simply have to press the Copy button The more critical issue is how to link standard reports to the new LDB. The answer is, no way. Instead, you should copy some of your favorite standard reports, and change the LDB in the copies.
But, I really do not think you need this, as ADA can provide you with the information required out of the box.
Hope that helps, points welcome
Csaba

SAP / ABAP Query - using logical database

Hi ,
We have a mandate to implement SAP Query using only Logical Databases (LDB ) .
We understand that there are several issues using this approach .
1 ) Paralled tables in MM need to be displayed on separate lines .
2 ) Statistics based on fields from 2 different tables cannot be produced eg: EKPO ( PO Number ) and EKKN . (Cost Center )
Please share your experiences .
Thank you in advance .
Kishore
Kishore

Adeel,
I do appreciate your experience and respect you for knowledge on SAP Query.
Joining tables seem simple to IT experts but not so for end users. SAP Query is an end-user tool and users seem to need a simple user-friend, drag-and-drop solution to extract information using SAP Query based on a pre-defined infoset. Various SAP conferences have been advocating the use of SAP delivered Logical Databses to create infosets in order to harness the various advantages of LDBs.
In MM there are several LDBs (e.g. ELM, EBM etc) to create queries on EKPO and EKKN. The problem arises when you use the same LDB to extract information from more than the above two tables e.g. EKPO, EKET, EKKN and EKBE. SAP expects you to display fields on multiple lines and also does not allow producing statistics based on fields from two parallel tables say EKKN and EKBE. Moreover, multi-line reports cannot be produced in the ALV/SLV format.
We are also looking for best practise solutions in providing SAP Query to MM or FI users based on SAP delivered Logical Databases.
Pascal

Adding cost center in RABEST_ALV01 from ANLZ node - ADA Logical database

Hi,
I am trying to display cost center in output list of RABEST_ALV01 ALV report (Copied it to ZRABEST_ALV01).
I was able to include fields which are there in ANLAB and ANLAV in FIAA_SALVTAB_RABEST structure - CI_REPRABEST inlcude. And have included cost center field also in the include (KOSTL).
This ALV report RABEST_ALV01 is reffering to ADA logical database. I included a node explicitly in the program along with other node declaration :
NODES: anla0,
             anlav,
             anlz ,
             anlb,
             anek,
             anepv,
             anlcv.
and added a GET statement in the program GET ANLZ before moving the values to final internal table.
Here, the the issue is that the values of ANLZ is getting displayed as "#".
Kidnly suggest.
Thanks and Regards,
Rashmi

Hi Rashmi,
Please make sure the order of the nodes should be same as the order in which they are there in LDB or else they will be overwritten
Thanks
Bala Duvvuri

Logical Database in Abap Objects

Hi to All
I want do it a program report using a Logical Database.
Is this possible ??? But when I make a GET <node>, occurs the following error:
 "" Statement "ENDMETHOD" missing. ""
I'm doing the following:
CLASS MONFIN IMPLEMENTATION.
 METHOD TRAER_DATOS.
 GET VBRK.
 ENDMETHOD.
ENDCLASS.
Please, somebody tell me how I use the logical database in Abap Objects.
Thank you very much
Regards
Dario R.

Hi there
Logical databases whilst of "some use" are not really part of OO.
If you want to use a logical database in an abap OO program I would create a special class which just does the get data from your DB and pass this either at record or table level.
Techniques such as GET XXXX LATE aren't really part of any OO type of application since at Object Instantiation time you should be able to access ALL the attributes of that object.
As far as OO is concerned Logical databases are a throwback to "Dinosaur Technology".
Since however modules such as SD and FI are still heavily reliant on relational structures (i.e linked tables etc) then there is still some limited life in this stuff but for OO try and solve it by another method.
If you really must use this stuff in OO then do it via a FMOD call and save the data in a table which your method will pass back to your application program.
You can't issue a GET command directly in a method.
Cheers
Jimbo

Logical Database in Webdynpro

Hello,
I have a program in R/3 that is based on a logical database. I don't want to have to write the program all over again in Webdynpro.
Is there a way to use the logical database in Webdynpro for ABAP.

Basically WDA calls a FM and then the following help is a good starting point:
"Calling a Logical Database Using a Function Module"
http://help.sap.com/saphelp_nw04/helpdata/en/64/237f8cd43711d1950b0000e8353423/content.htm
Kindly close the thread and award appropriate a points to the answer given.
Sergio

Logical database in adhoc query

Hello All,
Can anyone tell me what is the logical database in adhoc query?

Hi
When you create a query , you have to select an infoset. Infoset can be considered as a source from which data is populated in the Query Fields.
Infosets are created from Transaction SQ02.
There can be four methods through which an Infoset can become a source of data:
1. Table join ( By joining two or more tables from Data dictionary)
example: Joining tables PA0001 and PA0006 on Pernr to get a one resultant dataset
2. Direct read of Basis Table ( Like PA0001 as a source for data in Infoset )
3. Logical Database ( A Pre-written Program by SAP that extract data from clusters, tables taking care of authorizations and validity periods)
Example : Logical database PNP, PNPCE (Concurrent Employement),PCH ( LDB for Personnel Development Data)
Custom Logical DBs can be created in T_Code SE-36.
4. Data Retrieval by a Program ( Custom code written by ABAP developers which will collect and process data) . This program has a corresponding Structure in data dictionary and the fields of this structure will be used in query)
Reward Points, if helpful.
Regards
Waseem Imran

Logical Database o/p in ALV

Similar Messages

Maybe you are looking for