Sap Netweaver System Requirements

• Sap Netweaver Log In
• Sap Netweaver 7.5 System Requirements
• Sap Netweaver Portal Login
• Sap Netweaver Architecture
• Sap Netweaver Download

Sap Netweaver Log In

Before start the installation, it is recommended to run SAP Prerequisite Check to ensure all the requirements are met. Once you complete and verified the prerequisite checks, you can continue to navigate as below, SAP NetWeaver 7.4 MS SQL Server SAP Systems. All products based on SAP NetWeaver AS ABAP 7.4 are supported. Requirements: Additive sizing – Additional memory resources for the SAP NetWeaver AS ABAP system needs to be available on the SAP HANA server.

SAP NetWeaver ABAP is the application server running most of SAP's software. Version 7.4 comes with Gateway and the option to run Fiori on top of it. The installation of a NetWeaver ABAP system is not overly complex for a developer system: basically it is just installing the software. This installation process is composed of three steps:

• Perform the actual installation

After executing all three steps, you have a fully functional SAP NetWeaver ABAP system.

To install a SAP system, you need to check first the hard ware requirements. You also need to ensure that a correct user/group is set up. This depends normally on the SID of your SAP system.

Software packages you'll need

• Database: Files to install the underlying database. Here I will use MaxDB.
• Kernel. The kernel files, depend on your operating system and if you want to use unicode (UC) or not. I'll use Linux x64 and a UC kernel.
• SAP Installer: SWPM. This is the sapinst program. Be careful, as two version of SWPM exist. One is for installing NW AS and products; the other is for installing BS, SolMan and NW 7.0.

  With SWPM10SPxx_PL.SAR:
  

  Products based on SAP NetWeaver 7.1x

  SAP Composition Environment 7.1x

  SAP Composition Environment 7.2

  Products based on SAP NetWeaver 7.3x

  Products based on SAP NetWeaver 7.4 SR1*, SR2

  With 70SWPM10SPxx_PL.SAR:
  

  SAP NetWeaver 7.0, including Enhancement Package 1, 2, 3

  SAP Business Suite 7i 2011, 2010, 7 SR1, 2005 SR3 based on SAP NetWeaver 7.0, including Enhancement Package 1, 2, and 3

  SAP Solution Manager 7.0 including EHP1 SR1

  SAP Solution Manager 7.1 SR1

• Application Server: ABAP

All files are delivered as ZIP, except SWPM. You'll have to un-SAR this one. Copy all unziped/unsared file to a common location on your server, like /install.

User

For each SAP system you'll need to have one corresponding administration user. The user ID is determined by the SAP system Id (SID). The user id follows the schema: adm. For instance, when your SAP system is going to use the SID GWD, the user will be gwdadm. The group can be anything, but normally you use sapsys as group name. Creating a user in Linux is easy as it is just one command, and with SuSE you even get a wizard that aids you through the process.

User

Group

To start the installation, just run sapinst from the SWPM package.

There are two executables: sapinst and sapinstgui. Sapinst will start the local server and the local GUI, while sapinstgui needs to connect to an already started sapinst server. As long as you do not have to do a remote installation, sapinst is the executable you want to run.

The initial screen shows the install options

Pre-requisites check

I am going to install SAP NetWeaver 7.4 Support Release 2 ABAP for MaxDB. First thing to run is the preparations step.

Select what sapinst should test. If nothing is selected, sapinst will check a basic set of requirements. This does not mean that after the check is done your system really meets all the requirements. So make sure you select what you are going to install to have a meaningful test result. As I am going to install NetWeaver ABAP, I selected the ABAP related checks.

Provide the database type.

Confirm that a UC system will be installed.

SAPinst will ask for the location of the Kernel files.

Inform the location of the files. In my case, they are located at /sap/inst

Confirm the prerequisites data. If everything is OK, you can start the process.

The requisites are being verified.

After the check is done, sapinst presents you a screen with the results.

Go through the list. Everything needs to be OK.

The final dialog confirms that everything is OK and that a report was saved to a local file.

Now we are good to go: sapinst checked the system and gave it a quality stamp. Nothing impedes the installation of NetWeaver ABAP 7.4 SR2 with MaxDB.

Installation

The NW ABAP 7.4 SR2 system is going to be a standalone system, with everything on the same host.

Installation type

Installation mode

Chose mode. Typical is enough, you'll see still more than enough input dialogs.

In case the mode of the files is not correct, do not worry. Sapinst will take care of that (thank you sapinst!).

SAP system id

Specify the SID (here: GWD) and the mount directory (here: /sapmnt).

Set DNS name

The 2^nd input field is to set the domain name of the server. Do not enter the FQDN or the name of the server here, just the DNS name (here: tobias.de). If you server is nwgw74.tobias.de, only the tobias.de part.

Kernel files

Standard password for all users

Database SID

DB files

Inform where the DB files are located

ABAP files

Inform location of ABAP files

SLD

Let's do not add the system to a SLD

Secure Storage Key Generation

Let the installer create a secure key

Review parameters

Start installation

Lean back and relax, this will take a while

End of installation

After all steps are executed successfully and marked with a green check, the installation is done.

Install SAP license

Log on to the new SAP system is done via SAPGui. User is SAP* and the password is the standard password given during installation.

Transaction: slicense

Automatically, a temporary license is installed.

Click the install button and select the license file. If everything is OK, a popup will confirm the installation of the license(s).

Last check is to verify that the new license is installed and active.

If the installation goes through without any error: congratulations. Many users will run into some errors, just do a search on SCN for installation problems. Here are some common problems and their solution:

R3load connect error

Step: Import ABAP:

Problem: R3load –testconnect fails

Analysis:

Log file:

• File exists in sapdb folder

Cause: Library not loaded

How to add the MaxDB library to the LD path? Configuration is stored in directory /etc/ld.so.conf

The last line is a include parameter. To add the Max DB libraries, it is just to create a conf file maxdb.conf in /etc/ld.so.conf.d/ and add the lib path to the new file.

Running the ld command from above:

Sapinst: retry

Strange errors

SAPinst should be run as the admin user of the instance: adm. SCN is full of errors from users that had the problem to run the Import ABAP step. That error is caused by running the installation as root and not as adm. For instance, to configure the DB, R3load is called. With user adm the program connects flawlessly to the DB, as user root not. This is given by the simple fact that the environment variables are set for adm, and not for user root.

SAPUXUSERCHECK

In case sapinst isn't capable of setting the right permissions to the file sapuxusercheck, follow SAP Note 1563660.

Introduction:

I, Pradeep Srigiri working as Architect and has around 15 years of experience in SAP. Currently, I work for YASH Technologies. This blog post consists of High-Level technical information on S/4HANA Conversion Road Map from SAP Basis perspective from On-Premise to Cloud or Vice-Versa or Cloud to Cloud. However, I would like to recommend following the SAP Standard Guides & SAP Notes during the S/4HANA Conversion Process. This blog post will take you there in a structured method for current release and can use same process for other releases to find out the details easily.

SAP S/4HANA Conversion Road Map:

The blog post consists of the below steps.

Discovery Phase

System Requirements & Planning:

• Supported OS Versions for S/4HANA 1909
  SUSE Linux 12.0 or greater
  RHEL 7.0 or greater
  AIX 7.1 & 7.2
  Microsoft Windows 2016 or 2019
• Supported DB Version – S/4HANA 1909
  HANA 2.0 SP04 (Min)
• Minimum Source Versions with UNICODE required for S/4HANA 1909
  SAP ERP 6.0 SP20
  EHP2 FOR SAP ERP 6.0 SP10
  EHP3 FOR SAP ERP 6.0 SP09
  EHP4 to EHP8 FOR SAP ERP 6.0 No minimum SP required.
• Compatible NetWeaver versions for S/4HANA 1909
  SAP NetWeaver 7.0 SP14
  SAP EHP1 for SAP NetWeaver 7.0 SP05
  SAP EHP2 for SAP NetWeaver 7.0 SP06
  SAP EHP3 for SAP NetWeaver 7.0 SP01
  SAP NetWeaver 7.4 SP02
• For Cloud Support OS, DB & SAP, Check the below SAP Notes
  1656099 – SAP Applications on AWS: Supported DB/OS and AWS EC2 products
  1928533 – SAP Applications on Azure: Supported Products and Azure VM types
  SAP Note 2456406 – SAP on Google Cloud: Support Prerequisites
• Compatibility Matrix Checks – use PAM in SAP Support Portal
• Tools Used – DMO of SUM 2.0 SP8 (Latest) if Source is on non-HANA DB
  DMO with System Move for Conversion with DB Migration & data center relocation
• Use Data Volume Reduction – SAP Data Volume Management
  Reduces the data footprint & achieve a shorter conversion duration
  Capabilities supporting the pre- and post-conversion phases
  One central tool is the SAP DVM Work Center (DVM WoC) in SAP Solution Manager
• Maintenance Planner
  Generates the download files for Conversion
• List of supported add-ons see SAP Note 2214409.
• Business functions can have the following status: always_on, customer_switchable, and always_off (SAP Notes 2240359 and 2240360)
• Checks Industry Solutions – SAP Note 2799003

• SAP Solution Manager & SAP Systems – Backend SAP Support Connection
• To download & implement the SAP Notes
• To Pull the Latest Simplification Items from Support Portal to run the reports

Sap Netweaver 7.5 System Requirements

Conversion Pre-Check:

Readiness Check

• Achieve Next Generation SAP Business Scenario Recommendations
• Implement SAP Note 2745851
• Implement SAP Note 2758146
• Follow the steps mentioned in https://d.dam.sap.com/a/AREDtXr/Next-Generation_BSR_How_To-V27.pdf and upload the zip file in the SAP's website.
• Setting up SAP Readiness Check 2.0

• Implement SAP Note 2758146
• RC_COLLECT_ANALYSIS_DATA is the Report
• Activity 16 (Execution) of Authorization Object S_DEVELOP is required
  • For Discovery Phase Selection
  • Implement SAP Note 2185390: Set up custom code analysis
  • Implement SAP Note 1872170: Enabling SAP S/4HANA sizing
  • Implement SAP Note 2399707 – Simplification Item Check
  • Implement SAP Note 2769657 – INR: Interface Discovery for Idoc
  • Implement SAP Note 2721530 – Enabling Data Volume Management analysis
  • Implement SAP Note 2811183 – Enabling BP/CVI Analysis with Readiness Check 2.0
  • Implement SAP Note 2781766 – Enabling ATC check result export for SAP Readiness Check 2.0
  • Implement SAP Note 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks
• I Executed the Report RC_COLLECT_ANALYSIS_DATA in SE38 choosing relevant pre-check options (Background)

• Launch the SAP Readiness Check application using https://rc.cfapps.eu10.hana.ondemand.com and use the ZIP file that was generated from the program RC_COLLECT_ANALYSIS_DATA.
• To create a new analysis, I have clicked Create New Analysis

• SAP Readiness Check 2.0 will be ready under 30 minutes and followed with Pre-Checks Analysis
• For Custom Code Adjustments – Run program SYCM_DOWNLOAD_REPOSITORY_INFO
• Download the ZIP file and upload it to the Readiness check Link by selecting 'Update Analysis'

Addon Compatibility Check

• Retrieves the add-on and business function data from Maintenance Planner
• Check SAP Note 2214409

• Business functions
• Simplification Item Check to identify the mandatory steps before converting your system.
• CVI Conversion Prep

Sap Netweaver Portal Login

Custom Code Migration & Simplification Item Checks:

• Need to be performed by the respective teams using the latest custom code apps provided by SAP and implement the SAP Notes related to the Simplification Item Checks in the system before the Basis Team runs the SUM tool to start the Technical Conversion

Conversion Planning – landscape

Parallel Landscape Build

• Implement emergency fixes and to reduce the timelines for the code-freeze – build a parallel conversion/migration landscape.
• Any emergency change that is implemented in production landscape should also be applied in conversion/migration landscape.

It's always recommended to have Sandbox ready with a copy of Production System in order to start the S/4HANA Conversion to have a better under standing on the impact and procedure that can be followed in the upcoming systems with lessons learn during the Sandbox System conversion. However, the above Parallel Landscape is being used only for Development, Quality & Production Systems

High Level Roadmap

• Below pictorial diagram shows the process flow to achieve S/4HANA Conversion & Migration to Cloud or to On-Premise

High Level Cost Estimate

H/W Estimates:

• To determine the H/W sizing, implement SAP Note 1872170: Enabling SAP S/4HANA sizing
• Execute the program /SDF/HDB_SIZING in SE38

Sap Netweaver Architecture

• or select the pre-check option in SAP Readiness Check Report RC_COLLECT_ANALYSIS_DATA

Result: Upload the ZIP file in Readiness Check Link

• Below is the Sizing information

• Sizing for SAP Applications can be determined based on the current landscape for DEV, QAS & PRD systems with some additional increase in the Hardware Resources

S/W Estimates:

• Based on the system requirements column, any one of the mentioned releases & version can be on the source system to perform the conversion to S/4HANA
• S/4HANA 1909: Impact on current landscape – Use Upgrade Dependency Analyzer from Support Portal : https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ)/support/uda/main.htm and System Requirements for NetWeaver
• Procurement of S/4HANA License from SAP
• Identify the Solution Approach based on the existing releases
• Based on the Solution Approach, estimate the man days required for Basis to perform

Pre-Conversion Action list

Basis:

• Implement SAP Notes related to pre-checks using SNOTE
• Remove Client 066 – Not used in S/4HANA: Check SAP Note 1749142
• Uninstall Fiori Apps – if not released for SAP_UI 7.50: Check SAP Note 2034588
• Use Maintenance Planner to calculate stack.xml file and download files required for S/4HANA conversion
• Perform OS Prerequisites on S/4HANA Application & Target HANA Server
• Download the HANA Installation Media
• Setup Target HANA Server based on the Installation Guide
• Perform the prerequisites for HANA DMO – if required. For Prerequisites check SAP Notes 2882441 & 2832250
• Download SUM 2.0 SP8 on Source and Target Application Servers with the downloaded files

Target Landscape

• Based on the source SAP, DB & OS versions – below are the Major migration options

Note: Target or Source can be On-Premise or Cloud

1. One Step Migration: HANA DMO with S/4 HANA Conversion during the same maintenance window

2. Two Step Migration: Existing SAP/DB Upgrade and HANA DMO with S/4HANA Conversion

or

Lift & Shift AS-IS to Cloud and HANA DMO with S/4HANA Conversion

• HANA DMO required if source is on Non-HANA DB

Conclusion:

I would like to conclude that I have validated the SAP SUM DMO Guides and S/4HANA Conversion Guides from Support Portal and relevant information from the Notes mentioned in this blog post. I have followed the above mentioned steps & process and was able to achieve the goal which is S/4HANA 1909 conversion.

Sap Netweaver Download

Reference below:

https://help.sap.com/doc/2b87656c4eee4284a5eb8976c0fe88fc/1909/en-US/CONV_OP1909_latest.pdf

Thank you! Hope the blog post is helpful.

Best Regards,

Pradeep Srigiri, Architect