How to Approve Download Basket in SAP Solution Manager

When you generate a stack XML, the required software is automatically approved for download. However, when you want to download a single patch (to fix a bug for example), you would add the software to download basket, but it would be sitting there waiting for approval.

You can manually approve the software using the function module /TMWFLOW/MO_UI_BASKET_AUTHORIZ

Log in to Solution Manager system.

Call transaction SE37 and execute the function module  /TMWFLOW/MO_UI_BASKET_AUTHORIZ

How to Approve Download Basket in SAP Solution Manager

Set I_OSS_RFC = SAP-OSS and execute

How to Approve Download Basket in SAP Solution Manager

Select the software file and click on Confirm download

How to Approve Download Basket in SAP Solution Manager

Now the software will be ready to download in the Download Basket.

You can also use the report /TMWFLOW/RMOBASKETAPPROVAL to approve the software.

SUM Javaonly update on Dual Stack

SAP recommends using SUM tool for updates or upgrades, and at the same time they support SPAM and SAINT tools for updating ABAP stack. Using SPAM/SAINT is faster (and at the same time time tested method we all are comfortable with). As long as SAP continues supporting SPAM/SAINT, Basis admins are more likely to use it.

For J2EE stack, SAP has discontinued support of updating using using JSPM. Therefore patching J2EE can only be done using SUM.

In case of Dual Stack, because JSPM is not supported, J2EE can only be updated using SUM. You would still prefer to update the ABAP part using SPAM/SAINT. But you cannot patch ABAP and then start up SUM with default options to patch J2EE.

SUM Javaonly update on Dual Stack

It will error out on the ABAP side of SUM.

To patch J2EE on Dual Stack system, you can start SUM using the following option:
STARTUP javaonly

With this option, SUM will not patch ABAP stack and will only patch the J2EE patch.

The advantage? One can patch ABAP using SPAM/SAINT and then patch J2EE using SUM, eliminating the need for shadow instance and speeding up effort spent on SPS updates.

SUM Error: Could not detect AS Java release

This post discusses various known issues and solutions to deal with the following error when running Software Upgrade Manager (SUM):

Could not detect AS Java release.
Return code condition success evaluated to false
for process /usr/sap/<SID>/<INST>/j2ee/cluster/bootstrap/scripts/
for action ACTION_VERSION.

Using DEFAULT configuration fro web methods protection

  1. Edit DEFAULT.PLF file from /usr/sap/(SID)/SYS/profile and set configuration: service/protectedwebmethods = DEFAULT
  2. Restart all the SAP instances (including sapstartsrv) and retry the failed step.

Replace the scripts

  1. Download the latest SERVERCORE.SCA patch file from service market place.
  2. Extract from SERVERCORE.SCA/DEPLOYARCHIVES with an archiver.
  3. Extract the following files from
  4. Go to /usr/sap/[SID]/[INSTANCE]/j2ee/j2ee/cluster/bootstrap/scripts directory and backup all the launcher.* and version.* files.
  5. Copy the files from step 3 to this location.
  6. Ensure that the files have execute permissions against <sid>adm user (run the command chmod +x *.sh *.csh if the execute permissions are missing)

Apply latest patch of SAP JVM

The runs the script, which in turn launches the tool jstart. If there is any issue with the JVM, the tool won't start and the determination of engine release fails. One known solution is to apply the latest SAP JVM,

To troubleshoot any further, you have to tun manually, check dev_server<X> files or the latest traces in work folder.

How to reset SUM password

When you first launch SUM tool, it requests you to set an admin password for the tool itself. If for some reason you forgot the password (feeding incorrect password will throw the error: "The password you have entered for role Administrator is wrong"), here is how you can change it

  1. Stop the SUM tool
  2. Go to the folder <SUM Directory>/SUM/sdt/data
  3. Rename or move the files .sdt_storage and .sdt_keystore
  4. Start the SUM tool again and it will prompt you to set the new passwords

Changing passwords will not reset the upgrade phases, you can continue from the point where SUM stopped. Error on Integration Builder Login

As soon as you enter the credentials on ESR/Integration Repository/Integration Directory/Integration Builder, if you see the  error "", it means that the message server could not connect to  the P4 port of the PI system

Call the following URL and check if P4 port is listed:

Try msg_server_port as the port 81NN, when NN is the instance number of ASCS or SCS or Central Instance (where ABAP message server and enqueue servers are running)

Depending on which message server lists the P4 port, maintain the message_server_port (81NN) in the following exchange profile parameters

If the error includes, then the above profile parmaters are not maintained at all and must be maintained along with and