Scribd Logo
Upload

Welcome to Scribd!

  • 217 views

    Error While Activating The Datasource in BW With Hana

    Uploaded by

    Konatham Vinod Reddy
    This discussion describes an issue where certain data sources were not working with DXC (Data Exchange from SAP to SAP HANA) due to missing key fields. The error "Unable to modify DSO table: no key field defined" was occurring. It was determined that while some notes had been applied, additional steps were needed to define semantic keys for the problem data sources using transaction SE38 and report ROSOA_CHANGE_KEY. After making changes to add keys, the data replication worked successfully. Defining keys on the source system was sufficient and should not impact extraction to other BW systems.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Error While Activating The Datasource in BW With Hana

    Uploaded by

    Konatham Vinod Reddy
    217 views4 pages
    This discussion describes an issue where certain data sources were not working with DXC (Data Exchange from SAP to SAP HANA) due to missing key fields. The error "Unable to modify DSO table: no key field defined" was occurring. It was determined that while some notes had been applied, additional steps were needed to define semantic keys for the problem data sources using transaction SE38 and report ROSOA_CHANGE_KEY. After making changes to add keys, the data replication worked successfully. Defining keys on the source system was sufficient and should not impact extraction to other BW systems.

    Original Description:

    ERRORS

    Original Title

    Error While Activating the Datasource in BW With Hana

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This discussion describes an issue where certain data sources were not working with DXC (Data Exchange from SAP to SAP HANA) due to missing key fields. The error "Unable to modify DSO table: no key field defined" was occurring. It was determined that while some notes had been applied, additional steps were needed to define semantic keys for the problem data sources using transaction SE38 and report ROSOA_CHANGE_KEY. After making changes to add keys, the data replication worked successfully. Defining keys on the source system was sufficient and should not impact extraction to other BW systems.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    217 views4 pages

    Error While Activating The Datasource in BW With Hana

    Uploaded by

    Konatham Vinod Reddy
    This discussion describes an issue where certain data sources were not working with DXC (Data Exchange from SAP to SAP HANA) due to missing key fields. The error "Unable to modify DSO table: no key field defined" was occurring. It was determined that while some notes had been applied, additional steps were needed to define semantic keys for the problem data sources using transaction SE38 and report ROSOA_CHANGE_KEY. After making changes to add keys, the data replication worked successfully. Defining keys on the source system was sufficient and should not impact extraction to other BW systems.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 4

    Data Source Key Field error for DXC

    Saurabh Diwakar 199 posts since Mar 1, 2012


    Data Source Key Field error for DXC Dec 3, 2013 11:29 AM
    Hi All,
    While trying to activate the data source 2LIS_11_VAHDR and 0MATERIAL_TEXT in the BW System for DXC
    consumption I get the following error -

    Error in HANA DB system: Unable to modify DSO table


    '2LIS_11_VAHDR': no key field defined (at least one of the
    defined columns must be a key column)
    How can the data source keys be maintained.
    Pl assist. Thanks.

    Shreepad Patil 156 posts since Nov 7, 2012


    Re: Data Source Key Field error for DXC Dec 3, 2013 1:35 PM
    Hi Saurabh,
    These notes need to be applied in the Netweaver server where you're trying to implement DXC. BASIS team
    will be able to help you with these notes.
    1701750 DataSource: Secondary Index on the PSA
    If your DataSource is missing a key, apply this note to any BW systems connected to the SAP
    Business Suite system you are using with DXC.
    1677278 DataSource: Changing the Key Definition (A version)
    Provides a report where you can define a semantic key for any DataSources that are missing
    keys. DataSources without keys will cause an error when you try to generate the In-Memory
    DataStore Object in SAP HANA.
    Before applying this not to your SAP Business Suite system, first apply SAP note 1701750 to
    any BW systems connected to the SAP Business Suite system you are using with DXC.
    1710236 SAP HANA DXC: DataSource Restrictions
    Lists specific DataSources not supported by DXC.

    Generated by Jive on 2016-08-12Z


    1

    Data Source Key Field error for DXC

    Hope it helps.
    -Shreepad

    Saurabh Diwakar 199 posts since Mar 1, 2012


    Re: Data Source Key Field error for DXC Dec 4, 2013 6:21 AM
    Thanks Shreepad.
    Am getting this checked. DXC seemed to be working fine for the data source 0CO_PC_10 (this was done as
    part of COPA RDS installation).
    I can see the key fields in RSA2 for this extractor in ECC. Why does it work for one data source and not others,
    with the same system configuration. Pl advise. Thanks.

    Saurabh Diwakar 199 posts since Mar 1, 2012


    Re: Data Source Key Field error for DXC Dec 4, 2013 8:39 AM
    Hi Shreepad,
    I checked with my Basis team and these notes have already been applied on our systems. Thanks.

    Shreepad Patil 156 posts since Nov 7, 2012


    Re: Data Source Key Field error for DXC Dec 4, 2013 4:25 PM
    Hi Saurabh,
    As the notes are installed from BASIS, you should be able to perform the below steps:
    1. SE38
    2. Execute Report : 'ROSOA_CHANGE_KEY'
    3. Select P_CHNG
    4. In P_DS Enter your extractor name.
    5. Make Changes to the structure by having keys.
    6. Then redo the steps of Activation/Replication of Data Source.
    7. Then try the replication of data again.

    Hope it works this time


    --

    Generated by Jive on 2016-08-12Z


    2

    Data Source Key Field error for DXC

    Shreepad

    Saurabh Diwakar 199 posts since Mar 1, 2012


    Re: Data Source Key Field error for DXC Dec 5, 2013 10:07 AM
    Hi Shreepad,
    This works, thanks. I have some queries on the steps you mentioned above 1. Where do we run the the program ROSOA_CHANGE_KEY, on the source or on the BW System. I did both
    and it works in both cases, but what is the right approach.
    2. If this is done in the source and if the source feeds a HANA System (using DXC) and a BW System (using
    the normal extraction), will this affect the extraction into BW System.
    Pl advise. Thanks.

    Shreepad Patil 156 posts since Nov 7, 2012


    Re: Data Source Key Field error for DXC Dec 5, 2013 3:50 PM
    Hi Saurabh,

    Glad it works!!!
    1> Running the code only on source system should be enough.
    2> Though I have not tried it, but I think it should not affect the extraction to 'another' BW System as this
    program just adds semantic key(s) and does not change the physical structure of the extractor.
    Another point here would be the Embedded BW System in the source system is of no use once DXC is
    configured.
    -Shreepad
    *Kindly mark answers as Helpful/Correct if they solve your queries.

    Shreepad Patil 156 posts since Nov 7, 2012


    Re: Data Source Key Field error for DXC Dec 4, 2013 10:00 AM
    Hi Saurabh,
    As you know about how the DXC works by redirecting the flow of Data Source from PSA to an IMDSO in
    HANA.

    Generated by Jive on 2016-08-12Z


    3

    Data Source Key Field error for DXC

    So when this happens a set of tables has to be created in HANA based on the structure of Data Source. When
    the Data Source itself has no keys then the system throws an error while creating a table with no PK.
    Hence some of the Data Sources(With Keys) are directly supported, but others need some modifications in
    their structures which is given by these Notes.
    -Shreepad

    Generated by Jive on 2016-08-12Z


    4

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy