## 6.3.1.6 Business Configuration
Find out which lifecycle management tasks a business process configuration expert (business role SAP\_BPC\_EXPERT ) needs to perform for the administration of business configurations.
## Context
Business configuration is the customization of business applications. In enterprise software, business configuration refers to a predefined set of configuration options that affect its functionality and behavior. You can maintain custom business configuration content in your SAP BTP ABAP Environment to enrich your extensibility scenarios. This includes both functionalities provided by SAP and custom business configuration objects developed using ABAP Development Tools (ADT).
If you're looking for more information on how to implement custom business configuration objects, please refer to Custom Business Configurations App [page 2687].
## Requirements
The administration of your business configuration has the following requirements:
- The business configuration is client-dependent. After import, it's only available in the client where the import took place. In contrast, development objects are not client-dependent.
- Business configuration content is usually not directly maintained in a productive system, but created in a development system, and then transported to the test system and productive system. For more
information on how to set up your system landscape, please refer to the scenarios described in Setting Up and Working with Your Landscape.
- Changes to business configuration content are recorded onto transport requests of the type Customizing . They can be released in the source system and imported in any target system. For more information on how to set up a suitable software component for transport, please refer to Software Components.
## Procedure
You as a business process configuration expert are responsible for the lifecycle management of business configuration content. First, you need to create transport requests of the type Customizing that contain corresponding transport tasks. Once a suitable transport task has been assigned, you can proceed with the creation and adjustment of content. When the content is ready, the transport tasks and the transport requests can be released. The changes will be written to the remote repository corresponding to the software component that was used for transport. The content can then be imported into target systems simply by pulling the changes for the software component that was used. This procedure is valid regardless of the specific landscape setup or whether software components of the type Development or Business Configuration are used.
##  Note
It's possible to maintain local business configuration changes which can't be transported to other systems. If no software component of the type Business Configuration is cloned in the source system, you can still create a customizing transport request in the Export Customizing Transports app. This request will have no target. It can be used to record business configuration changes, but its release will have no effect.
The following sections will introduce the applications needed for both the maintenance and lifecycle management of business configuration content.