Creating an Open ODS View (field based modeling), for source of type “database table or view”:
There are two ways of creating an Open ODS view in the Data Warehousing Workbench in the BW system and you also have the option of creating Open ODS views in the BW Modeling tools in Eclipse.
Create in the InfoProvider Tree:
In the InfoProvider tree in the Data Warehousing Workbench, select the InfoArea that you want to assign the new Open ODS view to and choose Create Open ODS View in the InfoArea’s context menu. The dialog box for creating Open ODS views appears.
Under View Name, enter a technical name for the Open ODS view.
Enter a description for the Open ODS view under Long Description.
Select the semantics (facts, master data, and texts).
Select the type (DataSource (BW), database table or view, Virtual Table Using HANA Smart Data Access).
For sources of type database table or view:
- a. Under DB Object Schema, select the
schema where the table or view is located, which you want to use as the source object for the Open ODS view. You can choose from the schemas of the SAP HANA database, which the BW system runs on.
- b. A DB Connect source system is used to access the data in the source. The schema is specified in the configuration of the DB Connect source system. If a source system has already been defined for the DB object schema, this system is displayed in the Source System field. If there is no source system for the schema, it is created when the Open ODS view is created. In this case, the source system field displays a suggested name that you can overwrite. The proposal is derived from the schema name.
- c. In the DB Object Name field, select a table or view as the source object of the Open ODS view.
In the Open ODS view maintenance screen, you can generate the structure of the Open ODS view on the semantics tab by assigning the fields of the source object to field categories (example: for facts, assign to the categories characteristic key, characteristic, key figure and others).
To perform an automatic assignment of source fields to field categories of the Open ODS view, select the Create Proposal button. The system generates the proposal based on the source type. Alternatively, you can drag source fields into the field categories of the Open ODS view.
General Field Properties:
Field Name, Source Field, Long Description and Global Name.
The global field name is the name used as the InfoObject name in the InfoProvider of the Open ODS view. The global name is initially determined from the ODP name and the name of the Open ODS view field.
Properties for Fields of Type “Characteristic” :
Authorization Relevance, Display, Query Exec-Filter Val and Association.
Using associations on fields of type “characteristic”, you can link an Open ODS view to master data and texts of other Open ODS views or InfoObjects. This makes it possible to inherit properties – such as the global name, the authorization relevance or reporting properties of the associated object – and use texts and navigation attributes of the associated objects in the InfoProvider of the Open ODS view. Initially there are no associations.
Properties for Fields of Type “Key Figure”:
Aggregation, Currency/Unit, Reporting Properties.
Using associations on fields of type “key figure”, you can link an Open ODS view with InfoObjects. This allows you, for example, to use formulas and variables (defined on the associated InfoObject) in queries on the Open ODS view and inherit properties (such as the global name, aggregation or reporting properties) from the associated object. Initially there are no associations.
Open ODS view can be used in EDW modeling. Click on generate dataflow icon, it will create standard DSO, transformations and DTP.
good work, helpful ..
Thanks for sharing, good stuff.
Good work Madam........
Thanks Saritha. One question I have not checked in system but Open ODS view does sound like Transient infoprovider except analytic index and datasource as a source part?
Correct me if wrong please.
What do you mean by trainsient provider here are you refering to published HANA models in BW or you are refering to analytical index created in workspace?
In comparison to published HANA models in BW as transient provider the differences are:
1) Direct access of virtual table (SDA) is supported .
2) Data can be persisted simply via clicking
single dataflow button.
3)Own Schema can be build by joining multiple ODS not necessary to stick ony to start schema in BW.
4) Can consume HANA Managed schemas(tables and views) in BW
5)HANA artifacts cannot be used.
Hope this helps...
Thanks & Regards
Thanks for the details. I have only theoretical knowledge so correct me if wrong.
Transient- I meant RSDD_HM_PUBLISH where we create index on hana model ,tables/views and use it for extracting data. Here also data is extracted on the fly like ODS view.
May be data flow can not be created on transient provider but basic mechanism is same of populating metadata and data in BW?
You have to create Analytical Index on SAP HANA View, then your transient provider if you want to make use of any table/views in your Agile Data Mart - SAP HANA Studio.
Via RSDD_HM_PUBLISH you cannot access HANA Catalog objects you can access only Package object that means you cannot access HANA Database Objects Tables & Views.
But via Open ODS you can access even the DB tables and views.
You are also partially right transient and ODS has many features in common but in long term and in road map persecptive if you see transient provider will fade away and more investment goes in Open ODS.
I hope I have addressed your question now..
Thanks & Regards
Yes it is answered Dinesh. Package objects means I think it is allowed only on Analytic, calculation or attribute views for transient and for database table it is not possible.
Again small correction ,even in Pacakge objects you can access only analytical and calculation view not attribute view 🙂 .
Thanks & Regards