Basis Errors and Solutions

Symptom

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 or upload liveCache dataallow SAP to analyze errors more efficientlyand provide additional checks that stabilize the uploading process

———————– Implementing notes——————————–
This note contains notes that you must implement in the source release before section A, and it also contains notes that you must implement in the target release before section C. (When we use the formulation “section A, B, C or D”, we are referring to the areas of the same name in the initial screen of the /SAPAPO/OM_LC_UPGRADE_50 program.)
These notes for the source release that refer to the program /SAPAPO/OM_LC_UPGRADE_50 (as well as dependent programs and includes) can only be implemented using a fix buffer. The relevant notes listed below are marked “FixBuf”. To do this, import the newest version of the fix buffer (in accordance with Note 813658) before the start of section A.
If you have not yet imported SCM 5.0 Support Package 8, you require the /SAPAPO/OM_UPGR_MARK program to implement the notes mentioned below in the target release. This program is available in Note 994518. If this program is not yet available in your system, first implement Note 994518.
If the system is still locked because of the upgrade, meaning that you cannot use SNOTE to implement the notes, also refer to Note 809504.
Then proceed as follows – exactly in this sequence:
1. Execute the /SAPAPO/OM_UPGR_MARK program (if you have not yet installed SCM 5.0 Support Package 8).2. Implement the notes listed below.3. To continue with the upgrade (section C), call the /SAPAPO/OM_LC_UPGRADE_50 program.

Important (if you have not yet installed SCM 5.0 Support Package 8): Do not call the /SAPAPO/OM_LC_UPGRADE_50 program in the time between when you call the /SAPAPO/OM_UPGR_MARK program and when you import the notes listed below. If you have already called the /SAPAPO/OM_LC_UPGRADE_50 program, start at 1.
Important: Always use the /SAPAPO/OM_LC_UPGRADE_50 program 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.
—————————————————————–

Other terms

/SAPAPO/OM_LC_UPGRADE_50, upgrade

Solution

—————————————————————–
For an upgrade, we recommend that you always use the newest Support Packages in the target release.
If this is not possible, implement the notes mentioned below.
For information about the minimum requirements for the upgrade to SCM 5.0, see Note 869651.
—————————————————————–
—————– Loading Master Data (step C6) ————-
When you load the master data in SCM 5.0, the system may not create all master data in the liveCache, even though you successfully completed the relevant step (C6). Missing master data may result in errors when you later load the transaction data (C7). Therefore, for security reasons, we recommend that you use transaction /SAPAPO/OM17 to perform a consistency check on resources and product-location combinations after you load the master data and before you load the transaction data.
Notes 987666 and 1014197 provide the relevant error handling for step C6 so that the creation of the master data (step C6) terminates with the relevant message if an error occurs. As a result, a consistency check using transaction /SAPAPO/OM17 is no longer required.
—————————————————————–

Notes that you must implement into the source release (Prepare, before Section A):
The notes that refer to the program /SAPAPO/OM_LC_UPGRADE_50 can only be implemented using a new fix buffer. You must import this fix buffer before section A (in accordance with Note 813658). All other notes can be implemented using transaction SNOTE.
Note SP Priority Short Text
1351213 4 New check in /sapapo/om_check_activities…
1297605 – /19 4 New check in /sapapo/om_check_activities
1239634 3 /sapapo/om_check_activities: I/O nodes and categor…
1040742 – /32 4 /sapapo/om_check_activities: Activities without start times
1035428 27/32 3 /SAPAPO/DELETE_LC_ANCHORS may not run during upgrade
1007367 – 6 Consistency check on DP data before the upgrade
984297 FixBuf 2 Upgrade to SCM 5.0: Demand Planning
980497 FixBuf 3 Upgrade to SCM 5.0: No comparison in section B
977717 FixBuf 4 Upgrading a system with DP data only
954559 26/31 3 /sapapo/om13: Additional check for incorrect clients
953131 FixBuf 2 Upgrade to 5.0: fixed pegging on negative stocks
936995 FixBuf 4 Upgrade from SCM 4.x to SCM 5.0: Extracting DP times series
918238 25/30 4 Check on invalid secondary resources
846953 24/30 4 RPM: if RPM is not active, it must not be error message
796317 23/29 4 Extended check in /sapapo/om_check_activities
757196 21/29 2 Correction: Extended check in /sapapo/om_check_activities
750727 21/28 3 Enhanced check in /sapapo/om_check_activities
747060 21/28 3 Enhanced check in /sapapo/om_check_activities
744043 21/28 3 Enhanced check in /sapapo/om_check_activities
728288 20/28 2 Integrated consistency check suborders
Notes that you must implement in Release 5.0 (before Section C):
If you have not yet installed SCM 5.0 Support Package 8, you must execute the /SAPAPO/OM_UPGR_MARK program (as described above) directly before you implement the following notes. After you implement the notes, you can continue with step C1 in section C.
Note SP Priority Short Text
1356242 16 3 /SAPAPO/RESOURCES_LC_CREATE runs endlessly
1229835 14 4 Time shifts during upload
1172284 14 4 Analysis tool for Support for the log analysis
1171241 14 3 Time shifts during upload
1171011 14 3 Repeating an upload causes dump
1160915 14 4 Upgrade comparison: Time shift reason
1153291 13 3 Date shifts during upgrade
1152587 13 4 /SAPAPO/PEGAREA_LC_CREATE terminates with blank error
1096655 11 4 /SAPAPO/OM_UPGR_UPLOAD_ANALYSE: Stock creation
1089308 11 2 Error during creation of resources in liveCache
1084026 11 3 Speeding up the process of loading master data
1078058 11 2 Upgrade or download/upload: Starting points after termination
1073183 11 4 Upgrade or download/upload: Reducing the comparison runtime
1053895 10 3 Changes to UpgradeComparer and Upload/DownloadComparer
1014197 9 2 Logging for errors during creation of resources in liveCache
1036343 9 3 Upgrade or DownUpload: Error when creating stocks
1035428 – 3 /SAPAPO/DELETE_LC_ANCHORS may not run during upgrade
1035162 9 2 Down/upload or upgrade: Avail resource cap (time stream)
1017787 8 4 Upgrade to SCM 5.0: /sapapo/delete_lc_anchors austr.
1001962 8 3 Upgrade or down/upload: Loading master data
1004531 8 2 Upgrade 4.1->5.0 Compare returns differences in time calcul.
994518 8 2 Problems implementing upgrade notes
989800 – 2 Missing resources after loading the master data
988741 8 3 Improvements to the upgrade process and download/upload
987666 8 2 Logging for errors during creation of resources in liveCache
985039 7 4 Upgrade/upload of liveCache data: too many errors displayed
984297 8 2 Upgrade to SCM 5.0: Demand Planning
977717 7 4 Upgrading a system with DP data only
955473 6 3 Resources not created in liveCache
961872 6 4 Upgrade analysis program: Recreation for tracing
959245 6 3 Upgrade to SCM 5.0, behavior with master data job termination
954200 6 2 Upgrade to SCM 5.0: non liveCache-relevant clients
948083 5 2 Upgrade SCM: External constraints not complete
946175 5 4 Upgrade to SCM 5.0: Multiple automated steps
945617 5 4 Upgrade to SCM 5.0: “LEA” connection is not created
933581 4 2 Performance of TPVS upgrade report
931779 4 3 Upgrade: Error in /SAPAPO/OM_FIX_PEGGING_CHANGE
871254 4 4 Analysis of delayed requests
919315 3 2 Upgrade: Duplicate constraints
916696 3 4 Upgrade: SLCA_LCK_SYNCHOWNERS follow-up
905584 2 3 Upgrade to SCM 5.0: Red lights in comparison time series
905403 2 4 Upgrade to SCM 5.0: Detailed error analysis for DP data
895227 2 4 Upgrade to SCM 5.0: Time series detailed comparison
894210 2 2 Upgrading 4.x to 5.0: Problems with table /SAPAPO/ORDKEY
878167 1 2 Many requests missing when upgrading from Release 3.x