Skip to Content
author's profile photo Former Member
Former Member

Upgrade and its impact on "Developments"

Hi mates ,

As i was having confusion as to how upgrades in form of Patches / Enhancement packs affect the developments or customer space kindly provide your inputs on the behavior of below mentioned scenarios , during an patch/EHP upgrade.

- If there is a Z - Programme ( Saved in Z package ) . Totally Custom programme like a Z function pool .

- If BADI's or User Exits are implemented . ( Saved in Z Package ).

- If implicit enhancements are implemented . ( Saved in Z package ).

- If a source code modification is done - using the access key ( Saved in Z package/ SAP original Package ).

What would be the impacts on the above mentioned scenarios in case if :

- A patch is updated ( Lets say support package to be applied - 604 - 08).

- If there is an upgrade of enhancement package ( Lets say from EHP4 to EHP5 ).

Looking from the perspective whether Codes would be intact or the ABAPER has to code the things again ?

Looking Forward .

Cheers ,

Dewang.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Jul 14, 2011 at 02:58 PM

    Hi Dewang,

    See SAP Note 16466 - Customer name range for SAP objects. In this note we have the naming conventions to avoid troubles during upgrades.

    I hope this helps you

    Regards

    Eduardo

    PD: I remember after some support-packages on a 46B system, that by an error program, an enhancement didn't work, but the cause was an error program solved with other note. But it's an anecdote.

    Edited by: E_Hinojosa on Jul 14, 2011 4:58 PM

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 15, 2011 at 02:12 PM

    Hello,

    the easiest point are source modifications -

    if you apply patches or upgrade enhancement packages, you'll have to adapt your modifications

    using the SPAU transaction.

    The others points are not as easy.

    Most of you own programming is not affected - if it's really own programming.

    But - often you use standard parts in your own programming - like some standard classes or standard functions.

    Or worse - often there are own z-reports mixed of own programming and standard includes.

    That are the point that may be affected by patches or enhancement packages.

    At least i would run a syntax check using transaction 'SAMT' over all Z-Reports, Z-Function groups and Z-module pools.

    Regards

    Wolfgang

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 18, 2011 at 12:56 PM

    - If there is a Z - Programme ( Saved in Z package ) . Totally Custom programme like a Z function pool . -> These will not be affected

    - If BADI's or User Exits are implemented . ( Saved in Z Package ). -> These will not be affected. If affected SAP will list them out. But it is better to do testing if there are any user exits and BADI have been implemented.

    - If implicit enhancements are implemented . ( Saved in Z package ).

    - If a source code modification is done - using the access key ( Saved in Z package/ SAP original Package ).

    For both of them above sometimes they will when you are updating the same programs. In those cases SAP gives you a warning when implementing the support packs/Patches.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.