Sl. No.
Steps
Preparation of server
1 (VM validation)
2 Download and install the software(application and Database)
3 Downloading the add-on ( BI_ CONT )
4 Satisfy all the constraints
5 Running the Software Update Manager
Pre-Installation Setup of Mandatory Software Components
6
(Technical Configuration of the SAP HANA Database)
Details
1. Hardware and Software requirements check on OS
level (verify with Build Sheet Specifications)
2. Validate the FS and Sizes as per the layout design
document.
3. Validate the CPU and Memory Allocation with design
document.
4. Check for the global and local DIR files for available
space and permission.
5. Check if additional directory is present for backup and
export locations. If not we will require appropriate space
for it.
6. Validate hosts file in the target servers and Kernel
parameter Validation.
SAP BW on HANA we need to install SAP NetWeaver AS
for ABAP 7.52 with SAP HANA 1.0. Use the SAP
Maintenance Planner tool to select and download the
SAP NetWeaver installation files together with the SAP
HANA and the SAP BW Component Software files.
To get the installation of required SAP NetWeaver files
started, select Install or Maintain an Add-on and then
Install an AS ABAP system on HANA with product version
AS ABAP 1709 ON HANA, support package stack 17
(02/2020), in Maintenance Planner.
using the Maintenance Planner tool, select as your
system type, Install an AS ABAP ON HANA system with
product version AS ABAP 1709 ON HANA, support
package stack 17 (02/2020); then choose Install or
Maintain an Add-on and select as your software target
level, the product version name SAP NW 7.40 BI CONT
ADDON 7.57[SAPK-75724INBICONT]
○ 153967 : (BI Content Release Strategy)
○ 1000822 : (Overview: SAP Notes for the add-ons
BI_CONT and BI_CONT_XT)
○ 1678780 : (Installation or upgrade
BI_CONT/BI_CONT_XT 707/737/747)
○ 1943931 (Installation/Upgrade für das ABAPAdd-On
BI_CONT 757 / BI_CONT_XT 757).
○ 1808103 (BI Cont 737/747 SP04 and higher:
Information on Add-On SPs)
○ 1853775 (Errors when using BI Content 7.47 SP04 on
SAP BW 7.40 SP02)
○ 1600929 (SAP BW powered by SAP HANA
DB:Information)
○ 1949273 (Important SAP Notes for SAP BW
7.40,powered by SAP HANA)
After you have selected and downloaded installation files
with the SAP Maintenance Planner, then use the Software
Update Manager (SUM) or bu using SAINT T-code to install
the add-on.
Please check if the following tables are part of the row
store in the SAP HANA DB before you start to implement
Support Packages or other Add-Ons like Business
Content, SEM or BPC to ensure a performant import:
DOKIL, TADIR, E070, E071, PAT01. VRSD and SMODILOG.
If the tables are not in the row store you can use the SQL
Tool which has been delivered with SAP HANA Studio to
move the table within schema SAP<SID>:
alter table DOKIL row;
The tables can stay in the row store.
You can find alternative options and an exact description
of the change process in SAP Note 1660125.
See SAP Note 1659383 for more information about which
tables are located in the row store.
Reference SAP Note/link
Rlease and info. Note :-0002859225
◾2156130 - Add-on compatibility of SAP NetWeaver 7.5 - ABAP
CPU Core
Memory (RAM)
Information required for Source SWAP
Time Zone
Domain (DNS)
SAP SID
Host Alias
Instance No
Database
File-System
Information required for mounted file systems /usr/sap
/sapmnt
/usr/sap/trans (mounted from production)
Hana
Local/NFS Mounted/Global (NFS) Mount Purpose Size (GB) Owner Permission
local
Local
local
After installation, login to the 000 client and add the logical system entry.
Transaction BD54: Add all Logical systems which are in use
STEPS
2
3
10
11
12
13
14
POST ACTIVITIES
Check and modify the settings for the operating system users for your SAP system if they were created by SAPinst.
Set the required permissions for sapstartsrv and sapuxuserchk in the /<sapmnt>/<SAPSID>/exe, and /usr/sap/<SAPSID>/SYS/e
/usr/sap/<SAPSID>/<Instance_Name>/exe directories
call transaction SM21
1. Go to support.sap.com
2. Provide installation number.
3. Provide Hardware key.
5. Generate a new license and save it locally.
6. Apply the license with Tcode Slicense
Call transaction SICK. You should see the entry SAP System Check | no errors reported
In the DBA Cockpit (transaction DBACOCKPIT), check for missing tables or indexes by choosing Diagnostics Missing Tables and
Maintain the logical Systems
After installation, login to the 000 client and add the logical system entry.
Transaction BD54: Add all Logical systems which are in use
". For Quality/Production system: “No changes allowed”
Cross-client Object changes
For development system: Changes to repository and cross-client Customizing allowed."
. After creating the standard client, add the parameter login/no_automatic_user_sapstar in the instance profile and restart
". After creating the standard client, add the parameter login/no_automatic_user_sapstar in the instance profile and restart th
parameter to take effect. After the restart, you will be able to login to the standard client using the sap* user id with the stan
Perform a client copy from 000 client to the standard client which you have created
T-code SCCL."
". Schedule a background job to by giving the above input values.
Once the client copy is completed, perform a kernel upgrade to the latest level and then support pack upgrade."
RSADMINC (Customizing Table General BW) table configuration
Update the Table with below values:
INFOIDOCFRQ update with the value 10
IDOCPACKSIZE update with the value 30000
Step3: PSAPARTSIZE update with the value 1000000
File name: BW_OLAP_CACHE
File name span: BW_OLAP_CACHE_SPAN
UOM_BUFF_SIZE: 500
SPLT_QRY_TAB_THR: 50
SPLT_DM_TAB_THR: 20
ORA_PARALLEL_DEG: 4
TMPLID_ANALYZER: ANALYSIS_PATTERN_SPECIAL
RSER_TMPL_ID: 0REPORT_DEFAULT_SPECIAL
This table should have updated with User in source system for ALE communication – ALEREMOTE
Activating the Software Component SAP_BW in the CVERS_ACT Table
You can use Function module “RS_SET_ACTIVE_COMPONENT_FLAG” in SE37 to set flag I_ACTIVE_FLAG = ‘X’
Preparing the BW System
Go to transaction code RSA1:
Start the Data Warehousing Workbench (transaction RSA1). When starting for the first time, the ‘myself source system’ is crea
and table RSLOGSYSDEST is modified.
Activate Technical Content
When starting the Data Warehousing Workbench (transaction RSA1) for the first time, the content is activated automatically.
Set the BW Transport System as Default
Field TADIRPOPUP in table RSADMINS (System Settings) is set to “x”. With this entry, you define that the BW transport system
default system
In case of blank value the dialog prompting the user to enter a transport request does not appear when editing the objects.
Development system: As we need to record changes and collect into transport request, Field TADIRPOPUP in table RSADMINS
be blank.
This setting will work on top of SCC4 transport settings.
Defining the Recording Time for Transports
Go to->transaction code RSA1, click on transport connection.
Then Edit -> Transport -> Switch-on Standard.
Create job and schedules weekly once
Job name: ZBW_OLAP_CACHE_CLEAR
Program name: RSR_CACHE_RSRV_CHECK
Schedule report to clear the DTP buffer
Job: ZBW_DTP_CACHE_CLEAR
Program: RSBKCHECKBUFFER
Deleting Messages and Parameters of the BW Background
Job: BI_DELETE_OLD_MSG_PARM_DTPTEMP on daily basis
Program: RSBATCH_DEL_MSG_PARM_DTPTEMP.
Metadata repository configuration
Prerequisite: The HTTP or HTTP(s) port needs to be open based on the usage. By default, metadata repository will open using
case if you want to launch metadata repository using HTTPS protocol, you can add the below ICM parameter in the instance p
code and restart the ICM in SMICM transaction.
Icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http,
PROT=https, HOST=logicalsystem.FQDN, PORT=XXXX (HTTPS PORT NO)
Transaction code: STRUST
Activate SSL server Standard"
SPRO -> Maintain web protocol HTTP/HTTPS.
Transaction code SICF: Activate service “rso_metadata_repository”
Metadata repository then launches fine in RSA1transaction.
Activate personalization content:
Create Development package with project specific naming convention using T-code SE21 or SE80.
Then activate the personalization content using SPRO transaction
Sl. No. SLES 12 Package Prerequisites
1 Swap Space
2 Configure uuidd
4 Activate sysstat
5 Linux Kernel Parameter
Media Installation
Kernel Archive
SAP IGS Fonts and Textures
Installation for SAP IGS integrated in SAP Kernel
Host Agent
Language DVD
DVD containing the languages
DB client
Recommendation
For typical use types the recommended size of the swap is 20GB for systems with main memory
sizes greater or equal than 10GB. Systems with less than 10 GB should have a swap partition size
double that of the main memory (2 x RAM).
Activate sysstat (service boot.sysstat) to run the System Activity aRchiver (sar).
SAP Configuration Requirements
numa_balancing=disable
processor.max_cstate=1
intel_idle.max_cstate=1
Kernel Part I (753) (DB Independent)
Kernel Part II (753) (DB Dependent)
Reference SAP Note/link
SAPEXE_501-80002573.SAR or SAPEXE_500-
80002573.SAR
SAPEXEDB_501-80002572.SAR or SAPEXEDB_500-
80002572.SAR
