BC sets are a part of SAP Best Practices that are delivered in the form of preconfigured business settings which can be used to assemble either a prototype or a development system. The user can choose the pre-configuration to be used for implementation of a business scenario via the installation roles. When the BC Sets are activated in the development system, configuration settings are automatically carried out and saved in transport requests. If necessary, delta configuration is employed to implement further customer-specific requests that are not covered by the SAP Best Practices scenarios. The transport requests resulting from the BC Set activation and delta configuration are then imported into the quality assurance or production system.
When a BC Set is created, values and combinations of values are copied from the original Customizing tables into the BC Set and can be copied into in the tables, views and view clusters in the customer system. The BC Sets are always transported into the customer system in which Customizing is performed. The loading of BC Sets is logged by the system, i.e. which BC Set was copied when into the system, and any errors which occurred. This information is significant for Continuous Change and Upgrade.
BC Sets are provided by SAP for selected industry sectors, and customers can also create their own.
BC Sets have been developed to save customizing parameter values from a business point of view, (ie a part of the reference model). In order to save the parameters of one Customizing activity for a model element, individual Customizing profiles can be used. These can then be grouped to form Business Configuration Sets.
- 1.1 Simple BC Set
- 1.2 Hierarchical BC Set
1 Types of BC Sets
Types of BC Sets
There are two kinds of BC Sets:
- BC Set (or Simple BC Set).
- Hierarchical BC Set
Simple BC Set
A BC Set can contain data from one or more IMG activities. Each IMG activity is listed separately with its Customizing objects (tables or views). The data is selected by table columns and rows, each column is a field, each row a record. There is no BC Set size restriction.
Hierarchical BC Set
A hierarchical BC Set comprises several other BC Sets, which can also be hierarchical. The hierarchy can have any number of levels. It structures complex system setting data. You can delete or add lower-level BC Sets at any time.
BC Sets can be created:
- You go to the IMG structure, where you can select the Customizing activities. Call the activities in a business process and copy all the values which are relevant for the control of the process.
- A BC Set can comprise several other BC Sets. You can construct complex BC Sets for industry sectors or a group rollout from smaller BC Sets. These are called hierarchical BC Sets.
- You can base a BC Set on existing transports. In certain systems, every changed record is recorded in a transport request. A BC Set can be based on this transport request. BC Sets created in this way must usually be edited.
via the IMG hierarchy
by collecting BC Sets
Via a transport request
- You can edit BC Sets in the system.
- You can activate BC Sets in the system.
- You can see activation logs in the transaction
- BC sets can be later on used as a template.
- They provide continuity.
- Prevent project team members from over writing each others settings.
- Efficient group rollout.
- Industry sector systems are easier to create and maintain.
- Customizing can be performed at a business level.
- Change Management is quicker and safer.
- Upgrade is simpler.
Keep your BC Sets as small as possible to preserve comprehensibility and reusability. You can model complex data in hierarchical BC Sets.