zprogramm maintenance..

[Former Member]

During the years of running SAP a lot of Z programms have been developed.

Some programs can be deleted which is no problem but a lot of programs also contain coding that can still be of some interest for future applications.

especially when you search on a where used in a function or class the old obsolete coding for the current organisation can still be relevant.

When I deactivate an include which is obsoleten and I search from a where used I see in the listing that the include is colored red. when I deactivate a normal program I can't see from the where used that it is deactivated and it is normal blue like all other programms ?

are there some procedures guidelines or transactions which can support the maintenance and marking of obsolete programs without deleting. ??

Is there also a way to find out which z-transaction codes are not listed in menus ?

kind regards

arthur

[rainer_hbenthal]

Just one question: who do you think will go through Z programs to find a coding sample or a coded solution? I believe: no one. If the coding is not reusable (cmethods/function modules) no one will ever use it. In Addition, the risk of copying and pasting old code which will not fit into SAp anymore due to severel support packages and/or system upgrades is much too high.

Old code has to deleted or archived so that it is no longer accessible. deactivating is not a choice because it can be actived again by running SGEN. And how to you wanna deactive programs in the productional environment?

[Former Member]

> Just one question: who do you think will go through Z programs to find a coding sample or a coded solution? I believe: no one. If the coding is not reusable (cmethods/function modules) no one will ever use it. In Addition, the risk of copying and pasting old code which will not fit into SAp anymore due to severel support packages and/or system upgrades is much too high.
> 
> Old code has to deleted or archived so that it is no longer accessible. deactivating is not a choice because it can be actived again by running SGEN. And how to you wanna deactive programs in the productional environment?

If we thought and would have no experience with it that we often refer to code sample from historical progams I would not have asked this question. With things like bapis it has already saved tremendous amount of times when there was a example available in our history. even though a lot of packages have past , most functions or bapis rarely change on the input output level.

with things like BIMS I can agree that after 5 years they can be completely obsobelete in terms of changes.

kind regards

arthur

[rainer_hbenthal]

> If we thought and would have no experience with it that we often refer to code sample from historical progams I would not have asked this question.
> kind regards
> arthur

If I had no experience in that i would not have given this answer. Especially the break coming with ERP/Unicode makes most historical reports unuseable.

[Former Member]

> > If we thought and would have no experience with it that we often refer to code sample from historical progams I would not have asked this question.
> > kind regards
> > arthur

If I had no experience in that i would not have given this answer. Especially the break coming with ERP/Unicode makes most historical reports unuseable.

hmm I believe the conversion to unicode is delayed for another year.

and how would a programcoding for for instance a bapi could become totally useless when converted to unicode ?

do all variable declarations and structurenames change all of the sudden ?

it's not that they still need to run that's the problem but that the coding itself mostly contains usefull information that can enhance the speed of new implementations of the coding. if SAP would provide nice and good examples and documentation for every bapi they invent the need to keep old programs would be much less.

[Former Member]

Hi Arthur,

Getting back to your original question......

My thought would be to extend your development naming convention to include a prefex for obsolete code and rename objects rather than deactivate them. That way when the show up on a where-used list it will be clear from their name they are obsolete objects.

Is there also a way to find out which z-transaction codes are not listed in menus ? 

Is this also for the purpose of identifying obsolescence? If so you may be better using the Authorisation Information System reports to find all the Z transactions in authorisation roles, from there you can compare the list of existing transactions. If there is no authorisation to run it, it would seem reasonable a tcode is nolonger used.

Regards,

Nick

[Former Member]

>

> Hi Arthur,
> 
> 
> Is this also for the purpose of identifying obsolescence?  If so you may be better using the Authorisation Information System reports to find all the Z transactions in authorisation roles, from there you can compare the list of existing transactions.  If there is no authorisation to run it, it would seem reasonable a tcode is nolonger used.
> 
> Regards,
> Nick

which report did you have in mind ? I checked the authorisation reports but I could not find a report where I could enter more than 1 transaction or that a wildcard was allowed like Z* ??

kind regards

arthur