LDB (Logical Database) results

Dear All,
I have an requirement where I have get the selection screen fields list of logical database(LDB) in my custom program.
Also after getting the selection screen fields, whatever criteria is filled in those, once again i have to take those inputs and get the results by executing the LDB.
Is anyone can help me......
Regards
Munish Garg

You will need to call LDB_PROCESS, but you will have to map the data from LDB to internal table (how do your report "knows" which nodes and which fields from those nodes are to be included in the internal table ?)
So many dynamic statements like CREATE DATA <dref> TYPE REF TO (LBDA-DDIC_TYPE) using the parameter <formname> = LBDA-LDBNODE in a generic FORM <formname> USING <nodename> LIKE LDBCB-LDBNODE and then many ASSIGN statements to map the desired fields to the returned internal table records. At each call of this generic FORM, map each and every "corresponding" fields, add the record to the internal table at the lower level node.
Regards,
Raymond

Similar Messages

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

LDB(Logical Database) selection screen

Dear Contributors,
I am hopefull for finding solution to my problem from one of you.
My requirement is i would like to pass all the elements of the selection screen of LDB to non-sap application so as they can replicate and show all those parameters there. Once those are filled from there then i need to take them and process the LDB.
My question is i dont know how to get the selection screen parameters. I tried using FM 'RPY_DYNPRO_READ' and passed progname and screen number in that. It gave back all the parameters but we cant co-relate which parameter is from which table (like we say MATNR like MARA-MATNR).
Without having Technical details of field, non-sap application could not able to process it or show the required F4 help etc
Anyone know about it, can guide me....
Regards
Munish Garg

call function 'LDB_CONVERT_LDBNAME_2_DBPROG'
       exporting ldb_name             = headsg-logdb "#EC DOM_EQUAL
                  flag_existence_check = space
       importing db_name              = logdbprog
       exceptions others               = 1.
if sy-subrc eq 0.
    call function 'SELOPTS_AND_PARAMS'
         exporting program              = logdbprog
         tables     selpars              = dbselpars
         exceptions program_non_existent = 1
                    subroutine_pool      = 2
                    load_problems        = 3
                    others               = 4.
endif.

LDB(logical database)

Hello all,
I have LDB is BAM. This BAM is used in ME57(RM06BZ00)...when we execute ME57 the selection screen is coming from LDB..My req is i have to insert the new field like POGROUP in ME57 selection screen...so wat i did ultimately i was inserted the new field , which is in LDB select-options...when i execute the LDB inserted newfield is displying in the screen.....
But my problem is when i used the same LDB(which new field inserted) in ME57(RM06BZ00) program this newly inserted Field(POGROUP) is not displying....
Please anyone tell me how to insert the new field in ME57.....

You will need to call LDB_PROCESS, but you will have to map the data from LDB to internal table (how do your report "knows" which nodes and which fields from those nodes are to be included in the internal table ?)
So many dynamic statements like CREATE DATA <dref> TYPE REF TO (LBDA-DDIC_TYPE) using the parameter <formname> = LBDA-LDBNODE in a generic FORM <formname> USING <nodename> LIKE LDBCB-LDBNODE and then many ASSIGN statements to map the desired fields to the returned internal table records. At each call of this generic FORM, map each and every "corresponding" fields, add the record to the internal table at the lower level node.
Regards,
Raymond

Calling LDB (logical Database) into ALV output

h1.Dear Experts,
h3.I have called LDB AFI in my Z program.
h3.My requirement is in program i have to call LDB and output it in ALV display.
h3.But in output only one entry get displayed .
h3.Here is my code......
REPORT ZLDB_PROGRAM1                           .
NODES: DIAUFK.
GET DIAUFK.
TYPE-POOLS: SLIS.
*ALV data declarations
data : begin of itab occurs 0,
aufnr like diaufk-aufnr,
auart like diaufk-auart,
erdat like diaufk-erdat,
ustxt like diaufk-ustxt,
sttxt like diaufk-sttxt,
tplnr like diaufk-tplnr,
end of itab.
data : fieldcatalog type slis_t_fieldcat_alv with header line,
      gd_layout    type slis_layout_alv,
      gd_repid     like sy-repid.
data: gt_events type slis_t_event.
DATA: report_id LIKE sy-repid.
move-corresponding diaufk to itab.
append itab.
fieldcatalog-fieldname   = 'AUFNR'.
fieldcatalog-seltext_m   = 'Order Number'.
fieldcatalog-col_pos     = 0.
fieldcatalog-outputlen   = 10.
fieldcatalog-emphasize   = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'AUART'.
fieldcatalog-seltext_m   = 'Order Type'.
fieldcatalog-col_pos     = 1.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'ERDAT'.
fieldcatalog-seltext_m   = 'Created On'.
fieldcatalog-col_pos     = 2.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'USTXT'.
fieldcatalog-seltext_m   = 'User Status Line'.
fieldcatalog-col_pos     = 3.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'STTXT'.
fieldcatalog-seltext_m   = 'System Status Line'.
fieldcatalog-col_pos     = 4.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
report_id = sy-repid.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK              = ' '
I_BYPASSING_BUFFER             =
I_BUFFER_ACTIVE                = ' '
   I_CALLBACK_PROGRAM             = report_id
I_CALLBACK_PF_STATUS_SET       = ' '
I_CALLBACK_USER_COMMAND        = ' '
I_STRUCTURE_NAME               =
IS_LAYOUT                      =
   IT_FIELDCAT                    = fieldcatalog[]
IT_EXCLUDING                   =
IT_SPECIAL_GROUPS              =
IT_SORT                        =
IT_FILTER                      =
IS_SEL_HIDE                    =
I_DEFAULT                      = 'X'
I_SAVE                         = ' '
IS_VARIANT                     =
IT_EVENTS                      =
IT_EVENT_EXIT                  =
IS_PRINT                       =
IS_REPREP_ID                   =
I_SCREEN_START_COLUMN          = 0
I_SCREEN_START_LINE            = 0
I_SCREEN_END_COLUMN            = 0
I_SCREEN_END_LINE              = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER        =
ES_EXIT_CAUSED_BY_USER         =
TABLES
    T_OUTTAB                       = itab
EXCEPTIONS
PROGRAM_ERROR                  = 1
OTHERS                         = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Please reply.

hi,
Populate one more field in field catalog for each entry and try.
fieldcatalog-fieldname = 'AUFNR'.
fieldcatalog-tabname = 'itab'.
fieldcatalog-seltext_m = 'Order Number'.
fieldcatalog-col_pos = 0.
fieldcatalog-outputlen = 10.
fieldcatalog-emphasize = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
Regards,
Lokeswari.

Logical database LDB

hi,
what is LDB....its benefit
and how to to it for multiple tables ......
.... i want to use LDB instead of table joins...... there are abt 20 tables..... using joins , the performance is slow ...
..... please advise..
thanks

LOGICAL DATABASES:
Logical Databases are used to generate report.
It is a repository object, not a data dictionary object.
Under one logical database, a node is created first for the corresponding table in the database.
A logical database can have any number of related nodes in the hierarchical manner.
First node of the logical database is called as ROOT NODE.
SLDB or SE36 to create logical databases.
Navigations to Create Logical Database:
SLDB -> Specify LDB name starting with Z or Y -> Click on Create -> Opens an interface -> Enter short description
-> Create -> Save under a package and assign request number -> Opens an interface
-> Specify Root Node name (MARA) -> Enter short description for the Root node
-> Specify Database Table name (MARA) -> Create -> Opens an interface
-> Select the Root Node (KNA1) -> Click on SELECTIONS pushbutton from Appn.
Toolbar -> Click on Yes to generate Selection Screens from the Structure
-> Click on No to Search Help -> Opens an Interface
-> Select the checkboxes to create Field Selections and Free Selections
-> TRansfer -> Opens an Include Program -> Decomment Select-Options statement and specify range variable as follows:
SELECT-OPTIONS : MATNUM FOR MARA-MATNR.
-> Save -> Activate -> Come back.
Select the Node -> Click on SOURCE CODE pushbutton
-> Click on Yes to generate source code from Structure and Selections -> Opens a report with two Include Files :
include DBZLOGICAL_DATABASE1TOP . " header
include DBZLOGICAL_DATABASE1NXXX . " all system routines
-> Double click on Header File to declare global variables -> Specify Following code:
TABLES : MARA * Autogenerated
DATA IT_MARA LIKE MARA OCCURS 0 WITH HEADER LINE.
-> Save -> Activate -> Come back -> Double click on System Routine file, where the fetching operations are done
-> Opens an Include File with three subfiles as follows:
include DBZLOGICAL_DATABASE1N001 . " Node MARA
include DBZLOGICAL_DATABASE1FXXX . " init, PBO, PAI
include DBZLOGICAL_DATABASE1SXXX . " search help
-> Double click on the first file -> Specify SELECT operation statement as follows:
select * from mara into table it_mara where matnr in MATNUM.
PUT MARA. * AUTOGENERATED CODE
loop at it_mara.
write :/ it_mara-matnr, it_mara-mtart, it_mara-mbrsh, it_mara-meins.
endloop.
-> Save -> Activate.
To Access LDB node, create SE38 PROGRAM, Specify LDB name in ATTRIBUTES section -> Specify following code in SE38:
NODES MARA.
GET MARA.
-> Save -> Activate -> Execute.

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 SAP defined methods instead of Logical Database(LDB)

Hi All,
I gonethrough some documents related to new HR ABAP programing without using logical database. we can replace the logical databased with SAP defined methods for all the infotypes. Appreciate if anyone let me know how do this.
Thanks in advance.
Thanks,
-suresh

Yes.. we can use the Infotype reader class.. you can use the following sample code & go from there.. fyi I wrote this on a 47 system..
*& Report ZP_INF_CL                                                   *
*& read an infotype using ABAP Objects                                *
report zp_inf_cl line-size 1000.
infotypes: 0001,0008.
parameters: p_infty type infty,
            p_pernr type pernr_d.
constants: c_a type tclas value 'A',
           c_true value 'X'.
data: w_infotype_reader type ref to if_hrpa_read_infotype,
      t_inftab type hrpad_prelp_tab,
      w_missing_auth type boole_d,
      w_data_exists type boole_d,
      rec_infty like line of t_inftab.
* init infotype reader
call method cl_hrpa_read_infotype=>get_instance
importing
    infotype_reader = w_infotype_reader.
call method w_infotype_reader->read
exporting
    tclas         = c_a
    pernr         = p_pernr
    infty         = p_infty
    begda         = sy-datum
    endda         = sy-datum
    no_auth_check = c_true
importing
    infotype_tab = t_inftab
    data_exists   = w_data_exists
    missing_auth = w_missing_auth.
loop at t_inftab into rec_infty.
call method cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
    exporting
      prelp = rec_infty
    importing
      pnnnn = p0001.
append p0001.
endloop.
loop at p0001.
write:/ p0001-orgeh.
endloop.
~Suresh

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 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 PNPCE and inherited Sub Area

Hi,
I have asked this in the HR forum but no response......
I have a report using Logical Database PNPCE to find some values from a couple of info types. When I select a unit (from the 'OrgStructure' button at the top of the screen), say 111, and all its sub-units with no selections in the selection screen, I get one person displayed. This is correct and this person is in a sub-unit 3 levels down (unit 333).
I then added a selection to only display people in units with Personnel SubArea 'OTEC'. Now I get no results output. When I look in PPOME, I can see that unit 333 has Personnel SubArea 'OTEC' but it is inherited from '111'.
In PP01, unit 111 has an Account Assignment entry (Info Type 1008) but 333 does not.
Does anyone know how to report on this?
Is there a flag somewhere that tells the LDB to check for inherited units?
If not, any ideas if there is a function out there to find the superior unit for these sub-units?
Thanks.

Thanks,
I am aware of that FM but how do I find the parent unit in a clever fashion?
The structure could have multiple levels e.g.
Unit 1 - Unit 2a - Unit3a......
- Unit 2b
- Unit 2c
Unit 1 is the parent and all the below units inherit from it.
The LDB is looping through an internal table with a list of the units. It finds Unit 1 but not the rest.
So, when the LDB is looking for Unit 3a, how does it know that Unit 1 is the parent?
If I use that FM, I think I would have to look for all units above it and see if there is an Info Type 1008 exists. Seems like a lot of processing for something that should be simple?
Kroc.

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.

Infoset query logical database and transparent table

Hi!
We have an infoset with the data source logical database=PNP.
We get some fields from the infotype 0768, P0768-PERNR, P0768-BEGDA, etc.
Now we need add another table to make a join within infotype 0768 and table T5F99SE.
For instance, in infotype 0768 I have one record with the fields PERNR and BEGDA and in the T5F99SE I have 3 records related to the unique record of infotype 0768, the fields of the table are PERNR, BEGDA, ACTDT and ADDAT .
The fields values in the example can be:
Infotype 0768: PERNR=00101800, BEGDA=20110401, DICOT=20, BACHE=1200
Table T5F99SE: record 1 PERNR=00101800, BEGDA=20110401, ACTDT=20110401, ADDAT=PB    E
                         record 2 PERNR=00101800, BEGDA=20110101, ACTDT=20110405, ADDAT=PC    E01
                         record 3 PERNR=00101800, BEGDA=20110401, ACTDT=20110409, ADDAT=PA    E
The result we want get with infoset query is
PERNR    BEGDA   DICOT BACHE   ADDAT
00101800 20110101 20        1200       PB    E
00101800 20110101 20        1200       PC    E01
00101800 20110101 20        1200       PA    E
I would like to get the fields of the infotype and some fields of the table T5F99SE.
Is possible do this action with ABAP modifying an infoset that already exists adding the fields of the transparent table?
What should I do?
Kind regards,
Julian.

My guess is that it would not be possible to include a transparent table into the LDBs PNP and PNPCE. Would need input from a technical expert there.
However, instead of using the LDB, why don't you explore just using a direct table join? You may need to join PA0000, PA0001, PA0002 along with PA0768 and your other tables. An infoset can then be created on this table join.
To go to the mode where you can create the table join, in your infoset transactions, choose 'Table join' instead of 'LDB'.

Logical Database for MD04

I have been using Logical Database DBM to get the MRP Lists for materials (MD05). Is there a similar Logical database for the MD04 counterpart?
Problem with MRP lists, the data is static until I run MRP, with MD04, I see the realtime result every time.

Fernando,
You are very fortunate to be able to use DBM. The last system I worked on in which MDTB table was being populated was a 3.1H R/3 system in 2002, MDTB table is by default not populated in recent SAP releases, although as you have seen, this behavior can be changed through configuration, at the expense of MRP performance, .
I am not aware of any single LDB that contains all the elements of MD04. As you mention, most of the data in MD04 is extracted or calculated dynamically at run time, and is not stored in any tables in the same way that MRP stores data in MDKP and MDTB. If you need to see 'current' information, then just use MD04, or create a custom report.
Best Regards,
DB49

Customize selection screen of logical database AFI of report RIAUFK20 ?

Hi Experts,
I have to customize the report RIAUFK20 which use logical database AFI.
I have to do the following:
- Change the field labels of some fields in the selection screen.
- Add more field into selection screen which does not appear in the nodes of logical database structure, for example TIDNR in table EQUZ.
So what is the best way to achieve that result?
I intended to copy the AFI into ZAFI and change, but still struggle with add fields which does not appear in the structure of logical database.
Any help is appreciated, thanks!

Specify your logical database on Program "attributes".
It will display the standard selection screen of LDB. Now in your report, create selection screen as in other programs for the additional fields.
It will first display the field of LDB, followed by fields provided by your selection screen.

LDB (Logical Database) results

Similar Messages

Maybe you are looking for