You have to initialize the liveCache, or you want to migrate the liveCache to another operating system or convert your system to Unicode, and therefore you want to back up the liveCache data first so that you can reload it into the liveCache afterwards.
-------------------------- !!! CAUTION --------------------------
The program /SAPAPO/OM_LC_DOWNLOAD_UPLOAD may only be used if the SCM release (for example, SCM 4.0) remains unchanged. If you intend to implement yet another major release upgrade (for example, SCM 4.0 to SCM 5.0) at the same time as switching to another operating system or converting to Unicode, then you must not use the /SAPAPO/OM_LC_DOWNLOAD_UPLOAD program.
Instead, use the relevant upgrade program in accordance with the upgrade guide (for example, use the /SAPAPO/OM_LC_UPGRADE_50 program for the upgrade to SCM 5.0).
In addition, make sure that during the data backup described here, the /SAPAPO/DELETE_LC_ANCHORS report is not entered as a postprocessing report for liveCache initialization. Otherwise you may experience a loss of data.
liveCache, data backup, migration, Unicode, conversionReason and Prerequisites
This note is only relevant if you use SAP SCM 4.0 or higher. If you use APO 3.X, see Note 541644.
-------- Minimum requirements / Known problems ----------
For minimum requirements and known problems when you download or upload, see Note 1008187.
Make sure that the RFC connections for each client are maintained in accordance with Note 305634. If this is not the case, you may experience some problems.
As of SAP SCM 4.0, the /SAPAPO/OM_LC_DOWNLOAD_UPLOAD program is used to extract all transaction data (orders and stocks) from the APO applications (SNP, DP, PP/DS, CTM, ATP, TP/VS, and so on) in the liveCache and reload it into the liveCache after the liveCache is initialized. The RPM application (Rapid Planning Matrix) is the only application that has some restrictions. If you use RPM, refer to the supplementary information at the end of this note.
The relevant master data is not extracted from the liveCache because all master data is constantly redundant in the APO database and liveCache. After the liveCache is initialized, the /SAPAPO/UPGRADE_LC_ANCHORS program transfers this data from the master data table in the APO database to the liveCache.
To access the overview screen, execute the /SAPAPO/OM_LC_DOWNLOAD_UPLOAD program in transaction SE38 in a productive client. The program is divided into four sections:
Section A: Preliminary tasks (to be performed not more than two weeks
before the download)
Section B: Download (backing up the transaction data in the APO database)
Section C: Upload (copying the master data and transaction data from the
APO database to the liveCache)
Section D: Postprocessing tasks (to be performed not later than four
weeks after the upload)
In each of the four sections, execute all steps marked as "must" in the specified sequence. However, SAP recommends that you carry out all steps, if possible. In particular, you should perform the consistency checks and data comparisons. For more information about the individual steps, choose Info (colored blue).
To ensure that users are not logged on to the system during the download or upload and/or that new data is not imported into the system through the core interface (CIF), an upgrade is simulated. This means that only the DDIC user can log on to the system and that the CIF queues are stopped. You can also perform the download and upload with a user other than the DDIC user. (In this case, skip the step "Lock All Users Except DDIC" in Section B: Download") However, if you use another user, you must ensure that other users are not logged on to the system, that background jobs are not running, and that the CIF queues were stopped to avoid data inconsistencies.
- Section A (Preliminary tasks):
Execute all steps listed in Section A in the given sequence approximately two weeks before the download.
For more information about the individual steps, choose Info (colored blue).
In addition, execute the /SAPAPO/OM_TS_LCCONS report as a preparatory measure. For further information, see Note 1021038. As of SCM 5.0, you can add the /SAPAPO/OM_TS_LCCONS report with Note 1021088 as an additional subpoint to step A6, so that a separate execution using transaction se38 can be omitted.
In addition, in SCM 4.X, you must execute the reports /SAPAPO/TS_LCM_CONS_CHECK_ALL and /SAPAPO/TS_LCM_REORG_SNP and clean up any differences that arise. Use the report /SAPAPO/TS_LCM_CONS_CHECK to clean up the differences found by the report /SAPAPO/TS_LCM_CONS_CHECK_ALL. As of SCM 5.0, the reports mentioned above are integrated into the relevant part of section A in the program /SAPAPO/OM_LC_DOWNLOAD_UPLOAD.
In addition, you should execute the programs /SAPAPO/OM_ORDKEY_ORDMAP_CHECK and /SAPAPO/OM_CHECK_ACTIVITIES as preparatory measures in Release SCM 4.0. You should use the relevant program to delete any inconsistencies that may occur. For more information about deleting from the check programs or also about the necessary postprocessing, see Notes 929903 and 603593.
After you have performed the consistency checks in section A successfully, no application data should be changed. In the Demand Planning application, no longer make any changes to planning areas or planning object structures, in particular. For example, do not change the initialization horizon of planning areas or key figures, do not change planning object structures, or add or delete characteristic combinations. However, if you do make changes, perform the consistency checks contained in section A again. SAP recommends that you call application transactions only after you have carried out the procedure described here successfully, that is, after section C.
- Section B (Download):
In this section, you extract the transaction data contained in the liveCache from the liveCache. To do this, execute all steps listed in Section B in the given sequence.
In the "Download liveCache Data" step, you can deselect the "Including DP Time Series" indicator to exclude the demand planning (DP) data from extraction because this may be a large volume of data. For example, this may be useful if a backup of the demand planning data already exists in InfoCubes or if the demand planning data can easily be restored. However, this indicator is set by default. Note that the demand planning data is not extracted if the indicator is not set and that this data is lost when the liveCache is initialized.
You cannot prevent the extraction of other application data.
Between the successful download of transaction data from the liveCache and the successful comparison of the liveCache data with the download in section C, do not make changes to the transaction data in the liveCache under any circumstances because this may lead to data loss. These changes include, for example, changing the initialization of planning areas in the Demand Planning application, changing the initialization horizon of planning areas or key figures, changing the planning object structure or performing consistency checks with the repair option. Do not call application transactions or programs for consistency checks in the other applications, (for example, /SAPAPO/OM17, CIF delta report and so on) under any circumstances.
However, if you do make these changes after the transaction data has been downloaded, repeat sections A and B for the affected planning versions(s). You can repeat the download for a specific planning version. You do not need to edit planning versions that are not affected by the changes again.
To repeat the download for a planning version, select the "Client-specific" field and enter the relevant planning version in the "Planning Version" field. Since the download for the planning version has already been carried out once, before you schedule the relevant job, delete the transaction data from the previous download from the database. Before the job scheduling, the system issues a dialog box prompting you to delete the data. Confirm the dialog box. The system deletes the data only for the selected planning versions. When the jobs have been completed without errors, you can proceed with the following steps.
In this context, you should also bear in mind that the traffic lights of the "Download liveCache data" and "Compare liveCache with download" steps (both in Section B) may not switch to green even though all jobs recently executed to download or compare data were successful. This also applies to the traffic lights for the "Upload liveCache Data" and "Compare liveCache with Download" steps in Section C. Choose Info (colored blue) and read the "Technical Description of Information Display" paragraph for more information. (Comment: If you have implemented Note 1106226 or imported the relevant Support Package in the system, the step "Compare liveCache with Download" is no longer available in section B.)
The traffic lights display has another additional feature: After you perform the "Stop liveCache" step (Section B), the relevant traffic light switches to green. If you then execute the "Initialize liveCache" step in Section C, the liveCache is restarted. Therefore, the traffic light for the "Stop liveCache" step (Section B) switches to red again. This happens because the current liveCache status is determined for the traffic light display. The same applies to the "Switch Off Logging" and "Activate Logging" steps (both Section C). For more information, choose Info (colored blue). If you use liveCache OneDB, you cannot stop the liveCache during the procedure and therefore, points such as "Restart the system" and "stop liveCache" are deactivated (Note 1102801) and should not be executed.
Wait until all jobs are executed successfully. Then continue with the next step.
Before you proceed with section C of the program /SAPAPO/OM_LC_DOWNLOAD_UPLOAD, note the following preparatory measures depending on your application:
- If you only want to initialise liveCache without changing the operating system, the hardware or convert to Unicode, proceed with section C.
- If you want to change operating systems, use an installation guide to install a liveCache on the new operating system prior to proceeding with section C. For this, use at least the liveCache/LCA build combination you used on the previous operating system. Do not initialise the liveCache as mentioned in the installation guide. Otherwise you may experience a loss of data. Furthermore, adjust the liveCache parameter of the target instance to the ones in the source instance. Also, use transaction LC10 to adjust the connection data of the liveCache connections (LCA,LDA,LEA).
- A Unicode conversion without a change of operating system or hardware does not require a new installation of the liveCache. However, prior to the liveCache initialisation in section C, you must change the liveCache parameter DEFAULT_CODE from ASCII to Unicode. You can use transaction LC10, the DBM GUI or the dbmcli command
param_put DEFAULT_CODE Unicode
Check if the _UNICODE parameter is set to YES. If this is not the case, you must adjust the parameter accordingly.
You can use transaction LC10, the DBM GUI or the dbmcli command to carry out this adjustment.
param_put _UNICODE YES
In addition, you should also ensure that the Standard liveCache User (for example SAPR3 or SAP
You can check the Standard liveCache User code page using the following SQL command:
select DEFAULTCODE from users where username = 'SAPR3'
select DEFAULTCODE from users where username = 'SAP
If the SQL command does not return the value UNICODE, execute the following command in order to adjust the user code page:
alter user SAPR3 DEFAULTCODE UNICODE
alter user SAP
- Section C (Upload):
In this section, you initialize the liveCache and reload the master data as well as the transaction data that was previously extracted into the liveCache. To do this, execute all steps in Section C in the given sequence. Make sure that, for any liveCache connections, the /SAPAPO/DELETE_LC_ANCHORS report is not entered as a postprocessing report for liveCache initialization. Otherwise you may experience a loss of data.
Before initialization (the step "Initialize liveCache"), make sure that the traffic light for the "Prepare liveCache Initialization" is green. Otherwise, you may experience a loss of data.
When you load the master data (the step "Load Master Data"), make sure that you successfully execute the PEGAREA_LC_CLIENT_
For more information about the individual steps, choose Info (colored blue).
After you complete all of the necessary steps, the liveCache once again contains the transaction data extracted in Section B (Download) and the system is ready for use again.
- Section D (Postprocessing tasks):
This section should, at the earliest, be executed four weeks after the data upload. It releases the memory space occupied by the download table in the APO database. Only delete the data after approximately four weeks because you may need it for troubleshooting if you suspect that errors occurred during the upload and download.
If you are using RPM (Rapid Planning Matrix), read the following additional comment:
For RPM data, only the status matrix is extracted because all other data can be regenerated using requirements planning, and if you saved all of the RPM data, this would impede runtime performance.
|Release Status:||Released for Customer|
|Released on:||27.01.2009 13:08:28|
|Primary Component:||BC-DB-LCA liveCache Applications|