SAP NW Newbie

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 Set I_OSS_RFC = SAP-OSS and execute Select the software file and click on Confirm download Now the software will be ready to download in the Download Basket. You can also use the report /TMWFLOW/RMOBASKETAPPROVAL to approve the software.

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. 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 J2E