Proper Plan for SAP Support Pack Upload

[Former Member]

Hi Experts,

We are going for Support pack upload of SAP at your firm.

Like to get your suggestions on the Plan we have done for going with the update.

The Present Level of SAP in our server is very low 8 stacks low approx in both the Development Server and Production Server.

What is the best way to apply them from the below mentioned plan.

1. shall we go for 1 stack in Development for the required components then test it for 3-4 days then go for the same stack in Production. So that both the server go sync with each other. This way going till the target stack one by one.

2. shall we go and upload all 8 stacks for the components required in development first one by one and then test the system for all the errors available and then start with the Production. Will there be a transport problem if the system are not in sync for the so many days.

Please suggest which one shall be best suited if any other plan can be used for safe and proper update of Support pack.

-

Jitesh

[former_member524429 · Accepted solution]

Hi,

1. shall we go for 1 stack in Development for the required components then test it for 3-4 days
 then go for the same stack in Production. So that both the server go sync with each other. 
This way going till the target stack one by one.

If Large Support Stack gape is there, then

1. I would perform system copy of Existing Development System into another separate New Test Server.

2. Then , I will generate Side Effect Reports based on the Source-to-Target Support Stack gape. You can request such side effect from SMP at https://service.sap.com/side-effects by selecting the solution and by providing source to target SP level per component.

3.Refer The required SAP Notes regarding OCS Know problems for the support patches. Apply latest SPAM/SAINT Updates. Apply Latest SAP Kernel patches.

4. Apply the Required Support Package stack after taking successful offline backup of Database.

5. Perform SPDD - SPAU adjustment and record it in single/Multiple Change requests.

6. Ask the function team to check the Functionality in new Upgraded TEST system

7. After Confirmation from the Functional & Technical Team, Apply the same support package stack in existing real DEVELOPMENT system and move that SPAU-SPDD adjustment request.

2. shall we go and upload all 8 stacks for the components required in development first one by one
 and then test the system for all the errors available and then start with the Production. 
Will there be a transport problem if the system are not in sync for the so many days.

The same above steps will be applicable here also. Change Requests Transports are not recommended between the systems which are on different Support Patch Stacks. With the above mentioned steps your downtime as well as Development Holiday will be minimized.

Regards,

Bhavik G. Shroff

[Former Member]

Hi

All Steps suggested by Bhavik are appropriate.And also pl Release all the transports(Parent task & Sub-task) requests before you proceed for Patch up gradations and if you have BI system in your Landscape than clear inbound and outbound transactional queues,verify transactional deadlocks (SM12,SM13).

Also verify tablespace size and Redo logs

Regards,

Jasmeen Goswami