This is in continuation of my previous blog post Backup and Recovery of SAP HANA Database on Azure using Azure Backup Plugin for HANA – Part I
3.1 Discovery of Databases
After running the pre-registration script, we need to go to the Azure portal → Recovery Service Vault → + Backup
This article mostly concentrates on the information about installation and configurations of Azure Backup Plugin for HANA and related changes that needs to be done on HANA databases for backing up the HANA database.
SAP HANA databases are mission critical workloads that require a low recovery point objective (RPO) and a fast recovery time objective (RTO). SAP HANA databases can be backed up by running on Azure VMs using Azure Backup.
This Blog would give us most of the information about calendar attributes or date attributes through ABAP CDS. I am involved in Group Reporting implementation where we have to deal with lot of date attributes.
Little background on Group reporting, the data from group reporting is stored in ACDOCU (Consolidation Data table) where the data can be stored as Consolidated or Pre-consolidated which differentiated by RECORD TYPE. Consolidated data will have RECORD TYPE ‘R’, and the data is stored in cumulative manner ( Balance Carry Forward). For Balance Sheet reports if we want report DEC.2020 value then if you can directly the value of last period of the year 2020 and also YTD value for the 2020 can derived by reading last period value of 2020 as Record Type R will have Balance Carry forward. But the complexity increases when you are creating or designing the P&L reports where we need to show periodic values of the each month instead of Balance Carry forward.
In this blog, the steps outlined for setting up Custom Email Template for Purchase Requisition (PR) Item release with email Integration. This will help us set up an Email Header and Body as per Customer requirements. The SAP S/4HANA system can be configured to notify approvers via email about new work items in their inbox. By default, the approvers are informed by means of notifications in the SAP Fiori Launchpad. Sending emails provides them with an additional notification channel.
SAP Business Application Studio (a.k.a. BAS) is a modern development environment that enables developers to easily build and extend SAP solutions, seamlessly integrating SAP services, technologies, and solutions.
As an SAP product, it is designed to offer an Enterprise-Grade Security solution.
In this blog post, I will describe some of the different Kubernetes (K8S) security patterns and industry best practices that are implemented in SAP Business Application Studio for users that want to understand how it is done under the hood.
Note: I will not cover all the security aspects in this blog post, I will share a subset of them. As an SAP Business Application Studio is an Enterprise Product, we constantly reinvestigate and reevaluate it, including the new features and according to industry standards.
In this blog post I will try and show you the easiest way to import shapefiles data into HANA Cloud, via the wizard.
There are alternative ways of importing spatial data, that can be used.
◉ Import shapefile via wizard
◉ Import CSV via wizard and convert to spatial data types
◉ Import CSV from Cloud Object Store (S3, GCS, ADL) and convert.
In this blog post I will focus on our firsthand experience with remote conversions and point out the steps needed for a successful migration. A remote conversion consists of 2 Steps. Step 1 the Meta data conversion is being described in this blog post. Step 2 the Data Conversion is not discussed in this blog post.
With an In-place conversion the customer first needs to upgrade its BW system to BW 7.5 compatibility mode. For a client that is currently on BW 7.4 this requirement will add a step to navigate on their route from earlier versions of BW to SAP BW/4HANA For many customers, the Remote Conversion offers a way to avoid the initial upgrade to BW 7.5. Remote conversions can originate out of BW systems from BW7.3 and up. In addition, the sender system does not need to be on a Hana data base while an in place conversion requires to have a Hana DB as a starting point.
This blog post will outline how we can dynamically populate date in HANA Views that are designed to run for specific days only. We will demonstrate that instead of hardcoding the dates in the view we can populate them externally and facilitate the materialization (storing data into an ADSO/HANA Table) to happen with minimal manual intervention.
We’ll take an example of 2 views which have filters at their base projections to restrict data for 4 specific dates: Current Day, Current Day-1, Current Day-5, and Current Day-6.
We have been hearing/reading lot about SAP S/4HANA – Intelligent capabilities to consume and build applications infused with Machine Learning capabilities for text processing, image processing, predictive analytics…
In this article I would like to share the strategic dimensions and Intelligent Enterprise Solutions guiding principles enabled SAP to Operationalize Intelligence and thus increased process automation, faster response times.
SAP S/4HANA the Digital core ERP system acts as central system for an enterprise organization’s business processes infused with Intelligent capabilities.
The Export Master Data applications are a great way to pull a selection of master data into an Excel or CSV file. As of the 2102 release, there is an Export Master Data application variant for material/product, business partner, and business partner relationship master data.
CAP applications in either NodeJS or Java are a powerful tool for rapid development in the cloud. With simplified syntax, it is reasonably simple to create a beautiful and powerful application.
Usually a CAP application has the following structure
◉ /db
◉ /srv
◉ .hdiconfig
We will talk about how to perform data federation between SAP HANA Cloud and Amazon S3 bucket so that we can incorporate external data into our business data while keeping both data sitting in their own places. We will be focusing a bit more on the integration part where we need to install and run SAP Data Provisioning Agent on Linux environment. The architecture for the result looks like the following:
This blog post is to explain how to replicate a table from SAP S/4HANA >> SAP Landscape Transformation (SLT) >> DB2 Z/OS
◉ RFC Connection between SAP S/4HANA and SAP Landscape Transformation (SLT)
◉ DB Connection Between SAP Landscape Transformation (SLT) >> DB2 Z/OS
◉ Manually creating the Table in Target before starting the Replication
◉ Other Mandatory settings in SAP Landscape Transformation (SLT) like having all the required notes implemented in Source as per the version of SAP Landscape Transformation (SLT), users and required roles and privileges in Source and target.
◉ Required DB2 Drivers or ODBC connection from SAP Landscape Transformation (SLT) to DB2 Z/OS
There are times when your system copy requirements are more complex than what the guide describes. There are also times when the official documentation is not only innacurate but also completely misleading. This blog is about such a time.
When performing system copy you usually have several option how to copy the database from the source to the target system. Here I am focusing on restore using backint. In this case I am using Veritas Netbackup, but this procedure should be mostly valid for any certified HANA backint solution.
The reason for writing this blog is that SAP HANA Admin Guide is too generic and keeps refering to HANA studio. Also Netbackup Admin guide is still referring to HANA Studio too. Unfortunately HANA Studio isn’t really developed anymore and the current version can’t be used to do system copy using restore on a multitenant (i.e. HANA 2.0) database.
This blog is the continuation from blog Mass processing of Business partners using MDC in Fiori (Part-1)
In this blog I am going to discuss how to use the Fiori apps to create a process for update operation of master data.
During all SAP Implementation and roll-out projects we will have a requirement of updating different kinds of master data in the system.
The most common way is to use the ‘MASS’ transaction or develop custom programs using BAPI, BDC or LSMW to update master data.
For customers on S/4 Hana with MDG component, we can use Mass processing and consolidation option to upload different kind of master data’s (Business Partner, Business partner Relationship, Product master ).
I am sure many of us have come across a number of use cases where we need to perform real-time reconciliation of S/4HANA data in BW/4HANA system. Let us consider one of the most critical use cases and go through how this can be achieved.
In many companies, BW system is being used for financial month-end closing requirements. As part of it, the financial related data is extracted (e.g.: 0FI_ACDOCA_10 – Universal Journal Entry) from S/4HANA system and it is fed into a standard/custom ADSO in BW system.
During the month-end closing (specifically last 2 to 3 days), the financial data is frequently updated in S/4HANA system and the same data is extracted and reported (e.g.: Profit & Lost Statement, Balance Sheet, etc.) in BW system. It’s an iterative process.
