How to save configuration information in sap abap application?
There are parameters that I would not want to pass from production environment to qa. Personnel such as network path and URL. 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 these parameters. And it is error prone.
Is there a way to store the configuration information in such a way that it is not passed around using th database?
Thank.
source to share
In short: no - at least that would be very unusual in a SAP environment.
If your QC system is set up as a system copy of your production environment (which is the usual way), there are several steps that need to be taken for the system to work properly. This includes some configuration, which can be as simple as file paths such as you mention, and the addresses and names of "partner systems". For example, one of my clients is a bank, so by copying his production system, he makes three times sure that no activity on the QA side accidentally expires on the production side. Some other changes have also been made, such as hiding the names and addresses of people so no mail is accidentally sent, etc.
There are several ways to make it as easy as possible to apply these changes (look at any SAP documentation or books on SAP Transport and Change management, I had one from Sue McFarland Metzger or so it was good). From what I've seen, there are usually a bunch of transports that change configuration and setup, etc. In the QA system for the corresponding values.
Hope it helps.
source to share
Your question is not clear, are you talking about standard or custom config?
Hello, assuming you store these paths in table Z, then some stores put sy-sysid (system id) as one of the columns. Maintain all systems in your dev and transport them to production. It gets painful after a while, so I only suggest this for information that doesn't change much (file paths might be good). In the meantime, there is no need to know about it. ”
T.
source to share
You cannot prevent the configuration stored in the database from being copied to the cloned instance. However, you can configure the configuration store to prevent copied entries from being used. You should check with your base administrators if they can guarantee that the cloned system will receive a new system identifier (SID). If so, you can simply use SID as a key field in your config table. After the system copy, the SID will be changed and the cloned system will no longer access the original records.
source to share