4 replies
  1. Jonathan Haun
    Jonathan Haun says:

    Depending on the solution you use to provision HANA and the source of your data, the metadata discovery process will vary. If a SAP application is the source, SAP has several prebuilt models to simplify the discovery process. If a non-SAP data source is used, you are on your own to develop the model. There are also three main tools used to obtain data. SLT is used for real-time replication. DXC is used to obtain data from SAP sources in batch. Finally SAP Data Services is used for traditional ETL and aquisition of data from any source. In short, depending on the selected architecture and source system, the amount of metadata management and data modeling that is needed will vary.

    Reply
  2. Nick Porter
    Nick Porter says:

    I think Graham has made some valid points. There are sets of pre-built content for HANA (HANA Live) and these cover a number of popular areas that user may want to work with. But outside these, metadata exploration will be required. Tools like SAP Data Services are great if you know which tables you need to work with, but if you don’t they give very limited ‘discovery’ capability. That’s not a criticism of Data Services or other similar products, their job is data movement and they do that very well. The ‘discovery’ exercise is often overlooked and can put a real shunt in a project if it’s not recognized.

    Reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *