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

y Rv* Programs get overwritten in upgradation?

For User exit includes which are reserved for User Modifications, SAP does not release new version for such programs. So includes of this nature are not adjusted during modification upgrade.

But we have some RV* programs like RV45PFZA, RV60AFZC, RV60AFZD, RV60BFZA which are reserved for User modification.

But After upgradation we found that such program are overwritten by SAP and all are present under SPAU.

What can be the reason of it?

Regards,

Umesh

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jun 03, 2005 at 08:53 AM

    Hello,

    these RV*-Include-Programms with the Form-Exits are delivered empty by SAP. So after an upgrade the empty (SAP-Version) is active. Just put the old version with the customer coding to active. Think, there were no changes in these exits in the last years .

    Reason for this may be that the usage of these Form-Exits is technical a modification. The exits are the oldest i know, existing long before any cmod/smod-exits.

    Regards

    Wolfgang

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 03, 2005 at 08:06 AM

    Hi Umesh!

    That's correct behavior. Reason: technically that are modifications (namespace not Y* or Z*), only the meaning of these routines is user-exit.

    Because there are no well defined interface defninitions (you can change whatever you like), SAP sees changes in these exits as modification - but there is no other way and normally support is still given for these transactions.

    It's old stuff, so here you are facing 'historically' ballast.

    Regards,

    Christian

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Umesh!

      Overwriting - ups, not nice.

      I always include Z* into the form routines - this also helps to organize several developers, which want to change different implementations simultaneously. Also calling immediately own form routines for separate tasks helps organizing. This can be stored in multi includes, so transporting gets some more possibilities.

      Adjustments shouldn't be a problem - but also transaction behaviour might be changed a little bit, so your testing has to be intensive, anyway.

      Sorry, but I guess you weren't searching real help - like I couldn't give to you.

      Regards,

      Christian

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.