Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-EPT (Application Component) Processes and Tools for Enterprise Applications⤷
BS_REUSE_AKH (Package) Package for Components in the AKH
IMG Activity
| ID | BCV_MIGRATION | Migrate Data from PCV to BCV |
| Transaction Code | S_BTD_53000168 | (empty) |
| Created on | 20091111 | |
| Customizing Attributes | BCV_MIGRATION | Migrate Data from PCV to BCV |
| Customizing Activity | BCV_MIGRATION | Migrate Data from PCV to BCV |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BCV_MIGRATION |
Use
In this Customizing activity, you can migrate the data you used in Product-Centric View (PCV) to Business Context Viewer (CA-EPT-BCV).
If you used Product Centric View (PCV), you can migrate your PCV configuration data into BCV. This reduces the effort of having to manually create the PCV objects, such as query views, queries, search connectors in BCV again.
Note that not all configuration data can be migrated. For example, in the case of overviews and dashboards you have to define the layout again.
Requirements
Standard settings
Activities
This Customizing activity provides you with several options. You can choose from the following migration modes:
- Simulate
Choose this option to simulate data migration. The system offers a list with information that shows you which data can be migrated successfully and where it expects problems to occur.
- Insert New Records
Choose this option to migrate data for the first time or to migrate data that has not yet been migrated.
This might be necessary when you create PCV configuration data after you execute the data migration for the first time.
- Modify Existing Records
Choose this option to overwrite BCV configuration data with data migrated from PCV. This might be necessary when you correct PCV configuration data and want to migrate these corrections to BCV. Note that the system migrates all PCV data into BCV and that BCV data might be overwritten.
You can migrate data as often as you like. After the first migration using the insert or modify methods, the system displays a note saying that the data has already been migrated when you try to execute the migration with this method again.
The following additional options are available:
- Migrate Statistical Data
Choose this option to migrate the query and search connector statistical data as well.
- Check Own Search Connectors
If you choose this option, the system displays a warning when own search connector types are used, as they may contain additional configuration data that is not automatically migrated.
- Check BAPI Implementations
If you choose this option, the system displays warnings when non-standard classes of the BAPI search connector are used. In this case, you must manually adapt the implementation of such classes so that they work in BCV.
- Check BAdI Implementations
If you choose this option, the system displays warnings when BCV BAdIs are implemented. In this case, you must manually adapt the BAdI implementations so that they work in BCV.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | BCV_MIGRATION | 0 | BTD0000012 | Configuration |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /BCV/MIGRATION | T - Individual transaction object | /BCV/MIGRATION |
History
| Last changed by/on | SAP | 20091124 |
| SAP Release Created in | 702 |
