How to migrate your SCM with HANA with integrated liveCache to HANA?
The user is keen to migrate his existing SCM on SAP HANA system with an external liveCache to an SCM on SAP HANA system along with an integrated liveCache. The initial system is an SCM system with Release SCM 7.12 or higher which utilizes SAP HANA as its database and for which the liveCache is externally installed (based on SAP MaxDB technology). The user’s main objective is to migrate the external liveCache to an SAP HANA-integrated liveCache, so the liveCache in this SCM system is then a part of the SAP HANA database.
When the user executes the transaction DB02, the indexes STOCKANC_IX1, MATRIXINDEXTAB~1, MATRIXINDEXTAB~2, and MMRP_DATEVECS~1 are all displayed. These don’t exist in the ABAP Dictionary.
Solution
With the SUM DMO, all the steps apart from point 5 (installation of LCAPPS plugin) and point 10 (liveCache test) are automatically performed.
1. User Calls the report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD and performs the steps in section A. (For further information, see SAP Note 632357). If the user wants her can perform these steps few days prior to migrating the liveCache.
2. User Performs the steps in section B of the report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD in order. In the process, the data stored in the external liveCache is stored in the SAP HANA database. In step 7 from section B, call transaction LC10 and stop the external liveCache.
3. User Deletes the connection data of the external SAP liveCache connections LCA, LDA, and LEA using transaction LC10. Choose SAP liveCache -> Integration -> Display -> Change -> Connection -> Delete.You must carry out the deletion using transaction LC10 so that all relevant tables are included.
4. The maintenance of the connection data for the integrated SAP HANA liveCache does’nt function in transaction LC10. Instead, user utilizes transaction DBACOCKPIT as listed below:
Choose "DB Connections". In "SAP HANA Database", enter the new connections LCA, LDA, and LEA.
Example:
Connection Name: LCA
User Name <name of the ABAP SQL user (SAPSID)>
Password: <Password>
Database Host: <Database server of the SAP HANA database>
SQL Port: 3<Instance number of the SAP HANA database>15
5. In the other SAP Notes and documents, SAP LCA is also referred to as liveCache applications, LCApps, LCAPPS plug-in, and SAP LCA on (SAP) HANA to lay more importance that this version is intended only for use with the SAP HANA database and not in coordination with SAP MaxDB database technology.
For installing the LCAPPS plug-in (that is, component SAP HANA LCAPPS), proceed as explained in 'SAP HANA Server Installation and Update Guide'.
Following the successful installation of the LCAPPS plug-in, the database is in an online mode. A liveCache restart or a liveCache initialization is not essential.
6. User should ensure that the LCAPPS COM routines are all installed appropriately in the integrated SAP HANA liveCache:
For instance, APS_ORDER_GET_DATA must exist under "Catalog => Public Synonyms" in the SAP HANA Studio.
7. In the SAP HANA Studio, user logs on as user SYSTEM to the SAP HANA database and executes the following statement:
GRANT AFL__SYS_AFL_LCAPPS_EXECUTE TO SAP<SID>
8. Stop and start the application server for activating the new liveCache connections.
9. Use the report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD for uploading the master data and transaction data to the integrated SAP HANA liveCache (section C, see SAP Note 632357). Incase this is the first migration attempt and the SAP-HANA-integrated liveCache is still empty, then user can skip the liveCache initialization (steps C-1 and C-2). User can skip the maintenance of the liveCache administration (step 8), too.
If problems takes place during the upload of the data to the liveCache or if the subsequent comparison with the original data indicates differences, then user may be required to repeat the liveCache data upload (section C) following the correction of the associated error. In this case, the data still available in the SAP-HANA-integrated liveCache from the last upload attempt could damage the repeat upload. User should therefore initialize the liveCache (steps C-1 and C-2) before each repeat of section C of the report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD.
10. for completing the liveCache data migration, call transaction LCA03, which performs a short liveCache test.
If the user faces any issues specified above with transaction DB02, he can simply ignore this. In more recent versions, these indexes are no longer visible and displayed.