Logical Database KDF ( FBL1N )

Hi SPecialist
I am trying to add a new field in the logical database KDF. I have several tables here and I would like to add the field USERNAME from BKPF
I suppose that it is possible because I can see the following tables
LFA1           Vendor Master (General Sectio
ADDR1_VAL      Address Data
LFAS           Vendor Master (General Part E
LFBK           Vendor Master (Bank Details)
LFB1           Vendor Master (Company Code)
LFB5           Vendor Master (Dunning Data)
LFC1           Vendor Master (Transaction Fig
LFC3           Vendor Master (Transaction Fig
BSIK           Accounting: Secondary Index fo
ADMI_FILES     Archive Files
BSIKEXT        Secondary Index & Additions Se
BKPF           Accounting Document Header
But when I try to add the field in the functional groups It doesnt appear in the transaction FBL1N.
Any idea??
Thanks

Hi:
Have you tries adding this USERNAME field to FBL1N report using menu...settings...special fields..I think this can be done via special fields addition...Please note that in special fields , fields from BKPF and BSEG can be added. For adding other fields like Vendor name e.t.c you will have to make use of BTE 1650 in FIBF...Please take help for ABABPER. Hope it helps.
Regards

Similar Messages

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.

Logical Database KDF

Hello,
i want to select all open items of the vendor accounts.
I have tried this with the logical database KDF and the selection screen 900 for open items.
Now i have the problem, that i also want the customer items of the vendor account.
Can i get this items, too, with the logical database KDF or have i to select this separately?
Thanks.
Nicole

Nicole.
You can select customer / vendor open items directly from tables.
BSID : Customer Open Items
BSIK : Vendor Open Items
Regards,
Mahesh

Call Logical database KDF

Hi expert.
now that, I'm using Logical database KDF for report module AP, but i meet issue following.
first way i used SE38 and choose radio Attribute and Input LDB is KDF.
In program I get only NODE BSIK but structure BSEGA Not is initial( I don't get BSEG anywhere)
second way. I used FM LDB_PROCESS to call LDB KDF.
I also get NODE BSIK then BSEGA Is initial.
Please anybody to me first way structure BSEGA have data, second way it haven't data.
Thank & best regards,
Dungnv

don't use fm but include KDF as in standard report RFKOPO00
hope that helps
Andreas

Duplicated entries in BSIK using Logical Database KDF

Hello everyone,
I'm using Logical Database KDF to retrieve some data, but i'm getting duplicated entries when getting to BSIK. Can anyone point out in my program what could i be doing wrong?
If i put a breakpoint in the line immediatly below GET bsik, i can watch several entries being duplicated.
                                     Thanks in advance to everyone,
                                                   Nuno
START-OF-SELECTION.
GET lfa1.
MOVE-CORRESPONDING lfa1 TO t_alv.
GET lfb1.
GET bsik.
MOVE-CORRESPONDING bsik TO t_alv.
CLEAR bkpf.
SELECT SINGLE * FROM bkpf CLIENT SPECIFIED
         WHERE mandt = syst-mandt
         AND    bukrs = bsik-bukrs
         AND    belnr = bsik-belnr
         AND    gjahr = bsik-gjahr.
t_alv-xblnr = bkpf-xblnr.
SELECT        * FROM bset CLIENT SPECIFIED
         WHERE mandt = syst-mandt
         AND    bukrs = bsik-bukrs
         AND    belnr = bsik-belnr
         AND    gjahr = bsik-gjahr.
     t_alv-mwskz = bset-mwskz.
      t_alv-hwbas = bset-hwbas.
      t_alv-hwste = bset-hwste.
      t_alv-dmbtr = bset-hwbas + bset-hwste.
      t_alv-stceg = lfa1-stceg.
    APPEND t_alv.
ENDSELECT.

Hello Nuno Centeio ,
                                  According to the table definition there can be more than one entries for a vendor based on the table key definition.
Thanks,
Greetson

Exclude one field from Logical Database's dynamic selection screen

Hi Guru,
I have a requirement to amend a program to exclude the document number field (bsik-belnr) from the dynamic selection-screen of the logical database KDF(Vendor Database) so that the program will not filter according to the document number.
I have use the below syntax in my zprogram.
selection-screen exclude select-options: doc-no.
However I get syntax error "The addition EXCLUDE is only allowed in INCLUDE DBKDFSEL".
Please advice.
Best Regards,
Fung

The selection part of the logical database defines input fields for selecting data.
          The runtime environment displays these on the selection screen when you run an executable program linked to the logical database.
          Include called DB<ldbname>SEL.
        SELECTION-SCREEN BEGIN OF VERSION ver TEXT-xxx.
                                                                SELECTION-SCREEN EXCLUDE ... .
                                                SELECTION-SCREEN END OF VERSION ver.
Defines a selection screen version (with a three-character name ver ). Between BEGIN OF VERSION and END OF VERSION , you can exclude selection screen objects for the version ver , i.e. remove them from the selection screen with SELECTION-SCREEN EXCLUDE.
          SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE dbtab
If one of these tables is active in the report (i.e. it is declared under TABLES or lies somewhere on the path from the root of the database hierarchy to a table declared with TABLES ), a pushbutton called 'Dynamic selections' appears on the selection screen.

Modifying Dynamic selection in standard logical database

Hello guys,
I have a requirement to add a field to a dymamic selection of standard programs.
The standard programs used the logical database KDF.
I have created a custom selection view and included the required field which is from table BKPF.
But this field is not appearing as the table BKPF is not defined as a node in Dynamic selection but in only field selection.
Can anyone please provide me with come help on this?
I need to add the a field from BKPF to the dynamic selection of standard logical DB KDF. Is this possible?
Thanks and regards

Hello Thomas,
thank you very much for the precious help.
I appended the field BKTXT to BSIK and BSAK as used in logical database and these are automatically filled for new postings thanks to Move corresponding (as indicated).
We are left with only to feed these new fields with existing data/records.
kind regards..
Edited by: Devi on May 19, 2009 12:51 PM
Edited by: Devi on May 19, 2009 12:51 PM

How to know logical database supports Dynamic Selections

hi all,
1. Logical database KDF supports Dynamic Selections
2. How to know logical database 'KDF' supports Dynamic Selections

You might find an answer regarding dynamic 'WHERE' statements in standard SAP report SAPDBKDF

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.

Problem in KDF Logical Database !!

Hii Friends,
We need to modify Tcode F.42 and add a field Business Place(BUPLA) on Selection Screen. This is the main requirement.
So i make a copy of this program and KDF logical database.
I am adding a field BUPLA in ZKDF custom logical database. But this Business Place is not working, if i need to debug this logical database, I am unable to debug the logical database.
Please suggest your suggestions..
Nitin Garg

Hi Ramesh,
These are the type of error messages in exetnded syntax check:
The current ABAP command is obsolete
In the OO context either an INTO or an ASSIGNING specification or the addition
"TRANSPORTING NO FIELDS" must be used . be used. be used. be used. be used. be
used.
Internal Message Code: READ 018
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
      Program: Z_INT_I_PY_BONUSPAYMENT Include: Z_PY_F01_BONUSPAYMENT Row:    279
The current ABAP command is obsolete
At "LOOP AT itab" one of the additions "INTO", "ASSIGNING" or "TRANSPORTING NO
FIELDS" is required in the OO context . .
Internal Message Code: LOOP 012
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
      Program: Z_INT_I_PY_BONUSPAYMENT Include: Z_PY_F01_BONUSPAYMENT Row:    282
The current ABAP command is obsolete
In the OO context either an INTO or an ASSIGNING specification or the addition
"TRANSPORTING NO FIELDS" must be used . be used. be used. be used. be used. be
used.
Internal Message Code: READ 018
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
      Program: Z_INT_I_PY_BONUSPAYMENT Include: Z_PY_F01_BONUSPAYMENT Row:    282
The current ABAP command is obsolete
At "LOOP AT itab" one of the additions "INTO", "ASSIGNING" or "TRANSPORTING NO
FIELDS" is required in the OO context . .
Internal Message Code: LOOP 012
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
Please suggest me some way to clear these if it is possible.

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 for vendor cleared items

Hi,
What is the logical database for vendor cleared items. KDF is giving me only open items.
Actually I am preparing a report which uses vendor cleared items and trying to get the list from BSAK table. Which would be the better way (faster process for better performance)
a) directly fetching data from database table like BSAK or
b) by using logical database
any ideas please.
regards,
mallik

If just display of all cleared items in a report, then i would suggest you to go for Query development instead of a z report and use BSAK. Being Index table and query, we can reduce several errors in logic/easy to develop/less time.
If you need Z report only, then also, you can go for BSAK. Where as BASK is secondary index table which helps to fetch data fast.
In one way, BSEG - BSIK = BSAK for your case!
Regards
Sridevi

How to make changes on the selection screen of a logic database?

I want to make one of the select-options of logic database PNP no-interval no-extension, what should I do? Is there any links for manipulating LDB? thx~

Hi,
This blog on SDN will help you on this.
[Re: Change selection screen in LDB (KDF logical database - NOT HR);
Regards
Abhii....

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

Copying logical database from one server to another

Hello All,
I have one logical database name as KDF in my test server which has become inconsistent due to some reason . In my live server tht logical database is consitent now what is the option to copy the same from my live server to test server .
If i copied will it work properly or is there any other solutions or options.
Thanks
Sunny

Hi Suny,
First of all, we cannot create a transport request in Prodcution server and then transport it to the Development Server.Else, it is the other way round,one can create a request in development,then transport it to Test and then to the Production server.
That is why I said that if the SAP standard LDB is disturbed in Development as well,then you will have to manually look in for the modifications between the Production and the Test Server,and change them in the developemt and then transport it to Test server and then Production.
Hence,the best solution is to manually check for the inconsistencies and modify in the development server and then transport.
The path for copying that you are following is correct anyways.
In case you have any further clarifications,do let me know.
Regards,
Puneet Jhari.

Logical Database KDF ( FBL1N )

Similar Messages

Maybe you are looking for