Skip to Content

SCM on HANA

1. SAP SCM version 7.02 has been available on HANA 1.0

As per below path to upgrade SCM system to EHP2 FOR SAP SCM 7.0 ON HANA

/wp-content/uploads/2013/05/p1_211476.png

Any release of  SCM system first upgrade to EHP2 FOR SAP SCM 7.0 ON HANA on existing DATABASE using SUM tool.

SUM tool( Software Update Manager 1.0 SP09 sap note 1843776)

2. Database migration

2.1 Install SAP HANA

      SAP Note No. 1514967

2.2 Heterogeneous system copy

        –Before migration, implement the SAP Note 1775181 to preserve aggregates in SAP  APO             

          For more information, also see SAP Note 1822975.

       –SAP Note No. 178505

        —SAP HANA runs natively on Unicode only .If Source system is non Unicode so we        

            need to convert it to Unicode during database migration more information can be          

           found in sap note 1051576

       –Perform the following immediately after the migration and before post-migration

            activities: Information related to SAP BW post migration activities (compulsory)

2.3 CAUTION

          Do not start SAP BW before implementing these steps.

          Implement SAP Note 1695112. This SAP Note contains the document First guidance… BW   

           on HANA (ORANGE) Fresh Installation/Import – including unified Installer which describes   

          the steps you must carry out in detail.

3. Livecache

You have the following options to install SAP liveCache:

SAP liveCache is integrated in the SAP HANA database, so that SAP liveCache and SCM Server are running on the same database instance.

SCM Server is installed on the SAP HANA database, while SAP liveCache is installed on a separate (non-HANA) server using SAP MaxDB technology

liveCache is available to be deployed as a technical part of HANA DB from SCM 7.02, Version for HANA SP01.Migrating SCM to SAP HANA with integrated SAP HANA liveCache – 1825703

https://service.sap.com/sap/support/notes/18257033.1

/wp-content/uploads/2013/05/p2_211477.png

The following figure shows one deployment option for SAP Supply Chain Management. The ABAP stack runs on a SAP HANA database, while SAP liveCache and SCM Optimizer run outside of SAP HANA. In this option, SAP liveCache is installed as in all previous releases, as a separate instance, noton an SAP HANA database but on SAP MaxDB technology.

3.2

/wp-content/uploads/2013/05/p3_211526.png

The following figure shows another deployment option for SAP Supply Chain Management. The ABAP stack runs on an SAP HANA database, together with an integrated SAP liveCache, while SCM Optimizer runs outside of SAP HANA.

The following software components are either mandatory or optional for this deployment option, as indicated below.


4. The following table shows which technical usages and assigned product instances are available with SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA:

/wp-content/uploads/2013/05/p4_211527.png

5. Limitation

5.1 Dual-stack split

As only ABAP components are enabled for SAP HANA, and dual-stack systems are not supported beyond Business Suite i2011, (see SAP Note 1655335) you cannot deploy a dual-stack system (with both ABAP and Java components running in the same system). If your SAP SCM system is currently implemented as a dual-stack system, you have to perform a split.For information on how to do a dual-stack split, see the following SAP Note 1686144

5.2 Solution Manager Implementation

For SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA, SAP does not provide SAP Solution Manager Implementation content. If you want to implement a new process or scenario using the SAP Solution Manager Implementation content, you can do so before implementing SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA


6. POST Installation task

6.1 Adjusting the Installation Path for SAP SCM Optimizer

In SAP SCM Optimizer 10.0, the default installation path has changed from APOOPT to SCMOPT. As opposed to older versions of SAP SCM Optimizer, where the default installation path was fixed, you can change this installation path as of SAP SCM Optimizer 10.0. The selected installation directory is later on referred to as <INST_DIR> in this guide.

Furthermore, all subdirectories have been deleted so that any SAP SCM Optimizer executables are extracted directly to the chosen installation directory.

This means that after you have updated your system from SAP enhancement package 2 for SAP SCM 7.0 to SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA, and installed SAP SCM Optimizer 10.0, you must adjust the installation paths in your ABAP application server where SCM is installed.

Procedure

To adjust the installation path, proceed as follows:

If you use a standalone gateway instance, start the gateway instance.

Log on to the ABAP application server.

Call transaction SM59. The Display and maintain RFC destinations screen appears.

Open the node TCP/IP connection.

Double-click each SAP SCM Optimizer destination name. The default SAP SCM Optimizer destination is called OPTSERVER_<Optimizer01>, but if you set up RFC connections for additional SAP SCM Optimizer servers, you must change the installation paths for these as well.

The RFC Destination OPTSERVER_Optimizer01 screen appears.

On the Technical Settings tab page, in the Program field, check your program path, and change it.


6.2 Migration of SAP SCM to SAP HANA


To set up SAP NetWeaver Business Warehouse (SAP BW) when migrating the SAP SCM system to a SAP HANA database, proceed as follows:

Activate the myself source system in SAP BW (BW client) in transaction RSA1, under ModelingSource SystemsBWActivate.

Install the latest version of the following BI Content InfoObjects in transaction RSOR:

0LANGU

—0HIENM

Run the report RS_BW_POST_MIGRATION

Run the report RSDU_TABLE_CONSISTENCY in background processing mode. For more information about executing the report, see SAP Note 1695778). During the first run, the report creates an analysis. If it finds errors, you must run the report a second time using the Repair option, also in background processing mode.

NOTE

Depending on the number of tables to be repaired, the report can take several hours to run


Important notes:

SAP Event Management and SAP Extended Warehouse Management are not

released for productive usage with this product version.

The productive usage of SAP Extended Warehouse Management within SAP

enhancement package 2 for SAP SCM 7.0, can be achieved by installing the

Add-On SAP EWM 9.0 SP04.

With SP01 a seperate SAP liveCache installation can optionally be

migrated into SAP HANA (note 1825703).

References

•       SAP Notes

•       1768043 SAP EhP 2 for SAP SCM 7.0, version for SAP HANA

•       1825703 Migrating SCM to SAP HANA with integrated SAP HANA

•       1785057 Recommendations for migrating suite systems to SAP

•       www.saphana.com

•       Product upgrade guide for SAP Enhancement Package 2 for SAP SCM 7.0, Version for SAP HANA

•       For more information please check above mention note and upgrade guid

Thanks

Atul

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply