/SAPAPO/OM_LC_UPGRADE_70: Problems during upgrade

[] [] [] [] [] []

  1. /SAPAPO/OM_LC_UPGRADE_50: Problems during upgradeSymptom The notes specified below correct several problems that may occur when you upgrade from APO 3.0, APO 3.1, SCM 4.0 or SCM 4.1 to SCM 5.0, more precisely, when you download...

Symptom

The notes specified below
correct several problems that may occur when you upgrade from 4.1, 5.0, or 5.1 to SCM 7.0, or more precisely, when you download or upload liveCache data.allow SAP to analyze errors more efficiently.and provide additional checks that stabilize the uploading process.

Important: Always use the program /SAPAPO/OM_LC_UPGRADE_70 to execute each step of sections A to D. If you use transaction SE38 to call the programs that belong to each individual step, errors may occur. You should, therefore, avoid doing this.
—————————————————————–
================ Compression of Demand Planning data ==============
As of SCM 5.1, the Demand Planning data is saved in compressed form in liveCache.
When you upgrade from Release SCM 5.0 or lower to Release SCM 5.1 or higher, this may have the following result: The memory requirement in liveCache for Demand Planning data – depending on the data constellation – in the new release (SCM 5.1 or higher) is up to 40% lower than in the source release (SCM 5.0 or lower). In comparison to the previous releases, the memory requirement in liveCache for the data of the other SCM applications (SNP, PP/DS, ATP, and so on) will not change significantly when you upgrade to Release SCM 5.1 or higher.
The compression procedure saves four bits in the header of the time series for each time series bucket. These bits are used to determine whether the value of the bucket has the same value as the previous bucket, whether the value of the bucket is zero, or whether four bytes or eight bytes are required for saving the bucket value. Therefore, the more bucket values that are equal to zero or equal to the value of the previous bucket, and the more numbers that are lower than approximately two million, the greater the saving. Master data is not compressed.
Other terms

/SAPAPO/OM_LC_UPGRADE_70, upgrade

Solution

—————————————————————–
Implement the notes listed below.
For information about the minimum requirements for the upgrade to SCM 7.0, see Note 1170834.
—————————————————————–
Notes that you must implement into the source release (Prepare, before Section A):
Note Prio SP Short Text
1351213 4 New check in /sapapo/om_check_activities…
1301379 2 FixBuff No stocks are taken into account during an upgrade
1297605 4 19/–/– New check in /sapapo/om_check_activities
1257293 3 * /* /* Upgrade-relevant notes regarding resources…
Notes that you must implement in Release 7.0 (before Section C):
Note Prio SP Short Text
1358960 2 4 Global time interval is too long
1356242 3 4 /SAPAPO/RESOURCES_LC_CREATE runs endlessly
1353440 4 4 Upgrade: Automatic execution is inactive
1337202 3 4 Upgrade: Activity status has changed
1290534 4 3 Upgrade: Error-tolerant job overview
1267136 4 2 Upgrade: Behavior during connection problems
1264474 4 2 /SAPAPO/OM_UPGR_COMPARE_TIME: Application functions improved
1257293 3 * Notes regarding resource time stream, relevant for upgrade
1241534 4 2 Rescheduling at the end of the upload (upgrade)
1229835 3 7 Time shifts during upload
955473 3 3 Resources not created in liveCache

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment