Skip to Content

SPAM Patch Update - IS-OIL


Current version:


Required version


IS-OIL 0011 to 0022

When updating this kind of a patch is it requires to open scc4 settings and se06 settings.

We have opened these settings (scc4 and se06), in a training server and done the patch update successfully.

But, is it recommended to open these settings in the Production Server , while continueing with the patch?

or else, Is there any other method to continuing with that. (Creating a transport request in Development and Transporting that to the PRD?)



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Nov 28, 2016 at 03:59 PM

    Hello Zerandib

    normally you apply transports in client 000, I dont find many requirements not to have client 000 open for changes in SCC4, even in production, as long as you control the users that can access that client.

    I am curious what it requires to open in SE06, because that changes are cross-client, I am also not familiar with that add-on but if you give more details on what it requires to be open from SE06 it will be worth a check.


    Add comment
    10|10000 characters needed characters exceeded

  • Dec 01, 2016 at 05:16 PM


    Support Packs of this nature are typically applied via transaction SPAM in client 000 (or in newer systems with the SUM tool from outside the system, but for IS-OIL 600 you'll want to use SPAM). SPAM will not allow you to apply the Support Packs in any other client than 000.

    You do not need to make the system changeable in SE03/SE06 or SCC4. Applying a Support Pack is not considered a modification, as it is SAP-delivered.

    The only transports that you will possibly create yourself will be during the SPDD and SPAU processes while running SPAM in your DEV system. If SPAM finds modifications in your system (whether customizations or changes applied via SNOTE) that touch the same objects as those delivered in the Support Packs, then it will trigger a process by which you can either "reset" the objects to standard (i.e., the version delivered in the Support Packs) or integrate your modifications with the changes delivered in the Support Pack. The results of this process are stored in one or two transports (typically one for SPDD and one for SPAU). After you've finished applying the Support Packs in DEV, and when you're ready to move on to QAS, then you release those transports. However, you do not import them directly into QAS or PRD with STMS. Instead, when you start SPAM in those systems, it will ask you if you have "modification transports" to add to the Support Pack queue. Say "yes" and include the SPDD and SPAU transports. Then SPAM will automatically include those changes at the same time.

    It would be best to have someone expert in Basis and with running SPAM, SPDD, and SPAU manage this process for you.


    Add comment
    10|10000 characters needed characters exceeded