Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Support Package Plan

Former Member
0 Likes
580

Hi Experts,

We are going to start on next semester a new support package implementation in our R/3 4.7. As ABAPER I would like to know what is the best plan I have to have in mind to execute it.

Could you please give me some advices in order to prepare the enviroment and Z objects/programs as well for this 'small project'?

Points will be rewarded.

Michel Khouri

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
560

Hi MK ,

SP upgrade will not effect any Z objects until unless they are copied of Standard SAP program.

If u done any changes in any standard applications then it will ask for Accept SAP changes or retain changes done @ ur end .

tcodes involved in this is SPAM , SPAU , SPDD .

SPAM is to Import SP patches ,

SPAU is for Code Modifications

SPDD is for DDIC changes

Regards

Prabhu

5 REPLIES 5
Read only

suresh_datti
Active Contributor
0 Likes
560

It is a common practice to apply the support packs initially in a sandbox environment. As an ABAPER, you would ensure there are no syntax errors & resolve if there are any. If you have copied any Std Programs into Z-versions, you might have to look out if any major enhancements were made to such Std Programs. Sometimes, you will need to incorporate the same chnages in the custom version to keep in sync. And it might also happen that the enhanced version of the std program would meet your reqt & drop the custom program. It is mostly the Business Analysts who do the testing during the SupportPacks & report any ABAP related issues for resolution.

~Suresh

Read only

0 Likes
560

Hi,

In Addition to Suresh response, I would like to add one point. You need to taken care that, no standard SAP code is in modified stage in development or in test systems. The code should be same as one in production. Hence you need to eighther roll back the changes done in Development or those present in test systems and make the version same as one in Production environment.

Regards,

Shahu

Read only

Former Member
0 Likes
561

Hi MK ,

SP upgrade will not effect any Z objects until unless they are copied of Standard SAP program.

If u done any changes in any standard applications then it will ask for Accept SAP changes or retain changes done @ ur end .

tcodes involved in this is SPAM , SPAU , SPDD .

SPAM is to Import SP patches ,

SPAU is for Code Modifications

SPDD is for DDIC changes

Regards

Prabhu

Read only

0 Likes
560

Thanks for your tip.

So, I guess the SP application (SPAM , SPAU , SPDD) is done by BASIS team. And ABAPERS are responsible to fix programs that had problems due SP.

As Z's programs are not effect by SP, unless std copies, is there any way to know what are all the std copies in our enviroment (programs, objects, etc)?

This question above is essential to determine my SP plan.

Thanks again!

Michel Khouri

Read only

0 Likes
560

>>is there any way to know what are all the std copies in our enviroment

>>(programs, objects, etc)?

There is no Std approach.. you will not know unless you look at each of those Custom Object or if the previous developers have doucmented the changes.

~Suresh