[SIMGH] Reference a Database view

Hi,
I am using transaction SIMGH for creating a new customer node.
I would like to reference a <b>database view</b> in it. I know how to reference maintenance view but the problem with DB view is that they do not have a SOBJ record.
Is there a possibility to :
1) Reference DB views directly in SIMGH ?
2) Encapsulate the database views into a transaction that I will, then, reference into SIMGH ?
Thanks in advance.
Best regards,
Guillaume

Hi,
Check this link, i think i would be
useful for you.
http://searchsap.techtarget.com/search/1,293876,sid21,00.html?query=howtoreferenceadatabaseviewdirectlyintoannewlycreatedcustomer+node&bucket=ALL
Reward if it useful to you.
Thanks.

Similar Messages

  • Reference to database and/or server name in '' is not supported in this version of SQL Server

    Hello all
    I am using C# and ADO.NET (native) - Visual Studio 2013.
    I am always using full qualified queries like "SELECT * FROM [database].[schema].[table]"
    Obviously there is a problem when doing this against SQL Azure,
    I get the following error: "Reference to database and/or server name in '' is not supported in this version of SQL Server"
    Interesting fact: With SQL Management Studio, the same query works.
    I need to know if this error is really a true one or not.
    If yes, I can quit using SQL Azure. I would need a SQL Server and not a partial SQL Server :-)
    Thanks and best regards
    Frank

    Hi,
    Here are my suggestions:
    1. Use partially qualified queries, because:
    a. from a security standpoint, you'd want to limit your login's access across the server instance
    b. in order to achieve a even better, you should specify your database as the Initial Catalog directly in the SQL Connection.
    If you take into account these practices, SQL Database doesn't come with any limitation from that point of view.
    However, in regard to 'With SQL Management Studio, the same query works', this is actually only partially true because if you run that query agains ADO.NET, you'll actually end up in switching databases along the query which is obviously not permitted in
    SQL Database since you're running in a hosted black-box version of SQL you're not managing. It's just like running the USE <dbname> command which obviously doesn't work.
    Alex

  • Snowflake dimension: named query vs. database view

    A test question features a Product table with a Product Size code; Product Size description is taken from ProductSize table. As far as I can tell, the question asks me to choose between (a) setting up a database view joining Product and ProductSize, and
    (b) doing the join in a data-source-view named query. I don't see a clear winner. (My thinking is as follows.  Yes, he view would speed up the processing, even if not materialized. On the other hand, with a small dataset, the performance gain would be
    minor in absolute terms. Do I want to have an extra database object in the picture?) Yet the question's author does. Can anyone advise please?  

    Hi Demyan,
    According to your description, you want to know which is better, using named query in datasource view or using database view, right?
    Based on my research, there is no performance differences between using named query in datasource view and using database view because they both result in SQL query being sent to the source system. Here is a blog which discuss this issue.
    Consistency: If you already have logic in database views, I would continue to use them. As long as you know that you go to one spot to view/change the logic. Putting the logic in 2 different spots could lead to confusion.
    Security Permissions: often you may not have permission to alter the source databases, in this case you have no choice but to setup named queries in the dsv.
    Reference
    http://geekswithblogs.net/darrengosbell/archive/2006/09/05/90278.aspx
    http://bennyaustin.wordpress.com/2013/07/16/dbview/
    Regards,
    Charlie Liao
    TechNet Community Support

  • Z Database view is not showing all the entries?

    Hello
    Last year I have created a Z table, say, its name is Z_TABL_1, its working fine, say, there is around 1000 entries in PRD, well
    Last week I have created another 2nd Z table, its name is Z_TABLE_2, now it has 50 entries in PRD
    In both tables the key field os the same (VISITOR_NUMBER) and there is only one key field in both tables, its the same
    When creating the 2nd table I forgot to specify the CHECK table relationship in 2nd table refering 1st table, I mean, dependent table is 2nd whereas reference is 1st table
    Now, I created a database view, say, my_db_view on these 2 tables.
    When I opened this my_db_view in SE16, I expected 1000 (this 1st table count) entries, but am seeing just 50 (the 2nd table has only 50 entries) entries!!
    Pls. let me know how can I view all the 1000 entries in SE16 for my_db_view?
    Thank you

    Hi,
    in your DB view tables are joined and database views implement an inner join (you can check here: http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21ecab446011d189700000e8322d00/content.htm), that's why the system extracts only 50 records.
    It's not possible to have all the 1000 records using a database view.
    Marco

  • How to create a database view

    dear all,
    how to create database view with example.

    Hi,
    1. Go to se11
    2. click the view radio button and give the new object name
    3. Then you will be prompted to select one among 4 more views
    4. Select database view then enter.
    5.Give short description
    6. Click the Table/Join conditions tab then give the table names which are going to be joined.
    note: we can have only  inner join with the database view.
    7. Give the table names as mara,marc,makt under tables
    8. Then in the adjacent area that is in Join conditions just give
        mara-matnr = marc-matnr
        marc-matnr = makt-matnr
    9. Then click the tab View flds, give the field names whichever you want to fetch from the tables as just like the ineer join in the select query as like follows.
    matnr -> mara -> matnr
    werks -> marc -> werks
    maktx -> makt -> maktx
    10. Then save and activate.
    For further  reference use the link,
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm
    Regards,
    Sankar.

  • JDeveloper 3.0 and Database-Views

    I have started to test JDeveloper and have the first problem.
    I make extensive use of database-saved views and started with the Package Wizard to create default business-objects (view objects and view links).
    But when I select a database-view I get a save error: Entity creation failed no primary key attributes and does not support ROWID. oracle.jbo.dt.objects.Jbo.Exception
    The connection was established with jdbc.oracle.thin, the database is NT-Version 7.3.4, JDeveloper is Version 3.0 (Build 532).
    What have I done wrong or is it not possible to connect to views ???
    I hope for your help.
    Henry
    null

    Dan,
    JDeveloper 3.0 provides an 'Add-In API' and 'Custom Addins' for
    integration with third-party vendors. These were also in place
    for 2.0.
    If you go to the JDeveloper page, there are HTML documents
    available under the 2.0 Technical Information section, and also
    an online walkthrough available if you follow the 'Online Demo'
    link.
    Laura
    Dan Schroeder (guest) wrote:
    : Will JDeveloper 3.0 support source control integration? I am
    : currently MKS Source Integerty 7.5. I haven't seen any
    : references about source control within JDeveloper 3.0.482, but
    : someone told me that it may be available as an add on.
    null

  • Objects missing in database (views)

    As information/background, I have been away from SAP and basis for about four years.  Due to personnel changes here, I am now returning to it. While I was away, our SAP system was upgraded from version 4.0B to “SAP R/3 ENTERPRISE 47X110”.  I was not a part of the upgrade and have no details as to how it was accomplished.
    At this point, we have two SAP “systems”: DEV and PRD and they are on separate partitions of an i5 520.  Both are running on OS/i5 V5R3M5 with mostly updated CUMe packages, etc, and PASE is installed.  Both of these “systems” use the 6.20 kernel at patch level 1598.  We know that this is an OLD kernel and we need to upgrade.  I am currently planning the kernel upgrade to 6.40.
    In our PRD instance, using transaction DB02 I have been seeing that we are  missing  four views in the database:
      Views
        SYSTRIGCOL    Obligatory Base object is missing in DB
        SYSTRIGDEP    Obligatory Base object is missing in DB
        SYSTRIGGERS   Obligatory Base object is missing in DB
        SYSTRIGUPD    Obligatory Base object is missing in DB
    Is this a big deal?  Should I worry about it or just continue with my kernel-upgrade planning?
    If needed, can I just retrieve the source from the DEV instance, modify the source, and create the views in PRD? 
    I have confirmed that I can retrieve the DDL source from DEV via iSeries Navigator.  It would then just be a matter of copying it, modifying it for PRD, and then executing it for PRD.
    Thanks in advance for any advice.
    Robert

    Hi Robert,
    no this isn't critical during daily business, at least not in base release 6.20.
    You are missing a couple of system catalog views providing SQL trigger information on a schema basis. (They are views on top of the systemwide cross reference files.)
    I've seen this happening if you restore a library from an old OS/400 release (that did not know about those views) to a newer release.
    SAP does not use triggers in 6.20 during daily business that's why it is not critical.
    It's easy to fix though: You may consider removing all system catalog logical files from your R3<sid>DATA schema (WRKOBJ, 4) according to the following list:
    http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/db2/rbafzmstcatalogtbls.htm#catalogtbls .
    The following command will recreate them:
         CALL QSYS2/QSQXRLF PARM(CRT R3<sid>DATA)
    Hope that helps!
    Best regards,
    Dorothea

  • Error in ADF-BC Database view instead of insert trigger

    I received the following errors when trying to insert. Any help or hint will be greatly appreciated.
    JBO-26041: Failed to post data to database during "Insert": SQL Statement "BEGIN INSERT INTO DEV_EQMT_HISTORY_BY_CODE(ID,D_E_ID,STATUS_KEY) VALUES (?,?,?) RETURNING ID, ROWID INTO ?, ?; END;".
    ORA-22816: unsupported feature with RETURNING clause ORA-06512: at line 1
    The followings are the tables and view I used:
    create table device_eqmt (
    id number(6),
    code varchar2(40)
    alter table device_eqmt
    add (constraint device_eqmt_pk primary key (id));
    create table device_eqmt_history (
    id number,
    d_e_id number(6),
    status_key number(6),
    alter table device_eqmt_history
    add (constraint device_eqmt_history_pk primary key (id));
    alter table device_eqmt_history
    add ( constraint device_eqmt_hist_de_id_fk
    foreign key (d_e_id)
    references device_eqmt(id)
    CREATE TRIGGER dev_eqmt_hist_bi
         BEFORE INSERT ON device_eqmt_history
    FOR EACH ROW
    BEGIN
    SELECT SHARED_SEQ.nextval
    INTO :new.ID
    FROM dual;
    END;
    create view dev_eqmt_history_by_code
    as select h.id,
    h.d_e_id,
    de.code,
    h.status_key
    from device_eqmt_history h, device_eqmt de
    where h.d_e_id = de.id
    CREATE OR REPLACE TRIGGER dev_eqmt_hist_by_code_insert
    INSTEAD OF INSERT ON dev_eqmt_history_by_code
    REFERENCING NEW AS n
    FOR EACH ROW
    DECLARE
    deid number;
    BEGIN
         SELECT de.id INTO deid FROM device_eqmt de WHERE de.code = :n.code;
         INSERT INTO device_eqmt_history (id, d_e_id, status_key)
         VALUES (:n.id, deid, :n.status_key);
    END;

    The Oracle database doesn't support the returning clause for database views using instead-of triggers. ADF BC inherently includes the returning clause, if in a relating EO you have the refresh-after-insert or refresh-after-update property set on for an attribute.
    Hope this helps.
    CM.

  • Queston about database view creation

    I would like to ask whether I can view including 2 tables with left outer join relationship?
    i.e. a outer join b on ....
    thanks!

    You can use only projection view or database view in your ABAP program.
    <b>Projection view</b>
    Just retrieves some fields from only one table.
    <b>Help view</b>
    This is used for search help.
    <b>Database view</b>
    This is inner join view.
    Views in the ABAP Dictionary are implemented as inner joins. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
    See http://help.sap.com/saphelp_nw04/helpdata/en/aa/47349a0f1c11d295380000e8353423/content.htm for more reference.
    Ps: Reward points if helpful.

  • Database View do not refresh in ADF application

    Greetings,
    im facing a weird problem in my application (JDeveloper 11.1.2.4.0 - ADF). All this time i was working directly with tables (VO), but now i also started using database views.
    Everything works fine, when i add a new row in a table that my Database Views is associated with, it refresh properly.
    BUT if i delete rows manually from my database, the View do not refresh in my application, not by refreshing the page,
    redeploying application, even executing the view object query inside the view object. The only way for the DB View to be
    refresh inside the JDeveloper and on deployment time is by restart JDeveloper. I try adding an action on my OV to re-execute them when
    i do something specifically, hopefully the will reset the cache and retrieve the DB view again, but with no luck..
    Correction: now it doesnt even refresh on restart jdeveloper.
    Just for the clarification, im talking about Database Views, and not just Object Views. I create a Object View inside the application to retrieve the data
    from the Database View results.
    Can you help me on this please?

    Yes the queries in SQLDeveloper was showing me correct results.
    But i feel disappointed.. When i went to close SQLDeveloper to try something, it pop me a message to commit/rollback changes.
    After i commit them, my app show correct results too.

  • Set operator NE in Database View creation in  join condition

    Hi Experts,
         I have a requirement to set NE(not equal) operator in join condition of Database View creation. Could you please help me how to set in operator.
    Join condition :
    Ex : BSAK-AUGBL NE BSAK-BELNR.
    You know that by default operator is '='. i want to set NE in place of '='.
    Thanks,

    Hi Chinna,
    Check whether if there is any possibility or not to include more key fields like bukrs, lifnr, gjahr etc in the where condition, so that you query may result faster. Then, there won't be any necessary to create the view.
    Hope this helps.
    Please reward if useful.
    Thanks,
    Srinivasa

  • How to call database view in report

    Hi i have a small problem in report
    the problem is like this i had created a database view in which i got all the values displayed but can any one of you tell me how to declare this database view in report with example
    i had created a database view named as znew1
    and the fields are
                 LIFNR  LIKE EKKO-LIFNR,
                 EBELN  LIKE EKKO-EBELN,
                 LIFNR1 LIKE LFA1-LIFNR,
                 NAME1  LIKE LFA1-NAME1,
                 EKBE   LIKE EKBE-EBELN,
                 VGABE  LIKE EKBE-VGABE,
                 MATNR  LIKE EKPO-MATNR,
                 WERKS  LIKE EKPO-WERKS,
                 NETWR  LIKE EKPO-NETWR,
                 MENGE  LIKE EKPO-MENGE,
                 MWSKZ  LIKE EKPO-MWSKZ,
                 TXZ01  LIKE EKPO-TXZ01,
                 KOSTL  LIKE EKKN-KOSTL,
            PS_PSP_PNR  LIKE EKKN-PS_PSP_PNR,
                 EBELN1 LIKE EKKN-EBELN,

    Hi Mr. Rich
    This is the program code and i want this output int he alv grid format
    TABLES:EKKO,EKBE,EKPO.
    DATA:BEGIN OF RTAB_ALV OCCURS 30,
                 LIFNR  LIKE EKKO-LIFNR,
                 EBELN  LIKE EKKO-EBELN,
                 LIFNR1 LIKE LFA1-LIFNR,
                 NAME1  LIKE LFA1-NAME1,
                 EKBE   LIKE EKBE-EBELN,
                 VGABE  LIKE EKBE-VGABE,
                 MATNR  LIKE EKPO-MATNR,
                 WERKS  LIKE EKPO-WERKS,
                 NETWR  LIKE EKPO-NETWR,
                 MENGE  LIKE EKPO-MENGE,
                 MWSKZ  LIKE EKPO-MWSKZ,
                 TXZ01  LIKE EKPO-TXZ01,
                 KOSTL  LIKE EKKN-KOSTL,
            PS_PSP_PNR  LIKE EKKN-PS_PSP_PNR,
                 EBELN1 LIKE EKKN-EBELN,
         END OF RTAB_ALV.
    DATA:IZNEW1 TYPE TABLE OF ZNEW1 WITH HEADER LINE.
    select * into table IZNEW1 FROM ZNEW1 UP TO 10000 ROWS.

  • Using database views in ADF mobile client application

    Hi,
    I am using Jdeveloper 11.1.1.4 and WLS 10.3.4.
    I have developed a POC in ADF mobile client application both with and without synchronization. However, both work with entity objects based on tables.
    I need to use database views instead of tables. When I try to include entity object (based on views) in the view object, it shows an error saying "Only the entity objects based on tables can be selected"
    Please guide me if there is a work around for this.
    Also, please let me know if there is way to develop an ADF mobile client application skipping the use of entity objects at all and using view objects directly to specify the database query and fetch data from the database.
    Thanks in advance.
    Ansh
    Edited by: ansh on Mar 28, 2011 5:40 AM

    Hi, Ansh:
    Currently, out of box, ADF Mobile Client does not support synchronization against Database Views. This is because Mobile Server imposes some schema restrictions to ensure synchronization with multi-table views would work correctly. This schema restriction requires, for example, the view must have a primary parent table with key defined, and also all base table must be included in the data publication. These dependencies requires manual resolution and advanced planning, and is managed outside of the ADF Mobile Client/JDeveloper project.
    To continue development, you would need to create server Entity Objects directly against the base tables. You can then create the mobile ADF Business Component (EOs, VOs, etc). You can then create View Objects in your ADF Mobile Client application based on the database views, in order to retrieve the data you need exactly. In other words, instead of basing EO on the database view, create View Objects in the mobile applicaiton to mimic what you had in the View Object.
    Is there any other reason why you would need to access data via database views, instead of directly against base tables?
    Thanks,
    Joe Huang

  • How to delete a record in Database View?

    HI All,
    I have created a Database  View using tables LIKP,LIPS,VBUK,VBUP.
    In that view I am getting a extra record which is not exit in any tables
    but its getting in database view.
    I tried buffer memory refresh and even tried SE16n , SE11(thro CODE(DELE))..But record has not been
    deleted.
    Plz suggest wat shud i have to do to delete the record.
    Thanks in advance and help realy appriciate.
    Regards
    Steve

    >
    Steve Johnson wrote:
    > In that view I am getting a extra record which is not exit in any tables
    > but its getting in database view.
    Your intention should be in search of the root of that extra record. Not the deleting it without knowing anything.
    Sure, You have put join conditions correctly?
    Cheers

  • Progammatic update a table with a database view  in the page

    Hi All,
    I am using JDev 11g. With FOD database schema, I have one database view Products which comes from two tables Products_Base and Product_Transactions. I created three EOs (ProductEO, ProductsBaseEO, ProductTransactionsEO) and three VOs (ProductVO, ProductsBaseVO, ProductTransactionsVO) based on their EOs respectively.
    Here is my scenario. I have an ADF form which is based on the database view Products and is dragged and dropped from Data Controls->ProductVO. When an existing record is submitted, a backing bean method will be called to update the data against the table Products_Base (and the table Product_Transactions at the same time) programmatically. An update method updateProductPrice() is added into the Application Module and published it to UI Client. The submit button in the page is created by directly dragging and dropping Data Controls->updateProductPrice into the page. When I run it, I got the following error message,
    Failed to post data to database during "Update": SQL Statement "UPDATE PRODUCTS ProductEO SET COST_PRICE=:1 WHERE PRODUCT_ID=:2".
    What I don't understand here is that, in my update method updateProductPrice(), it supposes to update the table Products_Base. But from the error, it appears that it is trying to update the view Products. Can anyone give me a help on what I did wrong here? When I try to debug it, it throws an exception to this line in the method updateProductPrice(),
    getDBTransaction().commit();
    Here are my codes,
    The method which got called in the backing bean
    public String cb6_action() {
    DCBindingContainer bc = (DCBindingContainer)getBindings();
    FacesCtrlAttrsBinding ProductId = (FacesCtrlAttrsBinding)bc.get("ProductId");
    FacesCtrlAttrsBinding CostPrice = (FacesCtrlAttrsBinding)bc.get("CostPrice");
    JUCtrlActionBinding action =
    (JUCtrlActionBinding)bc.findCtrlBinding("updateProductPrice");
    DCDataControl dc = action.getDataControl();
    ApplicationModule am = (ApplicationModule)dc.getDataProvider();
    AppModule service = (AppModule)am;
    service.updateProductPrice(new Long(ProductId.toString()), CostPrice.toString());
    return null;
    public BindingContainer getBindings() {
    return BindingContext.getCurrent().getCurrentBindingsEntry();
    The update method defined in the Application module (AppModuleImpl.java)
    public void updateProductPrice(long productId, String costPrice) {
    ProductsBaseEOImpl product = retrieveProductById(productId);
    if (product != null) {
    try {
    product.setCostPrice(new Number(costPrice));
    getDBTransaction().commit();
    catch (JboException ex) {
    getDBTransaction().rollback();
    throw ex;
    catch (SQLException ex1) {
    getDBTransaction().rollback();
    private ProductsBaseEOImpl retrieveProductById(long productId) {
    EntityDefImpl productDef = ProductsBaseEOImpl.getDefinitionObject();
    Key productKey = ProductsBaseEOImpl.createPrimaryKey(new DBSequence(productId));
    return (ProductsBaseEOImpl)productDef.findByPrimaryKey(getDBTransaction(),productKey);
    Edited by: john wang on Oct 27, 2009 7:14 AM

    or
    merge into test
    using (select rowid rid
                , id
                , sub_id
                , startdate
                , lead (startdate) over (order by id, sub_id) - 1 ed
           from test) x
    on (x.rid = test.rowid)
    when matched then
       update set end_date = x.ed
    ;

Maybe you are looking for