I don't want configuration information to be transferred with the database in SAP ABAP

The straight answer to this is a big NO. This is one of the most common places of error in the SAP environment. When you create a clone of your production in the form of QA with most of the things as it is from production, you need to make sure that any action in QA after cloning doesn't have any implication or effect on actual production.

Why Configuration Transfer is Problematic

Transferring configuration information directly with the database can lead to several critical issues ?

• System interference ? QA actions might accidentally affect production systems
• Data inconsistency ? Configuration settings may not be appropriate for the target environment
• Security risks ? Production-specific configurations could expose sensitive information
• Functional errors ? Environment-specific settings may cause system malfunctions

Recommended Solution: SAP Transport and Change Management

To handle such a use case, you need to rely on SAP transport and Change management. You need to use the provided transports to alter the existing configurations to QA.

The proper approach involves the following steps ?

Transport Management Process

* Create transport request for configuration changes
* SE80 - Development Workbench
* Transaction: SE10 - Transport Organizer
* 
* Example transport structure:
* DEVK900001 - Workbench Request
*   ??? DEVT900001 - Configuration Task
*       ??? Table entries (customizing)
*       ??? Variant configurations  
*       ??? System parameters

Key transactions for managing configuration transports ?

• SE10 ? Transport Organizer for managing transport requests
• STMS ? Transport Management System for transport routes
• SE09 ? Workbench Organizer for development objects
• SCC4 ? Client administration for client-specific configurations

Best Practices

When setting up QA environments, follow these guidelines ?

• Use system refresh procedures that exclude configuration tables
• Implement environment-specific configuration management
• Establish clear transport routes from development to QA to production
• Document all configuration changes through proper change requests

Conclusion

Never transfer configuration information directly with database cloning. Always use SAP's transport and change management system to ensure proper separation between environments and maintain system integrity.