There are parameters that I would not want to be transfered from production environment to qa. Staff like network path and url's. The problem is that in sap abap everything is in the database and when the database is copied to the qa system you have to manually change those parameters. And this is prone to errors.
Is there a way to store configuration information in a way that wont get transfered with th database?
Thanks.
Hi,
your question is not clear, are you talking about standard or custom config ?
T.
In short: no - at least that would be very unusual in a SAP environment.
If your QA system is set up as a system copy of your production environment (which is the usual path), there are quite a few steps to do to make the system work correctly. This includes some configuration, which can be as simple as filepaths such as you mention, but also the addresses and names of "partner systems". For example, one of my customers is a bank, so when copying his production system, he makes triply sure that no activity on the QA side accidentally trickles to the production side. Some other changes are made as well, for example obscuring peoples names and addresses so no mail gets accidentally sent etc.
There are a few ways to make applying these changes as easy as possible (look for some SAP documentation or books on SAP Transport and Change management, I had one by Sue McFarland Metzger or so that was quite good). From what I've seen, there is usually a set of transports that change the configuration and customizing etc. on the QA system to the appropriate values.
Hope that helps.