Introduction
This blog will cover the condition where you can generate a Notification to Appropriate Authority which can be a Buyer/Procurement Department , Accounts Payable Department/ Finance Department etc, that a Plant Maintenance Order/Workorder has been Technically Completed(TECO).
SAP BW means inflexible and expensive monolith? That doesn’t have to be! With SAP BW/4 HANA, the development can be much more iterative than before.
So the following applies(?): SAP BW/4 HANA = leaner, faster … cheaper? It depends on your architecture!
With this post I would like to give you an impression of why SAP BW/4 HANA (finally) enables data models that react flexibly to changes!
In any SAP BW on HANA and BW/4HANA implementations, customers use an NLS (Near Line Store) solution to offload and archive data from the main system. The offering from SAP as well as a few partners uses SAP IQ as the database for the NLS solution. Invariably, situations arise when performance against data in the NLS system just seems slower than it should be.
The focus of this blog is to point you in the different directions that can be at the root cause of any performance issues. As always, we must be prepared to change our expectations. On countless occasions, I have had customers demand that the NLS system perform at the same level as the HANA system. That is just not realistic and should never be expected. SAP HANA operates on data that is in-memory and was designed to be an in-memory platform. SAP IQ is a general purpose database that was designed for disk based storage, albeit highly optimized.
The SAP Web IDE provides so-called replication tasks to set up real-time replication. It provides a graphical UI to browse tables in your connected source systems, create virtual tables, create subscriptions for real-time replication, create data load partitioning strategies, and more. The replication tasks in Web IDE are part of the SAP Smart Data Integration (SDI) toolset, which comes integrated with the SAP HANA platform, both on-premise and in the cloud.
In this blog I will discuss about the development lifecycle process and steps of develop an calculation view in HANA 2.0 XSA environment using Web IDE.
In HANA 1.0 till SPS12 we have developed Calculation view with the catalog object tables from a schema also the operation available for development like Join, Union is very less.
In HANA 2.0 XSA environment using web IDE we will get more operation option like NonEqui Join, Graph, Rank, Rank, Hierarchy Function, Anonymization etc. which are not available in HANA studio. Those option any body can easily adopt and use in their view development. I will not discuss this in my blog.
Enabled in SAP Data Warehouse Cloud through SAP HANA data anonymization
A growing number of people is making use of the latest technologies. Its power and increasing accessibility are shown in personal apps that ultimately generate data. For companies that build solutions on new technologies and retrieve information about their users, it is key to use methodologies that allow handling sensitive data with care. In order to derive insights from data, adherence to data privacy laws and regulations needs to be ensured. These considerations are necessary not only with regards to external customer or supplier data but also when working with internal data as we did in the case outlined in this blog article.
SAP Analytics Cloud’s story mode supports various filter concepts such as story filters, page filters, widget filters, input controls and linked analysis. SAC’s Analytic Application uses a different approach to implement filter capabilities in dashboards. In fact, the Analytics Designer (where Analytic Applications are created) is all about customization and flexibility.
SAC’s Analytics Designer provides filtering capabilities through programming APIs. A full documentation of SAC Analytics Designer APIs can be found here. This enables developers to create the desired filtering logic within a dashboard. Furthermore, with Analytics Designer APIs you can create your own filtering concepts! This blog post will guide you along one specific scenario to create such a custom filter.
To get started with SAP HANA Cloud, you need to create your trial instance. Because you are using a trial account, you will only be able to create one instance with a predefined size, which you see now on the screen. However, the process to create the instance is very similar to what you will see later if you choose to have a production instance of SAP HANA Cloud.
Changed Requirements for modern Data Warehouse Systems mean that aspects such as Simplicity, Flexibility and Agility are becomming more important and therefore should be considered in the architecture and modeling of such systems.
With its data warehouse product, SAP BW4 / HANA, SAP offers the possibility of implementing such modern architectures beyond a rigid and outdated Layered Scalable Architecture (LSA). SAP recommends an architecture that is based on the LSA ++. This new layer approach is particularly characterized by the focus on virtual objects. Virtualization means that fewer copies of data are required between layers of architecture, making their design simpler, smaller and faster. The data warehouse architecture should be designed as lean and simple as possible.
In this blog I describe how to set up real-time replication, and in this case for a Microsoft SQL, or MSSQL, database. The tool of choice is SAP Smart Data Integration (SDI), which comes with SAP HANA Cloud or the on-prem version.
The whole process is also documented in the readme file of this Github repo. That repo also contains the Web IDE project to built on top of the replication setup. How you can use the Web IDE to create real-time replication tasks, I’ll describe as a follow-up blog.
SAP S/4 HANA implementation involve massive business process reengineering and introduces a new user interfaces (SAP Fiori) with a shift from monolithic solutions to activity-based apps which means many changes to the Technical and Business users. This raises a question whether the previous authorization concept still support the security requirements of SAP S/4HANA?
I have talked about how SLES HA Automation process can really help to build and deploy an SAP HANA environment highly available. Let’s continue to explore SLES 15.2 capabilities for SAP HANA platform and more.
For this second article, I will talk to you about how SLES HA Cluster Update for SAP HANA can be leverage for nZDU (upgrade/update). By using this process, SLES gives the ability to orchestrate your SAP HANA maintenance in an HA environment, fully guided and in the right sequence from a cluster point of view.
Recently, while working on a Greenfield BW/4HANA project, I found myself asking a lot of questions about the inner workings of the SAP Operational Delta Queue (ODQ) which replaced the traditional BW delta queue (RSA7) in SAP ECC system. What is ODP framework? What is the location of ODQ? How ODQ behaves for different delta types? What are important ODQ tables? How ODQ retention period is maintained? Having done some digging into the ODQ itself, I discovered more detail than I’d seen online, so thought it would be worth sharing my findings in this blog.
When loading data from source systems, there are requirements in SAP BW that are often repeated at the field level. This includes, above all, logic for cleaning up and processing the data, such as:
◉ Add and remove leading zeros
◉ Case distinctions
◉ Remove spaces at the beginning or end
◉ Conversion to capital letters
◉ Derive one field from another with fixed pattern sub-strings, e.g. COAREA ==> COUNTRY
◉ Derivation of time characteristics
When we starting with the operation of a SAP Business One on HANA 10 environment, sometimes you may find that there are no possibilities to install a SAP HANA Cockpit for the administration of the database HANA 2.0 or simply “it is not budgeted” in the scope of the project .
Due to the characteristics of this type of project and the target of some the clients, many times these don’t have the necessary infrastructure and the technical personnel qualified for the administration of HANA as it “should be”.
This happens mainly in On-Premise environments where the customer has to ensure the security and integrity of their data, regardless of whether the solution is installed under a hyperscaler or not.
