Important Entries for the Extraction Roadmap Step
This chapter deals with the roadmap step Extraction, in which the Software Update Manager extracts the required software.
In the following, we go into detail of some important phases in which you enter information or confirm the existing values when prompted by the Software Update Manager:
-
Checking the Configuration of sapcpe (Phase PREP_INIT/CHECKPROF_INI)
-
SPAU Fill Level Display (Phase PREP_PARSETUP/SPAU_FILL_LEVEL_DEC)
Password of User DDIC and Database Users (Phase PROFREAD)
Enter the password of user DDIC in the system, client 000.
This password is needed for the RFC connection to the SAP system. To be able to perform all necessary actions, user DDIC needs the authorization SAP_ALL.
During the upgrade, you have to unlock the user. After the upgrade, the user is not locked again automatically.
Usually, it is not necessary to change the password of user DDIC during the upgrade. If you do change the password, you have to change it in the original system, the shadow system, and in the Software Update Manager.
For a description of this procedure, see in the section A.4 Administration of the SUM guide the chapter Changing the DDIC Password.
Enter in addition the SAP HANA database-specific passwords for your database user and for the database user SYSTEM.
Moreover, the Software Update Manager asks for the name and the password of the SAP HANA database security user. However, this dialog appears only when the database user SYSTEM is deactivated. In this case, the Software Update Manager asks for a security user that has the system privilege USER ADMIN. It uses this security user to activate the user SYSTEM if necessary. Then, the user SYSTEM is used for a short time and deactivated again afterwards.
Checking the Configuration of sapcpe (Phase PREP_INIT/CHECKPROF_INI)
During phase PREP_INIT/CHECKPROF_INI, the Software Update Manager is checking various profiles and their settings including the configuration of program sapcpe for the kernel replication.
If there is a problem with the configuration of sapcpe, phase PREP_INIT/CHECKPROF_INI stops and points you to the problem with the kernel directory. Change the replication configuration so that the SAP kernel can be replicated to $(DIR_INSTANCE)/exe.
For more information and the corresponding procedure, see SAP Note
1649026
.
SAP Note Implementation (CHECK4NOTES_TOOL)
A list of SAP Notes is displayed that you have to implement to avoid activation errors later in the procedure. Use the Note Assistant to apply the SAP Notes. After you have implemented all relevant SAP Notes, repeat the phase and then continue the process.
For more information about applying SAP Notes with the Note Assistant, see the SAP Help Portal for your SAP NetWeaver source release at http://help.sap.com:
|
Release |
Path in SAP Help Portal for SAP NetWeaver |
|---|---|
|
SAP NetWeaver 7.3 to 7.5 |
|
|
SAP NetWeaver 7.1 incl. EHP 1 |
|
|
SAP NetWeaver 7.1 |
|
|
SAP NetWeaver 7.0 SAP NetWeaver 7.0 incl. EHP 1, 2, or 3 |
|
SPAU Fill Level Display (Phase PREP_PARSETUP/SPAU_FILL_LEVEL_DEC)
In this phase, the Software Update Manger checks for SAP Notes and repository objects that were modified but not adjusted in the transactions SPDD and SPAU in previous updates. If such objects are detected, the phase SPAU_FILL_LEVEL_DEC displays the dialog Open actions in transaction SPDD and SPAU. This dialog offers you the possibility to complete all outstanding modification adjustments in an early stage of the current update to reduce the adjustment effort at a later point in time.
The dialog shows the following numbers:
- Obsolete and non-adjusted SAP Notes
- Non-adjusted objects that were modified either with or without Modification Assistant, and the SPDD-relevant objects of them
- Modified but non-adjusted objects with active SAP versions that can be reset to SAP standard versions
You can see the same statistics in transaction SPAU, provided that you use the default selections and you filter according to all possible statuses except for the status adjusted. Note that if one or more statuses are excluded in addition, the shown numbers may differ from the numbers in the above mentioned dialog Open actions in transaction SPDD and SPAU of the Software Update Manager.
If you perform the current update on your development system, we strongly recommend that you perform the following actions:
- Confirm all obsolete notes.
- Reset all non-adjusted objects with active SAP version to SAP standard versions.
- Carry out the outstanding modification adjustments.
Afterwards, release the resulting workbench request into the system landscape before you continue with the current update procedure.
In the development system, you can use the report RSUPG_AUTO_ADJ_SPAU. It retrieves the non-adjusted objects that can be reset to the SAP original version and writes a detailed list to a log file. Depending on the number of objects listed in the summary, you can execute this report in the background.
Furthermore, this report offers you the possibility to perform the reset of the listed non-adjusted objects to the SAP original version automatically. For this purpose, set the parameter p_check to <space> and enter a valid and already existing workbench request as value for parameter p_trkorr during the execution of the report.
-
Import the workbench request, which is required for this automatic adjustment, into the subsequent systems before you start the update of these systems.
-
Do not include this workbench request as single transport request or as SPDD/SPAU transport request during the update.


