Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CUS-TOL-BCD (Application Component) Business Configuration Sets⤷
SCPR (Package) Business Configuration Sets
Basic Data
| Data Element | SCPRSWCOMP |
| Short Description | BC Sets: Software Component |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DLVUNIT | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | CVERS |
Further Characteristics
| Search Help: Name | H_CVERS | |
| Search Help: Parameters | COMPONENT | |
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | S/W Comp. |
| Medium | 30 | Software Component |
| Long | 30 | Software Component |
| Heading | 30 | Software Component |
Documentation
Definition
The software component defines a set of software objects which can only be delivered together. A software component is delivered with new functionality in successive releases. Each software component can be patched separately.
Objects are assigned to a software component by assigning the package to which the object belongs, so objects can change software components between releases.
Use
Software components are relevant for BC Sets in the following cases:
- You must assign the BC Set to a software component when you create it. This ensures that the BC Set can only be activated in systems which contain this software component. Only assign software components to the BC Set, for which it actually contains data. The system cannot check whether data contained really only belongs to the specified software component.
Each software component has a release (e.g. component SAP_BASIS, Release 46C). The current release of the software component is determined automatically from the system data at creation. - The software component can help you to find BC Sets which are only intended for use in a certain area (i.e. data for a software component).
- When you activate a BC Set, a check is made that the software component specified in the BC Set is installed in the system (see example).
You can specify a "Default Software Component" in the user settings, which appears by default in the BC Set maintenance transaction when you create and select a BC Set.
Dependencies
Example
It would not be sensible to activate a BC Set containing data for the software component SAP_CRM (Customer Relationship Management), in a system in which this component is not installed.
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 630 |
