on 10-24-2022 11:52 AM
Dear all,
we are preparing for an S4H conversion, hence cleaning up our ERP system from obsolete coding. We are effectively deleting old code, after saving it to an external Git repo.
After code has been deleted, we want to make sure we don't allow new repository objects (let's exclude data dicitionary for now, if that helps) to have the same name as formerly deleted objects. We are talking AS ABAP only.
Example
I could think of different ways to achieve this, however, I'm pretty unsure what's the best way to takle the situation
Ideally the solution already prevents the object creation instead of checking on transport release and it should be working both in GUI and ADT
Don't expect solutions here, obviously, but a nudge in the right direction / best practices how you guys dealt with such requirements on your end.
Cheers
Jens
There is a so-called blocklist monitor when an object e.g. ABAP program is added to the list, and when it is executed, an ABAP dump occurs. Probably this may help developers to identify the namings that should no longer be used.
To have a brief look of the function, please check out Blocklist Monitor Demo Video.
Blocklist monitor is a function inbeded in Decommission Cockpit. Detailed Configuration steps can be found in CCLM How-to Guide.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One could use (or maybe missuse rather) the Naming Conventions in the SAP system. One could insert e.g. the following entry in the object type specific (export mode) maintenance view (V_TRESN) to at least force the object being created in an obsolete package.
However, there seem to be several downsides in this approach
So I don't think this is the ideal answer, albeit our requirement kind of lives in the same vicinity, I dare to say
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.