Skip to Content
avatar image
Former Member

Unable to see HANA database tables created through HANA Studio in ECC HANA System (ie; SE11).....

Hi all,

I'am new to SAP HANA...

I am facing an issue in table display. I have created a Table in HANA database through HANA Studio (in a particular schema), but i am unable to find the same table in ECC of my HANA system (SE11)..

And also , we all know that there is a “History Column Table” concept in HANA database where we can log the changes of a table(update,delete records), do we have the same functionality while creating a table in ECC HANA (ie; through SE11)?

Could you please help me out..

Many thanks,

Naveena.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • May 08, 2017 at 01:08 PM

    Hi.

    No . Dictionary connection is not an auto-feature in HANA. So if you'll create a table from HANA Studio, with a direct SQL, you'll surely not see in dictionary from SE11 but you'll be able to access it from an abap report or something like that.

    You can see your default scheme in ECC from DBACOCKPIT transaction->System Landscape->System Configuration Entries

    HANA is DB oriented so you'll have to manage data like you would live in a "console" world.

    update,delete records in ECC is managed in SCU3 transaction.

    You'll have to set the Log Data Changes flag in technical settings from se11 table definition.

    Hope to help

    Bye

    Add comment
    10|10000 characters needed characters exceeded

    • Hi.

      If you launch se14 and put your table you'll see is not active in dictionary but it's alive in DB.

      If you want to have access to your Table from ABAP report you'll need to use Open SQL or almost a View created in Hana Studio with reference to your table. An OPEN SQL will need your schema detail information.

      For your confirmation try out DBACOCKPIT transaction and put your Select instruction into Diagnostic->SQL Editor. You'll get your results

      It's stupid example (you know time) but here you are (partially copied from https://wiki.scn.sap.com/wiki/display/Snippets/ADBC+-+ABAP+Database+Connectivity ):.

      TYPES:
      " Definition of result structure
      BEGIN OF ty_result,
      id TYPE c,
        name(20) TYPE c,
      END OF ty_result.
      
      
      DATA:
            lv_statement TYPE string,
            lt_result TYPE TABLE OF ty_result,
      lr_result TYPE REF TO DATA,
            lo_conn TYPE REF TO cl_sql_connection,
            lo_statement TYPE REF TO cl_sql_statement,
            lo_result_set TYPE REF TO cl_sql_result_set,
            lx_sql TYPE REF TO cx_sql_exception.
      
      
      " Get data reference
      GET REFERENCE OF lt_result INTO lr_result.
      
      
      " Native SQL-Statement
      *lv_statement = | SELECT carrid, connid, fldate, |
      *&& | days_between(fldate, current_utcdate) AS days |
      *&& | FROM sflight WHERE mandt = '{ sy-mandt }' AND |
      *&& | days_between(fldate, current_utcdate) < 10 |.
      
      
       lv_statement = | SELECT id, name |
       && | FROM ZTESTH_TAB |.
      
      
      
      
      TRY.
      " Prepare SQL-Connection and SQL-Statement
      lo_conn = cl_sql_connection=>get_connection( ).
      lo_statement = lo_conn->create_statement( ).
      lo_result_set = lo_statement->execute_query( lv_statement ).
      lo_result_set->set_param_table( lr_result ).
      
      
      " Get result
      lo_result_set->next_package( ).
      lo_result_set->close( ).
      
      
      LOOP AT lt_result ASSIGNING FIELD-SYMBOL(<ls_result>).
        WRITE: / <ls_result>-id , <ls_result>-name.
      ENDLOOP.
      
      
      CATCH cx_sql_exception INTO lx_sql.
      " Error handling
        WRITE: lx_sql->get_text( ).
      ENDTRY.
      <br>

      Hope to help

      Bye

  • May 10, 2017 at 05:51 AM

    If you had a DDL source then we can see it on ABAP dictionary.

    But pure HANA DB tables can not be seen in SE11 . But we know they exist on the database. You can query them using an ABAP query

    Add comment
    10|10000 characters needed characters exceeded