Documente Academic
Documente Profesional
Documente Cultură
based replication. It is the replication technology to pass the data from the source
system to the target system. Here the source can be either SAP or non-SAP whereas
the Target system is SAP HANA system which contains HANA database.
<REPLICATION_SCHEMA>_SELECT
2 Stored procedures
RS_GRANT_ACCESS, RS_REVOKE_ACCESS
8 Tables
DD02L, DD02T, RS_LOG_FILES, RS_MESSAGES,
RS_ORDER, RS_ORDER_EXT,RS_SCHEMA_MAP,
RS_STATUS
Key features
Key features
We will now see the basic feature of Extraction and Loading from
Flat file system to HANA using BO Data Services.
5 Modeling in HANA
Modeling in BW on HANA
We will now see the basic steps of modeling Data marts in BW on
HANA.
Composite Provider
For Manual mapping, right click the dimension and click provider
specific-Info Objects properties.
Similarly do the same for Key Dimensions.
Note: Make sure measure attributes like COST,
NETPRICE,NETVALUE have same data type with predefined Info
Objects .
Finally Virtual provider is created and we now check the data
SAP BW 7.4 is released and we are excited to check the new functionality in the
system. In this blog series we will collect the most interesting to us new or
enhanced features of the system Integration with SAP HANA database, Planning
in SAP BW, LSA++, Operational Data Provisioning (ODP) and so much more.
The new major release of SAP NetWeaver is released and we are excited to check what
are the new features and developments around SAP BW.
SAP HANA
SAP HANA DB
Logically, the major developments come around the integration between SAP BW and
the SAP HANA platform. So, SAP Netweaver BW 7.4 utilizes the SAP HANA as an
underlying database and facilitates the optimization of applications for SAP HANA.
SAP HANA OPTIMIZED INFOPROVIDERS
Developers can now implement standard InfoCubes, standard DataStore objects and
semantically partitioned objects, which are optimized for SAP HANA. On top of that
existing objects can also be converted to SAP HANA optimized ones. The remodeling
feature is also enhanced, so that it can suit to the new objects.
New InfoProvider
The new InfoProvider is a VirtualProvider based on an SAP HANA model. Analytic views
and calculation views are available as SAP HANA models. This type of VirtualProvider
is capable to serve stable, long-term scenarios. Moreover, if you want a purely
virtualized model, there is the option to create virtual master data as well.
PLANNING
Planning Applications Kit
Set Key Figure Values is available in planning. The function sets values for key figures
and distributes them according to reference data.
BW WORKSPACE
This is a completely new functionality, which allows business users to create models
using central data from the BW system and local data, and to react quickly to new and
changing requirements. The functionality targets users, who would like to create ad-hoc
scenarios or would like to make a rapid prototype of a reporting solution. The
environment is integrated into the existing BW landscape, but makes the typical BW
functions less complex.
DB CONNECT
DB Connect can be used now to replicate data to BW from any schema in the SAP
HANA database.
TRANSFERRING DATA USING OPERATIONAL DATA PROVISIONING (ODP)
Using the ODP data replication interface, developers can transfer data from specific
SAP repositories (especially from SAP HANA and SAP Business ByDesign) to SAP
NetWeaver Business Warehouse.
Advanced DSO
Hi Diva,
1. What is the difference between ADSO and OpenODS? ADSO and openODS both support field based reporting and
Infobject level reporting .What are the benefits of using and ADSO over an openODS for reporting?
Open ODS view is a virtual provider and ADSO is a info provider.
2. Can ADSO act as a virtual provider i.e can it report directly from an ECC source?
No. By using SLT you can report on a live data but can't be used as a virtual provider.
A given database table is either memory-based (HANA column or row tables), or disk-based (extended table of
dynamic tiering). It is not possible to create a single table that has partitions in memory and partitions in dynamic
tiering. Extended tables cannot be partitioned. When a partitioned in-memory column table is converted to an
extended table (ALTER TABLE USING EXTENDED STORAGE), the partitioning specification is dropped and the
extended table is created as a non-partitioned table that contains the contents of all partitions of the original table.
5. As far as I know the request handling technique is Different b/w aDSO and In-Memory Cube or In-Memory DSO.
Also in-bound queue in aDSO can be kept in the WARM data.