Changes to View in logical database(SE36) is not saved in transport.!!

Hi ,
Logical Database: ADA
Selection view: CUS
We did few changes to the view for table fields ANLAV in SE36 .
When I press save, it is not asking for transport number.
How i can save these entries in transport?  Do I need to manually place in the transport?
Kindly Suggest.
Thanks

Hi,
Please check below sdn link..
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0e0039a-0d79-2c10-0aaf-9f6c062c0ffb?quicklink=index&overridelayout=true
BR,
Vijay

Similar Messages

  • Change output of abap logical database report

    Hello
    I have an abap report that is using a logical database to display some fields.My problem is that i have to change it and display more fields for output ,how can i control this?
    Thank you

    Hi,
    We need to add the required (additional) fields to the internal table structure, fill the fields with relevant data and display them on the screen. How is the output fields related to using a LDB..?
    Can you explain me a little bit more on the below stmt?
    " I have an abap report that is using a logical database to display some fields."
    I am not clear in understanding the relation b/w 'using LDB' and 'fields in output'. I dont think the fields displayed in the output screen will be restricted while using a LDB. Pls correct me if i understood wrong.
    Thanks,
    teja.

  • Changing selection sequence for logical database

    Hi,
    One of my current report is using logical database PNP. The users are satisfy with the standard selection screen. However they would like me to change the sequence of the selection field. Example, current sequence is Personnel number, company code, employee subarea. They would like it be Personnel number, employee subarea, company code.
    Is there any way I can change the sequence of the selection screen? I tried using report catagory but it don't allow me to change the sequence. Please advise.
    Regards,
    Lanwu

    Rich is correct.. but there is a workaround..
    Use the Report Category that suppresses all the selection fields.. I the program deifne your selection screen with the fields in your own order preference. In the STARt-OF-SELECTION event.. pass the values entered to the PNP fileds.. ie suppoes you have declared S_PERNR ( for Pers No), then use PNPPERNR[] = s_pernr[]. This way you will not have to change the LDB program..
    ~Suresh

  • Is it possible to change selection screen of logical database structure?

    I have to create a z report for a standard transaction FBL01N which is extracting data according to the vendor account number(LIFNR) at the selection screen. Now as per the requirement the system should extract details according to 'vendor name' keeping the same functionality.
    But the standard program is using some logical database structure KDB and the include for the selection screen is DBKDFSEL.So can I modify the selection screen of this transaction replacing Vendor No with Vendor Name.

    Hi..
    Refer this links
    http://help.sap.com/saphelp_46c/helpdata/en/9f/db9b8535c111d1829f0000e829fbfe/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/9f/db9b8535c111d1829f0000e829fbfe/content.htm
    Hope this may b very helpful to u
    Sravani
    Plz reward points

  • Logical databases (sorry for not introducing myself)

    New on this forum. Logical databases have any use?
    What is a subprogram?
    Moderator message: please search for available information/documentation.
    [Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
    [Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers]
    Edited by: Thomas Zloch on Aug 2, 2011 11:13 PM

    hi logiacl databases are mostly used in the hrabap.
    Logical databases are programs that read data from database tables and pass it to other programs for processing. The order of reading the database tables is determined by a hierarchy.
    Many tables in the R/3 System are linked using foreign key relationships. Parts of these relationships form tree-like hierarchical structures. Logical databases allow you to read data easily from database tables that form parts of these structures
    Retrieving Data Using a Logical Database:
    GET EVENT
    This is the most important event for executable programs that use a logical database. It occurs when the logical database has read a line from the node <table> and made it available to the program in the work area declared using the statement NODES <table>.
    When you define the corresponding event block in the program, you can specify a field list if the logical database supports field selection for this node:
    GET <table> http://FIELDS <f1> <f 2>....
    Transation is se36
    check this simple example..
    REPORT  Z_LDB_DEMO.
    NODES: SPFLI, SFLIGHT, SBOOK.
    START-OF-SELECTION.
      WRITE 'Test Program for GET'.
    GET SPFLI.
      SKIP.
      WRITE: / 'From:', SPFLI-CITYFROM,
               'TO  :', SPFLI-CITYTO.
    GET SFLIGHT.
      SKIP.
      WRITE: / 'Carrid:', SFLIGHT-CARRID,
               'Connid:', SFLIGHT-CONNID.
      ULINE.
    GET SBOOK.
      WRITE: / 'Fldate:',    SFLIGHT-FLDATE,
               'Bookid:',    SBOOK-BOOKID,
               'Luggweight', SBOOK-LUGGWEIGHT.
      ULINE.
      END-OF-SELECTION.

  • 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.

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

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

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

  • P.O change if i change only screen exit field the data is not saving

    Hi ,
    In the purchase order header custom tab i am added a screen exit field .In the purchase order creation mode the screen exit field is saving.But in the change mode if i am changing only the screen exit field then it is showing as 'no data to save' and not saving .But at the same time if i am changing some standard field with the screen exit field then both the field is saving.
    I have to activate any field to save the screen exit field.Please let me know any exit to be activated for saving the data.
    With Regards,
    Ambrose

    Hi
    Pls keep a break-point in the PAI of Screen exit and check, whether it stops in change mode
    Regards
    Madhan D

  • 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

  • Steps to create LOGICAL DATABASE in sap

    hi guys,
    i have gone through many documents about LDB. But, i didnt get the steps to create a LDB.
    plz provide me with the steps to be followed to create a LDB.
    thnx,
    shivaa.

    Hi Shiva,
    This might help you!
    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 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.
    Reward if useful.
    Thankyou,
    Regards.

  • 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

  • Transport logical database

    Hello,
    I have added a new field for de logical database 'DDF'.
    I can´t transport this change.
    I have transported the structure but not the selection view. So, I don`t have the new field transported.
    Is it possible to transport new fields?
    Thanks in advance.

    Welcome to SCN.
    It is not at all advisable to change/modify the standard logical databases as it may be used in several standard programs.
    Instead use them in your report as it is and add the required functionality in the report itself.
    Still, if its require to change it then follow this SAP Link -
    http://help.sap.com/saphelp_erp2005/helpdata/en/9f/db9bed35c111d1829f0000e829fbfe/frameset.htm
    Edited by: Amit Khare on Dec 15, 2008 11:18 PM

  • Can i limit the selection in Logical database ?

    hello  ,
    how can i limit the number of records in Logical
                                  database ( my "yyf"  , not standart )   ?
    i get dump on memory  , when i press F4 , becouse i have to many records ,
    so how can i limit the amount of records .
    in se36 ?
    in my program  ( se38 ) ?
    dump description
    &INCLUDE INCL_INSTALLATION_ERROR
    The current program had to be terminated because of an
    error when installing the R/3 System.
    The program had already requested 386785568 bytes from the operating
    system with 'malloc' when the operating system reported after a
    further memory request that there was no more memory space
    available.

    Hi ,
    Hope this helps you .
      SELECT roll name
      FROM tab
      INTO TABLE it_tab.
      CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
        EXPORTING
          retfield        = 'ROLL'
          dynpprog        = sy-repid
          dynpnr          = sy-dynnr
          dynprofield     = 'P_ROLL'
          value_org       = 'S'
        TABLES
          value_tab       = it_tab
        EXCEPTIONS
          parameter_error = 1
          no_values_found = 2
          OTHERS          = 3.

  • 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.

  • Logical Database selection screen pushbutton

    Hello All,
    I need to create a pushbutton on a selection screen of a logical database.  Basically this pushbutton when clicked will either display or suppress some fields on the screen.  I have tried to use the SSCRFIELDS option to create a pushbutton, however that never displays for me.  Logical Database DDF has an example of a pushbutton that I am looking to create, however the functionality will be different.  I am not sure what I am missing, can anyone help?  Thanks.
    John

    Hello All,
    Thanks for your replies. However, there is something that is causing these options not to work.  For some reason when using SSCRFIELDS nothing displays.  For the SELECTION-SCREEN PUSHBUTTON command, we see the push button however our code for some reason is not working.  I have another developer working this with me and we are both stumped.  We are mirroring that DDF Logical Database and are not having any luck so far.  Does anyone have any further suggestions?
    John

Maybe you are looking for