Let's Talk SAP

Step 1 : Content Migration for SAP HANA The old repo of SAP HANA 1.0 stores calculation views ( native artifacts : to create and access native database objects ) in a singleton schema _SYS_BIC which is not zero downtime compliant  Future Scope is to ship the above native artifacts of SAP HANA will be shipped in HDI Containers to be zero downtime ready  Several areas in SAP S/4HANA have already provided reports to migrate native content of SAP HANA from Repo of SAP HANA 1.0 to HDI containers. Summary from the above mentioned 3 points would be that native artifacts that were used to create or access native database objects are not supported by ZDO and are migrated to HDI containers to make them compatible for the same All changes performed by SUM in ZDO need to be invisible to the user in the bridge sub system . The repo 1.0 in SAP HANA (native artifacts) does not have the capability to encapsulate the changes during ZDO upgrades. Since SAP S/4HANA 1709 FPS 02 ,comes with the new way to

Whenever we think about different downtime approaches 1.Standard Approach 2. Near Zero Downtime Approach  3. Zero Downtime Approach 1 -> 2 -> 3 [Effort increases and Downtime decreases ] So even if we say Zero Downtime Option it means you will surely have a very small downtime that is the business downtime ( Ramp Down Restart Ramp Up ) This will be a series of blog and this is part 1 of that blog. All the technical downtime in Zero Downtime approach is shifted to the phase called Uptime on Bridge. This approach is generally available starting from SAP S/4HANA 2021 also includes the update of feature or support package stacks within SAP S/4HANA 2020 also SAP S/4HANA Foundation 2020 (not allowed as standalone but only as foundation in combination with a defined list of add-on product version )i.e. ZDO can be used as a Standard feature.   Note :- ZDO is not applicable for system conversion  SAP S/4HANA supports add-ons from different vendors like SAP or 3rd party: 1. Standard add-

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

This is a very small blog just discussing an issue faced while using R3trans -d , Basically this needs some environment variable attached to it i.e. before running this command you should just make sure that your environment variables are set. Whenever we get this dbms_type is not set , the first thing which should be checked is that the environment variables are set or not. What is environment variable ? We have different types of environment variable but without confusing you , right now we are talking about local environment variable These variable are set and configured in ~/.bashrc, ~/.bash_profile, ~/.bash_login, ~/.profile  files according to the requirement. These variables can be accessed by a particular user and persist through power offs. Now the point to understand here, is that the local variable is as per the user , thus it is mandatory for us to run r3trans -d from <sid>adm user (OS User). Moving forward , sometimes this issue is resolved using start R3trans -d

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info