Post-Migration Steps – SAP BW on SAP HANA Specific

 Below steps are specific for the BW system on HANA database-

Step 1: Deactivate password change for System Users

In the default settings, the system prompts at regular intervals for changing the passwords of SAP HANA users. This may cause issues for system users because the password may be stored in another system, or jobs are scheduled for them. If such kind of password changes and you don't modify the environment accordingly, this may effect the operating procedure. So, you should deactivate the periodic password change for selected users. For security reasons, you must consider this carefully.

You can deactivate the  password change with the following statement:

ALTER USER SAP<SID> DISABLE PASSWORD LIFETIME.

Step 2: Adapt Privileges

As specified in SAP note 1897236, check whether the database user SAP <SID> has SELECT privileges for accessing the _SYS_REPO and _SYS_BIC schemas. You can use the following SQL command for this purpose:

SELECT GRANTEE, GRANTOR, OBJECT_TYPE, SCHEMA_NAME, PRIVILEGE, IS_GRANTABLE, IS_VALID FROM SYS.GRANTED_PRIVILEGES WHERE GRANTEE = 'SAP<SID>'

If the privileges are missing for these schemas, you must add them to the SAP<SID> user. Logon to the SYSTEM user, and expand the tree below your SAP HANA system in SAP HANA studio. Go to SECURITY-USERS, and double click SAP<SID>.

Choose the OBJECT PRIVILEGES tab. Use the '+' icon to add _SYS_REPO and _SYS_BIC, and set the checkmark to READ, respectively, on the right side of the window. Then click on the green arrow icon (DEPLOY).

You no longer need to assign the SELECT privileges to the user for Tables TABLE_PLACEMENT and SCHEMAVERSION because the TABLE_REDISTRIBUTION role encapsulates the required rights and is assigned automatically by the SWPM. (SAP note 1908075).

Step 3: Conversion of Infocubes to SAP HANA Optimized Infocubes

The existing Infoproviders should be converted to HANA optimized to use the full potential of SAP BW on HANA.

You can convert the selected or all Infoproviders to HANA optimized using the report RSMIGRHANADB.

Step 4: Activation of Planning Application Kit (PAK)

By activating PAK, you can considerably increase the speed for BW-IP (Integrated Planning) because numerous planning functions are executed directly through code push down in SAP HANA database. The PAK activation however requires a separate License.

Concluding Activities

Now you can set the SAP BW on HANA system to operation mode again. Call the report BTCTRNS2 to start the batch job execution.

Using report RS_SYSTEM_SHUTDOWN, you can plan the process chains.

Also, import the packages required for SAP BW on HANA system.

Now you can unlock all the users using the tcode SU01 or SU10.

Before releasing the users, add the new system in the SAP GUI, inform them about successful migration completion. Also, check some data flows and reports if they are working properly.

If you have also deployed a BW application server on Java, you should ensure that the Java system users use the new SAP BW on HANA system. Depending on the configuration, you must also adapt the UME configuration and update certificates if required.