Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-CCO (Application Component) Client Copy⤷
STRM (Package) Client Copy & Adjustment Tools
Basic Data
| Data Element | CCORIGCONT |
| Short Description | Recording Client for Switch BC Sets |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| 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 | 0 | |
| Medium | 0 | |
| Long | 30 | Create Switch BC Sets |
| Heading | 12 | S BC Sets |
Documentation
Definition
This flag controls whether customizing in this client is to be recorded in Switch BC Sets.
Use
If the recording of Switch BC Sets is active ('X'), customizing changes are put in Switch BC Sets before they are put in transport requests. This affects the following use cases:
- If customizing data is recorded in transport requests in the standard recording module TR_OBJECT(S)_INSERT, it checks which data can be put in Switch BC Sets. This could involve several Switch BC which are offered in a user dialog. When the data has been put in the Switch BC Sets, they are put in the current transport tables (E071/E071K), and the original transport objects (E071) and transport key (E071K) are removed. Then you are usually prompted for a transport request (workbench request, not a customizing request, because the Switch BC Sets are cross-client objects).
When you leave the recording module, the request is given the Switch BC Set and transport objects/keys, which could not be put in the Switch BC Set.
Note: Analogously to the transport request, the recorded Switch BC Set only contains the table keys. When the transport is released, the data parts in the Switch BC Sets are not automatically completed by the system. You can complete the Switch BC Sets, for example, by calling them in change mode of the BC Set maintenance transaction SCPR3. They are completed, and must then be saved by the user. More convenient mechanisms to automatically complete these Switch BC Sets (completion report, integration in transport release, Checkman, ...) are planned, but not yet realized (as of 31.08.2004). - When a new BC Set is created in the BC Set maintenance transaction SCPR3, the user must decide whether it is a Switch BC Set or a classical BC Set. You can change existing Switch BC Sets.
- You can run the report SCPR_MIGRATION_REPORT_SFW in the client which can create Switch BC Sets based on an existing transport request.
Notes:
You need administration authorization in CTS (Change and Transport System) to maintain this attribute. This is in the delivered default authorization S_CTS_ADMIN.
As (Switch) BC Sets are cross-client repository objects, "Changes to Repository and Cross-Client Customizing" must also be allowed in this client (see, "Changes to Cross-Client Objects" in transaction SCC4). Switch BC Sets can also only be created in automatic customizing recording, if it is active in the system. This is also done in "Changes and Transport for Cross-Client Objects" in transaction SCC4.
Dependencies
Example
#############
History
| Last changed by/on | SAP | 20041216 |
| SAP Release Created in | 50A |
