Knowledge Management

Question:
Changes made to SAP standard program are stored in which table?
Regards,
Answer:
i dont the the 'code' is actually held like a table? prog. details are held like in TRDIR etc
a file is created of the source code that gets transported. The editor is basically more like sapscript...if anything...
there is TXN to look for mods if you not truning off the asistand - SE95
Answer:
i dont the the 'code' is actually held like a table? prog. details are held like in TRDIR etc
a file is created of the source code that gets transported. The editor is basically more like sapscript...if anything...
there is TXN to look for mods if you not truning off the asistand - SE95
Answer:
Changes made to SAP standard program are stored in which table?Regards,
Program source is stored in D010S or REPOSRC, depending on the release.
So I would say, changes are stored here as well.
If you want an easy way to find out which SAP programs have been modified, and what modifications have been done - that's a different story.
If the developers played by the rules, you'll fint the Object key of the program / function group in table ADIRACCESS.
You use the so-called modification browser (tcode SE95, IIRC).
You can use transaction SE03 to see which transport requests include a particular object.
Or, you can use the version history (or check table VRSD via SE16 to see what versions exist.)
Finally, you can check TRDIR-UNAM.
But all these methods don't work if a developer tried to avoid being detected when modifying the SAP standard.
The only help in this case:
Install a clean SAP system, apply all the appropriate patches, do a remote version comparison for all SAP standard source codes, function modules.
But first, manually check that the function modules which retrieve the versions have been biased.
And while we are at it:
don't use SE38, SE80, ... to manually verify the source code.
These transactions could also have been manipulated.
Answer:
transaction SPAU
_________________
Oscar.